Flexitron Webdyn SunPM User Manual

contact@webdyn.com | webdyn.com
V2.05 subject to changes | Webdyn © by Flexitron Group
154
The IO and MODBUS type alarm le format is the following:
datetime_1;AlarmSource_1;leDenitionName_1;nameEquipment_1;
indexVariable_1;value_1
datetime_2;AlarmSource_2;leDenitionName_2;nameEquipment_2
indexVariable_2;
value_2
...
datetime_Y;AlarmSource_X;leDenitionName_N;nameEquipment_N;
indexVariable_A;variable_A_value_B
Colour code:
• Blue: device-specic information or data.
Where:
• datetime_Y: alarm timestamp at trigger point Y. For the format, see variables FTP_
EuroDateFormat, FTP2_EuroDateFormat, HTTP_EuroDateFormat and HTTP2_EuroDateFormat
in section 3.2.2.5: “Servers”.
• AlarmSource_X: Source that triggered the alarm (IO, MODBUS).
• leDenitionName_N: Denition le name for the device.
• nameEquipment_N: Device name. “Name” eld in the “<uid>_daq.csv” le (see section
“3.1.2.1.3.4 Declaration of equipment”).
• indexVariable_A: Index A for the alarm variable.
• variable_A_value_B: Value B of Variable A corresponding to alarm index A.
The reported values for IO and MODBUS alarms are raw and must be linked to the index conguration
in the device denition le. The IS must interpret the data using the raw data le and the denition le
to be able to apply the dened factors A and B and the unit for each input or index. (see section “2.2.
Denition File Content”).
Example of a MODBUS alarm le:
21/02/12-07:00:19 MODBUS MODBUS_DELTA_M88H-COM1.20-Sunspec.csv OndA 48 0.000000
21/02/12-07:00:49 MODBUS MODBUS_DELTA_M88H-COM1.20-Sunspec.csv OndA 48 3.000000

Flexitron Webdyn SunPM Specifications

General

Brand	Flexitron
Model	Webdyn SunPM
Category	Controller
Language	English