Hardware Power and Bottom LCD Display Diagnostics
When commissioning the SOLT SR5-MPR PC Monitoring Receiver, confirm that the external AC/DC power supply is functioning correctly. The receiver requires the designated AC 110–240V input to DC 12V / 1A output adapter connected securely to the DC barrel jack. If the unit fails to initialize, inspect the AC mains outlet and verify voltage stability.
The unit features a 1.3-inch LCD display located on the bottom/back panel of the glossy-black and white enclosure. This screen indicates operational status and mode settings. If the 1.3-inch LCD does not illuminate upon connecting the DC 12V power supply, test the adapter output with a multimeter or inspect the DC connector for mechanical seating issues before escalating hardware replacement.
USB-to-Serial Interface and Virtual COM Port Conflicts
The SR5-MPR communicates with host personal computers running Windows operating systems (compatible with Windows XP, Vista, 7, 8, 10, and 11 in 32-bit and 64-bit architectures) via an RS-232 serial or USB-to-serial converter cable. If the SOLT PC Monitoring software cannot establish communication with the receiver, follow these verification steps:
- Open Windows Device Manager and expand the Ports (COM & LPT) category.
- Locate the USB Serial Port entry. If a yellow exclamation mark or error code is displayed, reinstall the dedicated USB-to-serial converter cable driver provided on the installation media.
- Verify the assigned virtual COM port number. The SOLT PC Monitoring program must be configured to match the exact COM port assigned by the operating system.
- If the COM port is assigned a high port index (such as COM12 or higher) that the software interface cannot poll, reassign the port in the advanced port properties to an open lower number (e.g., COM1 through COM4).
- Resolve any port conflicts caused by legacy peripheral hardware or virtual serial emulation software.
Firebird 2.1 Database Service Initialization
The SOLT PC Monitoring application relies on the Firebird 2.1 relational database engine to log incoming bell transmissions, manage system configurations, and record timestamps. If the application displays database connection errors upon launch or fails to log incoming calls:
- Open Windows Services (services.msc) and check that the Firebird Server - DefaultInstance service is running and set to start automatically.
- Ensure that the Firebird 2.1 program files or configuration directories have not been altered, modified, or quarantined by host endpoint security software.
- Regularly verify database integrity and schedule automated backups of the call history database to non-volatile external storage, preventing data loss during host OS maintenance.
RF Signal Reception and 434 MHz Dipole Antenna Issues
The SR5-MPR operates on the 434 MHz band (433.92 / 434.65 MHz) using FSK / GFSK digital modulation to capture omnidirectional (360-degree) signals. If the receiver fails to register wireless calls from compatible SOLT call buttons (such as SB3, SB5, SB6, SB7, or SB9 series):
- Check the external dipole antenna attachment on the 146 mm × 90 mm × 32 mm receiver body. Ensure the antenna is threaded tightly and oriented vertically to maximize RF reception.
- Ensure the receiver is positioned away from large structural metal enclosures, high-voltage electrical panels, or dense concrete columns that cause RF shielding.
- For expansive, multi-floor, or industrial plant installations where transmitter distances exceed direct RF coverage, integrate SOLT SR5-BPR signal repeaters/transceivers to capture and retransmit 434 MHz data packets to the receiver.
- If a specific wireless call bell fails to trigger data capture while others register normally, verify that the call button's internal cells required (they are not included) are fully charged and delivering adequate operating voltage.
Call Registration and 'Dealing Time' Escalation Alarms
The SOLT monitoring program supports registration for up to 500 to 1,000 wireless call button endpoints. If an active call button triggers an RF transmission but does not reflect on the PC monitor screen, open the software configuration console and verify that the button's unique 6-digit chip ID and input key code value have been entered correctly.
If the host PC emits continuous audible siren alerts through the PC speaker, this is an automated escalation notification rather than a system fault. The siren activates when an unaddressed call exceeds the user-configured 'Dealing Time' threshold, notifying supervisors that response time limits have lapsed.
