In-Sight® Display Control 6.1.1 Release Notes

Revision: 6.5.1.8, 2024 October 14

Overview

This document describes the In-Sight Display Control for Microsoft^® Windows^®, including the following topics:

About the In-Sight Display Control
System Requirements
Installation
Sample Projects
API Changes
Known Issues

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

About The In-Sight Display Control

The In-Sight Display Control (CvsInSightDisplay) forms the heart of the Job View window in In-Sight Explorer and provides a display of images, graphics and spreadsheet data when connected to an In-Sight vision system. This control is packaged as a .NET control that can be inserted into a Microsoft Visual Studio C# .NET or VB.NET Windows Forms application.

Note: The In-Sight Micro 1020, In-Sight 2000 series and In-Sight 7020, 7010, 7230, 7430 and 7432 are not supported with the In-Sight Display Control.

System Requirements

This section describes system requirements for the In-Sight Display Control 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 In-Sight Display Control may function on other operating systems, systems not meeting the preceding requirements have not been tested and are not supported.

Supported Languages

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

Firmware Version Support

In-Sight 6.5.1 software contains three firmware versions:

In-Sight 6.5.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.5.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)

Note: The In-Sight Micro 1020, In-Sight 2000 series and In-Sight 7020, 7010, 7230, 7430 and 7432 are not supported with the In-Sight Display Control.

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.

Supported Development Environments

Microsoft Visual Studio 2013
Microsoft Visual Studio 2015

Installation

The In-Sight Display Control is installed with the In-Sight Software and In-Sight SDK installers, and you must be logged on as a user with full administrative privileges to install the software.

Sample Projects

In-Sight Display Control Sample Projects are installed to the following folder: C:\Users\Public\Documents\Cognex\In-Sight\In-Sight Sample Projects 6.5.1. A shortcut on the Microsoft Windows Start menu is available to open this location.

API Changes

Refer to the In-Sight Display Control help file for a complete list of enhancements and other API changes in this release of the In-Sight Display Control.

Known Issues

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

Issue#	Issue
5319	When a PairDistance function is added to an Abs formula, as in either of the following examples, "Abs(B2)+PairDistance(C2,0,1)" or "PairDistance(C2,0,1)+Abs(B2)", the expression may cause the Property Sheet to open incorrectly. Workaround: The PairDistance function should be placed in its own cell and referenced by the other expression.
5230	If you add an OPC Tag from an In-Sight Display Control, the corresponding OPC Tag inside the In-Sight OPC Server must use the exact same upper and lower case characters. If the two names do not match exactly, a Configuration Error will result in the OPC Server.
5093	The Open and Save File dialogs (such as CTRL+O), when invoked from the In-Sight Display Control in a custom .NET environment, differ in behavior from the Open/Save File dialogs launched from In-Sight Explorer. Under the list of "In-Sight Sensors," In-Sight Explorer will list all In-Sight vision systems on the local subnet and any Explorer Host Table entries. When launched from an In-Sight Display control in a .NET environment, however, these same dialogs will show the list of all systems on the local subnet and In-Sight Host Table entries stored on the vision system to which the display is connected.

Issue#

Issue

5319

When a PairDistance function is added to an Abs formula, as in either of the following examples, "Abs(B2)+PairDistance(C2,0,1)" or "PairDistance(C2,0,1)+Abs(B2)", the expression may cause the Property Sheet to open incorrectly.

Workaround: The PairDistance function should be placed in its own cell and referenced by the other expression.

5230

If you add an OPC Tag from an In-Sight Display Control, the corresponding OPC Tag inside the In-Sight OPC Server must use the exact same upper and lower case characters. If the two names do not match exactly, a Configuration Error will result in the OPC Server.

5093

The Open and Save File dialogs (such as CTRL+O), when invoked from the In-Sight Display Control in a custom .NET environment, differ in behavior from the Open/Save File dialogs launched from In-Sight Explorer. Under the list of "In-Sight Sensors," In-Sight Explorer will list all In-Sight vision systems on the local subnet and any Explorer Host Table entries. When launched from an In-Sight Display control in a .NET environment, however, these same dialogs will show the list of all systems on the local subnet and In-Sight Host Table entries stored on the vision system to which the display is connected.