Driver Identifier Issue

Hello everyone,

I'm encountering an issue where driver identifiers that start with a letter (e.g., AB0010006584E901) are not being detected by the system, although they appear in the logs. On the other hand, identifiers that start with a number are recognized and stored in the database.The source code has been customized, but we haven't made any changes related to driver identifiers.

I'm using Teltonika devices, and I suspect the issue lies in this part of the code:

~/src/main/java/org/traccar/protocol/TeltonikaProtocolDecoder.java

        register(78, null, (p, b) -> {
            long driverUniqueId = b.readLongLE();
            if (driverUniqueId > 0) {
                p.set(Position.KEY_DRIVER_UNIQUE_ID, String.format("%016X", driverUniqueId));
            }
        });

Has anyone encountered a similar issue, and what would be the correct approach to resolve this?

Do you have a HEX sample?

Hi Anton,

Here it is:

2024-09-23 12:27:57 INFO: [T135927c0: teltonika < xx.x.xx.xxx] 000000000000012e8e04000001921e012ed80122e6740d0e0feaf80036008e0f0000004e0009000600ef0100f00000150500010100b40000716200020042326c0018000000000001004e00000000000000000000000001921e0123340122e6740d0e0feaf80036008e0e000000ef0009000600ef0100f00000150500010100b4000071620002004231900018000000000001004e01b632b0000500e10000000001921e01232a0122e6740d0e0feaf80036008e0e000000f8000a000700ef0100f00000150500010100b40000716200f8010002004231940018000000000001004e01b632b0000500e10000000001921e011f380122e6740d0e0feaf80036008e100000004e0009000600ef0000f00000150500010100b4010071620002004231f70018000000000001004e01b632b0000500e1000004000067ec

But not show in traccar application. Attached.

And what are the expected values?

From Attached image in previous post that 3 records and in reality it must be 4 records.

1. First records on 22/09/2024 (show)
2. Second record must be on 23/09/2024 with RFID in Hexa shared in previous post (Not Show)
3. Third and Fourth records as it show on 24/09/2024.

expected second record to be available in traccar.

This is not the result I get from the sample.

Hi Anton,

But that what I got. Do you have solution for that?

Are you sure you're using the latest official release without any code modifications?

Hi

I used old one and customized.

In that case not sure I can help. Try the latest official release.

i face with the same issue anton, it shows "driverUniqueId" on parameter when connecting iButton key but the parameter not showing when changing to another iButton Key. note that it shows "event:78" on both keys.