Generic Modbus Profile - Description
Description
The Modbus protocol is an open communication protocol based on a master/slave - / client/server architecture . You can use the function Generic Modbus Profile to quickly and easily integrate measuring devices (primarily non-proprietary devices) via Modbus RTU or Modbus TCP/IP into the GridVis. The master device in the architecture controls the transfer, and the connected devices (slaves) are only allowed to send telegrams when requested by the master device.
Note
Knowledge of Modbus Fundamentals is a prerequisite for understanding this function!
Requirements for the integration of measuring devices
Note
Requirement for the integration of measuring devices (non-proprietary devices) into the GridVis software:
The non-proprietary devices support the Modbus RTU / Modbus TCP protocol. Modbus ASCII protocols are not supported.
A Modbus address list from the device manufacturer.
Data formats conform to the Modbus recommendation, or to the available formats.
Properties and functions
The non-proprietary device is always connected through a UMG master, or a Modbus TCP gateway in Modbus TCP.
The value readout from the non-proprietary device In the GridVis software runs through the Modbus TCP/IP over Ethernet.
Non-proprietary device connected through a Modbus profile are managed as templates in the GridVis software.
Templates can be exported.
Modbus profiles can be created and edited in the GridVis software.
Non-proprietary device measurement values are queried (polled) cyclically, and can be analyzed through the GridVis functions Topology and Virtual Devices.
In the GridVis Standard edition and higher, measurement values from non-proprietary devices can be saved online, and a mean value can be derived.
A statistics function in the GridVis software serves to control communication with the non-proprietary device.
