In-Sight® Explorer 5.1.1 Release Notes

The In-Sight 8405 is reporting an incorrect maximum segment size during TCP connection establishment. As a result, In-Sight Explorer may not be able to connect to the 8405 (or may lose the connection) if the network adapter of the PC is configured to support jumbo Ethernet frame sizes.

Workaround: To prevent loss of connection, configure the PC’s network adapter to use the default Ethernet MTU (Maximum Transmission Unit) of 1500 bytes.

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

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

The FindPatMaxRedLine function's Ignore Polarity setting can produce unexpected results when the search image has the inverse polarity from the training image. For example, false matches may be found on a blank background having the inverse polarity from the training image.

Workaround: If Ignore Polarity is necessary in the application, it is recommended to set the Fine Granularity setting to 1 or widen the Angle/Scale Find Tolerances.

For EtherNet/IP communications, when using Rockwell RSLogix Studio 5000, version 21 through 24, the In-Sight EDS generated profile’s default Input and Output Assembly sizes (496 bytes for each) cannot be edited.

Workaround: If it is necessary to edit the default size, use and configure a generic Ethernet module. Once the updated In-Sight Add-On Profile (AOP) has been published to the Cognex Support Website, download the latest version, and use it instead of the EDS file or generic Ethernet module.

In the TCPDevice, UDPDevice, WriteFTP, WriteImageFTP, ImportData, ExportData and List Property Sheet, the Host Name drop-down menu does not list Host Names of In-Sight vision systems and/or emulators on the network.

Workaround: Manually enter the host name or the IP address of the target vision system/emulator in the Host Name field.

In-Sight Explorer may recognize a valid symbolic tag name as invalid when the symbolic tag name is in the form of a cell name with the value greater than 32766. For example, when the Extended Native Mode command EV SetCellName(B3,"A32767") is issued, the command will be executed successfully and the symbolic tag name "A32767" will be inserted in cell B3. However, when the Symbolic Tag Editor dialog is opened from In-Sight Explorer, a symbolic tag name error is displayed in cell B3.

Workaround: Do not use a cell name or the form of a cell name for a symbolic tag name.

When attempting to load a job containing the PointFilter and/or NeighborFilter functions that are no longer supported on In-Sight 5.1.x firmware, and the function is password-protected using the Format Cells dialog’s Protection tab, the job load will fail.

Workaround: Load the job to an In-Sight vision system running In-Sight firmware 4.x.x and modify the job. For more information on accessing or removing password-protected cells, refer to the Licensing topic in the In-Sight® Explorer Help file.

When connected to a color In-Sight vision system, and the Record/Playback Options dialog is configured to record color images as 16-bit JPEG image files, the images will be recorded at 24-bit depth.

Workaround: If 16-bit depth is necessary, record the images as Bitmap files (*.bmp).

If a SurfaceFlaw function is configured with an angled or curved region, and the Straighten Images parameter is enabled and the Show parameter is set to the "input and results graphics" option, the only output that will be displayed will be the red overlay graphics.

Workaround: In this type of application scenario, set the Show parameter to the "results graphics" option to view the straightened image and graphics.

If the In-Sight Explorer application is left running for several days with multiple Spreadsheet View connections open, the Spreadsheet View toolbars may be drawn in the wrong location, regardless of user interaction (i.e. turning the toolbars on or off, or attempting to move them to the correct location). The toolbars and menus still function, but they cannot be repositioned.

Workaround: To re-enable the repositioning of the toolbars, close and restart the In-Sight Explorer application (it may be necessary to use the Windows Task Manager to force the application to exit).

In high-precision applications, differences of less than a pixel may be reported if a FindPatMaxPatterns function is constructed to find the patterns returned by a TrainPatMaxPattern function, and the two functions use different external regions for their search and training, respectively. However, if either of the two functions reference an external region that is angled and/or curved, the pixel differences may be much larger.

Workaround: When constructing the job, ensure that the FindPatMaxPatterns and TrainPatMaxPattern function reference the same external region for both searching and training, or use the internal regions of both functions for the searching and training.

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.

If a PLC project created in the English version of GXWorks2 is downloaded to the PLC, and then uploaded to a Japanese version of GXWorks2, In-Sight 5000 and In-Sight 7000 series vision systems will be missing their icons and descriptive information. This issue also occurs if the process is reversed, i.e. the PLC project is created in the Japanese version of GXWorks2 and then uploaded to an English version of GXWorks2.

Workaround: Keep PLC projects within the same language of GXWorks2.

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.

21041

If an In-Sight vision system is on a POWERLINK network and connected to In-Sight Explorer, attempting to download a change to the PLC, or performing a software reboot of the PLC, may cause the vision system to no longer be able to connect to In-Sight Explorer.

Workaround: Disconnect the vision system from In-Sight Explorer before performing any changes or rebooting the PLC. Power cycle the vision system if this situation has been encountered to restore the connection to In-Sight Explorer.

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.