E0H (Self-Test Notification)¶
The terminal generates and sends the message in the following cases:
The terminal will automatically perform self-test (i.e., monitor the status of components) while the software is running. If the result of the self-test changes, the terminal will send a notification report to the backend server.
When the terminal executes the subcommand 99 of AT@RTO command from the backend server, the terminal will send a resulting report to the backend server.
When the subcommand 99 of AT@RTO command is initiated by other channels (not backend server), the terminal will respond with a resulting report to the initiator after executing the command, and the terminal will also send the resulting report to the backend server.
Report carrying this record is a high-priority report, please see here for more information.
The frame format of a report that only carries E0H record is as follows:
For example (Total 42 bytes):
2B 00 00 2A 00 01 23 45 67 89 01 23 45 C0 31 00 0A 00 00 13 66 8E 47 F7 00 00 E0 00 78 08 5D B3 8C 80 00 00 00 00 01 23 30 24
Parts |
Fields |
Length (Byte) |
Range/Format |
Default |
|
|---|---|---|---|---|---|
Head |
18 or 20 |
||||
Reserved |
1 or 1+N |
||||
Records |
Record Length |
1 or 2 |
00H-7FH or 8080H-FFFFH |
||
Generated Time |
4 |
||||
Record Count Number |
2 |
0000H-FFFFH |
|||
Record ID |
1 |
E0H |
E0H |
||
Event Code |
1 |
00H, 01H |
|||
Data of Record |
Data ID |
1 or 2 |
00H-7FH or 8080H-FFFFH |
||
Data Length |
1 or 2 |
00H-7FH or 8080H-FFFFH |
|||
Data Content |
N |
||||
… |
|||||
… |
|||||
Tail |
4 |
||||
The definitions of parts ‘Head’, ‘Reserved’, and ‘Tail’ are here.
Event Code
00H - Normal.
01H - Abnormal.
Data of Record
It consists of one or more Data ID units.
By default, this record contains only the data IDs listed below, which can be changed by the AT@QRC command described below.
Data 120 - Self-Test Status.
Configuration¶
The parameters related to the generation and transmission of E0H record are controlled by the following QRC command:
Example:
AT@QRC=gl601###,E0,,,1,120,012F$
+ACK:QRC,123456789012345,C031,10,0,E0,012F,20210407101530,1234$
AT@QRC?gl601###,E0,0C37$
+QRY:QRC,123456789012345,C031,10,0,1,1,E0,,,1,120,0C37,20210407101530,1234$
Parts |
Fields |
Length (Byte) |
Range/Format |
Default |
|---|---|---|---|---|
Head |
Header |
3 |
AT@ |
AT@ |
Command Word |
3 |
QRC |
QRC |
|
Leading Symbol |
1 |
= |
= |
|
Password |
8-16 |
gl601### |
||
Body |
Record ID |
2 |
E0 |
E0 |
Reserved |
||||
Reserved |
||||
Action |
1 |
0-2 |
||
Data IDs |
N |
ID1|ID2|ID3… |
||
Tail |
Sequence Number |
4 |
0000-FFFF (‘0’-‘9’, ‘A’-‘F’) |
|
Tail |
1 |
$ |
$ |
Record ID
Which record to configure. Always “E0” here.
Action
Empty - No change the data IDs in the terminal. If this field is empty, the ‘Data IDs’ field will be ignored.
0 - Append the data IDs carried in the ‘Data IDs’ field to the terminal.
1 - Replace the data IDs in the terminal with the data IDs carried by the ‘Data IDs’ field.
2 - Clear the data IDs carried in the ‘Data IDs’ field from the terminal.
Note: In particular, it always will be 1 when reading this field.
Data IDs
The data IDs contained in the E0H record. The characters ‘|’ are used to connect each data ID.
For example, “2|88” means Data 2 (Device Name) and Data 88 (SIM Card).