can't identify protocol

stefano6 years ago

Hi all, new to traccar, very nice indeed

I'm trying to connect to the server my device, a peplink BR1 router which have a gps forwarding feature

I see data logged on server in HEX format..

2447505654472c2c542c2c4d2c2c4e2c2c4b2c4e2c414141412a30300d0a2447504753412c412c312c2c2c2c2c2c2c2c2c2c2c2c2c2c2c2c414141412a33320d0a2447504747412c2c2c2c2c2c302c2c2c2c2c2c2c2c2c414141412a34410d0a244750524d432c2c562c2c2c2c2c2c2c2c2c2c4e2c414141412a37460d0a2447504753562c342c312c31362c30312c2c2c32382c30322c2c2c33342c30332c2c2c33352c30342c2c2c32362c414141412a35430d0a2447504753562c342c322c31362c30352c2c2c32372c30362c2c2c33362c30372c2c2c32382c30382c2c2c33342c414141412a35350d0a2447504753562c342c332c31362c30392c2c2c33302c31302c2c2c32332c31312c2c2c33362c31322c2c2c33342c414141412a35450d0a2447504753562c342c342c31362c31332c2c2c32382c31342c2c2c33332c31362c2c2c33352c31372c2c2c33332c414141412a35380d0a

once decoded, data looks like:

$GPVTG,,T,,M,,N,,K,N,AAAA*00
$GPGSA,A,1,,,,,,,,,,,,,,,,AAAA*32
$GPGGA,,,,,,0,,,,,,,,,AAAA*4A
$GPRMC,,V,,,,,,,,,,N,AAAA*7F
$GPGSV,4,1,16,01,,,28,02,,,34,03,,,35,04,,,26,AAAA*5C
$GPGSV,4,2,16,05,,,27,06,,,36,07,,,28,08,,,34,AAAA*55
$GPGSV,4,3,16,09,,,30,10,,,23,11,,,36,12,,,34,AAAA*5E
$GPGSV,4,4,16,13,,,28,14,,,33,16,,,35,17,,,33,AAAA*58

in my device configuration I can enable either NMEA (above, with all the sentence type enabled) or TAIP but after playing a bit and searching here (https://raw.githubusercontent.com/tananaev/traccar/master/tools/test-integration.py) I didn't find anything useful

the first question is: is my device supported in any way? is there a way to make it work?

Thank you in advance
Ciao
S.

Anton Tananaev6 years ago

Both NMEA and TAIP protocols are supported by Traccar. The problem with NMEA is that this protocol doesn't support identification, so unless your router has custom extension to NMEA for identification (many routers do), it's not possible to use it. TAIP (port 5031) should work fine.