© Copyright 1999-2022 Cognex Corporation. All rights reserved.
Revision: 6.4.0.7, 2022 August 22
This document describes the In‑Sight Explorer software, including the following topics:
This section describes system requirements for In‑Sight Explorer software.
Notes:
| 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 |
In-Sight software has been tested on the following operating systems:
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.
In-Sight 6.4.0 software contains three firmware versions:
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 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 |
|---|
|
Added functionality to support Vision Guided Robotics (VGR) applications. The following spreadsheet functions have been introduced:
The In-Sight Explorer package now also contains VGR snippets and sample jobs. For more information, see the Function Reference > Robotics Functions and How to... > Work with Robots sections of the In-Sight Explorer Help document. |
|
The following functions are obsolete and no longer supported, even in legacy jobs:
|
Notes:
| Issue# | Change/Fix | Applicable Firmware Version |
|---|---|---|
| IS-5366 | Fix saving SVG files in IS-9902L to have the correct Width and Height values. |
6.4.0 |
| IS-5663 | Graphics plot not seen when using WriteImageFTP with default font size. |
6.4.0 |
| IS-5255 | SNTP does not always choose the preferred or alternate SNTP server correctly. |
6.4.0 |
| IS-5622 | Enhancement allowing webHMI to access specific cell results without needing to subscribe to all of them. |
6.4.0 |
| IS-5608 | Increase default result buffer size for In-Sight vision systems with larger imagers to improve filmstrip performance. |
6.4.0 |
| IS-5657 | Setting a job timeout can occasionally cause a fatal camera error. |
6.4.0 |
| IS-1915 | Allow saving job with a "." in its name via native mode for the IS2000 and 8000 series cameras. |
6.4.0 |
| IS-5242 | 9902L was incorrectly reporting the encoder and line counts. |
6.4.0 |
| IS-5599 | Fix the CalibrateGrid audit message so it is sent properly. |
6.4.0 |
| IS-5599 | Added audit messages containing the checksum of the trained model for TrainMatchColor, TrainExtract Color, and TrainFlawModel. | 6.4.0 |
| IS-5599 | Added an audit message containing the checksum of the Script tool. | 6.4.0 |
| IS-5952 | EditCompositeRegion now sends detailed audit messages for each changed subregion. |
6.4.0 |
| IS-5732 |
Freezing filmstrip caused delay in In-Sight processing. |
6.4.0 |
| IS-5395 |
DetectBlobs can return an image that can be used by other tools. |
6.4.0 |
| IS-5825 |
The ExtractBlobs and DetectBlobs functions could occasionally find blobs outside of the specified Annulus region. |
6.4.0 |
| IS-5401 |
Fix for HistMean to compute HSI distance correctly. |
6.4.0 |
| IS-6027 | ISDK Display: Camera image was incorrectly cropped in certain cases. | N/A |
| 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.4.0 |
| 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.4.0 |
| 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:
Workaround:
|
6.4.0 |
| 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.4.0 |
|
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.
|
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.4.0 |
| 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.4.0 |
| 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. Workaround: Reinstall or update the firmware on the vision system/sensor and then retry the Web HMI connection. |
6.4.0 |
| 48478 | If an In‑Sight vision system that runs firmware 5.6.0 or later has a job with many instances of the ReadIDMax function, the job might require more memory than is available on the vision system. Any instances of the ReadIDMax function that exceed the available memory returns #ERR. For example, if an In‑Sight 8405 vision system job contains more than 100 instances of the ReadIDMax function, you might encounter this problem. | 6.4.0 |
| 45581 | For In‑Sight 7000 Gen2 series and 9000 series vision systems configured for CIP‑Sync/PTP, 1588 synchronization accuracy through a transparent clock‑switch might increase to more than 10µs offset from master. | 6.4.0 |
| 35828 |
If an industrial Ethernet communication protocol triggers the vision system, the JobPass signal is sent only if the job contains a WriteResultsBuffer function. This issue does not occur with EasyBuilder applications once the Communication application step has been configured. |
6.4.0 |
| 32479 |
If you update the In‑Sight vision system firmware while it is connected to a POWERLINK network, it results 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 you update the vision system firmware, complete the following steps:
|
4.10.5 PR1 |