Fire AlarmEngineers Hub
โ— Offline ready
Advanced
MANUFACTURER KNOWLEDGEBASE

Advanced Engineer Guide

MxPro 5 / MxPro 4 / Axis EN: practical field notes for testing, disablements, logic and restoration. Menu wording can vary by firmware and site configuration.

Before changing a live system: agree the test/disablement with the responsible person, identify any ARC/fire-routing connection and plant interfaces, decide what must remain operational, record every temporary change, and restore/verify everything before leaving.
ADVANCED

MxPro 5 / MxPro 4 / Axis EN

Advanced panels are widely used as multi-protocol control equipment. Always confirm the installed basecard/loop protocol before using device-specific addressing or diagnostics.

Protocol / ecosystemMulti-protocol: Apollo, Hochiki ESP, Argus Vega, Nittan

One-man / walk test

  1. Enter the authorised test/commissioning menu for the installed family.
  2. Select the required zone/area walk test rather than globally suppressing outputs where possible.
  3. Advanced states its one-man walk test normally gives a short automatic alarm period; relays do not operate by default.
  4. Test each device and confirm its text, zone and required audible/visual response.
  5. Exit walk test and review the panel for any remaining TEST or DISABLE indications.

Disable / enable

  1. Use the panel Enable/Disable functions for the smallest practical scope: device/input, zone, output purpose or group.
  2. Check whether timed automatic re-enablement has been configured; do not rely on it unless site procedure permits.
  3. After enabling, review active disablements across the relevant network sector and confirm normal status.

Cause & effect / groups

  1. MxPro 5 supports standard mapping and flexible logic; networked systems can pass input/output information between panels.
  2. Use sectors, time clocks and disablement groups deliberately; document what they include.
  3. Use the configuration tool/cause-effect checker for complex systems and retain a revision-controlled site file.

Engineer notes

  1. MxPro 5 can network panels using different supported protocols, but each individual panel/loop arrangement must match its configured protocol.
  2. Use trace logging/diagnostics for intermittent data issues rather than repeated blind resets.
  3. Record service-due and firmware/configuration information before making programming changes.
Return to service:Exit test modeClear temporary disablementsRestore sounders / outputsRestore fire routing / ARCRestore delays / time controlsProve a normal event pathCheck panel = normalRecord work
PRIMARY REFERENCES

Manuals and manufacturer resources

External links are references only and require internet access. The knowledgebase itself remains usable offline.