LAST EDITED: 2000-01-11 by HO
* A K 1 0 0 E R R O R M E S S A G E E X P L A N A T I O N S *
LAST EDITED: 2000-01-11 by HO.
Error messages from AK 100 will now be prepared for three different
error levels depending on the possibility to recover or restart.
1. Unconditional technical error. No restart or recovery attempts.
This will be used where patient safety cannot be guaranteed in presence
of the error.This could be caused by some serious hardware error.
2. Conditional technical error. Continued treatment is allowed given that
a certain condition is fulfilled or a confirmation has been made.
These errors are marked with "/" before the error code, "/FCN 5.02 002".
3. Recoverable technical error. A number of restart attempts will
be made. If this is unsuccessful an unconditional or conditional
technical error will appear.
These errors are marked with "*" before the error code, "*FCN 8.09 001".
The letters [F,T,D,S] can follow the names of the functions.
[F,.....] means that the error codes can appear during the function
checks.
[.,T,...] means that the errors can appear during treatment.
[...,D,.] means that the errors can appear during rinse or disinfection.
[.....,S] means that the errors can appear during service mode.
Look in the end of file for:
AK 100 attention explanation.
AK 100 incorrect operation.
LED STATUS MESSAGES
TIME DISPLAY ERROR MESSAGES/MAIN BOARD LED STATUS CPU A IN BM100 / BM102.
1. CPU INIT
------
"FCh" is displayed during starup. BM main board LED status
indicates the test that is in progress.
"Exy" is displayed when a test fails. BM main board LED status
indicates the test that failed.The correspondence between
time display and main board LED indication will be:
LED indicator V15-V17 = Least significant digit on time display (y).
V12-V14 = Most significant digit on time display (x).
V10,V11 = Not significant on time display.
NOTE. The appearance of the first LED status code 11000000 may,
besides the status explained below, also be considered as
a 'CPU A is executing' indication.
Also note,that it is advisable NOT to interfere with the
machine during start up test other than when explicitly
advised to do so.(Non-relevant error messages may occur)
Status codes 11 000 000 through 11 101 111 are BASIC tests performed before
the operating system is allowed to start.
INITIAL TESTS ( --000nnn )
Error Diode status (V10 - V17)
------
V V V V V V V V
1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7
"E00" / 1 1 0 0 0 0 0 0 - CPU A test code verification
"E01" / 1 1 0 0 0 0 0 1 - Test of CPU A clock signals
"E02" / 1 1 0 0 0 0 1 0 - Test of CPU A 8279 display RAM
"E03" / 1 1 0 0 0 0 1 1 - Test of function of CPU A (80188)
"E04" / 1 1 0 0 0 1 0 0 -
"E05" / 1 1 0 0 0 1 0 1 -
"E06" / 1 1 0 0 0 1 1 0 -
"E07" / 1 1 0 0 0 1 1 1 -
MEMORY TESTS ( --001nnn )
Error Diode status
------
V V V V V V V V
1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7
"E10" / 1 1 0 0 1 0 0 0 - Test of CPU A middle CS 0 memory
"E11" / 1 1 0 0 1 0 0 1 - Test of CPU A middle CS 1 memory.
Checksum error in prom.
Adress 20000H - 3FFFFH.
"E12" / 1 1 0 0 1 0 1 0 - Test of CPU A middle CS 2 memory
"E13" / 1 1 0 0 1 0 1 1 - Test of CPU A middle CS 3 memory
"E14" / 1 1 0 0 1 1 0 0 - Test of CPU A middle CS 4 memory
"E15" / 1 1 0 0 1 1 0 1 - Test of CPU A upper CS memory.
Checksum error in prom.
Adress E0000H - FFFFFH.
"E16" / 1 1 0 0 1 1 1 0 - Test of CPU A data memory initialization
"E17" / 1 1 0 0 1 1 1 1 - Test of CPU A middle CS 5 memory.
Checksum error in prom.
Address A0000H-BFFFFH.
MISCELLANEOUS I/O TESTS ( --010nnn )
Error Diode status
------
V V V V V V V V
1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7
"E20" / 1 1 0 1 0 0 0 0 - Test of CPU A timer 9513 (IC 85)
"E21" / 1 1 0 1 0 0 0 1 - Test of CPU A timer 9513 (IC 104)
"E22" / 1 1 0 1 0 0 1 0 - Test of CPU A digital pot logic (IC 126)
"E23" / 1 1 0 1 0 0 1 1 - Test of CPU A digital pot logic (IC 128)
"E24" / 1 1 0 1 0 1 0 0 -
"E25" / 1 1 0 1 0 1 0 1 -
"E26" / 1 1 0 1 0 1 1 0 -
"E27" / 1 1 0 1 0 1 1 1 -
MISCELLANEOUS I/O TESTS (PF-TESTS?) ( --011nnn )
Error Diode status
------
V V V V V V V V
1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7
"E30" / 1 1 0 1 1 0 0 0 - 1) Non-volatile memory battery failure.
2) P110 not connected.
"E31" / 1 1 0 1 1 0 0 1 -
"E32" / 1 1 0 1 1 0 1 0 -
"E33" / 1 1 0 1 1 0 1 1 -
"E34" / 1 1 0 1 1 1 0 0 -
"E35" / 1 1 0 1 1 1 0 1 -
"E36" / 1 1 0 1 1 1 1 0 -
"E37" / 1 1 0 1 1 1 1 1 -
KEYBOARD CONTROL TESTS ( --100nnn )
Error Diode status
------
V V V V V V V V
1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7
"E40" / 1 1 1 0 0 0 0 0 - Test of CPU A 8279 FIFO status test.
"E41" / 1 1 1 0 0 0 0 1 - Test of CPU A 8279 scan to sense shortage.
"E42" / 1 1 1 0 0 0 1 0 - Test of CPU A keyboard PAL.
"E43" / 1 1 1 0 0 0 1 1 - Test of CPU A keyboard scanning.
"E44" / 1 1 1 0 0 1 0 0 - Test of CPU A keyboard repeat circuitry
timing.
"E45" / 1 1 1 0 0 1 0 1 - Test of CPU A keyboard matrix simulated
closures.
"E46" / 1 1 1 0 0 1 1 0 -
"E47" / 1 1 1 0 0 1 1 1 -
FINAL BASIC TESTS ( --101nnn )
Error Diode status
------
V V V V V V V V
1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7
"E50" / 1 1 1 0 1 0 0 1 -
"E51" / 1 1 1 0 1 0 0 1 -
"E52" / 1 1 1 0 1 0 1 0 -
"E53" / 1 1 1 0 1 0 1 1 - Test of technical error lamp.
"E54" / 1 1 1 0 1 1 0 0 - Test of CPU A internal register content.
"E55" / 1 1 1 0 1 1 0 1 - Test of CPU B (8344) start up status.
"E56" / 1 1 1 0 1 1 1 0 - Test phase CPU A NMI interrupt.
"---" / 1 1 1 0 1 1 1 1 - CPU A operating system start.
Codes --11nnnn [E60]-[E67],[E70-E77] are reserved for use within CPU A
task AINIT.PLM. ALL tests passed main board LED status should be 00000000
and will be output in AINIT.
Error Diode status
------
V V V V V V V V
1 1 1 1 1 1 1 1
0 1 2 3 4 5 6 7
"E60" / 0 0 1 1 0 0 0 0 - CPU A initialization task started.
"E61" / 0 0 1 1 0 0 0 1 - CPU A error logger task start.
"E62" / 0 0 1 1 0 0 1 0 - CPU A data initialization.
"E63" / 0 0 1 1 0 0 1 1 - CPU B data initialization.
"E64" / 0 0 1 1 0 1 0 0 - CPU D data initialization.
"E65" / 0 0 1 1 0 1 0 1 - CPU data initialization.
"E66" / 0 0 1 1 0 1 1 0 - CPU data initialization.
"E67" / 0 0 1 1 0 1 1 1 - CPU data initialization.
"E70" / 0 0 1 1 1 0 0 0 - System data transfer start.
"E71" / 0 0 1 1 1 0 0 1 - System EEPROM initialization error.
"E72" / 0 0 1 1 1 0 1 0 -
"E73" / 0 0 1 1 1 0 1 1 -
"E74" / 0 0 1 1 1 1 0 0 -
"E75" / 0 0 1 1 1 1 0 1 -
"E76" / 0 0 1 1 1 1 1 0 -
"E77" / 0 0 1 1 1 1 1 1 - CPU A tasks start up.
LED status 00000000 indicate completed/passed basic and AINIT tests.
"FCh",however,will continue to be shown on time display until all
functional tests of the monitors are completed.
2. SUPERVISORY TASK
------
In some cases,an E-code in the range E80-EFF may show up on the time
display.Such a code indicates an error condition where it might not
be possible to route the message the normal way to the information
display.
Error
-----
This errorcodes are now saved as Mailerrors:
TSK E__ = task underrun
"E80" is supervisory low task (idle-task) underrun.
"E81" is ADC task underrun.
"E82" is AOTRC task underrun.
"E83" is ABTRC task underrun.
"E84" is FCN 0 task underrun.
"E85" is FCN 1 task underrun.
"E86" is FCN 2 task underrun.
"E87" is COM task underrun.
"E88" is INFO DISP task underrun. (FCN309)
"E89" is FCN 3 task underrun.
"E8A" is recovery task underrun. (FCN827)
"E8B" is AATRC task underrun.
"E90" is supervisory low task (idle-task) time-out.
"E91" is ADC task time-out.
"E92" is AOTRC task time-out.
"E93" is ABTRC task time-out.
"E94" is FCN 0 task time-out.
"E95" is FCN 1 task time-out.
"E96" is FCN 2 task time-out.
"E97" is COM task time-out.
"E98" is INFO DISP task time-out. (FCN309)
"E9A" is recovery task time-out. (FCN827)
"E9B" is AATRC task time-out.
"EA0" AOTRC transition controller time-out
"EA1" ABTRC transition controller time-out
MAIN BOARD LED STATUS FOR CPU B IN BM100 / BM102.
------
Power-up LED-status for CPU B (8344) is given by one green and
one red LED-diode indicating last successful test.
The status is defined as follows:
ORDER RED(V1) GREEN(V2) STATUS
------
1 On On Power-on.
2 Off Off Prior to start of tests.
3 On On CPU (8344) instruction set test.
4 On Off PROM checksum test.
5 Off Off CPU (8344) internal RAM test.
6 Off On External RAM test.
Lit green LED-diode and not lit red LED-diode means all tests are OK.
MAIN BOARD LED STATUS CPU C IN FM 100 / FM102.
------
Power-up LED-status for CPU C (8344) is given by one green and one
red LED-diode indicating last successful test.
The status is defined as follows:
ORDER RED(V53) GREEN(V52) STATUS
1 On On Power-on.
2 Off Off Prior to start of tests.
3 On On CPU (8344) instruction set test.
4 On Off PROM checksum test.
5 Off Off CPU (8344) internal RAM test.
6 Off On External RAM test.
Lit green led and not lit red led means all tests are OK.
(ERROR) INDICATION ON LEDS FOR CPU D IN FM100 / FM102.
------
0 = The LED is off,
1 = The LED is lit,
? = The LED is off or lit.
START UP TEST, NORMAL EXECUTION:
2 2 2 3 3 3 3 3 3 3 3 3 3 4 4 = LED NUMBER
7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 = LED NUMBER
------EXPLANATION:
0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 Cpu test 1 flags.
1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 Cpu test 2 register.
0 1 0 0 0 0 0 0 0 0 0 0 0 0 1 Cpu test 3 chip select.
1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 Set up chip select
0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 Ram test active.
1 0 1 0 0 0 0 0 0 0 0 0 0 0 1 Prom 2 test active.
0 1 1 0 0 0 0 0 0 0 0 0 0 0 1 Prom E test active.
START UP TEST, ERROR INDICATION:
2 2 2 3 3 3 3 3 3 3 3 3 3 4 4 = LED NUMBER
7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 = LED NUMBER
------EXPLANATION:
0 0 0 0 0 0 0 0 1 ? ? 0 0 0 1 Cpu error.(flag test)
1 0 0 0 0 0 0 0 1 ? ? 0 0 0 1 Cpu error.(register test)
0 1 0 0 0 0 0 0 1 ? ? 0 0 0 1 Cpu error.(chip select test)
1 1 0 0 0 0 0 0 1 ? ? 0 0 0 1 Cpu error.(set up chip sel.)
0 0 1 0 0 0 0 0 ? 1 ? 0 0 0 1 Ram error.
1 0 1 0 0 0 0 0 ? ? 1 0 0 0 1 Prom address 20000 error.
0 1 1 0 0 0 0 0 ? ? 1 0 0 0 1 Prom address E0000 error.
SUPERVISORY ERRORS (Task 0 is the low priority supervisory task)
2 2 2 3 3 3 3 3 3 3 3 3 3 4 4 = LED NUMBER
7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 = LED NUMBER
------EXPLANATION:
0 0 0 0 0 0 0 0 0 0 0 1 0 0 1 Task 0 timeout.
1 0 0 0 0 0 0 0 0 0 0 1 0 0 1 Task 1, ADC task timeout.
0 1 0 0 0 0 0 0 0 0 0 1 0 0 1 Task 2, DTRC task timeout.
1 1 0 0 0 0 0 0 0 0 0 1 0 0 1 Task 3, FCN task 0 timeout.
0 0 1 0 0 0 0 0 0 0 0 1 0 0 1 Task 4, FCN task 1 timeout.
1 0 1 0 0 0 0 0 0 0 0 1 0 0 1 Task 5, FCN task 2 timeout.
0 1 1 0 0 0 0 0 0 0 0 1 0 0 1 Task 6, COM task timeot.
0 0 0 0 0 0 1 0 0 0 0 1 0 0 1 Task 0 underrun.
1 0 0 0 0 0 1 0 0 0 0 1 0 0 1 Task 1, ADC task underrun.
0 1 0 0 0 0 1 0 0 0 0 1 0 0 1 Task 2, DTRC task underrun.
1 1 0 0 0 0 1 0 0 0 0 1 0 0 1 Task 3, FCN task 0 underrun.
0 0 1 0 0 0 1 0 0 0 0 1 0 0 1 Task 4, FCN task 1 underrun.
1 0 1 0 0 0 1 0 0 0 0 1 0 0 1 Task 5, FCN task 2 underrun.
0 1 1 0 0 0 1 0 0 0 0 1 0 0 1 Task 6, COM task underrun.
1 1 1 1 1 1 1 0 0 0 0 1 0 0 1 DTRC not running.
0 0 0 0 0 0 0 1 0 0 0 1 0 0 1 Out of SRB.
1 0 0 0 0 0 0 1 0 0 0 1 0 0 1 Out of SMR.
E R R O R L O G G E R M E S S A G E S
Listed below are error message explanations for error information
handled the normal way via the system error logger and which might
be read on the information display entering the error logger menue.
System messages.
SYS CONF 000 = No system request blocks(SRB:s) available
SYS CONF 001 = No system memory request blocks(SMR:s) available
SYS CONF 002 = Illegal internal MTOS call: X_OVIN
SYS CONF 003 = Illegal internal MTOS call: X_OVOUT
SYS CONF 004 = Illegal internal MTOS call: X_GET_BLOCK
SYS CONF 005 = Illegal internal MTOS call: X_FREE_BLOCK
SYS CONF 006 = Illegal internal MTOS call: X_ALLOC_8087
SYS INTR 000 = Divide error exception interrupt
SYS INTR 001 = Single step interrupt
SYS INTR 002 = Non=maskable interrupt
SYS INTR 003 = Breakpoint interrupt
SYS INTR 004 = Overflow exception interrupt
SYS INTR 005 = Array bounds exception interrupt
SYS INTR 006 = Unused opcode exception interrupt
SYS INTR 007 = Escape opcode exception interrupt
SYS INTR 008 = Reserved vector interrupt
SYS INTR UNX = Unexpected vector interrupt
SYS REAL 000 = Floating point illegal opcode
SYS REAL 001 = Floating point real overflow
SYS REAL 002 = Floating point integer overflow
CPU A task errors
TSK Exx = supervisory task A "Exx" errors above
Transition controller messages.
TzA Pxxx ttt = Process nr xxx out of range in transition test.
TzB Pxxx yyy = State nr yyy out of range.
TzC Pxxx ttt = Test nr ttt out of range in transition test.
TzD P000 xxx = Process state shadow table corrupt in process xxx.
TzE Pxxx yyy = Process attempt to assume non-defined state yyy.
TzF Pxxx yyy = State yyy attempt to control process at own or higher
level.
TzG Pxxx yyy = State yyy attempt to control non-defined process.
TzH Pxxx yyy = State yyy attempt to control non-defined function.
TzI Pxxx yyy = State yyy attempt to duplicate process control.
TzJ Pxxx yyy = State yyy attempt to duplicate function control.
TzK Pxxx yyy = State yyy attempt to reference non-defined event-
control.
TzL Pxxx yyy = State yyy attempt to set non-defined event mode.
TzM P000 fff = Non-controlled function fff.
TzN Pxxx yyy = State yyy attempt to set non-existant output cross=
reference.
TzO jjjj iii = Crossreference iii references non-existant logical
output jjjj.
TzP P000 fff = Function shadow table corrupt in function fff.
TzQ jjjj iii = Output shadow table corrupt, crossreference iii,
output jjjj.
xxx = Process number
yyy = State number
z = Transition controller identifier [O,B,P,Q,F]
CPU A operating system errors
AOS INIT 000 = SVC ERROR : Communication task start.
AOS INIT 001 = SVC ERROR : AD=converter task start.
AOS INIT 002 = SVC ERROR : Opcom TRC task start.
AOS INIT 003 = SVC ERROR : Blood TRC task start.
AOS INIT 004 = SVC ERROR : Function task 0 start.
AOS INIT 005 = SVC ERROR : Function task 1 start.
AOS INIT 006 = SVC ERROR : Function task 2 start.
AOS INIT 007 = SVC ERROR : Supervisory high priority task start.
AOS INIT 008 = SVC ERROR : Supervisory low priority task start.
AOS INIT 009 = SVC ERROR : Information display task start.
AOS INIT 010 = SVC ERROR : EEPROM task start.
AOS INIT 011 = RIO ERROR : CPU D Power=up/Recovery string call.
AOS INIT 012 = SVC ERROR : Recovery task start.
AOS INIT 013 = SVC ERROR : Attention traco task start.
AOS INIT 014 = SVC ERROR : No recovery data from CPU D.(Timeout).
Bitbus communication errors. (CPU A and CPU D).
BIT INTR 000 = Bitbus protocol error in FIFO CPU B to CPU A.
The message did not end with command byte = 0.
The message is discarded.
BIT INTR 001 = Bitbus protocol error in FIFO CPU C to CPU D.
The message did not end with command byte = 0.
The message is discarded.
Flow generator communication errors. (CPU E).
FLG ERR 001 = Flow generator not responding.
FLG INTR 002 = Flow generator program restart error.
FLG INTR 003 = Flow generator NMI restart error.
FLG INTR 004 = Flow generator unused opcode error.
FLG INTR 005 = Flow generator cpu error.
FLG INTR 006 = Flow generator ram error.
FLG INTR 007 = Flow generator prom error.
FLG INTR 008 = Flow generator dialyzer pressure out of limit.
FLG INTR 009 = Flow generator pump motor in overload.
FLG INTR 010 = Flow generator pump motor out overload.
FLG INTR 011 = Flow generator ad offset out of limit.
FLG INTR 012 = Flow generatot ad reference out of limit.
FLG INTR 013 = Flow generator high pressure guard out of limit.
FM operating system errors.
DOS INIT 000 = Error in calling MTOS.
DOS INIT 001 = SVC ERROR : AD=converter task start.
DOS INIT 002 = SVC ERROR : Fluid TRC task start.
DOS INIT 003 = SVC ERROR : Function task 0 start.
DOS INIT 004 = SVC ERROR : Function task 1 start.
DOS INIT 005 = SVC ERROR : Function task 2 start.
DOS INIT 006 = SVC ERROR : Communication task start.
DOS INIT 007 = SVC ERROR : Supervisory high task start.
DOS INIT 008 = RIO ERROR : CPU D Power=up/Recovery string call.
DOS FCN0 000 = Error in calling MTOS.
DOS FCN1 000 = Error in calling MTOS.
DOS FCN2 000 = Error in calling MTOS.
FM test program errors.
RAM ERR 000 = Ram error from CPU D.
PRM ERR 000 = Prom error from CPU D.
PRM ERR 001 = Prom adress 20000 error from CPU D.
PRM ERR 002 = Prom adress E0000 error from CPU D.
FCH RAM 000 = Ram error from CPU D.
FCH PROM 002 = Prom adress 20000 error from CPU D.
FCH PROM 00E = Prom adress E0000 error from CPU D.
Function messages.
FCN x.xx yyy = Function error message
x.xx = Issuing functions number)
yyy - Function error type,application specific,
although 000 reserved for case ptr error)
FCN 1.00, AD FUNCTION (CPU C)
FCN 1.00 000 SOFTWARE ERROR
General description of conditions for occuring:
The software is not executing correctly.
Technical description of conditions for occuring:
One part of the software asks another part of the software
to execute code that does not exist.
Some possible explanations why the error has occured:
* The software code is incorrect.
* RAM error.
FCN 1.00 000 = Case error. The program is not working properly
FCN 1.00 001 = Channel address out of limit.
FCN 1.00 002 = AD overflow.
FCN 1.00 003 = Division by zero or overflow in treatment calculation.
FCN 1.00 004 = Offset value out of limit.
FCN 1.00 005 = Reference value out of limit.
FCN 1.00 006 = ADC locked in busy state.
FCN 1.00 007 = Diagnostic channel request out of limit (> 7).
FCN 1.00 008 = Division by zero or overflow in diagnostic calculation.
Fluid error function. (CPU B).
FCN 1.01 000 = Case error. The program is not working properly.
FCN 1.01 001 = Conductivity set error.
FCN 1.01 002 = Division by zero or overflow.
FCN 1.01 003 = PD AD overflow error.
FCN 1.01 004 = TEMP AD overflow error.
FCN 1.01 005 = Removed.
Previously: COND AD overflow error.
FCN 1.01 006 = Bicarbonate constant comparation error.
Protective system and CPU A differ in constants.
Infodisplay function. (CPU B).
FCN 1.02 001 = No hardware reply from infodiplay.
FCN 1.02 002 = Removed.
FCN 1.02 003 = Removed.
FCN 1.02 004 = Removed.
FCN 1.02 005 = Removed.
Buzzer function. (CPU B).
FCN 1.03 000 = Case error. The program is not working properly.
FCN 1.03 001 = Cpu B buzzer (H1) test error.
FCN 1.03 002 = Cpu A buzzer (H2) test error.
Possible explanation: There may be a bad connection to X0VC
from the FM power distribution board
FCN 1.03 003 = Buzzer already on even before buzzer test.
Check microphone or comparator.
Level detector function. (CPU B).
FCN 1.04 000 = Case error. The program is not working properly.
FCN 1.04 001 = Sync not toggled from cpu A.
FCN 1.04 002 = Removed.
Previously: No short burst or receiver trigged anyway.
FCN 1.04 003 = Reset of receiver failed.
FCN 1.04 004 = CPU A not responding on level detector alarm.
FCN 1.04 005 = Can not syncronize with CPU A.
FCN 1.04 006 = Removed.
Previously: Invalid DAC value.
Priming detector function. (CPU B).
FCN 1.05 000 = Case error. The program is not working properly.
FCN 1.05 001 = Sample error.
FCN 1.05 002 = No missing puls LED on puls.
FCN 1.05 003 = Invalid primingdetector combination.
* Possible explanation: IC40 or IC78 broken.
FCN 1.05 004 = Invalid high DAC value. Not inside PROM limit.
FCN 1.05 005 = Invalid low DAC value. Not inside PROM limit.
FCN 1.05 006 = Water filled tube comparator level to near
empty primingdetector comparator level.
FCN 1.05 007 = PRL(P_PRIM$DET$EMPTY),-TUBE,-BLOOD combination error.
FCN 1.05 008 = Can not synchronize with CPU A.
FCN 1.06, BLOOD PUMP FUNCTION (CPU B)
Purpose:
Please also refer to the description of FCN 5.00 and FCN 5.01.
* Checks the different ways to turn off the blood pumps during the
function check.
* Checks if the blood pumps have been rotating so much that the priming
must have been completed.
* Turns off the blood pumps if the protective system detects certain
alarms during treatment.
FCN 1.06 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.
FCN 1.06 001 BLOOD PUMP RUNNING WHILE SAFE BUS ALARMING ERROR [F]
General description of conditions for occuring:
The blood pump(s) were running during function test even if the safe
bus was set in alarm mode.
Technical description of conditions for occuring:
The safe bus was set in alarm mode. Current shoult NOT flow through it.
The relay K1 on the BM CPU board (K11353) should be deactivated and
the supply voltage for the blood pumps R24V should be 0V.
No other electronic signals tried to stop the blood pump. The
protective system detected that at least one of the blood pumps were
rotating during more than 1.6s.
Some possible explanations why the error has occured:
* The relay K1 on the BM CPU board is broken.
FCN 1.06 002 DOUBLE PUMP STOP WHILE SAFE BUS NOT ALARMING ERROR [F]
General description of conditions for occuring:
At least one of the blood pumps were not running during function test
when the safe bus was NOT set in alarm mode.
Technical description of conditions for occuring:
The safe bus was NOT set in alarm mode. Current should flow through it.
The relay K1 on the BM CPU board (K11353) should be activated and the
supply voltage for the blood pumps R24V should be 24V.
The protective system could not detect that both blood pumps were
rotating during 6.8s.
Some possible explanations why the error has occured:
* The arterial blood pump is broken.
* The venous blood pump is broken.
* Some of the electronics on the arterial blood pump
distribution board (K11345) are broken.
* Some of the electronics on the venous blood pump
distribution board (K11348) are broken.
* The relay K1 on the BM CPU board is broken.
* The monostable multivibrator IC 26 on the BM CPU board is broken.
* The protective system resets the monostable multivibrator IC 26 on the
BM CPU board.
* The blood pump cover sensor is broken.
* The blood pump overload sensor is broken.
* Some cablings are broken or not connected.
* The protective system detection of the blood pump rotation is broken.