IDBlue – Communication Protocol v2.4.1
- 8 -
Data Capture
for Workforce
in Motion
Packet Structure
Packets are a sequence of bytes sent to the IDBlue device via a serial port connection.
The table below shows the formatting for all request and response packets used to communicate
with the IDBlue™ device.
Note
: the data length does not include the checksum.
* Please see Appendix C - Checksum Generation for information on how to calculate
the packet checksum.
Asynchronous Events
When the user presses the button on the device an asynchronous event is created, sending a packet
to the computer. To designate this packet as an asynchronous event, and not a possible response to
an earlier command issued over the serial connection, a special packet (ASYNCH) is sent before the
main packet to indicate that it is a asynchronous event. This has the form:
Response format (Asynchronous Header)
This is true for all modes of operation during a button press, excluding reactive mode.
Applications (and driver libraries) should interpret the response packet immediately following an
ASYNCH (asynchronous header) packet as an asynchronous event.
In reactive mode, only a button press response (as seen below) is sent.
Response format (Button Pressed)
Summary of Contents for IDBlue
Page 1: ...Data Capture for Workforce in Motion IDBlue Communication Protocol Baracoda TM December 2008...
Page 3: ...IDBlue Communication Protocol v2 4 1 3 Data Capture for Workforce in Motion GLOSSARY 47...
Page 15: ...IDBlue Communication Protocol v2 4 1 15 Data Capture for Workforce in Motion...
Page 43: ...IDBlue Communication Protocol v2 4 1 43 Data Capture for Workforce in Motion...
Page 44: ...IDBlue Communication Protocol v2 4 1 44 Data Capture for Workforce in Motion...
