When the panel reports a fire condition, the sounders activate and can be silenced via the panel display. By default, sounders across the network will resound if a new fire is detected in a different zone to the first activation.
However, if the user programmes the panel to re-sound the sounders from a “new device in fire” (instead of “new zone in fire”), the sounders would not operate across the network and only the local sounders would operate.
This update ensures resound on “new device in fire” now works correctly across a network.
MxPro5 Firmware Release Notes
Our determination to manufacture and deliver a high-quality product, and your valued feedback, allow us to provide you, our ‘Customers’, with the latest features and enhancements available in the industry today.
If there is a function or feature that you want from your control panel, contact us and we will gladly discuss your requirements.
V60-03-05-00
August 2025
V60-03-05-00 Improvements
V60-03-04-00
July 2025
V60-03-04-00 Improvements
When performing a test print, the panel will no longer re-boot.
The AdvancedLive system will now remain live if there is a conflict between cloud messages and signals from AdvancedLive. This means it is easier to determine whether communication fails are due to the panel, the network, or the cloud communications.
The responsiveness of the panel display has been increased when viewing events on the panel.
When using an Apollo CoreProtocol panel, the response time of the loop outputs has been increased so they will activate faster.
The network communications have been made more reliable when there is lots of network data.
Message reliability and network visibility has been improved with a Gen2 MxPro 5 panel is connected to AdvancedLive. Additionally, sounders connected to the panel can now be resounded from AdvancedLive.
V60-03-03-00
April 2025
V60-03-03-00 Improvements
When a CHQ-WSB2 is auto-learned onto a Hochiki panel, it is recognised as a YBO-BSB. If a download is taken using PC-NET-022 configuration tool and manually changed to a CHQ-WSB2 before uploading to the panel, a fault would appear for “Type Change”. The CHQ-WSB2 can now correctly be identified by the panel during an autolearn.
When a calibration was initiated on a Nittan panel, Rate of Rise heat detectors would go into fire. This fix ensures the panel does not enter fire condition when a calibration is initialised.
When using remote indicators on a Hochiki protocol panel, the LEDs would not operate unless programmed within an output group through cause and effect.
This fix ensures the remote indicator LEDs operate correctly, without the need to be programmed within cause and effect output groups.
On a mixed networked system of MxPro5 Gen 1 and Gen 2 panels, CO life safety events were not showing correctly in the log.
If viewing the log of a Gen 2 panel from a Gen 1 panel across the network, AdvancedLive “Not Connected” faults would actually show as a CO life safety event, and CO life safety events would not show the associated text.
If viewing the log of a Gen 1 panel from a Gen 2 panel across the network, CO life safety events would show as “Not Connected”.
This firmware update ensures the correct event is shown in the log, with the correct associated text.
When using false alarm management (FAM) on an Apollo Core protocol panel, and a device goes into fire, the panel will display “Verifying” and the sounders will activate with a verification tone. The pre-alarm LED on the panel display will also illuminate.
If the fire condition is verified by a second zone in fire, the panel would cancel the verification and enter full fire, but the sounders would still be active with the verification tone instead of the fire tone. The pre-alarm LED would also remain active.
An update has been included in this firmware update so that the sounders will change from a verification tone to a fire tone once the fire has been confirmed by a second zone in fire. The pre-alarm LED will now turn off once the fire is confirmed and the panel enters full fire.
On Apollo protocol MxPro5 panels, when using Discovery multi sensors with the heat point enabled, the panel would report a “Too Low” fault against the heat point sub-address. This was because the panel incorrectly retrieved the device analogue value.
This update ensures the panel retrieves the correct analogue value from enabled heat points so that the correct device state is reported.
V60-03-02-00
January 2025
V60-03-02-00 Improvements
When an Apollo protocol panel has been programmed to change device sensitivities according to a time clock, the pre-alarm value would return to 20 every time the programming was uploaded into the panel. This would require a manual device sensitivity change through the panel menu.
Now, when the programming is uploaded into the panel, the pre-alarm value remains as programmed instead of returning to 20.
Fault tolerant network earth faults may not be reported correctly due to delays in communication timing. Additionally, wiring faults on a fault tolerant network were not reporting correctly.
A change has been in the way a fault tolerant network communicates so faults with the network wiring can now be reported correctly.
V60-03-01-00
November 2024
V60-03-01-00 Improvements
Outputs could not be activated correctly through AdvancedLive. Now, if a user of AdvancedLive selects to activate an output, this will correctly be sent to the panel network.
Also, AdvancedLive would occasionally show sites as being offline when they are actually online. This reporting has been fixed so AdvancedLive can now correctly show the site status.
V60-03-00-00
November 2024
V60-03-00-00 New Features
On Apollo protocol panels, the FastTest feature has been updated to include support for the Apollo tri-sensor. When viewing the device states (Access level 3 -> “Loop” -> “View/Edit”), clearer text has been added to indicate which devices have passed and failed.
When a control panel re-boots, a “CPU reset” is recorded in the log. The firmware version will now be displayed next to the “CPU reset” event.
Configuration changes logged
While the panel configuration is being updated, the panel will log a “Config updating” event in the log. Once the configuration has successfully been uploaded, “Config updated” will be recorded in the log.
MxPro 5 Gen 2 base cards have AdvancedLive connectivity built in, meaning only a single node on the network is required to be the new generation base card in order to establish an AdvancedLive connection. Previously, a LiveMod and BMS interface were required to connect a panel network to AdvancedLive.
Connectivity stability has also been improved.
PC-NET-022 configuration software allows users to enter user notes. Up to 950 characters can be entered and these notes are now retained when transferring the configuration to and from the panel.
When a download is taken onto PC-NET-022 configuration software, the date and time of the last upload is now recorded and displayed within the “Product Summary” section.
To ensure the panel firmware is compatible with the latest version of configuration software, a feature has been added where the configuration software will block communication and display a warning if the incorrect version of PC-NET-022 configuration software is used.
In this release, the minimum version the panel expects to see is V12.00.
V60-03-00-00 Improvements
On an AV protocol panel where wireless devices are used, the wireless translator reports analogue values to the panel, and the panel uses these analogue values to indicate fires, faults, pre-alarm etc.
The text associated with these analogue values (fire, fault, pre-alarm etc.) has been added into all relevant sections of the panel, where previously this was missing.
Nittan sounders and beacons now activate as programmed during alarm verification. Previously, they did not turn on during alarm verification where they were programmed to turn on.
When a panel has been left in diagnostics logging mode and it is re-booted, the panel logged faults that did not exist on the panel display. These faults were “Loop card incompatible”, “Loop card device missing” and “Earth fault”, which may have existed for a brief period of time while the panel was initialising.
Now, these faults are ignored until the panel has fully initialised and are no longer logged during power up. Loop card firmware will also need to be updated to v4.06 or greater.
AV protocol device have a feature where they can be tested using a magnet. However, if the devices are programmed to use a non-latching input action (e.g. general alarm, fire evacuate, pre-alarm), they will not reset after the test until a panel re-boot is carried out.
Now, when the “Reset” button is pressed on the panel, all devices will reset and come out of test, irrespective of input action.
Please refer to “680-169-01A MxPro 5 Argus Vega” for further information on magnet testing.
When an AV panel is networked to a BMS interface, loop outputs can now be manually turned on from the graphics software, through the BMS. Previously, this was not possible.
Also, when AV and Nittan protocol panels are networked to a BMS interface, they were able to receive “Fire” signals but not “Evacuate” and “Alarm” signals. AV and Nittan protocol panels can now receive and respond to “Evacuate” and “Alarm” signals sent from the BMS interface.
After erasing the panel configuration, if a download was taken using PC-NET-022 configuration software, the network sector programming was showing incorrect default settings. This has been changed so the correct default settings are applied where only local sectors will be ticked.
On an Apollo Protocol panels, sounders were incorrectly showing “Device missing” after a configuration upload. This fault will no longer appear until devices have initialised.
When the panel is re-booted, Core Protocol devices incorrectly report “Unapproved device” until they have initialised. This fault will no longer appear when Core Protocol devices are initialising.
When viewing devices from the panel display (Access level 3 -> “Loops” -> “View/Edit”), sensitivity options were showing for all devices, irrespective of device type and whether the sensitivity could be adjusted.
The sensitivity of devices can now only adjusted if the device supports this. Please refer to “860-167-07A MxPro 5 Apollo” for device sensitivity options.
Axis-WSM devices have a built in microphone test feature. However, if the sounder is not fitted correctly, the test will fail and the panel will display a fault.
The microphone teat feature is now disabled as default and can be enabled from within PC-NET-022 configuration software v12.2 or greater.
If a CHQ-POM is connected to a Hochiki panel and the output of this device is inverted, the output voltage of the device did not increase from 0V to 24V. A change has been made so the device output voltage increases when the output has been inverted through PC-NET-022 configuration software.
In access level 2 when a user tries to gain access to a panel menu using a password and an incorrect password was entered, the panel displayed “Password not recognised”. Upon pressing tick, the user level changed to access level 1. A change has been made so the current access level is retained and access is not given to the requested menu.
When a programmable input is programmed to “disable zone”, it would only disable the inputs in that zone which were fire inputs. However, when manually disabling zones through the panel menu, all inputs in that zone were disabled, irrespective of the input action.
Now, when either a programmable input or manual selection has been made to disable a zone, all inputs within that zone will be disabled, irrespective of the input action.
The panel checksum number is a unique identifier of the configuration programming stored within the panel. When a download is taken using PC-NET-022 software, the checksum number is displayed on the download and matches the panel checksum number (until programming changes are made).
If no configuration changes have been made and the configuration is uploaded to the panel, the checksum number would change if a different version of configuration tool was used to upload.
For example, if a download was taken using PC-NET-022 v12.1 and an upload was complete using PC-NET-022 v12.2, the checksum would change even though no programming changes were made, as the configuration software versions are different.
A change has been made so the checksum number remains the same when a different version of configuration software has been used to upload into the panel, unless a programming change has been made.
After a panel re-boot, Apollo Discovery Open Area sounders would report “Device missing” while the loop card powers up. The panel now waits for loop cards to fully power up before displaying loop device faults.
Hochiki CHQ-PCM devices will now be able to report HVAC faults if the device has failed to open, close or run as expected.
On Hochiki protocol panels, the first alarm condition reports within 10 seconds of device activation. An improvement has been made to ensure all subsequent alarm conditions also notify the panel with 10 seconds of each device activation, while still maintaining prompt output activations.
Also, group control is now supported on all output types. Previously this was only available for sounders and beacons.
Please refer to “680-168-05 MxPro 5 Hochiki” protocol addendum for further information.
An improvement has been made to the order in which outputs turn on from an activation. Sounders and beacons in the zone of origin have the highest priority and turn on first. Then all other sounder and beacons will activate. All relay outputs will turn on last.
The “Sounder Disabled” LED and any output group programmed to operate from a sounder being disabled will now activate from any sounder being disabled, even if no sounders have been programmed with the “May silence” enabled. Previously, if “May Silence” was unticked and that sounder was disabled, the “Sounder Disabled” LED and the programmed output group would not turn on.
MxPro 5 panels are approved to EN54-13 which means the loop and sounder circuits are monitored to ensure they will operate as intended during a fire condition. As this standard is not mandatory in the UK and Ireland, this feature is now disabled as default. It can be turned on from the front of the panel (Access level 3 -> “Next Menu” -> “EN54-13”) or through PC-NET-022 configuration software.
Please refer to “680-212-01 EN45-13 Overview” for further information on EN54-13.
When connected to the panel using a direct USB lead, an earth fault will show if the PC is connected to mains i.e. when it is charging. When in access level 3, the panel will ignore this earth fault for 5 minutes following a new connection.
Faults on an AV protocol panel will now be reported within 90 seconds.
V60-02-01-00
July 2024
V60-02-01-00 Improvements
When using the EN54-13 monitoring settings within the panel, the loop current can now be set to a minimum of 25mA. Previously, this was set to 100mA.
Please refer to “680-212-01 EN45-13 Overview” for further information on EN54-13.
On a panel network, information is not sent or received by any panel in access level 3 and the panels will only send and receive signals when in access level 1 or 2. When panels are networked to a BMS interface and an event comes through from the graphics system (fire, fault, disable, enable etc.), only panels in access levels 1 and 2 will receive this information.
If a panel was in access level 3 it did not receive this information, and when it came out of access level 3 into level 2, the signal was not re-sent. Therefore, even though the panel is then in access level 2, it still did not receive the event from the BMS interface.
A fix has been made so when a panel is taken out of access level 3 and put into access level 2, events from the BMS interface are re-sent, so the panel is now able to receive an update across the network to respond to the event (enable, disable, fire, fault etc.).
V60-02-00-00
June 2024
V60-02-00-00 Improvements
If a detector has alarm verification enabled, the verification countdown timer will start when the device reaches high-alarm. Previously, this countdown timer would start when the device enters pre-alarm state. This improves the accuracy of the alarm verification timer.
When Gen 1 and Gen 2 panels are networked as part of a standard network, the was a delay in the network establishing and network faults may have been displayed during this time. Also, the network would occasionally not establish and a permanent network fault would be displayed.
The standard network has been improved so it can establish a connection quicker, before network faults are displayed. The standard network now operates as expected.
When Apollo Soteria sounder bases and beacon bases are in the same output group, the beacons will now synchronise with the sounders and activate at the same time. Previously, the beacon bases were delayed in turning on until after the sounders had activated.
Networked panels will now log device text against events which originated on a panel across the network. Historically, the device text was only logged for local activations.
After a panel re-boot, when the panel is in normal operation without any faults, “Device initialising” is displayed next to the devices when in the “View” menu. However, as soon as an event comes through, “Device initialising” would disappear and the device status would change to show the event. To improve visibility, “Device initialising” will now be displayed at the top of the “View” menu to indicate if any devices are still initialising.
MxPro 5 panels allow the loop numbers to be changed for easier fault finding and reporting. For example, on a 4-loop panel, the loops will be numbered from 1-4 as default but this can be changed so the loops indicate as loop numbers 5-8.
When the loops are re-numbered and the panel displays a “New device” fault, the original loop number was showing in the log and on the panel display instead of the new loop numbers i.e.5-8.
Now, if the loops are re-numbered, a “New device” fault will correctly show the re-numbered loop number instead of the original loop number.
Note, the firmware on all network panels will need to be updated to v060-03-00-00 or greater to fully support this improvement.
When AV protocol panels are using wireless devices, the wireless translator reported as a zone monitor. This has been changed so the device can correctly report as a radio interface.
Apollo wireless sounder bases and relay modules were unable to report the correct battery fault messages. For example, a battery fault would display as a generic device fault. Accurate device states will now be shown on the panel display and in the log.