...
The periodic mapping files are used for building up EFM Periodic and Daily History Records. Each row of such file maps specific fields of LOG_PERIOD or DAILY records to a database column names. It also allows user to turn a database column off. In other words if column is disabled, respective filed will not be 'recordized. The MeterPeriodicMapping.csv is an example of such file.'. These mappings are CSV files with the following values:
- Array Number
- Array number (i.e. 250 for the LOG_PERIOD_RECORD and 251 for DAILY_RECORD)
- Application Enumeration
- List of application enumerations this mapping entry should be applied. If empty, the mapping entry is applicable to any application.
- Record Field Offset
- Field offset within the record
- Data Type
- Description
- Column Name
- Enabled
- A flag that turns this field 'on/off'. In other words it defines if this field should be recordized.
Below is a mapping example for the LOG_PERIOD_RECORD:
# arrayNum, appEnum, offset, data type, description, column name, enabled
250,4|20,6,FLOAT,Average Differential Pressure,dp_avg,enabled
250,5|21,6,FLOAT,Pulse Counts,pulses,enabled
250,,10,FLOAT,Average Static Pressure,sp_avg,enabled
250,,14,FLOAT,Average Temperature,temp_avg,enabled
250,5|21,18,FLOAT,Uncorrected Volume,raw_vol,enabled
250,,22,FLOAT,Volume,volume,enabled
250,,26,FLOAT,Heating Value,heating_value,enabled
250,,30,UINT16,Flow Time,flo,enabled
250,,32,UINT16,Period Time,flo_rate,enabled
An example of the periodic mapping file can be found here: MeterPeriodicMapping.csv
Main Properties
...