Sinotrack ST-901 config issues
After sending SLEEP0000 0 the tracker starts sending messages, and it doesn't stop after 5 minutes as before.
If I send SLEEP0000 1 , the messages stop after 1 minute.
This setting shouldn't be correct, since the interval of sending is set at 10 minutes, and SLEEP (if set) should be set to a larger time then the normal interval of sending.
Welcome to the club! My traccar version is 6.7.3. Do you have an ST-901L 4G? If so, then we have the same problem. It doesn't work properly on external servers, but it does work ‘somehow’ on the SinoTrack server, and I have the same problems as you on traccar. I emailed a sales manager at SinoTrack and didn't get any useful information on how to fix it, just a bunch of nonsense and a request to enter the usual commands, but nothing changed. I suspect that we've ended up with a Chinese GPS that officially reports its location to the regulatory chinese authorities every 2 seconds.
I am not sure if it has to do with traccar itself. I do not know if traccar can change the behavier of the tracker. There are a lot of 'secret' commands for this device existing, but nothing stops that 2 sec. send-intervall. And .... I do not play around any longer with that junk!
It should have something to do with an aknowledgement which needs to be send to confirm the receipt of the message. I think the tracker keeps on sending the same message again untill it receives an aknowledgement.
That is why 6.9 works better then 6.6 - some work has been done to implement this, but I think something is still missing.
It is not the 'HQ...' message which is being resend, but another message starting with a nr.
I haven't found yet what needs to be send to answer.
And yes, somebody at SinoTrack responds to questions, but doesn't respond with an answer to the above question ...
G.S., Update your Traccar to v6.8.0 and above. There solved the problem with ST-901L 4G
gdb, Show your server's tracker-server.log logs and we'll try to help and analyze them. Maybe even fix it
I try to send the log from today.
The tracker was put online at 10:55:58
There are some strange entries before this time.
Between 10:55:58 and 10:56:57 (which is 1 minute) there are a few entries I don't understand.
At 10:56:57, the first run finished and it waited for +/- 10 minutes which is correct.
At 11:07:22, the second message is send, followed by 1 minute of undefined entries.
I don't see outgoing messages in this log.
I tried to upload the log-file itself, but this doesn't seem to work.
@Anatoly: Thanks for the info. I updated to v6.9.0. But get similar log as @gdb. Too much traffic on the line!
in traccar is not much to see on the screen, but the log is full, as before, every few seconds comes an entry:
ST-901L 4G 21.08.2025, 13:43:09 Ignition on
ST-901L 4G 21.08.2025, 13:43:10 Status online
ST-901L 4G 21.08.2025, 13:48:40 Status offline
ST-901L 4G 21.08.2025, 14:14:31 Status online
--shorted log--
08-21 13:43:10 INFO: [Td7be856c]connected
2025-08-21 13:43:10 INFO: [Td7be856c:h02 < 176.2.
2025-08-21 13:43:10 INFO: Eventid:9171026011, tim
2025-08-21 13:43:11 INFO:[Td7be856c:h02 <176.2.6.
2025-08-21 13:43:12 INFO:[Td7be856c:h02 <176.2.6.
2025-08-21 13:43:14 INFO:[Td7be856c]id: 917102601
2025-08-21 13:43:14 INFO: Eventid:9171026011, tim
2025-08-21 13:43:14 INFO: [Td7be856c]id: 91710260
2025-08-21 13:43:14 INFO: [Td7be856c:h02 < 176.2.
2025-08-21 13:43:15 INFO: [Td7be856c]id: 91710260
2025-08-21 13:43:18 INFO: [Td7be856c]id: 91710260
2025-08-21 13:43:27 INFO: [Ted35b623]connected
2025-08-21 13:43:27 INFO: [Ted35b623:h02 < 176.2.
2025-08-21 13:43:28 INFO: [Ted35b623:h02 < 176.2.
2025-08-21 13:43:30 INFO: [Ted35b623]id: 91710260
2025-08-21 13:43:31 INFO: [Ted35b623]id: 91710260
2025-08-21 13:43:43 INFO: [T25feb803]connected
2025-08-21 13:43:43 INFO: [T25feb803:h02 < 176.2.
2025-08-21 13:43:44 INFO: [T25feb803:h02 < 176.2.
2025-08-21 13:43:46 INFO: [T25feb803]id: 91710260
2025-08-21 13:43:47 INFO: [T25feb803]id: 91710260
2025-08-21 13:43:50 INFO: [T25feb803:h02 < 176.2.
2025-08-21 13:43:53 INFO: [T25feb803]id: 91710260
2025-08-21 13:46:44 INFO: [T25feb803:h02 < 176.2.
2025-08-21 13:46:47 INFO: [T25feb803]id: 91710260
2025-08-21 13:46:50 INFO: [T25feb803:h02 < 176.2.
2025-08-21 13:46:53 INFO: [T25feb803]id: 91710260
2025-08-21 13:48:36 INFO: [T25feb803:h02 < 176.2.
2025-08-21 13:48:39 INFO: [T25feb803]disconnected
2025-08-21 13:48:39 INFO: Event id:9171026011, ti
2025-08-21 13:48:39 INFO: [T25feb803]id: 91710260
2025-08-21 13:49:35 INFO: [Tf42660cf]connected
Perhaps the problem is with sleep or buffer overflow for the old st901. There the connection is maintained and if something happens, or the device reboots or loses connection or the device goes into SLEEP mode, then this is the reason for the shutdown. The protocol handles correctly.
Sinotrack communicates with 2 protocols at once. One protocol for communicating in REALTIME, which begins with *HQ, and the other one sends unsent undelivered requests.
Try using version v6.8.1. If it is newer, here is what I noticed was added
https://github.com/samm-git/traccar/commit/97ec12cd0b0f2347754c14ac4b383e2bfbb3b021
Add this configuration to your config:
<entry key='h02.ack'>true</entry>
Sinotrack has send me the used protocol. I don't know how to upload it to this forum, but it seems to be the same as : "http://gpsonline.com.ua/media/SinoTrack%20Protocol%20.pdf".
From the bottom of page 5 there is something about "Standard mode upload data to increase the base station location information"
This format seems to correspond with the messages send every 2 seconds (message starts with 24, which is HEX for $).
If this is the case, there should be a way to change to another mode which doesn't send this so often.
Maybe this is command S17 (transmission interval), but I don't know how this can be send to the tracker.
They also sent me this protocol. But in fact, there is another protocol format embedded there.
And so I corrected it there so that the second protocol could be processed.
Try adding what you reported earlier to the config, it should help
I added <entry key='h02.ack'>true</entry> to my traccar config and restarted, but this makes no difference.
Every 10 minutes I get 1 "*HQ" message (which is correct) , followed by many "24..." messages during +/- 1 minute (1 every second).
Then it disconnects en reconnects.
It looks like you have SLEEP set up.
Try turning it off by sending SMS
SLEEP0000 0where0000is your PIN