I am seeking assistance with a technical issue surrounding the integration of the ISTA WATER METER MBUS MODULE with PXC001.E.D using Relay PW60 level converter. The readings on the water meter do not align with the readings in the software, despite some data appearing on MB Sheet that is increasing linearly. Additionally, the water meter loses communication a few hours after software integration, while energy meters from a different manufacturer in the same loop are functioning correctly. There are 6 to 8 water meters and 3 to 4 energy meters connected in one loop, with 3 loops connecting to one Mbus to RS 485 converter. Various attempts have been made to address the issue, including reducing the number of water meters in a loop, connecting water meters as standalone, and avoiding star connections when connecting all devices in the loop. Regrettably, the issue persists. The software used for scanning and integration includes MB Sheet and Siemens Xworks Plus.
I may not be well-versed in your particular hardware, but I have encountered devices that can freeze if they are polled too quickly multiple times. In some cases, lowering the polling frequency was necessary, while in another instance, a firmware upgrade from the manufacturer resolved the issue. How are you reestablishing communication once it halts?
It sounds like you've already done a comprehensive assessment of the situation – good job on that. Now, considering the symptoms you've described, the problem may be linked with the ISTA water meter itself or the Mbus module tied to it. Firmware/version compatibility or calibration can sometimes be an issue. Start by checking if there are any firmware updates available that you haven't applied yet. Then, try to verify if the values reported by the ISTA meter, when read directly from the device, match the data seen on MB Sheet. If the meter readings are correct when read independently from any system integration, the issue might be with the software or the communication protocol, as it might not interpret the data properly. Sometimes the register mapping in software does not correspond perfectly with the meter's values, causing such discrepancies. Lastly, check the termination resistors on the Mbus to RS 485 converter and wiring, as improper termination and signal reflection could cause communication failure. Good luck!
It sounds like you've certainly done a thorough job troubleshooting already, but based on what you've shared, it's possible that there could be an issue with the compatibility of the ISTA Water meter MBus module and PXC001.E.D. Additionally, a potential data transmission error could occur when readings are communicated from the water meter to the software. It might be beneficial to confirm the compatibility of all components involved, or perhaps check if there are any recent firmware updates for your devices. You could also try to adjust the refresh-rate at which your MB Sheet software is reading from the ISTA Water Meter. I recommend reaching out to the technical support of ISTA and Siemens directly, as they'll have in-depth visibility into their products’ behaviour under certain scenarios.
Ensuring compatibility among different devices can be quite challenging. One possibility that comes to my mind is a mismatch between the data transmission rate of your water meters and the software. I would suggest checking the baud rate settings on both ends to make sure they match. Another likelihood could be related to signal degradation due to either the intrinsic design or some sort of interference. Is there any deterioration noted in the quality of the signal as it makes its journey through the system? Also, are you using any filters or repeaters? In some scenarios, using repeaters can help boost and clean up the signal periodically. Lastly, given the complexity of your system and the extent of the issue, I would recommend reaching out to technical support from the manufacturers on both sides for a detailed diagnostic. They are often the best resource for complex, product-specific issues like this.
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: - This discrepancy could be due to communication errors or integration issues between the water meter, MBus module, and PXC001.E.D. It is recommended to check the configuration settings and ensure proper communication protocols are being followed.
Answer: - The loss of communication could be caused by compatibility issues, signal interferences, or faulty hardware. Troubleshooting steps may include checking the connections, verifying power supply stability, and investigating potential conflicts with other devices in the loop.
Answer: - Several attempts have been made, such as reducing the number of water meters in a loop, connecting water meters as standalone devices, and avoiding star connections when connecting all devices in the loop. Despite these efforts, the issue persists, indicating a more complex underlying problem.
Answer: - The software tools mentioned in the discussion thread are MB Sheet and Siemens Xworks Plus. These tools are utilized for monitoring, collecting, and integrating data from the water meters and energy meters connected in the loop.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.