Data Mapping Module
Module icon

Overview
There are many types of Data Mapping modules, and the module names and icons indicate the type of data being mapped. Data Mapping modules are core modules which can be disabled to allow for custom Modbus mapping using Modbus Slave modules.
To provide additional values not included in your meter’s default Modbus map, use a Modbus Slave module.
Inputs
These registers are connected to the output registers of other modules and define your device’s default Modbus map as well as the values shown on your device’s display and webpages. The quantity of Source inputs varies depending on the Data Mapping module.
Setup registers
This setup register enables or disables that Data Mapping module’s Modbus functions (by setting it to yes or no respectively). This register does not impact the data displayed on your device’s display or webpages. When disabled, the values connected to the module’s inputs are no longer available to a Modbus master as described in the device’s default Modbus map, and the associated Modbus registers can be used by Modbus Slave modules to create a custom Modbus map.
This setup register enables or disables all default Modbus registers that are not mapped to a Data Mapping module. An example of this type of register is a setup register like Volts Mode (from the Power Meter module). This register does not impact the data displayed on your device’s display or webpages. When disabled, Modbus register values not linked to a Data Mapping module are no longer available to a Modbus master as described in the device’s default Modbus map, and the associated Modbus registers can be used by Modbus Slave modules to create a custom Modbus map.
Output registers
All events produced by the Data Mapping module are recorded in the Event register. Possible events and their associated priority numbers are shown in the table below.
Event priority group | Priority | Description |
---|---|---|
Setup Change | 10 | Input links, setup registers or labels have changed. |
The Event output register stores the following information for each ION event: time stamp, priority, cause, effect, and any values or conditions associated with the cause and effect.
Responses to special conditions
The following table summarizes how the Data Mapping module behaves under different conditions.
Condition | Response of output registers |
---|---|
When the meter is started or powered-up (either the first time, or after a shutdown). | All output registers retain the values they held when the meter was shutdown. |
Detailed module operation
The following table lists the possible Data Mapping modules that may exist on your device:
Creating a Custom Modbus Map
Specific ION data values can be mapped using Modbus Slave modules, even if they are already connected to a Data Mapping module.
To create a custom Modbus map using registers that are assigned in the default map, you must make these registers available by disabling the associated Data Mapping module(s) before creating the custom map using Modbus Slave modules. The Modbus Slave module will not go online if there are Modbus address register conflicts with a Data Mapping module, and the Data Mapping module will remain offline even if enabled if a Modbus address conflict is detected.
To create a custom Modbus map using registers that are defined in the default Modbus map but are not inputs to a Data Mapping module, you must make these registers available by setting the Cfg Modbus Map Enable setup register (usually located in the Data Mapping Meas module) to disabled (no).