Modbus Tcp Commands; Modbus Tcp Register Map - ABB VSN300 Product Manual

M
odbus TCP Commands
In order to implement communication between the VSN300/inverter
(Modbus TCP server) and an external monitoring or SCADA system
(Modbus TCP client), the VSN300 and the external system must be on
the same network subnet or have a route set up in order to communicate
each other.
The VSN300 is able to forward Modbus TCP traffic on port 502. An
example of Modbus TCP command sent by the Modbus TCP client to
the VSN300 follows:
Where:
- IP_address: IP address assigned to the VSN300 board
- 502: port used for enabling the communication between the Modbus
TCP client (external monitoring or SCADA system) and server (VSN300)
- Protocol_address: 247 in case of communication between VSN300
board and inverter via INTERCOM bus; AURORA PROTOCOL address
in case communication between VSN300 board and inverter via legacy
bus.
M
odbus TCP register map
The Modbus TCP register map the Modbus TCP client has to refer to is
Sunspec compliant. The specific map to be referred to depends on the
specific inverter type monitored as indicated below:
- SunSpec M101: with single MPPT - single phase ABB inverter
- SunSpec M103: with single MPPT - three phase ABB inverter
- SunSpec M106: with dual MPPT ABB inverter
<IP_address>:502:<protocol_address>.
- 61 -
7 - Operation