MxPro 5 Firmware Releases

When the panel reports a fire condition [in a particular zone], the sounders [in that zone] activate and can be silenced via the panel display.
If a new fire is detected in a different zone to the first activation, sounders across the network will re-sound by default.
If the default settings have been changed, and the panel has been programmed to re-sound the sounders from a ‘New Device in Fire’ instead of ‘New Zone in Fire’, only the local sounders would operate instead of the sounders across the network.
This update ensures that sounders re-sound correctly across the network when ‘New Device in Fire’ is programmed.

The panel no longer re-boots when performing a test print.

AdvancedLive now remains live if there is a conflict between cloud messages and signals from AdvancedLive. This means it’s easier to determine whether communication fails are due to the panel, the network, or the cloud communications.

We’ve also improved message reliability and network visibility when a Gen2 MxPro 5 panel is connected to AdvancedLive. Plus, sounders connected to the panel can now be resounded from AdvancedLive.

The responsiveness of the panel display has been increased when viewing events on the panel.

We’ve improved the reliability of network communications when there is a lot of network data.

Initialising calibration on a Nittan panel no longer causes rate of rise heat detectors to enter fire condition.

When using remote indicators on a Hochiki protocol panel, the LEDs now operate without needing to be programmed within cause and effect output groups.

On a mixed networked system of MxPro 5 Gen 1 and Gen 2 panels, events and text now show correctly in the log.

If viewing a Gen 2 panel log from a Gen 1 panel across the network, AdvancedLive no longer shows ‘Not Connected’ faults as CO life safety events, and CO life safety events now show the associated text.

If viewing a Gen 1 panel log from a Gen 2 panel across the network, CO life safety events no longer show as ‘Not Connected’.

When using Apollo protocol MxPro 5 panels with Discovery multisensors and the heat point enabled, the panel no longer reports a ‘Too Low’ fault against the heat point sub-address.

The panel now retrieves the correct analogue value from enabled heat points so that the correct device state is reported.

When an Apollo protocol panel has been programmed to change device sensitivities according to a time clock, the pre-alarm value no longer returns to 20 every time the programming is uploaded into the panel. This means you no longer need to change device sensitivity through the panel menu.

We’ve improved communication timing so that fault-tolerant network earth faults and wiring faults are reported correctly.

Outputs activated in AdvancedLive are now consistently communicated to the panel network.

We’ve also improved AdvancedLive status indication so that occasional incidents of AdvancedLive online sites appearing to be offline no longer occur.

While the panel configuration is being updated, the panel will now log a ‘Config Updating’ event in the log as well as a ‘Config Updated’ event once the configuration has been successfully uploaded.

On an AV protocol panel using wireless devices, 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.

When a panel has been left in diagnostics logging mode and it is re-booted, the panel no longer displays faults that did not exist on the panel display.

These faults, ‘Loop Card Incompatible’, ‘Loop Card Device Missing’ and ‘Earth Fault’, may have existed for a brief period while the panel was initialising but are now 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 devices have a magnet test feature. If the devices are programmed to use a non-latching input action (e.g. general alarm, fire evacuate, pre-alarm), they will now reset and come out of test, irrespective of input action, when the ‘Reset’ button is pressed on the panel.

For further information on magnet testing, please refer to:

• MxPro 5 – 680-169-01A MxPro 5 Argus Vega
• Axis EN – 680-165V-07 Axis EN Product Manual

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 are now able to consistently receive ‘Evacuate’ and ‘Alarm’ as well as Fire’ signals.

If a download is taken using PC-NET-022 configuration software after erasing the panel configuration, the network sector programming now shows the correct default settings and only local sectors will be ticked.

On Apollo protocol panels, sounders will no longer show ‘Device Missing’ after a configuration upload 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), the sensitivity of devices can now only be adjusted if the device supports this. Previously, sensitivity options were showing for all devices, irrespective of device type and whether the sensitivity could be adjusted.

Please refer to ‘860-167-07A MxPro 5 Apollo’ for device sensitivity options.

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 levels 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 receive this information.

A change has been made to ensure that 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 receives an update across the network to respond to the event (enable, disable, fire, fault etc.).

Axis-WSM devices have a built-in microphone test feature. This test feature is now disabled by default to prevent the panel from displaying a fault when incorrectly fitted sounders fail the test. The feature can be enabled from within PC-NET-022 configuration software v12.2 or greater.

When a CHQ-WSB2 is auto-learned onto a Hochiki panel, it is recognised as a YBO-BSB. If a download is taken using the PC-NET-022 configuration tool and manually changed to a CHQ-WSB2 before uploading to the panel, a ‘Type Change’ fault no longer appears and CHQ-WSB2 can now be correctly identified by the panel during an auto-learn.

If a CHQ-POM is connected to a Hochiki panel and the output of this device is inverted through PC-NET-022 configuration software, the output voltage of the device now increases from 0V to 24V.

In access level 2 if a user tries to gain access to a panel menu and enters an incorrect password, when ‘Password Not Recognised’ displays, the user level will remain unchanged.

When ‘Disable Zone’ is either programmed or conducted manually, all inputs in that zone will now be disabled, not just fire inputs.

The configuration programming stored within the panel has a unique identifier – the checksum number. When a download is taken using PC-NET-022 software, the checksum number is displayed on the download and matches the panel checksum number

We have made updates to ensure that the checksum number remains the same even when a different version of configuration software is used to upload into the panel. This ensures that only time the checksum number changes is when configuration changes are made.

For example, if a download is taken using PC-NET-022 v12.1 and an upload is completed using a different version e.g. PC-NET-022 v12.2, the checksum number will now remain unchanged (as long as no programming changes are made).

After a panel re-boot, Apollo Discovery Open Area sounders no longer 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 within 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-04 MxPro 5 Hochiki protocol addendum for further information.

We’ve improved 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 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 no longer shows 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 are now consistently reported within 90 seconds.

We’ve updated the FastTest feature on Apollo protocol panels to include support for Apollo’s Tri-Sensor. We’ve also added clearer text making it easier to see which devices have passed and failed when viewing the device states (Access level 3 -> ‘Loop’ -> ‘View/Edit’).

When a control panel re-boots, a ‘CPU Reset’ is recorded in the log. The firmware version will also now be displayed next to the ‘CPU Reset’ event.

Any user notes (up to 950 characters) you’ve entered in the PC-NET-022 configuration software are now still available to you when transferring the configuration to and from the panel.

The date and time of the last upload is now recorded and displayed within the ‘Product Summary’ section when you take a download within PC-NET-022 configuration software.

The configuration software now blocks communication and displays a warning if the incorrect version of PC-NET-022 configuration software is used. This ensures the panel firmware is compatible with the latest version of the ConfigTool.

In this release, the minimum required version is V12.00.

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.

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, there is no longer a delay in the network establishing, and network faults are now not displayed during this time. In addition, the standard network has been improved so it can establish a connection faster and before network faults are displayed.

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.

Previously, as soon as an event came 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 and Axis EN panels allow you to change the loop numbers for easier fault finding and reporting. For example, on a 4-loop panel, the loops will be numbered from 1-4 as default but can be changed to loop numbers 5-8.

Now, if the loops are re-numbered, a ‘New Device’ fault will consistently show the re-numbered loop number rather than the original loop number.

Please note, the firmware on all network panels will need to be updated to v60-03-00 or later to fully support this improvement.

When AV protocol panels are using wireless devices, the wireless translator consistently reports as a radio interface. This update addresses a radio interface occasionally reporting as a zone monitor.

Apollo wireless sounder bases and relay modules now consistently report the correct battery fault messages. This update addresses cases where a battery fault would display as a generic device fault. Accurate device states now show on the panel display and in the log.

You no longer need a ‘LiveMod’ and BMS interface to connect to AdvancedLive. MxPro 5 Gen 2 base cards have AdvancedLive connectivity built in via Ethernet, so you only need a single node on the network to establish an AdvancedLive connection.

We’ve also improved connection stability.