FMB920 Protocols

V0.10
Contents
1. FMB920 DATA PROTOCOL......................................................................................................................3
1.1 AVL DATA PACKET.........................................................................................................................................................3
1.2 AVL DATA........................................................................................................................................................................ 3
1.3 PRIORITY............................................................................................................................................................................ 3
1.4 GPS ELEMENT.................................................................................................................................................................. 3
1.5 IO ELEMENT...................................................................................................................................................................... 4
1.6 EXAMPLE..........................................................................................................................................................................13

2. SENDING DATA OVER TCP/IP..............................................................................................................16

3. SENDING DATA OVER UDP/IP............................................................................................................. 17
3.1 UDP CHANNEL PROTOCOL..........................................................................................................................................17
3.2 SENDING AVL DATA USING UDP CHANNEL......................................................................................................... 17

4. SENDING DATA USING SMS................................................................................................................ 20

5. SMS EVENTS............................................................................................................................................ 21
6. CHANGE LOG.......................................................................................................................................... 22

2 / 22
1. FMB920 DATA PROTOCOL

1.1 AVL data packet

Below table represents AVL data packet structure.

4 zeroes Data field Codec ID Number of AVL Data Number of CRC-16
length Data 1 Data 2
4 Bytes 4 Bytes 1 Byte 1 Byte 30- 147 1 Byte 4 bytes
Bytes

Number of data – number of encoded data (number of records).

In FM920 codec ID is constant 08.
Data field length is the length of bytes [codec id, number of data 2].
Number of data 1 should always be equal to number of data 2 byte.
CRC-16 is 4 bytes, but first two are zeroes and last two are CRC-16 calculated for [codec id, number of data 2]
Minimum AVL packet size is 45 bytes (all IO elements disabled).
Maximum AVL packet size for one record is 783 bytes

1.2 AVL Data

Timestamp Priority GPS Element IO Element

8 Bytes 1 Byte 15 Bytes 6-123
Timestamp – difference, in milliseconds, between the current time and midnight, January 1, 1970 UTC.

1.3 Priority

0 Low
1 High
2 Panic

1.4 GPS Element

Longitude Latitude Altitude Angle Satellites Speed

4 Bytes 4 Bytes 2 Bytes 2 Bytes 1 Byte 2 Bytes

3 / 22
 X Longitude1
Y Latitude1
Altitude In meters above sea level1
Angle In degrees, 0 is north, increasing clock-wise 1
Satellites Number of visible satellites1
Speed Speed in km/h. 0x0000 if GPS data is invalid1

Longitude and latitude are integer values built from degrees, minutes, seconds and milliseconds by formula.

d Degrees
m Minutes
s Seconds
ms Milliseconds
p Precision (10000000)

If longitude is in west or latitude in south, multiply result by –1. To determine if the coordinate is negative,
convert it to binary format and check the very first bit. If it is 0, coordinate is positive, if it is 1, coordinate is
negative.
Example:
Received value: 20 9c ca 80
Converted to BIN: 00100000 10011100 11001010 10000000 first bit is 0, which means coordinate is positive
Convered to DEC: 547146368
For more information see two‘s compliment arithmetics.

1.5 IO element
N1 of One Byte IO

N8 of Eight Bytes
N4 of Four Bytes
N2 of Two Bytes
N1’th IO Value

N2’th IO Value

N4’th IO Value

N8’th IO Value
N of Total IO

1’st IO Value

1’st IO Value

1’st IO Value

1’st IO Value
N1’th IO ID

N2’th IO ID

N4’th IO ID

N8’th IO ID
Event IO ID

1’st IO ID

1’st IO ID

1’st IO ID

1’st IO ID
IO

IO

IO
…

…
2 Bytes

2 Bytes

4 Bytes

4 Bytes

8 Bytes

8 Bytes
1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

1 Byte

Event IO ID – if data is acquired on event – this field defines which IO property has changed and generated
an event. If data cause is not event – the value is 0.

1
If record is without valid coordinates – (there were no GPS fix in the moment of data acquisition) – Longitude, Latitude and Altitude
values are last valid fix, and Angle, Satellites and Speed are 0.

4 / 22
 N total number of properties coming with record (N=N1+N2+N4+N8)
N1 number of properties, which length is 1 byte
N2 number of properties, which length is 2 bytes
N4 number of properties, which length is 4 bytes
N8 number of properties, which length is 8 bytes
Permanent I/O elements
(are always sent (with every record) to server if enabled)
Property ID
in AVL Property Name Bytes Description
packet
Logic: 0 / 1
239 Ignition 1
* Depends on Ignition source
Logic: 0 / 1
240 Movement 1
* Depends on Movement source
Value in scale 0 – 5
0 – Home On Stop
1 – Home On Moving
80 Data Mode 1 2 – Roaming On Stop
3 – Roaming On Moving
4- Unknown On Stop
5 – Unknown On Moving
21 GSM Signal 1 Value in scale 1 – 5
200 Sleep Mode 1 0 – No Sleep; 1 – GPS Sleep; 2 – Deep Sleep; 3- Online Sleep
0 - OFF
1 - ON with fix
69 GNSS Status 1
2 - ON without fix
3 - In sleep state
181 GNSS PDOP 2 Probability * 10; 0-500
182 GNSS HDOP 2 Probability * 10; 0-500
66 External Voltage 2 Voltage: mV, 0 – 30 V
24 Speed 2 Value in km/h, 0 – xxx km/h
205 GSM Cell ID 2 GSM base station ID
206 GSM Area Code 2 Location Area code (LAC), it depends on GSM operator. It
provides unique number which assigned to a set of base GSM
stations. Max value: 65536
67 Battery Voltage 2 Voltage: mV
68 Battery Current 2 Current: mA
241 Active GSM Operator 4 Currently used GSM Operator code
199 Trip Odometer 4 Trip Odometer Value in meters
16 Total Odometer 4 Total Odometer Value in meters
1 Digital Input 1 1 Logic: 0 / 1
9 Analog input 1 2 Voltage: mV, 0 – 30 V
179 Digital Output 1 1 Logic: 0 / 1
12 Fuel Used GPS 4 Fuel Used in mili Liters
13 Fuel Rate GPS 2 Average Fuel use in (Litersx100) /100km
17 Axis X 2 X axis: value mG range [-8000; 8000]
18 Axis Y 2 Y axis: value mG range [-8000; 8000]
19 Axis Z 2 Z axis: value mG range [-8000; 8000]
Value of SIM ICCID, MSB
*11 ICCID1 8
(Example Below)
Value of SIM ICCID, LSB
*14 ICCID2 8
(Example Below)

5 / 22
 Permanent I/O elements
(are always sent (with every record) to server if enabled)
Property ID
in AVL Property Name Bytes Description
packet
10 SD Status 1 0 – not present, 1 – present
Average amount of events on some distance. Min – 0, Max –
15 Eco Score 2
65536. Multiplier – 0.01
MAC address of NMEA receiver device connected via
238 User ID 8
Bluetooth
Multiplier – 0.1. Degrees ( °C ), -40 - +125; Error codes:
4000 - abnormal sensor state
25 BLE Temperature #1 2
3000 - sensor not found
2000 - failed sensor data parsing
Multiplier – 0.1. Degrees ( °C ), -40 - +125; Error codes:
4000 - abnormal sensor state
26 BLE Temperature #2 2
3000 - sensor not found
2000 - failed sensor data parsing
Multiplier – 0.1. Degrees ( °C ), -40 - +125; Error codes:
4000 - abnormal sensor state
27 BLE Temperature #3 2
3000 - sensor not found
2000 - failed sensor data parsing
Multiplier – 0.1. Degrees ( °C ), -40 - +125; Error codes:
4000 - abnormal sensor state
28 BLE Temperature #4 2
3000 - sensor not found
2000 - failed sensor data parsing
29 BLE Battery voltage #1 1 Battery voltage in % of sensor #1
20 BLE Battery voltage #2 1 Battery voltage in % of sensor #2
22 BLE Battery voltage #3 1 Battery voltage in % of sensor #3
23 BLE Battery voltage #4 1 Battery voltage in % of sensor #4
86 BLE Humidity #1 2 Multiplier 0.1. %RH
104 BLE Humidity #2 2 Multiplier 0.1. %RH
106 BLE Humidity #3 2 Multiplier 0.1. %RH
108 BLE Humidity #4 2 Multiplier 0.1. %RH
There are 8 IO elements of 1 byte size.
Also 13 IO elements of 2 byte size.
Also 4 IO elements of 4 byte size.
And 0 IO elements of 8 byte size.

*ICCID Full Value Calculation, Example

1) Calculate ID:14 lenght as string
2) If lenght < 10, then add_zeros = 10 – length
3) Else no zeros must be added
4) Concat strings to get final value. Final value = String(ID 11) +
String(add_zeros) + String(ID 14).

6 / 22
ID:11 Len as ID:14 Len as
Full Value Full Value Len
string string

9 9 String(ID 11) + „0“ + String(ID 14) 19

9 10 String(ID 11) + String(ID 14) 19

10 10 String(ID 11) + String(ID 14) 20

9 11 String(ID 11) + String(ID 14) 20

11 8 String(ID 11) + „00“ + String(ID 14) 21

11 10 String(ID 11) + String(ID 14) 21

12 10 String(ID 11) + String(ID 14) 22

12 9 String(ID 11) + „0“ + String(ID 14) 22

Eventual I/O elements

(Send if corresponding event had happen)
Property ID
in AVL Property Name Bytes Description
packet
Logic: 0 / 1
155 Geofence zone 1 1
0 – Exit Event; 1 – Enter Event;
Logic: 0 / 1
156 Geofence zone 2 1
0 – Exit Event; 1 – Enter Event;
Logic: 0 / 1
157 Geofence zone 3 1
0 – Exit Event; 1 – Enter Event;
Logic: 0 / 1
158 Geofence zone 4 1
0 – Exit Event; 1 – Enter Event;
Logic: 0 / 1
159 Geofence zone 5 1
0 – Exit Event; 1 – Enter Event;
0 – target left zone
1 – target entered zone
61 Geofence zone 6 1 2 – over speeding end
3 – over speeding start

0 – target left zone

1 – target entered zone
62 Geofence zone 7 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
63 Geofence zone 8 1
2 – over speeding end
3 – over speeding start
0 – target left zone
64 Geofence zone 9 1
1 – target entered zone

7 / 22
 Eventual I/O elements
(Send if corresponding event had happen)
Property ID
in AVL Property Name Bytes Description
packet
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
65 Geofence zone 10 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
70 Geofence zone 11 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
88 Geofence zone 12 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
91 Geofence zone 13 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
92 Geofence zone 14 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
93 Geofence zone 15 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
94 Geofence zone 16 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
95 Geofence zone 17 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
96 Geofence zone 18 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
97 Geofence zone 19 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
98 Geofence zone 20 1
2 – over speeding end
3 – over speeding start
0 – target left zone
99 Geofence zone 21 1 1 – target entered zone
2 – over speeding end

8 / 22
 Eventual I/O elements
(Send if corresponding event had happen)
Property ID
in AVL Property Name Bytes Description
packet
3 – over speeding start
0 – target left zone
1 – target entered zone
153 Geofence zone 22 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
154 Geofence zone 23 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
190 Geofence zone 24 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
191 Geofence zone 25 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
192 Geofence zone 26 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
193 Geofence zone 27 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
194 Geofence zone 28 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
195 Geofence zone 29 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
196 Geofence zone 30 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
197 Geofence zone 31 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
198 Geofence zone 32 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
208 Geofence zone 33 1
2 – over speeding end
3 – over speeding start

9 / 22
 Eventual I/O elements
(Send if corresponding event had happen)
Property ID
in AVL Property Name Bytes Description
packet
0 – target left zone
1 – target entered zone
209 Geofence zone 34 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
216 Geofence zone 35 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
217 Geofence zone 36 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
218 Geofence zone 37 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
219 Geofence zone 38 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
220 Geofence zone 39 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
221 Geofence zone 40 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
222 Geofence zone 41 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
223 Geofence zone 42 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
224 Geofence zone 43 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
225 Geofence zone 44 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
226 Geofence zone 45 1
2 – over speeding end
3 – over speeding start
227 Geofence zone 46 1 0 – target left zone

10 / 22
 Eventual I/O elements
(Send if corresponding event had happen)
Property ID
in AVL Property Name Bytes Description
packet
1 – target entered zone
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
228 Geofence zone 47 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
229 Geofence zone 48 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
230 Geofence zone 49 1
2 – over speeding end
3 – over speeding start
0 – target left zone
1 – target entered zone
231 Geofence zone 50 1
2 – over speeding end
3 – over speeding start
Logic: 0 / 1
175 Auto Geofence 1
0 – Exit Event; 1 – Enter Event;
Logic: 0 / 1
250 Trip 1
0 – Trip Ended; 1 – Trip Started;
255 Over speeding 1 Value km/h that generated event
251 Idling 1 Logic: 0 / 1
0- Idling ended event; 1 – Idling started event;
253 Green Driving Type 1 Possible Values: [1/2/3]
1 – Acceleration
2 – Braking
3 – Cornering
254 Green Driving Value 1 Depending on eco driving type: if harsh acceleration, braking
and cornering – g*10
246 Towing 1 1 – Send Towing detected

252 Unplug 1 1 – Send when unplug event happens

1 – Crash Detected
247 Crash Detection 1 2 – Crash Trace Record, (begins 5 sec before crash, and ends 5
sec after crash */
1 – Jamming Detected
249 Jamming 1
0 – Jamming Ended

11 / 22
 Permanent I/O elements
(Send if ask to get with OBDII dongle)
Property ID
in AVL Property Name Bytes Description
packet
30 „Number of DTC“ 1
„Calculated engine load 1 %
31
value“
„Engine coolant 1 C
32
temperature“
33 „Short term fuel trim 1“ 1 %
34 „Fuel pressure“ 2 kPa
„Intake manifold 1 kPa
35
absolute pressure“
36 „Engine RPM“ 2 rpm
37 „Vehicle speed“ 1 km/h
38 „Timing advance“ 1 O
39 „Intake air temperature“ 1 C
40 „MAF air flow rate“ 2 g/sec, *0.01
41 „Throttle position“ 1 %
„Run time since engine 2 s
42
start“
„Distance traveled MIL 2 Km
43
on“
„Relative fuel rail 2 kPa, *0.1
44
pressure“
„Direct fuel rail 2 kPa, *0.1
45
pressure“
46 „Commanded EGR“ 1 %
47 „EGR error“ 1 %
48 „Fuel level“ 1 %
„Distance traveled since 2 Km
49
codes cleared“
50 „Barometric pressure“ 1 kPa
„Control module 2 mV
51
voltage“
52 „Absolute load value“ 2 %
„Ambient air 1 C
53
temperature“
54 Time run with MIL on 2 Min
„Time since trouble 2 Min
55
codes cleared“
„Absolute fuel rail 2 kPa, *10
56
pressure“
„Hybrid battery pack 1 %
57
remaining life“
„Engine oil 1 C
58
temperature“
59 „Fuel injection timing“ 2 O, *0.01
60 „Engine fuel rate“ 2 L/h, *100

12 / 22
 To receive CAN data, send if ask to get with OBDII dongle. FMB9 module CAN data is not
reading.

1.6 Example

Received data:
000000000000008c08010000013feb55ff74000f0ea850209a690000940000120000001e0
9010002000300040016014703f0001504c8000c0900730a00460b00501300464306d74400
00b5000bb60007422e9f180000cd0386ce000107c700000000f10000601a4600000134480
0000bb84900000bb84a00000bb84c00000000024e0000000000000000cf00000000000000
000100003fca
In total 152 Bytes.

00000000 4 zeroes, 4 bytes

0000008c data length, 4 bytes
08 – Codec ID
0- Number of Data (1 record)
1’st record data

0000013feb55ff74 – Timestamp in milliseconds (1374042849140)

GMT: Wed, 17 Jul 2013 06:34:09 GMT
00 – Priority

GPS Element

0f0ea850 – Longitude 252618832 = 25,2618832º N

209a6900 – Latitude 546990336 = 54,6990336 º E
0094 – Altitude 148 meters
0 – Angle 214º
12 – 12 Visible sattelites
0 – 0 km/h speed

IO Element

00 – IO element ID of Event generated (in this case when 00 –

data generated not on event)
1e – 30 IO elements in record (total)
09 – 9 IO elements, which length is 1 Byte
0 – IO element ID = 01
0 – IO element’s value = 0
02 – IO element ID = 02
0 – IO element’s value = 0
03 – IO element ID = 03
0 – IO element’s value = 0
04 – IO element ID = 04
0 – IO element’s value = 0
16 – IO element ID = 22 (dec)

13 / 22
 0 – IO element’s value = 1
47 – IO element ID = 71 (dec)
03 – IO element’s value = 3
F0 – IO element ID = 240 (dec)
0 – IO element’s value = 0
15 – IO element ID = 21 (dec)
04 – IO element’s value = 0
C8 – IO element ID = 200 (dec)
0 – IO element’s value = 0

0C – 12 IO elements, which value length is 2 Bytes

09 – IO element ID = 9 (dec)
0073 – IO element’s value
0a – IO element ID = 10 (dec)
0046 – IO element’s value
0b – IO element ID = 11 (dec)
0050 – IO element’s value
13 – IO element ID = 19 (dec)
0046 – IO element’s value
43 – IO element ID = 67 (dec)
06d7 – IO element’s value
44 – IO element ID = 68 (dec)
0 – IO element’s value
B5 – IO element ID = 181 (dec)
000b – IO element’s value
B6 – IO element ID = 182 (dec)
0007 – IO element’s value
42 – IO element ID = 66 (dec)
2e9f – IO element’s value
18 – IO element ID = 24 (dec)
0 – IO element’s value
cd – IO element ID = 205 (dec)
0386 – IO element’s value
CE – IO element ID = 206 (dec)
0 – IO element’s value

07 – 7 IO elements, which value length is 4 Bytes

C7 – IO element ID = 199 (dec)

0 – IO element’s value
f1 – IO element ID = 241 (dec)
0000601a – IO element’s value
46 – IO element ID = 70 (dec)
00000134 – IO element’s value
48 – IO element ID = 72 (dec)
00000bb8 – IO element’s value
49 – IO element ID = 73 (dec)
00000bb8 – IO element’s value
4a – IO element ID = 74 (dec)

14 / 22
00000bb8 – IO element’s value
4c – IO element ID = 76 (dec)
0 – IO element’s value

15 / 22
 02 – 2 IO elements, which value length is 8 Bytes
4e – IO element ID = 78 (dec)
0 – IO element’s value
cf – IO element ID = 207 (dec)
0 – IO element’s value

0 – Number of Data (1 record)

00003fca - CRC-16, 4 Bytes (first 2 are always zeroes)

2. SENDING DATA OVER TCP/IP

First when module connects to server, module sends its IMEI. First comes short identifying number of bytes
written and then goes IMEI as text (bytes).
For example IMEI 356307042441013 would be sent as 000f333536333037303432343431303133
First two bytes denote IMEI length. In this case 000F means, that imei is 15 bytes long.
After receiving IMEI, server should determine if it would accept data from this module. If yes server will reply
to module 01 if not 00. Note that confirmation should be sent as binary packet. I.e. 1 byte 0x01 or 0x00.
Then module starts to send first AVL data packet. After server receives packet and parses it, server must
report to module number of data received as integer (four bytes).
If sent data number and reported by server doesn’t match module resends sent data.

Example:
Module connects to server and sends IMEI:
000f333536333037303432343431303133
Server accepts the module:
01
Module sends data packet:
AVL data packet header AVL data array CRC
Four zero bytes, CodecId – 08, CRC of ‘AVL data array’
‘AVL data array’ length – 254 NumberOfData – 2.
(Encoded using continuous bit
stream. Last byte padded to align
to byte boundary)
00000000000000FE 0802...(data elements)...02 00008612
Server acknowledges data reception (2 data elements):
00000002

16 / 22
 3. SENDING DATA OVER UDP/IP

3.1 UDP channel protocol

UDP channel is a transport layer protocol above UDP/IP to add reliability to plain UDP/IP using
acknowledgment packets. The packet structure is as follows:

UDP datagram
UDP Packet length 2 bytes Packet length (excluding this field) in big
channel endian byte order
packet x N
Packet Id 2 bytes Packet id unique for this channel

Packet Type 1 byte Type of this packet

Packet payload m bytes Data payload

Packet Type
0 Data packet requiring acknowledgment
1 Data packet NOT requiring acknowledgment
2 Acknowledgment packet

Acknowledgment packet should have the same packet id as acknowledged data packet and empty data payload.
Acknowledgement should be sent in binary format.

Acknowledgment packet
Packet length 2 bytes 0x0003
Packet id 2 bytes same as in acknowledged packet
Packet type 1 byte 0x02

3.2 Sending AVL data using UDP channel

AVL data are sent encapsulated in UDP channel packets (Data payload field).

AVL data encapsulated in UDP channel packet

AVL packet id (1 byte) Module IMEI AVL data array

AVL packet id (1 byte) – id identifying this AVL packet

Module IMEI – IMEI of a sending module encoded the same as with TCP

17 / 22
 AVL data array – array of encoded AVL data

Server response to AVL data packet

AVL packet id (1 byte) Number of accepted AVL elements (1 byte)

AVL packet id (1 byte) – id of received AVL data packet

Number of AVL data elements accepted (1 byte) – number of AVL data array entries from the beginning of array,
which were accepted by the server.

Scenario:
Module sends UDP channel packet with encapsulated AVL data packet (Packet type=1 or 0). If packet type is
0, server should respond with valid UDP channel acknowledgment packet. Since server should respond to the
AVL data packet, UDP channel acknowledgment is not necessary in this scenario, so Packet type=1 is
recommended.
Server sends UDP channel packet with encapsulated response (Packet type=1 – this packet should not require
acknowledgment)
Module validates AVL packet id and Number of accepted AVL elements. If server response with valid AVL packet
id is not received within configured timeout, module can retry sending.

Example:
Module sends the data:

UDP channel header AVL packet header AVL data array

Len – 253, AVL packet id – 0xDD, CodecId – 08,
Id – 0xCAFE, IMEI – 1234567890123456 NumberOfData – 2.
Packet type – 01 (Encoded using continuous bit
(without ACK) stream)
00FDCAFE01 DD000F3133343536373839303132333435 0802…(data elements)…02

Server must respond with acknowledgment:

UDP channel header AVL packet acknowledgment

Len – 5, AVL packet id – 0xDD,
Id – 0xABCD, NumberOfAcceptedData – 2
Packet type – 01 (without ACK)
0005ABCD01 DD02

18 / 22
Another example, with all IO id’s enabled
Server received data:
00a1cafe011b000f33353633303730343234343130313308010000013febdd19c8000f0e9
ff0209a718000690000120000001e09010002000300040016014703f0001504c8000c0900
910a00440b004d130044431555440000b5000bb60005422e9b180000cd0386ce000107c70
0000000f10000601a460000013c4800000bb84900000bb84a00000bb84c00000000024e00
00000000000000cf000000000000000001

Data length: 00a1 or 161 Bytes (not counting the first 2 data length
bytes)
Packet identification: 0xCAFE 2 bytes
Packet type: 01
Packet id: 1b
Imei length: 000f
Actual imei: 333536333037303432343431303133
Codec id: 08
Number of data: 01
Timestamp: 0000013febdd19c8
Priority: 00
GPS data: 0f0e9ff0209a718000690000120000

UDP protocol is the same as TCP except message header is 7 bytes, which consist of: data length, packet
identification, packet type and packet id.
Then goes imei length and imei itself.
And after that goes AVL data.
And at the very end number of data byte. There is no CRC in UDP.

19 / 22
 4. SENDING DATA USING SMS

AVL data or events can be sent encapsulated in binary SMS. TP-DCS field of these SMS should indicate that
message contains 8-bit data (for example: TP-DCS can be 0x04).

SM data (TP-UD)
AVL data array IMEI: 8 bytes

AVL data array – array of encoded AVL data

IMEI – IMEI of sending module encoded as a big endian 8-byte long number.

20 / 22
 5. SMS EVENTS
When Configured to generate SMS event user will get this SMS upon event

<Year/Month/Day> <Hour:Minute:Second> Lon:<longitude> Lat:<latitude> Q:<HDOP> <SMS Text>

Val:<Event Value>

Example:
2016/04/11 12:00:00 Lon:51.12258 Lat: 25.7461 Q:0.6 Digital Input 1 Val:1

21 / 22
6. CHANGE LOG
New
Nr. Date version Comments
number
1 2016.10.02 0.0.1 First release
2 2016.11.15 0.0.3 Minor changes
3 2017.01.24 0.0.4 OBD AVL ID
4 2017.03.30 0.0.5 Added ICCID and SD status.
5 2017.04.24 0.0.6 GPS AVG Fuel Use in 100km. Multiplier (x100)
info added
CCID ID is put to two IO elements (AVL ID:11
and AVL ID:14), parsing instructios added
6 2017.06.16 0.0.7 Updated IO GNSS status values
7 2017.07.03 0.0.8 Description added: ICCID Full Value Calculation
8 2017.07.25 0.0.9 Updated OBD fuel rate param.
9 2018.02.21 0.0.10 Added new I\O elements

22 / 22