OBD Tracker Not Coming Online with Traccar Server 6.6 osmand hex protocol
The only protocol, that matches your hex pattern is the huasheng protocol on port 5111.
Eventually there is an sms command, that clears the trackers cache. Some devices makes trouble, if you change the server with unsent positions in cache...
Thanks a lot for your reply!
I was wondering—if I try with a brand-new device that hasn’t been configured before, would that help prove your point?
It would be great if you could also guide me on the SMS command to clear the cache, or suggest any AT+ command I can use from the serial terminal.
Best regards,
Ahmed
You can try a new device with your traccar server. I dont have the sms commands for your tracker...
If the original company modified the protocol, the chances are minimal to get the tracker working with traccar.
Read the Thread https://www.traccar.org/forums/topic/unsupported-commands/, there is the documentation for the original Huasheng device...
you can try
clear
to clear the device cache...
Thank you, Sebastian, for your sincere help. What I've noticed is that my original ODB settings were using port 7000. The link you provided me with has an OBD emulator with an OBD testing tool. I configured the tool to connect to my server using port 5111, and the emulated device showed up on my server map. But when I changed the port to 7000, it did not. From what I understood, each protocol is bound to a specific port. For example, Huasheng uses port 5111, and Osmand uses port 5055, etc.
My question is: if the device must use port 7000, which is supposed to be a XXXX protocol, then will the server not recognize the device due to a lack of support for this protocol?
Port 7000 isnt used by traccar... so it cant work.
Is there any known protocol use port 7000 ?
Each software vendor has different port numbers, so 7000 doesn't really tell anything.
The protocol docs are the million-dollar question, aren't they? Sadly, I don't have them. But here's what I've figured out with my CW-601G:
The firmware version is OBD_WM_V1.9.6_YMX (I decoded the HEX to get this).
I configure it by sending SMS commands or via a serial connection to set the APN and server details.
The big breakthrough for me was the port. It refused to come online on port 5111, but connected when I switched my device to connect on port 5015 but the device did not show on the map
thank you for your help
Warm regards,
Ahmed