VSN700 Data Logger Product Manual
- 21 -
Interfacing VSN700-05 with SCADA systems
This section describes how to interface external monitoring or SCADA systems with the VSN700-
05 data logger and is intended only for these Max version data loggers. This section does not apply
to the Residential and Commercial versions. There are two important aspects of the data logger
that allow for easy integration into a SCADA system, the Power-One SunSpec Adapter and
Modbus TCP communication.
Power-One SunSpec Adapter
The data logger’s Power-One SunSpec Adapter is a software adapter that has two main
functions—it continuously polls legacy Power-One inverters as fast as it can using the proprietary
Aurora protocol and caches data polled from these inverters in SunSpec-compliant Modbus data
maps. The SunSpec Alliance has standardized how inverter data is stored. This allows SCADA
systems to use standard Modbus read commands and a SunSpec inverter data map to gather
information from legacy Power-One inverters. In addition, a SCADA system can send a supported
Modbus write command to a SunSpec inverter control register and the data logger sends the
sequence of Aurora protocol commands which cause the inverter to execute a control action, such
as grid disconnection or output power reduction. Note that only legacy Power-One inverters using
the Aurora protocol have their data converted and cached in SunSpec Modbus maps when using
the data logger’s SunSpec adapter; Modbus RTU device data maps are not converted or cached.
For complete SunSpec specifications and open information standards, go to
http://www.sunspec.org/specifications/
.
Modbus TCP server
External monitoring or SCADA systems must communicate with the data logger using Modbus
TCP. The data logger’s Modbus TCP server/gateway converts and forwards onto the serial port(s)
commands intended for Modbus RTU capable inverters or other Modbus RTU devices connected
to the data logger. The device response is then converted and forwarded back to the Modbus TCP
client that sent the command.
The Modbus TCP server also passes Modbus commands intended for legacy Power-One
inverters, which communicate via the proprietary Aurora Protocol, to the Power-One SunSpec
Adapter. When a Modbus TCP client sends read commands to a legacy Power-One inverter, the
data logger’s Modbus TCP server will respond based on data that has been cached for that
inverter by the SunSpec adapter. When a Modbus TCP client sends a supported write command to
a legacy Power-One inverter using the inverter’s SunSpec Modbus data map, the SunSpec
adapter will convert this command to Aurora Protocol for communication to the inverter. If there are
any problems with the command, an exception response will be sent back to the Modbus TCP
client. There is no confirmation that a command is successful and that the inverter has performed
the control action; so, write commands should always be followed up shortly after with read
commands to confirm the change(s).