In-Sight® Explorer 5.4.1 Release Notes

© Copyright 1999-2017 Cognex Corporation. All rights reserved.

Version: 5.4.1.11, 05/23/2017

Overview

This document describes the In-Sight® Explorer software, including the following topics:

Note: Visit the In-Sight Online Support Center to download the latest release notes and documentation, including localized versions. In order to access the updated documentation from the In-Sight Explorer user interface and Windows Start menu, you will need to first log on to the PC with administrative privileges. Next, you will need to copy the downloaded documentation to the appropriate location within the installation directory; the default location is: C:\Program Files (x86)\Cognex\In-Sight\In-Sight Explorer 5.x.x\Documentation.

System Requirements

This section describes system requirements for the In-Sight Explorer software.

PC Hardware Requirements

Minimum

Note: The Minimum Hardware Requirements are for PCs that will be connecting to a single low resolution In-Sight vision system running at a slow production speed.
  • Intel® Pentium® 4 processor running at 2GHz (or equivalent)
  • 1GB of available RAM
  • 2GB of available hard-disk space
  • Video card capable of displaying 1024 x 768 resolution at 24-bit color depth (the DPI Display setting must be set to 96 DPI)
  • Network Interface Card (at least 100Mbps) for connecting to an In-Sight vision system

Recommended

Note: The Recommended Hardware Requirements are for PCs that will be connecting up to four In-Sight vision systems.
  • Intel Core™ i7 processor running at 2.7GHz (or equivalent)
  • 4GB of available RAM
  • 2.5GB of available hard-disk space
  • Video card capable of displaying 1920 x 1080 resolution at 32-bit color depth (the DPI Display setting must be set to 96 DPI)
  • Gigabit Network Interface Card for connecting to In-Sight vision systems

Operating System Requirements

In-Sight software has been tested on the following operating systems:

  • Microsoft® Windows® 10 Professional (64-bit)
  • Microsoft® Windows® 7 Professional, Service Pack 1 (64-bit)
  • Microsoft Windows Server 2008 R2, Service Pack 1 (64-bit)

Although In-Sight Explorer may function on other operating systems, systems not meeting the preceding requirements have not been tested and are not supported.

Supported Languages

  • English
  • Japanese
  • French
  • German
  • Spanish (European)
  • Korean
  • Chinese (Simplified)

Supported In-Sight Vision Systems/Sensors

Firmware Version Support

In-Sight 5.4.1 software contains three firmware versions: In-Sight 4.10.4, In-Sight 5.2.2 and In-Sight 5.4.1. In-Sight vision systems with older firmware versions may work properly; however, some features are unsupported with older firmware versions and are not fully tested. For optimal performance, vision systems running older firmware should be updated to the most recent, supported firmware versions.

Note: For a complete list of models and supported firmware versions, refer to the Firmware Versions topic in the In-Sight® Explorer Help file.

In-Sight Firmware 4.10.4

  • In-Sight Micro 1000 series vision systems
  • In-Sight 5000 series vision systems (except In-Sight 5705 and 5705C vision systems)
  • In-Sight 7000 series vision systems (except In-Sight 7600/7800 series vision systems)

In-Sight Firmware 5.2.2

  • In-Sight Advantage Engine

In-Sight Firmware 5.4.1

  • In-Sight 2000 series vision sensors
  • In-Sight 5705 and 5705C vision systems
  • In-Sight 7600/7800 series vision systems
  • In-Sight 8000 series vision systems

Microsoft .NET Framework 4.5

Microsoft .NET Framework 4.5 must be installed prior to installing the In-Sight software. The installer will attempt to download/install .NET 4.5 prior to installation if it is not detected on the system.

Changes & Fixes

Notes:

  • Please see past In-Sight Explorer Release Notes for changes and fixes in previous releases. The past 5.x.x Release Notes are available in the In-Sight Explorer Help file.
  • Change Request numbers (CR#) have been included (where applicable) to improve tracking of Known Issues reported via Cognex Technical Support.
CR# Change/Fix Affected Firmware Version
41201

In the EasyBuilder view, up to two communication protocols can now be added to a job in the Communication application step. When adding two protocols, the TCP/IP or UDP protocol can be added in addition to other communication protocols. Previously, only one communication protocol was allowed to be added in the EasyBuilder view.

 5.4.1
46302 The WriteResultsBuffer function (Input/Output Functions > Network), ReadUserDataBuffer function (Input/Output Functions > Network) and ReadLatchedUserDataBuffer function (Input/Output Functions > Network) have been updated to support the Byte/Word Order parameter for EtherNet/IP, PROFINET and SLMP Scanner protocols. Previously, the Byte/Word Order parameter was only supported for the Modbus TCP Server protocol. 5.4.1
46381

In the EasyBuilder Communication application step, when configuring Format Input Data or Format Output Data for EtherNet/IP, PROFINET and SLMP Scanner protocols:

  • The Data Type drop-down has been updated to include the Byte-Swapped String option.
  • The High Byte/Low Byte and High Word/Low Word checkboxes are now available.

Previously, these options were only supported for the Modbus TCP Server protocol.

 5.4.1

Known Issues

Note: Change Request numbers (CR#) have been included (where applicable) to improve tracking of Known Issues reported via Cognex Technical Support.
CR# Issue Affected Firmware Version
45581 For In-Sight 7600/7800 series vision systems configured for CIP-Sync/PTP, 1588 synchronization accuracy through a transparent clock-switch may increase to greater than 10µs offset from master. 5.4.1
43186 While configuring a Serial Text, Serial Native, TCP/IP or UDP device in the Communication application step on an In-Sight 2000 series vision sensor, the FormatString dialog will show #ERR in the Output String box. To see the Output String, you must click OK to close the dialog, and then the Output String is displayed correctly in the Format Output String tab. 5.4.1
42550 In-Sight Track & Trace job files are not supported on In-Sight models running 5.1.0 and later firmware versions. 5.4.1
32542 EasyBuilder sample jobs are not supported on vision systems or vision sensors running firmware version 5.1.0 and later, however jobs with compatible tools may still load properly. 5.4.1
31638

After renaming the Host Name of an In-Sight vision system or vision sensor configured for PROFINET using the Add Sensor/Device to Network dialog, when attempting to re-connect the vision system or vision sensor to PROFINET, the connection is not established.

Workaround: Restart the vision system or vision sensor after renaming the Host Name. Alternatively, use the Network Settings dialog to rename the Host Name of the vision system or vision sensor, which prompts the user to restart the vision system or vision sensor to make configuration changes to take effect.

 5.4.1
35828 If the vision system is triggered via an industrial Ethernet communication protocol, the JobPass signal is only sent if the job contains a WriteResultsBuffer function. This is not an issue for EasyBuilder applications. 5.4.1
31717 The In-Sight 8405 vision system only supports the Normal Orientation setting when acquiring images, and the Orientation parameter in the AcquireImage Property Sheet is disabled. 5.4.1
32781 The FindPatMaxRedLine function’s XY Overlap setting may be ignored. For example, when searching for two targets which overlap by a very small amount, only one match may be found, regardless of the XY Overlap setting. 5.4.1
32479

Updating the firmware of an In-Sight vision system while connected to a POWERLINK network will result in a code 13710, with the vision system needing to be power cycled and the files restored (the firmware will be successfully updated, however).

Workaround: Before updating the vision system's firmware, follow these steps:

  1. Remove the vision system from the POWERLINK network, and connect the vision system to a network port on the same subnet as the computer running In-Sight Explorer.
  2. Power cycle the vision system.
  3. Update the firmware while the vision system in Ethernet mode.
  4. Place the vision system back onto the POWERLINK network.
  5. Power cycle the vision system.
 4.10.4
27483

While editing the SLMP Scanner protocol in the EasyBuilder View Communications Application Step, if changes are made in the Format Output Data and/or Format Input Data tabs, and the user leaves the Communications Application Step and then selects Undo Communications Changes from the Edit menu, the slmpoutaddressmap file will be corrupted.

Workaround: Do not use the Undo Communications Changes option from the Edit menu; manually edit the necessary changes instead.

 4.10.4
26990

While connected to a Mitsubishi iQ Sensor Solution and an In-Sight vision system, if an attempt is made to change parameter settings (such as Set Parameter or Set IP) while the vision system is Online, a failure code (C05C) is not properly issued.

Workaround: Do not attempt to change parameter settings of the vision system while it is Online. If attempting to change settings while Online, a C05C code, which indicates that write processing has been aborted, should be issued.

 4.10.4