Ax60+

The Ax60+ systems have latched alarms as standard however does have the option of disabling alarm latching. It is our hope that the following information will help to avoid confusion when silencing and acknowledging alarms.

Latched Alarms

These will not clear unless acknowledged. For example, if the target gas level increases beyond the alarm threshold, the device will go into alarm and remain like this until the alarm has been acknowledged.

Non-Latched Alarms

These will clear without acknowledgement. For example, if the target gas level increases beyond the alarm threshold, the unit will go into alarm but once the gas returns to safe limits the alarm automatically clears.

Both Latched and Non-Latched alarms can be muted with a single press of the Accept/Test button, but in order to acknowledge a latched alarm the user must first cycle through the display until an ‘*’ is seen, then press and hold the Accept/Test button for 3 seconds (resulting in the ‘*’ changing into a ‘>’.

The video below shows an example of muting and acknowledging a latched alarm

The Ax60+ Alarm/Strobe Unit is IP55 rated.

IP means Ingress Protection, the 2 numbers after indicate to what level the unit is able to protect itself against dust, moisture, liquids and accidental contact. The IP rating for this unit is broken down below;

• 5 – Solids – Dust Protected. Limited ingress of dust permitted. Will not interfere with operation of the equipment. 2 to 8 hours.
• 5 – Water – Protected against jets of water. Limited ingress permitted.

However, the unit is Not Waterproof/Weatherproof for long periods of time, and in direct sunlight the UV light will fade the label on the unit. The Alarm Unit can be mounted outside if it has sufficient protection from the elements.

All relevant Ax60+ document information can be found on the Ax60+ product page.

There are two potential reasons for the Ax60+ to show a FLT16 code on the screen, these are:

1. The sensor unit requires zero and span calibration adjustment (see the service manual for guidance on carrying out this process)
2. The CO2 sensor alarm directions have been incorrectly set.

If your unit is displaying a Flt16, first attempt a zero and span calibration adjustment then power cycle the device. If this is not possible or the issue is not resolved, check to see if it has been correctly configured as detailed below.

The Ax60+ is primarily a breathing air device, as such, the CO2 sensor unit alarms are restricted to only trigger in the ‘high-going’ direction. If a user changes the alarm ‘going’ to ‘low-going’ a FLT16 will ensue.

To clear this fault the following steps should be followed (be aware that only a short period of non-alarm time is available so you’ll need to be quick!!):

1. Power cycle the Ax60+ (turn it off and on again)
2. Wait for the sensors display on the screen
3. Press the Accept/Test button briefly to silence any alarms. Press and hold the top two buttons (Cancel and cycle) until the top level menu is reached.
4. Press the cycle button six times (until sensor config is shown)
5. Press the Accept/Test button. Press the cycle button twice (Alarm direction is shown)Press the Accept/Test button. Select the sensor that had the alarm ‘going’
6. changed (press cycle to move the arrow selector over until the relevant sensor is identified and press the Accept/. test button)
7. Select the alarm that had the alarm ‘going’ changed
8. (press cycle to move the arrow selector over until the relevant alarm is identified and press the Accept/test button)
9. Change the alarm direction to ‘up’ (press the cycle button until the arrow selector points at the up arrow and press the Accept/test button)
10. Press the cancel button five times until the sensors display on screen
11. Acknowledge any faults displayed
12. Power cycle the unit

All relevant Ax60+ document information can be found on the Ax60+ product page.

There are two potential reasons for the Ax60+ to show a FLT16 code on the screen, these are:

1. The sensor unit requires zero and span calibration adjustment (see the service manual for guidance on carrying out this process)
2. The CO2 sensor alarm directions have been incorrectly set.

If your unit is displaying a Flt16, first attempt a zero and span calibration adjustment then power cycle the device. If this is not possible or the issue is not resolved, check to see if it has been correctly configured as detailed below.

The Ax60+ is primarily a breathing air device, as such, the CO2 sensor unit alarms are restricted to only trigger in the ‘high-going’ direction. If a user changes the alarm ‘going’ to ‘low-going’ a FLT16 will ensue.

To clear this fault the following steps should be followed (be aware that only a short period of non-alarm time is available so you’ll need to be quick!!):

1. Power cycle the Ax60+ (turn it off and on again)
2. Wait for the sensors display on the screen
3. Press the Accept/Test button briefly to silence any alarms. Press and hold the top two buttons (Cancel and cycle) until the top level menu is reached.
4. Press the cycle button six times (until sensor config is shown)
5. Press the Accept/Test button. Press the cycle button twice (Alarm direction is shown)Press the Accept/Test button. Select the sensor that had the alarm ‘going’
6. changed (press cycle to move the arrow selector over until the relevant sensor is identified and press the Accept/. test button)
7. Select the alarm that had the alarm ‘going’ changed
8. (press cycle to move the arrow selector over until the relevant alarm is identified and press the Accept/test button)
9. Change the alarm direction to ‘up’ (press the cycle button until the arrow selector points at the up arrow and press the Accept/test button)
10. Press the cancel button five times until the sensors display on screen
11. Acknowledge any faults displayed
12. Power cycle the unit

There is some backwards compatibility:

• Ax60+ CO2 sensor units CAN be used with both Ax60 and Ax60+ central displays.
• Ax60 sensor units CAN ONLY be used with Ax60 central displays.
• Oxygen sensors CAN ONLY be used on the Ax60+ central displays.

See table below for reference: