GL600 protocol

leonardo2 years ago

I have a mobicon brand container lock and GL600 protocol
it only reflects me on the map in the middle of the sea and does not save routes it only reflects in port 5013

Anton Tananaev2 years ago

Please provide logs and protocol documentation.

leonardo2 years ago

I have the protocol provided by the manufacturer I send it to you through the google link

leonardo2 years ago
leonardo2 years ago

The logs are already in the shared folder

Anton Tananaev2 years ago

I briefly checked the logs and I don't see any server issues. It seems like all messages with GPS data are decoded. If you think something is not decoded correctly, you should be more specific. Provide specific samples from logs.

leonardo2 years ago

I add a sheet with the capture of the padlock, it does not keep any record, I went out for a walk, I check the route and there is no record, it only appears in the middle of the sea.
if you provide me with an ip and port to address it to your server and do the test
there I left a route for linear geofence that gives me an error when loading it

Anton Tananaev2 years ago

If you can't provide specific examples, I won't be able to help.

leonardo2 years ago

This is how the padlock frame arrives with gl600 protocol but traccar detects it on port 5013

2022-07-20 00:26:05 INFO: [T859fce06: h02 < 200.85.80.178]
246020110241011100342007220026030215978307953620990151000000e20a0000000020c05
f3202c47c19002510030868817043604204003602e40201
2022-07-20 00:26:05 INFO: [T859fce06] id: 6020110241, time: 2008-09-03 01:11:00, lat:
22.00434, lon: -160.30513, speed: 362.0, course: 99.0

2022-07-20 00:27:05 INFO: [T859fce06: h02 < 200.85.80.178]
246020110241011100342007220027030216016107953592390368000000e20a0000000020c05
f3202c47c1c002510020868817043604204003602e40202
2022-07-20 00:27:05 INFO: [T859fce06] id: 6020110241, time: 2008-09-03 01:11:00, lat:
22.00451, lon: -160.26847, speed: 359.0, course: 239.0
Anton Tananaev2 years ago

That's definitely not H02 protocol, so port 5013 is the wrong one. Try port JT600.

leonardo2 years ago

I already tried port 5014, it doesn't turn green at all, that's why I sent you the communication protocol for future updates

Anton Tananaev2 years ago

Have you checked logs with port 5014?

leonardo2 years ago

This is how the data arrives through port 5014

2022-07-26 23:50:07  INFO: [Tb936d950: gt06 < 200.85.80.40] 78780a13840604000101652f510d0a
2022-07-26 23:50:07  INFO: [Tb936d950: gt06 > 200.85.80.40] 787805130165d50b0d0a

2022-07-26 23:52:07  INFO: [Tb936d950: gt06 < 200.85.80.40] 78780a13840604000101661dca0d0a
2022-07-26 23:52:07  INFO: [Tb936d950: gt06 > 200.85.80.40] 787805130166e7900d0a

2022-07-26 23:54:07  INFO: [Tb936d950: gt06 < 200.85.80.40] 78780a13840604000101670c430d0a
2022-07-26 23:54:07  INFO: [Tb936d950: gt06 > 200.85.80.40] 787805130167f6190d0a

2022-07-26 23:56:07  INFO: [Tb936d950: gt06 < 200.85.80.40] 78780a1384060400010168f4b40d0a
2022-07-26 23:56:07  INFO: [Tb936d950: gt06 > 200.85.80.40] 7878051301680eee0d0a

2022-07-26 23:58:07  INFO: [Tb936d950: gt06 < 200.85.80.40] 78780a1384060400010169e53d0d0a
2022-07-26 23:58:07  INFO: [Tb936d950: gt06 > 200.85.80.40] 7878051301691f670d0a
Anton Tananaev2 years ago

That's completely different protocol and port. I'm pretty sure it's not even the same device.

leonardo2 years ago

Sorry, none of the data arrives at the port, it is correct, it is another team