Unknown device with IMEI 359710040xxxxxxx very similar to "gps103"

marc8 years ago

Tracker server works great. Though getting it up and running is a steep learning curve, but well worth the effort.

I believe my device has protocol not supported by Traccar. Very close but not = "gps103". I think the Traccar server might be tripping over on a detail.

Looking at the server's logfile my device's data remains in HEX, not decoded. The exchange going on (I decoded the hex) is:

device > server:

imei:359710040103591,tracker,1704090902,,F,080259.000,A,5153.3944,N,00026.2571,W,0.06,340.01;

(I'd just switched servers with an SMS command)

server > Log:

WARN: Unknown device - 359710040103591  

...Then after a while:

device > server:

359710040103591;

server > device:

LOAD

...repeating every minute...

I can confirm the device ID 359710040103591 and model 'gps103' both appear in the device list, so I can only assume it's unknown protocol.

When put data side by side with examples (my other devices which work) we can see there's a very slight difference (highlighted)

imei:123456789012345,help me,1201011201,,F,120100.000,A,6000.0000,N,13000.0000,E,0.00,;
imei:359710040103591,tracker,1704090902,,F,080203.000,A,5153.3959,N,00026.2581,W,0.05,8.70;

imei:359710040638182,tracker,1704091804,,F,170416.000,A,5153.7459,N,00031.6153,W,0.00,0;
imei:359710040103591,tracker,1704090902,,F,080203.000,A,5153.3959,N,00026.2581,W,0.05,8.70;

imei:359710042078619,tracker,1704091804,,F,170428.000,A,5154.1287,N,00032.6630,W,0.00,0;
imei:359710040103591,tracker,1704090902,,F,080259.000,A,5153.3944,N,00026.2571,W,0.06,340.01;

imei:868683028449852,tracker,1704091804,,F,170444.000,A,5154.6767,N,00031.0957,W,0.00,0;
imei:359710040103591,tracker,1704090914,,F,081459.000,A,5153.3935,N,00026.2583,W,0.07,25.43;

imei:359710040635113,tracker,1704091804,,F,170446.000,A,5153.2932,N,00030.4313,W,0.00,0;
imei:359710040103591,tracker,1704090915,,F,081559.000,A,5153.3933,N,00026.2586,W,0.10,32.15;

(If can't see the ends, zoom out page view i.e. CTRL & - )

I don't know what the extra number at the end is , but I suspect it's tripping up the data parsing and causing WARN: Unkown device log entry

Anton Tananaev8 years ago

It's a regular GPS103 protocol, so port 5001 should work. "Unknown device" warning means that you haven't registered your device on the server.

marc8 years ago

hmmm.. strange. I'm reasonably sure I'd made known this device on the server, using:

Identifier; 359710040103591
Model: gps103

I'll check again, I'll now cut and paste the number out of the Log File and below that paste the number from out the "Device" dialog box...

359710040103591
359710040103591

I'll try deleting the device and re-creating it

marc8 years ago

Working now. After I'd deleted then re-created the device. Maybe there was an invisible character somewhere?

The only WARN messages now are

WARN: Geocoding failed - Empty address - GeocoderException (JsonGeocoder:74 < ...)

for all the devices but I'll deal with that later.

I'm still puzzled about those last numbers on the end of the raw data message (highlighted):

imei:359710040103591,tracker,1704100059,,F,235934.000,A,5153.3982,N,00026.2565,W,0.09,152.94;

My other devices have zero values here.

Anton Tananaev8 years ago

It's course/direction. The value is in degrees with zero meaning North.

marc8 years ago

Ah yes of course. I can confirm these last two values are velocity (km/hr) & course (degrees reference N)

I've just noticed something else about the data. Extra data sometimes appears between the 3rd and 4th comma. For some of my devices, I see my own mobile/cellphone number I use to send SMS. I guess that is to remind which number is registered as admin.