Xexun protocol is updated:
identification changed for those xexun devices that send messages in the following format:
(027044861111BP05355227044861111190926A0611.4496S10639.5890E000.0073950000.0000000000L00000000)

Now such devices are identified by serial number 027044861111, not by IMEI 3552270448611111 as before.
This is likely TK103 and TK110 devices. But it's not for sure.

The other xexun devices that send messages in one of the following formats are identified by IMEI as usual:
imei:864895030551111,tracker,191003074503,,F,044503.00,A,4700.08753,N,02853.79387,E,4.985,327.55;
190926151811,+31711117111,GPRMC,151811.775,A,5215.5816,N,00508.7693,E,28.31,83.20,260919,,,A*6D,F,SHAKE, imei:354778030121111,03,1.3,F:4.14V,1,143,5451,204,08,0D2A,B6E5\n\r

This is likely TK102, TK102-2 and TK103-2, but it's not for sure either.

So, if you are in doubt what to choose as ident when creating a device, you can:

• try to connect a device to xexun channel and see how it is identified
• or use proxy channel and handy hex viewer to see raw traffic from device

we've added a logic to correctly parse wrong timestamps caused by GPS Rollover problem that was detected for TK110 device type
This problem is caused because GPS date is defined by 10-bit week number which results to max 1024 number. So when this number overflows to 0 then tracker (with firmware algorithms not covering this) starts to send time as it is in the beginning of the 1024 week period which is August 21, 1999.

Time Zone setting is added for Xexun TK102-2 device, Actions tab.

Setup correct Time Zone value (same as configured in tracker) and hit 'Send over connection' button. After that server will apply this value in timestamp parameter parsing.

Some devices require password to change time zone. Please, ensure that correct 'SMS Password' is specified in device configuration.

Time Zone setting is also added for Xexun TK103-2 device.
The details are in the post above.

Xexun protocol is updated.
Add parsing of message content of BP00 packet Handshake signal message.
The following parameters may be registered for this packet (depending on the actual packet content):

• device.imei
• battery.level, %
• battry.voltage, volts

Applicable for Xexun TK102

YuryAheichyk changes have been applied, the can.dtc parameter type changed to array

The OBDII DTC codes registration is planned to be changed. Currently, error codes are stored in the can.dtc parameter as an array of strings. To unify with other diagnostic protocol types, errors will be stored as an array of objects.

The changes will be applied in 2 weeks, on May 8, 2025.

For reference, two additional parameters have been added:

• can.dtc.strings - contains errors in the current format (will be removed in 1 month, on May 24, 2025)
• can.dtc.objects - contains errors in the new format (will be removed in 2 weeks, on May 8, 2025)

can.dtc.strings example:
["P0020","U0001"]
can.dtc.objects example:
[{"standard":"OBDII","code":"P0020"},{"standard":"OBDII","code":"U001"}]