User - Modbus

Introduction

This page covers the Modbus configuration. This link has more information regarding the Modbus Protocol: Modbus Specifications and Implementation Guides.

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

Modbus

Open

Modbus Mode

This is the data output mode.

Open

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.

Heartbeat Period: When the radar has SafeGuard enabled, alarms can be output over Modbus. Additionally, the radar will update a 'heartbeat' count so that other devices on the Modbus can identify if the radar is working correctly.

The heartbeat is in the form of an incrementing count. The heartbeat update rate can be selected via Vertex to be either 1Hz, 4Hz, 8Hz or 16Hz. The default value is 4Hz, which we generally recommend.

This allows customers with systems that require a faster rate-of-response to check the heartbeat more frequently.

Related Information