Functionality
IntesisBox polls, either continuously or only when ordered from the KNX, the M-Bus devices to obtain updated
readings for the points configured in it (the points corresponding to measures and states of the meters in the
integration points list explained later in this document). With every read, the new values received are updated in the
Intesisbox's memory and become updated in the KNX side. When a change in any point configured as write-enabled
in IntesisBox is detected (this is written from the KNX side), the corresponding action in the M-Bus device will be
performed. These actions can be: force a polling of a specific M-Bus device or force a polling of all M-Bus devices.
The polling of a specific M-Bus device, or of all M-Bus devices, can be forced in any moment from KNX side by
writing a 1 in the corresponding KNX object specially enabled for this purpose in the IntesisBox.
The automatic continuous polling of all M-Bus devices can be activated/deactivated writing from KNX in a specific
KNX object specially enabled for this purpose in the IntesisBox.
Other M-Bus information accessible from KNX, using specific KNX objects of the IntesisBox, is:
• Bus activity (indicates if meters are currently being polled or if polling is in stand-by).
• M-Bus status of every meter (this M-Bus status is sent by the own meter with every poll and indicates the
internal status, manufacturer specific in every case).
These are the main features of the M-Bus interface of IntesisBox:
• Embedded level converter. Direct connection to M-Bus devices with no extra hardware required.
• Scan option to automatically detect M-Bus devices and its available registers.
• Import/Export of M-Bus device templates.
• MBUS-/+ two wires (plug-in terminal bloc with screws) connection.
• Baud rate configurable from 300 to 9600 bps (allowed baud rates in M-Bus. The devices are normally
configured at 2400 bps at the factory).
• Primary or secondary addressing allowed.
• Useful timeouts and specific parameters to make the interface widely compatible with many meter's
peculiarities found usually between different manufacturers.
• Polling of the meters can be continuously, either configured in the own IntesisBox or you can
activate/deactivate continuous polling of the meters from KNX side using a special datapoint.
• You can force a polling of the meters (refresh of readings) in any moment from KNX side using special
datapoints: one datapoint to force a polling of all the meters, and one specific datapoint per meter to force
the polling of the individual meter.
• IntesisBox can also be configured to make a single polling of the meters (refresh of readings) at start up.
• For each meter, a datapoint is available in KNX indicating communication error with the meter, also a general
communication error datapoint is available (that will be active whenever the communication with one or
more meters has failed).
• Fully flexible configuration of the registers to poll in the meter, to adapt to any meter.
Every meter, depending on manufacturer and model, offers different type of signals from the mentioned before. To
know what signals offers the meter and of what type, to be able to integrate those wanted, refer to the device technical
documentation. Anyway, and to ease and speed up the identification of the signals offered by any device (and of
what type), the scan option is highly recommended or the import of templates too.