Fimer VSN700, Руководство по эксплуатации продукта

Страница: 17 / 29

EN
17
8. 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 the 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 Aurora Protocol to SunSpec Adapter and Modbus
TCP communication.
8.1 Aurora Protocol to SunSpec Adapter
The data logger’s Aurora Protocol to SunSpec Adapter is a software adapter that has two main functions
• it continuously polls inverters that use the proprietary Aurora Protocol as fast as it can
• caches data gathered from these inverters in SunSpec compliant Modbus data maps.
NOTE – D The SunSpec Alliance is a global trade alliance that aims to standardize how inverter data is stored.
This allows SCADA systems to use standard Modbus TCP read commands and a common SunSpec inverter data map to gather
information from any FIMER (or legacy Power-One) inverter that only supports Aurora Protocol.In addition, a SCADA system can send
a supported Modbus write command to a SunSpec inverter control register and the data logger sends the equivalent Aurora protocol
command(s) causing the inverter to execute a control action, such as grid disconnection or output power reduction.
NOTE –
D
Note that only inverters using the Aurora protocol have their data converted and cached in SunSpec compliant Modbus
data maps.
NOTE –
D
For complete SunSpec specifications and open information standards, go to http://www.sunspec.org/specifications/.
8.2 Modbus TCP server
External monitoring or SCADA systems must communicate with the data logger using the Modbus TCP protocol . 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 protocol 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 communicates with the SunSpec Adapter allowing SCADA systems to gather data using Modbus TCP
protocol from inverters which use the proprietary Aurora protocol. When a Modbus TCP client sends read commands intended for an
inverter that is using Aurora protocol, 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, the SunSpec adapter will send the
equivalent Aurora protocol command(s) 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 write 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).
8.3 Data logger configuration for SCADA or other monitoring systems
8.3.1 Set a Static IP Address for the data logger
Connect a PC to the Eth1 (Local) port of the data logger and browse to address http://172.17.17.1 to access the data logger’s web based
configuration UI. In the Network tab configure a static IP address for the data logger’s Eth0 port that is either within the same subnet as
the SCADA system or can be routed to/from the SCADA system. Use a single space between your primary and secondary DNS servers,
if applicable. Alternatively, the data logger can be set for DHCP if the DHCP server it receives its IP address from is configured to always
assign the same IP address to the data logger.
8.3.2 Configure the serial interfaces
Configure the serial port interfaces for the appropriate communication protocols based on the devices installed at the site. If using inverters
that only communicate using the Aurora protocol, then the serial interface they are connected to must be set for Aurora Protocol (to
SunSpec) Adapter for the inverter’s data to be accessible by Modbus TCP clients. Note that the ULTRA central inverter is only supported
via Modbus RTU or via the SunSpec Adapter options; it is not supported via the Legacy Aurora Protocol Adapter option. Setting the
interface for Modbus RTU will allow for better polling performance; however, advanced features like remote inverter firmware upgrade are
only available through the SunSpec Adapter option.
In the Home tab click the pencil icon and use the drop down menus to configure the Primary and Secondary RS-485 interfaces
based on the type of devices connected to these ports. Polling performance is better if half of the devices are connected to one of the data
logger’s RS-485 ports and half connected to the other, though this may not be practical depending on the physical locations of devices
or protocols used. Try to spread as many devices as possible across the two ports for better polling performance. The protocols used
on each interface can be changed on the Max version data logger. They can both be set for the same protocol or different protocols. All
devices daisy chained to a particular port must use the same communication protocol and settings as those set in the data logger for
that port, including baud rate and parity checking. Note that to monitor the ULTRA central inverter via Modbus RTU, the baud rate for the
interface on the data logger must be set for 19,200 bps.
Verify that both ports are configured to the appropriate baud rate and parity for the connected serial devices by clicking on the wrench