© Copyright 1999-2020 Cognex Corporation. All rights reserved.
Revision: 5.8.0.1, 2020 April 23
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 5.9.0 software contains two 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. Optionally, Microsoft .NET Framework 3.5 SP1 can be installed. If the In-Sight software installer fails to detect Microsoft .NET Framework 4.5.2, it attempts to download and install it.
| New Feature |
|---|
| Supports the new In-Sight 8505P vision system. |
| The Web HMI application now supports the Custom View, which allows you to make simple adjustments to the job configuration directly in the Web HMI application. |
| The Web HMI application now supports dialog and wizard cell types. |
Notes:
| Issue# | Change/Fix | Applicable Firmware Version |
|---|---|---|
| IS-2267 | Improved the usability of the HDR mode. The HDR settings can now be modified when an In-Sight vision system is Online. | 5.9.0 |
| IS-2817 | If logged onto an In-Sight Emulator and loading a job with a ReadIDMax function that has the Max Results parameter set to 0, the job now returns an error and no longer crashes the In-Sight Emulator. | 5.9.0 |
| IS-3507 | Fixed an issue where the BeadInspect function could break the link to the BeadFind reference, and sometimes cause the BeadInspect cell to be deleted after retraining the bead path. | 5.9.0 |
| IS-3572 | Fixed an issue where the In-Sight Explorer might become unresponsive for a long period of time when loading a job on an In-Sight 2000 series vision sensor or emulator. | 5.9.0 |
| Issue# | Issue | Affected Firmware Version |
|---|---|---|
| IS-2200 |
If using the Web HMI or FTP, the PROFINET connection between the PLC and the vision system may disconnect when using a 100 Mbps network. Workaround: Use a 1000 Mbps switch/network or increase the PROFINET Update Time to 16ms or higher within the PLC software. |
5.7.x and higher |
|
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). Workaround: Use the LoadJob method to reload the job file to the vision system/sensor. For more information, see the In-Sight® Explorer Help file. |
5.9.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. | 5.9.0 |
| IS-334 |
When you try to connect your vision system/sensor to the Web HMI for the first time, you may receive an error message: Permission error appears and connection is denied. Workaround: Reinstall or update the firmware on the vision system/sensor and then retry the Web HMI connection. |
5.9.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. | 5.9.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. | 5.9.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. | 5.9.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 |