IFM O3D300 - Page 35

35
3D sensor
UK
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 Result
<ticket=0010> 0010
L<length> L000000045
CR+LF \r\n
<ticket=0010> 0010
<unique message ID> 000500000
<JSON content> {"ID": 1034160761,"Index":1,"Name": "Pos 1"}
CR+LF \r\n
Asynchronous message IDs
Asynchronous
message ID
Description Example Description
000500000 Application
changed
{"ID": 1034160761,"Index":1,"Name":
"Pos 1","valid":true}
000500001 Application
is not valid
{"ID": 1034160761,"Index":1,"Name":
"Pos 1","valid":false}
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 "".