17H (GEO Information)¶
When the terminal detects entering or exiting Geo-fence according to the settings of the AT@GEO command, it will use this message to report to the backend server.
The frame format of a report that only carries 17H record is as follows:
For example (Total 60 bytes):
2B 00 00 3C 00 01 23 45 67 89 01 23 45 C0 31 00 0A 00 00 25 66 8E 47 F7 00 00 17 01 5C 02 01 00 52 16 09 F9 20 A8 E1 FF 2D C0 96 5F 17 9D A0 01 7D 0A 00 25 00 01 B3 0C 01 23 E3 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 |
17H |
17H |
||
Event Code |
1 |
01H, 02H |
|||
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
01H - The terminal enters the Geo-fence area.
02H - The terminal exits the Geo-fence area.
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.
Configuration¶
The parameters related to the generation and transmission of 17H record are controlled by the following QRC command:
Example:
AT@QRC=gl601###,17,,,1,2|88,0,012F$
+ACK:QRC,123456789012345,C031,10,0,17,012F,20210407101530,1234$
AT@QRC?gl601###,17,0C37$
+QRY:QRC,123456789012345,C031,10,0,1,1,17,,,1,2|88,0,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 |
17 |
17 |
Reserved |
0 |
|||
Reserved |
0 |
|||
Action |
1 |
0-2 |
||
Data IDs |
N |
ID1|ID2|ID3… |
||
Ignore Event When Geo-fence Initialed |
1 |
0-1 |
0 |
|
Tail |
Sequence Number |
4 |
0000-FFFF (‘0’-‘9’, ‘A’-‘F’) |
|
Tail |
1 |
$ |
$ |
Record ID
Which record to configure. Always “17” 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 17H record. The characters ‘|’ are used to connect each data ID.
For example, “2|88” means Data 2 (Device Name) and Data 88 (SIM Card).
Ignore Event When Geo-fence Initialed
0 - Not ignore. An event is detected when the Geo-fence is initialized, the terminal does not ignore this event and will generate a Rocord 17H.
1 - Ignore. An event is detected when the Geo-fence is initialized, the terminal ignores this event and will not generate a Rocord 17H.
In other words, in mode 0 (Not ignore), when the terminal receives the AT@GEO command to enable Geo-fence detection, and if the current location meets the detection condition, the terminal will immediately generate a Rocord 17H, while mode 1 (Ignore) will not.