Page 77/95
21January2021/Version 0
LEM International SA
Chemin des Aulx 8
1228 PLAN-LES-OUATES Switzerland
www.lem.com
7.5.
Status
and
errors
flags
7.5.1. Overview
The DCBM provides status and error flags allowing monitoring of its proper installation, its
readiness towards transactions, the fulfillness of its logbook, its internal operation, among others.
Those flags are available under various formats as follows:
• In
/status
API: current status and errors
• In
/legal
API: transaction status
• In
/ocmf
API: OCMF
EF
and
ST
fields
Additionally,
/logbook
API keeps track of raised statuses when a new event occurs.
Refer to "7.6. Event logbook".
7.5.2. Status/errors
value
field description
In
/status
API, status and error flags are available through two formats, as follows. In
/legal
), only
value
field format is used.
“suLinkStatusIsOk”
“status”
: {
“value”
: 17,
“bits”
: {
: true,
“muFatalErrorOccured”: false,
“transactionIsOnGoing”: false,
“tamperingIsDetected”: false,
“timeSyncStatusIsOk”: true,
“overTemperatureIsDetected”: false,
“reversedVoltage”: false,
“suMeasureFailureOccurred”: false
}
},
Format 1:
value
Concatenation of flags as a
binary value
Format 2:
bits
List of flags with explicit
name and unitary value
“errors”
: {
“value”
: 0,
“bits”
: {
“muInitIsFailed”: false,
“suStateIsInvalid”: false,
“versionCheckIsFailed”: false,
“muRngInitIsFailed”: false,
“muDataIntegrityIsFailed”: false,
“muFwIntegrityIsFailed”: false,
“suIntegrityIsFailed”: false,
“logbookIntegrityIsFailed”: false,
“logbookIsFull”: false,
“memoryAccessIsFailed”: false,
“muStateIsFailed”: false
}
},
Figure 44: Description of the 2 formats of status and errors
Summary of Contents for DCBM 400 Series
Page 95: ......
