writer
544
edits
Line 40: | Line 40: | ||
[[File:modbus_2.png]] | [[File:modbus_2.png]] | ||
===Recording=== | |||
The add-on detects Recording starts and stops in NVGate. When properties are defined in the Input file, they are updated when the recording stops. | |||
===Input file=== | |||
This file contains the list of data to be read from the server: | |||
• General | |||
o Label: Name of the input displayed in NVGate. | |||
o User unit: the unit as described in the Units.xlsx | |||
o Min value and Max value: The minimum and maximum value (expressed in user unit). The min value must correspond to Bus data min, and the max value must correspond to Bus data max, i.e., if a temperature in [-20, 100] can be encoded on the bus with values in [-200, 1000]. So, range min = -20 and max = 100. | |||
• Modbus input | |||
o Address: the register address. | |||
o Type: type of MODBUS request (among Discrete Input, Internal Bits, Holding Register, Input Register). | |||
o Bit: for Discrete Input or Internal Bits, the position of the bit in the register | |||
o Bus min, Bus max: Bus data: see range (in this example, the values must be min = -200 and max = 1000). | |||
• NVGate Simulated DC number: Must be in [1, 32]. | |||
• Measurement properties (the parameters are metadata written in the measurement when the recording stops. They are accessible from Measurement Properties in NVGate.) | |||
o Name: the name displayed in NVGate. | |||
o Method: how the value is computed (first, last, min, max, average). If the method is ‘file’, the value is read from the Properties file. | |||
o # digits after dot: value rounding. |