contact@webdyn.com | webdyn.com
V2.05 subject to changes | Webdyn © by Flexitron Group
The automatically generated les are prexed with the concentrator ID of which the default value is
“WPM” followed by the last 6 digits of the MAC address of the device that generated them.
The concentrator ID can be modied by the client, however, if it is modied after a le has been generated,
there will be no resulting modication of the le name or its declaration in the daq.ini le.
The prex is separated from the remainder of the le name by an underscore. The purpose of this is to
prevent overwriting les that previously existed at the IS level.
The les will have a csv extension. If another extension (.ini for example) is given in the daq le, it will be
accepted.
Files generated automatically or created by the local web interface will be named as follows:
3.1.2.2.1.1 IO
The IO le names are dened as follows:
<uid>_IO.csv
3.1.2.2.1.2 Modbus
There are two types of modbus le:
• The les generated by the installer/integrator.
• The les generated by SunSpec auto-detection.
For the les generated by the installer/integrator, there are no le naming rules. The le name is free
form. There are no rules.
For the les generated by SunSpec detection, the name is composed as follows:
<uid>_SunSpec_<Category>_<Manufacturer>_<Model>_<Options>_<Protocol>.csv:
• Category: the device type. Currently only the “Inverter” type is used.
• Manufacturer: the manufacturer name. The value is obtained from the ”Manufacturer” eld in
the SunSpec tables.
• Model: model name. The value is obtained from the ”Model” eld in the SunSpec tables.
• Options: options detected on the device. The value is obtained from the ”Options” eld in the
SunSpec tables.
• Protocol: the protocol name. The values are:
• modbusRTU: for a device on the serial connection.
• modbusTCP: for modbus devices on Ethernet.
3.1.2.2.1.3 Proprietary Protocol
Proprietary protocol le names are detailed in the proprietary protocols application note.
To Next Page
Loading...
Need help?
General