GPS 103A alarm messages

Blejzer9 years ago

Hi,

I'm looking at messages that I received from my GPS103A. Some messages I figured out on my own, but some I am still trying to workout.

here is the list of messages that I managed to figure out:

<info><protocol>gps103</protocol><alarm>acc off</alarm><io1>;</io1></info>
<info><protocol>gps103</protocol><alarm>acc on</alarm><io1>;</io1></info>

These two are pretty simple, they are ignition on and off messages.

<info><protocol>gps103</protocol><alarm>stockade</alarm><io1>;</io1></info>

This is alarm message once the vehicle leaves the GeoFence that you set up. It will not deactivate once vehicle is back in the permitted zone, you still have to cancel the alarm by sms!

<info><protocol>gps103</protocol><alarm>help me</alarm><io1>;</io1></info>

This is alarm message once the SOS button is pressed

New message that I noticed this morning is:

<info><protocol>gps103</protocol><alarm>qt</alarm><io1>;</io1></info>

I receive this message after I send command "load+password" (using sms, of course), and once the data from the SD card has been sent to the server, this message appears. Based on this, I assume it is some sort of confirmation that load command has finished or something, but I could not find any reference to it so far.

<info><protocol>gps103</protocol><alarm>ac alarm</alarm><io1>;</io1></info>

Also this one. I believe this one is after you kill the car with sms, if you try to turn the car on, it starts sending this message, until you cancel it (stop and resume messages).
*just to mention, EVERYONE, please make sure, when installing, cut the power to the vehicle starter, otherwise, you can kill someone if you disable the car while in motion!!!

Anton Tananaev9 years ago

Thanks for sharing all this info.

One weird thing I noticed in your XML samples is <io1>;</io1>. Are those messages from real device? Are you using TCP or UDP protocol?

Blejzer9 years ago

I'm using TCP, per default.
This is real device in my car. I just copy paste result from select on MySql database.

This is normal data:
<info><protocol>gps103</protocol><alarm>tracker</alarm><io1>;</io1></info>

mysql traccar positions
Anton Tananaev9 years ago

Can I see some HEX message samples from the tracker-server.log file please.

Blejzer9 years ago

Sure, here are some of the sample messages:

HEX: 696d65693a3335393731303034373732353434362c747261636b65722c3135303631333038323233392c2c462c3030323233382e3030302c412c343535302e323639342c4e2c30313630312e383638302c452c302e30302c303b
2015-06-13 00:22:41 INFO: device: 115, time: Sat Jun 13 00:22:38 GMT+00:00 2015, lat: 45.83782333333333, lon: 16.031133333333333

HEX: 696d65693a3335393731303034373732353434362c747261636b65722c3135303631333135333431372c2c462c3037333431372e3030302c412c343535302e323731382c4e2c30313630312e383632322c452c302e302c303b
2015-06-13 07:34:20 INFO: device: 115, time: Sat Jun 13 07:34:17 GMT+00:00 2015, lat: 45.83786333333333, lon: 16.031036666666665

And when getting acc on alarm:
2015-06-13 07:34:52 DEBUG: [3F2A1FC6: 5001 <- xxx.xxx.xxx.xx] - HEX: 696d65693a3335393731303034373732353434362c616363206f6e2c3135303631333135333434392c2c462c3037333435302e3030302c412c343535302e323731382c4e2c30313630312e383632322c452c302e30302c303b
2015-06-13 07:34:52 INFO: device: 115, time: Sat Jun 13 07:34:50 GMT+00:00 2015, lat: 45.83786333333333, lon: 16.031036666666665

Anton Tananaev9 years ago

Fixed the semi-colon problem. It won't be there in the next release.