Do you have HEX data logs?
When I check the logs the rows for this unit don't have a HEX entry. Just the raw line like the one above...
That's not possible.
I found one (and then 2 returns after it) but I can't make sense of it:
24474e474e532c3233353633302e30302c323934382e3337323836382c4e2c30393833302e3035323130362c572c41414e4e2c31372c302e372c3431372e352c2d32302e302c2c2c562a31440d0a24474e4753412c412c332c2c2c2c2c2c2c2c2c2c2c2c2c312e302c302e372c302e382c342a33410d0a2447504747412c3233353633302e30302c323934382e3337323836382c4e2c30393833302e3035323130362c572c312c31312c302e372c3431372e352c4d2c2d32302e302c4d2c2c2a35350d0a2447504753412c412c332c30332c30362c31312c31322c31342c31372c31392c32302c32322c32342c33302c2c312e302c302e372c302e382c312a32420d0a2447504753562c342c312c31342c30332c30392c3034362c34302c30362c38302c3139362c34362c31312c34332c3231302c35302c31322c30382c3331302c34322c312a36340d0a2447504753562c342c322c31342c31342c33352c3131352c35322c31372c33372c3034352c35302c31392c35352c3030392c34362c32302c30382c3138312c33382c312a36410d0a2447504753562c342c332c31342c32322c35362c3039352c34382c32342c33342c3238352c34392c33302c30352c3136342c32352c31332c2c2c2c312a35360d0a2447504753562c342c342c31342c34362c2c2c35322c34382c2c2c35302c312a36440d0a244750524d432c3233353633302e30302c412c323934382e3337323836382c4e2c30393833302e3035323130362c572c36352e392c3236392e382c3234303132342c342e342c452c412c562a36370d0a2447505654472c3236392e382c542c3236352e342c4d2c36352e392c4e2c3132322e302c4b2c412a31380d0a2450435054492c424154312c3233353633302c3233353633302a31340d0a24504350544f42442c302c37372e36372c312c313739342c332c3133383935352c342c36352e31332c382c4f4e2c31332c31332e34332c33342c323733352e30302c33382c2c34372c2c34382c2c35322c2c35332c2a36460d0a
I just figured it out. The name of this vehicle was BAT1. Now i just gotta figure out how to get the data its returning into traccar. I know the 138955 it returns is the milage
You can convert "BAT1" into HEX and filter by it.
But in general NMEA doesn't include things like mileage and fuel. If your device reports it, it's probably some custom NMEA extension and I'm not sure Traccar supports it. We would need to see technical documentation to answer that question.
Its cradlepoint IBR900 but other then that i'm not sure where I would even try to find that information.
You have to contact the vendor.
Hi Anton,
Hopefully, the following will help as I am in the same boat as Jesse, however I am using Cradlepoint IBR900, IBR1700 & R1900:
https://docs.cradlepoint.com/r/OBDII/OBD-II-NMEA-Sentence-Syntax
Support PIDs: https://docs.cradlepoint.com/r/OBDII/Supported-PIDs
The general structure of the NMEA OBD-II sentence takes the form of:
$PCPTOBD, Enabled PID #, corresponding parameter value, Enabled PID #, corresponding parameter
The following example shows the format of an NMEA OBD-II sentence with PIDs enabled for vehicle speed, engine speed, throttle position, and fuel level:
$PCPTOBD,0,0,1,760,2,13,4,67.487*4E
The meaning of this sentence, from left to right, is shown in the following table.
NMEA OBD-II Sentence Parameters and Enabled Values Example
Field Value Header
$PCPTOBD
PID 0 (PID for VEHICLE_SPEED) = 0
PID 1 (PID for ENGINE_SPEED) = 760
PID 2 (PID for THROTTLE_POSITION) = 13
PID 4 (PID for FUEL LEVEL)= 67.487
This is not supported currently.
Thanks Anton,
Do you believe it is possible to update the Cradlepoint (now Ericsson) GPS protocol (5118) to incorporate the provided ODB-II NMEA sentence syntax?
Definitely possible to implement support.
Anton, Thats awesome news!
When do you think this could be supported? Is there anything else you need me to provide to help expedite?
Running:
The IBR900 is setup to send the NMEA data over to the server and is working for location data. I am receiving correct data for that.
The issue is that the VEHICLE SPEED, MILAGE, FUEL LEVEL and other data points are not being read in the traccar system. They are enabled on the IRB900 and the GPS settings have the box checked to send vehicle telemetry. What might be a solution for this? Where do I even start?