IFM O3D300 Instrucciones De Uso página 47

Format of asynchronous notifications
The format of the asynchronous notifications is a combination of the unique message ID and a
JSON formatted string containing the notification details: <unique message ID>:<JSON content>
Example for protocol version 3:
<ticket=0010>L<length>CR LF<ticket=0010><unique message ID>:<JSON content>CR LF
Result:
0010L000000045\r\n0010000500000:{"ID": 1034160761,"Index":1,"Name": "Pos 1"}\r\n
Explanation of the result:
Command
<ticket=0010>
L<length>
CR LF
<ticket=0010>
<unique message ID>
<JSON content>
CR LF
Asynchronous message IDs
Asynchronous
Description
message ID
000500000 Application
changed
000500001 Application
is not valid
000500002 image
acquisition
finished
Result
0010
L000000045
\r\n
0010
000500000
{"ID": 1034160761,"Index":1,"Name": "Pos 1"}
\r\n
Example
{"ID": 1034160761,"Index":1,"Name":
"Pos 1","valid":true}
{"ID": 1034160761,"Index":1,"Name":
"Pos 1","valid":false}
{}
Sensor de visión 3D
Description
If a application exists on
given index but it is invalid,
the ID and Name are filled
accoring to the application.
If there is no application on
given index, the application
ID will contain 0 and the
name an empty string "".
This message signals the
reciever, that the device
has finished the image
acquistion. This can be
used for cascading multiple
devices with a software
trigger.
ES
47