Notification Message - Magtek DynaFlex II Go Programmer's Manual

3 - Messages (Requests, Responses, Notifications, and Files)

3.2.2.3 Notification Message

Table 3.2-5 - Notification Message Format
Tag Len
One byte standard Start of Message constant, not in TLV format.
•
0xAA = Standard start of message byte
One byte standard API Framework Version constant, not in TLV format, used for tracking version
compatibility. Devices that implement higher (newer) versions of the API framework are designed to be
reasonably compatible with current and previous (lower) versions:
•
0x00 = Pre-production development (limited breaking changes). At minimum, every device
MagTek ever produces using the MMS framework will accept this value.
•
0x01 = First Production release (no breaking changes)
•
0x02 = Second Production release
•
Etc.
81 var Message Information
Message Type & Direction
•
/null (1) 0x03 = Notification from host to device (Reserved)
•
0x83 = Notification from device to host
/null (1) Reserved, set to 0x00
Notification Source
This byte and the Notification Type form the first two bytes of
a unique six byte Notification ID. Use this byte to look up the
Notification Group subsection in 7 Notifications.
/null (1)
•
0x01 = Transaction
•
0x09 = Firmware Update
•
0x10 = Device
•
0x18 = User Interface
Notification Type
Append this byte to Notification Source to look up the
Notification 0xNNNN subsection in the Notification Group
subsection to find the documentation for the notification.
•
0x01 = Information Update
•
0x02 = Warning (e.g. low battery, reset soon)
/null (1)
•
0x03 = Action Request (device is asking the host to take
action)
•
0x04 = Callback (request for action from host, device
waits before continuing the related operation)
•
0x05 = Operation Complete (either success or error)
/null (var) Reserved
82 (4) Notification Detail Code
DynaFlex II Go| Secure Card Reader | Programmer's Manual (COMMANDS)
Value / Description
Page 39 of 301 (D998200597-102)
Typ Req Default
B R
R
R
R
R
O
B R