Discrete I/O Functions

Discrete I/O functions read and write an In-Sight vision system's parallel discrete I/O channels.

ReadDiscrete: Reads a range of bits from a discrete input channel.
WriteDiscrete: Writes a range of bits to a discrete output channel.

The number of direct (built-in) inputs and outputs varies per In-Sight vision system, as follows. For more information, see Default Input and Output Lines.

In-Sight Vision Systems	Direct (built-in) Inputs	Direct (built-in) Outputs
In-Sight Micro 1000 series	None	2 high-speed outputs 2 user-configurable LEDs (1 green, 1 red)
In-Sight 5000 series	None	2 high-speed outputs 2 user-configurable LEDs (1 green, 1 red)
In-Sight 70xx - 74xx series	3 general-purpose inputs	4 high-speed outputs 2 user-configurable LEDs (1 green, 1 red)
In-Sight 7000 Gen2 series	Up to 3 general-purpose inputs	Up to 4 high-speed outputs 2 user-configurable LEDs (1 green or red, 1 red)
In-Sight 8000 series	None	2 high-speed outputs 2 user-configurable LEDs (1 green, 1 red)
In-Sight 9902L	1 general-purpose input	2 high-speed outputs 2 user-configurable LEDs (1 green or red, 1 red)
In-Sight 9912	Up to 3 general-purpose inputs	Up to 4 high-speed outputs 2 user-configurable LEDs (1 green or red, 1 red)

Note:

In-Sight vision systems have one dedicated acquisition trigger input on the vision system. For more information, refer to the vision system installation manual or reference guide, included with In-Sight Explorer software.
When connected to the Breakout cable, the In-Sight 7000 Gen2 series and 9912 vision systems support bi-directional high-speed outputs and general-purpose inputs for HS OUT 2 / IN 2 and HS OUT 3 / IN 3. These lines are configured as outputs by default.

An I/O module can be used to provide additional discrete inputs and outputs. The number of discrete inputs and outputs varies per applicable I/O module, as follows. For more information, see Default Input and Output Lines.

I/O Modules	Supported In-Sight Vision Systems	Discrete Input Lines	Discrete Output Lines
CIO-1400	In-Sight 5000 series (except 5604), In-Sight 7000 Gen2 series, In-Sight 9000 series	7 general-purpose inputs	6 general-purpose outputs
CIO-MICRO	In-Sight Micro 1000 series, In-Sight 5000 series, In-Sight 70xx - 79xx series, In-Sight 8000 series, In-Sight 9000 series	8 general-purpose inputs	8 general-purpose outputs
CIO-MICRO-CC	In-Sight Micro 1000 series, In-Sight 5000 series (except 5705, 5705C and 5715), In-Sight 70xx - 74xx series	8 general-purpose inputs	8 general-purpose outputs
CIO-1450	In-Sight 5000 series (except 5604, 5705, 5705C and 5715)	8 general-purpose inputs	8 general-purpose outputs
CIO-1460	In-Sight 5000 series (except 5604, 5605, 5705, 5705C and 5715)	8 general-purpose inputs	8 general-purpose outputs
CIO-WENET	In-Sight Micro 1000 series	8 general-purpose inputs	8 general-purpose outputs

Note:

The CIO-1400 I/O module supports the In-Sight 7000 Gen2 series vision system using In-Sight Explorer 5.4.0 and higher. If you log onto the vision system using an earlier version of In-Sight Explorer, connect to the CIO-1400 I/O module and configure the I/O lines, the changes will not be retained.
The CIO-MICRO I/O module supports In-Sight 5705, 5705C, 5715 and In-Sight 8000 series vision systems with firmware version 5.3.0 and higher.
The CIO-MICRO & CIO-MICRO-CC I/O modules support In-Sight 5100 series and 5400 series vision systems with 128MB non-volatile flash memory or higher. Models can be identified by the Type number (821-xxxx-xx). The Type number is located on the label affixed to the vision system. For a complete list of models and supported firmware versions, see Firmware Versions.
The CIO-1450, CIO-1460 and CIO-WENET I/O modules are obsolete and no longer available for purchase, however these modules are still supported within In-Sight Explorer for backward compatibility only.
In-Sight vision systems may also be used to communicate with standard Ethernet I/O solutions available from other vendors, including Opto 22, Wago, and Sixnet, to provide a virtually unlimited number of I/O channels. However, the In-Sight TCPDevice function, configured for Modbus packet type communications, must be used to configure Ethernet-based I/O on these vision systems. For more information, see TCPDevice.
In job deployment environments where In-Sight Explorer or the VisionView application are monitoring inspections, if the job depends on a Soft Event (e.g., configured as a Timer function) to trigger a spreadsheet event, it may cause the inspection of an image to be delayed if it is triggered shortly before the acquisition cycle completes. If the job file is large (i.e., it contains many Vision Tools, such as Pattern Match, Flaw Detection or InspectEdge tools, in addition to other job logic), the update required by In-Sight Explorer or VisionView may prevent an image from being inspected until the display update is queued. For applications that require exact timing (e.g., measured in the 10s of milliseconds), this update might delay the determination of pass/fail results and the transmission of results to the next station (e.g., a PLC or motion controller) in the inspection process. To avoid delayed inspections in these application environments, Cognex recommends Soft Events not be used.