User - Modbus
Introduction
This page covers the Modbus configuration. This link has more information regarding the Modbus Protocol: https://modbus.org/specs.php.
We can inform clients using the Modbus over TCP Protocol, which links the radar to a client, and can trigger alarms. This works in conjunction with the SafeGuard™ Lite application. This is an optional feature that is subject to its own software licence.
Contents
- 1 Modbus
- 1.1 Modbus Mode
- 2 Related Information
Modbus
Modbus Mode
This is the data output mode.
None: Both Modbus and Relay output are disabled
Master: The radar will poll other devices that are operating as a slave.
Modbus Address: This is the IP Address of the slave.
Port: This is the TCP port used by Modbus in order to connect to the slave.
Health Offset: The health register offset used by Modbus.
Slave: The radar acts as a server and makes alarm data available to the Modbus master.
Port: This is the port used by Modbus in order to connect to the slave.
Health Offset: This is the register offset used by Modbus.
Relay: The radar will output nav mode area alarms via a Relay unit instead of using Modbus.
The Adam relay is accessed via TCP/IP; its configuration (IP address and port) are on this page: User - Radar Configuration.
Related Information
-
Vertex User Guide (Products)
-
Firmware Control and Upgrade (Products)
-
Changing the Configuration (Products)
-
Login (Products)
-
Engineer (Products)
-
User - Radar Data (Products)
-
User - Radar Hardware (Products)
-
User - Radar Configuration (Products)
-
Standard User (Products)
-
4. Using the Vertex Interface (Products)