Loading…
Loading…
Resources · Interactive Guide
Four short scenes: the gateway polls your field devices, sends each reading to two servers on different platforms and protocols, lets your SCADA read the devices straight through, and fails over from Ethernet to 4G with TLS without losing a reading.
In polling mode the WT460M is the Modbus master: it reads each field device on the RS-485 bus and sends the time-stamped readings to your servers as one event, in JSON or CSV. In transparent mode your SCADA sends its own Modbus frame over the secondary server link, by TCP or MQTT, and the gateway passes it to the slave exactly as sent, CRC and all, returning the reply byte for byte.
Yes. The two server links are set up separately: each has its own protocol (HTTP, MQTT or plain TCP), its own data format (CSV, JSON, ThingSpeak/CPCB or ThingsBoard) and its own TLS setting. One reading can go to an HTTP platform and an MQTT broker at the same time, or to two brokers, or any other mix. The primary server always receives polled data; the secondary receives it too, or runs transparent mode.
Yes, as payload formats. Each server link can send in ThingsBoard format or ThingSpeak/CPCB JSON, as well as CSV and JSON, over whichever protocol that link uses. The two links are set independently, so one platform can get one format and the other a different one.
On 4G, both server links support TLS. On Ethernet, the primary link supports TLS and the secondary runs without it. The same rule follows the active link after a failover.
The gateway logs each new event instead of losing it, fails over to 4G, and then sends the logged events in order, oldest first, while live readings carry on.
Yes. A local SCADA or HMI reads the same values from the WT460M as a Modbus TCP slave. Transparent frames can also reach one Modbus TCP device on the plant LAN.