Use this page to configure the shared communication profiles for external equipment such as meters, readers, lights, sensors, and other supported equipment.
Each profile uses the same index across these settings. For example, profile 1 uses DEVMODEL1, DEVNETPROFILE1, DEVADDR1, DEVSLOT1, and the related settings for that same profile.
Use this sequence when commissioning a shared driver profile.
DEVMODEL#.DEVNETPROFILE# and, where required, DEVGWPROFILE#. Use Instrument Defaults when a known factory address or serial default must be confirmed.DEVSLOT# and DEVADDR#.Start by selecting the connected equipment model and the communication path used for that profile. See Device Model Setup for the model-specific communication setup values and Instrument Defaults for known factory communication defaults.
Use Device Model Setup to select the registered model code and the related communication values. Then enter the selected model code in DEVMODEL# for the same profile index.
| Index | Range | Format | Default | Example | |
DEVMODEL# |
1..128 | 0..999999999 |
0 = No equipment assigned 100xxxxxx = Auto or unused model type Other values = registered model code |
0 | DEVMODEL1 101114101 |
Select a gateway profile only when communication must pass through a converter layer between the communication profile and the connected equipment. See Gateway profiles.
| Index | Range | Format | Default | Example | |
DEVGWPROFILE# |
1..128 | 0..4 |
0 = No gateway 1..4 = Built-in gateway profile |
0 | DEVGWPROFILE1 1 |
Select the built-in communication profile that defines the transport path, protocol family, and serial settings used by the connected equipment. See Network profiles and Instrument Defaults.
| Index | Range | Format | Default | Example | |
DEVNETPROFILE# |
1..128 | 0..20 |
0 = No net profile selected 1..20 = Built-in net profile |
0 | DEVNETPROFILE1 1 |
After the communication path is selected, map the profile to the correct slot and address.
Assign the runtime slot used by the configured profile so the decoded value is routed to the correct product function, meter slot, or reporting destination.
DEVSLOT# uses the same profile index as the other driver parameters. The value after the command is the slot number. Use 0 only when no slot is assigned. Slot numbering starts at 1 within the relevant equipment family or product function: the first energy meter uses slot 1, the second energy meter uses slot 2, and the first water meter uses slot 1. The maximum valid slot depends on the equipment family and product layout.
| Index | Range | Format | Default | Example | |
DEVSLOT# |
1..128 | 0..128 |
0 = No slot assigned 1..128 = Logical slot number |
0 | DEVSLOT1 1 |
Enter the address value required by the selected equipment model and communication path. Depending on the equipment family, this can be a bus address, a serial number, or an input number.
| Index | Range | Format | Default | Example | |
DEVADDR# |
1..128 | -2147483648..2147483647 |
Use the address value required by the selected device model and net profile. This can be a bus address, serial number, or input number. |
0 | DEVADDR1 10 |
The communication system can either read a profile as fast as possible or add a fixed wait between read cycles.
Use this parameter to reduce how often the system reads the selected profile. This is typically used to reduce traffic or power consumption for slower or battery-based equipment.
| Index | Range | Format | Default | Example | |
DEVON# |
1..128 | 0..8 |
0 = Disabled 1 = No added wait between reads 2 = 5 seconds 3 = 10 seconds 4 = 30 seconds 5 = 60 seconds 6 = 120 seconds 7 = 300 seconds 8 = 600 seconds |
0 | DEVON1 5 |
Use this section when selected decoded driver values must be logged in DataGuard or exported onward to Emiko. Configure the Driver Communication profile first, then continue on DataGuard via Driver Communication.
These settings override the default timeout, retry, and owner-group behavior. Keep the default values unless there is a confirmed need to tune a specific profile.
Set a custom timeout for the selected driver profile. The meaning of the numeric value depends on the selected driver and communication method, so the recommended value is normally the system default.
A shorter timeout can detect a missing reply faster, but it can also create unnecessary communication faults on slower equipment or busy links.
| Index | Range | Format | Default | Example | |
DEVTIMEOUT# |
1..128 | -1..500 |
-1 = Use system default timeout 0 = No timeout >0 = Custom timeout value |
-1 | DEVTIMEOUT1 30 |
Set how many internal retries the system may attempt for the selected driver profile after a timeout or read failure.
More retries can help ride through short disturbances, but they also increase the time before a real communication failure is treated as failed.
| Index | Range | Format | Default | Example | |
DEVRETRY# |
1..128 | -1..12 |
-1 = Use system default retry count 0 = No internal retry >0 = Number of internal retries |
-1 | DEVRETRY1 3 |
Assign the preferred owner group only when the automatic assignment does not give the required communication behavior. Automatic owner selection is the normal and recommended mode.
Public revision 21/05/2026