Remote Alarm Manager (RAM) – Engine Fails to Start or Shuts Down Unexpectedly

[Product_Support]

Issue

The Remote Alarm Manager (RAM) engine either:

• Fails to start, or
• Shuts down unexpectedly during normal operation.

Product Line

Satchwell BAS & Sigma

Environment

• Satchwell Sigma
• Satchwell BAS 2800+
• TAC Vista
• Satchwell Micronet
• Remote Alarm Manager

Cause

The issue is typically caused by the Log.mdb file growing excessively large. This file logs:

• System alarms
• User actions
• RAM system actions

Since there is no size limit on this file, it can consume excessive memory, leading to RAM instability or shutdown.

1. Resolution

   Manage the Log.mdb File

   To prevent the file from growing uncontrollably:

   • Stop RAM services.
   • Navigate to the Log.mdb file location (commonly found at:
     Sigma\\Data\\Remote Alarm Manager).
   • Delete or rename the Log.mdb file.
   • Restart RAM services – a new Log.mdb file will be automatically created.

   🔁 Best Practice: Perform this cleanup regularly if the system is stable.

2. Adjust Logging Settings

   Reduce the frequency and verbosity of logging to minimize file growth:

   • Navigate to the Debugging screen for the relevant interface (e.g., GSM Modem).

     

   • Set the logging level to one of the following:
     • Nothing – No logging (recommended if RAM is stable)
     • Errors – Logs only error messages (recommended)
     • Normal – Logs low-level operational info
     • Detailed – Logs more in-depth data
     • Verbose – Logs all available information (not recommended for production)

       ✅ Recommendation: Use “Nothing” or “Errors” for stable systems to reduce log file size and improve performance.