EnOcean Mapping Files

The EEP profiles included in the default database (FIL1201–1227) should be used whenever possible. Additional tested profiles may be available on support.deltacontrols.com. You can also contact Delta's Professional Development Services group to have a custom mapping file made.

Modifying a Default Mapping File

Occasionally, you may want to modify one of the default EEP mapping files. For example, you may want to adjust the range and scale values.

To modify a default mapping file:

1. Open the FIL object you want to modify (e.g., FIL1215) and click Download File. The XML file (A5-10-10_4BS_Telegram_Room_Operating_Panel_Temperature_and_Humidity _Sensor_Set_Point_and_Occupancy_Control.xml) is saved to the Downloads folder.
2. Create a new FIL object (e.g., FIL115).
3. Open the new FIL object (e.g., FIL115) and click Upload File. Upload the XML file you downloaded in step 1.
4. Modify the mapping values in the Translation table as needed.

• To edit a value, double-click the value you want to edit, enter the new value, then click Save.
• To add a new mapping row, click Add, double-click each cell and enter the desired value, then click Save.
• To copy a mapping row, select the row, then click Copy. The row is added to the end of table.
• To delete a mapping row, select the row, then click Delete.

If no values appear in the Translation table, the uploaded XML file may contain invalid syntax or unsupported options.

If a FIL object associated with a Device SV object is changed or edited, a controller reboot is required to clear data from the previous profile.

Translation Table Details

The following table describes each column in the Translation table and notes which values are not supported.

Column	Values
Object Type	variable input, output (not supported)
Name	Name of the BACnet object. Can be up to 47 characters including spaces.
Object	AV, BV AI, BI, MI, MV, AO, BO, MO, LO, CSV (not supported)
Mapping	advalue complex, hoa-switch, feedback (not supported)
Mapping Type	analogValue, binaryValue
Direction	get = read (for EnOcean inputs) set = write (for EnOcean outputs) [blank] = read/write
ioNumber	Instance number of the BACnet object.
offset	The bit offset in the data packet, where an offset of '0' is the most significant bit of the first byte in the data packet. For example, offset 0 and size 3 in a byte that has a value of 0x55 (0x01010101) means a value of 0000010. The three most significant bits are selected (010).
size	Number of bits that make up the object value. The size starts at the most significant bit of the first byte. For AV objects, the size can be up to 32 bits. For BV objects, the size is always 1.
minRange	Lowest possible raw value.
maxRange	Highest possible raw value.
minScale	Engineering value that corresponds to the minRange value.
maxScale	Engineering value that corresponds to the maxRange value.

Differences Between Current and Previous FIL Object Mappings

The History pane in enteliWEB provides a convenient way to see changes made to a FIL object.

To see the differences between the current and previous version of a FIL object, in the History pane at the right of the enteliWEB page, click the details link.

A window opens showing the differences between the current and previous version of the file. Scroll down to see recent changes.

Creating a Custom XML Mapping File

While it is recommended to use the predefined EEP mapping files included in the default database (FIL1201–1227), you can also create your own XML mapping files that follow the syntax rules defined in the Special Interface and EnOcean XML schema files (FIL1001 and FIL1012). You will need an XML editor for this, such as Microsoft Visual Studio.

To create a mapping file using an XML editor:

1. Download SpecialInterface.xsd (FIL1001) and EnOcean.xsd (FIL1012) to your PC.
2. Open your XML editor and create a new XML document.
3. Open the XML document and add the following lines to set up the XML document file to refer to the two schema files:

<?xml version="1.0" encoding="utf-8"?>
<si:mapping xmlns:si="http://schema.deltacontrols.com/schemas/entelibus/SpecialInterface1.0" xmlns:eno="http://schema.deltacontrols.com/schemas/entelibus/enOceanMapping" type="enocean">

</si:mapping>

1. If necessary, assign the schema files to the XML document using the XML editor. For example, Visual Studio allows you to assign schema files that help it validate the XML document.
2. Add mappings to the XML document (e.g., ioNumber, offset, size, minRange, etc.). The value number and ioNumber (object instance) are mandatory.
3. Save the XML document to the same folder as the schema files.

Instances (ioNumber) must follow sequentially for the mapping translation to work. If non-sequential instance numbers are used, the FIL interface will accept them but the mappings will not work correctly.

Saving Mapping Data

If you do an enteliWEB database save, the .zdd file does not include SV objects or XML mapping content. To save mapping data, you must use the Download File button on the FIL page.