FMS Alarms Data Group
The "FMS Alarms" (FMSAlarm) data group is used to send alarm data to FMS. It gets its data from the "Hist - Alarms" (HistAlarm) data group, which reads alarms from the Emerson event file. Each alarm includes an Emerson point tag. If the tag is found in the associated Meter Configuration data group or the "Hist - Station" data groups for the current type/instance, it is deemed applicable to the current meter. Units come from the native alarm history data group, not from the device template file.
Data Group Mapping
The mapping between Emerson and FMS items is contained in the fmsMaps/alarmItems section of the device template file. There are three options for data sources: EFM item, DEID, or Emerson point tag:
-
The value comes from a specific EFM item in the "Hist - Station" data groups. EFM items are matched to an item in the "Hist - Config" (HistCfg) data group. For more information, see EFM Data Items.
|
<fmsMaps> <alarmItems> … <eFMS_ALARM_TYPE_DP efmItem="2"/> … </alarmItems> </fmsMaps> |
-
The value comes from a specific DEID in the Meter Configuration data groups or the Station History data groups.
|
<fmsMaps> <alarmItems> … <eFMS_ALARM_TYPE_DP deid="C0030"/> … </alarmItems> </fmsMaps> |
-
The value comes from an Emerson point tag.
|
<fmsMaps> <alarmItems> … <eFMS_ALARM_TYPE_DEVICE tag="Station_%station%.*"/> … </alarmItems> </fmsMaps> |
Device specific items may contain a wildcard in the tag. For example, the tag "DP_%meter%.*" will include alarms for this DP meter.
Substitution strings in point tag names are supported for meter number (%meter%), station number (%station%) and gas component number (%comp%), and are filled using values specified by the user in FMS Configuration data group.
FMS Alarms Data Group Structure and Components
For more information about working with device template files, see Device Template Files.
|
<!-- By default, alarm tags that are not mapped to FMS data items are recorded as device-specific alarms. Set omitUnmappedAlarms to "true" to override this behavior. --> <FmsAlarm niceName="FMS Alarms" baseOrd="1" maxCnt="24" ordLabel="Meter" omitUnmappedAlarms="false"> <dgElements/> <uccRecvParms type="string"> <SDate desc="Start date" required="true"/> <EDate desc="End date" required="false"/> </uccRecvParms> </FmsAlarm> |
Unmapped Alarms
The "FMS Alarms" (FmsAlarm) data group includes an attribute omitUnmappedAlarms. If this flag is set to "false" or is missing, a device specific alarm will be recorded for any alarm tag that matches the instance portion of a tag in the Meter Configuration data group or the "Hist - Station" data groups for the current type/instance.
Example
If the Meter Configuration data group includes an item with tag "DP Meter_1.OBJ_NAME", any alarm tag beginning with "DP Meter_1" will be included as a device specific alarm.
Single-Meter and Multi-Meter Station Support
The DNP3Emerson sample DTFs support single-meter and multi-meter stations to send historical data to FMS from the Emerson FBx devices. The meter naming conventions are as follows:
- Single-meter stations — auto-created history DEIDs use the Hxxx format, where xxx is an EFM item ID.
-
Multi-meter stations — the meter instance is appended: the Hxxx-yyyy format is used, where yyyy is a type/instance, one for each meter in the station, e.g., H004_0211 and H004_0212.
The DNP3Emerson sample DTFs use the efmItem attribute instead of the deid attribute for history items in the fmsMaps/histItems section of the device template file. This provides support for both single-meter and multi-meter stations.
