Appendix; Process Interface; Sending Commands - IFM O3D300 Instrucciones De Uso

Sensor de visión 3D

13. Appendix

13.1 Process Interface

The process interface is used during the normal operation mode to get operational data (e.g. 3D images,
process values) from the O3D3xx.

13.1.1 Sending Commands

For sending commands via the process interface the commands have to be sent with a special protocol
and as ASCII character strings. This protocol conforms to the version 3 of the O2V/O2D products.
Structure of the protocol:
<Ticket><length>CR LF <Ticket><content>CR LF
Abbreviation Description
CR Carriage Return
LF Linefeed
< > Marking of a placeholder
(e.g. <code> is a placeholder for code)
[ ] Optional argument
(possible but not required)
Command Description
<content> It is the command to the device (e.g. trigger the unit).
<ticket> It is a character string of 4 digits between 0-9. If a message with a specific ticket is sent
to the device, it will reply with the same ticket.
A ticket number must be > 0999.
Use a ticket number from the range 1000 - 9999.
<length> It is a character string beginning with the letter 'L' followed by 9 digits. It indicates the
length of the following data (<ticket><content>CR LF) in bytes.
They are different protocol versions available:
Version Input format
V1 <Content>CR LF
V2 <Ticket><Content>CR LF
V3 <Ticket><Length>CR LF<Ticket><Content>CR LF
V4 <Content>CR LF
The default protocol version is "V3". It is recommended to use protocol version 3 for machine
to machine communication. This is due to the fact that only version 3 supports asynchronous
messages and provides length information.
Ticket numbers for asynchronous messages:
Ticket number Description
0000 Asynchronous results
0001 Asynchronous error messages / codes
0010 Asynchronous notifications / message codes
46
ASCII code (dec) ASCII code (hex)
13 D
10 A
Output format
As input
As input
As input
<length>CR LF<Content>CR LF