Manualshelf

Instructions

ManualsBrandsANYBUS ManualsRemote MaintenanceBus RJ-45 M-Bus/Modbus-TCP-RJ45 Gateway 80 M-Bus Slaves
31323334353637383940
Troubleshooting 32
Anybus M-Bus to Modbus-TCP Gateway User Manual Doc: HMSI-27-300, Rev: 1.10
6.3.3 Meters are detected but have no data
Some meters may contain an erroneous declaration of the secondary address. This is why these meters
are not addressable for meter readouts, although they are visible in the meter list.
The system parameter MBUS_SELECTMASK makes it possible to mask parts of the secondary address
and replace them with a wildcard character. The version field especially is a frequent cause of this prob-
lem (MBUS_SELECTMASK=4). See 7.4.1
System configuration file.
6.3.4 Scanning takes too long
Under certain circumstances, performing a scan of the M-Bus can take a very long time (>1 h).
• Try working with search masks or limiting the address space to perform a gradual scan.
See 3.1.3
Configuration tab.
• Decrease the value of the system parameter MBUS_MAXRETRY
See 7.4.1
System configuration file.
• Select a different scan mode, either on the
Configuration tab (see 3.1.3 Configuration tab), or
by setting the system parameter MBUS_SCANMODE.
Reversed secondary scan (SECONDARYSCANREVERSE) is often particularly useful to speed up
scanning of the M-Bus.
6.3.5 Gateway restarts occasionally during scan
The gateway is equipped with an internal watchdog to prevent denial of service (DoS). If a scan takes a
very long time, the watchdog may reboot the gateway.
If the scan usually takes a very long time (due to a large number of connected meters or a slow connec-
tion) it may be necessary to increase the value of the system parameter WATCHDOG_SCAN.
See 7.4.1
System configuration file.
Under certain circumstances there can be lots of collisions on the M-Bus, for example if all meters are
responding at the same time. These collisions and the resulting high current draw of the M-Bus slaves
can in exceptional cases trigger a reboot of the gateway.
Try working with search masks or limiting the address space to perform a gradual scan.
See 3.1.3
Configuration tab.
If possible, try to split the bus and scan each bus segment separately.