What to do if Vigilant MX1-Au Fire Alarms buzzer is not functioning?
If the buzzer is not functioning, first check if the buzzer has been muted or disabled, and verify the configuration operates the buzzer. Next, check and reconnect the buzzer lead if it is disconnected. If neither of these resolves the issue, the LCD/Keyboard may need to be replaced due to a hardware fault.
What to do if Vigilant MX1-Au Button LED flashes but does not change state?
If the button LED flashes but does not change state, it means communication between the DSS master and the MX1 main board or network communications with the remote DSS controls have failed. Check the communication cable from the master control board to the MX1 main board. Check the network communications if the control is a ‘Duplicate’.
What causes Vigilant MX1-Au Fire Alarms internal sounder to sound continuously?
If the internal sounder sounds continuously with no fault present, it indicates a hardware fault. Replace the LCD/Keyboard.
What does Zone not configured in database mean on Vigilant MX1-Au?
If your Vigilant Fire Alarms system displays 'Zone not configured in database', it means the SID specified by the zone number that has been entered does not appear in the list of SIDs in this panel’s configuration database. If you need to recall a zone from the specified SID from this panel, you need to add the SID to the configuration data file.
What to do if Vigilant MX1-Au Fire Alarms display Command not sent. Queue is full?
If you get the message 'Command not sent. Queue is full' on your Vigilant Fire Alarms, it suggests a problem with the network connection. Check that the network connection is working. Restarting the local MX1 panel might also resolve the issue.
What does ERROR: UNABLE TO RECEIVE CONFIG DATA mean on Vigilant MX1-Au Fire Alarms?
If your Vigilant Fire Alarms system shows 'ERROR: UNABLE TO RECEIVE CONFIG DATA', it means the LCD/Keyboard communications are working, but the Controller won't send a valid configuration message to the Keyboard. This is likely because the LCD/Keyboard and Controller board firmware versions are incompatible. You should install compatible firmware versions in both the LCD/Keyboard and Controller. Contact your service company for assistance.
What does PreAlarm mean on Vigilant Fire Alarms?
If your Vigilant Fire Alarms system indicates a 'PreAlarm' condition, it means that one of the points mapped to the zone is in pre-alarm. Use the history display or the off-normal recall menu to identify which point is in pre-alarm. You can also check the analogue values of the point in pre-alarm using the values menu.
What to do if Vigilant Fire Alarms LCD shows 'ERROR: CANNOT COMMUNICATE WITH MAIN BOARD'?
If the LCD shows “ERROR: CANNOT COMMUNICATE WITH MAIN BOARD”, check the links on the LCD/keyboard and the cabling. Also, verify the controller indicators and ensure the controller firmware is not corrupt and is operating. Press SILENCE and recheck when programming is completed. You may need to replace or re-fit the components.
What to do if Vigilant MX1-Au shows 'MX Loop overload' point in fault?
If the “MX Loop overload” point is in fault, use the MX Loop Status Display to check the voltage and current being drawn by the loop. Check for additional loads resulting from recent system changes, such as additional devices or sounder bases. Re-validate the loop design using MX1Cal.
Why is the Vigilant Fire Alarms POWER ON LED flashing?
The POWER ON LED flashes when the mains power is off or has failed. Check the mains supply. If the mains supply is present, verify that the MX1 PSU is functioning correctly.
Provides instructions on operating the MX1 panel and understanding its displays and conventions.
Describes the core functions and capabilities of the VIGILANT MX1 fire detection system.
Details the different access levels and their associated command permissions.
Step-by-step guide for managing alarms using the Fire Brigade Panel (FBP) controls.
Explains how the MX1 indicates alarm presence and displays alarm details.
Procedures for resetting alarms after investigation and clearing conditions.
Describes how the MX1 indicates faults and how to view fault details.
Explains how to view disabled items (zones, points) and their status.
Details how to access and interpret the MX1's event history log.
Describes the format and meaning of zone-specific event messages.
Explains the format and meaning of point-specific event messages.
Guides on recalling and viewing the status of off-normal points and zones.
Procedures for resetting zones and points to clear alarm or fault states.
Instructions for disabling or enabling individual or ranges of points/zones.
Details on performing various tests on zones, including alarm and fault tests.
Step-by-step guide to access critical service functions using User Code and PIN.
Checking power supply voltage, current, and battery status.
Monitoring the voltage and current status of MX addressable loops.
Procedures for replacing MX devices and automatic re-addressing.
Enabling commissioning mode to reduce detector test times.
Restarting the MX1 panel from the LCD, requiring Access Level 3.
Allows remote panel operation as if standing in front of it via the network.
Displays communication status of network interface devices.
Shows status of network faults, including path and communication failures.
Provides a guide to interpreting LCD messages and taking corrective actions.
Instructions for installing the MX1 panel within its cabinet.
Details on connecting the dedicated mains feed to the MX1 cabinet.
Guidance on connecting batteries for system standby power.
Instructions for wiring MX addressable devices to the MX1 controller.
Steps for the initial power-up sequence and basic checks.
Provides overall technical specifications for the MX1 system.
Lists devices compatible with the MX1 analogue loop.
Detailed descriptions of all in-built points and their functions.
General| Brand | Vigilant |
|---|---|
| Model | MX1-Au |
| Category | Fire Alarms |
| Language | English |
To Next Page
