How to send AVL data periodically, even when stationary?

Hi,

I’m currently testing the RUTC50v2 outside of a vehicle. I want it to send AVL data to my traccar server, but the config does not seem to allow setting this up (because the minimum distance travelled can’t be 0, same with min angle. I need to see the device is still active, even if the vehicle is stationary, so this is a major (blocking) limitation if I can’t set it up to periodically send position data, even when the vehicle is stationary for a long time.

Is there really no way to get the RUTC50v2 to periodically send it’s position, no matter if it is moving or not?

AVL server settings: enabled on, retry on fail on, hostname: 192.168.1.253 (my local traccar server), port 5027, protocol TCP, don’t contain connection off, static navigation off, send emtpy on, no signal timeout 2.

RUTC50v2 is connected to my LAN via the WAN port, has IP 192.168.1.115 (and LAN IP is static at 192.168.1.5).

No SIM or eSIMs active.

*Status:**Up, **Uptime:**0h 3m 46s, **Current distance:**0.00346, **Current angle:**0.0, **Current accuracy:**0.7

Hostname Port Protocol Connection Successful count Failed count Collected records Time since last record sent
192.168.1.253 5027 TCP Up 0 0 57 -

Main rule:

Rule priority: Low priority level

Collect period * 5

Min distance * 1

Min angle * 1

Min accuracy * 10

Min saved records * 1

Send period * 10

No secondary rules.

GPS position is fixed, map shows correct location.

Greetings,

We are currently working on your inquiry and will get back to you as soon as possible.

Best Regards,
Justinas

Out of interest, as I’m watching this thread …. on your RUTC, what is the AVL Server setting for ‘Static Navigation’?

Thx, Mike

Greetings,

Could you please confirm which firmware version is currently running on your device?

I tested this setup using a TCP Server (Hercules) instead of Traccar, and I found that the router successfully sends data even when the device is stationary. Just ensure that the Static Navigation setting is turned off.


The records are being collected successfully, however, the fact that both Failed count and Successful count remain at 0 indicates that the router is unable to deliver these packets to Traccar. From my tests, the count only increments when the router receives an acknowledgment from the server. Please verify that the router’s IMEI is correctly registered on the Traccar server. You can find the IMEI under Status → System, in the Modem section.

Are you hosting the server on a Windows computer? If so, please try temporarily disabling the firewall to see if that has an effect.

Could you provide a simple diagram of your network topology, including IP addresses? This will help us troubleshoot the issue more effectively.

If possible, could you perform a simple test with the Hercules TCP/IP server instead of Traccar? It can be found here:

Start the server on your PC/laptop and try sending AVL data to your PC/laptop connected to the RUTC50 locally (for example, via local Wi-Fi on the same subnet). Hostname in AVL settings should be your LAN IP address of PC/laptop). Also, please make sure that the firewall on your PC does not block traffic.

On Hercules go to TCP Server, set the port to the one on the RUTC50 configuration. Once configured, check whether the AVL packets arrive in Hercules, the router will first send the IMEI, you will have to send 01 as a HEX value from Hercules and then you will receive the AVL data.

This will help us determine if the issue is with the router’s AVL transmission or with the Traccar server configuration.

Best Regards,
Justinas

If your IMEI is correctly configured ….. are you seeing any data registered, when you look at the Traccar Positions’ report?

If Traccar Server is Windows based, then Windows Defender should have an Inbound and Outbound rule for the TCP Web UI and an Inbound rule(s) for the TCP Clients.

Other then the above, I’d suggest following Justinas’ suggestions for a simple Hercules test.

All settings are listed in my original post. Static navigation = off.

Firmware version = RUTC_R_00.07.19.4 (fully updated to latest stable).

IMEI is registered on Traccar. I have several MicTrack devices that all work perfectly fine. Port 5027 is open (no firewall issue).

Traccar running on my DS418 NAS inside Container Manager (Docker). 2 MicTrack devices are successfully sending data over port 5030. Port 5027 is open (configured in my router, same as 5027).

DrayTek Vigor2927 router: 192.168.1.1
NAS: 192.168.1.253 (running Traccar in docker)
RUTC50v2 LAN IP: 192.168.1.5
RUTC50v2 WAN IP: 192.168.1.120 (GW 192.168.1.1)

Traccar log is NOT showing ANY data coming from the Teltonika. It would be VERY good if there would be an option to force-send a test string. Can I do that via SSH maybe?

BTW, the CLI option in the WebUI errors out: The webpage at https://192.168.1.5:4218/#https%3A%2F%2F192.168.1.5%2Fcgi-bin%2Fcli,RB1gW0/MaYg8iLxwuropjQ might be temporarily down or it may have moved permanently to a new web address.

Hercules does receive the IMEI on port 5027 and if I send 0x01 I get more data, but it is weird data, not what is expected I think: "œXÌ›œXÌ®˜z’

Failed count is now increasing (with the number of times I send 0x01).

I can use Hercules (from my PC at 192.168.1.100) to connect to 192.168.1.253:5027 and send the IMEI from Hercules. That all works, as can be seen from the Traccar log:

2026-02-13 21:16:31 INFO: [Tea9f23e2] connected
2026-02-13 21:16:34 INFO: [Tea9f23e2: teltonika < 172.17.0.1] 86XXXXXXXXXXX
2026-02-13 21:16:56 INFO: [Td90481fa] disconnected

Note: I X’ed out the IMEI above.

Note that the 172.17.0.1 IP is because Traccar runs in Docker. Docker routes incoming packets on 192.168.1.253:5027 to the Docker container running Traccar at 172.17.0.1:5027.

So, the port is open, Traccar is setup correctly, but it seems that maybe the RUTC50v2 is using another interface to send the AVL data over? Does it try to send it over WIFI instead of the WAN connection?!

Ok, when inserting a SIM and disconnecting my local LAN from the WAN port, it all works. I’ll try to figure out why it doesn’t work when connected to my LAN, but at least I know it will work when the RUTC50 will be mounted in the vehicle. For now, low priority getting this to work on LAN.

I’ll open another topic because I can’t get Email to SMS to work. It doesn’t seem to want to pop the mailbox…

Greetings,

Do I understand correctly that you don’t want to continue troubleshooting the issue for now, because the setup works in the intended use case?

Best Regards,
Justinas

Hi Justinas,

Thanks for following up. Yes, it doesn’t work on the same LAN, but that’s probably just a local config problem. It works as advertised in the intended use case, so all good for now. I also managed to get the email to SMS functionality going, so I’m pretty much all setup now. Thanks!