CSV Import/Export
The EFM Mappings support the import and export of data in a Comma Separated Variable (CSV) file. CSV import and export supports the efficient configuration of many devices.
Creating a Template
The easiest way to create an import CSV file is to create a template. For more information, refer to the instructions below.
1. To start, create a new device using the default settings. Then, click OK.
2. Next, right-click on the device and select Properties | EFM Mapping. Then, click Export.
3. Save the file to an accessible location.
4. Use the exported template in a spreadsheet application that supports CSV files, and then modify the file as desired.
Note: Microsoft Excel is an excellent tool for editing large groups of tags outside the server. Once a template CSV file has been exported, it can be loaded directly into Excel for editing.Exporting EFM Mappings
Exporting an EFM Mapping will generate a CSV text file that contains sections for History and Alarms. Each section has a heading record followed by a record for each item. Column names must match those listed; however, columns may be in any order.
Note: For Gas models, the CSV file will contain two sections for Hourly History and Daily History mapping data. For Liquid models, the CSV file will contain three sections for Hourly History, Daily History, and Batch History mapping data. CSV files cannot contain data for both.History Mapping
The table below displays the History Mapping for the Hourly History, Daily History, and Batch History mapping data. The required columns are listed in bold.
Column Name | Description |
|---|---|
Attribute | This is the name of the History Mapping attribute. Attributes can be in any order. Attributes that are not included on an import will be left blank in the mapping. Note: All possible attribute names are listed in the History group. For more information, refer to EFM History Mapping. |
Value | This is the address syntax for the attribute. It can be blank, static, or take the form S<N>. For the Batch Start attribute available in liquid models, the syntax is X:Y. For more information, refer to EFM History Mapping - Liquid Models.  For information on each attribute's value limitations, refer to EFM History Mapping. |
Alarm Mapping
The required columns are listed in bold.
Column Name | Description |
|---|---|
Address | This is the address of the alarm. It can take the form 1N34. For more information, refer to EFM Alarm Mapping. |
Alarm Type | This is the type of the alarm. The default is Differential Pressure. The valid types are as follows:1 = Differential Pressure2 = Static Pressure3 = Temperature4 = Cutoff5 = Backflow6 = Battery |
Alarm State | This is the state of the alarm. The default is Off.1 = Off2 = On3 = Hi4 = Lo |
Importing EFM Mappings
Once the CSV file has been created and exported, it may be re-imported into an EFM Mapping. To do so, open EFM Mapping and then click Import.
Note: For History and Alarms, importing will replace all existing settings with the settings specified in the CSV file. When the import is complete, the configured mapping should match one for one with the file.Using Other Characters as the Delimiter
When utilizing a CSV file that does not use a comma or semi-colon delimiter, users should do one of the following:
• Save the project in XML. Then, perform mass configuration on the XML file instead of using CSV.
• Perform a search-and-replace on the delimiter in the CSV file and then replace the delimiter with a comma or semicolon. The delimiter being used by the OPC server (either comma or semicolon) must be set to the replacement character.
For information on specifying which character to use as the variable (comma or semicolon), refer to "Options - General" in the server help file.