Atop ABLEPick AT500 - 4.4.11 Return devices F;W model string.; 4.4.12 Return devices detail information

ABLEPick pick-to-light communication protocol
40
DATA[0]
DATA[1]
:
DATA[34]
DATA[0~2]: reserved for compatibility reason with older version format
DATA[3~34]: Field Device Status
Field Device Status:
Bit 0 of BYTE 0 -> status of SUB-NODE 1
Bit 1 of BYTE 0 -> status of SUB-NODE 2
Bit 2 of BYTE 0 -> status of SUB-NODE 3
．
．
Bit 7 of BYTE 0 -> status of SUB-NODE 8
Bit 0 of BYTE 1 -> status of SUB-NODE 9
．
．
Bit 7 of BYTE 1 -> status of SUB-NODE 16
．
．
Bit 6 of BYTE 24 -> status of SUB-NODE 199
Bit 7 of BYTE 24 -> status of SUB-NODE 200
*Note:
Bit value = 0 : normal (connected)
Bit value = 1 : abnormal (unconnected)
4.4.10 Special return code.
SUB-COMMAND = 64H
CCB LEN (L) = 0AH
Data length of this block
CCB LEN (H) = 00H
MESSAGE TYPE = 60H
60H : port 1
Reserved
Reserved
Reserved
SUB-COMMAND = 64 H
SUB-NODE = {01H ~ FAH}
0x01~0xFA (address)
or 0xFC (Broadcasting)
DATA[0] =
DATA[1] =
DATA[0] = 00H
The return message when the Keycode return function is enabled.
Data(1)= 16H “confirmatin key “ pressed
43H “shotage button/down-count button” pressed
25H “function button/up-count button” pressed.
Actually, the return code number is not only the above 3 values (16H, 25H and
43H), users can push the 3 buttons by different combinations to get different
return code. Within each combination, the last released button is different, then
the value will be different, even on the same buttons.
For example, push up-count + confirmation buttons together at the same time:
> release both up-count + confirmation together -> return code value is 04H