Re-start regular position reports of 'gps103' after a connection loss
It's possible to implement a workaround with some small modifications to the protocol decoder.
An idea..... If while the time a device is disconnected, somehow a Command is sent (impossible from the user interface, button is grayed-out), what happens to this Command? Does it get buffered and then sent on the next connection?
If so that could solve the problem, in conjunction with a Trigger of some kind. Perhaps trigger being connection loss.
Incidentally I'd like to see on Traccar if possible user-definable triggering of Commands. Useful in conjunction with Geofences for example.
You can send commands only if device is connected, unless SMS commands are supported for the protocol.
For any feature requests use GitHub.
Yes, by definition a command can only get through when there's a connection. I meant what happens if a command message is created anyway (independently of the grayed out button) and it's sent towards a disconnected device. Is it queued on server side awaiting the next connection to the destination device?
I don't know how to request features with Github.
Commands are not queued. If device is disconnected, you get a failure result.
You can post feature requests here:
https://github.com/tananaev/traccar/issues
Just make sure it's not already there, in which case just comment on existing thread.
Is there any easy way of queuing commands to wait for the device?
What do you mean by "easy"? You would have to implement it in the code. If you are comfortable with Java, it should be fairly easy.
"Easy" for me is microcontroller assembler (20 years experience), but to me Java would be "quite impossible" with zero years experience.
It’s possible to implement a workaround with some small modifications to the protocol decoder.
OK. I'd just searched github tananaev/traccar source code for "Protocol Decoder" and got 474 search results. Although every single search result displayed on the first page had the word "protocol decoder" in it, none of them seemed to have relevance, to me. I didn't check any of the other 48 pages as I didn't know what I'm supposed to be looking for.
I know exactly what I want to do: At the time a new connection is made to specific device, send this 'refresh' command:**,imei:xxxxxxxxxxx,C,01m
I then searched the folder on the hard drive where Traccar Server is installed to, searching within every single file for the text: "protocol decoder" , but all I got was "search is complete, there are no results to display"
So therefore it seems to me there's no Protocol Decoder in my version of Traccar. I think implementing such a small modification will be about as impossible as me coding Java!
All protocol decoders are here:
https://github.com/tananaev/traccar/tree/master/src/org/traccar/protocol
In above link there appears to be three .java sources relevant to the device in question:
Gps103Protocol.java
Gps103ProtocolDecoder.java
Gps103ProtocolEncoder.java
My guess is it's Gps103ProtocolDecoder.java
Meanwhile, I searched the Traccar installation on the server's HDD again and I still think this could be impossible to implement. There are no .java files at all, and no Gps103ProtocolDecoder file of any file type within the Traccar folder. I didn't try searching the rest of the hard drive.
All protocol decoders are here:https://github.com/tananaev/traccar/tree/master/src/org/traccar/protocol
Do I need to download one of these 'protocol decoders' and install it to where the server is installed?
You would have to have at least some basic Java knowledge if you want to do the modifications.
What basic Java knowledge do I need because all I want to do is send the command: **,imei:xxxxxxxxxxx,C,01m to the device right after it connects. As a 'hello' greeting from server. Surely it's just a case of strategically pasting the command into a file somewhere.
I would try pasting the command into this 'protocol decoder' you mentioned earlier, but there is no sign of any .java files at all on the server installation, and I really can't see how changing a file located on Github (even if I had access) could have any effect on the server program I'm running.
Normally a gps103 GPS device resumes regular reporting when a connection is broken and restored. I've noticed reporting resumes fine even after a connection loss of some weeks.
However I've got a 'gps103' example (IMEI 35971004xxxxxx) that quite often doesn't resume reporting, it does nothing more until commanded to report again. All it does is announce itself (heartbeat) to keep the server connection alive every 90 seconds. If the connection break time is quite short (a few seconds), this device resumes regular reporting.
I would have posted this is the GPS devices forum, but I'm reasonably sure there's nothing can be done with the device itself, unless there is some undocumented command I don't know about. So this is why the posting is in the server forum.
Is there anything can be done easily at the server to fix this problem? Examples:
Here's the log file entries showing the problem. With HEX: decoded for ease of reading.
(repeating every 90 secs the whole time while connected)