If you have arrived here with your questions, you must have already understood that Divakos devices and meters are distinct from each other, and a device can have an unlimited number of meters. Furthermore, in reality, a device/communicator may be interfaced with another physical device that previously functioned solely as a reader, without any network connectivity. Consequently, Divakos also offers the flexibility to assign a serial number in three different locations. We have three separate locations for the serial numbers like module serial and meter serial under device view, and the meter serial number under each meter.
As you can see in the picture, there are three locations where you can set serial numbers. The logic behind overwriting the serial numbers is explained by the green arrows in the diagram. The Module Serial number serves as the base serial number, which is required for all types of motherboards. If this communication module is implemented, for example, in a water meter, then the water meter can have its own serial number, which can be entered in the Meter Serial field.
In this case, one device can have two serial numbers, but in the lists, we will display the Meter Serial number as the main serial number. However, if you create a meter from that device, which essentially represents one data point of that device, it is possible to overwrite the serial number. This allows for the possibility of having a different serial number for each data point.
Serial numbers serve as the main connection ID for integrations with third-party systems. They provide a unique identifier for establishing connections and facilitating communication between Divakos and external systems. Additionally, serial numbers play a crucial role in network planning, acting as the primary connection point between planning tools and the Divako network. By using serial numbers, the planning tool can accurately map and organize the network infrastructure.
Serial numbers in Divako are 8char to 16char long. The standard length is 8char.
Allowed serial lengths in the system:
| Where | Minimum Length | Maximum Length |
|---|---|---|
| Network Planner Device Serial | 8char | 16char |
| Device Meter Serial | 8char | 16char |
| Meter Serial | 8char | 16char |
| Device Module Serial * | 8char | 8char |
The Device Module Serial includes prefixes, if added. A serial with a prefix will be overwritten by the meter serial.
Note: The minimum serial length is always 8 characters. For example, if your serial number contains only 6 digits like
123456, it will be displayed in Divako as00123456.
The
8charrule originates from standards used in WmBus and IoT (UNI CEI EN13757).
Serial prefixes are employed in WmBus (Wireless M-Bus) systems to extend serial numbers. This is because 8char serials are often insufficient for ensuring uniqueness across all devices. Typically, these prefixes are 6char in length. For instance, 9APA01 is a prefix associated with the Apator manufacturer, leading to serial numbers like 9APA0112345678, totaling 14char in length. However, in Payload in the Serial field, only the last 8char are displayed, which correspond to the segment visible in the payloads sent by the device.
The Wm-Bus standard has also updated its serial logic to a 14char format, such as WT2410075996572. This serials are saved directly under meter serial field to keep the full-serial format.
In Divako, you don’t need to understand the logic behind why or where serials are saved, as Divako will automatically handle them for you, while still allowing you to view and edit them in detail.
The Network Planner contains records of all your planned devices, each with its own serial number. We maintain 8char serials plus prefixes on both ends to ensure that each serial is precisely 8char in length. This facilitates the synchronization of planner devices with network devices by comparing these 8char serials. In cases where duplicated serials are present on both sides, prefixes are included in the comparison process to ensure accurate matching.