OBD Tracker Not Coming Online with Traccar Server 6.6 osmand hex protocol
It's definitely not the OsmAnd protocol.
You can try following this guide:
Hello Anton,
Thank you for getting back to me so quickly.
I have reviewed the guide and proceeded to test connections on the ports typically associated with the device's protocol:
gps103 on port 5001
hk103 on port 5002
totem on port 5007
gt06 on port 5023
Unfortunately, I have not had any success with these. The log file consistently captures the same raw data packet in hexadecimal (see below).
Log Output:
c0010c00530002000000000015020015a0014f42445f574d5f56312e392e365f594d580013a0043836343034393032313633353536320013a0a83630323033303831343438373333330005a087000006a0a10477c0
I would be grateful for your guidance on the next steps to troubleshoot this. Is there a way to identify the correct protocol from this hex code, or should I be investigating a different set of ports?
Thank you again for your help.
It doesn't seem like you actually read the link I provided.
Hi,
I did read the link, now I'm in a better position, the port 5015 works with Unknown device, according to "2 Check if HEX messages are decoded"
If HEX messages are followed by Unknown device warning, then it means that you haven't registered device on the server. To fix this issue, add device with unique id you see in the log through web console.
I added 000200000000 as ID, now the device is online but no locating update.
I'm getting a series of device connected disconnected
2025-09-07 17:05:38 INFO: [Tec96496f] connected
2025-09-07 17:05:39 INFO: [Tec96496f: huabao < 156.187.39.13] c0010c00530002000000000065020015a0014f42445f574d5f56312e392e365f594d580013a0043836343034393032313633353536320013a0a8363032303330>
2025-09-07 17:05:39 INFO: Event id: 000200000000, time: 2025-09-07 17:05:39, type: deviceOnline, notifications: 0
2025-09-07 17:06:05 INFO: [Tec96496f: huabao < 156.187.39.13] c0010c000c0048000000000066c0
2025-09-07 17:06:33 INFO: [Tec96496f] disconnected
2025-09-07 17:06:33 INFO: Event id: 000200000000, time: 2025-09-07 17:06:33, type: deviceOffline, notifications: 0
2025-09-07 17:06:40 INFO: [T5ce4e278] connected
2025-09-07 17:06:41 INFO: [T5ce4e278: huabao < 156.187.39.13] c0010c00530002000000000067020015a0014f42445f574d5f56312e392e365f594d580013a0043836343034393032313633353536320013a0a8363032303330>
2025-09-07 17:06:41 INFO: Event id: 000200000000, time: 2025-09-07 17:06:41, type: deviceOnline, notifications: 0
2025-09-07 17:08:41 INFO: [T5ce4e278] timed out
2025-09-07 17:08:41 INFO: [T5ce4e278] disconnected
Thank you for your help and support
It's almost certainly not Huabao.
Obviously if the device id is incorrect, it was not decoded correctly, so it's probably not the right protocol.
But the main thing you're missing is checking HEX against test cases.
I've attempted to grasp how to verify HEX using the test cases, but I'm struggling to figure it out. I'm not a programmer, but I can follow the logic if you provide a hint to guide me.
What if I experimented with all the other protocol ports—would that be helpful?
Hello Ahmed,
try huasheng protocol on port 5111
Greetings
Sebastian
Hello Sebastian,
Thank you again for your efforts. I understand these issues can be complex.
A little about me: I'm 65 with 41 years in IT and Telco (though not on the programming side). I'm setting up your wonderful Traccar server to help keep my family and loved ones safe, so I truly appreciate your support.
Please feel free to provide high-level guidance or point me in the right direction—I'm happy to do the legwork to save your valuable time.
Any next steps you can suggest would be greatly appreciated.
Warm regards,
2025-09-07 22:36:26 INFO: [Tf4f15918] connected
2025-09-07 22:36:28 INFO: [Tf4f15918: huasheng < 105.88.22.137] c0010c0053000200000000004c020015a0014f42445f574d5f56312e392e365f594d580013a0043836343034393032313633353536320013a0a83630323033303831343438373333330005a087000006a0a10488c0
2025-09-07 22:36:28 INFO: [Tf4f15918: huasheng > 105.88.22.137] c00100000c000300000000004cc0
2025-09-07 22:36:29 INFO: [Tf4f15918: huasheng < 105.88.22.137] c0010c0032000400000000004d020015a0014f42445f574d5f56312e392e365f594d580007a0335049440009a0344641554c54c0
2025-09-07 22:36:30 INFO: [Tf4f15918: huasheng < 105.88.22.137] c0010c004b000000000000004e0000000000000000303030303030000000000000000000000000000000000006a0a500000006a0a600000015a0b4ff00ff00000000000000046f00ffffffffc0
My dream goal is to create n8n workflow that automatically collects trip data from all our vehicles every night using the Traccar tracking server APIs. At the end of the day, it generates a single combined report and sends it to our email inbox.
The report includes:
Start and End Times of each trip
Distance traveled (in kilometers)
Duration of the trip (in minutes)
Average speed
Google Maps links to the start and end locations (just click to open the map)
Multi-device support → whether it’s one car or several, everyone’s trips are included in the same report
The email comes in a clean HTML table format, making it easy to read on phone or computer. No need to log in anywhere — just open your inbox and see the day’s driving summary.
Wish me good luck ;)
Hello, everybody,
Any Help or update !!
Regards ;)
Here’s a screenshot of my n8n workflow email output, the Daily Driving Report by Device. I can’t really use it yet since my tracker isn’t working, so this is just sample data from the Traccar server with the iOS app.
Do you have a protocol documentation or other informations of the used OBD tracker (e.g. exact device model)?
What Commands do you use, to point the tracker to your Traccar server?
Hi everyone,
I used to have a couple of OBD trackers from a Chinese provider (no longer in business). Since their tracking service is no longer available, I set up my own Traccar server. The server works perfectly when tested with the iPhone client.
However, I’m having issues with the OBD tracker. The device connects to my server on port 5051, and the server log shows that it is sending hex data, for example:
I ran the hex message through ChatGPT and got the following decoded output:
"Firmware": "OBD_WM_V1.9.6_YMX"
"IMEI": "864049021635562"
"ICCID/ID": "602030814487333"
Status1:
Ignition: true
GPS Powered: true
GSM Registered: true
Device Active: true
Status2:
Satellites (guess): 4
GSM Signal Byte: 118
Flags: "11000000"
The problem is that the device still shows as offline in Traccar.
I also connected to the tracker via serial cable, and confirmed that the device ID matches the IMEI (864049021635562).
Has anyone worked with a similar OBD tracker or knows how to get it properly recognized by Traccar? Any guidance would be greatly appreciated.
Traccar version: 6.6