Product manual

TAC Xenta Server – Gateway, Technical Manual B Protocols
Schneider Electric Buildings AB, June 2011 169 (184)
04-00124-06-en
B.7.3 M-Bus Meters
One or more meter devices are added to the M-Bus interface node in the
network pane of XBuilder, as shown for the Wh and kWh metering
devices of the PW3 example network in the following screenshot.
Device Template
Device templates having a [MBus] filename prefix are used to create
M-Bus Meter devices in XBuilder. Subsequently, each device node is
used to configure communications with the physical meter it represents
on the M-Bus network.
Device Properties
• Meter Address – Allows the required meter primary or secondary
address to be entered based on the selected Mode The number
should match either the Primary address of a meter on the M-Bus
network (0–250), or its secondary ID number (0–99999999).
In many cases each physical M-Bus device will occupy a single
address, in which case device and meter are the same. However, a
single device may occupy more than one M-Bus address, in which
case the device represents multiple sub-meters. For example, the
Relay PadPuls M2 operates as 2 independent meters, each with its
own M-Bus address/ID.
• Communications Timeout – Selects the maximum number of
seconds that the meter is allowed to respond to a request (5–15).
The default value of 5 is acceptable for most meters, but it may be
necessary to increase the time-out for slower meters.
Notes
• XBuilder contains one node per meter or sub-meter, regardless of
how many physical devices exist on the M-Bus network.
• A Primary address of 0 should only be used for preliminary test-
ing of a newly installed device or address clashes may occur with
another meter on the network.