How to disable one Alarm on my protocol?

joepr7 years ago

Hello Traccar Team

I'm using protocol H02 and I'm constantly receiving the Vibration Alarm. I don't need this. Is there a way to disable this alarm directly on the Traccar server?

Best Regards

Anton Tananaev7 years ago

Are you sure it's not some problem with decoding of the data?

joepr7 years ago

Hello Anton

Sorry I'm not sure about that.

The portable GPS Tracker with H02 protocol I'm using is not hardwired to the car. It's just a simple tracking device. So I really don't understand what this "Vibration Alarm" stands for. I have read that there are some issues with the poor documentation on this H02 protocol. But if could be possible to edit a config, xml or some sort of file on the Traccar 3.9 server that will help to stop receiving this alert that will be helpful.

Once again Thanks and I appreciate the hard work you have put on this project.

Anton Tananaev7 years ago

There is no way to disable specific alarm. You can only disable all of them.

I need to take a look at the server logs to check if there is any problem with decoding.

joepr7 years ago

Anton

Looking at the server logs file in /opt/traccar/logs/tracker-server.log

I did notice something really interesting. Each time a "vibration alarm" is triggered and a email is sent under the log file it shows the device has been "disconnected"

Sorry I can't attach a picture but here is a copy of the log file for yesterday . I lookup every single alarm message and it match the disconnected

2017-01-10 07:41:01  INFO: [8269C4A8] id: 4106012736, time: 2017-01-10 07:41:00, lat: 18.42257, lon: -67.15418, speed: 1.0, course: 0.0
2017-01-10 07:41:15  INFO: [8269C4A8] disconnected
2017-01-10 08:06:31  INFO: [D865639F] connected
2017-01-10 08:06:31 DEBUG: [D865639F: 5013 < 74.126.90.205] HEX: 2a48512c343130363031323733362c56312c3132303633302c562c313832352e333437332c4e2c30363730392e323535342c572c3030302e30302c3230342c3130303131372c46464646464246462c3331302c3236302c34393130312c313739312c3623
2017-01-10 08:06:31  INFO: [D865639F] id: 4106012736, time: 2017-01-10 08:06:30, lat: 18.42246, lon: -67.15426, speed: 0.0, course: 204.0
Anton Tananaev7 years ago

I have just tested your example and it doesn't have any vibration alarm in it. Note that I am interested in HEX data.

joepr7 years ago

Anton

I have sent you via email the tracker-server.log with all the hex data. Hope this could help to detect the vibration alarm issue on the H02 protocol.

Thanks for your help

josuelich7 years ago

I have the same problem..im receiving the vibration alarm when device power on button is pressed and sometimes too...do you find any reason or solution?

Thanks!

Anton Tananaev7 years ago

I need HEX message and protocol documentation to fix the issue, if there is an issue.

Gaston7 years ago

Hello Anton, my case is similar to the previous ones ... when you turn on the device (LK109) it sends two packets to the Traccar, where one of them has information of the cell number that manages the device. This information is interpreted as alarm information and gives an incorrect "vibration alarm" or "SOS", depending on the cell number used as administrator. In principle here would be the problem, not yet the solution. Thank you.

*HQ,4109179024,NBR,181517,722,310,0,4,8106,32010,23,8101,22007,20,8106,12010,18,8106,22105,13,090217,FFFFFBFF,6#

*HQ,4109179024,V19,181519,V,3853.2587,S,06205.9175,W,000.00,000,090217,,5492932630888,8954314165044716555?,FFFFFBFF#
Anton Tananaev7 years ago

There are no vibration alarms in either of those two messages.

Gaston7 years ago

If, correct there is no vibration alarm information (FFFFFBFF), what is giving that incorrect information is that the software part that is responsible for decoding the packet interprets the cell number (5492932630888) as the container of the alarm data. In the capture, you can see the status 1412089870 decimal = 54929326, which is the first part of the cell number that appears in the packet. I hope I have explained. Thank you

screenshot
Anton Tananaev7 years ago

Looks like you are right. It interprets wrong field. Anyway, as I said, I need full protocol documentation to fix the issue.

Anton Tananaev7 years ago

Also, please provide those messages in original HEX format.

Gaston7 years ago

Hello Anton, here is the log of the lk109 power-up moment. Thank you

2017-02-10 07:37:22  INFO: [454308E6] connected
2017-02-10 07:37:22 DEBUG: [454308E6: 5013 < 186.158.138.240] HEX: 2a48512c343130393137393032342c4e42522c3130333733322c3732322c3331302c302c362c383130362c33323031302c32332c383130312c32323030372c32352c383130362c31323031302c32332c383130362c32323130352c32322c383130312c32323031322c31362c383130362c34323031302c352c3130303231372c46464646464246462c3523
2017-02-10 07:37:23  INFO: [454308E6] id: 4109179024, time: 2017-02-10 07:30:17, lat: -38.88795, lon: -62.09780, speed: 0.0, course: 0.0
2017-02-10 07:37:23 DEBUG: [454308E6: 5013 < 186.158.138.240] HEX: 2a48512c343130393137393032342c5631392c3130333733322c562c333835332e323737302c532c30363230352e383637382c572c3030302e30302c3030302c3130303231372c2c353439323933323633303838382c383935343331343136353034343731363535353f2c464646464642464623
2017-02-10 07:37:23  INFO: [454308E6] id: 4109179024, time: 2017-02-10 07:37:32, lat: -38.88795, lon: -62.09780, speed: 0.0, course: 0.0