Objectives

At the end of this section Participants will be able to:

Network Communications
Section 7
- Describe the use of communications within EasyBuilder
- Configure the FTP communications settings
- Utilize the In-Sight Emulator as an Authorized FTP Directory

Section 7 | Slide 2

The seventh section of the In-Sight EasyBuilder Standard training will focus on At the end of this section, Participants will be able to:
Communications.
- Describe the use of communications within EasyBuilder
The Communication step is used to define inspection results for open data access - Configure the FTP communications settings
and exchange (OPC), to configure an EasyView for the VisionView™ Operator - Utilize the In-Sight Emulator as an Authorized FTP Directory
Interface Panel, exporting images via FTP or to the SD card, and to define the
network and serial communication settings of In-Sight Vision Systems, enabling them
to communicate data to and from other devices, such as a robot or a Programmable
Logic Controller (PLC) / Motion Controller (MC).

Section 7 | Slide 1 Section 7 | Slide 2

 Communications FTP

Excel or other
3rd Party Applications

Robots

PLCs

HMIs

Section 7 | Slide 3 Section 7 | Slide 4

The Communication step is used to define inspection results for open data access In-Sight vision systems have an integrated FTP client/server that allows them to
and exchange (OPC), to configure an EasyView for the VisionView® Operator share files with other vision systems on the network using the FTP protocol. The
Interface Panel, exporting images via FTP, and to define the network and serial Save and Open dialogs act as FTP clients and can establish connections with FTP
communication settings of In-Sight vision systems, enabling them to communicate servers on the network to transfer job, image and firmware update files.
data to and from other devices, such as a robot or Programmable Logic Controller
(PLC) / Motion Controller (MC). From the Communication Application Step select FTP from the Communications
window.
NOTE: The In-Sight camera must be Offline to enable the Communication step. The FTP window displays.
The In-Sight 8405 vision system does not support serial communication or
connection to an I/O module.

Section 7 | Slide 3 Section 7 | Slide 4

 FTP Settings Dialog WriteImageFTP

Section 7 | Slide 5 Section 7 | Slide 6

The FTP Settings Dialog configures an In-Sight sensor to share jobs, images and On the Image tab, click the Add button.
settings with other network devices that use the File Transfer Protocol. Users typically The WriteImageFTP tool displays.
do not need to modify the default settings on dedicated, local In-Sight sensors where
all FTP connections will occur between In-Sight sensors and other network servers, The tool parameters will display to the right of the Image tab.
or between In-Sight sensors on different networks, then the default FTP settings may Transfer Condition defines when the data should be sent to the FTP server, for
need to be changed. example, when a particular tool passes or fails, or an input is received. By default,
none is selected, which ensures that the data will be exported every time an image is
To display the FTP Settings dialog, select FTP Settings from the Sensor menu. acquired when the Enabled checkbox is checked. If the Enabled checkbox is
disabled, or the tool referenced is disabled, the export operation will not execute.
File Format defines the file format of the exported image: BMP (Windows bitmap
format) or JPG (standard encoded JPEG format). By default, BMP is selected.
Default File Name defines the name of the image format that is exported, the default
name is Image. Enter the Authorized FTP directory followed by a \ before the Image if
using In-Sight Explorer as your FTP directory.

Section 7 | Slide 5 Section 7 | Slide 6

 WriteFTP FTP

Section 7 | Slide 7 Section 7 | Slide 8

On the File tab, click the Add button. The Settings tab is where you will configure the In-Sight Emulator as the target
The WriteFTP tool displays. device.

The tool parameters will display to the right of the File tab. Host Name defines the host name (or IP Address) for the target device’s FTP server.
Transfer Condition defines when the data should be sent to the FTP server, for User Name defines the valid user name for the target device’s FTP server. This
example, when a particular tool passes or fails, or an input is received. By default, name does not have to exist on the In-Sight vision system that is exporting the image
none is selected, which ensures that the data will be exported every time an image is file or data.
acquired when the Enabled checkbox is checked. If the Enabled checkbox is Password defines the valid password for the target device’s FTP server. The
disabled, or the tool referenced is disabled, the export operation will not execute. password is case-sensitive, and its length cannot exceed 20 characters.
File Contents: Format String defines the data written to the file using the
FormatString dialog. Since we will be using the In-Sight Emulator as the target device, the user name is
Default File Name defines the name of the image format that is exported, the default admin, and the password is left blank.
name is File. Enter the Authorized FTP directory followed by a \ before the File if
using In-Sight Explorer as your FTP directory.

Section 7 | Slide 7 Section 7 | Slide 8

 FTP

Communicating with PLCs

Section 7 | Slide 9 Section 7 | Slide 10

Go Online, trigger the camera a few times to capture images. This section gives an overview of how an In-Sight can send or receive values with a
Go Offline and check the FTP folder. PLC in EasyBuilder Mode. It assumes familiarity with the PLC end of the
communications.
There will be BMP files for each image captured in the folder.

Section 7 | Slide 9 Section 7 | Slide 10

 Implicit vs Explicit Messaging Example Results/Output Assembly

Sent from Camera to PLC

Implicit Message Explicit Messaging
• Factory Floor Protocol • Native Mode Commands
• Automatic • Only sent/reply when
Send/Receive/Reply told Pre-Determined
• Prebuilt Functions • Must send each
command

Formatted using FormatOutputBuffer and WriteResultsBuffer

Section 7 | Slide 11 Section 7 | Slide 12

There are two kinds of messaging between In-Sight and the PLC: Implicit and With Implicit Messaging, you also need to set up the Assembly Objects on the PLC.
Explicit.
Assembly Objects represent the structure of the packet sent between the PLC and
Implicit Messaging is when a server sends information from predefined memory the Camera. Each bit, or group of bits, is labeled according to its function and
locations to a client at a given interval. For PLCs, this given interval is the RPI cycle position in the packet.
time. Implicit Messaging uses UDP and is faster than Explicit Messaging and is thus
intended for time-critical applications. When doing There are always two Assembly Objects: (1) one for sending from the
camera to the PLC (Input Assembly) , and (2) one for sending from the PLC to the
camera (Output Assembly) . Each Industrial Protocol has its own packet description,
but many of the Assembly Objects tend to have the same bits with very similar
functionality.

Assembly Objects come in handy when you are unable to use the Add-On Profile
(AOP) or Copy Rung Instruction. If you are not using the AOP, even if you are using
the EDS (Electronic Data Sheet) file, your bits will not be labeled; all you will have is
a large space in memory filled with bits. Using the position of the bit on this map, it is
possible to determine functionality without having them labeled. This can also come
in handy for troubleshooting, specially if the memory space on the PLC is not
properly aligned with the bits.

Formats vary with the version of In-Sight. Complete formats and explanations are
found in the In-Sight Explorer Help menu under:
“EtherNet/IP Object Model - In-Sight 4.x.x Firmware”
“EtherNet/IP Object Model - In-Sight 5.x.x Firmware”

Section 7 | Slide 11 Section 7 | Slide 12

 Example Control/Input Assembly Rockwell ControlLogix: Communication

From PLC to Camera

Pre-Determined

Read using FormatInputBuffers and WriteUserDataBuffer

Section 7 | Slide 13 Section 7 | Slide 14

With Implicit Messaging, you also need to set up the Assembly Objects on the PLC. To send or receive values with a PLC, go to the Communication step in EasyBuilder.
Navigate through the pull-down menus until to get to PLC/Motion Controller –
Assembly Objects represent the structure of the packet sent between the PLC and Rockwell Automation – Ethernet/IP. Then click the OK button.
the Camera. Each bit, or group of bits, is labeled according to its function and
position in the packet.

When doing There are always two Assembly Objects: (1) one for sending from the
camera to the PLC (Input Assembly) , and (2) one for sending from the PLC to the
camera (Output Assembly) . Each Industrial Protocol has its own packet description,
but many of the Assembly Objects tend to have the same bits with very similar
functionality.

Assembly Objects come in handy when you are unable to use the Add-On Profile
(AOP) or Copy Rung Instruction. If you are not using the AOP, even if you are using
the EDS (Electronic Data Sheet) file, your bits will not be labeled; all you will have is
a large space in memory filled with bits. Using the position of the bit on this map, it is
possible to determine functionality without having them labeled. This can also come
in handy for troubleshooting, specially if the memory space on the PLC is not
properly aligned with the bits.

Formats vary with the version of In-Sight. Complete formats and explanations are
found in the In-Sight Explorer Help menu under:
“EtherNet/IP Object Model - In-Sight 4.x.x Firmware”
“EtherNet/IP Object Model - In-Sight 5.x.x Firmware”

Section 7 | Slide 13 Section 7 | Slide 14

 Rockwell ControlLogix: Communication Rockwell ControlLogix: Communication

Section 7 | Slide 15 Section 7 | Slide 16

You will see at the bottom of the EasyBuilder window two tabs: Format Input Data In this slide, we are showing two variables that have been selected to be output: the
and Format Output Data. Each allows you to select parameters from the vision Brightness value from a tool named “Connector” and the String read by an IDCode
tools in your job. tool. Default data types of 32 bit float and string are shown, buy these can be
changed by using the Data Type pull-down menu. At the very right, the actual data
that will be sent to the PLC is displayed.

Section 7 | Slide 15 Section 7 | Slide 16

 Explicit Messaging Rockwell ControlLogix: Help Topics

• Better suited for operations that occur less frequently

• No need for Factory Floor Protocols
• PLC issues MSG instructions to In-Sight, usually Native
Mode commands, via telnet protocol

Example: change job on camera

Get Data from an In-Sight Vision System
Controller Tags
Send Data to an In-Sight Vision System
EtherNet/IP PLC Setup
Install the EDS Files
Industrial Communication Overview
EtherNet/IP I/O Assembly Data Format Assemblies

Section 7 | Slide 17 Section 7 | Slide 18

Unlike Implicit Messaging, there is no RPI. Usually, the PLC sends an MSG to In- Use the In-Sight Explorer Help file to answer your Rockwell PLC questions. Above
Sight Explicit, set up for a Native Mode command. are a few topics to get you started.

Section 7 | Slide 17 Section 7 | Slide 18

 Other PLCs: Help Topics Quick Setup of Communications

PROFINET PLC Setup

Configuring the PLC Hardware
Setting up the Siemens S7 PLC
Triggering the Camera from the PLC
Reading Data from the PLC
Writing Data to the PLC

Section 7 | Slide 19 Section 7 | Slide 20

Use the In-Sight Explorer Help file to answer your PLC questions. Above are a few Select a communication type to either configure OPC tags to the In-Sight OPC
topics to get you started. Server or an EasyView for the VisionView Operator Interface Panel.

Or, click the Add Device button to configure communications to an external device.

Section 7 | Slide 19 Section 7 | Slide 20

 Adding a Device Adding a Device

Section 7 | Slide 21 Section 7 | Slide 22

Choose a communication protocol by selecting a Device, Manufacturer (if applicable), An In-Sight camera can be configured to act as a TCP/IP client device, TCP/IP is a
and Protocol. When selecting, the drop-down lists are contingent upon what is standard Ethernet protocol (Transmission Control Protocol / Internet Protocol)
selected in the list above. If you do not see your desired selections, set Device to opening a connection between the In-Sight camera and another TCP/IP device for
Other and Manufacturer to Other to enable all of the Protocol selections. Click OK to sharing data over the network.
confirm. Once the TCP/IP connection has been established, EasyBuilder will initiate the
communication with another TCP/IP device on the network.
Device Settings:

- None – Disables communication via Ethernet and Serial. NOTE: Selecting Other allows for custom configuration of communications settings.
- PLC / Motion Controller – Prepares communications protocol settings for
PLCs. To configure an In-Sight camera for client device TCP/IP service:
- Robot – Prepares communications protocol settings for robots.
- Other – Allows custom communications configurations. 1. In the Communications group box, press the Add Device button.
2. From the Device Setup group box, select Other from the Device drop-down list.
3. Select TCP/IP from the Protocol drop-down box.
4. Press the OK button.

Section 7 | Slide 21 Section 7 | Slide 22

 Example – Adding TCP/IP Selecting Values

Section 7 | Slide 23 Section 7 | Slide 24

5. Click the TCP/IP Settings tab and enter the name of the TCP/IP service device 9. Once the TCP/IP settings have been established, click the Format Output String
with which to establish connection in the Server host Name field. tab to select and format the data that will be transmitted.
6. Enter the Port Number of the TCP/IP server at which the connection will be 10. Click the Format String button, which will launch the FormatString dialog where
established between TCP/IP devices in the Port field. The Port number entered you will be able to add, customize and modify the order of the data sent.
must also be assigned on the server.

NOTE: A valid Port assignment is any unused number between 1 and 65,535, except
for ports used for In-Sight communications. In-Sight Emulator users should always
assign Port numbers 3000 (the default) and higher to prevent conflicts with ports
reserved by services on the PC.

7. Enter the milliseconds (100 to 15,000; default = 1000) to wait for the TCP/IP
connection to be established before aborting the connection in the Timeout field.
8. From the Terminator drop-down list, select a String with Customer Terminator to
specify an ASCII character (0 to 255).

NOTE: Can be set to Client (opens port) and Server (listens for data).
If In-Sight is Client, Server Host Name is the IP Address or Name of the device being
connected to. If Server, then the Server Host Name is left blank. The Port and
Terminator need to match on the Client and Server

Section 7 | Slide 23 Section 7 | Slide 24

 FormatString Settings FormatString Settings

Section 7 | Slide 25 Section 7 | Slide 26

11. Within the FormatString dialog, click the Add button, which will launch the Select 13. After you have selected your data in the Select Output Data dialog the
Output Data dialog. FormatString dialog will reappear.
14. You can modify the strings and/or rearrange the order of the data that will be sent
12. The Select Output Data dialogs contain the data from any Location or Inspection
by selecting the data from the list and clicking either the Up or Down buttons to
Tools that were added to your job and the overall job results. From the dialog,
set your desired order. Once you have finalized your string modifications, press
select the appropriate data that you want sent from the In-Sight camera, and
the OK button.
press the OK button.
15. Now that the string has been formatted, the output data will be sent after the
camera completes its job execution.

Section 7 | Slide 25 Section 7 | Slide 26

 Cognex Knowledge Base Summary

• In-Sight is able to communicate with many 3rd party

applications
• An In-Sight Emulator can be utilized as an Authorized
FTP Directory to capture BMP images
• PLC communications may be Implicit or Explicit, and
may require an AOP or EDS file, as well as assembly
objects

Section 7 | Slide 27 Section 7 | Slide 28

Cognex Knowledge Base is another resource available to help you find answers to In this section we covered the following topics:
your Communication related questions.
The site to access the Knowledge Base is help.cognex.com. - In-Sight is able to communicate with many 3rd party applications
- An In-Sight Emulator can be utilized as an Authorized FTP Directory to
capture BMP images
- PLC communications may be Implicit or Explicit, and may require an AOP
or EDS file, as well as assembly objects

Section 7 | Slide 27 Section 7 | Slide 28

 Skills Journal Lab Exercise

Complete:
Section 7
Skills Journal

Section 7 | Slide 29

Complete:
Skills Journal (image designed by pngtree)
Lab Exercise

Section 7 | Slide 29