This work is protected under Title 17 of the United States copyright code and is the sole property of Respironics.
No part of this document may be copied or otherwise reproduced, or stored in any electronic information
retrieval system, except as specifically permitted under United States copyright law, without the prior written
consent of Respironics.
In the U.S. and Canada
Respironics California, Inc.
2271 Cosmos Court
Carlsbad, CA 92011
USA
1-800-345-6443
For Technical support, contact:
Respironics, Inc. Customer Service
Within the U.S.A. 1-800-345-6443
Outside the U.S.A. 724-387-4000
Facsimile 724-387-5012
service@respironics.com
The BiPAP Focus Non-invasive Ventilator is a microprocessor-controlled,
electrically powered mechanical ventilator. The BiPAP® Focus™ Ventilator
System provides noninvasive ventilation for adult (over 30 kg or 66 lbs.)
patients for the treatment of respiratory insufficiency and distress, and
obstructive sleep apnea. The BiPAP Focus is appropriate for acute, sub-acute,
and intra-hospital transport settings.
The BiPAP Focus System is intended for use with nasal and full face masks.
The BiPAP Focus is not intended to be a life-support device.
The BiPAP Focus Ventilator meets or exceeds all applicable safety
requirements, consensus guidelines, US regulatory statutes, and international
regulatory standards for life support/mechanical ventilation devices.
Read this manual thoroughly prior to performing service or maintenance on the
BiPAP Focus Ventilator. This manual contains advanced troubleshooting,
calibration, and maintenance instructions for the BiPAP Focus. All
maintenance and repair work should be performed by qualified biomedical
technicians who have received appropriate training and authorization to
provide maintenance, repair, and service for the BiPAP Focus.
Review the operating instructions for the BiPAP Focus Ventilator before
running tests, checking operational readiness, or initiating patient use. These
instructions include important information about ventilator safety and
operation.
For additional information about accessories or related equipment, such as
humidifiers and remote alarm systems, refer to the appropriate instruction
manual prior to operating with the BiPAP Focus Ventilator.
The BiPAP Focus Operator’s Manual for the BiPAP Focus Ventilator lists all
applicable warnings and cautions. Review these notices thoroughly before
operating the ventilator.
Where to Go for HelpFor Customer Service and Product Support contact:
Respironics, Inc.
USA telephone: 1-800-345-6443
USA: 1-800-886-0245
International telephone: 724-387-4000
International fax: 724-387-5012
service@respironics.com.
clinical@respironics.com.
www.respironics.com.
Warnings, Cautions, and Notes are used throughout this manual to
identify possible safety hazards, conditions that may result in
equipment or property damage, and important information that must be
considered when performing service and testing procedures on the
BiPAP Focus.
WARNING:A condition that could cause injury to a patient, operator or technician if
the operating instructions in this manual are not followed correctly.
CAUTION:A condition that could cause damage to, or shorten the service life of,
the device.
NOTE:Important information concerning the construction or operation of the
device.
Warnings•To assure the safety of the service technician and the specified
performance of the device, Respironics recommends that only
technicians having prior training or experience servicing
ventilatory devices perform any repairs or adjustment to the BiPAP
Focus.
•Use only Respironics repair/service parts. Use of non-Respironics
parts may alter ventilator reliability resulting in damage. Use of
non-Respironics repair parts will affect the ventilator warranty.
Contact Customer Service at 1-800-345-6443 or 724-387-4000
for more information.
•High voltages are present in the AC/DC Power Supply, Power Cord
and VGA PCB. To avoid electrical shock, disconnect the power
cord before attempting any repairs on the device or cleaning.
•DO NOT immerse this device into any fluids or allow any liquid to
enter the cabinet or the filter intake.
•To avoid personal injury, always disconnect external AC and DC
power sources from the ventilator before servicing or cleaning.
•To avoid personal injury or the possibility of damage to the
ventilator, regularly inspect the power cord to ensure it is free from
defects and any obvious wear and is properly grounded.
•Never troubleshoot while a patient is connected to the ventilator,
since normal operation is suspended.
•If the ventilator has been operating, the internal parts may be hot.
Use caution when accessing.
•To prevent disease transmission, use protective equipment when
handling contaminated bacteria filters or other patient
accessories. Follow manufacturers' labeling and institutional
guidelines for disposal of contaminated accessories.
•To avoid cross-contamination between the test equipment and
ventilator, always install a bacteria filter between the main outlet
and test device.
•Explosion hazard. Do not operate the ventilator in the presence of
flammable anesthetic agents.
•To avoid the risk of fire, use only Respironics-approved batteries.
All battery connections are keyed to ensure proper connection. Do
not attempt to connect a battery incorrectly. Only qualified
technicians should install the battery.
•Use only Respironics-supplied cables with the nurse call station/
serial communications connector.
•To avoid personal injury or the possibility of damage to the
ventilator, DO NOT operate this device if it has failed any of its
diagnostic tests, either self or service initiated.
Cautions•Federal law (US) restricts this device to sale by, or on the order of,
a physician.
•Failure to replace a dirty filter may cause the device to operate at
higher than normal temperatures and damage the device.
•Use only Respironics-approved filters.
•Use only Respironics-approved batteries.
•The gray reusable air inlet filter must be completely dry before
use. Never place a wet filter into the device.
•Do not place more than one gray reusable air inlet filters that
come with the ventilator into the device at the same time. One
gray reusable air inlet filter and one white disposable ultra-fine
filter may be used.
•Replace any filter that is damaged.
•Do not attempt to clean or reuse disposable air inlet filters.
•Electronic components used in this device are subject to damage
from static electricity. Repairs made to this device must be
performed only in an antistatic, Electro-static Discharge (ESD)protected environment.
The BiPAP® Focus™ Ventilator System provides noninvasive breathing
support for adult patients weighing 30 kg (66 lbs.) or greater.
The BiPAP Focus System offers two ventilation modes:
•Continuous positive airway pressure (CPAP), which provides a single
level of positive pressure to the patient.
•Spontaneous/Timed (S/T), which provides two levels of positive
pressure (one during inspiration and one during exhalation), and
delivers timed breaths if the patient does not initiate a breath.
The BiPAP Focus System alarms annunciate when high or low pressure
regulation, apnea, patient disconnect, low power, or loss of mains power
conditions occur. The system displays a real-time estimated delivered pressure
bar graph.
An Apnea Rate (#Apnea) Alarm is provided to alert the caregiver to repeated
periods of short apneas of 10 seconds or more. The caregiver can set the value
for how many apnea periods (10 seconds or more) can occur within an hour
before alarming. The total number of Apnea periods (10 seconds or more) for
the previous hour is displayed as part of the patient data. Because the previous
hours data is displayed, the number of apnea periods for the first hour is an
estimate only.
The BiPAP Focus System includes alarm silence and alarm pre-silence
features. Battery backup provides a minimum of 45 minutes of backup power
at default settings in case AC power is not available (for example, during
transport within the hospital).
The BiPAP Focus System features Digital Auto-Trak™, which allows it to
recognize and compensate for unintentional leaks and promote synchrony by
adjusting its trigger and cycle algorithms to maintain optimum performance.
Air Inlet Filter(s)The air inlet filter removes coarse particulate from
BlowerThe blower draws room air though the air inlet filter and
ambient air as it is entrained into the blower assembly.
See Section 4 for periodic maintenance information.
The BiPAP Focus has a reusable dust filter that is gray in
color. An optional pollen filter, white in color is also
available.
muffler, and outputs air for delivery to the patient. The
DC impeller-type blower recirculates air through the flow
valve when not delivering gas to the patient. Compressor
speed is determined by patient settings. The controller
PCB controls compressor speed.
Flow valve (FV)The flow valve (valve assembly) is a mechanical sliding
assembly driven by an electromagnetic coil. Valve
commands from the PCB control current (-125mA to
675mA) to the coil. Movement of the flow valve is
proportional to the current through the coil. The flow
valve operates as a closed-loop system, using feedback
from the flow sensor and pressure transducers.
Air Flow SensorThe air flow sensor measures flow from the flow valve.
The ventilator uses this measurement to provide closed
loop control of the flow valve and to compute the flow
and volume delivered to the patient.
Patient circuit pressure bar
graph (continuous display)
Rate
Measured respiratory rate
Est. Vt
Estimated delivered tidal
volume
Est. MV
Estimated exhaled minute
volume
Range: 0-35 cmH2O (0-35 hPa)
Resolution: 1 cmH
Accuracy: ±10% of scale
In the event of total loss of power, the inspiratory
and expiratory pressure measured at the patient
exhalation port at 60 L/min is less than 1 cmH2O
by virtue of mask and ventilator design.
Range: 0-60/min
Resolution: 1/min
Accuracy: ± (1 + 10% reading)
Range: 0-4000 mL
Resolution: 1 mL
Accuracy (S/T Mode): ± (50 mL + 10% reading)
(when leak <60 L/min, using the Vision circuit)
Accuracy (CPAP Mode): ± (100 mL + 10%
reading) (when leak <60 L/min, using the Vision
circuit)
Vt display flashes when peak inspiratory flow for
successive breaths varies by more than 15 L/
min.
Range: 0-99 L/min
Resolution: 0.1 L/min
Accuracy: ± 1 L or ± 10% actual, whichever is
greater (when leak is <60 L/min using the Vision
circuit).
O (1hPa)
2
Leak
Estimated Patient leak
#Apnea
Brief apnea periods
Trigger
Breath trigger
NOTE: Est. Vt and Est. MV estimates are at ambient temperature and pressure, dry
(ATPD). Pressure signals are filtered using a 50-Hz low pass Butterworth filter.
Battery backup3.8 amp-hour (Ah) nickel metal hydride (NiMH) battery
provides 45 minutes of operation at default settings.
System automatically activates the battery charge cycle
when connected to AC power and the ON/OFF switch is
ON ( | ) (during normal operation or Standby mode).
Recharge time is typically under 5 hours, but may extend
further depending on machine settings if operating on
battery prior to recharge, or if operating in elevated
ambient temperature (above 28°C). Charge is complete
when the green CHARGING LED extinguishes.
Nurse call station relayRated current: 0.280 A
Rated voltage: 250V
Fuse typeNo replaceable fuses.
Power cordRefer to the“Complete Parts List” on page 9-1
Triggers and Cycles
Volume-based trigger
Flow reversal cycle
Shape signal
Timed trigger
IPAP maximum of 3.0 seconds
Peak flow cycle
Supplemental Oxygen
Flow and pressure into
oxygen valve
Maximum flow: 15 L/min at ambient pressure
Environmental
TemperatureOperating: +5 to +35°C at 10 to 95% relative
humidity
Storage: -20 to 60°C at 95% relative humidity
Atmospheric pressureOperating: 83 to 102 kPa (830 to 1020 mBar)
StorageWhen the BiPAP Focus is not in use for periods
of 2 weeks or longer, it is recommended that the
unit be stored in a clean, sanitized plastic bag.
Bacteria Filter
Dead space68 mL
Bacteria/viral filter
efficiency
Resistance0.7 cmH
ConnectorsMale connector 15-mm I.D./22-mm O.D.
>99.99%
P/N 342077
O/L/s at 0.5 L/s
2
Female connector 22-mm I.D.
Date of Manufacture
The 12-digit serial number located on the base of the unit indicates the date of
manufacture. From left to right, the fifth and sixth digits indicate the year; the
seventh and eighth, the month; the ninth and tenth, the day. For example, the
serial number 0001050903-20 indicates that the device was manufactured 3
September, 2005.
When the BiPAP Focus is not in use for periods of 2 weeks or longer, it is
recommended that the unit be stored in a clean, sanitized plastic bag.
While the unit is being stored, ensure that the power switch on the back of the
unit is in the OFF (O) position. If the switch is not turned OFF, the internal
battery will be depleted within two weeks. If the unit is stored with the power
switch in the OFF (O) position, the internal battery will deplete within 3
months.
Follow these steps to clean the reusable air inlet filter (Figure 1):
1. Remove the filter via the main rear access door (filter door) and
examine for damage or debris on the filter.
2. Wash using one of the following solutions, then rinse thoroughly:
•Liquid dishwashing detergent
•White distilled vinegar (5% acidicy)
•Isopropyl alcohol (99.9%)
•Hydrogen peroxide (3%)
•Bleach
•Sodium hypochloride (6%)
3. Allow the filter to dry completely before reinstalling.
Figure 1: Reusable Air Filter
Reusable
air inlet filter
(gray)
CAUTION:Failure to replace a dirty filter may cause the device to operate at higher
than normal temperatures and damage the device.
CAUTION:Use only Respironics-approved filters.
CAUTION:The gray reusable air inlet filter must be completely dry before use. Never
The reusable air inlet filter (gray) must be installed and replaced every year.
An additional ultra-fine disposable filter (white) is also recommended for
enhanced particulate filtering.
CAUTION:Replace any filter that is damaged.
CAUTION:Do not attempt to clean or reuse disposable air inlet filters.
CAUTION:Do not place more than one gray reusable air inlet filters that come with
the ventilator into the device at the same time. One gray reusable air inlet
filter and one white disposable ultra-fine filter may be used.
Replacing the BatteryWARNING:To avoid the risk of fire, use only Respironics-approved batteries. All battery
connections are keyed to ensure proper connection. Do not attempt to connect
a battery incorrectly. Only qualified technicians should install the battery.
NOTE:NOTE: If a Low Battery or Battery Depleted alarm occurs during Pre-
Operational Check, then the battery requires charging. If a Batt. Charge
Failure alarm occurs, the battery may be fully depleted. A re-charge is
recommended before proceeding. If the battery does not begin to charge
after one hour and the Batt. Charge Failure persists, contact customer
service for a replacement battery.
NOTE:Battery alarms will sound towards the end of the battery test. Gas delivery
will continue during this time, until the battery is depleted.
If the number of battery powered operations is greater than 220 per year, the
battery should be replaced every six months. If the number of battery
powered operations is less than 220 per year, the battery should be replaced
every year. It is recommended that the battery be tested once per month. A
fully charged battery is designed to operate for 45 minutes at default settings
(See “Power” on page 3-11). If the battery does not continue to deliver gas for
45 minutes at these settings, it should be replaced.
1. Turn the system OFF and disconnect the DC power supply.
2. Remove the two screws that secure the battery compartment door.
3. Unplug the battery cable and remove the old battery from its
compartment.
4. Insert a new Respironics-approved battery (see “BiPAP Focus
Replacement Parts List” on page 9-1) into the compartment and plug
the battery cable into its connector.
5. Replace the battery compartment door and screws.
This section describes the BiPAP Focus diagnostic mode and other
troubleshooting procedures.
Diagnostic mode allows:
•View product information, including serial numbers and versions of
software and hardware.
•View and adjust system settings, including Language, time since last
service, date and time.
•View and adjust operator preferences, including units of pressure,
alarm volume, contrast, brightness, reverse video and screen lock.
•View the significant event log.
•View the UI board controls and sensor readings for troubleshooting.
•Test alarm indicators and view internal voltages for troubleshooting.
•Test blower and controller board backup alarm.
Entering Diagnostic
Mode
WARNING:Diagnostic mode suspends normal ventilation: disconnect the patient from
the ventilator before entering diagnostic mode.
CAUTION:Troubleshooting and repair should be performed only by a qualified
service technician.
To enter diagnostic mode, simultaneously press the Alarm/Reset and Alarm/Silence keys on the ventilator front panel at power up for 15 seconds or until
diagnostic mode appears on the screen. At the warning prompt, press Enter to
start diagnostic mode. The diagnostic main menu (Figure 5-1) appears.
Press the arrow keys to highlight the menu selection, then press Enter.
To exit diagnostic mode at any time, turn the ventilator off.
Product InformationThe product information screen (Figure 5-2) displays serial number and
version number information for hardware and software components of the
ventilator.
To view the product information screen, use the arrow keys to highlight
PRODUCT INFORMATION on the diagnostic mode main menu, then
press Enter. Press Menu to return to the main menu.
Figure 5-2: Diagnostic Mode: Product Information Screen
To view the preferences screen, use the arrow keys to highlight PREFERENCES
on the diagnostic mode main menu, then press Enter.
1. Use the arrow keys to highlight the button whose value to change, then
press Enter:
2. If selected:
Display Units, the screen shows the current ventilator units settings.
Use the arrow keys to highlight cmH
O, hPa, or mbar then press Enter.
2
Alarm Volume, a popup screen displays the current alarm volume
setting. Use the arrow keys to adjust the volume from 1 to 5 (in
increments of 1), then press Enter (or press Cancel to exit without
making a change). The alarm volume cannot be turned completely off.
Contrast, a popup screen displays the current display contrast setting.
Use the arrow keys to adjust the contrast from 20% to 100% (in
increments of 20%), then press Enter (or press Cancel to exit without
making a change).
Brightness, a popup screen displays the current display brightness
setting. Use the arrow keys to adjust the contrast from 10% to 100%
(in increments of 10%), then press Enter (or press Cancel to exit
without making a change).
Reverse Video, pressing Enter toggles between reverse and normal
video.
Screen Lock Timer, the screen displays on/off lock setting. Use the
arrow keys to select, the press Enter.
Significant Event LogThe significant event log (Figure 5-5) allows viewing a log of system events,
including settings changes, alarms, and codes that can be used for
troubleshooting. See “Significant Event Log” on page 5.which describes
significant event codes in detail. The log includes the 200 most recent events.
To view the significant event log, use the arrow keys to highlight SIGNIFICANT
EVENT LOG on the diagnostic mode main menu, use the arrow keys to scroll
up and down. Press Menu to return to the main menu.
Follow these steps to connect the ventilator and a PC to create a diagnostic
report (DRPT):
between the PC and BiPAP Focus ventilator. Connect the male end
labeled Diagnostics to the back of the ventilator and the female end to
the service PC.
2. Power up the ventilator in diagnostic mode: simultaneously press the
Alarm/Reset and Alarm Silence keys for approximately 15 seconds
while turning ventilator power on.
3. Launch the HyperTerminal program on the PC by clicking Start >
Programs > Accessories > Communications > HyperTerminal, then
double-clicking on the HyperTerminal icon.
4. Enter a name for the connection (BiPAP Focus Communications is
entered in Figure 5-6) and choose an icon, then click OK).
14. Match the ASCII Setup screen (Figure 5-11), then click OK.
Figure 5-11: ASCII Setup Screen
15. Save this configuration. Select File > Save As and save to the desktop
if you want to create an icon for BiPAP Focus Communications on the
Windows desktop.
1. With the BiPAP Focus ventilator in diagnostic mode and the serial
communcations cable, the end labeled Diagnostics connected to the
ventilator, start HyperTerminal, open the BiPAP Focus
Communications file, or click on the BiPAP Focus Communications
icon on the PC (if created).
2. Type DRPT (all caps) in the dialog box, and press the Enter key. This
pulls information found in the significant event log.
3. If the ventilator is connected and communication occurs, a response
similar to the following appears:
Respironics Inc. BiPAP Focus Ventilator
Serial Number: 8772060206-04
Date & Time : 6/19/06 20:49
Event ID Date Time
905 Pwr O n r e set6/1 9 / 0 620:43
300 POS T S u c ce ssful6/1 9 / 0 620:43
102 Pow e r O f f 6/1 9 / 0 620:42
4 3 7B a t t e r y V o l t a g e F a i l e d6 / 1 9 / 0 62 0 : 4 2 V 6 1 5 , 6 1 5
639 Dis c o n n e ct 6/1 9 / 0 620:42
6 3 5B a t t e r y D e p l e t e d6 / 1 9 / 0 62 0 : 4 2 6 3 7 , 6 3 3
644 Apne a 6/19/0620 : 4 2
639 Disconnect 6/19/0620:
6 3 5B a t t e r y D e p l e t e d6 / 1 9 / 0 62 0 : 4 1 6 8 7 , 6 4 9
6 4 3L o w B a t t e r y 6 / 1 9 / 0 62 0 : 4 1 7 1 4 , 7 2 3
+18VBSTCMP18V_BOOST_COMPSignal for detection if the 18V_Boost mains
voltage is above a certain threshold
(15.64V typically)
Hi: Above threshold
Lo: Below threshold
BattChrgFaultBATT_CHRG_FAULT_BUFSignal for detection if there is a fault in the
battery charging
Hi: Fault
Lo: No Fault
BattOnChrgBATT_ON_CHG_BUFSignal for detection if the battery is being
charged
Hi: Battery charging
Lo: Battery not charging
BattChrgTocBATT_CHR_TOCSignal for detection if a top-off charge is
being applied to battery
Hi: Battery NOT in TOC state
Lo: Battery in TOC state
BattChrgRdyBATT_CHG_READY_BUFSignal for detection if the battery is ready
PORLATCHEXT_WDOG_LATCHEDSignal for detection if the processor was
for charging
Hi: Ready for charging
Lo: Not ready for charging
reset due to a drop in the +3.3V rail. This
signal must be primed by software, with the
EXT_WDOG_LATCH_CLR signal. This can
be done using the PORLATCLK diagnostics
label in the System Test screen.
Hi: Loss of +3.3V supply caused last reset
Lo: Last reset not caused by loss of +3.3V
supply. Probably caused by watchdog
(software reset)
PWRSWLATCHPWR_SW_LATCHEDLatched User interface Standby Key
Sensor Readings Defined
Hi: Standby key is in-active (released).
Lo: Standby key is active (pressed).
monitor. This signal must be primed by
software with the PWR_SW_CLK signal.
This can be done using the PWRSWCLK
diagnostics label in the System Test screen.
Used to turn blower on/off TCB_SWITCH_ON Hi and
TCB_SWITCH_OFF Lo: Blower ON TCB_SWITCH_ON Lo
and TCB_SWITCH_OFF Hi: Blower OFF
These signals are mutually exclusive in software
temperature
Hi: Battery voltage measured by ADC
Lo: Battery temperature measured by ADC
Page 48
Chapter 5
Diagnostic Mode and Troubleshooting
Diagnostics
LabelSchematic LabelDescription
V Out EnableVOUT_ENOption to turn on/off the power out to the TCB.
PWRSWCLKPWR_SW_CLKClocks the Standby Switch latch.
PWRTUIOFFPWR_TUI_OFFPWR_TUI_OFF: Control line to switch off the power.
PORLATCLKEXT_WDOG_LATC
H_CLR
System Test Defined
Reserved for future use. Therefore, the option to control
the power to the UI cannot be changed in software.
If used, the following applies:
HI: Turns on the 18V_Boost out to the Controller Board.
LO: Turns off the 18V_Boost out to the Controller Board.
Lo to Hi: Clocks a '1' to the latch output.
Hi to Lo: No change of state.
Hi: Clears the latch which removes the 18V_Boost rail
from the system, thereby shutting down power by placing
the unit in Standby mode.
Lo: No change in state
Clocks the Power On Reset latch. This can be used to
determine if an external power on reset has occurred due
to the +3.3V rail dropping.
Significant Event
Codes
Lo to Hi: No change of state.
Hi to Lo: Clocks a '1' to the latch output.
WDSTROBEWDSTROBEWDSTROBE: External watchdog strobe. Software is
required to apply a high pulse of 50ns minimum duration
at a maximum of every 1.2seconds to avoid the watchdog
resetting the processor.
Table 5-2: System Test Defined (Sheet 2 of 2)
The BiPAP Focus Ventilator generates a log of system events, including
settings changes, alarms, and codes that can be used for troubleshooting. If a
ventilator inoperative condition or unexpected reset occurs, the significant
event log includes the ventilator settings, patient data, and alarm conditions
that were in effect.
The significant event log can include at least 200 of the most recent events,
with the most recent events listed first. The ventilator maintains the significant
event log regardless of whether there is power to the ventilator.
The significant event log includes the following information:
1. Event ID: This includes a code and brief text description of the event.
2. Date: Each event is date-stamped in a month/day/year format (for
example, 10/20/02).
3. Time : Each event is time-stamped in hour/minute/second format (for
example, 09:15:23).
4. Old value: For settings changes, the previously selected value is
displayed.
5. New value: For settings changes, the most recently selected value is
displayed.
Use the arrow keys to scroll through the log.
NOTE:Table 5-3 lists event IDs, and recommends corrective actions if
appropriate. When performing corrective actions:
•Perform the corrective actions in the order listed (if applicable)
until the problem is resolved.
•Before replacing a part, slave in a replacement part to verify that
it corrects the problem. If so, verify that the problem recurs with
the original part installed, then replace the part and confirm that
the problem is corrected.
Significant Event Log: Event IDs
Code Short text for code Comment / Corrective Action
1ERR SOFTWAREController processor detected a software error.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
2ERR PROGRAM CRC FAILURE Controller processor detected a program memory
checksum error.
If this persists replace the controller PCB.
3ERR EXTERNAL RAM
FAI LUR E
4ERR FIQ STACK OVERFLOWController processor detected a stack overflow.
Controller processor detected an external RAM memory
error.
If this persists replace the controller PCB.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Code Short text for code Comment / Corrective Action
5ERR FIQ STACK UNDERFLOW Controller processor detected a stack underflow.
6ERR NEST STACK OVERFLOW Controller processor detected a stack overflow.
7ERR NEST STACK
UNDERFLOW
8ERR IRQ STACK OVERFLOWController processor detected a stack overflow.
9ERR IRQ STACK UNDERFLOW Controller processor detected a stack underflow.
Significant Event Log: Event IDs (Continued)
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected a stack underflow.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
10ERR TMR STACK OVERFLOWController processor detected a stack overflow.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
11ERR TMR STACK
UNDERFLOW
12ERR SVC STACK OVERFLOW, Controller processor detected a stack overflow.
13ERR SVC STACK UNDERFLOW Controller processor detected a stack underflow.
14ERR THREAD STACK
OVERFLOW
15ERR ARM UNDEFINED
INSTRUCTION EXCEPTION
Controller processor detected a stack underflow.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected a stack overflow.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected an unexpected exception.
If this persists and to multiple resets and the system
declaring a system error because too many errors
occurred in 24 hours, replace the controller PCB.
Code Short text for code Comment / Corrective Action
16ERR ARM SWI EXCEPTIONController processor detected an unexpected exception.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
17ERR ARM PREFETCH
EXCEPTION
18ERR ARM ABORT EXCEPTION Controller processor detected an unexpected exception.
20ERR AIC DEFAULT HANDLERController processor detected an unexpected interrupt.
Controller processor detected an unexpected exception.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
21ERR AIC SPURIOUS
HANDLER
22ERR CAL DATA CRC FAILURE Controller processor detected a calibration data
23ERR INVALID DRIFT INDEX AT
CAL
24ERR UNRECOGNIZED CAL
VERSION BY SW
Controller processor detected an unexpected interrupt.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
checksum error.
1. Attempt to re-calibrate the system.
2. If this fails, replace the controller PCB.
Controller processor detected that the flow sensor drift
check has failed. Flow sensor drift and calibration
information can be monitored using the "D) Drift
Screen" from the debug screen using the RASP utility,
capture screen output to a file.
1. Attempt to re-calibrate the system.
2. If this fails, replace the controller PCB.
Controller processor detected that the calibration table
version check has failed.
Code Short text for code Comment / Corrective Action
25ERR DRIFT FLOW TOO HIGHController processor detected that the flow sensor drift
27ERR DRIFT PRESSURE TOO
HIGH
28ERR CAL DATA BLANKController processor detected that the calibration table
29ERR DRIFT SECONDARY
PRESSURE TOO HIGH
30ERR INVALID NVDATA
SCHEMA
31ERR INVALID NVDATA LOCKController processor detected an error accessing the
32ERR INVALID NVDATA
CHECKSUM
33ERR NVDATA STORAGE
ERROR
Significant Event Log: Event IDs (Continued)
check has failed.
Flow sensor drift and calibration information can be
monitored using the "D) Drift Screen" from the debug
screen using the RASP utility, capture screen output to
a file.
1. Attempt to re-calibrate the system.
2. If this fails, replace the controller PCB.
Controller processor detected that the drift check on
the primary pressure has failed. Pressure sensor drift
and calibration information can be monitored using
using the "D) Drift Screen" from the debug screen using
the RASP utility, capture screen output to a file.
1. Attempt to re-calibrate the system.
2. If this fails,replace the controller PCB.
is blank.
1. Attempt to re-calibrate the system.
2. If this fails, replace the controller PCB.
Controller processor detected that the drift check on
the secondary pressure has failed.
1. Attempt to re-calibrate the system.
2. If this fails, replace the controller PCB.
Controller processor detected an error in format of the
calibration data in EEPROM.
1. Attempt to re-calibrate the system.
2. If this fails,replace the controller PCB.
calibration data in EEPROM.
1. Attempt to re-calibrate the system.
2. If this fails,replace the controller PCB.
Controller processor detected a checksum error on the
calibration in EEPROM.
1. Attempt to re-calibrate the system.
2. If this fails,replace the controller PCB.
Controller processor detected that the data structure is
bigger than the EEPROM device.
Code Short text for code Comment / Corrective Action
34ERR NVDATA QUEUE FULLController processor detected that the queue to the
EEPROM manager thread is full.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
35ERR NVDATA READBACK
FAI LUR E
36ERR NVDATA RANGE
FAI LUR E
37ERR CORRUPT RTC VALUEController processor detected that the Real Time Clock
Controller processor detected that a write operation to
EEPROM failed the readback check.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that a write operation to
EEPROM failed the range check for that data item.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
time and the RTOS tick timer has drifted since it was
last tested. When changing the time, this could happen
and an RTC Failure Alarm maybe annuciated, this
alarm can be reset by pressing Alarm Reset.
No action necessary.
38ERR RTC NOT TICKINGController processor detected that the Real Time Clock
39ERR UI QUEUE FULLController processor detected a RTOS queue full
40ERR INVALID BIST TEST
CALL
time and the RTOS tick timer has drifted significantly
(>4 seconds) since it was last tested. When changing
the time, this could happen and an RTC Failure Alarm
maybe annuciated, this alarm can be reset by pressing
Alarm Reset.
No action necessary.
condition.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected an invalid BIST test was
attempted to be run.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Code Short text for code Comment / Corrective Action
41ERR PRESSURE REG OVERController processor detected that a high pressure
42ERR BIST THREAD LOCKEDController processor detected that the built in selftest
43ERR ALARM VOLTAGE
FAI LUR E
44ERR 12VREF FAILUREController processor detected that the limits test on the
Significant Event Log: Event IDs (Continued)
condition (i.e. 5 cmH20 above the IPAP or CPAP
setting) lasted for greater than ten seconds.
1. Check for kicked tubes on the Primary pressure
sensor.
2. Check for blockages near the Primary pressure
sensor in the gas outlet port.
3. Replace the controller PCB.
4. If this persists replace the pneumatics subassembly
(blower and valve).
thread is locked, i.e. it's not alive as expected.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the backup alarm
buzzer voltage test failed a limits check for greater than
five seconds.
1. Enter Diagnostics mode and use the System Test
screen, to check if the backup alarm can be turned
on and off.
2. Replace the controller PCB.
12V reference voltage signal failed.
Replace the controller PCB.
45ERR 5VREF FAILUREController processor detected that the limits test on the
46ERR VBULK FAILUREController processor detected that the limits test on the
47ERR NEG15VREF FAILUREController processor detected that the limits test on the
48ERR FL12 SENSOR RAILEDController processor detected that the limits test on the
5V reference voltage signal failed.
Replace the controller PCB.
VBULK reference voltage signal failed.
Replace the controller PCB.
-15V reference voltage signal failed.
Replace the controller PCB.
Flow sensor signal failed.
1. Replace the controller PCB.
2. If this persists replace the pneumatics subassembly
(blower and valve)
Code Short text for code Comment / Corrective Action
49ERR PV2 SENSOR FAILUREController processor detected that the limits test on the
secondary pressure sensor signal failed.
1. Replace the controller PCB.
2. If this persists replace the pneumatics subassembly
(blower and valve)
50ERR FLASH FAILUREController processor detected a Boot Flash failure
Replace the controller PCB.
51ERR UNRECOGNIZED BOARD
REV
52ERR MOTOR FAILUREController processor detected a stalled blower, i.e. less
53ERR BLOWER RPM FAILED
TOLERANCE
54ERR BLOWER OFF CURRENT
HIGH
55ERR PRINTF BUFFER
OVERFLOW
Controller processor detected an out of range board
revision
Replace the controller PCB.
than 1000 RPM.
1. If this persists replace the pneumatics subassembly
(blower and valve).
2. If this persists, replace the controller PCB. The
original pneumatics subassembly (blower and valve)
should be re-inserted and the system retested and
recalibrated
Controller processor detected an out of tolerance
blower speed, i.e. outside +/- 5500 RPM from the
target blower speed for more than 5 seconds.
1. If this persists replace the pneumatics subassembly
(blower and valve).
2. If this persists, replace the controller PCB. The
original pneumatics subassembly (blower and valve)
should be re-inserted and the system retested and
recalibrated
Controller processor detected a current draw of more
than 100mA for more than 5 seconds, when the motor
is powered off.
1. If this persists replace the pneumatics subassembly
(blower and valve).
2. If this persists, replace the controller PCB. The
original pneumatics subassembly (blower and valve)
should be re-inserted and the system retested and
recalibrated
Controller processor detected a buffer overflow while
outputting serial data.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Code Short text for code Comment / Corrective Action
56ERR BLOWER ON CURRENT
HIGH
57ERR THERAPY EVENT QUEUE
FULL
59ERR P1 SENSOR RAILEDController processor detected that the limits test on the
60ERR P2 SENSOR RAILEDController processor detected that the limits test on the
61ERR RTC BATTERY DEADController processor detected that the Real Time Clock
62ERR BLOWER RPM
EXCEEDED MAX
63ERR INTERNAL WATCHDOG
FAI LUR E
Significant Event Log: Event IDs (Continued)
Controller processor detected a current draw of more
than 3000mA for more than 10 seconds, when the
motor is powered on.
1. If this persists replace the pneumatics subassembly
(blower and valve)
2. If this persists, replace the controller PCB.
3. The original pneumatics subassembly (blower and
valve) should be re-inserted and the system retested
and recalibrated
Controller processor detected a RTOS queue full
condition.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Primary pressure sensor signal failed.
1. Replace the controller PCB.
2. If this persists replace the pneumatics subassembly
(blower and valve)
Secondary pressure sensor signal failed.
1. Replace the controller PCB.
2. If this persists replace the pneumatics subassembly
(blower and valve)
time and the RTOS tick timer has drifted significantly
since it was last tested. When changing the time, this
could happen and an RTC Battery depleted technical
alert maybe annuciated, this can be reset by pressing
Alarm Reset. No action necessary.
Controller processor detected an out of tolerance
blower speed, i.e. above 23337 RPM for more than 3
seconds.
1. If this persists replace the pneumatics subassembly
(blower and valve)
2. If this persists, replace the controller PCB. The
original pneumatics subassembly (blower and valve)
should be re-inserted and the system retested and
recalibrated
Controller processor detected an internal watchdog
failure.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Code Short text for code Comment / Corrective Action
64ERR EXTERNAL WATCHDOG
FAI LUR E
65ERR UNEXPECTED
WATCHDOG
67ERR RTOS INIT FAILUREController processor detected an initialisation failure
Controller processor detected an external watchdog
failure.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected a watchdog failure, when
it wasn't expecting one.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
when starting the RTOS.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
68ERR SERIAL QUEUE FULLController processor detected a RTOS queue full
condition.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
69ERR SNORE SAMPLING
THREAD LOCKED
70ERR MAIN EXECUTION
THREAD LOCKED
71ERR INTERNAL RAM
FAI LUR E
72ERR EVENT LOG QUEUE
FULL
Controller processor detected that the snore sampling
thread is locked, i.e. it's not alive as expected.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the main execution
thread is locked, i.e. it's not alive as expected.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected an internal RAM memory
checksum error.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected a RTOS queue full
condition.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Code Short text for code Comment / Corrective Action
75ERR IPC MSG TOO BIGController processor detected an IPC message that was
76ERR ALARM CAPACITOR
FAI LUR E
77ERR HIGH PRESSURE
REGULATION
Significant Event Log: Event IDs (Continued)
too big.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the backup alarm
buzzer capacitor test failed a limits check for greater
than five minutes.
1. Enter Diagnostics mode and use the System Test
screen, to check if the backup alarm can be turned
on and off.
2. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller
PCB.
Controller processor detected a high pressure condition
and annuciated the "Hi P Reg" alarm. No action
necessary.
If this condition persists for greater than 10 seconds
then the system will declare system error code 41
78ERR LOW PRESSURE
REGULATION
79ERR_LOW_PRESSURE_SUPP
ORT_REGULATION
80ERR IPC QUEUE FULLController processor detected a RTOS queue full
81ERR IPC INVALID MSGIDController processor detected an IPC message with an
Controller processor detected a low pressure condition
and annuciated the "Lo P Reg" alarm. No action
necessary.
Unable to maintain Pressure Support. System Error
declared after condition is present for one minute.
condition.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
invalid message id.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Code Short text for code Comment / Corrective Action
82ERR IPC COMMS FAILUREController processor detected an IPC message failure, it
can be due to : a low level I2C receive error, a low level
I2C transmit error or that the once a second I'm alive
message was not received
1. Check the UI PCB to Controller PCB IPC 8-way
multi-coloured cable.
2. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller
PCB.
83ERR IPC CKSUM FAILUREController processor detected an IPC message with an
invalid checksum.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the ST mode IPAP
setting change is not consistent with the value stored in
EEPROM.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the ST mode EPAP
setting change is not consistent with the value stored in
EEPROM.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the ST mode rise
time setting change is not consistent with the value
stored in EEPROM.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Code Short text for code Comment / Corrective Action
89SID TCB ST RATE SETTING
FAI L
90SID TCB ST ITIME SETTING
FAI L
91SID TCB ST RAMP TIME
SETTING FAIL
Significant Event Log: Event IDs (Continued)
Controller processor detected that the ST mode breath
rate setting change is not consistent with the value
stored in EEPROM.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the ST mode
inspiratory time setting change is not consistent with
the value stored in EEPROM.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the ST mode ramp
time setting change is not consistent with the value
stored in EEPROM.
92SID TCB ST RAMP START
SETTING FAIL
93SID TCB CPAP CPAP SETTING
FAI L
94SID TCB CPAP RAMP TIME
SETTING FAIL
95SID TCB CPAP RAMP START
SETTING FAIL
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the ST mode ramp
start setting change is not consistent with the value
stored in EEPROM.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the CPAP mode
CPAP setting change is not consistent with the value
stored in EEPROM.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the CPAP mode
ramp time setting change is not consistent with the
value stored in EEPROM.
Controller processor detected that the CPAP mode
ramp start setting change is not consistent with the
value stored in EEPROM.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Code Short text for code Comment / Corrective Action
96SID TCB APNEA SETTING
FAI L
97SID TCB APNEA RATE
SETTING FAIL
98ERR TUI SYSTEM ERROR IND A system error has occurred on the UI processor and
300SID POST SUCCESSFULPOST successful logged to the significant event log
301SID POST BLOWER SWITCH
CONTROL
302SID POST SOFTWARE
VERSION MISMATCH
Controller processor detected that the APNEA alarm
setting change is not consistent with the value stored in
EEPROM.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
Controller processor detected that the #APNEA rate
alarm setting change is not consistent with the value
stored in EEPROM.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller PCB.
the controller processor has been informed of the fact.
The controller processor shuts down.
1. If this persists replace the UI PCB
2. If replacing the UI PCB doesn't fix the issue, replace
the controller PCB.
UI processor detected that the blower switch control
test failed during POST.
1. Check the blower switch control cable.
2. If this persists replace the controller PCB.
3. If replacing the Controller PCB doesn't fix the issue,
replace the UI PCB.
UI processor detected that the UI and Controller
processors have a mismatch in software versions.
Ensure that the download of the released software
completes without any errors reported.
303SID POST TCB NOT
RESPONDING
During POST the UI processor detected that the
Controller processor did not synchronise with it, it
timed out.
Note: the system must be powered from mains as part
of the software download procedure
1. Check the UI PCB to Controller PCB IPC 8-way
multi-coloured cable.
2. If this persists replace the controller PCB.
3. If replacing the Controller PCB doesn't fix the issue,
replace the UI PCB.
Code Short text for code Comment / Corrective Action
308SID POST MAX SYSTEM
RESETS
309SID POST INDICATOR FAILUI processor detected one of the leds is faulty during
310SID POST ABNORMAL
RESTAR
332SID POST VBATT MONITOR
FAI L
Significant Event Log: Event IDs (Continued)
The system has detected either, 5 soft resets early in
the UI processor POST or the system declaring a
system error because 3 resets occurred in the last 24
hours.
1. Examine the significant event log, check the recent
error codes and see if the Entries point to either a
Controller PCB, Controller subassembly or UI PCB
issue.
2. If this persists replace the UI PCB
3. If replacing the UI PCB doesn't fix the issue, replace
the controller PCB.
POST
1. Enter Diagnostics mode and use the System Test
screen, to test the leds and identify which led is
faulty.
2. If no led is found to be faulty and If this persists and
leads to multiple resets and the system declaring a
system error because too many errors occurred in 24
hours, replace the UI PCB.
The system has detected that a soft reset has occurred
unexpectedly.
1. Examine the significant event log, check the recent
error codes and see if the entries point to either a
Controller PCB, Controller subassembly or UI PCB
issue.
2. If this persists replace the UI PCB
3. If replacing the UI PCB doesn't fix the issue, replace
the controller PCB.
UI processor detected that the VBATT test failed during
POST.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when POST is run on
mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
Code Short text for code Comment / Corrective Action
333SID POST 3 3V MONITOR
FAI L
334SID POST 5 0V MONITOR
FAI L
335SID POST 12V MONITOR FAIL UI processor detected that the 12V test failed during
336SID POST 18VIN MONITOR
FAI L
UI processor detected that the 3.3V test failed during
POST.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when POST is run on
mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the 5.0V test failed during
POST.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when POST is run on
mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
POST.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when POST is run on
mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the 18VIN test failed during
POST. Signal is only present while on mains.
1. Check if the problem exists when POST is run on
mains and battery.
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
Code Short text for code Comment / Corrective Action
337SID POST 18VBOOST
MONITOR FAIL
338SID POST SUPERCAPV
MONITOR FAIL
339SID POST HIGH INT TEMP
VIO
340SID POST LOW INT TEMP VIO UI processor detected that the enclosure low
Significant Event Log: Event IDs (Continued)
UI processor detected that the 18VBOOST test failed
during POST.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when POST is run on
mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the SUPERCAP test failed
during POST.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when POST is run on
mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the enclosure high
temperature test failed during POST. (> 60 degrees)
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the temperature readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
temperature test failed during POST. (< -3 degrees)
1. Ensure that the system is at room temperature or
within the operating specifications (5-35° C / 4195° F).
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the temperature readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
Code Short text for code Comment / Corrective Action
341SID POST BOARD OVER TEMP
MONITOR FAIL
342SID POST BOARD UNDER
TEMP MONITOR FAIL
343SID POST BATTERY CHARGER
READY MONITOR FAIL
344SID POST BATTERY CHARGER
FAU LT M ONITOR FA I L
UI processor detected that the board high temperature
test failed during POST.
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the board low temperature
test failed during POST.
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the battery charger ready
signal test failed during POST.
1. Enter Diagnostics mode and use the Sensor
Readings screen, to check the battery charger status
bits.
2. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the battery.
3. If this persists replace the UI PCB
UI processor detected that the battery fault ready
signal test failed during POST.
1. Enter Diagnostics mode and use the Sensor
Readings screen, to check the battery charger status
bits.
2. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replacethe battery.
Code Short text for code Comment / Corrective Action
345SID POST BATT THERMISTOR
MONITOR FAIL
401SID CBIT MONITOR RAM FAIUI processor detected that the RAM memory test failed
Significant Event Log: Event IDs (Continued)
UI processor detected that the battery thermistor test
failed during POST.
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Check the battery is present
3. Check the battery wiring for shorts or opens.
4. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
5. Replace battery.
6. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
during CBIT.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
403SID CBIT MONITOR
PROGRAM CRC FAI
409SID CBIT INDICATOR FAIUI processor detected that the led test failed during
417SID CBIT HIGH INT TEMP
ALARM
UI processor detected that the UI program memory
checksum test failed during CBIT.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
CBIT.
If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the enclosure high
temperature is high (> 58 degrees)
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the temperature readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
Code Short text for code Comment / Corrective Action
419SID CBIT HIGH INT TEMP VIO UI processor detected that the enclosure high
temperature test failed during CBIT. (> 60 degrees).
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the temperature readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
426SID CBIT LOW INT TEMP
ALARM
432SID CBIT 3.3V MONITOR FAIL UI processor detected that the 3.3V test failed during
433SID CBIT 5.0V MONITOR FAIL UI processor detected that the 5.0V test failed during
UI processor detected that the enclosure low
temperature is low (< 0 degrees).
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the temperature readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
CBIT.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when the system is run
on mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
CBIT.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when the system is run
on mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
Code Short text for code Comment / Corrective Action
434SID CBIT 12V MONITOR FAIL UI processor detected that the 12V test failed during
435SID CBIT 18VIN MONITOR
FAI L
436SID CBIT 18VBOOST
MONITOR FAIL
437SID CBIT VBATT MONITOR
FAI L
Significant Event Log: Event IDs (Continued)
CBIT.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when the system is run
on mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the 18VIN test failed during
CBIT.
1. Signal is only present while on mains.
2. Check if the problem exists when the system is run
on mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the 18VBOOST test failed
during CBIT.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when the system is run
on mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the VBATT test failed during
CBIT.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when the system is run
on mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
Code Short text for code Comment / Corrective Action
438SID CBIT BATT THERMISTOR
MONITOR FAIL
439SID CBIT BOARD OVER TEMP
MONITOR FAIL
440SID CBIT BLOWER SWITCH
CONTROL FAIL
441SID CBIT IPC CBIT TEST FAIL UI processor detected that the IPC test failed during
UI processor detected that the battery thermistor test
failed during CBIT.
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Check the battery is present
3. Check the battery wiring for shorts or opens.
4. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
5. Replace battery.
6. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the board high temperature
test failed during CBIT.
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the blower test failed during
CBIT.
1. Enter Diagnostics mode and use the System Test
screen, to check if the blower can be turned on.
2. Check the blower switch control cable
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
4. If this persists replace the controller PCB.
5. If replacing the Controller PCB doesn't fix the issue,
replace the Blower.
CBIT.
1. Enter Diagnostics mode and use the System Test
screen, to check if the blower can be turned on and
off. Also check that the backup alarm can be turned
on and off.
2. Check the UI PCB to Controller PCB IPC 8-way
multi-coloured cable.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
Code Short text for code Comment / Corrective Action
442SID CBIT BOARD UNDER
TEMP MONITOR FAIL
443SID CBIT LOW INT TEMP VIOUI processor detected that the enclosure low
444SID CBIT SUPERCAPV
MONITOR FAIL
445SID CBIT SETTINGS TEST FAI UI processor detected that the settings cross check test
Significant Event Log: Event IDs (Continued)
UI processor detected that the board low temperature
test failed during CBIT.
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
temperature test failed during CBIT. (< -3 degrees).
1. Ensure that the system is at room temperature or
within the operating specifications as per the
Operator’s Manual.
2. Enter Diagnostics mode and use the Sensor
Readings screen, to check the temperature readings.
3. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
UI processor detected that the SUPERCAP test failed
during CBIT.
1. If running on battery, ensure the system has a
charged battery as per the setup section in the
Operator’s Manual.
2. Check if the problem exists when the system is run
on mains and battery.
3. Enter Diagnostics mode and use the Sensor
Readings screen, to check the adc readings.
4. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
failed during CBIT.
1. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the UI PCB.
2. If this persists and leads to multiple resets and the
system declaring a system error because too many
errors occurred in 24 hours, replace the controller
PCB.
•Phase 2- Download user interface software to the BiPAP Focus
Ventilator.
•Reprogramming the BiPAP Focus serial number
The service PC must be equipped with Windows XP, and a USB port. The
service PC must have administrator privileges to load the BiPAP Focus
communications software.
CAUTION:Be sure the ventilator is powered by the mains power and not running on
battery power. This is to prevent possible power loss.
CAUTION:The ventilator must be recalibrated following a software download.
Download Service
Software to the
Service PC
The most current revisions of the Service Center Tools Suite and BiPAP Focus
operational software should be downloaded from the Respironics Service
website.
1. Go to the URL http://servicesoftware.respironics.com and click on Respironics Utility Tools.
2. Click the download button next to Service Center Tools Suite.
3. Download this utility to the service PC.
4. Extract the file Service-Center-Tools.exe and launch the installation
wizard.
5. Go to the URL http://servicesoftware.respironics.com and click on
Respironics Products Operating Software Updates.
6. Click the download button next to Bipap Focus Operational Software
to download the most current revision.
Communications software allows the ventilator to communicate with the
service PC. Follow these steps to install BiPAP Focus communications software
onto a service PC:
1. Connect the universal serial bus (USB) cable between the service PC
and ventilator.
NOTE:Do not connect the USB cable through a hub or docking station. Using
an intermediate connection causes communication errors.
2. Connect the female end of the serial communications cable to the
service PC. Then connect the male end labeled Software/Rasp to the
ventilator.
3. If the software drivers for the communications software are not already
installed on the PC, the New Hardware Found Wizard appears when
the ventilator is powered on. Select “Install software automatically”
and click Next. Refer to Figure 6-1. If drivers are loaded proceed to
step ‘1.’ on page 6-4.
Figure 6-1: New Hardware Wizard
4. Select the BEST driver then click Next. Refer to Figure 6-2.
Figure 6-4: Completing the Found New Hardware Wizard dialog box
Starting the BiPAP
Focus Wizard
Downloading
Controller Board
Software to the
Ventilator
7. Once the drivers for software downloads are complete the process for
loading the BiPAP Focus can begin.
The BiPAP Focus Wizard is comprised of two phases:
•Phase 1 - Downloading controller board software to the ventilator.
•Phase 2 - Downloading user interface software to the ventilator.
1. Start the ventilator in Download Mode. Press the Standby key while
pressing the Up and Down arrow keys.
2. Navigate to the wizard executable program:
Install_Focus_Software.exe
3. Double-click on Install_Focus_Software.exe.
This will open Phase 1 of the of the wizard.
Follow these steps to download controller board software from the computer to
the ventilator:
1. This is the Phase 1 Start screen. The screen then shows the order of
installation and Warns “Ensure that there is no patient connected.”
From the Phase 1 Start screen click Next.
During this portion of the software installation the alarm enunciator will sound.
Hearing protection may be desired.
1. Follow the onscreen instructions to install the software: confirm that
no patient is connected to the ventilator and that the ventilator is in
download mode (Figure 6-10). Click Next.
Figure 6-10: Phase 2 welcome
2. Connect a universal serial bus (USB) cable between the service PC
and ventilator. If necessary choose the option to display more detailed
connection instructions (Figure 6-11). Click Next.
NOTE:Do not connect the USB cable through a hub or docking station. Using
an intermediate connection causes communication errors.
NOTE:The female end of the serial communications cable should be connected
to the service PC. The male end, labeled Software/Rasp, should be
connected to the ventilator.
Figure 6-11: Connecting the Ventilator to the Service PC
3. Click Next.
Figure 6-12: Powering Up the Ventilator
4. The software connection process dialog box appears identifying the
steps including, Searching for the ventilator, retrieving ventilator
configuration information, and installing the communications software
(Figure 6-13). Click Next.
6. Click Next, the Ventilator Management dialog box appears
(Figure 6-15), which allows loading new software into the ventilator
configuration or selecting Advanced configuration operations.
10. The screen then displays the user interface software installation
process, including erasing old user interface software, installing new
interface software, and updating software configuration information
(Figure 6-18). Click Next.
Figure 6-18: New Software Installation
11. Once the user interface software installation is complete, a completion
screen (Figure 6-19) is displayed. Click Finish.
1. Follow the onscreen instructions to install the software: confirm that
no patient is connected to the ventilator and that the ventilator is in
download mode (Figure 6-20). Click Next.
Figure 6-20: Phase 2 welcome
2. Connect a universal serial bus (USB) cable between the service PC
and ventilator. If necessary choose the option to display more detailed
connection instructions (Figure 6-21). Click Next.
NOTE:Do not connect the USB cable through a hub or docking station. Using
an intermediate connection causes communication errors.
NOTE:The female end of the serial communications cable should be connected
to the service PC. The male end, labeled Software/Rasp, should be
connected to the ventilator.
Figure 6-21: Connecting the Ventilator to the Service PC
Chapter 6
3. Once the ventilator and PC are connected, power up the ventilator
while holding down the Up and Down arrow buttons until the ventilator
displays the message Waiting to detect the BiPAP Focus Ventilator
(Figure 6-22). Click Next.
Figure 6-22: Powering Up the Ventilator
4. The software connection process dialog box appears identifying the
steps including, Searching for the ventilator, retrieving ventilator
configuration information, and installing the communications software
(Figure 6-23).
5. Click Next, the Ventilator Management dialog box appears
(Figure 6-24), which allows loading new software into the ventilator
configuration or selecting Advanced configuration operations.
6. Fill the “I want to perform advanced configuration operations.” check
box then click Next, or click Cancel to exit.
Figure 6-24: Ventilator Management Screen
7. The BiPAP Focus Update Ventilator Configuration screen appears. Fill
the Ventilator Serial Number check box then enter the serial number
in the text box.
The performance verification verifies the integrity of the ventilator's critical
components using external measurement devices. The performance
verification consists of several tests (Table 7-1).
Table 7-3 summarizes the test equipment required, and Table 7-4 summarizes
the service accessories required for the performance verification. Check the
calibration status of all test equipment before use.
Required Test Equipment for Performance Verification
DescriptionRecommended Manufacturer/Model
Digital multimeter (DMM) and frequency counter
accurate to three decimal places
Electrical safety analyzerDale LT 5440 or equivalent
Pneumatic calibration analyzer(s) capable of
measuring low pressure (cmH2O), flow rate (LPM),
volume (Liters BTPS), and respiratory rate
Utility Software
Calibration and testing of the BiPAP Focus requires
the use of Respironics Utility Software
Local supplier
Respironics P/N 1012598 or equivalent
Log on to
http:// servicesoftware.respironics.com
and download the Utility Software onto
your PC.
Table 7-3: Required Test Equipment for Performance Verification
Required Service Accessories for Performance Verification
WARNING:To prevent disease transmission, use protective equipment when handling
contaminated bacteria filters or other patient accessories. Follow
manufacturers' labeling and institutional guidelines for disposal of
contaminated accessories.
1. Before servicing the ventilator, clean and inspect as follows:
•Remove humidifier connections from the ventilator, if applicable.
•Visually inspect the exterior of the ventilator for damage. Replace
damaged parts as needed.
•Clean the ventilator exterior as described in the BiPAP Focus Clinical Manual.
•Clean the ventilator interior using an ESD-safe vacuum.
•Remove and inspect the air inlet filters. Clean or replace as
described in the BiPAP Focus Clinical Manual.
2. Connect a standard USB cable between the service PC and the USB
port on the back panel of the ventilator.
3. Download and execute the Service Center Tools software (http://
servicesoftware.respironics.com) and follow the prompts to retrieve the
significant event log (the log includes the ventilator's configuration
and hour meter reading).
4. Print the significant event log and attach to the Performance
Verification Data Form (page 7-29).
Electrical Safety TestThe electrical safety test verifies that the ground resistance and forward and
reverse leakage current are within specified limits. Record the following
information on Performance Verification Data Form (page 7-29).
Use the DB9 shell on the Nurse call station / serial
communications port at the back of the ventilator to connect
the electrical safety analyzer to ventilator ground.
1. Check that the ground resistance < 0.2 ohm (Ω).
2. Turn ventilator on and wait until gas delivery begins.
3. Check that the forward and reverse leakage current is < 100
microamperes (µA) for ventilators connected to 100-120 V), or < 300
µA for ventilators connected to 220-240 V.
The BiPAP Focus will record and track several different parameters (e.g.
patient pressures, apnea events, when and how the device is used, error codes,
etc.). To do this in a logical manner and for a technician or therapist to know
exactly when a certain event has occurred, the BiPAP Focus runs and records
events in real-time. This time is checked and compared to your computers
time when running the calibration software. If the time does not match, the
calibration will fail. Therefore, you must perform the real-time clock calibration
before you proceed with the BiPAP Focus calibration.
1. Ensure AC power is connected to the BiPAP Focus.
2. Remove the bacteria filter from the ventilator if it is connected.
3. Start the ventilator in Normal mode. Be sure the vent is in S/T mode.
4. Connect the universal serial bus (USB) cable between the service PC
and ventilator.
NOTE:Do not connect the USB cable through a hub or docking station. Using
an intermediate connection causes communication errors.
5. Connect the female end of the serial communications cable to the
service PC. Then connect the male end labeled Software/Rasp to the
ventilator.
6. Open the Service Center Tools and select “Read Serial Number &
Model number”. Write down the serial number and the model number
for use later on during the calibration.
7. Open the Service Center Tools and select “Real-time Clock
Calibration”.
8. Click the red “Set Clock/Verify Clock” button in the upper left-hand
corner to begin calibration (the button will turn green).
If calibration fails, confirm that the BiPAP Focus Time and Date are set to
within 5 minutes of the service PC. Re-run the calibration. If the calibration
fails again, replace the controller PCB and retest.
MFTS CalibrationThis procedure provides instructions for calibrating the BiPAP Focus from the
Multi Function Test Station (MFTS). The results of this calibration can be
printed and used as a final test data sheet that can be retained as part of the
device history record.
NOTE:To preform a Field Calibration using a PC refer to “Field Calibration” on
page 7-17.
Multi Function Test Station Set-up (MFTS)
Refer to Figure 7-4. Start the ventilator in Normal mode. While in S/T mode
set the Respiratory Rate to 4bpm.
1. Ensure the computer and monitor are turned “ON”.
2. Ensure the MFTS is connected to a 110 VAC and 220VAC power
source.
Figure 7-4: MFTS Setup
3. Ensure the MFTS is connected to a negative pressure source.
1. Select a unit from the warm-up stand and ensure it has been running
for a minimum of 30 minutes. Power of unit and move to the MFTS.
2. Connect the Druck DPI-260 O
3. Connect the power and RS232 cables to the back of the unit.
4. Start the BiPAP Focus in diagnostic mode. Power on the unit and
press the Standby key, then immediately press both the Alarm Silence
and Alarm Reset keys simultaneously until the unit enters diagnostic
mode then press Continue.
1. Click the green Test UUT box on the PC screen. Refer to Figure 7-5.
2. The software will now run a series of tests on the UUT. The person
conducting the test will need to follow on-screen instructions
throughout the testing process.
NOTE:Retrieve and WRITE down the BLOWER SUBSYSTEM SERIAL
NUMBER from the BiPAP Focus Product Information screen. It may be
necessary to input the blower subsystem serial number if the memory is
cleared because it failed calibration.
3. When prompted enter serial number of the sub-assembly and click
OK.
Chapter 7
Figure 7-8: Entering Serial Number
4. When prompted enter the model number, enter 1026652 and click