Evoo Protocol gt06

Hi,
The ignition status shows and then disappears, shows and then disappears and is not constant. But when it shows, it shows the correct status.

Line 01: is correct? I couldn't convert it to text.
78780512004c2acc0d0a
Line 02: is correct? I couldn't convert it to text.
78781f121803170d3512c60025a2c50532992000182e02d40298f2004c0b004da0e10d0a
Line 03:
id: 0010102233, time: 2024-03-23 11:18:48, lat: -1.37028, lon: -48.44563, course: 350.0

Protocol gt06
https://drive.google.com/file/d/1EvlZOKZVmzQZn1MlwW3dR1LJvDiYX23k/view?usp=sharing

Image 01: no status ignition
https://drive.google.com/file/d/16SdB3PatIR9ZhPrQ8ng8Mekc3RjS5A6Y/view?usp=sharing

Image 02: ignition on
https://drive.google.com/file/d/19jJ2zBhw1Z69hoVFjGySLgmNlgGFNWJW/view?usp=sharing

Image 02: ignition off
https://drive.google.com/file/d/10kc_qadt-XZ-uamM7p3Gn7jHZTCtCvcO/view?usp=sharing

It's pretty common for GT06-based protocols because not all the data is reported with every message.

Anton,

But do you think the device doesn't send all the data including the ignition status or did I need to adjust the traccar source code?

Have you tried converting?

78781f121803170d3512c60025a2c50532992000182e02d40298f2004c0b004da0e10d0a

I haven't tried, but you can try and let us know.

ASCII to TEXT
input: 78781f121803170d3512c60025a2c50532992000182e02d40298f2004c0b004da0e10d0a
output: [some binary data]

HEX to TEXT
input: 78781f121803170d3512c60025a2c50532992000182e02d40298f2004c0b004da0e10d0a
output: [some binary data]

Why would you try to convert it into text when it's a binary protocol? No, you have to take the protocol documentation and break down the binary byte by byte.