In-Sight® Explorer 5.3.0 Release Notes

When loading a job saved using 5.2.3 or earlier firmware on an In-Sight 2000 series vision sensor, the maximum Light Intensity will increase for some ranges of Exposure settings, resulting in a brighter image:

• 640x480 resolution: Exposures of 3.5ms - 8.2ms
• 640x480 resolution, Image Magnification Mode: Exposures of 1.8ms - 4.9ms
• 800x600 resolution, Image Magnification Mode: Exposure of 2.2ms - 5.1ms

When using Manual Exposure with an In-Sight 2000 series monochrome vision sensor, the image that is acquired for any Exposure value will be slightly brighter than with previous firmware versions. For applications that are highly sensitive to changes in image brightness, you may need to reduce the Exposure value in the Set Up Image step by up to 0.180 ms in order to match the image brightness achieved with a previous firmware version.

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.

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.

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.

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.