Query on device alarm message
Yes, those messages are recorded with other positions. For other protocols there would be an "alarm" value if it's an alarm message. For TK103 I don't think it's handle at the moment. I need protocol documentation and message sample to add support.
Hello Anton,
Thank you for the response.
I would have attached the protocol doc here, but I didn't find any option for attachment. Please visit https://docs.google.com/folderview?id=0B9QofkYKWsMuZnIwZ1BqeXhzQlE. Then open the last but one item - 'TK103 ALTERNATE protocol vs 2.1.pdf'.
Refer the table at 2.3.3 > B (Up message) > O > 01, i.e., protocol command BO01. The details of the command is at 3.2.4. Hope this helps.
Awaiting further response.
I have implemented support for alarm messages. Here is a new build:
https://www.dropbox.com/s/cgmlansv32j3ii0/tracker-server.jar?dl=0
Thanks a lot for the prompt support. Really appreciated.
Two further queries on this:
Should I simply overwrite this file at /opt/traccar/? Will it continue to run with the existing database structure and data?
After installing this new build and once a few alarm messages are sent by the device, where and what can I expect to see in the database?
Today It so happened, that I was as well testing TK103. Here is some things I have been wondering as well.
Here are two different type of value I received in Attributes., I was just wondering what is the difference in the value 'tracker' and 'ac alarm' in both entries.
{"alarm":"tracker","io1":"0","io2":"0","io3":"0.00%","ip":"223.176.129.54"}
{"alarm":"ac alarm","io1":"0","io2":"0","io3":"0.00%","ip":"223.176.129.54"}
Also What would be the best way to handle different protocol / different terminologies used in attributes? say such as i03 here refers to fuel, however would it be same for other protocols as well?
@rb_traccar_user, you need to replace the file, but make sure you have version 3.2 installed first.
Thanks again Anton. I have version 3.2 installed, so I will simply replace the file.
Now that alarm message support for TK103 has been added, can you please advise as to which field in the 'position' table I should look at in order to confirm that its an alarm record. Also, which bit/flag in which field will let me know the specific type of alarm received?
In the "attributes" there should be an "alarm" field.
OK. Thanks for the information.
Hello Anton,
Sorry to reopen this old thread, but this is the best place for the clarification, which I need. Please review the communication above.
I wanted to ask you if you have incorporated the modified tracker-server.jar in the main Traccar download (e.g., https://github.com/tananaev/traccar/releases/download/v3.2/traccar-linux-64-3.2.zip).
What I want to mean is, if I now download https://github.com/tananaev/traccar/releases/download/v3.2/traccar-linux-64-3.2.zip, or any of its future releases, will it have the TK103 alarm support built within it? Or will I need to replace the downloaded tracker-server.jar every time with the one you provided in this thread?
Thanks.
You can compare release date with the comment date to find out if it's included or not. I don't modify already released binaries.
Basically all the changes I make go into the next release, so this one will be included in Traccar version 3.3.
OK, thank you for clarifying.
Hello,
I am using Traccar v3.2 with a device that uses tk103 protocol.
My question is, does Traccar record device alarm messages as well? If yes, I guess such messages are recorded in the 'position' table itself, along with other standard position messages. Then how do I identify these alert messages in the table in particular? Also, how do I know what type of alarm it is?
Thanks in advance.