DNP3 FBx Archive Collection Tab

Collection Interval

Select the desired collection interval relating to the Schedule object assigned on the Connection tab. EFM upload collections occur on the frequency of this interval.

If multiple schedule objects are selected for this device (Primary, Secondary, or Alternate) ensure that each Schedule has the same interval numbers configured.

Use meter config from device

When publishing meter configuration, event, or alarm records, use information from a meter config file retrieved from the device. The meter config file will only be retrieved if it has not been stored previously, or if the meter list file indicates that its contents have changed. The Generic meter does not have a meter config file.

If a Meter Configuration object has been assigned to the meter, that Meter Configuration object will not be used to publish the meter configuration. If EFM Event Configuration or EFM Alarm Configuration objects have been assigned to the device, they'll be used to publish events and alarms that are not defined by the meter config file.

Publish all meter config fields

When using the meter config file from the device to publish meter configuration records, publish all the fields that would be published if the meter config file contained tags for every enumeration that it currently supports. Any fields that don’t actually have tags in the meter config file will be empty. This will prevent data from shifting from one column to another in a CSV file if contents of the meter config file change.

Disable EFM/multiple event format

Some single events from the device are published as multiple EFM events. For example, a change event for the temperature units yields change events for these four EFM fields: base temperature units, orifice reference temperature units, pipe reference temperature units, and temperature units. EFM publishers translate these into four different events, but with non-EFM publishers (CSV, Database) it will look as though the same event has been published four times.

Do not select this option if you are publishing to an EFM format. It will disable all EFM formatting, not just the multiple events.

Use history points from device

When publishing history records, use information from a history header retrieved from the device. The history header will only be retrieved if it has not been stored previously, or if the history configuration counter indicates that its contents have changed. If an Archive Field Configuration object has been assigned to the upload, that Archive Field Configuration object will not be used to publish history.

Use end timestamp for history

Default = Not selected. Use end timestamp as timestamp for history record instead of start timestamp.

Use transaction points from device

When publishing transactional log records, use information from a transactional log header retrieved from the device. The transactional log header will only be retrieved if it has not been stored previously, or if the transactional log configuration counter indicates that its contents have changed. If an Archive Field Configuration object has been assigned to the transactional log, that Archive Field Configuration object will not be used to publish the transactional log.

Log progress of uploads

Default = Not selected. Log status messages as uploads are collected.

Log fields of archive records

Default = Not selected. Log fields of archive records as uploads are collected.

Log fields of meter files

Default = Not selected. Log fields of meter list files and meter config files if retrieved during upload collection.

Log fields of history headers

Default = Not selected. Log fields of history headers if retrieved during upload collection.

Log fields of transaction headers

Default = Not selected. Log fields of transactional log headers if retrieved during upload collection.