Sinotrack ST-901 config issues
I tried with ACC OFF and SLEEP0000 01 the following command: <SPBSJ*P:BSJGPS*D:030> from "http://www.urion.cn/m/gps500/gps/help/Default.asp". Means normally 30 min pause. There comes an info back:
<BSJ*N:917xxxx011*Q:guentexxxx20.synology.me:5013*CGREG:1*CSQ:21*GPS:(A,30,25)*A:internet.xxxxxxde,blau,blau*C:180*O:180*CS:0*3U:0*3Z:1*H:18
0*2A:1*GP:NO*60:0*5Y:9.0*5T:6,6*9E:00:00*1H:1*3D:104001*SNW:0*UTZ:1*SOS:0,1>
Can't yet decode that Sh%t. Result: Every 10 minutes comes a bunch of about 20 entries. h02 < 17x.2.x.237... and h02 > 17x.2.x.237... and id: 91xxxx6011, time: 2025-08-28 20:54:39, lat: 4x.xxx28, lon: 1.xxxx2, course: 255.0
The above IP seams to be the IP of my tracker.
Then tried with:
<SPBSJ*P:BSJGPS*D:300> Means normally 300 min pause. But here 20 min pause and then around 20-25 entries.
With ACC OFF still to much traffic, with ACC ON every 2 sec. an entry, so unusable.
This seem to have fixed the 2 second requests problem for me:
<entry key='h02.ack'>true</entry>
I'm using version 6.10.0
Hello,
I have your GPS device SinoTrack ST-901, everything worked fine until now, but now it suddenly shows me the wrong location. It shows me that I am somewhere in Malaysia, but I am in Croatia. When I call the number from the GPS device, it sends me the exact location, and when I go to see the location via the SinoTruck application, it shows me that the GPS is in Malaysia, and until now the application was ad-free, but now I can barely use it because of video game ads and such.
Regard
Ivica
Hi @ivica, so you don't use traccar but the SinoTrack platform? Then you may better contact the SinoTrack support?
Hi,
I'm also having a problem.
The platform is Traccar 6.10.0, hosted on my local server using a Docker container.
Until now, I've been using WanWay Tech S20 trackers based on the GT06 protocol, and it worked perfectly.
I've now bought a SinoTrack ST-901L (4G), which I think only supports the h02 protocol. I connected it to the car's wiring harness with the orange ACC cable. Despite setting "sleep mode: on" and a 5-minute sleep timer, the tracker wakes up constantly, sends positions, and sometimes informs me when I leave the designated zone because the GPS wakes up randomly and provides false positions. This never happened with the WanWay Tech S20.
2025-12-05 03:50:11 INFO: Event id: 9171063713, time: 2025-12-05 03:50:11, type: deviceOnline, notifications: 0
2025-12-05 03:50:12 INFO: [Tefdc2176: h02 < 188.33.14.35] *HQ,9171063713,V8,035006,A,5227.7085,N,1654.9496,E,0.00,0,051225,FFFFF9FF,0,0,0,0,7,31,122,0#
2025-12-05 03:50:12 INFO: [Tefdc2176: h02 > 188.33.14.35] *HQ,9171063713,R12,035012#
2025-12-05 03:50:13 INFO: [Tefdc2176: h02 < 188.33.14.35] *HQ,9171063713,V6,035013,A,5227.7085,N,1654.9496,E,0.00,0,051225,FFFFF9FF,0,0,0,0,89480610500629596924#
2025-12-05 03:50:13 INFO: [Tefdc2176: h02 > 188.33.14.35] *HQ,9171063713,R12,035013#
2025-12-05 03:50:15 INFO: Event id: 9171063713, time: 2025-12-05 03:39:31, type: deviceStopped, notifications: 0
2025-12-05 03:50:16 INFO: [Tefdc2176] id: 9171063713, time: 2025-12-05 03:49:56, lat: 52.46184, lon: 16.91590, course: 0.0
2025-12-05 03:50:17 INFO: [Tefdc2176] id: 9171063713, time: 2025-12-05 03:50:06, lat: 52.46184, lon: 16.91590, course: 0.0
2025-12-05 03:50:17 INFO: [Tefdc2176] id: 9171063713, time: 2025-12-05 03:50:13, lat: 52.46184, lon: 16.91590, course: 0.0
2025-12-05 03:51:55 INFO: [Tefdc2176: h02 < 188.33.14.35] *HQ,9171063713,V8,035155,A,5227.7085,N,1654.9496,E,0.00,0,051225,FFFFF9FF,260,6,31311,8314236,17,29,122,0#
2025-12-05 03:51:55 INFO: [Tefdc2176: h02 > 188.33.14.35] *HQ,9171063713,R12,035155#
2025-12-05 03:51:58 INFO: [Tefdc2176] disconnected
This type of log entry appears every 2-3 minutes, sometimes every 5, sometimes every 10. The tracker detects ACC correctly, but still works as it pleases. I've even looked for help on ChatGPT, but the only thing it suggests is trying to change the tracker's protocol to GT06 and giving some commands like PROTOCOL,1# or FORMAT,1#, but it doesn't work – the tracker doesn't respond to such messages. After changing the port from 5013 to 5023, the tracker is offline.
2025-12-05 07:12:56 INFO: [T48d5722d: gt06 < 188.33.8.225] *HQ,9171063713,V6,071256,A,5227.7051,N,1654.9565,E,0.00,0,051225,FFFFF9FF,260,6,7a4f,dd7c,89480610500629596924# 2025-12-05 07:12:58 INFO: [T48d5722d: gt06 < 188.33.8.225] *HQ,9171063713,V6,071258,A,5227.7051,N,1654.9565,E,0.00,0,051225,FFFFF9FF,260,6,7a4f,dd7c,89480610500629596924# 2025-12-05 07:13:00 INFO: [T48d5722d: gt06 < 188.33.8.225] *HQ,9171063713,V6,071300,A,5227.7051,N,1654.9565,E,0.00,0,051225,FFFFF9FF,260,6,7a4f,dd7c,89480610500629596924# 2025-12-05 07:13:02 INFO: [T48d5722d: gt06 < 188.33.8.225] *HQ,9171063713,V6,071302,A,5227.7051,N,1654.9565,E,0.00,0,051225,FFFFF9FF,260,6,7a4f,dd7c,89480610500629596924#
Theoretically, the log shows the GT06 protocol, but I don't think so, because it's not the full GT06 frame (which starts with 7878...).
Is there any way to convert this tracker to the GT06 protocol, or, I don't know, update the firmware to make it finally work properly?
By the way, I've already added the following to the Traccar configuration:
<entry key='h02.ack'>true</entry>
<entry key='gt06.port'>5023</entry>
But the problem with the tracker constantly waking up persists. Is the 2G version better in this regard?
Hi,
I have similar results with the 4G-Version. Discussion with Sinotrack was useless. As far as I know, only the 4G version is that stupid. I am using:
<entry key='h02.ack'>true</entry>
<entry key="h02.port">5013</entry>
In Europe 2G will be switched off in 2026 - 2028, except IT and GB. So I would not invest in dead horses ... and never again in Sinotrack devices.
I agree with @G.S., but I would not blame SinoTrack in general, see my post from beginning of 2025: Try the SinoTrack ST-906L instead (if you don't need water-resistance for your tracker).
After sending SLEEP0000 00 to the tracker (instead of SLEEP0000 0 ), there are hardly any "24..." messages any more. So this seems to be much better.
But now I keep on getting positions every 3 minutes, even after I resend 8090000 600 and 8050000 600 (10 minutes interval).
Settings are confirmed with RCONF