ModBMS RUD (Request for Unsolicited Data) Updates Debug

Product_Support · ‎2018-09-06

Issue

ModBMS intermittently fails to update certain data points from controllers, leading to potential data inconsistencies.

Product Line

Satchwell BAS & Sigma

Environment

Satchwell ModBMS

Warning

Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance.

Cause

ModBMS may occasionally fail to update specific controller points due to issues in the RUD update mechanism.

Resolution

To diagnose and troubleshoot the issue, enable debug logging in ModBMS:

Steps to Enable Debug Logging

Locate Configuration File:
- Navigate to the ModBMS installation directory.
- Open the ModBMS.cfg file using Notepad or a similar text editor.
Modify Debug Settings:
- Find the [General] section.
- Look for the entry Debug. If it does not exist, add it manually.
- Set the value as follows:
  - <Debug>0</Debug>: No debug logging (default)
  - <Debug>2</Debug>: Logs only changes in RUD updates
  - <Debug>4</Debug>: Logs all RUD updates (recommended for troubleshooting)
Save and Restart:
- Save the changes to ModBMS.cfg.
- Restart the ModBMS application to apply the new settings.
Collect Debug Logs:
- After reproducing the issue, locate the ModBMS.txt file.
- Send this file to Product Support for analysis.
Disable Debug Logging (Optional):
- Based on Product Support's recommendation, you may disable debug logging by setting <Debug>0</Debug> and restarting ModBMS.

Additional Notes

Turning on debug logging increases the size of log files. Monitor disk space if left enabled for extended periods.
Always follow up with Product Support for guidance on interpreting logs and next steps.