Configure the Fieldtime configuration setting
- Last UpdatedApr 24, 2025
- 1 minute read
Note: For information on overriding default configuration settings, refer to Modifying Configuration Settings.
The Fieldtime configuration setting provides a method to swap the time and fieldtime values in the Historical Collect table. The time column now contains the timeserver (when the point is collected) and the fieldtime column contains the time coming in from Omnicomm or protocols (such as modbus, Open Platform Communications (OPC), Distributed Network Protocol [DNP3]).
Some protocols, like DNP3, have a feature that allows the Remote Terminal Unit (RTU) to store values in an internal memory when a communication outage occurs. These values are sent to the AVEVA Enterprise SCADA system when communication is restored. This situation creates a conflict with the time column (primary key) since old values that are coming in from a point are collected at the same moment. To avoid this constraint, you can use the time column (primary key) as the field time (which is always unique) and the fieldtime column as server time.
In order for this new feature to take effect, you must add the new configuration setting to the RealTime.json file.
To add the Fieldtime configuration setting to the RealTime.json file
-
Stop the RealTime Service.
-
Create or open the RealTime.json file in %DNADataRoot%\RealTime\config\Settings.
-
Add in the following line of text:
{
"RealTime": {
"FIELDTIME_AS_TIME_IN_COLLECT": true
}
}
4. Start the RealTime Service.