Well, I get a different result on 5.5 with your configuration and your sample.
if possible to know where the difference is because I have not changed the configuration of my boxes it is the same for the 5.5 and the 5.6
I don't think I can help you because I think you're not providing full information. I have tested your sample with the official Traccar 5.5, with your config and I get a different result. Maybe you should upload full log and config, so we can see the difference.
is this enough because the log file is very long
It's enough to see that there's the same problem. For example:
2023-03-05 21:49:53 INFO: [T17df9177: atrack < 108.223.128.105] 4050b46d02cb04ae000311119014816c6405001e6405001d6405003e0040b73102297d50015402005ba54e000601004d0000000007d007d0000f012200280f000032f252090f000001e50000090000000000000000000000000000000032313030313a31333034323a31352d303a303a302d303a303a302d303a303a302d303a303a302d303a303a302d303a303a3000004d0000a4ffe804100000000064050031640500316405003e0040b35c02298b42015a02005ba553000701004f0000000007d007d0000e012200281b000032f252091b000001d90000090000000000000000000000000000000032313030313a31333034323a32372d303a303a302d303a303a302d303a303a302d303a303a302d303a303a302d303a303a3000004f000018fff003880000000064050033640500326405003e0040b2f902298cb7015673005ba553000701004e0000000007d007d0000e012200281b000032f252091b000001d80000090000000000000000000000000000000032313030313a31333034323a32372d303a303a302d303a303a302d303a303a302d303a303a302d303a303a302d303a303a3000004f0000bcffc403c40000000064050039640500386405003e0040b06c02299116014b02005ba55400070100500000000007d007d0000c012200281b000032f252091b000001d30000040000000000000000000000000000000032313030313a31333034323a32372d303a303a302d303a303a302d303a303a302d303a303a302d303a303a302d303a303a300000500000d4ffb403fc000000006405003c6405003b6405003e0040aed702299308014573005ba555000701004f0000000007d007d0000e012100281b000032f252091b000001d40000090000000000000000000000000000000032313030313a31333034323a32372d303a303a302d303a303a302d303a303a302d303a303a302d303a303a302d303a303a300000510000a8ffb8049c00000000
2023-03-05 21:49:53 INFO: [T17df9177: atrack > 108.223.128.105] fe02000311119014816c04ae
2023-03-05 21:49:53 INFO: [T17df9177] id: 86555559511148, time: 2023-03-05 21:48:30, lat: 36.27349, lon: 4.24120, speed: 41.6, course: 340.0
2023-03-05 21:49:53 INFO: [T17df9177] id: 86555559511148, time: 1970-01-01 07:06:45, lat: 0.00000, lon: 4.06330, speed: 968.1, course: 35650.0
2023-03-05 21:49:53 INFO: [T17df9177] id: 86555559511148, time: 1970-01-01 07:06:45, lat: 0.00000, lon: 4.06330, speed: 968.1, course: 36023.0
2023-03-05 21:49:53 INFO: [T17df9177] id: 86555559511148, time: 1970-01-01 07:06:45, lat: 0.00000, lon: 4.06330, speed: 968.1, course: 37142.0
2023-03-05 21:49:53 INFO: [T17df9177] id: 86555559511148, time: 1970-01-01 07:06:45, lat: 0.00000, lon: 4.06330, speed: 968.1, course: 37640.0
The difference is that older version just ignores invalid coordinates and the new version throws an error.
maybe that's the problem then?
That's exactly the problem.
will there be an update?
What kind of update are you expecting? You need to figure out the root cause first. It could be that your configuration is incorrect or some parameters that you're using are not supported. Once you figure it out, let us know.
OK thanks
Hello Antoine the problem was in the in the at$form command sent by the box, there were the two parameters %HB and %HC which does not exist in binary mode but which exists that is why in text mode j I had to just edit the command and remove both. Thanks for your help
no nothing after that