VISOR®Communications manual
Cop yright (Eng lish)
No part of this document may be reproduced, published, or stored in databases or information
retrieval systems in any form – even in part – nor mayillustrations, drawings, or the layout be
copied without prior written permission from SensoPart Industriesensorik GmbH.
We accept no responsibility for pr inting errors or mistakes which occurred in drafting these
document. Subject to delivery and technical alterations.
First publication 01/2019
SensoPart Industriesensorik GmbH
Nägelseestr. 16
79288 Gottenheim
Page 2 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Table of contents
1 Information on this document 5
1.1 What the symbols mean 5
1.2 Additional documents 6
2 Network connection 7
2.1 Integrating the VISOR® into the network/ gateway 7
2.2 Network connection, procedure / Troubleshooting - Direct connection 8
2.3 Network connection, procedure / Troubleshooting - Network connection 9
2.4 Used Ethernet - Ports 10
2.5 Accessto VISOR® through network 11
2.6 Accessto VISOR® through the Internet / World Wide Web 12
2.7 VISOR® electricalconnection on the network 13
3 VISOR® configuratio n 15
4 Eth ernet TCP/IP, p ort 2005 / 2006 19
4.1 Example: Data output from VISOR® to PC / PLC 19
4.2 Example: Commands (requests) from PC / PLC to VISOR® 24
4.3 Example: Job change from PC / PLC to VISOR® 26
4.4 Example Beckhoff CX 1020 29
4.5 Example Siemens S7 29
5 Service / Visualizatio n 30
5.1 Backup creation 30
5.2 Visualization 30
6 VISOR® telegrams for PROFINET and EtherNet/IP 31
6.1 Module 1: "Control" (from controller to VISOR®) 31
6.2 Module 2: "Status" (from VISOR® to controller) 32
6.3 Module 3: "Data" (from VISOR® to controller) 34
6.4 Module 4: "Request" (from controller to VISOR®) 34
6.5 Module 5: "Response" ( from controller to VISOR®) 35
6.6 Start / end criteria for each telegram 35
7 Timing diagrams fo r VISOR® communication 36
8 Request sequences 42
9 PROFINET 49
9.1 Siemens S7-1200 TIA 12 configuration example 49
9.1.1 Create new project 49
9.1.2 Selecting the GSD file 49
9.1.3 Adding the VISOR® to the project 50
9.1.4 Writing a name to VISOR® 56
9.1.5 Load the project onto the PLC 57
9.1.6 Mappingof output data 57
9.2 PLC example programs 60
06814859 - 1/24/2019-00 Page 3 EN
VISOR®Communications manual
10 EtherNet/IP 64
10.1 Rockwell CompactLogixTM configuration example 64
10.2 Rockwell Studio 5000 configuration example 64
10.2.1 Create new project 64
10.2.2 Select EDS file 66
10.2.3 Load the project onto the PLC 71
10.2.4 Mapping of output data 77
10.3 PLC example programs 79
11 Append ix 81
11.1 Telegram, Data Output tab 81
11.1.1 Overview telegrams 81
11.1.2 T elegrams: Availabilityand supported interfaces 85
11.1.3 Error codes 88
11.1.4 Serialcommunication ASCII 90
11.1.5 Serialcommunication BINARY 189
Page 4 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
1 Information on this document
1.1 What the symbols mean
Warnings
CAUTION / WARNING /
DANGER
This symbol isused to indicate a potentiallyhazardous situation that, if not avoided,
could result in death or serious injury.
WARNING
This symbol isused to indicate potentiallyhazardous situationsarising from laser
beams.
ATT ENTION:
This symbol isused to indicate text that must be observed without fail. Failure to do
so may result in bodily injury or pr operty damage.
NOTE:
This symbol isused to highlight useful tips and recommendations, as well as
information intended to help ensure efficient operation.
Detectors
Pattern matching Data code
Contour comparison OCR
Contrast Color value
Brightness Color list
Grayscale Color area
Caliper
BLOB
Barcode
Align ment
06814859 - 1/24/2019-00 Page 5 EN
VISOR®Communications manual
Alignment
Includes the position detectors: Contour comparison, Pattern matching, and Edge
detection
1.2 Additional documents
The following documents for the VISOR®vision sensor are available for download in the
Download area of the SensoPart website.
l VISOR
l VISOR
l VISOR
l Furthermore, these documentsis part of the VISOR®software installation and can be
®
User manual
®
Communication manual
®
Operating manual
found in the sub directory "\Documentation\" and the Windows Star t,Menu.
Page 6 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
2 Network connection
2.1 Integrating the VISOR®into the network / gateway
SensoFind/Active sensors will show a listwith all the VISOR®vision sensors that are found on the
same network segment on the PC on which SensoFind is running. To update the list, press the
"Find" button for e.g. sensors that were only activated after viewing SensoFind.
For sensors which are installed in the network but are located in a different networksegment via a
gateway, please enter the corresponding sensor IP addr essunder "Add active sensor" and press
the button "Add". T he corresponding sensor willnow also appear in the "Active sensors" list, and
you will be able to accessitand workwith it.
06814859 - 1/24/2019-00 Page 7 EN
VISOR®Communications manual
2.2 Network connection, procedure / Troubleshooting - Direct connection
Establishing a direct Ether net connection between the VISOR®vision sensor and the PC
Fig. 1: Direct connection sensor / PC, procedure / troubleshooting
Page 8 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
2.3 Network connection, procedure / Troubleshooting - Network connection
Establishing an Ethernet connection between the VISOR®vision sensor and the PC through a
network.
Fig. 2: Connection via network sensor / PC, proceeding / troubleshooting
06814859 - 1/24/2019-00 Page 9 EN
VISOR®Communications manual
2.4 Used Ethernet - Ports
If you ar e integrating the VISOR®into a network, make sure that an admin opens the following
ports if necessary. This is only the case if these ports were previouslyexplicitlyblocked in the
company networkor by a firewall installed on the PC.
The following ports ar e used for communications between the VISOR®Software (PC) and the
VISOR®vision sensor:
l Port 2000, TCP
l Port 2001, UDP Broadcast (to find sensors via SensoFind)
l Port 2002, TCP
l Port 2003, TCP
l Port 2004, TCP
he following portsare used for communicationsbetween the PLC ( PLC or control PC) and
VISOR®.
Process interfaces:
l Ethernet
l Port 2005, TCP (Implicit results, i.e. user- configured result data)
l Port 2006, TCP (Explicit requests, e.g. trigger or job switch)
l EtherNet/IP:
l Port 2222, UDP
l Port 44818, TCP
l PROFINET:
l Port 161, UDP
l Port 34962, UDP
l Port 34963, UDP
l Port 34964, UDP
l Service:
l Port 1998
l SensoWeb:
l Port 80
NOTE:
If Ports2005 or 2006 are changed in the configuration softwar e, they must also be
changed accordingly in the firewallbyan administrator.
Page 10 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
2.5 Access to VISOR®through network
Exemplary valuesfor IP, etc.
Access to VISOR®1 from PC 1 if on the same subnet
l Via SensoFind (/find)
Access to VISOR®2 from PC 1 if on a different subnet
Onlyif:
l Gateway is set correctly in Sensor 2 (here to 192.168.30.1) - and
l in SensoFind via Add IP, the sensor IP of Sensor 2 is set correctly
˃ After this, VISOR®2 will also appear in the "Activesensors" list in SensoFind!
06814859 - 1/24/2019-00 Page 11 EN
VISOR®Communications manual
Fig. 3: Accessto VISOR®through networ k, same or other subnet
2.6 Access to VISOR®through the Internet / World Wide Web
Exemplary valuesfor IP, etc.
Access from PC 1 (company network1), through the Word Wide Web, to company network2 to
VISOR®1.
Page 12 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
1. On PC 1 (company network 1) enter and add the IP WAN of Router 2 (company network
2) under "Add active sensor" in SensoFind (here in this example: 62.75.148.101)
2. On router 2, open the ports that the sensor will be using (please refer to section: Used
Ethernet - Ports).
Fig. 4: Accessto VISOR®through the Internet / World Wide Web
2.7 VISOR®electrical connection on the network
The VISOR®vision sensor is connected to the network through a switch.
06814859 - 1/24/2019-00 Page 13 EN
Fig. 5: VISOR®electricalconnection on the network
VISOR®Communications manual
Page 14 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
3 VISOR®configuration
In order to configure the vision sensor, follow the steps below.
Settings in Senso Find
1. Start the VISOR®software . SensoFind
are opened.
2. Clickon the "F ind" button. The vision
sensor will be listed in the "Active
sensors" window.
3. Clickon the "Settings" button. T he
dialog box for configuring the IP address
and the sensor name willappear.
4. Assign an IP addressand a name to the
sensor.
5. Clickon the "Set" button. The IP
address and the name have now been
updated.
06814859 - 1/24/2019-00 Page 15 EN
VISOR®Communications manual
6. Open SensoConfig by selecting the
sensor you want and then clicking on the
"Configure" button.
7. Confirm the following dialog box with
"OK" to stop SensoFind and start the
configuration in SensoConfig.
Page 16 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Select an interface in SensoConfig
1. Use the "Output" setup step to open the
2. Enable the interface by enabling the
3. In the "Setting 3" column, select the
Defin ing telegrams / data output in Sen soConfig
1. Use the "Output" setup step to open the
2. Set the control characters you want for
3. Select the drop-down menus you want.
4. Configure the data you want to be
5. Select the detector you want in the
6. Select the detector value you want in the
"Interfaces" tab.
corresponding checkbox in the
"Enabled" column.
format for the data output.
NOTE:
For PROFINET, the binary
format must be selected for the
data output.
"Data output" tab.
the data output.
output.
Use the "+" button to gener ate new
entry.
What the buttons do:
l "+": Insert new entry
l "-": Delete marked entry
l "Up", "Down": Displace marked
entry
"Detector" column.
"Value" column so that this value willbe
output through the enabled interface.
Additionalinformation: Data output (ASCII /
binary)
Start sensor
06814859 - 1/24/2019-00 Page 17 EN
VISOR®Communications manual
1. Clickon the "Star t sensor" setup step.
The data will be transferred to the vision
sensor and the vision sensor will be
started.
Page 18 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
4 Ethernet TCP/IP, port 2005 / 2006
Numerical data, which has been configured under Output/Telegram, can be output in a separate
ASCII/BINARY format.
The sensor here is the (socket) "server", and provides the data via a "server socket" interface.
This is mainlya "programming interface".
To read / process the data, a "socket client" (PC, PLC, etc.) must establisha (socket) connection
(active) to the sensor, and then receivesthe data.
Hand ling, settin gs
4.1 Example: Data output from VISOR®to PC / PLC
Step 1:
After the job with allnecessary detectors, if alignment, etc. is set, the Ethernet interface for data
output is activated here and, if necessary, parameterized.
Fig. 6: Data output, Ethernet
In the example, the Ethernet interface is activated in the parameter field in the tab "Interfaces" by
marking the checkbox"Active". The default settings for input port (IN) = 2006 and output port
(OUT) = 2005 are adopted in this way. Any other settings can be made here to adapt the data
output to your networkenvironment. If necessary, contact your network administrator.
Step 2:
The "Data output" tab configures the user data to be output via Ethernet Port 2005.
In this example, it is the:
l Trailer "010"
l Overallresult of Detector 1
l Trailer "xxx"
"ASCII" is defined as a data format, which facilitatesthe traceabilityof this example. The function
with other data or in binary is analogous to settings made here by way of example.
06814859 - 1/24/2019-00 Page 19 EN
VISOR®Communications manual
Fig. 7: Data output, Configure output data
Step 3:
After opening the Hercules Ethernet tool, you will need to open the "TCP-Client" tab to
communicate with the VISOR®socket server via Ethernet.
Fig. 8: Data output, Ethernet Tool / 1
You will need to enter the IP addressof the VISOR®and the correct port in order to receive data.
The IP addressof the VISOR®can be found in SensoFind. See the first line in the window "Active
sensors" = 192.168.60.199
Page 20 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 9: SensoFind, IP address ...
The port number for the output port was adopted under Step 1 with Port 2005.
Step 4:
Therefore, the following settings are made in Hercules: Module IP = 192.168.60.199, Port =
2005. All other settings remain in the default values. Clicking on the "Connect" button willestablish
a connection to the VISOR®, and the connection willbe shown in green letters in the main
window.
06814859 - 1/24/2019-00 Page 21 EN
VISOR®Communications manual
Fig. 10: Data output, Ethernet Tool/ 2
Step 5:
You will now need to start the VISOR®from the PC application with "Start sensor" (later during
operation, the VISOR®willrun normallyafter being turned on and willtransmit data if
configured). Here in the example, T rigger mode = continuously set, i.e. evaluation is done
continuously and data are sent. These are only visible in the main window of Hercules.
Page 22 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 11: Data output, Ethernet, Start sensor
06814859 - 1/24/2019-00 Page 23 EN
VISOR®Communications manual
Fig. 12: Data output, Ethernet, Tool/ 3
The data visible here are set under "Data output":
l Trailer "010"
l Overallresult of Detector 1 (here, a "P" for positive, since test condition: brightness fulfilled)
l Trailer "xxx"
4.2 Example: Commands (requests) from PC / PLC to VISOR
With acknowledge / data output from VISOR
®
®
Step 1
For better clarity, the triggered operation isswitched to here for Example 2. Thiscan be done as
follows: Under Job/Image acquisition/Trigger mode = Set Trigger. Otherwise, the settings from
Ethernet example 1 will remain the same in the VISOR®.
Page 24 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 13: Data output, Ethernet, Tr igger
Step 2
In order to transmit commands to the VISOR®, the Hercules application needs to be opened
again. This time with port 2006 as the VISOR®input port through which it can receive commands.
Alltelegrams (commands and response strings) to and from the VISOR®are described in section
Overview telegrams (Page 81).
Fig. 14: Data output, Ethernet Tool/ 4
In the right pane, the "TRG" command (for Trigger; see first line on the bottom for command)
was sent from port 2006 to the VISOR®by clicking on the corresponding "Send" button. T his
command is shown in the main window in red letters when being sent. The VISOR®responds to
06814859 - 1/24/2019-00 Page 25 EN
VISOR®Communications manual
port 2006 with an acknowledge to the "T RG" command and, in this case, "P" for a positive
detector 1 result (black letters in right pane).
In the left pane, the VISOR®uses output por t 2005 to send the "010Pxxx" value defined in Data
output the same way as in the Ethernet 1 example.
4.3 Example: Job change from PC / PLC to VISOR
With acknowledge / data output from VISOR
®
®
Function of both Ethernet ports fo r in- and out put:
*A: Port 2005, only one direction: Sensor >> PC, all user data, defined under "Data output"
*B: Port 2006, both direction: Sensor <> PC, commands to VISOR®with acknowledge, + all
response data to commands(no payloads)
Fig. 15: Ethernet ports
Step 1
For better clarity, it is switched here to the triggered mode. This can be done as follows: Under
Job/Image acquisition/Trigger mode = Set Trigger. Otherwise, the settings from Ethernet
example 1 willremain the same in the VISOR®. All data output definitionsare made here in
"ASCII" for better traceability of the examples.
In this example, at least two jobs must be saved on the VISOR®. Usethe function “Duplicate” to
create a job on the basis of an existing job. For easy testing of the job change, adapt the following
parameter. Later, you can define the output as r equired.
For this example, Job 1 was defined with the data output:
l Start: "010" and
l Trailer: "xxx"
Page 26 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 16: Data output, Ethernet, Job switch Job 1
Fig. 17: Data output, Ethernet, Job switch, Job 2
Step 2
06814859 - 1/24/2019-00 Page 27 EN
VISOR®Communications manual
Here, the application Hercules was opened twice. Once with port 2005 (receiving of r esultsas
defined in "Data output") and port 2006 (commands + acknowledge) asVISOR®input port
through which it can r eceive commands.
Alltelegrams (commands and response strings) to and from the VISOR®are described in section
Overview telegrams.
Fig. 18: Data output, Ethernet, Job switch, Tool/ 1
In the right window (Port 2006), the command TRG (Trigger, see "Send" below, first line) was
issued. Thisis displayed in the main window in red letters with "TRG". The VISOR®responds
immediatelywith the "T RGP" acknowledge (repetition of "TRG" command and "P" for positive, in
blackletters in the right pane)
In the left pane (Port2005), the VISOR®on which Job 2 is currentlyactive sends the
corresponding r esultstring, which is defined in Data output in Job 2 with "020Pyyy".
Fig. 19: Data output, Ethernet, Job switch, Tool/ 2
Now in the r ight window ( Port2006), the command CJB001 (Change Job 001, 001 = Job no. 1,
see "Send" below, second line) was issued. This is displayed in the main window in red letters with
"CJB001". The VISOR®responds immediately with the "CJBPT001" acknowledge (repetition of
"CJB" command, "P" for positive, "T" = Triggered, 001 job number to which the change was
made)
Page 28 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 20: Data output, Ethernet, Job switch, Tool/ 3
After the next T rigger command TRG (see "Send" below, third line) is displayed again in the main
window in red letters. The VISOR®immediatelyresponds again with the "T RGP" acknowledge
(repetition of "TRG" command and "P" for positive)
In the left pane (Port2005), after the job has changed to Job 1, the VISOR®sends the
corresponding r esultstring, which is defined in Data output in Job 1 with "010xxx"!
4.4 Example Beckhoff CX 1020
The connection to a Beckhoff CX 1020 and the corresponding configuration is described in the
following document:
Startmenü/SensoPart/VISOR Vision-Sensor/Tools/SPS PLC/...
4.5 Example Siemens S7
The connection to a Siemens S7 PLC and the corresponding configuration is described in the
following document: "Siemens S7 Operating Instructions" in:
Startmenü/SensoPart/VISOR Vision-Sensor/Tools/SPS PLC/...
06814859 - 1/24/2019-00 Page 29 EN
VISOR®Communications manual
5 Service / Visualization
There is a service port (Ethernet TCP/IP port 1998) available for the VISOR®vision sensor. This
port will be availableregardless of how you configure the various steps.
5.1 Backup creation
The following telegrams can be used for automatic backups and restores
l Read job set (ASCII)
The "Import job set" telegram can be used to change the VISOR®vision sensor’s job set.
The job set file must first be loaded onto the VISOR®.
l Save job set (ASCII)
The "Back up job set" telegram can be used to read the VISOR®vision sensor’s job set.
5.2 Visualization
The VISOR®vision sensor provides all data through the service port so that applications can be
visualized.
Additionalinformation: Update visualization data (ASCII) (Page 161)
06814859 - 1/24/2019-00 Page 30 EN
VISOR®Communications manual
6 VISOR®telegrams for PROFINET and EtherNet/IP
6.1 Module 1: "Control" (from controller to VISOR®)
Name in controller "CTRL (3 bytes)"
Timing diagramsfor VISOR® communication (Page 36)
Page 31 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
6.2 Module 2: "Status" (from VISOR®to controller)
Name in PLC "STAT (6 bytes)"
06814859 - 1/24/2019-00 Page 32 EN
VISOR®Communications manual
Page 33 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
6.3 Module 3: "Data" (from VISOR®to controller)
Name in PLC "DATA (2 + 8 / 16 / … bytes)"
6.4 Module 4: "Request" (from controller to VISOR®)
Name in PLC "REQU (4 + 8 / 16 / … bytes)"
06814859 - 1/24/2019-00 Page 34 EN
VISOR®Communications manual
6.5 Module 5: "Response" (from controller to VISOR®)
Name in PLC "RESP (4 + 8 / 16 / … bytes)"
6.6 Start / end criteria for each telegram
Telegram
("Control"
module)
Trigger Ready = T rue Trigger acknowledge = True Image ID changed
Change Job /
Switch-to-Run
Page 35 EN 06814859 - 1/24/2019-00
Start condition
("Status"
module)
Operation Mode =
False
Acceptance confirmation
("Status" module)
Change Job acknowledge =
True
Switch-to-Run acknowledge
= True
Execution
confirmation
("Status" module)
Job number changes
Operation Mode =
True
VISOR®Communications manual
7 Timing diagrams for VISOR®communication
Case: Trigger ok
Fig. 21: Timing Trigger ok
Case: Trigger not po ssible (not ready)
Fig. 22: Timing Trigger not ready
06814859 - 1/24/2019-00 Page 36 EN
Case: Job change ok
Fig. 23: Timing Job change ok
Case: Job change delayed
VISOR®Communications manual
Fig. 24: Timing Job change delayed
Page 37 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Case: Job change no t possible (e.g. wrong job number)
Fig. 25: Timing Job change not possible
Case: Switch to run ok
Fig. 26: Timing Switch to run ok
06814859 - 1/24/2019-00 Page 38 EN
Case: Switch to run not p ossible
Fig. 27: Switch to run not possible
VISOR®Communications manual
Page 39 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
06814859 - 1/24/2019-00 Page 40 EN
VISOR®Communications manual
Page 41 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
8 Request sequences
Important recommendations for PL C programmers
1. Follow the sequence of requests
2.
Wait for complete execution of an action before sending the next one. Complete
execution takes placewhen the image ID changes in the trigger request, or the
corresponding acknowledge bit is set for the other requests.
PLEASE NOTE:
The complete execution of an action cannot be reliably determined based on a
low/high transition at READY, since it ispossible for there to be long cycle times
between the PLC and VISOR®(e.g., 32 ms) that result in READY never having a low
state.
3. READY should always be high before a trigger requestissent
Accepting / discarding of requests of the control module
1. Request is accepted with an increasing acknowledge bit
2. Request is discarded if the error bit is set.
3. Request is discarded without an err or bit and acknowledge bit if the sensor is still
processing the previous request and no acknowledgment has yet been set for it. (i.e. not
following the recommended handshake)
06814859 - 1/24/2019-00 Page 42 EN
Trigg er Request Sequence
VISOR®Communications manual
Page 43 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Chan ge jo b request sequence
06814859 - 1/24/2019-00 Page 44 EN
VISOR®Communications manual
Switch to Run sequence
Page 45 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
06814859 - 1/24/2019-00 Page 46 EN
Sequence for requests via request/response module
VISOR®Communications manual
Telegrams: Availabilityand supported interfaces (Page 85)
Error codes (Page 88)
Error Reset (depicted in the use case "Job chang e not possible")
1. Reset with "Reset Error Bit"
Page 47 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
2. Error bits are overwritten by new error bits.
06814859 - 1/24/2019-00 Page 48 EN
VISOR®Communications manual
9 PROFINET
This section explains how to oper ate the VISOR®vision sensor with PROFINET.
9.1 Siemens S7-1200 TIA 12 configuration example
This description shows all PLC screenshots in English; switch the TIA software to English if
necessary.
9.1.1 Create new project
New project with: Project / Create new project
Fig. 28: PROFINET Create new project
9.1.2 Selecting the GSD file
First a PROFINET PLC must be added to the project.
In order to be able to use the PROFINET functions of the VISOR®vision sensor, the latest
version of the corresponding VISOR®GSD file must be installed. This is done at: Options/Install
general station description file. The GSD file can be found in the installation path for the VISOR
in: ...\SensoPart\VISOR®Vision-Sensor\Tools\PROFINET and is also available for download at
www.sensopart.com.
06814859 - 1/24/2019-00 Page 49 EN
®
VISOR®Communications manual
Fig. 29: Selecting and installing the GSD file
9.1.3 Adding the VISOR®to the project
The VISOR®modules are added in the har dware catalog: Other field devices/PROFINET
IO/Sensors/ SensoPart Industriesensorik GmbH.
Page 50 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 30: Adding the VISOR®to the project
Connecting the VISOR®to the PLC
You can now drag a VISOR®module from the catalog and drop it in the Network View. T he
VISOR®is connected to the PLC via PROFINET (Network View tab).
06814859 - 1/24/2019-00 Page 51 EN
Fig. 31: Connecting the VISOR®to the PLC
Definition of I/O data
VISOR®Communications manual
In the tab "Device view", the modules CTRL (Control) and STAT (Status) are active by default.
As an option, the module DATA (Data module) can be added with a certain use size.
In this example: 2 bytes + 16 bytes of payload (1 byte: Image ID, 1 byte: Result data overrun (see
Module 3: "Data" (from VISOR® to controller) (Page 34)), + 16 bytes of data). If the data are
longer than the defined range, these are truncated (in this case: Result data overrun = 1); if it’s
shorter, the rest of the 16 bytes are filled with 00h.
Page 52 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 32: Enter I/O data
06814859 - 1/24/2019-00 Page 53 EN
VISOR®Communications manual
Configuring the VISOR®IP address
Option 1: In the p roject
The IP addressfor the VISOR®can be assigned through the project in the PLC. Select option
"Set IP address in the project" and enter IP address. The address from the "IPaddress" field will
be wr itten to the VISOR®. The IP addresses of the PLC and the VISOR®must be different fr om
each other but correspond to each other, i.e., fall within the same addressspace.
Fig. 33: Configuring the VISOR®IP addressin the project
The VISOR®can also be used without a running PROFINET, and accordingly can be configured
via SensoFind. If the IP address of the VISOR®does not match the one in the TIA project, the
PLC will configure the IP addressinstead. In this case,the original configuration in the VISOR
willbe overwritten with 0.0.0.0. This meansthat the IP address is set correctly but the IP
configuration is deleted (thisis important for a restart, possibly without a connected PLC).
Option 2: In SensoFind
Page 54 EN 06814859 - 1/24/2019-00
®
VISOR®Communications manual
The IP addressof the VISOR®can also be configured via SensoFind. Select option "Set IP
address using a different method" in the PLC / TIAinterface. Configure the IP address via
SensoFind (please refer to section: Settings in SensoFind (Page 15)).
Fig. 34: Configure the IP address for the VISOR®in SensoFind; the corresponding settings can
be found in the PLC/TIA interface
Set the name in the TIA portal
There are two ways to configure the name for the VISOR®from the TIA Portal.
Generate name aut omatically
The PROFINET name for the VISOR®can be generated automaticallyin the PLC. Option:
"Generate PROFINET device name automatically" takes the name from the project.
Set n ame manually
06814859 - 1/24/2019-00 Page 55 EN
VISOR®Communications manual
If the option "Set PROFINET device name using a different method" is activated, any name can
be edited.
Information: In the field "Converted name", a different name than entered is displayed, which is
then also used. As in the PROFINET, not all characters can be used, a conversion may be
necessary, which is made here automatically(names must be DNS-compatible, see also Chapter
Settings in SensoFind (Page 15)).
If the VISOR®vision sensor’s name is configured using the TIA Portal, it must be wr itten to the
sensor with the "PROFINET device name" tool(as described in section VISOR®).
The PROFINET name in the project and in the VISOR®must match.
Fig. 35: Set name in project
9.1.4 Writing a name to VISOR
In order to be able to establish communications, the PROFINET name must be written to the
VISOR®in case it needs to be updated.
Page 56 EN 06814859 - 1/24/2019-00
®
VISOR®Communications manual
This is done with the tool: Online/Assign PROFINET device name. Select the corresponding
device (VISOR®) and apply the name with "Assign name."
Fig. 36: Writing a name to VISOR
®
9.1.5 Load the project onto the PLC
To finish the configuration and save changes of the project: 1. tr anslate and 2. transfer / write to
the PLC
Fig. 37: Tr anslate project and write to PLC
9.1.6 Mapping of output data
The VISOR®vision sensor’s output data can be mapped to the data in the PROFINET log as
follows:
Step 1) T he start address for an input variable can be taken from "Device Overview".
06814859 - 1/24/2019-00 Page 57 EN
VISOR®Communications manual
Fig. 38: Table of variables
Step 2) Creating a tag tab le in the PLC
Fig. 39: Device overview
Step 3) Creating the configuration in SensoFind and saving th e con figured log as a
CSV file.
Fig. 40: Output for mat saved as CSV file
Step 4) Opening the file with th e text program
Page 58 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 41: Output pr otocolin Excel representation
For a description of the format of the PROFINET Data module, please refer to Module 3: "Data"
(from VISOR® to controller) (Page 34)
Step 5) T he result is the following assig nment between the inpu t data of the PLC
Fig. 42: Input data PLC
... and the configured protocol:
Fig. 43: In the vision sensor configured protocol
Con version of binary values
Alldetector-specificpayloads with decimal places willbe transmitted as integers multiplied by
1000, and accordinglymustbe divided by 1000 after the data is received. The valuesare
06814859 - 1/24/2019-00 Page 59 EN
VISOR®Communications manual
transferr ed in the format "Big-endian". The length is based on the value, e.g., score 32 bits
(DWord).
9.2 PLC example programs
The following PLC example programs show some basic functions.
PLC example 1: Trigger when VISOR®ready
Fig. 44: Tr igger when VISOR®ready (without err or handling)
PLC example 2: Send Job number to VISOR
Page 60 EN 06814859 - 1/24/2019-00
®
VISOR®Communications manual
Fig. 45: Send job number
PLC example 2.1: Job change when VISOR®ready
Fig. 46: Job change when VISOR®ready (without err or handling)
PLC example 3: Switch to Run when VISOR®in configuration mode
06814859 - 1/24/2019-00 Page 61 EN
VISOR®Communications manual
Fig. 47: Switch to Run when VISOR®in configuration mode (without er ror handling)
PLC example 4: Data transfer, data block on PLC, creating tags
Variable "Data Array" (type: Array of Byte) Length (34 bytes) = User data (32) + 2 bytes (header)
(Module "Data" with 32 bytes: User data + 1 byte: Image ID + 1 byte: Result data overrun = 34
bytes)
Fig. 48: Data block for data transfer
PLC example 4.1: Data transfer
Data transfer from input memory to data block with function DRPD_DAT. Access to diagnosis
address via "PLC_T ags". Conversion of data of the read codes into a string with variable data
length.
Fig. 49: Data transfer
PLC example 4.2: VISOR®telegram settings
Page 62 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 50: Settings for sample telegram in VISOR
®
06814859 - 1/24/2019-00 Page 63 EN
VISOR®Communications manual
10 EtherNet/IP
This section explains how to oper ate the VISOR®vision sensor with EtherNet/IP.
10.1 Rockwell CompactLogixTMconfiguration example
Following is a description of the PLC settings required for data transfers between the VISOR
vision sensor and the PLC via EtherNet/IP (using Rockwell CompactLogixTMas an example).
®
10.2 Rockwell Studio 5000 configuration example
This description shows all PLC screenshots in English; switch the Rockwell software to English if
necessary.
10.2.1 Create new project
Create the project in: Create/New Project.
Fig. 51: EtherNet/IP Create new project
06814859 - 1/24/2019-00 Page 64 EN
VISOR®Communications manual
Select the right PLC type and assign a name.
Fig. 52: EtherNet/IP Select the PLC type.
You can apply the default settings. Clickon "Finish" to create the project.
Fig. 53: EtherNet/IP Apply the default settings.
Page 65 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
10.2.2 Select EDS file
In order to be able to use the EtherNet/IP functions of the VISOR®vision sensor, the latest
version of the corresponding VISOR®EDS file must be installed. The EDS file can be installed in:
Tools/EDS Har dware Installation Tool.
Fig. 54: Project view, Tool, EDS Hardware Installation Tool
06814859 - 1/24/2019-00 Page 66 EN
Confirm information with Next.
Fig. 55: Confirming information
Select "Register an EDS F ile(s)" in the options.
VISOR®Communications manual
Fig. 56: Register an EDS File(s)
Page 67 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Select "Register a single file" and specify the path to the EDS file.
The EDS file can be found in the installation path for the VISOR®in: ...\SensoPart\VISOR
®
Vision-Sensor\Tools\EtherNet/IP and is also available for download at www.sensopart.com.
NOTE:
The exact same EDS file can be used for all VISOR®vision sensors.
Fig. 57: Select EDS file
06814859 - 1/24/2019-00 Page 68 EN
Confirm the EDS file test.
Fig. 58: EDS file test
If necessary, select an icon or continue with the default icon.
VISOR®Communications manual
Fig. 59: Icon
Page 69 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Confirm the installation.
Fig. 60: Confirming the installation
Clickon Finish to successfullycomplete the installation.
Fig. 61: Finishing the installation
06814859 - 1/24/2019-00 Page 70 EN
VISOR®Communications manual
10.2.3 Load the project onto the PLC
Go online with the project. T o do this, click on Communications/Go Online.
NOTE:
Before this, the project path must be configured corr ectly.
Page 71 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Right-clickon the networkconnection you want to create a new module.
Fig. 62: Creating a new module
06814859 - 1/24/2019-00 Page 72 EN
VISOR®Communications manual
Select VISOR®from the catalog or searchfor available devices online.
NOTE:
The software must alreadybe online in order to be able to use the online search
option.
The VISOR®modules are added in the har dware catalog: Other field devices/PROFINET
IO/Sensors/ SensoPart Industriesensorik GmbH.
Configure the device name and IP address for the VISOR
The devicename will be used as a variable name for the data later on. The IP addresscan be
read with the SensoFind module in the VISOR®software.
®
Fig. 63: Configure the device name and IP address
Page 73 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
You can select the modules and module sizesyou want with "Change ..." Additional information:
VISOR® telegramsfor PROFINET and EtherNet/IP (Page 31)
In Connection, configure the refresh rate time(RPI) you want.
Fig. 64: Set the refresh rate.
Clickon OK to finish configuring the settingsfor the node.
Download the project onto the PLC with Communications/Download.
06814859 - 1/24/2019-00 Page 74 EN
Fig. 65: Download
Check all information and confirm with Download.
VISOR®Communications manual
Page 75 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 66: Information
After a successful download, the sensor will have the "Running" status.
06814859 - 1/24/2019-00 Page 76 EN
VISOR®Communications manual
Fig. 67: Running
10.2.4 Mapping of output data
The input data is mapped as follows. (selection of module CNTL + STAT + data (2+69))
Vision-Sensor-Dev …. I1.Data[0] – …. I1.Data [5] Statusmodule (Module 2: "Status" (from
VISOR® to controller) (Page 32))
e.g. ... I1.Data [3] = Job number
…. I1.Data[4] = Image_ID
The data moduleisappended directly. Start of Data module from ... I1.Data[6] - …. I1.Data[71]
The data specified in Output/Telegram is inserted here. Additionalinformation: Defining
telegrams / data output in SensoConfig (Page 17)
Page 77 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 68: Output data
Con version of binary values
Alldetector-specificpayloads with decimal places willbe transmitted as integers multiplied by
1000, and accordinglymustbe divided by 1000 after the data is received. The valuesare
transferr ed in the format "Big-endian". The length is based on the value, e.g., score 32 bits
(DWord).
06814859 - 1/24/2019-00 Page 78 EN
VISOR®Communications manual
10.3 PLC example programs
The following PLC example programs show some basic functions.
PLC example 1: Trigger when VISOR®ready
Fig. 69: Tr igger when VISOR®ready (without err or handling)
PLC example 2: Job change when VISOR®ready
Fig. 70: Job change when VISOR®ready (without err or handling)
PLC example 3: Switch to Run when VISOR®in configuration mode
Page 79 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Fig. 71: Switch to Run when VISOR®in configuration mode (without er ror handling)
06814859 - 1/24/2019-00 Page 80 EN
VISOR®Communications manual
11 Appendix
11.1 Telegram, Data Output tab
This section describes the telegrams available for the VISOR®vision sensor. These telegrams
can be sent to the VISOR®vision sensor through various interfaces.
l Ethernet TCP/IP
l PROFINET (Request / Response module)
The telegrams are available in ASCII and Binaryformat. T he format isdefined in the module
"SensoConfig", in the tab "Data Output" of the setup "Output".
The following settings are possible:
Communication TCP / IP EtherNet/IP PROFINET
Telegram format ASCII / Binary Binary Binary
11.1.1 Overview telegrams
VISOR®General
l Reset statistic (ASCII / Binary)
The "Reset statistics" telegram can be used to reset the VISOR®vision sensor’s internal
statisticscounter.
VISOR®Check
l Trigg er (ASCII / Bin ary)
With the telegram "Tr igger", an image can be acquired. Some commands need additional
image acquisition. The result data of the evaluation are output via the "Out" port.
l Extended trigger (ASCII / Bin ary)
This telegram "Extended trigger" is an expansion of the "trigger" telegram. Besidesthe
result data, there is also the option to assign an ID or to receive information about the
operating mode (run/config). Unlike the "tr igger" telegram, the result data of the "Extended
trigger" telegram are also transferred via the "In" port.
l Job change (ASCII / Binary)
The "Job change" telegram will trigger a job change on the VISOR®vision sensor.
l Job change permanent (ASCII / Binary)
The "Job change, permanent" telegram will trigger a permanent job change on the
VISOR®vision sensor. The job is run again after restarting.
l Job change by job name (ASCII / b inary)
The "Job change by job name" telegram will trigger a job change on the VISOR®vision
Page 81 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
sensor. The job will be run by job name. You can read the job names by using the "Read job
list" telegram, for example.
VISOR®Job settings
l Auto operating distance (ASCII / binary)
The "Auto operating distance" telegram can be used to have the operating distance for the
job be automaticallydetermined.
l Set o peratin g distance (ASCII / binary)
The "Set operating distance" telegram can be used to change the operating distance for
the job.
l Read operating distance (ASCII / binary)
The "Read operating distance" telegram can be used to read the current operating
distance for the job.
l Auto shutter sp eed ( ASCII / bin ary)
The "Auto shutter speed" telegram can be used to have the shutter time for the job be
automaticallydetermined.
l Set shutt er speed (ASCII / Binary)
With the telegram "Set shutter speed", the shutter speed of the job can be changed. This
telegram can, for example, be used for brightness compensation.
l Read shut ter speed (ASCII / Binary)
With the telegram "Read shutter speed", the set shutter speed of the job can be read.
l Set g ain ( ASCII / Binary)
With the telegram "Set gain", the gain of the job can be changed. This telegram can, for
example, be used for brightness compensation.
l Read gain (ASCII / Binary)
With the telegram "Read gain", the set gain of the job can be read.
l Set p arameter (ASCII / Binary)
With the telegram "Set parameter", the detector parameters can be adjusted, e.g.
reference strings, detector thresholds.
l Read parameter (ASCII / Binary)
With the telegram "Read parameter", the set parameters of the detectors can be read.
l Set ROI (ASCII / Binary)
With the telegram "Set ROI", the position of the selected detector can be changed.
l Read ROI (ASCII / Binary)
With the telegram "Read ROI", the position of the selected detector can be read.
l Read job list (ASCII / Binary)
The "Read job list" telegram can be used to output a list of all available jobs on the VISOR
vision sensor.
®
06814859 - 1/24/2019-00 Page 82 EN
VISOR®Communications manual
l Read detector list (ASCII / Binary)
With the telegram "Read detector list", a list of all detectors in the current job will be
displayed.
l Teach detector ( ASCII / Binary)
The "Teach detector" telegram willresult in the specified detector being re-taught
(available onlyfor Pattern matching and Contour comparison).
l Set t rigger delay (ASCII / Bin ary)
With the telegram "Set tr igger delay", a delay for starting a trigger can be set (in time (ms)
or encoder steps).
l Read trigger delay (ASCII / Bin ary)
With the telegram "Read trigger delay", the set delay for starting a trigger can be read.
l Save job permanently (ASCII / binary)
The "Save job permanently" telegram willtake allthe parameters that were previouslyset
temporar ily and copy them to a job set.
VISOR®Calibration
l Calibration: Initialize point list (ASCII / Binary)
With the telegram "Calibration: Clear point list", the point list is initialized.
l Calibration: Add world poin t (ASCII / Binary)
With the telegram "Calibration: Add world point", a world point (fiducialor point pair) of the
point list isadded. The telegram can be used for the calibration method Point pair list
(Robotics) and Calibration plate (Robotics).
l Calibration: Point list (ASCII / Binary)
With the telegram "Calibration: Point list", the calibration is carried out using the point list in
the current job.
l Calibration:Validate point list (ASCII / Binary)
With the telegram "Calibration: Validate point list", the calibration is validated using the point
list.
l Calibration: Calibration plate (ASCII / Binary)
With the telegram "Calibration: Calibration plate", the calibration is carried out using the
calibration plate.
l Set f iducial (ASCII / Binary)
With the telegram "Set fiducial", the fiducials are set using the point list in the current job.
l Calibration:Copy calibration (ASCII / Binary)
With the telegram "Calibration: Copy calibration", the calibration of the current job is copied
to the selected destination.
l Calibration: Set parameter (ASCII / Binary)
With the telegram "Calibration: Set parameter", the parameter values for the calibration
can be set.
Page 83 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
l Calibration: Read parameter (ASCII / Binary)
With the telegram "Calibration: Read parameter", the set parameter values of the
calibration can be read.
VISOR®Visualization
l Get image (ASCII / Binary)
The "Get image" telegram can be used to get the image from the VISOR®vision sensor.
VISOR®Service (available o nly o n port 1998 and in ASCII format)
l Upd ate visualization results (ASCII)
With the telegram "Update visualization results", the visualization results, e.g. image,
detector information, and results, are updated.
l Read sensor id entity (ASCII)
With the telegram "Read sensor identity", the current firmware status as well as the
hardware type can be queried.
l Upd ate firmware (ASCII)
With the telegram "Update firmware", a firmware update isstarted. The firmware file must
first be loaded onto the VISOR®vision sensor.
l Read job set (ASCII)
The "Import job set" telegram can be used to change the VISOR®vision sensor’s job set.
The job set file must first be loaded onto the VISOR®.
l Save job set (ASCII)
The "Back up job set" telegram can be used to read the VISOR®vision sensor’s job set.
Data output
(ASCII / Binary)
This section provides information about the data output. In par ticular which format the individual
results receive.
Telegrams: Availabilityand supported interfaces (Page 85)
06814859 - 1/24/2019-00 Page 84 EN
VISOR®Communications manual
11.1.2 Telegrams: Availability and supported interfaces
Page 85 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
06814859 - 1/24/2019-00 Page 86 EN
Overview telegrams (Page 81)
VISOR®Communications manual
Page 87 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
11.1.3 Error codes
Error code Description
000 Successful
001 Error
003 Invalidparameter data
005 Invalidtelegram
006 Input par ameters with invalid size or invalid value
007 File does not exist
008 Recorder off
009 Matching image of requested type not found
010 Invalidfile name or length
011 Invaliddata length
012 Not allowed due to job set mismatch
013 Failed to start new job fr om job set
016 Firmware version mismatch
018 Calibration plate data not available
020 More than one visfile present
021 Sensor type does not match for vis file
030 Calibration not enabled
031 Calibration copy err or
032 Mismatched input conditionsfor destination job
033 Calibration / validation err or
034 Invalidnumber of points
035 Calibration error: Add point, e.g. last job result failed
036 Invalidfiducial
037 Job set protection error: "Permanent" job change is not allowed
038 Parameter values are not available to write / read
039 Sensor is in configuration mode. The telegram was rejected
040 Write / read error for parameter value
041 No matching job found
042 Format mismatch error
043 Jobset/Job saving error
06814859 - 1/24/2019-00 Page 88 EN
Error code Description
044 Focus lock time error
045 Multiple files error
VISOR®Communications manual
Page 89 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
11.1.4 Serial communication ASCII
Reset statistic (ASCII)
Telegrams: Availabilityand supported interfaces (Page 85)
Overview telegrams (Page 81)
Reset statistics (ASCII) req uest string to sensor
Byte no. Content Meaning
1 R
Reset Statistics2 S
3 T
Example: RST
Reset statistics (ASCII) resp onse string from sensor
Byte no. Content Meaning
1 R
Reset Statistics2 S
3 T
4
Example: RSTP
Additionalinformation:
Accepted in run mode: Yes
Accepted in config mode: No
Accepted when Ready is low: Yes
Status of Ready signal during
processing:
Supported interfaces:
06814859 - 1/24/2019-00 Page 90 EN
P
F
P successful (Pass)
F Fail
No change
Telegrams: Availabilityand supported interfaces
(Page 85)
End of telegram: Max. 4 bytes (optional)
VISOR®Communications manual
Page 91 EN 06814859 - 1/24/2019-00
VISOR®Communications manual
Trigger (ASCII)
Telegrams: Availabilityand supported interfaces (Page 85)
Overview telegrams (Page 81)
Trigg er (ASCII) request string to sensor
Byte no. Content Meaning
1 T
2 R
3 G
Example: TRG
Trigg er (ASCII) response string from sensor
Byte no. Content Meaning
Trigger (simple trigger, inport)
1 T
2 R
3 G
4
Example: TRGP
Additionalinformation:
Accepted in run mode: Yes
Accepted in config mode: Yes
Accepted when Ready is low: No
Status of Ready signal during processing: Low
Supported interfaces:
End of telegram: Max. 4 bytes (optional)
06814859 - 1/24/2019-00 Page 92 EN
P
F
Trigger (response to
command trigger without
index, via port 2006. If
defined: Result data
without index via port 2005)
P successful (Pass)
F Fail
Telegrams: Availabilityand
supported interfaces (Page
85)
VISOR®Communications manual
Extended trigger (ASCII)
Telegrams: Availabilityand supported interfaces (Page 85)
Overview telegrams (Page 81)
Extended trigger (ASCII) request string to sensor
Byte no. Content Meaning
1 T
2 R
3 X
4 - 5 X Length of following data (n)
6 ... n X Data
Example: TRX06MyPart
Extended trigger (ASCII) respon se string from sensor
Byte no. Content Meaning
1 T
2 R
3 X
4
5 - 6 X Length of following data (n)
7 ... n X Data of sending command
n+1
P
F
C
R
Extended trigger, (trigger
with index, for correlation of
trigger to corresponding
result data, via port 2006)
Extended trigger,
(response to trigger with
index and result data, via
port 2006, for correlation of
trigger to corresponding
result. Result data without
index via port 2005)
P successful (Pass)
F Fail
C = Config
R = Run
n+2 ... n+9 X
n+9 ... m X Result data
Page 93 EN 06814859 - 1/24/2019-00
Length of following result
data (n)
VISOR®Communications manual
Example: TRX06MyPartR00000000
Additionalinformation:
Accepted in run mode: Yes
Accepted in config mode: Yes
Accepted when Ready is low: No
Status of Ready signal during processing: Low
Telegrams: Availabilityand
Supported interfaces:
supported interfaces (Page
85)
End of telegram: Max. 4 bytes (optional)
06814859 - 1/24/2019-00 Page 94 EN
VISOR®Communications manual
Job change (ASCII)
Telegrams: Availabilityand supported interfaces (Page 85)
Overview telegrams (Page 81)
Job change (ASCII) req uest string to sensor
Byte no. Content Meaning
1 C
Change Job2 J
3 B
4 - 6 X Job number
Example: CJB005
Job change (ASCII) resp onse string from sensor
Byte no. Content Meaning
1 C
Change Job2 J
3 B
4
5
6 - 8 X Job number
Example 1:
Example 2:
Additionalinformation:
Accepted in run mode: Yes
Accepted in config mode: No
Accepted when Ready is low: Yes
Page 95 EN 06814859 - 1/24/2019-00
P
F
T
F
CJBPT005
CJBFF005
P successful (Pass)
F Fail
Triggered
Freerun
VISOR®Communications manual
Status of Ready signal during processing: Low
Telegrams: Availabilityand
Supported interfaces:
supported interfaces (Page
85)
End of telegram: Max. 4 bytes (optional)
NOTE:
If an error occurs during the job change, it is possible to change to Job 1.
06814859 - 1/24/2019-00 Page 96 EN
VISOR®Communications manual
Job change permanent (ASCII)
Telegrams: Availabilityand supported interfaces (Page 85)
Overview telegrams (Page 81)
Job change, permanent (ASCII) request string to sensor
Byte no. Content Meaning
1 C
Change Job Permanent2 J
3 P
4 - 6 X Job number
Example: CJP005
Job change, permanent (ASCII) response string from sen sor
Byte no. Content Meaning
1 C
Change Job Permanent2 J
3 P
4
5
6 - 8 X Job number
Example 1:
Example 2:
Additionalinformation:
Accepted in run mode: Yes
Accepted in config mode: No
Accepted when Ready is low: Yes
Status of Ready signal during
Page 97 EN 06814859 - 1/24/2019-00
P
F
T
F
CJPPT005
CJPFF005
P successful (Pass)
F Fail
Triggered
Freerun
Low
VISOR®Communications manual
processing:
Supported interfaces:
Telegrams: Availabilityand supported interfaces
(Page 85)
End of telegram: Max. 4 bytes (optional)
NOTE:
If an error occurs during the job change, it is possible to change to Job 1.
06814859 - 1/24/2019-00 Page 98 EN
VISOR®Communications manual
Job change by job name (ASCII)
Telegrams: Availabilityand supported interfaces (Page 85)
Overview telegrams (Page 81)
Job change by job name (ASCII) req uest string to sensor
Byte no. Content Meaning
1 C
Change Job by Name2 J
3 N
4 1 Request version
5 - 7 X Job name length
8 - n X Job name
Example: CJN1005Myjob
Job change by job name (ASCII) resp onse string from sensor
Byte no. Content Meaning
1 C
Change Job by Name2 J
3 N
4
5 - 7 X Error codes (Page 88)
8 X
Example: CJNP000T
Additionalinformation:
Accepted in run mode: Yes
Accepted in config mode: No
Page 99 EN 06814859 - 1/24/2019-00
P
F
P successful (Pass)
F Fail
Trigger mode
T - T rigger
F - F ree run
VISOR®Communications manual
Accepted when Ready is low: Yes
Status of Ready signal during
processing:
Supported interfaces:
Low
Telegrams: Availabilityand supported interfaces
(Page 85)
End of telegram: Max. 4 bytes (optional)
06814859 - 1/24/2019-00 Page 100 EN
Loading...