JT808 Chinese Protocol

Here attached protocol documentation for Chinese device called JT808.

JT808 Vehicle Tracking Protocol

I have tried connecting with port 5015 (huabao), but there is an error in the log as follows:

INFO: [Tbd15b4aa] error - readerIndex(113) + length(126) exceeds writerIndex(113): UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 113, widx: 113, cap: 113) - IndexOutOfBoundsException (... < HuabaoProtocolDecoder:691 < *:237 < ExtendedObjectDecoder:75 < ... < WrapperContext:102 < ...)

The following is one of the location information data sent to the server:

7e02000062010000809750003f00000000000c0001000000000000000000000000000023111314532201040000000002020000030200001404000000051504000000021604000000001702000218030000002504000000002b040000000030011d31010051020000ee020031f30100227e

Looks like it's not compatible with the current implementation. They probably changes something and decoder needs to be updated to support the change.

Hello Antón, I have a similar problem. Can the protocol code be modified? If so, could you give me a guide on how to do it please

I already explained what needs to be done. If you have the skills, you should be able to do it. Please send us a pull request if you manage to update the protocol.

@MarcosZreal, were you able to update the protocol?

I got today, this updated JT808 protocol from gps tracker factory from China. I am assuming that is the latest version. How can I upload here?

Looks like I have a similar problem. Here is my forum post on it. https://www.traccar.org/forums/topic/huabao-incorrect-battery-level/

Has anyone managed to modify the protocol?

Are you also getting the same error?

I get a similar error. Happens when the device sends a large packet / data.

error - Adjusted frame length exceeds 512: 12853 - discarded - TooLongFrameException (... < WrapperInboundHandler:57 < ... < StandardLoggingHandler:51 < ... < NetworkMessageHandler:37 < ...)

That's a very different error.

Hi guys, JT808 Chinese Protocol is supported in latest release? it is not mentioned in devices protocol list

https://www.traccar.org/clones/