
94 Revision 10 – 1/09/2015 FTS 370d/w/r
Appendix B: Vanguard Modbus Specification Map (V8).
Modbus RTU over RS485
The Vanguard system master controller (VSMC) is configured to be a Modbus slave device. It is statically configured as
follows:
Baud Rate 9600 Stop Bits 1
Modbus RTU over TCP
The Vanguard system master controller is configured to be a Modbus slave device. It is statically configured as Station 2
and host TCP socket # 502. The Modbus RTU over TCP protocol expects messages to be formatted exactly as the Modbus
RTU over RS485 protocol.
Behavior notes:
1. The Vanguard system’s IP address mode can be set to static or dynamic via the ‘MONITORING CONFIG ->
LOCAL ETH CONFIG’ menu on the Vanguard system 1 controller.
2. The Vanguard Modbus RTU over TCP socket #502 will accept incoming connections. However if no data is
transmitted through the socket for 5 minutes it will be terminated.
Behavior during Controller Reboots
The Modbus interface (both via RS485 or Ethernet) is disabled during the Vanguard controller power-up diagnostic
sequence. Modbus messages will not receive a response during this time-period, which lasts 45 seconds for each system
controller. Due to this behavior, it is advised to allow up to 5 minutes for the Vanguard controller to complete its power-up
sequence before normal Modbus operation begins.
Implemented Modbus Map
The following tables detail the data that can be read using Modbus function code 03, and the values that can be written one
register at a time by using Modbus function code 16. Unmapped address space will return the values 65535 or 61166.
Address Read/Write Register Name Description / Values
0 R
Number (version) 0-65535
Komentarze do niniejszej Instrukcji