Balluff BVS ID-M1280-F1 Series, Configuration Manual

Page: 225 / 342

BVS ID-M1280xF1-xx-xxx
english 51
Result container
The inspection in monitor mode will send the result data in this message after processing the inspection.
Length in bytes Structure Value Description
2 UINT16 20
hex
Message ID
2 UINT16 User data length in bytes (the inspection
program ID is considered as user data)
2 UINT16 Inspection program ID. This section
indicates the inspection program, which
created the result container.
Result data as specified tool " Outputs ".
Bool value "false" is sent as 0x00, "value"
true as 0xFF.
Example of how a result container is formed:
After each completed inspection BVS ID sends a results container to the controlling system. The structure of
the user data depends on the configuration in BVS ID . In this example it is assumed that an inspection was
configured which provides a string of 20 bytes (= 14
hex
). BVS ID reads the value “Hello World” and sends it to
the controlling system.
The data encoding is in UTF-8 format. The code content that is read (11 bytes long) is shorter therefore than the
area provided in the message (20 bytes).
BVS ID therefore fills the remaining bytes with zeros. One byte chain is
simply sent after the other. Little-endian has no meaning here since these are individual bytes.
The entire message is thus:
20
hex
00
hex
(Message ID)
16
hex
00
hex
(user data length = 2 bytes for inspection ID + 20 bytes result data)
15
hex
00
hex
(inspection ID: 21)
48 65 6C 6C 6F 20 57 6F 72 6C
64 00 00 00 00 00 00 00 00 00
(UTF-8: 'H', 'e', 'l', 'l' 'o', space, 'W', 'o', 'r', ‚l‘, 'd', 9× fill-bytes)