3 - Messages (Requests, Responses, Notifications, and Files)
3.2.1.2 TLV Example
Below is a brief example of a TLV-encoded request and response for Command 0xDF01 - Echo,
wrapped in the standard message format documented in section 3.2.2 Message Structure.
The host sends the host a binary byte stream AA0081040101DF018407DF018103010203, which
breaks down as follows:
•
AA00 = Standard Start of Message / API Framework Version (not TLV)
•
81, 04, 0101DF01
o Tag 81 = Request Message Parameter 1, Message Information
o Length 04
o Value 0101DF01
▪
01 = Request from host to device
▪
01 = Message reference number
▪
DF01 = Command 0xDF01 - Echo
•
84, 07, DF018103010203
o Tag 84 = Request Message Parameter 4, Request Payload
o Length 07
o Value DF018103010203
▪
DF01 = Payload format is for Request Command 0xDF01 - Echo (not TLV)
▪
Tag 81 = Payload Parameter 1, Value to Echo
▪
Length 03
▪
Value 010203 = Value to Echo 010203
In response, the sends the host a binary byte stream
AA0081048201DF018204000000008407DF018103010203, which breaks down as follows:
•
AA00 = Standard Start of Message / API Framework Version (not TLV)
•
81, 04, 8201DF01
o Tag 81 = Response Message Parameter 1, Message Information
o Length 04
o Value 8201DF01
▪
82 = Response from device to host
▪
01 = Message reference number
▪
DF01 = Command 0xDF01 - Echo
•
82, 04, 00000000
o Tag 82 = Response Message Parameter 2, Response Status (one byte Operation Status
Summary, three bytes Operation Status Detail)
o Length 04
o Value 00, 000000 = OK / Done, General / All Good / Requested operation was successful
•
84, 07, DF018103010203
o Tag 84 = Response Message Parameter 4 for Response Payload
o Length 07
o Value DF018103010203
DynaFlex II Go| Secure Card Reader | Programmer's Manual (COMMANDS)
Page 29 of 301 (D998200597-102)
Need help?
Do you have a question about the DynaFlex II Go and is the answer not in the manual?
Questions and answers