Troubleshooting Modbus TCP timeout errors during high-frequency mobile script execution?

Hi everyone,
I’m working on a remote monitoring setup using a RUTX50 and I’ve run into a consistent issue with my Modbus TCP client. I’m trying to sync real-time sensor data from an industrial PLC to a mobile dashboard, but I’m experiencing significant packet loss whenever the client-side execution cycle drops below 100ms.

As part of my testing, I’ve been using a delta mod on my iOS testing device to simulate a high-load automation environment. I wanted to see if the router’s internal data-to-server service could handle the rapid-fire requests coming from the script, but I keep seeing “Master connection timeout” in the system logs. It seems like the RutOS firewall might be flagging the burst of traffic from the mobile executor as a potential flood and dropping the packets.

Has anyone else noticed issues with the RUTX series handling high-velocity HTTP POST or Modbus requests from mobile-based executors? I’m trying to figure out if I should be increasing the ‘Connection Timeout’ in the Modbus TCP Master settings or if I need to set up a custom traffic-shaping rule to prioritize this specific mobile MAC address. I really want to avoid cloud-based polling to keep the latency low, but if the local mod triggers keep timing out the Modbus stack, I might have to rethink the whole architecture. Any advice on tuning the router to handle these types of intense mobile automation scripts would be greatly appreciated!

Greetings,

For testing purposes, could you please navigate to Network → Firewall → Attack Prevention and temporarily disable “SYN flood” protection to see if it may be causing the issue?
image

Additionally, could you provide screenshots of the current Modbus configuration on your device?

Best Regards,
Justinas