Application Note

This document describes linking a Senquip device to Modbus TCP servers on Ethernet, either directly or via an RS485‑to‑Ethernet bridge such as the USR‑TCP232‑304. It covers IP addressing, port assignment, and how Modbus application data is encapsulated in TCP frames (MBAP header). Example mJS code opens sockets, sends read/write requests, and validates responses with transaction IDs and length checks. The note compares Modbus TCP with RTU in latency and concurrency, and explains when to prefer one or to use a gateway for mixed fleets. A troubleshooting section addresses NAT, firewalls, keep‑alives, and stale connections. With proper socket lifecycle and retries, Senquip devices can poll multiple TCP endpoints reliably and feed consolidated data to the Portal or third‑party platforms.

Access Application Note

Fill out the form below to access the full application note.