Page History

...

• TLP Definitions (Global)
  • The global TLP definitions made available to the EFM Emerson ROC module.  They are uploaded to the Ignition instance in the form of specifically formatted CSV files.  These TLP definitions can be reference by the configurations of the individual ROC devices that they apply to. A single Ignition Gateway may contain multiple global TLP definitions files that are used to configure different device types where the actual point types & parameters of the individual TLPs may differ across the different files and device types.
• EFM Mappings
  • Configuration Mappings
    • The configuration mapping files are used for building up EFM Configuration Records. They define which TLPs map to which fields (columns) in an EFM Configuration Record.  Additionally they can provide bit and/or value mappings for the TLP values. They are uploaded to the Ignition instance in the form of specifically formatted CSV files. 
  • Periodic Mappings
    • The periodic mapping files are used for building up EFM Periodic History Records.  They define which TLPs map to which fields (columns) in an EFM Periodic History Record, the logical type of the point type table (meter, station, or input), and an archive type of the value. They are uploaded to the Ignition instance in the form of specifically formatted CSV files. 

...

This can be uploaded to the Emerson ROC driver configuration and called 'Main TLPs'.  Once complete, it will look similar to what is shown below.

EFM Mappings

Configuration Mappings

Anchor
Configuration Mappings Configuration Mappings

The configuration mapping files are used for building up EFM Configuration Records.  They define which TLPs map to which fields (columns) in an EFM Configuration Record.  Additionally they can provide bit and/or value mappings for the TLP values. 

...

• Column Name
  • The name of the EFM Configuration Record field
• Column Data Type
  • The datatype of the EFM Configuration Record. Must be one of the following:
    • VARCHAR
    • INTEGERNUMBER
• TLP Point Type
  • The 'T' parameter of a TLP - must be an integer
• TLP Parameter Number
  • The 'P' parameter of a TLP - must be an integer
• Bits
  • An optional declaration of the bits to use from the value of the TLP
  • An ordered, colon-delimited, list of bit positions
  • Examples:
    • If the TLP value is a byte and only the first (least significant) bit is used, this value would be: 0
    • If the TLP value is a byte and the 2nd and 3rd bits are used, this value would be: 2:3
• Event Value Mapping
  • An optional, semicolon delimited mapping of the TLP values to the values that will be stored in the EFM Event Record
  • If using only certain bits the values themselves will need to be ordered, colon - delimited . lists of bit values
• Config Value Mapping
  • An optional, semicolon delimited mapping of the TLP values to the values that will be stored in the EFM Configuration Record
  • If using only certain bits the values themselves will need to be ordered, colon - delimited , lists of bit values

Below is an example of a properly formatted Configuration Mapping file:

...