TB Event Mdb Status
Mdb Status Event
Identification.
Frequency.
Sent after change is detected or on request.
Body Structure.
Name |
Type |
Description |
mdb_status_timestamp |
Long |
Event timestamp |
mdb_status_type |
String |
Mdb Interface ID: -> Table 1 |
mdb_status_coin |
String |
Device Status: -> Table 2 |
mdb_status_bill |
String |
Device Status look Table 2 |
mdb_status_cashless |
String |
Device Status look Table 2 |
mdb_status_cashless2 |
String |
Device Status look Table 2 |
mdb_status_cgw |
Short |
Device Status look Table 2 |
Table 1. Mdb Interface ID.
Device Status |
Description |
Vmc |
Interface VMC -> Pheriperals |
VmcMcu |
Interface VMC -> Terminal |
Mcu |
Interface Terminal -> Pheriperals |
McuVnd |
Interface Terminal MDB Driver ( MCU as Master MDB ) -> Terminal Core ( VND ) |
Vnd |
Interface Terminal Core ( VND as Master MDB ) -> Terminal MCU |
Table 2. Parameters Info.
Device Status |
Description |
NOT_HANDLE |
Not operating or right after RESET |
NOT_OPERATING |
Peripheral device not responding |
DISABLED |
Operational but disabled |
FULLY_OPERATIONAL |
Fully operational |
ERROR |
Problem with peripheral hardware or protocol error |
UNKNOWN |
Unknown state - no info from MDB driver |
Diagram 1. Typical connection with status Interface ID example
Example.
{
"mdb_status_timestamp": 35468,
"mdb_status_type": "Vnd",
"mdb_status_coin": "UNKNOWN",
"mdb_status_bill": "UNKNOWN",
"mdb_status_cashless": "FULLY_OPERATIONAL",
"mdb_status_cashless2": "UNKNOWN",
"mdb_status_cgw": "UNKNOWN"
}