In-Sight® Explorer 6.2.1 Release Notes

Revision: 6.2.1.27, 2021 October 04

Overview

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

System Requirements
New Features
Changes & Fixes
Known Issues

Note: For the latest release notes and documentation, visit: support.cognex.com/documentation/in-sight.

System Requirements

This section describes system requirements for In‑Sight Explorer software.

PC Hardware Minimum and Recommended Requirements

Notes:

The following minimum hardware requirements are for PCs that are connected to a single low-resolution In-Sight vision system running at a slow production speed.
The following recommended hardware requirements are for PCs that are simultaneously connected to up to four In-Sight vision systems.

Minimum	Recommended
Intel^® Celeron^® 1000M processor running at 1.8GHz (or equivalent)	Intel Core™ i7 processor running at 2.7GHz (or equivalent)
2GB of available RAM	4GB of available RAM
4GB of available disk space	8GB of available disk space
Video card that can display 1024 x 768 resolution at 24-bit color depth (the DPI Display setting must be set to 96 DPI)	Video card that can display 1920 x 1080 resolution at 32-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	Gigabit network interface card for connecting to multiple 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 Server 2016

Although you can install and run In‑Sight Explorer on other Windows operating systems, PCs that do not meet the preceding requirements are not officially supported.

Supported Languages

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

Firmware Version Support

In-Sight 6.2.1 software contains three firmware versions:

In-Sight 6.2.1
In-Sight 5.9.2
In-Sight 4.10.5 PR1

In-Sight vision systems that have older firmware versions might work properly. However, some features are unsupported with older firmware versions and are not fully tested. For optimal performance, update vision systems that run older firmware to the most recent, supported firmware versions. For a list of models and supported firmware versions, see the Firmware Versions topic in the In-Sight^® Explorer Help file.

In-Sight Firmware 6.2.1

In-Sight 2000 series vision sensors
In-Sight 7000 Gen2 series vision systems
In-Sight 8000 series vision systems
In-Sight 9000 series vision systems
In-Sight Advantage Engine

In-Sight Firmware 5.9.2

In-Sight 5705 and 5705C vision systems

In-Sight Firmware 4.10.5 PR1

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 7000 Gen2 series vision systems)

Microsoft .NET Framework 4.5.2

In-Sight software requires Microsoft .NET Framework 4.5.2. If the In-Sight software installer fails to detect Microsoft .NET Framework 4.5.2, it attempts to download and install it.

New Features


Introducing Cognex Network Server 3.0.0, a desktop and web application that supports single-sign-on, built-in audit message server, managing users across all devices, and creating and managing trusted certificates required to establish an HTTPS connection between In-Sight devices and the Web HMI.
Introducing Compare Jobs, allowing you to see a list of cell differences between two .job files. Accessible from the System menu and file pane of the In-Sight Explorer, and through and API & sample project in the ISDK..
New Job Timeout spreadsheet functions allow for advanced-level control of the job’s execution duration.

Changes & Fixes

Notes:

For changes and fixes in previous releases, see past In‑Sight Explorer release notes. Release notes for previous releases are available in the In‑Sight Explorer^® Help file.
The release notes include issue numbers (where applicable) to better track known issues reported by Cognex Technical Support.

Issue#	Change/Fix	Applicable Firmware Version
IS‑5418	Fixed issue where the PLC Time Synchronization details screen was not working correctly for certain In-Sight Explorer languages.	6.2.1
IS‑5403	Fixed inability of In-Sight to maintain or recover an FTP connection if a separate FTP operation is performed. This can impact or be caused by WriteImageFTP, WriteFTP, Import/ExportData, or file operations. Affects 6.1.1 - 6.1.3 firmware on all models.	6.2.1
IS‑5368	Improved OCRMax read scoring for dash and other small punctuation characters.	6.2.1
IS‑5365	Fixed rare combinations of exposure duration and image row settings that corrupted the acquired image. Affected AdvantageEngine and In-Sight 200X models only.	6.2.1
IS‑5337	Fixed 'CjsDialogView' error that prevented use of secure Web HMI in certain cases.	6.2.1
IS‑5202	Improved speed of the ExtractHistogram when using a small input region.	6.2.1
IS‑5201	Fixed an issue where the first FTP transfer attempt by the camera failed after bringing the camera online. Affects only v6.1.1 - v6.1.3 firmware.	6.2.1
IS‑5166	Fixed issue where not all DLL signatures appeared in the SDK.	6.2.1
IS‑5096	Reverted changes to audited values will now cause audit messages to be sent after canceling a dialog.	6.2.1
IS‑5040	Fixed issue where Operator (protected) level users were not able to modify settings of EasyBuilder tools.	6.2.1
IS‑4947	Fixed issue when on job load, Color Pixel Count tool could cause Communications device to disappear, if the tool was dependent on comms input.	6.2.1
IS‑4842	Fixed an issue where set PortNum did not work correctly. Affects v6.1.0 - 6.1.3 firmware	6.2.1
IS-4785	Fixed a slowdown in the ReadIDMax function in cases where the code orientation was rotated 90 degrees relative to the orientation of the search region.	6.2.1
IS-4785	The max search ROI of the ReadIDMax function is extended to 2592 x 2592 for code types that previously supported a max region size of 2592 x 2048.	6.2.1
IS‑4455	Fixed error in the Web HMI occurring when you modify the camera's acquisition start row and the number of rows.	6.2.1
IS-383	Previously, there was an issue with UDP connection: sometimes the UDP WriteDevice did not reestablish connection after a disconnect.	6.2.1

Known Issues

Note: The release notes include issue numbers (where applicable) to better track known issues reported by Cognex Technical Support.

Issue#	Issue	Affected Firmware Version
IS‑5258	Web HMI: 403 error seen in browser after successfully firmware updating certain IS2000 devices. Workaround: performing a 2nd firmware upgrade.	6.2.1
IS‑4432	If the ReadIDMax function is configured to read Data Matrix symbols, the Enable Training option is checked, and Train Perspective is selected from the Perspective drop-down, subsequent attempts to read the symbol will fail.	6.2.1
IS‑2854	After a power-cycle, if the vision system/sensor receives a new trigger, no new results are added to the Sensor Filmstrip queue. However, the image and spreadsheet continue to update correctly. Conditions: An In-Sight vision system/sensor is configured to use the Sensor Filmstrip. In the Sensor Filmstrip Settings dialog, the Queue drop-down is configured as Separate Pass and Fail Results. In the Sensor Filmstrip Settings dialog, the Queue Size is increased or decreased. The vision system/sensor is power-cycled. After the power-cycle, the vision system receives a new trigger. Workaround: Within In-Sight Explorer, click Sensor menu > Sensor Filmstrip Settings to launch the Sensor Filmstrip Settings dialog. From the Queue drop-down, select an option other than Separate Pass and Fail Results and click OK. Relaunch the Sensor Filmstrip Settings dialog. From the Queue drop-down, select Separate Pass and Fail Results and click OK. When the vision system/sensor is triggered, results are correctly added to the queue.	6.2.1
FFP‑1646	In-Sight 2000 series vision sensors running In-Sight firmware version 5.9.1 and later are not certified for PROFINET Conformance. To run In-Sight 2000 series vision sensors with PROFINET Conformance, you can downgrade the In-Sight 2000 series vision sensors' firmware version to In-Sight 5.9.0 or 5.8.x.	5.9.1 & 6.2.1
IS‑2195	If In-Sight Explorer is installed to a PC with a Microsoft Windows 10 operating system and the Beta: Use Unicode UTF-8 for worldwide language support is checked in the Region dialog, the vision system or emulator may not be able to connect to the In-Sight Explorer Spreadsheet View. Workaround: Uncheck the Beta: Use Unicode UTF-8 for worldwide language support checkbox. In the search box on the Windows taskbar, type Control Pane and select the Control Panel App. From the Windows Control Panel search box, type Region and select the Region text. In the Region dialog that opens, click the Administration tab and click the Change system locale... button. In the Region Settings dialog that opens, uncheck Beta: Use Unicode UTF-8 for worldwide language support and click OK to close the Region Settings dialog. Click OK to close the Region dialog. Reboot the PC.	N/A
FFP‑1053	When the vision system is configured to load a job at startup (Sensor menu > Startup) and the EV SetSystemConfig OPCUA.TimeSync Extended Native Mode command is issued, OPC UA Job Tags are missing in the OPC UA client when browsing the address space (Objects > Server > VisionSystem > Results > JobTags node).	6.2.1
FFP‑875	Sending the communication settings, such as the IP address, from Mitsubishi iQ Sensor Solution (GX Works) to the In-Sight vision system/sensor is not supported.	6.2.1
IS‑334	When you try to connect your vision system/sensor to the Web HMI for the first time, you may receive a permission error and connection is denied.