AK100错误信息综述

* 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.

FCN 1.06 003 SINGLE PUMP STOP WHILE SAFE BUS NOT ALARMING ERROR [F]
General description of conditions for occuring:
The arterial blood pump was 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 the arterial blood pump
was rotating during 6.8s.

Some possible explanations why the error has occured:
* The arterial blood pump is broken.
* Some of the electronics on the arterial blood pump distribution board
is 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.

FCN 1.06 004 BLOOD PUMP FREQUENCY ERROR [F]
General description of conditions for occuring:
At least one of the blood pumps were running during function test while
none of them has got any input frequency.

Technical description of conditions for occuring:
The frequencies that tells the blood pumps to run were turned off. No
other electronic signals told the blood pumps to stop. The protective
system detected that at least one of the blood pumps was rotating
during 8.6s.

Some possible explanations why the error has occured:
* Some of the electronics on the venous blood pump distribution board
(K11348) is broken.
* Some of the electronics on the arterial blood pump distribution board
(K11345) is broken.

FCN 1.06 005 BLOOD PUMP ENABLE ERROR [F]
General description of conditions for occuring:
At least one of the blood pumps was running during function test while
CPU A had commanded them to stop.

Technical description of conditions for occuring:
CPU A told the blood pumps to stop by setting both the signals BPAE/
and BPVE/ to 5V. The protective system detected that at least one of
the blood pumps were rotating during 2.6s.

Some possible explanations why the error has occured:
* Some of the electronics on the venous blood pump distribution board
(K11348) is broken.
* Some of the electronics on the arterial blood pump distribution board
(K11345) is broken.
* The IC58 on the BM CPU board (K11352) is broken.

FCN 1.06 006 BLOOD PUMP TRIG ERROR [F]
General description of conditions for occuring:
At least one of the blood pumps were running during function test while
CPU A tried to stop them.

Technical description of conditions for occuring:
CPU A did not trig the monostable multivibrator IC 26 on the BM CPU
board.The protective system detected that at least one of the blood
pumps were rotating during 6.6s.

Some possible explanations why the error has occured:
* The monostable multivibrator IC 26 on the BM CPU board (K11353) is
broken.
* The relay K1 on the BM CPU board (K11353) is broken.

Safety gaurd function. (CPU B).

FCN 1.07 000 = Case error. The program is not working properly.
FCN 1.07 001 = Safety guard pressure AD overflow error.

Heater function. (CPU C).

FCN 1.08 000 = Case error. The program is not working properly.

EEPROM control function, FM protective system. (CPU C).

FCN 1.09 000 = Case error. The program is not working properly.

The remaining error messages is built according to:

FCN 1.09 2xy

where 2 = current I2C-bus, FM 8344 I2C-bus.
x = current EEPROM address.

Address EEPROM
0 MAIN BOARD CPU C.
1 C2G. CONDUCTIVITY/TEMPERATURE 2 GUARD CPU C.
2 AUP. AUXILIARY CHANNEL. CPU C.
3 BLD. BLOOD LEAK DETECTOR.
4 SAG. SAFETY BYPASS GUARD.
5 PD1. DIALYSIS PRESSURE.

y = error type: 0, EEPROM acknowledge or CRC verification error.
1, EEPROM header verification error.
2, parameter validation error.

Watch-dog driver function. (CPU B).

FCN 1.10 001 = Communication error, no acknowledge detected.
FCN 1.10 002 = Unexpected reply from watch-dog.

Watch-dog driver function. (CPU C).

FCN 1.11 001 = Communication error, no acknowledge detected.
FCN 1.11 002 = Unexpected reply from watch-dog.

Direct valve function. (CPU B).

FCN 1.12 000 = Case error. The program is not working properly.

Direct valve function. (CPU C).

FCN 1.13 000 = Case error. The program is not working properly.

Clamp function. (CPU B).

FCN 1.14 000 = Case error. The program is not working properly.
FCN 1.14 001 = Venous clamp should not be open error.
FCN 1.14 002 = Arterial clamp should not be open error.
FCN 1.14 003 = Venous clamp should not be closed error.
FCN 1.14 004 = Arterial clamp should not be closed error.

EEPROM control function, BM protective system. (CPU B).

FCN 1.15 000 = Case error. The program is not working properly.

The remaining error messages is built according to:

FCN 1.15 4XZ

where 4 = current I2C-bus, BM 8344 I2C-bus.
X = current EEPROM address.

Address EEPROM
0 MAIN BOARD CPU B, level detector, priming
detector and concentrate presets.

Y = error type: 0, EEPROM acknowledge or CRC verification error.
1, EEPROM header verification error.
2, parameter validation error.

Conversion function. (CPU B).

FCN 1.16 000 = Case error. The program is not working properly.

Service strap function. (CPU B).

FCN 1.17 000 = Case error. The program is not working properly.

FCN 1.18, BLOOD LEAK FUNCTION (CPU C)
Purpose:
* The blood leak transmitter sends light to the blood leak receiver. If
the receiver detects too little light during the function checks, then
an attention is given.
* If the receiver detects too little light during treatment, then a blood
leak alarm is given.
* Resets the blood leak alarm when the operator presses the blood leak
key.
* Checks that a blood leak can be detected by turning off the light for
7s during the function checks and for 7s every 5 minutes during
treatment.

FCN 1.18 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 1.18 001 BLOOD LEAK SENSOR TEST "LED OFF" FAILED [F,T,D]
General description of conditions for occuring:
The blood leak receiver detected too much light when the blood leak
transmitter was told to be turned off.

Technical description of conditions for occuring:
The blood leak transmitter was told to be turned off.
Wait 7s.
QRI(QI_BLOOD$LEAK) < PW(EPW_BLOOD$LEAK$OFF).
(QRI(QI_BLOOD$LEAK) = 0 when the fluid is completely transparent and
it is about 120 when the fluid is completely dark.)

Some possible explanations why the error has occured:
* Incorrect blood leak detector calibration.
* The blood leak receiver is broken.
* The A/D system is broken.
* The blood leak transmitter was never turned off.

Some hints of what to do if the error occurs:
Check the blood leak detector calibration.

FCN 1.18 002 BLOOD LEAK AD OVERFLOW
General description of conditions for occuring:
The error code has been removed.

Some possible explanations why the error has occured:
* Signal to AD system to high. ( > 60 mV.)
* Resistor R5 on bloodleak detector board to big, this will cause a
signal that is to high for the AD converter. Recalibrate.
* Bloodleak sensor partially filled. The light beam was reflected in the
fluidsurface.
* Strong infra red abient light.
* AD converter is not working properly.

FCN 1.18 003 CPU A IS NOT RESPONDING ON BLOOD LEAK DETECTOR ALARM
General description of conditions for occuring:
The error code has been removed.

FCN 1.18 004 BLOOD LEAK TEST ERROR DURING FUNCTION CHECK
General description of conditions for occuring:
The error code has been removed.
The detector was not able to see that the infra red beam was lit.

Technical description of conditions for occuring:
QRI(QI_BLOOD$LEAK) > PW(EPW_BLOOD$LEAK$ON) during test.

Some possible explanations why the error has occured:
* Dirty bloodleak detector.
* The bloodleak detector was not filled with fluid when this test was
done.
* Infra red diode not working properly.
* Aborted heatdisinfection might cause this meassage, due to a slight
thermal change in the phototransistor.

HDF scale supervision function.

FCN 1.25 000 = Case error. The program is not working properly.

Profiling function.(Na profiling in Acetate mode and
Na, HCO3 profiling in Bicarbonate mode)

FCN 1.26 000 = Case error. The program is not working properly.
FCN 1.26 001 = Undefined Na type in Bicarbonate mode neither of (Off,Linear,Degressive,Progressive).
FCN 1.26 002 = Undefined HCO3 type in Bicarbonate mode neither of (Off,Linear,Degressive,Progressive).
FCN 1.26 003 = Undefined Na type in Acetate mode neither of (Off,Linear,Degressive,Progressive).
FCN 1.26 004 = Division by zero or overflow error.

Profiling parameter set function.

FCN 1.27 000 = Case error. The program is not working properly.
FCN 1.27 001 = Removed.
Previously: No correct safememory area for profiling setings.
FCN 1.27 002 = Irelevant profiling model selected.
FCN 1.27 003 = Division by zero or overflow error.

HDF infusion pump rate supervision function.

FCN 1.28 000 = Case error. The program is not working properly.

HDF infusion pump rate calculation function.

FCN 1.29 000 = Case error. The program is not working properly.
FCN 1.29 001 = The HDF infusion pump is running to fast.
FCN 1.29 002 = A pump error has occured .
General description of conditions for occuring:
Infusion pump running when blod pump is stopped(Not in EXTRA mode).
Infusion pump stopped in EXTRA mode.

Arterial pressure guard supervision. (CPU A).

FCN 2.00 000 = Case error. The program is not working properly.

Extra pressure supervision. (CPU A).

FCN 2.01 000 = Case error. The program is not working properly.
FCN 2.01 001 = Test error. Extra pressure was not appr. 0 mm Hg
during functional test, not even after attention.

Venous pressure supervision. (CPU A).

FCN 2.02 000 = Case error. The program is not working properly.
FCN 2.02 001 = Test error. Venous pressure was not appr. 0 mm Hg
during functional test, not even after attention.

Level detector function (CPU A).

FCN 2.03 000 = Case error. The program is not working properly.
FCN 2.03 001 = Receiver trigged by short kick puls.
FCN 2.03 002 = PRS has not answered the syncronizing puls.
FCN 2.03 003 = CPU A can not syncronize with CPU B.
FCN 2.03 004 = CPU B has not reset reciever latch.

Priming detector function. (CPU A).

FCN 2.04 000 = Case error. The program is not working properly.
FCN 2.04 001 = PRS has not detected the missing "LED ON" puls.
FCN 2.04 002 = Can not syncronize with CPU B.
FCN 2.04 003 = PRL(P_PRIM$DET$EMPTY),-TUBE,-BLOOD combination
error.

Arterial tidal volume supervision. (CPU A).

FCN 2.05 000 = Case error. The program is not working properly.

Arterial pump supervision function. CPU A).

FCN 2.07 000 = Case error. The program is not working properly.
FCN 2.07 001 = Technical error in the arterial pump.
FCN 2.07 002 = Arterial pump head does not move when it should.
FCN 2.07 003 = Arterial pump head move when it should not.
FCN 2.07 004 = Arterial pump head does not move whith right speed.

Venous pump supervision function. CPU A).

FCN 2.08 000 = Case error. The program is not working properly.
FCN 2.08 001 = Technical error in the venous pump.
FCN 2.08 002 = Venous pump head does not move when it should.
FCN 2.08 003 = Venous pump head move when it should not.
FCN 2.08 004 = Venous pump head does not move whith right speed.

Preset conversion function. CPU A).

FCN 2.09 000 = Case error. The program is not working properly.

Optional pressure function. (CPU A).

FCN 2.10 000 = Case error. The program is not working properly.
FCN 2.10 001 = Test error. Optional pressure was not appr. 0 mm Hg
during functional test, not even after attention.

Pressure transducer connection supervision. (CPU A).

FCN 2.11 000 = Case error. The program is not working properly.

HDF scale supervisory function. (CPU A).

FCN 2.12 000 = Case error. The program is not working properly.

Bargraphs. (CPU A).

FCN 3.00 000 = Case error venous pressure.
FCN 3.00 003 = Function state conflict ( Not 0 during lamp/LED-test).
FCN 3.01 000 = Case error blood flow.
FCN 3.01 003 = Function state conflict ( Not 0 during lamp/LED-test).
FCN 3.02 000 = Case error conductivity.
FCN 3.02 003 = Function state conflict ( Not 0 during lamp/LED-test).
FCN 3.03 000 = Case error temperature.
FCN 3.03 003 = Function state conflict ( Not 0 during lamp/LED-test).
FCN 3.04 000 = Case error extra pressure.
FCN 3.04 003 = Function state conflict ( Not 0 during lamp/LED-test).
FCN 3.05 000 = Case error TMP.
FCN 3.05 003 = Function state conflict ( Not 0 during lamp/LED-test).
FCN 3.06 000 = Case error UF volume.
FCN 3.06 003 = Function state conflict ( Not 0 during lamp/LED-test).
FCN 3.07 000 = Case error UF rate.
FCN 3.07 003 = Function state conflict ( Not 0 during lamp/LED-test).

FCN BGPH 001 = Lamp/LED broken : Venous press & Blood flow BGPH
FCN BGPH 004 = Shortage : Venous press & Blood flow BGPH
FCN BGPH 011 = Lamp/LED broken : Cond & Temp BGPH
FCN BGPH 014 = Shortage : Cond & Temp BGPH
FCN BGPH 021 = Lamp/LED broken : Extra press & TMP BGPH
FCN BGPH 024 = Shortage : Extra press & TMP BGPH
FCN BGPH 031 = Lamp/LED broken : UF-vol & UF-rate BGPH
FCN BGPH 034 = Shortage : UF-vol & UF-rate BGPH

UF gain control (CPU A)

FCN 3.08 000 = Case error. The program is not working properly.

Information display (CPU A)

FCN 3.09 xxx = Case error in main state xxx.
FCN 3.09 256 = SVC error.
FCN 3.09 258 = RIO error status=??.
FCN 3.09 259 = RIO error status=1.
FCN 3.09 260 = RIO error status=0.
FCN 3.09 261 = RIO error status=-1.
FCN 3.09 262 = RIO error status=-2.
FCN 3.09 263 = RIO error status=-3.
FCN 3.09 270 = reference to non-existant treatment text
FCN 3.09 271 = reference to non-existant service text
FCN 3.09 272 = reference to non-existant treatment language
FCN 3.09 280 = nonexistant chem type in EEB_CH$TYPE$0
FCN 3.09 281 = nonexistant chem type in EEB_CH$TYPE$1
FCN 3.09 282 = nonexistant chem type in EEB_CH$TYPE$2
FCN 3.09 283 = nonexistant preset type in OB_PRESET$TEXT
FCN 3.09 284 = nonexistant heating type in EEB_HEAT$TYPE$0
FCN 3.09 285 = nonexistant heating type in EEB_HEAT$TYPE$1
FCN 3.09 286 = nonexistant heating type in EEB_HEAT$TYPE$2
FCN 3.09 287 = nonexistant rinse type in EEB_RINSE$TYPE$0
FCN 3.09 288 = nonexistant rinse type in EEB_RINSE$TYPE$1
FCN 3.09 289 = nonexistant rinse type in EEB_RINSE$TYPE$2
FCN 3.09 981 = LLLA , Low limit lamp/LED. Nr : 43 broken
FCN 3.09 982 = LLLA , Low limit lamp/LED. Nr : 43 shortage
FCN 3.09 983 = SPLA , Set parameter lamp/LED. Nr : 44 broken
FCN 3.09 984 = SPLA , Set parameter lamp/LED. Nr : 44 shortage
FCN 3.09 985 = HLLA , High limit lamp/LED. Nr : 45 broken
FCN 3.09 986 = HLLA , High limit lamp/LED. Nr : 45 shortage
FCN 3.09 992 = lamp/LED test: two lamps broken.
FCN 3.09 993 = lamp/LED test: three lamps broken.
FCN 3.09 994 = lamp/LED test: one lamp broken.
FCN 3.09 995 = lamp/LED test: short circuit.
FCN 3.09 996 = lamp/LED test: short circuit.
FCN 3.09 997 = lamp/LED test: one or more lamp(s) or LED(s) broken.
FCN 3.09 998 = lamp/LED test: bad reply from cpu B.
FCN 3.09 999 = Main Case error. The program is not working
properly.

Access code control. (CPU A).

FCN 3.10 000 = Case error. The program is not working properly.

Lamp/LED functions. (CPU A).

Function 3.11 to 3.44, 3.75, 3.76, 3.78 : Key lamps/LEDs.

FCN 3.nn 000 = Case error. The program is not working properly.
FCN 3.nn 001 = Lamp/LED broken or bad connection.
FCN 3.nn 002 = Removed.
FCN 3.nn 003 = Function state conflict (Not 0 during lamp/LED-test).
FCN 3.nn 004 = Shortage error.

FCN 3.12 nnn = L 3 Auto heat lamp/LED test.
FCN 3.13 nnn = L 9 Auto rinse lamp/LED test.
FCN 3.14 nnn = L 4 Isolated UF lamp/LED test.
FCN 3.15 nnn = L 5 TMP mode lamp/LED test.
FCN 3.16 nnn = L 6 UF mode lamp/LED test.
FCN 3.17 nnn = L 10 Single needle mode lamp/LED test.
FCN 3.18 nnn = L 11 Acetate mode lamp/LED test.
FCN 3.19 nnn = L 12 Bicarbonate mode lamp/LED test.
FCN 3.20 nnn = L 7 Chemical disinfection lamp/LED test.
FCN 3.21 nnn = L 2 Heat disinfection lamp/LED test.
FCN 3.22 nnn = L 22 Heparin pump lamp/LED test.
FCN 3.23 nnn = L 14 Blood flow lamp/LED test.
FCN 3.24 nnn = L 15 Single needle parameters lamp/LED test.
FCN 3.25 nnn = L 17 Conductivity lamp/LED test.
FCN 3.26 nnn = L 16 Temperature lamp/LED test.
FCN 3.27 nnn = L 28 UF volume lamp/LED test.
FCN 3.28 nnn = L 29 UF rate lamp/LED test.
FCN 3.29 nnn = L 30 Level detector lamp/LED test.
FCN 3.30 nnn = L 32 Attention lamp/LED test.
FCN 3.31 nnn = L 18 Priming detector lamp/LED test.
FCN 3.32 nnn = L 34 pH lamp/LED test.
FCN 3.33 nnn = L 35 Blood leak lamp/LED test.
FCN 3.34 nnn = L 21 Time lamp/LED test.
FCN 3.35 nnn = L 31 Arterial guard lamp/LED test.
FCN 3.36 nnn = L 8 Rinse / Drain lamp/LED test.
FCN 3.37 nnn = L 13 Venous pressure lamp/LED test.
FCN 3.38 nnn = L 25 Extra pressure lamp/LED test.
FCN 3.39 nnn = L 26 TMP lamp/LED test.
FCN 3.40 nnn = L 36 Blood pump lamp/LED test.
FCN 3.41 nnn = L 38 Mute lamp/LED test.
FCN 3.42 nnn = L 39 Fluid bypass lamp/LED test.
FCN 3.43 nnn = L 41 Start / Stop lamp/LED test.
FCN 3.44 nnn = L 42 Hold lamp/LED test.
FCN 3.75 nnn = L 19 Profiling lamp/LED test.
FCN 3.76 nnn = L 23 HDF lamp/LED test.
FCN 3.78 nnn = L 24 HF lamp/LED test.

Remaining time calculation. (CPU A).

FCN 3.45 000 = Case error. The program is not working properly.

Passed time calculation. (CPU A).

FCN 3.46 000 = Case error. The program is not working properly.

Non-diffusion time (bypass time) calculation. (CPU A).

FCN 3.47 000 = Case error. The program is not working properly.

UF volume predict. (CPU A).

FCN 3.48 000 = Case error. The program is not working properly.

TMP - UF transition. (CPU A).

FCN 3.49 000 = Case error. The program is not working properly.

Blood flow path lamps/LEDs. (CPU A).

FCN 3.50 000 = Case error. The program is not working properly.
FCN 3.50 003 = Function state conflict ( Not 0 during lamp/LED-test ).

FCN 3.50 001 = Broken : AFL1 , Arterial Lamp/LED 1 Nr : 46
FCN 3.50 004 = Shortage : AFL1 , Arterial Lamp/LED 1 Nr : 46
FCN 3.50 011 = Broken : AFL2 , Arterial Lamp/LED 2 Nr : 47
FCN 3.50 014 = Shortage : AFL2 , Arterial Lamp/LED 2 Nr : 47
FCN 3.50 021 = Broken : VFL1 , Venous Lamp/LED 1 Nr : 48
FCN 3.50 024 = Shortage : VFL1 , Venous Lamp/LED 1 Nr : 48
FCN 3.50 031 = Broken : VFL2 , Venous Lamp/LED 2 Nr : 49
FCN 3.50 034 = Shortage : VFL2 , Venous Lamp/LED 2 Nr : 49

Fluid flowpath lamps/LEDs. (CPU A).

FCN 3.51 000 = Case error
FCN 3.51 003 = Function state conflict ( Not 0 during lamp/LED-test ).

FCN 3.51 001 = Broken : FLOL, Fluid Left Ok Lamp/LED Nr : 53
FCN 3.51 004 = Shortage : FLOL, Fluid Left Ok Lamp/LED Nr : 53
FCN 3.51 011 = Broken : FLAL, Fluid Left Alarm Lamp/LED Nr : 54
FCN 3.51 014 = Shortage : FLAL, Fluid Left Alarm Lamp/LED Nr : 54

FCN 3.51 021 = Broken : BYOL, Bypass Ok Lamp/LED Nr : 55
FCN 3.51 024 = Shortage : BYOL, Bypass Ok Lamp/LED Nr : 55
FCN 3.51 031 = Broken : BYAL, Bypass Alarm Lamp/LED Nr : 56
FCN 3.51 034 = Shortage : BYAL, Bypass Alarm Lamp/LED Nr : 56

FCN 3.51 041 = Broken : FROL, Fluid Right Ok Lamp/LED Nr : 57
FCN 3.51 044 = Shortage : FROL, Fluid Right Ok Lamp/LED Nr : 57
FCN 3.51 051 = Broken : FRAL, Fluid Right Alarm Lamp/LED Nr : 58
FCN 3.51 054 = Shortage : FRAL, Fluid Right Alarm Lamp/LED Nr : 58

FCN 3.51 061 = Broken : DLOL, Dialyzer Left Ok Lamp/LED Nr : 50
FCN 3.51 064 = Shortage : DLOL, Dialyzer Left Ok Lamp/LED Nr : 50
FCN 3.51 071 = Broken : DROL, Dialyser Right Ok Lamp/LED Nr : 51
FCN 3.51 074 = Shortage : DROL, Dialyser Right Ok Lamp/LED Nr : 51

FCN 3.51 081 = Broken : DRAL, Dialyzer Right Al. Lamp/LED Nr : 52
FCN 3.51 084 = Shortage : DRAL, Dialyzer Right Al. Lamp/LED Nr : 52

Fluid bypass (DIVA bus). (CPU A).

FCN 3.52 000 = Case error. The program is not working properly.

Venous pressure auto alarm limits adjust. (CPU A).

FCN 3.53 000 = Case error. The program is not working properly.

Extra pressure auto alarm limits adjust. (CPU A).

FCN 3.54 000 = Case error. The program is not working properly.

TMP auto alarm limits adjust. (CPU A).

FCN 3.55 000 = Case error. The program is not working properly.

Time display. (CPU A).

FCN 3.56 000 = Case error. The program is not working properly.

Keyboard input. (CPU A).

FCN 3.57 000 = Case error. The program is not working properly.
FCN 3.57 001 = Hardware error. The keyboard controller requests
an interrupt but the CPU cannot determine which
key was pressed.
FCN 3.57 002 = Error in START/UF/STOP KEY handshaking with CPU B
General description of conditions for occuring:
START/UF/STOP key is stuck or does not respond.

Manual data input. (CPU A).

FCN 3.58 000 = Main Case error. The program is not working properly.
FCN 3.58 xxx = Case error in main state 0 - 255.
FCN 3.58 256 = OI_UF$RATE$SET has become negative

Machine off. (CPU A).

FCN 3.59 000 = Case error. The program is not working properly.
FCN 3.59 001 = Estimated heat time too large.
FCN 3.59 002 = Estimated rinse time too large.
FCN 3.59 003 = Machine still running after machine-off sequence.
FCN 3.59 004 = clock alarm write error.
FCN 3.59 005 = clock read error.
FCN 3.59 006 = dummy alarm write error.
FCN 3.59 007 = clock NODA write error.
FCN 3.59 008 = clock COMP write error.
FCN 3.59 009 = Auto on (heat/rinse) safememory area checksum error.
This area is set to defaul values when error.
FCN 3.59 010 = Auto on (heat/rinse) safememory week sceduler area
checksum error.
This area is set to defaul values when error.
To correct error change time in week sceduler.

Main buzzer control. (CPUA).

FCN 3.60 000 = BM case error. The program is not working properly.
FCN 3.60 001 = FM case error. The program is not working properly.

Blood potentiometer data input. (CPU A).

FCN 3.61 000 = Case error. The program is not working properly.

Heparin auto stop limit. (CPU A).

FCN 3.62 000 = Case error. The program is not working properly.

Linear transducer calibration calculation. (CPU A).

FCN 3.63 000 = Case error. The program is not working properly.

Real time calculation. (CPU A).

FCN 3.64 000 = Case error. The program is not working properly.
FCN 3.64 002 = Error when writing YEAR in EEPROM.
FCN 3.64 003 = CMOS realtime clock was not initialized.
Automatic initialization follows, but previous
settings are lost.
FCN 3.64 004 = The time saved in battery powered RAM is corrupt.
Previous settings are lost.
FCN 3.64 1xy = Error accessing CMOS realtime clock over the I2C bus:
x = type of access
x = 1 reading time once every minute
x = 2 reseting alarm time at startup
x = 3 reseting NODA flag at startup
x = 4 reseting COMP flag at startup
x = 5 reading time at startup
x = 6 writing valid time at startup
y = I2C access error
y = 1 I2C acknowledge error
y = 2 I2C byte address error
y = 9 I2C bus address error (bus 3 is not valid)

Select chemical mode. (CPU A).

FCN 3.65 000 = Case error. The program is not working properly.

Parallel E2prom function. (CPU A).

FCN 3.66 000 = Case error. The program is not working properly.
FCN 3.66 001 = CRC error.
FCN 3.66 002 = Preset variable out of range.
FCN 3.66 003 = Too few variables in EEPROM according to program.
Initiate the new variables in preset handling.
FCN 3.66 004 = EEPROM read error.
FCN 3.66 005 = EEPROM write error.
FCN 3.66 006 = PC preset calculation not performed.
FCN 3.66 007 = PC preset not compleat.
FCN 3.66 008 = Default preset error in EEL array.
FCN 3.66 009 = Default preset error in EEB array..
FCN 3.66 010 = Default preset error in EEW array..
FCN 3.66 011 = Default preset error in EEI array..
FCN 3.66 012 = Default preset error in EER array..
FCN 3.66 013 = PC preset to CPU D not performed.
FCN 3.66 014 = PC preset to CPU B not performed.

Internal support function. (CPU A).

FCN 3.67 000 = Case error. The program is not working properly.

Battery test function. (CPU A).

FCN 3.68 000 = Case error. The program is not working properly.
FCN 3.68 001 = The 12V winding in the AC/DC unit is broken.

Lamp/LED test function. (CPU A).

FCN 3.69 000 = Case error lamp/LED test function.
FCN 3.69 001 = Lamp/LED port out of range [0..7] Lamp/LED test

Preset calculation function. (CPU A).
FCN 3.70 000 = Case error. The program is not working properly.

Conductivity function. (CPU A).

FCN 3.71 000 = Case error. The program is not working properly.
FCN 3.71 001 = Bicarbonate constant comparation error.
Protective system and CPU A differ in constants.

Concentrate preset mode/alternative function. (CPU A).

FCN 3.72 000 = Case error. The program is not working properly.

Attention function. (CPU A).

FCN 3.73 000 = Case error. The program is not working properly.

Bicarbonate mode time measurement function. (CPU A).

FCN 3.74 000 = Case error. The program is not working properly.

More lamps/LEDs. (CPU A).

FCN 3.75 nnn = Profiling lamp/LED. (See 3.11 to 3.44.)
FCN 3.76 nnn = HDF lamp/LED. (See 3.11 to 3.44.)
FCN 3.78 nnn = HF lamp/LED. (See 3.11 to 3.44.)

Profiling parameter set function.

FCN 3.79 000 = Case error. The program is not working properly.
FCN 3.79 001 = No correct safememory area for profiling setings.
FCN 3.79 002 = Irelevant profiling model selected.

Conductivity profiling function.

FCN 3.80 000 = Case error. The program is not working properly.
FCN 3.80 001 = NA undefined profile type.
FCN 3.80 002 = HCO3 undefined profile type.
FCN 3.80 003 = NA AC undefined profile type.

Convert function. Convert preset variables.

FCN 3.81 000 = Case error. The program is not working properly.

UF equation and UF gain utilities (UF profiling).

FCN 3.82 000 = Case error. The program is not working properly.
FCN 3.82 001 = UF undefined profile type.

System pressure alarm limit controler.

FCN 3.83 000 = Case error. The program is not working properly.

Treatmenttime handling function in protective system.(CPU B)

FCN 3.84 000 = Case error. The program is not working properly.

GSS lamp/LED. (CPU A).

FCN 3.86 nnn = GSS lamp/LED. (See 3.11 to 3.44.)

BM AD function. (CPU A).

ADC INTR 000 = AD-buffer full error

FCN 4.00 000 = Undefined AD case error
FCN 4.00 001 = Undefined sequence selection
FCN 4.00 002 = Multiple AD-restarts
FCN 4.00 003 = Ref voltage out of range
FCN 4.00 004 = Offset voltage out of range
FCN 4.00 005 = Illegal sensitivity coeff
FCN 4.00 006 = Ref voltage limits start up check

FM AD function. (CPU D).

ADC INTR 001 = A/D timer load counter error call from
interrupt state.
ADC INTR 002 = A/D timer mode load hold register test error
call from interrupt state.
ADC 4.01 0xx = More then 20% overrange on channel xx
Channel xx Explanation
0 MAIN PC BOARD TEMPERATURE
1 MOTOR CURRENT
2 VALVE CURRENT
3 COND. CONTROL ACCETATE/TOTAL
4 DEGASS PRESURE
5 HEATING VESSEL TEMPERATURE
6 COND. CONTROL BCM OPTION
7 TEMP BCM COND. TRANSDUCER
8 UF TRANSDUCER COIL CURRENT
(POSITVE SYNC)
9 HIGH PRESSURE GUARD (HPGS)
10 DIALYSATE PRESSURE (PD)
11 AUX INPUT
12 AUX INPUT
13 AUX INPUT
14 OFFSET VOLTAGE AD-SYSTEM
15 REFERENCE VOLTAGE AD-SYSTEM

FCA 4.01 001 = A/D timer load counter error call from ad-task.
FCA 4.01 002 = A/D timer mode load hold register test error call
from ad-task.
FCB 4.01 xxx = AD conversion stop for xxx sec.
FCN 4.01 000 = Case error. The program is not working properly.
FCN 4.01 001 = Timer error.
FCN 4.01 002 = AD converter offset out of limits.
-10 mV < offest (= 0.0 mV) < + 10 mV
FCN 4.01 003 = AD converter reference out of limits.
45.45 mV < reference ( = 49.50 mV) < 54.89 mV
FCN 4.01 004 = AD-system timeout 1 sec.
FCN 4.01 005 = AD buffer full.
FCN 4.01 006 = AD buffer full and empty.

pH measuring function. (CPU D).

FCN 4.02 000 = Case error. The program is not working properly.
FCN 4.02 001 = Timer problem detected.
FCN 4.02 F00 = init timer error.
FCN 4.02 F01 = overflow error. (Currently not used after prom 3.40)
FCN 4.02 F02 = read timer error.

Clamp controller. (CPU A).

FCN 4.03 000 = Case error. The program is not working properly.
FCN 4.03 001 = Clamp verify error. Venous clamp was not opened.
FCN 4.03 002 = Clamp verify error. Arterial clamp was not opened.
FCN 4.03 003 = Clamp verify error. Arterial clamp was not closed.
FCN 4.03 004 = Clamp verify error. Venous clamp was not closed.
FCN 4.03 005 = Venous clamp does not close during functional test.
FCN 4.03 006 = Arterial clamp does not open during functional test.
FCN 4.03 007 = Venous clamp does not open during functional test.
FCN 4.03 008 = Arterial clamp does not close during functional test.

Flow generator transducer calibration function. (CPU D).

FCN 4.04 000 = Case error. The program is not working properly.

FCN 4.05, FLOW MEASURING FUNCTION (CPU D)
Purpose:
* NORMAL OPERATION: The signal TMO0 is used for the syncronisation of the
UF flow measurement. TMO0 is a 401.44 Hz square wave (50% duty cycle)
with TTL levels. It switches the magnetic field in the UF measuring
unit and controls the sampling of the recieved flowsignals. The two
measured flow signals are amplified at the UF preamplifier board. The
flow signals then passes multiplexers, are amplified and sampled on the
FM CPU board (K11302). The sampled voltages are converted to frequen-
cies that are measured by two counters that both are contained in IC94
on the FM CPU board (K11302). FCN 4.05 calibrates the counter values
and creates the variables FRR(FR_CH1$RATE) and FRR(FR_CH2$RATE).
FRR(FR_CH1$RATE) is the flow through channel 1 and it has the unit
ml/min. FRR(FR_CH2$RATE) is the flow through channel 2.
FRR(FR_UF$RATE) is calculated as the difference between the flow
through channel 2 and the flow through channel 1. FRR(FR_UF$RATE) has
the unit 1 l/h.
The UF volume FRR(FR_UF$VOL) is calculated. It's unit is 1 l.
* EVERY 30 MINUTES: A self calibration is done twice an hour.
The normal operation of the self calibration is as follows:
1 The measuring system is calibrated by first grounding the input and
then applying a reference voltage to the input.
2 ZEVA is opened and DIVA/BYVA are closed so that no flow passes the
flow cell. The zero flow signals are measured for 15 seconds and the
program checks that the signals are stable. Flow transducer offsets
are calculated. If neccessary the measurement is prolonged for 15s.
3 BYVA is opened and DIVA/ZEVA are closed so that the same flow passes
through flow channel 1 and flow channel 2. The flow signals are
measured after 15s. The measurement continues for 15s and the
program checks that the signals are stable. If neccessary the
measurement is prolonged for 15s. The program checks that
the parameters FRR(FR_UFR$TOLERANCE) and FRR(FR_UFR$OFFSET) have not
changed too much since the last self calibration. If a self
calibration fails, then it is repeated after 5 minutes.
* VALVE LEAKAGE TEST : The direct valve, the bypass valve and the zeroing
valve are leakage tested during the function checks. DIVA, BYVA and
ZEVA are closed. The flow output pump tries to force fluid through the
closed valves, and the flow measuring function FCN 4.05 checks that no
flow is leaking through them.

* CALIBRATION: The calibration is done in service mode, and it consists
of the following steps:

1 Tempered fluid flows through both the flow channels for 10 minutes.
2 The linearity of the UF measuring unit is checked by letting three
different flows flow through both the channels.
3 The offsets are calculated by not having any flow through the
channels.
4 The channel 1 coefficient is calculated by letting the flow through
channel 1 fill a reference volume.
5 The channel 2 coefficient is calculated by having the same flows
through both the channels.
6 The calibration parameters are verified.

If "Internal" mode is selected to update offset's and channel 2
coefficient then only steps 1,3 and 5 is performed.

NOTE! The channel 1 flow signal is forwarded through the VFC channel 2
and vice versa.
NOTE! The most probable error explanations are described the first.

FCN 4.05 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.05 001 INVALID CHANGE OF MUX ADDRESS [F,T,D,S]
General description of conditions for occuring:
The UF measurement multiplexers are not selecting the correct data.

Technical description of conditions for occuring:
The address signals UIS0 and UIS1 for the multiplexer IC3 on the FM
CPU board K11302 have incorrect values
OR
The address signals UIS2 and UIS3 for the multiplexer IC9 have
incorrect values.

Some possible explanations why the error has occured:
* FM CPU BOARD: The Multiplexer, IC3,IC9,IC11 is broken. (drawing K11302)
* FM CPU BOARD: The IO-PORT, IC102 is broken. (drawing K11302)
* FM CPU BOARD: The RAM, IC98 is broken. (drawing K11301)
* SOFTWARE: The program is not executing correctly.
* SOFTWARE: The software code is incorrect.

FCN 4.05 002 TIMER ERROR [F,T,D,S]
Please refer to the description of FCN 5.00 001.

Some possible explanations why the error has occured:
* FM CPU BOARD: The timer IC94 is broken (drawing K11302).

FCN 4.05 003 VFC CHANNEL 1 PULSE COUNTER OVERFLOW [F,T,D,S]
General description of conditions for occuring:
The pulse counter for VFC channel 1 has counted up to its maximum
value. Note! VFC channel 1 takes care of flow measurement signals CH2P
and CH2N!

Technical description of conditions for occuring:
The pulse counter for VFC channel 1 has counted up to its maximum value
at 5 following attempts
OR
The pulse counter has counted up to a value greater than 32768 at 5
following attempts.
The value of the pulse counter = SRR(6) and has the unit 0.08 ml/min.
The counter was set to 0 after each time the error occured.

Some possible explanations why the error has occured:
* FM CPU BOARD: The VFC, IC36 (K11302) or some of the components around
it are broken.

FCN 4.05 004 VFC CHANNEL 2 PULSE COUNTER OVERFLOW [F,T,D,S]
Please refer to the description of FCN 4.05 003
The value of the pulse counter = SRR(11) and has the unit 0.08 ml/min.
Note! VFC channel 2 takes care of flow measurement signals CH1P and CH1N.

FCN 4.05 005 TIMER ERROR [F,T,D,S]
Please refer to the description of FCN 5.00 001.

Some possible explanations why the error has occured:
* FM CPU BOARD: The timer IC94 on the FM CPU board K11302 is broken.

FCN 4.05 006 VFC CHANNEL 1 REFERENCE MEASUREMENT ERROR [F,T,D,S]
General description of conditions for occuring:
The VFC channel 1 has been connected to the reference voltage.
The pulse counter has measured a frequency that differs too much from
the frequency that usually is measured when the reference voltage is
connected.

Technical description of conditions for occuring:
VFC1.VALUE > 0.86241*VFC1.OFFSET for 2s
OR
VFC1.VALUE < 0.82859*VFC1.OFFSET for 2s

VFC1.VALUE = SRR(6) and has the unit 0.08 ml/min.
VFC1.OFFSET = SRR(7) and has the unit 0.08 ml/min.
VFC1.REF = SRR(8) holds the result of the reference measurement
and has the unit 0.08 ml/min.

Some possible explanations why the error has occured:
* FM CPU BOARD: The VFC, IC36 or some of the passive components around it
is broken. Problems have been noted if the capacitors C46 and C50
are of ceramic type. From approx. FM serial No. 4750 these capacitors
are changed to a polypropylene type (100 116 003). Please refer to
General Information 179 for more details.
* FM CPU BOARD,TMO0: The signal TMO0 is not present or the levels are out
of the TTL specification (low level<0.5 Volt, high level>2.4 Volt). One
reason for this error could be that there is a bad connection between
the CPU, IC101 on the FM CPU board (K11301) and its socket. The socket
should be manufactured by AMP. Sockets from other manufacturers have
caused problems.
* FM CPU BOARD: The timer, IC94 on the FM CPU board K11302 is not working
properly. The sampling pulses at pin 2 and 3 are incorrect or missing.
The pulse duration should be 50 microseconds and the pulse repetition
time should be 2.49 milliseconds. The pulses should have TTL levels.
* FM CPU BOARD,TMO0: The signal TMO0 is incorrect as the CPU, IC101 is
broken or the driver IC113 is broken.
* UF DRIVER BOARD,TMO0: TMO0 short circuit. If TMO0 becomes correct when
the flow transducer is disconnected then the error is probably caused
by a broken IC2 on the UF driver board K11195.
* FM CPU BOARD: The sample and hold circuits IC27 and IC29 are broken.
* FM CPU BOARD: The multiplexer IC3 is broken.
* FM CPU BOARD: The amplifier IC20 or some of the components around it
are broken.

FCN 4.05 007 VFC CHANNEL 2 REFERENCE MEASUREMENT ERROR [F,T,D,S]
General description of conditions for occuring:
The VFC channel 2 has been connected to the reference voltage.
The pulse counter has measured a frequency that differs too much from
the frequency that usually is measured when the reference voltage is
connected.

Technical description of conditions for occuring:
VFC2.VALUE > 0.86241*VFC2.OFFSET for 2s
OR
VFC2.VALUE < 0.82859*VFC2.OFFSET for 2s

VFC2.VALUE = SRR(11) and has the unit 0.08 ml/min.
VFC2.OFFSET = SRR(12) and has the unit 0.08 ml/min.
VFC2.REF = SRR(13) holds the result of the refernce measurement
and has the unit 0.08 ml/min.

Some possible explanations why the error has occured:
* FM CPU BOARD: The VFC, IC38 or some of the passive components around it
is broken. Problems have been noted if the capacitors C46 and C50
are of ceramic type. From approx. FM serial No. 4750 these capacitors
are changed to a polypropylene type (100 116 003). Please refer to
General Information 179 for more details.
* FM CPU BOARD,TMO0: The signal TMO0 is not present or the levels are out
of the TTL specification (low level<0.5 Volt, high level>2.4 Volt). One
reason for this error could be that there is a bad connection between
the CPU, IC101 on the FM CPU board (K11301) and its socket. The socket
should be manufactured by AMP. Sockets from other manufacturers have
caused problems.
* FM CPU BOARD: The timer, IC94 on the FM CPU board K11302 is not working
properly. The sampling pulses at pin 2 and 3 are incorrect or missing.
The pulse duration should be 50 microseconds and the pulse repetition
time should be 2.49 milliseconds. The pulses should have TTL levels.
* FM CPU BOARD,TMO0: The signal TMO0 is incorrect as the CPU, IC101 is
broken or the driver IC113 is broken.
* UF DRIVER BOARD,TMO0: TMO0 short circuit. If TMO0 becomes correct when
the flow transducer is disconnected then the error is probably caused
by a broken IC2 on the UF driver board K11195.
* FM CPU BOARD: The sample and hold circuits IC26 and IC28 are broken.
* FM CPU BOARD: The multiplexer IC9 is broken.
* FM CPU BOARD: The amplifier IC20 or some of the components around it
are broken.

FCN 4.05 008 VFC CHANNEL 1 OFFSET MEASUREMENT ERROR [F,T,D,S]
General description of conditions for occuring:
The VFC channel 1 has been connected to 0V.
The pulse counter has measured a frequency that differs too much from
the frequency that usually is measured when 0V is connected.

Technical description of conditions for occuring:
(VFC1.VALUE-8907) > 2000 for 2s
OR
(VFC1.VALUE-8907) < -2000 for 2s.

VFC1.VALUE = SRR(6) and has the unit 0.08 ml/min.
VFC1.OFFSET = SRR(7) holds the result from the offset measurement
and has the unit 0.08 ml/min.

Some possible explanations why the error has occured:
* FM CPU BOARD: The VFC, IC36 or some of the passive components around it
is broken. Problems have been noted if the capacitors C46 and C50
are of ceramic type. From approx. FM serial No. 4750 these capacitors
are changed to a polypropylene type (100 116 003). Please refer to
General Information 179 for more details.
* FM CPU BOARD,TMO0: The signal TMO0 is not present or the levels are out
of the TTL specification (low level<0.5 Volt, high level>2.4 Volt). One
reason for this error could be that there is a bad connection between
the CPU, IC101 on the FM CPU board (K11301) and its socket. The socket
should be manufactured by AMP. Sockets from other manufacturers have
caused problems.
* FM CPU BOARD: The timer, IC94 on the FM CPU board K11302 is not working
properly. The sampling pulses at pin 2 and 3 are incorrect or missing.
The pulse duration should be 50 microseconds and the pulse repetition
time should be 2.49 milliseconds. The pulses should have TTL levels.
* FM CPU BOARD,TMO0: The signal TMO0 is incorrect as the CPU, IC101 is
broken or the driver IC113 is broken.
* UF DRIVER BOARD,TMO0: TMO0 short circuit. If TMO0 becomes correct when
the flow transducer is disconnected then the error is probably caused
by a broken IC2 on the UF driver board K11195.
* FM CPU BOARD: IC16 is broken.
* FM CPU BOARD: The sample and hold circuits IC27 or IC29 are broken.
* FM CPU BOARD: The multiplexer IC3 is broken.
* FM CPU BOARD: The amplifier IC20 or some of the components around it
are broken.

FCN 4.05 009 VFC CHANNEL 2 OFFSET MEASUREMENT ERROR [F,T,D,S]
General description of conditions for occuring:
The VFC channel 2 has been connected to 0V.
The pulse counter has measured a frequency that differs too much from
the frequency that usually is measured when 0V is connected.

Technical description of conditions for occuring:
(VFC2.VALUE-8907) > 2000 for 2s
OR
(VFC2.VALUE-8907) < -2000 for 2s.

VFC2.VALUE = SRR(11) and has the unit 0.08 ml/min.
VFC2.OFFSET = SRR(12) holds the result from the offset measurement
and has the unit 0.08 ml/min.

Some possible explanations why the error has occured:
* FM CPU BOARD: The VFC, IC38 or some of the passive components around it
is broken. Problems have been noted if the capacitors C46 and C50
are of ceramic type. From approx. FM serial No. 4750 these capacitors
are changed to a polypropylene type (100 116 003). Please refer to
General Information 179 for more details.
* FM CPU BOARD,TMO0: The signal TMO0 is not present or the levels are out
of the TTL specification (low level<0.5 Volt, high level>2.4 Volt). One
reason for this error could be that there is a bad connection between
the CPU, IC101 on the FM CPU board (K11301) and its socket. The socket
should be manufactured by AMP. Sockets from other manufacturers have
caused problems.
* FM CPU BOARD: The timer, IC94 on the FM CPU board K11302 is not working
properly. The sampling pulses at pin 2 and 3 are incorrect or missing.
The pulse duration should be 50 microseconds and the pulse repetition
time should be 2.49 milliseconds. The pulses should have TTL levels.
* FM CPU BOARD,TMO0: The signal TMO0 is incorrect as the CPU, IC101 is
broken or the driver IC113 is broken.
* UF DRIVER BOARD,TMO0: TMO0 short circuit. If TMO0 becomes correct when
the flow transducer is disconnected then the error is probably caused
by a broken IC2 on the UF driver board K11195.
* FM CPU BOARD: IC16 is broken.
* FM CPU BOARD: The sample and hold circuits IC26 or IC28 are broken.
* FM CPU BOARD: The multiplexer IC9 is broken.
* FM CPU BOARD: The amplifier IC20 or some of the components around it
are broken.

FCN 4.05 010 MEASURED MAGNETISATION CURRENT INCORRECT [F,T,D,S]
General description of conditions for occuring:
Measured magnetisation current differ to much from typical value.

Technical description of conditions for occuring:
( FRI(FI_UF$COIL$CU)/10000.0 - 0.23 ) > 0.05 A for 5s
OR
( FRI(FI_UF$COIL$CU)/10000.0 - 0.23 ) < - 0.05 A for 5s

SRI(37) has the unit 1 mA, and it corresponds to
FRI(FI_UF$COIL$CU) / 10.

Some possible explanations why the error has occured:
* UF PREAMP BOARD: The IC that generates the signal MFC0 is broken.
* UF DRIVER BOARD: Something is broken on the UF driver board.
* FM CPU BOARD,TMO0: The signal TMO0 is not present or the
levels are out of the TTL specification (low level<0.5 Volt,
high level>2.4 Volt). One reason for this error could be that there is
a bad connection between the CPU, IC101 on the FM CPU board (K11301)
and its socket. The socket should be manufactured by AMP. Sockets from
other manufacturers have caused problems.
* FM CPU BOARD,TMO0: The signal TMO0 is incorrect as the CPU, IC101 is
broken or the driver IC113 is broken.
* UF DRIVER BOARD,TMO0: TMO0 short circuit. If TMO0 becomes correct when
the flow transducer is disconnected then the error is probably caused
by a broken IC2 of the UF driver board K11195.
* CABLINGS: Some cablings are broken or short circuit.
* UF MAGNETISATION COIL: Broken or short circuit.

FCN 4.05 011 SELF CALIBRATION PARAMETERS DIFFER TOO MUCH FROM
THE LAST SELF CALIBRATION [T]
General description of conditions for occuring:
A self calibration was run. It failed as the values of the variables
FRR(FR_UFR$TOLERANCE) and FRR(FR_UFR$OFFSET) had changed too much since
the last self calibration. A new self calibration was run after 5
minutes. It did also fail for the same reason.

Technical description of conditions for occuring:
The following parts of the self calibration executed successfully
without any errors:
VFC channel 1 reference measurement (NO error 4.05 006)
VFC channel 2 reference measurement (NO error 4.05 007)
VFC channel 1 offset measurement (NO error 4.05 008)
VFC channel 2 offset measurement (NO error 4.05 009)
Flow offset calibration (NO error 4.05 015)
Differential flow calibration. The same flow through channel 1 and
channel 2. The following parts succeded:
NO error 4.05 015
NO error 4.05 014

CALIBR DIFF FLOWnew differed more than 1 ml/min from CALIBR DIFF
FLOWold

A new self calibration was done after 5 minutes.

CALIBR DIFF FLOWagain differed more than 1.0 ml/min from CALIBR DIFF
FLOWnew AND CALIBR DIFF FLOWagain differed more than 1.0 ml/min from
CALIBR DIFF FLOWold

EXPLANATIONS:
CALIBR DIFF FLOW is the calibrated differential flow. It is stored
in the variable FRR(FR_UF$RATE) and has the unit l/h. The following
equation is used to calculate it:
CALIBR DIFF FLOW =
0.048 * ( UNCALIBR DIFF FLOW +
FRR(FR_UFR$TOLERANCE) * UNCALIBR CH1 FLOW -
FRR(FR_UFR$OFFSET) )

0.048 is an approximate value that varies for different flow
measuring units.
UNCALIBR DIFF FLOW = SRR(16), has the unit 0.08 ml/min.
UNCALIBR CH1 FLOW = SRR(11), has the unit 0.08 ml/min.
NOTE! VFC channel 2 takes care of flow channel 1.

CALIBR DIFF FLOWold is a CALIBR DIFF FLOW that is calculated using
the values of FRR(FR_UFR$TOLERANCE) and FRR(FR_UFR$OFFSET) from the
last self calibration. (If there is no last self calibration then the
values that are stored in the E2PROM are used, and the difference is
allowed to be 1.5 ml/min instead of 1 ml/min.)

CALIBR DIFF FLOWnew is a CALIBR DIFF FLOW that is calculated using
the values of FRR(FR_UFR$TOLERANCE) and FRR(FR_UFR$OFFSET) from the
main self calibration.

CALIBR DIFF FLOWagain is a CALIBR DIFF FLOW that is calculated using
the values of FRR(FR_UFR$TOLERANCE) and FRR(FR_UFR$OFFSET) from the
self calibration that is done 5 minutes after the main self
calibration.

Some possible explanations why the error has occured:
* FLOW CELL: The flow cell has been coated by dirt.
* FLOW CELL: The flow cell is broken.
* FLOW CELL: The resistance between one of the flow cell carbon tubes and
the Z0VR on the UF preamp board is greater than 2 ohms.
* DIVA: The direct valve is leaking.
* BYVA: The bypass valve is leaking.
* UF PREAMP BOARD: The UF preamp board is broken.

FCN 4.05 012 SELF CALIBRATION PARAMETERS DIFFER TOO MUCH [T]
General description of conditions for occuring:
A self calibration was run. It failed as the value of the variable
FRR(FR_UFR$TOLERANCE) differed too much from the value that was
stored in the EEPROM or estimated at the last performed self
calibration.

Technical description of conditions for occuring:
The following parts of the self calibration executed successfully
without any errors:
VFC channel 1 reference measurement (NO error 4.05 006)
VFC channel 2 reference measurement (NO error 4.05 007)
VFC channel 1 offset measurement (NO error 4.05 008)
VFC channel 2 offset measurement (NO error 4.05 009)
Flow offset calibration (NO error 4.05 015)
Differential flow calibration. The same flow through channel 1 and
channel 2. The following parts succeded:
NO error 4.05 015
NO error 4.05 014

CALIBR DIFF FLOWnew differed more than 7.5 ml/min from CALIBR DIFF
FLOWold

EXPLANATIONS:
CALIBR DIFF FLOW is the calibrated differential flow. It is stored in
the variable FRR(FR_UF$RATE) and has the unit l/h. The following
equation is used to calculate it:
CALIBR DIFF FLOW =
0.048 * ( UNCALIBR DIFF FLOW +
FRR(FR_UFR$TOLERANCE) * UNCALIBR CH1 FLOW -
FRR(FR_UFR$OFFSET) )

0.048 is an approximate value that varies for different flow
measuring units.
UNCALIBR DIFF FLOW = SRR(16), has the unit 0.08 ml/min.
UNCALIBR CH1 FLOW = SRR(11), has the unit 0.08 ml/min.
NOTE! VFC channel 2 takes care of flow channel 1.

CALIBR DIFF FLOWnew is a CALIBR DIFF FLOW that is calculated using
the values of FRR(FR_UFR$TOLERANCE) and FRR(FR_UFR$OFFSET) from the
current self calibration.

CALIBR DIFF FLOWold is a CALIBR DIFF FLOW that is calculated using
the value of FRR(FR_UFR$TOLERANCE) that was stored in the eeprom or
estimated at the previous self calibration and FRR(FR_UFR$OFFSET)
from the current self calibration.

Some possible explanations why the error has occured:
* FLOW CELL: The flow cell has been coated by dirt.
* FLOW CELL: Leakage in flow cell (and positive dialysate pressure)
* FLOW CELL: The flow cell is broken.
* FLOW CELL: The resistance between one of the flow cell carbon tubes and
the Z0VR at the UF preamp board is greater than 2 ohms.
* DIVA: The direct valve is leaking.
* BYVA: The bypass valve is leaking.
* UF PREAMP BOARD: The UF preamp board is broken.

Some hints of what to do if the error occurs:
Run a chemical disinfection.

FCN 4.05 014 TOO LOW SELF CALIBRATION FLOW [T]
General description of conditions for occuring:
The flow measuring unit measured a flow through channel 1 that was less
than 100 ml/min.

Technical description of conditions for occuring:
The following parts of the self calibration have executed successfully
without any errors:
VFC channel 1 reference measurement (NO error 4.05 006)
VFC channel 2 reference measurement (NO error 4.05 007)
VFC channel 1 offset measurement (NO error 4.05 008)
VFC channel 2 offset measurement (NO error 4.05 009)
Flow offset calibration (NO error 4.05 015)
Differential flow calibration. The same flow through channel 1 and
channel 2. The following parts succeded:
NO error 4.05 015

FRR(FR_CH1$RATE) < 100.0 ml/min.
The self calibration was repeated after 5 minutes and the tests above
did not fail.
FRR(FR_CH1$RATE) < 100.0 ml/min.

FRR(FR_CH1$RATE) = SRR(0), has the unit ml/min.

Some possible explanations why the error has occured:
* FLOW OUTPUT PUMP RESTRICTOR: Dirty or wrong restrictor.
* FLOW OUTPUT PUMP PRESSURE TRANSDUCER: Broken or uncalibrated.
* FLOW OUTPUT PUMP: Dirty or broken.
* FLOW INPUT PUMP RESTRICTOR: Dirty or wrong restrictor.
* FLOW INPUT PUMP PRESSURE TRANSDUCER: Broken or uncalibrated.
* FLOW INPUT PUMP: Dirty or broken.
* ZEVA: Leaking.
* FLOW CELL: The flow cell has been coated by dirt.
* FLOW CELL: The flow cell is broken.
* FLOW CELL: The resistance between one of the flow cell carbon tubes and
the Z0VR at the UF preamp board is greater than 2 ohms.
* UF PREAMP BOARD: The UF preamp board is broken.

FCN 4.05 015 UNSTABLE SIGNALS DURING SELF CALIBRATION [T]
General description of conditions for occuring:
The self calibration failed because at least one of the measured flow
signals varied too much. A new self calibration that was done 5 minutes
later did also fail because at least one of the measured flow signals
varied too much.

Technical description of conditions for occuring:
The following conditions occured twice, and there was 5
minutes between the two attempts:
The calibration of the measuring system was successful.
The zero flow signals were measured for 15s.
Variance of the flow signals were calculated.
Flow channel 1 variance SRR(34) > 146.5 OR
Flow channel 2 variance SRR(35) > 146.5
( The measuring of zero flow signals was continued for 15s.
Variance of flow signals were calculated from 30s data.
Flow channel 1 variance SRR(34) > 293.0 OR
Flow channel 2 variance SRR(35) > 293.0 )
OR
( New zero flow signals were measured for 15s.
Variance of flow signals were calculated from 15s data.
Flow channel 1 variance SRR(34) > 146.5 OR
Flow channel 2 variance SRR(35) > 146.5 )
OR
The following conditions occured twice, and there was 5 minutes
between the two attempts:
The calibration of the measuring system was successful.
The calibration of the offset flow was successful.
Wait for 15s.
The differential flow signals were measured for 15s.
Variance of the differential flow signal was calculated.
Differential flow variance SRR(36) > 585.9.
( The measuring of differential flow signals was continued for 15s.
Variance of the differential flow signal was calculated from 30s
data.
Differential flow variance SRR(36) > 1171.9.
OR
( New measurement of differential flow.
Variance of the differential flow signal was calculated from 15s
data.
Differential flow variance SRR(36) > 585.9. )

The same flow went through both the flow channels while the
differential flow was measured.
The unit of the variances is 0.0064*(ml/min)*(ml/min)
Note! VFC channel 2 takes care of flow channel 1!

Some possible explanations why the error has occured:
* Air is flowing through flow channel 1.
* The ultra sonic transcducer in the bubble trap 1 is broken.
* TAVA: The taration valve is leaking.
* DIVA: The direct valve is leaking.
* BYVA: The bypass valve is leaking.
* FLOW CELL: The flow cell is dirty.
* FLOW CELL: The flow cell is broken.
* FLOW OUTPUT PUMP RESTRICTOR: The restrictor is dirty.
* FLOW OUTPUT PUMP: The pump is not working properly.
* The flow system before bubble trap 1 causes an unstable level in bubble
trap 1.
* FLOW OUTPUT PUMP PRESSURE TRANSDUCER: Not working properly.
* FM CPU BOARD: The signal TMO0 is not buffered according to the change
order 10827.

FCN 4.05 016 SELF CALIBRATION TIME OUT [T]
General description of conditions for occuring:
The self calibration executed for a too long time.

Technical description of conditions for occuring:
SELF CALIBRATION TIME > MAX SELF CALIBRATION TIME
MAX SELF CALIBRATION TIME = 15s - 68s.

Some possible explanations why the error has occured:
* Secondary error to the error FCN 4.05 006.
* Secondary error to the error FCN 4.05 007.
* Secondary error to the error FCN 4.05 008.
* Secondary error to the error FCN 4.05 009.
* FM CPU BOARD: The VFC IC36 or some of the components around it are
broken. (Circuit diagram K11302).
* FM CPU BOARD: The VFC IC38 or some of the components around it are
broken.
* FM CPU BOARD: The timer IC94 is broken.

FCN 4.05 017 SELF CALIBRATION TIME OUT [T,S]
Please refer to the description of FCN 4.05 016.

FCN 4.05 018 SELF CALIBRATION TIME OUT [T,S]
Please refer to the description of FCN 4.05 016.

FCN 4.05 019 SELF CALIBRATION TIME OUT [T,S]
Please refer to the description of FCN 4.05 016.

FCN 4.05 020 SELF CALIBRATION TIME OUT [T,S]
Please refer to the description of FCN 4.05 016.

FCN 4.05 021 MEASURED MAGNETISATION CURRENT INCORRECT [T,S]
Please refer to the description of FCN 4.05 010.

FCN 4.05 022 UNSTABLE SIGNAL DURING UF CALIB LINEARITY TEST [S]
General description of conditions for occuring:
The channel 1 flow and the differential flow varied too much during the
linearity test in service mode.

Technical description of conditions for occuring:
The following occured twice during the linearity test in the UF
calibration in service mode:
The calibration of the measuring system was correct.
The linearity test was started and the same flow should flow through
both the UF measuring channels.
The variance of the channel 1 flow and the variance of the differen-
tial flow were calculated at the times stated below while the
linearity test was going on.
CHANNEL 1 FLOW VARIANCE > 293.0 after 30s OR
DIFFERENTIAL FLOW VARIANCE > 293.0 after 30s
AND
CHANNEL 1 FLOW VARIANCE > 439.5 after 45s OR
DIFFERENTIAL FLOW VARIANCE > 439.5 after 45s
AND
CHANNEL 1 FLOW VARIANCE > 585.9 after 60s OR
DIFFERENTIAL FLOW VARIANCE > 585.9 after 60s
AND
CHANNEL 1 FLOW VARIANCE > 732.4 after 75s OR
DIFFERENTIAL FLOW VARIANCE > 732.4 after 75s
AND
CHANNEL 1 FLOW VARIANCE > 878.9 after 90s A N D
DIFFERENTIAL FLOW VARIANCE > 878.9 after 90s

The variances have the unit 0.0064*(ml/min)*(ml/min).
CHANNEL 1 FLOW VARIANCE = SRR(34).
DIFFERENTIAL FLOW VARIANCE = SRR(36).
Note! VFC channel 2 takes care of flow channel 1!

Some possible explanations why the error has occured:
* Air is flowing through flow channel 1.
* The ultra sonic transducer in the bubble trap 1 is broken.
* TAVA: The taration valve is leaking.
* DIVA: The direct valve is leaking.
* BYVA: The bypass valve is leaking.
* FLOW CELL: The flow cell is dirty.
* FLOW CELL: The flow cell is broken.
* FLOW OUTPUT PUMP RESTRICTOR: The restrictor is dirty.
* FLOW OUTPUT PUMP: The pump is not working properly.
* The flow system before bubble trap 1 causes an unstable level in bubble
trap 1.
* FLOW OUTPUT PUMP PRESSURE TRANSDUCER: Not working properly.
* FM CPU BOARD: The signal TMO0 is not buffered according to the change
order 10827.

FCN 4.05 023 UNSTABLE SIGNAL DURING UF CALIB LINEARITY TEST [S]
General description of conditions for occuring:
The channel 1 flow varied too much during the linearity test in the UF
calibration in service mode.

Technical description of conditions for occuring:
The following occured twice during the linearity test in the UF
calibration in service mode:
The calibration of the measuring system was correct.
The linearity test was started and the same flow should flow through
both the UF measuring channels.
The variance of the channel 1 flow and the variance of the differen-
tial flow were calculated at the times stated below while the
linearity test was going on.
CHANNEL 1 FLOW VARIANCE > 293.0 after 30s OR
DIFFERENTIAL FLOW VARIANCE > 293.0 after 30s
AND
CHANNEL 1 FLOW VARIANCE > 439.5 after 45s OR
DIFFERENTIAL FLOW VARIANCE > 439.5 after 45s
AND
CHANNEL 1 FLOW VARIANCE > 585.9 after 60s OR
DIFFERENTIAL FLOW VARIANCE > 585.9 after 60s
AND
CHANNEL 1 FLOW VARIANCE > 732.4 after 75s OR
DIFFERENTIAL FLOW VARIANCE > 732.4 after 75s
AND
CHANNEL 1 FLOW VARIANCE > 878.9 after 90s

The variances have the unit 0.0064*(ml/min)*(ml/min).
CHANNEL 1 FLOW VARIANCE = SRR(34).
DIFFERENTIAL FLOW VARIANCE = SRR(36).
Note! VFC channel 2 takes care of flow channel 1!

Some possible explanations why the error has occured:
* FLOW OUTPUT PUMP RESTRICTOR: The restrictor is dirty.
* FLOW OUTPUT PUMP: The pump is not working properly.
* The flow system before bubble trap 1 causes an unstable level in bubble
trap 1.
* FLOW OUTPUT PUMP PRESSURE TRANSDUCER: Not working properly.
* Air is flowing through flow channel 1.
* The ultra sonic transcducer in the bubble trap 1 is broken.
* ZEVA: The zero setting valve is leaking.
* FM CPU BOARD: The signal TMO0 is not buffered according to the change
order 10827.

FCN 4.05 024 UNSTABLE SIGNAL DURING UF CALIB DIFFERENTIAL FLOW [S]
General description of conditions for occuring:
The differential flow varied too much during the differential flow
calibration in service mode.

Technical description of conditions for occuring:
The following has occured twice during the differential calibration in
the UF calibration in service mode:
The calibration of the measuring system was correct.
The differential flow calibration was started and the same flow
should flow through both the UF measuring channels.
The variance of the differential flow was calculated at the times
stated below while the differential flow calibration was going on.
DIFFERENTIAL FLOW VARIANCE > 293.0 after 30s
AND
DIFFERENTIAL FLOW VARIANCE > 439.5 after 45s
AND
DIFFERENTIAL FLOW VARIANCE > 585.9 after 60s
AND
DIFFERENTIAL FLOW VARIANCE > 732.4 after 75s
AND
DIFFERENTIAL FLOW VARIANCE > 878.9 after 90s

DIFFERENTIAL FLOW VARIANCE = SRR(36).
The variance has the unit 0.0064*(ml/min)*(ml/min).

Some possible explanations why the error has occured:
* Air is flowing through flow channel 1.
* The ultra sonic transcducer in the bubble trap 1 is broken.
* TAVA: The taration valve is leaking.
* DIVA: The direct valve is leaking.
* BYVA: The bypass valve is leaking.
* FLOW CELL: The flow cell is dirty.
* FLOW CELL: The flow cell is broken.
* FLOW OUTPUT PUMP RESTRICTOR: The restrictor is dirty.
* FLOW OUTPUT PUMP: The pump is not working properly.
* The flow system before bubble trap 1 causes an unstable level in bubble
trap 1.
* FLOW OUTPUT PUMP PRESSURE TRANSDUCER: Not working properly.
* FM CPU BOARD: The signal TMO0 is not buffered according to the change
order 10827.

FCN 4.05 025 UNSTABLE SIGNAL DURING UF OFFSET CALIBRATION [S]
General description of conditions for occuring:
The channel 1 flow signal and the channel 2 flow signal varied too much
during the mainflow offset calibration in service mode. There should be
no flow through the measuring cells.

Technical description of conditions for occuring:
The following has occured twice during the mainflow offset calibration
in the UF calibration in service mode:
The calibration of the measuring system was correct.
The mainflow offset calibration was started and no flow should flow
through the UF measuring channels.
The variance of the channel 1 flow and the variance of the channel 2
flow were calculated at the times stated below while the mainflow
offset calibration was going on.
CHANNEL 1 FLOW VARIANCE > 293.0 after 30s OR
CHANNEL 2 FLOW VARIANCE > 293.0 after 30s
AND
CHANNEL 1 FLOW VARIANCE > 439.5 after 45s OR
CHANNEL 2 FLOW VARIANCE > 439.5 after 45s
AND
CHANNEL 1 FLOW VARIANCE > 585.9 after 60s OR
CHANNEL 2 FLOW VARIANCE > 585.9 after 60s
AND
CHANNEL 1 FLOW VARIANCE > 732.4 after 75s OR
CHANNEL 2 FLOW VARIANCE > 732.4 after 75s
AND
CHANNEL 1 FLOW VARIANCE > 878.9 after 90s OR
CHANNEL 2 FLOW VARIANCE > 878.9 after 90s

The variances have the unit 0.0064*(ml/min)*(ml/min).
CHANNEL 1 FLOW VARIANCE = SRR(34).
CHANNEL 2 FLOW VARIANCE = SRR(35)
Note! VFC channel 2 takes care of flow channel 1!

Some possible explanations why the error has occured:
* FLOW CELL: The flow cell is dirty.
* FLOW CELL: The flow cell is broken.
* BYVA: The bypass valve is leaking.
* DIVA: The direct valve is leaking.
* TAVA: The taration valve is leaking.
* FM CPU BOARD: The signal TMO0 is not buffered according to the change
order 10827.

FCN 4.05 026 CHANNEL 1 FLOWS TOO CLOSE DURING LINEARITY TEST [S]
General description of conditions for occuring:
The minimum and maximum channel 1 flows differed to little during the
linearity test in service mode OR
The medium and maximum channel 1 flows differed to little during the
linearity test in service mode.

Technical description of conditions for occuring:
( MINIMUM CHANNEL 1 FLOW > 0.75 * MAXIMUM CHANNEL 1 FLOW OR
MEDIUM CHANNEL 1 FLOW > 0.88 * MAXIMUM CHANNEL 1 FLOW )

CHANNEL 1 FLOW = SRR(11) and has the unit 0.08 ml/min.
Note! VFC channel 2 takes care of flow channel 1!

Some possible explanations why the error has occured:
* FLOWCELL: The channel 1 part of the flow cell is broken.
* UF PREAMP BOARD: The channel 1 part is broken.

FCN 4.05 027 CHANNEL 2 FLOWS TOO CLOSE DURING LINEARITY TEST [S]
Please refer to the description of 4.05 026.
CHANNEL 2 FLOW = SRR(6) and has the unit 0.08 ml/min.
Note! VFC channel 1 takes care of flow channel 2!

FCN 4.05 028 FLOWS TOO CLOSE DURING LINEARITY TEST [S]
General description of conditions for occuring:
The minimum and maximum channel 1 flows differed to little during the
linearity test in service mode OR
The medium and maximum channel 1 flows differed to little during the
linearity test in service mode.
AND
The minimum and maximum channel 2 flows differed to little during the
linearity test in service mode. OR
The medium and maximum channel 2 flows differed to little during the
linearity test in service mode.

Technical description of conditions for occuring:
( MINIMUM CHANNEL 1 FLOW > 0.75 * MAXIMUM CHANNEL 1 FLOW OR
MEDIUM CHANNEL 1 FLOW > 0.88 * MAXIMUM CHANNEL 1 FLOW )
AND
( MINIMUM CHANNEL 2 FLOW > 0.75 * MAXIMUM CHANNEL 2 FLOW OR
MEDIUM CHANNEL 2 FLOW > 0.88 * MAXIMUM CHANNEL 2 FLOW )

CHANNEL 1 FLOW = SRR(11) and has the unit 0.08 ml/min.
CHANNEL 2 FLOW = SRR(6) and has the unit 0.08 ml/min.
Note! VFC channel 2 takes care of flow channel 1!

Some possible explanations why the error has occured:
* FLOW OUTPUT PUMP RESTRICTOR: dirty.
* FLOW OUTPUT PUMP: not working properly.
* FLOW OUTPUT PUMP PRESSURE TRANSDUCER: not working properly.
* FLOW CELL: The resistance between one of the flow cell
carbon tubes and the Z0VR at the UF preamp board is greater than 2
ohms.
* FLOW CELL: The channel 1 part AND the channel 2 part of the flow cell
are broken.

Some hints of what to do if the error occurs:
Check during linearity test if the three different linearity test flow
rates can be observed at the drain. If that is the case, then the flow
cell is out of order. Otherwise the flow generation is not working
properly.

FCN 4.05 029 UF CALIB REF VOLUME OUT OF LIMITS [S]
General description of conditions for occuring:
The reference volume was outside its specified limits during the UF
calibration in service mode.

Technical description of conditions for occuring:
ORI(OI_UF$CAL$REF$VOL) < PI(EPI_UF$CAL$REF$VOL$LL)
OR
ORI(OI_UF$CAL$REF$VOL) > PI(EPI_UF$CAL$REF$VOL$HL)

ORI(OI_UF$CAL$REF$VOL) has the unit 0.1 ml.

Some possible explanations why the error has occured:
* Probably failure in communication of the reference volume value from
opcom.
* FM CPU BOARD: The RAM, IC98 is broken. (drawing K11301)

FCN 4.05 030 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.05 031 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.05 032 SOFTWARE ERROR [T]
Please refer to the description of FCN 1.00 000.

FCN 4.05 033 DIRECT VALVE LEAKAGE TEST FAILED [F]
General description of conditions for occuring:
The leakage flow of the direct valve was more than 1 ml/min.

Technical description of conditions for occuring:
The direct valve and bypass valve were closed.
The flow through channel 1, CH1 FLOWnopress was measured.
The flow input pump tried to suck flow through DIVA and channel 1
by applying a negative pressure at DIVA.
The CH 1 FLOWpress was measured.
The DIVAtestValue = CH1 FLOWpress - CH1 FLOWnopress was calculated.
The DIVAtestValue > +/-1.0 ml/min.
The same test procedure was performed once more.
The DIVAtestValue was < -1.0 ml/min.
CH1 FLOW is stored in SRR(0) and has the unit ml/min.
DIVAtestValue is stored in SRR(45) and has the unit ml/min.

Some possible explanations why the error has occured:
* The direct valve (DIVA) is leaking.
* See "FCN 4.05 034".

FCN 4.05 034 UNSTABLE SIGNALS FOR CHANNEL 1 DURING SELF CHECK [T]

General description of conditions for occuring:
A self check was run (requested by flow supervision). It failed as the
channel 1 flow signal was unstable during the self check.

Technical description of conditions for occuring:
(Treatment mode is uf control and difference between measured uf and
selected uf is less than -100 or bigger than +250 ml/min for more
than 30s. )
OR
(Treatment mode is tmp control and measured uf is less than -100 or
bigger than +250 ml/min for more than 30s. )
No flow through the channels and not in Isolated uf mode.
The calibration of the measuring system was successful.
The zero flow signals were measured for 15s.
Variance of the flow signals were calculated.
Flow channel 1 variance SRR(34) > 293 OR
Flow channel 2 variance SRR(35) > 293
( The measuring of zero flow signals was continued for 15s.
Variance of flow signals were calculated from 30s data.
Flow channel 1 variance SRR(34) > 586.0 )
OR
( New measurement of zero flow signals for 15s.
Variance of flow signals were calculated from 15s data.
Flow channel 1 variance SRR(34) > 293 )

Some possible explanations why the error has occured:
* Connection between electrodes and preamplifier board K14012 broken.
* Ground connection between preamplifier board K14012 and Carbon tubes
K08296 A to high. Should be less than 2 ohm.
* Broken preamplifier board K14012.
* Uf measurement system on FM CPU board broken.
* Flow output pump not working properly.

FCN 4.05 035 UNSTABLE SIGNALS FOR CHANNEL 2 DURING SELF CHECK [T]

General description of conditions for occuring:
A self check was run (requested by flow supervision). It failed as the
channel 2 flow signal was unstable during the self check.


Technical description of conditions for occuring:
(Treatment mode is uf control and difference between measured uf and
selected uf is less than -100 or bigger than +250 ml/min for more
than 30s. )
OR
(Treatment mode is tmp control and measured uf is less than -100 or
bigger than +250 ml/min for more than 30s. )
No flow through the channels and not in Isolated uf mode.
The calibration of the measuring system was successful.
The zero flow signals were measured for 15s.
Variance of the flow signals were calculated.
Flow channel 1 variance SRR(34) > 293 OR
Flow channel 2 variance SRR(35) > 293
( The measuring of zero flow signals was continued for 15s.
Variance of flow signals were calculated from 30s data.
Flow channel 2 variance SRR(34) > 586.0 )
OR
( New measurement of zero flow signals for 15s.
Variance of flow signals were calculated from 15s data.
Flow channel 2 variance SRR(35) > 293 )

Some possible explanations why the error has occured:
See "FCN 4.05 034".

FCN 4.05 036 CHANNEL 1 OFFSET OUT OF LIMIT MEASURED AT SELF CHECK [T]

General description of conditions for occuring:
A self check was run (requested by flow supervision). It failed as the
measured offset for channel 1 was to big.

Technical description of conditions for occuring:
(Treatment mode is uf control and difference between measured uf and
selected uf is less than -100 or bigger than +250 ml/min for more
than 30s. )
OR
(Treatment mode is tmp control and measured uf is less than -100 or
bigger than +250 ml/min for more than 30s. )
No error 4.05 034.
Measured offset of channel 1 bigger than 1000 or less than -1000

Some possible explanations why the error has occured:
See "FCN 4.05 034".

FCN 4.05 037 CHANNEL 2 OFFSET OUT OF LIMIT MEASURED AT SELF CHECK [T]

General description of conditions for occuring:
A self check was run (requested by flow supervision). It failed as the
measured offset for channel 2 was to big.

Technical description of conditions for occuring:
(Treatment mode is uf control and difference between measured uf and
selected uf is less than -100 or bigger than +250 ml/min for more
than 30s. )
OR
(Treatment mode is tmp control and measured uf is less than -100 or
bigger than +250 ml/min for more than 30s. )
No error 4.05 035.
Measured offset of channel 2 bigger than 1000 or less than -1000

Some possible explanations why the error has occured:
See "FCN 4.05 034".

FCN 4.05 038 UNSTABLE DIFF.FLOW SIGNAL DURING SELF CHECK [T]

General description of conditions for occuring:
A self check was run (requested by flow supervision). It failed as the
differential flow signal was unstable during the self check.

Technical description of conditions for occuring:
(Treatment mode is uf control and difference between measured uf and
selected uf is less than -100 or bigger than +250 ml/min for more
than 30s. )
OR
(Treatment mode is tmp control and measured uf is less than -100 or
bigger than +250 ml/min for more than 30s. )
The calibration of the measuring system was successful.
The check of the offset flow was successful.
Wait for 15s.
The differential flow signals were measured for 15s.
The variance of differential flow signal was calculated.
Differential flow variance SRR(36) > 1171.9
( The measuring of differential flow signals was continued for 15s.
Variance of differential flow signal were calculated from 30s data.
Differential flow variance SRR(36) > 2343.8. )
OR
( New differential flow signals were measured 15s.
Variance of differential flow signal was calculated.
Differential flow variance SRR(36) > 585.9. )

The same flow went through both the flow channels while the
differential flow was measured.
The unit of the variances is 0.0064*(ml/min)*(ml/min)

Some possible explanations why the error has occured:
See "FCN 4.05 034".

FCN 4.05 039 TOLLERANCE CHANNEL 2 TO CHANNEL 1 FLOW TO BIG [T]

General description of conditions for occuring:
A self check was run (requested by flow supervision). It failed as the
tollerance between channels differed too much from the values measured
at the last approved self calibration.

Technical description of conditions for occuring:
(Treatment mode is uf control and difference between measured uf and
selected uf is less than -100 or bigger than +250 ml/min for more
than 30s. )
OR
(Treatment mode is tmp control and measured uf is less than -100 or
bigger than +250 ml/min for more than 30s. )
No error 4.05 038.
Tollerance between channels differs more than 7.5 ml/min
from value measured at last approved self calibration.
See 4.05 012 for description of how difference is calculated.

Some possible explanations why the error has occured:
See "FCN 4.05 034".

FCN 4.05 040 UNEXPECTED RESULT AT DIRECT VALVE LEAKAGE TEST [F]
General description of conditions for occuring:
The leakage flow of the direct valve DIVA (measured by channel
1 of the flowmeter) was more than +1 ml/min. This is an unexpected
result as the applied pressure over the valve should result in
a negative flow upon a leaking valve.

Technical description of conditions for occuring:
The direct valve and bypass valve were closed.
The flow through channel 1, CH1 FLOWnopress was measured.
The flow input pump tried to suck flow through DIVA and channel 1
by applying a negative pressure at DIVA.
The CH 1 FLOWpress was measured.
The DIVAtestValue = CH1 FLOWpress - CH1 FLOWnopress was calculated.
The DIVAtestValue > +/-1.0 ml/min.
The same test procedure was performed once more.
The DIVAtestValue was once more > +1.0 ml/min.
CH1 FLOW is stored in SRR(0) and has the unit ml/min.
DIVAtestValue is stored in SRR(45) and has the unit ml/min.

Some possible explanations why the error has occured:
* The bypass valve (BYVA) is leaking.
* See "FCN 4.05 034".

FCN 4.05 041 TARATION VALVE LEAKAGE TEST FAILED [F]
General description of conditions for occuring:
The leakage flow of the direct tava was more than 1 ml/min.

Technical description of conditions for occuring:
The tava valve and bypass valve were closed.
The zeva valve was opened.
The flow through channel 2, CH2 FLOWnopress was measured.
The flow input pump tried to force flow through TAVA and channel 2
by applying a positive pressure at TAVA.
The CH 2 FLOWpress was measured.
The TAVAtestValue = CH2 FLOWpress - CH2 FLOWnopress was calculated.
The TAVAtestValue > +/-1.0 ml/min.
The same test procedure was performed once more.
The TAVAtestValue was once again < -1.0 ml/min.
CH2 FLOW is stored in SRR(1) and has the unit ml/min.
TAVAtestValue is stored in SRR(46) and has the unit ml/min.

Some possible explanations why the error has occured:
* The bypass valve (BYVA) is leaking.
* The taration valve (TAVA) is leaking.
* See "FCN 4.05 034".

FCN 4.05 042 UNEXPECTED RESULT FROM TARATION VALVE LEAKAGE TEST [F]
General description of conditions for occuring:
The leakage flow of the taration valve TAVA (measured by channel
2 of the flowmeter) was more than +1 ml/min. This is an unexpected
result as the applied pressure over the valve should result in
a negative flow upon a leaking valve.

Technical description of conditions for occuring:
The tava valve and bypass valve were closed.
The zeva valve was opened.
The flow through channel 2, CH2 FLOWnopress was measured.
The flow input pump tried to force flow through TAVA and channel 2
by applying a positive pressure at TAVA.
The CH 2 FLOWpress was measured.
The TAVAtestValue = CH2 FLOWpress - CH2 FLOWnopress was calculated.
The TAVAtestValue > +/-1.0 ml/min.
The same test procedure was performed once more.
The TAVAtestValue was < -1.0 ml/min.
CH2 FLOW is stored in SRR(1) and has the unit ml/min.
TAVAtestValue is stored in SRR(46) and has the unit ml/min.

Some possible explanations why the error has occured:
* See "FCN 4.05 034".

FCN 4.05 043 UNSTABLE SIGNALS DURING DIRECT AND TARATION [F]
VALVE TEST.
General description of conditions for occuring:
The offset calibration failed because at least one of the measured
flow signals varied too much. A new offset calibration that was done
did also fail because at least one of the measured flow signals
varied too much.

Technical description of conditions for occuring:
The following happened twice:
The calibration of the measuring system was successful.
The zero flow signals were measured for 15s.
Variance of the flow signals were calculated.
Flow channel 1 variance SRR(34) > 146.5 OR
Flow channel 2 variance SRR(35) > 146.5
( The measuring of zero flow signals was continued for 15s.
Variance of flow signals were calculated from 30s data.
Flow channel 1 variance SRR(34) > 293.0 OR
Flow channel 2 variance SRR(35) > 293.0 )
OR
( New zero flow signals were measured for 15s.
Variance of flow signals were calculated from 15s data.
Flow channel 1 variance SRR(34) > 146.5 OR
Flow channel 2 variance SRR(35) > 146.5 )

Some possible explanations why the error has occured:
* DIVA or TAVA is leaking (causing unstable flow in channel 1 (DIVA)
or channel 2 (TAVA)).
* Air in channel 1 or 2.
* FLOW CELL: The flow cell is dirty.
* FLOW CELL: The flow cell is broken.
* FM CPU BOARD: The signal TMO0 is not buffered according to the change
order 10827.

FCN 4.05 044 TOO LONG TIME SINCE LAST APPROVED TARATION. [T]

General description of conditions for occuring:

The flow meter has failed to finish and approve a taration
within 6 attempts (?30 minutes).

Technical description of conditions for occuring:

The following happened more than 6 times:

The taration timer (SRI-74) was incremented upto 1800
and a taration was requested. The counter holding the
number of attempts was incremented. When the taration was
started the taration timer was reset to 1500 (30 minutes
minus 5 minutes). The taration was interrupted or taration
was not approved. Taration was interrupted if at least one
of flags FRL(F_COND$ACH), FRL(F_TEMP$ACH), FRL(F_MAIN$FL$ACH),
FRL(F_TAR$PRES$LIM$INH) (= Dialysate pressure SRI-4 or High
Pressure Guard Pressure SRI-6 was out of pressure range low
SRI-44 or pressure range high SRI-43 limits) was false or if
PH installed at least one of FRL(F_PH$AL) or FRL(F_PH$AH) was
true. Treatment continued and the taration timer was once more
reset to 1500.

Some possible explanations why the error has occured:
* Unstable conductivity (see description at the last
part of this document).
* Unstable dialysate pressure control.
* Unstable PH (if PH installed).
* Unstable mainflow control.
* Unstable temperature control.

FCN 4.05 045 UNSTABLE SIGNALS DURING THE DIRECT AND TARATION [F]
VALVE TEST.
General description of conditions for occuring:
The offset calibration failed twice because the measured differential
flow signal varied too much.

Technical description of conditions for occuring:
The following happened twice:
The calibration of the measuring system was successful.
The differential flow signal was measured during 15s.
The variance of the differential flow signal was calculated.
The differential flow variance > 585.9
( The measuring of the differential flow signal was continued for 15s.
The variance of the signal was calculated from 30s data.
The differential flow variance > 1171.9 )
OR
( New differential flow signal was measured during 15s.
Variance of the signal was calculated from 15s data.
The differential flow variance > 585.9

Some possible explanations why the error has occured:
* DIVA or TAVA is leaking.
* Air in channel 1 or 2.
* FLOW CELL: The flow cell is dirty.
* FLOW CELL: The flow cell is broken.
* FM CPU BOARD: The signal TMO0 is not buffered according to the change
order 10827.

FCN 4.05 046 UNEXPECTED RESULT AT DIVA/TAVA LEAKAGE TEST (-300 mmHg) [F]
General description of conditions for occuring:
The leakage flow of DIVA and/or TAVA were less than -1 ml/min.
This is an unexpected result as the applied pressure over
the valves should result in a positive flow leakage.

Technical description of conditions for occuring:
The direct valve and the taration valve were closed.
The flow input pump tried to suck flow through the valves
by applying a negative pressure at the valves.
The differential flow (DIFF FLOW) was measured.
矰IFF FLOW?> +/-1.0 ml/min.
The same test procedure was performed once more.
The DIFF FLOW was < -1.0 ml/min.
The DIFF FLOW is stored in FRR(FR_DIVA$TEST$VAL) (SRR(45)) and
has the unit ml/min.

Some possible explanations why the error has occured:
* See "FCN 4.05 034".

FCN 4.05 047 DIVA/TAVA LEAKAGE TEST FAILED (-300 mmHg) [F]
General description of conditions for occuring:
The leakage flow of the direct valve and/or the taration valve
were more than 1 ml/min.

Technical description of conditions for occuring:
The direct valve and the taration valve were closed.
The differential flow was measured.
The flow input pump tried to suck flow through DIVA and TAVA
by applying a negative pressure.
The differential flow (DIFF FLOW) was measured.
矰IFF FLOW?> +/-1.0 ml/min.
The same test procedure was performed once more.
The DIFF FLOW was > +1.0 ml/min.
The DIFF FLOW is stored in FRR(FR_DIVA$TEST$VAL) (SRR(45)) and
has the unit ml/min.

Some possible explanations why the error has occured:
* Possible leakage through the direct valve (DIVA) and/or the taration
valve (TAVA). Test the valves by applying a pressure with a syringe.
* See "FCN 4.05 034".

FCN 4.05 048 DIVA/TAVA LEAKAGE TEST FAILED (+300mmHg) [F]
General description of conditions for occuring:
The leakage flow of the direct valve and/or taration valve were
more than 1 ml/min.

Technical description of conditions for occuring:
The direct valve and tava valve were closed.
The flow input pump tried to force flow through DIVA and TAVA
by applying a positive pressure.
The differential flow (DIFF FLOW) was measured.
矰IFF FLOW?> +/-1.0 ml/min.
The same test procedure was performed once more.
The DIFF FLOW was < -1.0 ml/min.
The DIFF FLOW is stored in FRR(FR_TAVA$TEST$VAL) (SRR(46)) and
has the unit ml/min.

Some possible explanations why the error has occured:
* Possible leakage through the direct valve (DIVA) and/or the taration
valve (TAVA). Test the valves by applying a pressure with a syringe.
* See "FCN 4.05 034".

FCN 4.05 049 UNEXPECTED RESULT FROM DIVA/TAVA LEAKAGE TEST (+300 mmHg) [F]
General description of conditions for occuring:
The leakage flow of the taration valve TAVA and/or the direct valve
was more than +1 ml/min. This is an unexpected
result as the applied pressure over the valves should result in
a negative flow upon a leaking valve.

Technical description of conditions for occuring:
DIVA and TAVA were closed.
The flow input pump tried to force flow through DIVA and TAVA
by applying a positive pressure.
The differential flow (DIFF FLOW) was measured.
矰IFF FLOW?> +/-1.0 ml/min.
The same test procedure was performed once more.
The DIFF FLOW was > +1.0 ml/min.
The DIFF FLOW is stored in FRR(FR_TAVA$TEST$VAL) (SRR(46)) and
has the unit ml/min.

Some possible explanations why the error has occured:
* See "FCN 4.05 034".

High pressure guard evaluation function. (CPU D).

FCN 4.06 000 = Case error. The program is not working properly.

Valve control function. (CPU D).

FCN 4.07 000 = Case error. The program is not working properly.
Non allowed combination of valves is selected.

Water inlet function. (CPU D).

FCN 4.08 000 = Case error. The program is not working properly.
FCN 4.08 001 = Heating vessel level-detector indicates both low
and high level. Check and/or replace the level
detector.
This error will show up if the level-detector is
disconnected.

Level measuring function. (CPU D).

FCN 4.09 000 = Case error. The program is not working properly.
FCN 4.09 001 = Timer 4 (STC1) intiation error.
FCN 4.09 002 = Timer 5 (STC1) intiation error.

Bypass control function. (CPU D).

FCN 4.10 000 = Case error. The program is not working properly.

E2prom control function. (CPU D).

FCN 4.11 000 = Case error. The program is not working properly.
FCN 4.11 xyz = x - I2C bus, y - logical address,
(see I2C list at end)
z - error type
1 - acknowledge error (no response)
2 - wrong byte addr. or byte count
3 - read CRC error
4 - type error
5 - position error
6 - offset limit error
7 - coefficient limit error
8 - E2PROM is reference type
9 - wrong bus number
A - read verify error
B - internal table error
C - read error: main board (corrected by next preset)
F - E2PROM is empty
FCN 4.11 F0z = error reading "online installed flag" from
main board CPU D eeprom (z = error above)
FCN 4.11 F3z = error reading "Top prim inst flag" from
main board CPU D eeprom (z = error above)
FCN 4.11 F4z = Removed
FCN 4.11 F5z = error reading "pH available flag" from
main board CPU D eeprom (z = error above)
FCN 4.11 F6z = error reading "BiCart available flag" from
main board CPU D eeprom (z = error above)
FCN 4.11 FBz = error reading "Central Conc. installed flag" from
main board CPU D eeprom (z = error above)
FCN 4.11 FCz = error reading "DuoCart hardware installed flag" from
main board CPU D eeprom (z = error above)

Real time compare function. (CPU D).

FCN 4.12 000 = Case error. The program is not working properly.

Cycling logic function. (CPU D).

FCN 4.13 000 = Case error. The program is not working properly.
FCN 4.13 001 = Case error. The program is not working properly.
Main cycle counter out of range.

Stirring motor function. (CPU D).

FCN 4.14 000 = Case error. The program is not working properly.

Disinfection time estimate. (CPU D).

FCN 4.15 000 = Case error. The program is not working properly.

E2prom control function. (CPU A).

FCN 4.16 000 = Case error. The program is not working properly.
FCN 4.16 xyz = x - I2C bus, y - logical address,
(see I2C list at end)
z - error type
1 - acknowledge error (no response)
2 - wrong byte addr. or byte count
3 - read CRC error
4 - type error
5 - position error
6 - offset limit error
7 - coefficient limit error
8 - E2PROM is reference type
9 - wrong bus number
A - read verify error
B - internal table error

Service strap monitoring function. (CPU A).

FCN 4.17 000 = Case error. The program is not working properly.

Blood dialyzer pressure. (CPU A).

FCN 4.18 000 = Case error. The program is not working properly.

Uf rate filter function. (CPU D).

FCN 4.19 000 = Case error. The program is not working properly.

Select chemical disinfection fluid concentration function. (CPU D).

FCN 4.20 000 = Case error. The program is not working properly.
FCN 4.20 001 = Selected chemical desinfectant error, unknown
disinfectant.
The selcted disfectant can not work be used in this
fluid monitor.
FCN 4.20 002 = Selected heat desinfection error, unknown program.
The selcted disfection program can not work be used
in this fluid monitor.
FCN 4.20 003 = Selected rinse program error, unknown rinse program.
The selcted rinse program can not work be used in this
fluid monitor.

FCN 4.21, VALVES AND MOTOR CURRENT (CPU D)
Purpose:
* Checks that the valve currents are within certain limits.
* Checks that the fan motor current, degassing motor current and stirring
motor current are within certain limits.

FCN 4.21 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCM 4.21 011 VALVES REFERENCE CURRENT TOO HIGH WHILE VALVES ARE OFF.
The error code has been removed.

FCN 4.21 021 INVA CURRENT TOO HIGH WHILE SAFE BUS WAS ALARMING. [F]
General description of conditions for occuring:
The current through the inlet valve was too high while the safe bus was
set in alarm mode. The valve should be disconnected from the 24V
supply.

Technical description of conditions for occuring:
The safe bus was set in alarm mode. There should not flow current
through it. The relay K1 on the FM CPU board (K11306) should be
deactivated, and the supply voltage MC24 should be 0V. An attempt to
open the inlet valve was made. The valve should not open since it had
no supply voltage. The measure current is not allowed to increase with
more than 50 mA for 4 sec.
(FRI(FI_VALVE$CURR) - VALVE REFERENCE CURRENT) > 50mA for 4s.

Some possible explanations why the error has occured:
* Current was flowing through the safebus on the FM CPU board when it
should not. One reason for this could be that the relay K1 on the FM
CPU board is broken. (Circuit diagram K11306)
* Bad AD converter.

Some hints of what to do if the error occurs:
Check the safe bus and the relay K1 on the FM CPU board.

FCN 4.21 031 INVA CURRENT TOO LOW WHILE SAFE BUS WAS NOT ALARMING. [F]
General description of conditions for occuring:
The current through the inlet valve was too low while the safe bus was
NOT set in alarm mode. The valve should be connected to the 24V supply.

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 FM CPU board (K11306) should be activated, and the
supply voltage MC24 should be 24V.
An attempt to open the inlet valve was made.
(FRI(FI_VALVE$CURR) - VALVE REFERENCE CURRENT) < 200mA for 4s.

Some possible explanations why the error has occured:
* Not connected valve.
* Broken valve.
* Current does not flow through the safe bus even if it should. One
reason for this could be that the relay K1 on the FM CPU board is
broken. (Circuit diagram K11306)
* Broken transistors. Q1, Q2 Drawing K11303
* Bad AD converter.

FCN 4.21 032 INVA CURRENT TOO HIGH WHILE SAFE BUS WAS NOT ALARMING. [F]
General description of conditions for occuring:
The current through the inlet valve was too high while the safe bus was
NOT set in alarm mode. The valve should be connected to the 24V supply.

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 FM CPU board (K11306) should be activated, and the
supply voltage MC24 should be 24V. An attempt to open the inlet valve
was made. The measured current increased with more than 450 mA when the
valve was activated.
(FRI(FI_VALVE$CURR) - VALVE REFERENCE CURRENT) > 450mA for 4s.

Some possible explanations why the error has occured:
* Short circuit or bad valve.
* Bad AD converter.

FCN 4.21 041 FLVA CURRENT WAS TOO LOW. [F]
General description of conditions for occuring:
The FLVA current was too low when just that valve was tested.

Technical description of conditions for occuring:
An attempt to open FLVA was made. the measured current increased with
less than 200 mA and stayed so for 4 sec.
(FRI(FI_VALVE$CURR) - VALVE REFERENCE CURRENT) < 200mA for 4s.

Some possible explanations why the error has occured:
* Not connected valve.
* Broken valve.
* IC4, IC6 or IC10 on the FM CPU board is broken. (K11303)
* Bad AD converter.

FCN 4.21 042 FLVA CURRENT WAS TOO HIGH. [F]
General description of conditions for occuring:
The FLVA current was too high when just that valve was tested.

Technical description of conditions for occuring:
An attempt to open FLVA was made. The measure current increased with
more than 450 mA and stayed so for more than 4 sec.
(FRI(FI_VALVE$CURR) - VALVE REFERENCE CURRENT) > 450mA for 4s.

Some possible explanations why the error has occured:
* Short circuit or bad valve.
* Bad AD converter.

FCN 4.21 051 BYVA CURRENT WAS TOO LOW. [F]
Please refer to the description of FCN 4.21 041.

FCN 4.21 052 BYVA CURRENT WAS TOO HIGH. [F]
Please refer to the description of FCN 4.21 042.

FCN 4.21 061 EVVA CURRENT WAS TOO LOW. [F]
Please refer to the description of FCN 4.21 041.

FCN 4.21 062 EVVA CURRENT WAS TOO HIGH. [F]
Please refer to the description of FCN 4.21 042.

FCN 4.21 071 EMVA CURRENT WAS TOO LOW. [F]
Please refer to the description of FCN 4.21 041.

FCN 4.21 072 EMVA CURRENT WAS TOO HIGH. [F]
Please refer to the description of FCN 4.21 042.

FCN 4.21 081 RFVA CURRENT WAS TOO LOW. [F]
Please refer to the description of FCN 4.21 041.

FCN 4.21 082 RFVA CURRENT WAS TOO HIGH. [F]
Please refer to the description of FCN 4.21 042.

FCN 4.21 091 TAVA CURRENT WAS TOO LOW. [F]
Please refer to the description of FCN 4.21 041.

FCN 4.21 092 TAVA CURRENT WAS TOO HIGH. [F]
Please refer to the description of FCN 4.21 042.

FCN 4.21 101 PBVA CURRENT WAS TOO LOW. [F]
Please refer to the description of FCN 4.21 041.

FCN 4.21 102 PBVA CURRENT WAS TOO HIGH. [F]
Please refer to the description of FCN 4.21 042.

FCN 4.21 111 FOVA CURRENT WAS TOO LOW. [F]
Please refer to the description of FCN 4.21 041.

FCN 4.21 112 FOVA CURRENT WAS TOO HIGH. [F]
Please refer to the description of FCN 4.21 042.

FCN 4.21 121 ZEVA CURRENT WAS TOO LOW. [F]
Please refer to the description of FCN 4.21 041.

FCN 4.21 122 ZEVA CURRENT WAS TOO HIGH. [F]
Please refer to the description of FCN 4.21 042.

FCN 4.21 131 DRVA CURRENT WAS TOO LOW. [F]
Please refer to the description of FCN 4.21 041.

FCN 4.21 132 DRVA CURRENT WAS TOO HIGH. [F]
Please refer to the description of FCN 4.21 042.

FCN 4.21 141 FAN MOTOR CURRENT TOO LOW. [F]
General description of conditions for occuring:
The fan motor current was too low when just that motor was tested.

Technical description of conditions for occuring:
An attempt to start the fan motor was made. The measured current
increased less than 50 mA within 4 sec.
(FRI(FI_MOTOR$CURR) - MOTOR REFERENCE CURRENT) < 50mA for 4s.

Some possible explanations why the error has occured:
* Not connected fan motor.
* Broken fan motor.
* Bad AD converter.
* Broken fan motor electronics.

FCN 4.21 142 FAN MOTOR CURRENT TOO HIGH. [F]
General description of conditions for occuring:
The fan motor current was too high when just that motor was tested.

Technical description of conditions for occuring:
An attempt to start the fan motor was made. The measured current
increased with more than 300 mA and stayed so for 4 sec.
(FRI(FI_MOTOR$CURR) - MOTOR REFERENCE CURRENT) > 300mA for 4s.

Some possible explanations why the error has occured:
* Short circuit or bad fan motor.
* Bad AD converter.

FCN 4.21 151 STIRRING MOTOR CURRENT TOO LOW. [F]
General description of conditions for occuring:
The stirring motor current was too low when just that motor was tested.

Technical description of conditions for occuring:
An attempt to start the stirring motor was made. The measured current
increased with less than 15 mA within 4 sec.
(FRI(FI_MOTOR$CURR) - MOTOR REFERENCE CURRENT) < 15mA for 4s.

Some possible explanations why the error has occured:
* Not connected stirring motor.
* The stirrer rotates in the air, not in fluid.
* Broken stirring motor.
* The polarity of the contact for the stirring motor was reversed when
the contact was mounted.
* Broken stirring motor electronics.
* Bad AD converter.

FCN 4.21 152 STIRRING MOTOR CURRENT TOO HIGH. [F]
General description of conditions for occuring:
The stirring motor current was too high when just that motor was tested

Technical description of conditions for occuring:
An attempt to start the stirring motor was made. The measured current
increased with more than 100 mA and stayed so for 4s.
(FRI(FI_MOTOR$CURR) - MOTOR REFERENCE CURRENT) > 100mA for 4s.

Some possible explanations why the error has occured:
* Short circuit or bad stirring motor.
* Bad AD converter.

FCN 4.21 161 DEGASSING MOTOR CURRENT TOO LOW. [F]
General description of conditions for occuring:
The degassing motor current was too low when just that motor was tested

Technical description of conditions for occuring:
An attempt to start the degassing motor was made. The measured current
increased with less than 100 mA within 4s.
(FRI(FI_MOTOR$CURR) - MOTOR REFERENCE CURRENT) < 100mA for 4s.

Some possible explanations why the error has occured:
* Not connected degassing motor.
* Broken degassing motor.
* Decoupled pump.
* Loose magnet coupling. (the screw has to be fastened)
* Broken degassing motor electronics.
* Bad AD converter.

FCN 4.21 162 DEGASSING MOTOR CURRENT TOO HIGH. [F]
General description of conditions for occuring:
The degassing motor current was too high when just that motor was
tested.

Technical description of conditions for occuring:
An attempt to start the degassing motor was made. The measured current
increased with more than 500 mA and stayed so for 4s.
(FRI(FI_MOTOR$CURR) - MOTOR REFERENCE CURRENT) > 500mA for 4s.

Some possible explanations why the error has occured:
* Short circuit or bad degassing motor.
* The degassing motor is occluded by calcium precipitations.
(Run citric acid cleaning.)
* Bad AD converter.

FCN 4.21 171 DIVA CURRENT TOO HIGH WHEN CPU A ALARMS AT THE DIVA-BUS. [F]
General description of conditions for occuring:
The DIVA current was too high when CPU A tried to turn off the current
in the DIVA bus.

Technical description of conditions for occuring:
An attempt to open the direct valve was made when CPU A kept the DIVA
bus closed. The measured current increased with more than 50 mA for 4s.
(FRI(FI_VALVE$CURR) - VALVE REFERENCE CURRENT) > 50mA for 4s.

Some possible explanations why the error has occured:
* The Diva bus is not working properly.

Some hints of what to do if the error occurs:
Check Q1, Q2, Q3 on the FM CPU board. (K11303)
Check IC76 and IC82 on the FM CPU board. (K11305)
Check Q7 on the BM CPU board. (K11352)

FCN 4.21 181 DIVA CURRENT TOO HIGH WHEN CPU B ALARMS AT THE DIVA-BUS. [F]
Please refer to the description of FCN 4.21 171.

FCN 4.21 191 DIVA CURRENT TOO HIGH WHEN CPU C ALARMS AT THE DIVA-BUS. [F]
Please refer to the description of FCN 4.21 171.

FCN 4.21 201 DIVA CURRENT WAS TOO LOW. [F]
Please refer to the description of FCN 4.21 041.

Some hints of what to do if the error occurs:
Check Q1, Q2, Q3 on the FM CPU board. (K11303)
Check Q7 on the BM CPU board. (K11352)

FCN 4.21 202 DIVA CURRENT WAS TOO HIGH. [F]
Please refer to the description of FCN 4.21 042.

FCN 4.22, EVALUATE FM TRANSDUCERS (CPU D)
Purpose:
* Checks that the measured high pressure guard pressure, dialysis
pressure and safety guard pressure does not differ too much from each
other.

FCN 4.22 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.22 011 FRI(FI_E$HPG) DIFFER TOO MUCH AT 0 MMHG [F]
General description of conditions for occuring:
The high pressure guard pressure and the dialysis pressure differs
more than 25 mmHg
AND
The high pressure guard pressure and the safety guard pressure differs
more than 25 mmHg.

Technical description of conditions for occuring:
The dialysis pressure is regulated at 0 mmHg. FRI(FI_E$HPG),
FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable for 5 seconds.
( ( FRI(FI_E$HPG)-150 ) - FRI(FI_E$PD) < -250 ) OR
( ( FRI(FI_E$HPG)-150 ) - FRI(FI_E$PD) > 250 )
AND
( ( FRI(FI_E$HPG)-150 ) - PRI(PI_SAG$PR) < -250 ) OR
( ( FRI(FI_E$HPG)-150 ) - PRI(PI_SAG$PR) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The high pressure guard transducer is uncalibrated.
* The high pressure guard transducer or its electronics is broken.

FCN 4.22 012 FRI(FI_E$PD) DIFFER TOO MUCH AT 0 MMHG [F]
General description of conditions for occuring:
The dialysis pressure and the high pressure guard pressure differs
more than 25 mmHg
AND
The dialysis pressure and the safety guard pressure differs more than
25 mmHg.

Technical description of conditions for occuring:
The dialysis pressure is regulated at 0 mmHg. FRI(FI_E$HPG),
FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable for 5 seconds.
( FRI(FI_E$PD) - (FRI(FI_E$HPG)-150) < -250 ) OR
( FRI(FI_E$PD) - (FRI(FI_E$HPG)-150) > 250 )
AND
( FRI(FI_E$PD) - PRI(PI_SAG$PR) < -250 ) OR
( FRI(FI_E$PD) - PRI(PI_SAG$PR) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The dialysis pressure transducer is uncalibrated.
* The dialysis pressure transducer or its electronics is broken.

FCN 4.22 013 FRI(FI_E$HPG) DIFFER TOO MUCH FROM FRI(FI_E$PD) AT 0 MMHG [F]
General description of conditions for occuring:
The high pressure guard pressure and the dialysis pressure differs
more than 25 mmHg.

Technical description of conditions for occuring:
The dialysis pressure is regulated at 0 mmHg. FRI(FI_E$HPG),
FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable for 5 seconds.
( ( FRI(FI_E$HPG)-150 ) - FRI(FI_E$PD) < -250 ) OR
( ( FRI(FI_E$HPG)-150 ) - FRI(FI_E$PD) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The high pressure guard transducer is uncalibrated.
* The high pressure guard transducer or its electronics is broken.
* The dialysis pressure transducer is uncalibrated.
* The dialysis pressure transducer or its electronics is broken.

FCN 4.22 014 PRI(PI_SAG$PR) DIFFER TOO MUCH AT 0 MMHG [F]
General description of conditions for occuring:
The safety guard pressure and the high pressure guard pressure differs
more than 25 mmHg
AND
The safety guard pressure and the dialysis pressure differs more than
25 mmHg.

Technical description of conditions for occuring:
The dialysis pressure is regulated at 0 mmHg. FRI(FI_E$HPG),
FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable for 5 seconds.
( PRI(PI_SAG$PR) - ( FRI(FI_E$HPG)-150 ) < -250 ) OR
( PRI(PI_SAG$PR) - ( FRI(FI_E$HPG)-150 ) > 250 )
AND
( PRI(PI_SAG$PR) - FRI(FI_E$PD) < -250 ) OR
( PRI(PI_SAG$PR) - FRI(FI_E$PD) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The safety guard pressure transducer is uncalibrated.
* The safety guard pressure transducer or its electronics is broken.

FCN 4.22 015 FRI(FI_E$HPG) DIFFER TOO MUCH FROM PRI(PI_SAG$PR)
AT 0 MMHG [F]
General description of conditions for occuring:
The high pressure guard pressure and the safety guard pressure differs
more than 25 mmHg.

Technical description of conditions for occuring:
The dialysis pressure is regulated at 0 mmHg.
FRI(FI_E$HPG), FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable for
5 seconds.
( ( FRI(FI_E$HPG)-150 ) - PRI(PI_SAG$PR) < -250 ) OR
( ( FRI(FI_E$HPG)-150 ) - PRI(PI_SAG$PR) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The high pressure guard transducer is uncalibrated.
* The high pressure guard transducer or its electronics is broken.
* The safety guard pressure transducer is uncalibrated.
* The safety guard pressure transducer or its electronics is broken.

FCN 4.22 016 FRI(FI_E$PD) DIFFER TOO MUCH FROM PRI(PI_SAG$PR) AT 0 MMHG [F]
General description of conditions for occuring:
The dialysis pressure and the safety guard pressure differs more than
25 mmHg.

Technical description of conditions for occuring:
The dialysis pressure is regulated at 0 mmHg. FRI(FI_E$HPG),
FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable for 5 seconds.
( FRI(FI_E$PD) - PRI(PI_SAG$PR) < -250 ) OR
( FRI(FI_E$PD) - PRI(PI_SAG$PR) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The dialysis pressure transducer is uncalibrated.
* The dialysis pressure transducer or its electronics is broken.
* The safety guard pressure transducer is uncalibrated.
* The safety guard pressure transducer or its electronics is broken.

FCN 4.22 017 FLUID PRESSURES DIFFER TOO MUCH AT 0 MMHG [F]
General description of conditions for occuring:
The high pressure guard pressure and the dialysis pressure differs
more than 25 mmHg
AND
The high pressure guard pressure and the safety guard pressure differs
more than 25 mmHg.
AND
The dialysis pressure and the safety guard pressure differs more than
25 mmHg.

Technical description of conditions for occuring:
The dialysis pressure is regulated at 0 mmHg. FRI(FI_E$HPG),
FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable for 5 seconds.
( ( FRI(FI_E$HPG)-150 ) - FRI(FI_E$PD) < -250 ) OR
( ( FRI(FI_E$HPG)-150 ) - FRI(FI_E$PD) > 250 )
AND
( ( FRI(FI_E$HPG)-150 ) - PRI(PI_SAG$PR) < -250 ) OR
( ( FRI(FI_E$HPG)-150 ) - PRI(PI_SAG$PR) > 250 )
AND
( FRI(FI_E$PD) - PRI(PI_SAG$PR) < -250 ) OR
( FRI(FI_E$PD) - PRI(PI_SAG$PR) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The high pressure guard transducer is uncalibrated.
* The high pressure guard transducer or its electronics is broken.
* The dialysis pressure transducer is uncalibrated.
* The dialysis pressure transducer or its electronics is broken.
* The safety guard pressure transducer is uncalibrated.
* The safety guard pressure transducer or its electronics is broken.

FCN 4.22 018 UNSTABLE FLUID PRESSURES AT 0 MMHG [F]
General description of conditions for occuring:
It has for 1 minute not been possible to create a dialysis pressure of
0 mmHg or at least one of the dialysis pressure, high pressure guard
pressure, and safety guard pressure have not been stable for 1 minute.

Technical description of conditions for occuring:
All the conditions below have not been true within 1 minute:
* -50 <= FI_E$PD <= 50
* The change of FRI(FI_E$HPG) during 1s is less than 100
* The change of FRI(FI_E$PD) during 1s is less than 100
* The change of PRI(PI_SAG$PR) during 1s is less than 100
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The dialysis pressure transducer is uncalibrated.
* The high pressure guard transducer or its electronics is broken.
* The dialysis pressure transducer or its electronics is broken.
* The safety guard pressure transducer or its electronics is broken.
* The flow output pump is broken.
* The flow input pump is broken.

FCN 4.22 021 FRI(FI_E$HPG) DIFFER TOO MUCH AT -100 MMHG [F]
Please refer to the description of FCN 4.22 011

FCN 4.22 022 FRI(FI_E$PD) DIFFER TOO MUCH AT -100 MMHG [F]
Please refer to the description of FCN 4.22 012

FCN 4.22 023 FRI(FI_E$HPG) DIFFER TOO MUCH FROM FRI(FI_E$PD) AT -100 MMHG
[F]
Please refer to the description of FCN 4.22 013

FCN 4.22 024 PRI(PI_SAG$PR) DIFFER TOO MUCH AT -100 MMHG [F]
Please refer to the description of FCN 4.22 014

FCN 4.22 025 FRI(FI_E$HPG) DIFFER TOO MUCH FROM PRI(PI_SAG$PR) AT
-100 MMHG [F]
Please refer to the description of FCN 4.22 015

FCN 4.22 026 FRI(FI_E$PD) DIFFER TOO MUCH FROM PRI(PI_SAG$PR) AT -100 MMHG
[F]
Please refer to the description of FCN 4.22 016

FCN 4.22 027 FLUID PRESSURES DIFFER TOO MUCH AT -100 MMHG [F]
Please refer to the description of FCN 4.22 017

FCN 4.22 028 UNSTABLE FLUID PRESSURES AT -100 MMHG [F]
Please refer to the description of FCN 4.22 018

FCN 4.22 031 FRI(FI_E$HPG) DIFFER TOO MUCH AT 100 MMHG [F]
Please refer to the description of FCN 4.22 011

FCN 4.22 032 FRI(FI_E$PD) DIFFER TOO MUCH AT 100 MMHG [F]
Please refer to the description of FCN 4.22 012

FCN 4.22 033 FRI(FI_E$HPG) DIFFER TOO MUCH FROM FRI(FI_E$PD) AT 100 MMHG
[F]
Please refer to the description of FCN 4.22 013

FCN 4.22 034 PRI(PI_SAG$PR) DIFFER TOO MUCH AT 100 MMHG [F]
Please refer to the description of FCN 4.22 014

FCN 4.22 035 FRI(FI_E$HPG) DIFFER TOO MUCH FROM PRI(PI_SAG$PR) AT 100 MMHG
[F]
Please refer to the description of FCN 4.22 015

FCN 4.22 036 FRI(FI_E$PD) DIFFER TOO MUCH FROM PRI(PI_SAG$PR) AT 100 MMHG
[F]
Please refer to the description of FCN 4.22 016

FCN 4.22 037 FLUID PRESSURES DIFFER TOO MUCH AT 100 MMHG [F]
Please refer to the description of FCN 4.22 017

FCN 4.22 038 UNSTABLE FLUID PRESSURES AT 100 MMHG [F]
Please refer to the description of FCN 4.22 018

FCN 4.22 041 FRI(FI_E$HPG) DIFFER TOO MUCH AT 100 MMHG, NO FLOW [F]
General description of conditions for occuring:
The high pressure guard pressure and the dialysis pressure differs
more than 25 mmHg
AND
The high pressure guard pressure and the safety guard pressure differs
more than 25 mmHg.

Technical description of conditions for occuring:
The high pressure guard pressure is regulated at 100 mmHg.
The DIVA valve is opened but TAVA valve is closed so that no flow
passes through the machine.
FRI(FI_E$HPG), FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable
for 5 seconds.
( FRI(FI_E$HPG) - FRI(FI_E$PD) < -250 ) OR
( FRI(FI_E$HPG) - FRI(FI_E$PD) > 250 )
AND
( FRI(FI_E$HPG) - PRI(PI_SAG$PR) < -250 ) OR
( FRI(FI_E$HPG) - PRI(PI_SAG$PR) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The high pressure guard transducer is uncalibrated.
* The high pressure guard transducer or its electronics is broken.

FCN 4.22 042 FRI(FI_E$PD) DIFFER TOO MUCH AT 100 MMHG,NO FLOW [F]
General description of conditions for occuring:
The dialysis pressure and the high pressure guard pressure differs
more than 25 mmHg
AND
The dialysis pressure and the safety guard pressure differs more than
25 mmHg.

Technical description of conditions for occuring:
The high pressure guard pressure is regulated at 100 mmHg.
The DIVA valve is opened but TAVA valve is closed so that no flow
passes through the machine.
FRI(FI_E$HPG), FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable
for 5 seconds.
( FRI(FI_E$PD) - FRI(FI_E$HPG) < -250 ) OR
( FRI(FI_E$PD) - FRI(FI_E$HPG) > 250 )
AND
( FRI(FI_E$PD) - PRI(PI_SAG$PR) < -250 ) OR
( FRI(FI_E$PD) - PRI(PI_SAG$PR) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The dialysis pressure transducer is uncalibrated.
* The dialysis pressure transducer or its electronics is broken.

FCN 4.22 043 FRI(FI_E$HPG) DIFFER TOO MUCH FROM FRI(FI_E$PD)
AT 100 MMHG, NO FLOW [F]
General description of conditions for occuring:
The high pressure guard pressure and the dialysis pressure differs
more than 25 mmHg

Technical description of conditions for occuring:
The high pressure guard pressure is regulated at 100 mmHg. The DIVA
valve is opened but TAVA valve is closed so that no flow passes
through the machine.
FRI(FI_E$HPG), FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable
for 5 seconds.
( FRI(FI_E$HPG) - FRI(FI_E$PD) < -250 ) OR
( FRI(FI_E$HPG) - FRI(FI_E$PD) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The high pressure guard transducer is uncalibrated.
* The high pressure guard transducer or its electronics is broken.
* The dialysis pressure transducer is uncalibrated.
* The dialysis pressure transducer or its electronics is broken.

FCN 4.22 044 PRI(PI_SAG$PR) DIFFER TOO MUCH AT 100 MMHG, NO FLOW [F]
General description of conditions for occuring:
The safety guard pressure and the high pressure guard pressure differs
more than 25 mmHg
AND
The safety guard pressure and the dialysis pressure differs more than
25 mmHg.

Technical description of conditions for occuring:
The high pressure guard pressure is regulated at 100 mmHg. The DIVA
valve is opened but TAVA valve is closed so that no flow passes
through the machine. FRI(FI_E$HPG), FRI(FI_E$PD) and PRI(PI_SAG$PR)
have all been stable for 5 seconds.
( PRI(PI_SAG$PR) - FRI(FI_E$HPG) < -250 ) OR
( PRI(PI_SAG$PR) - FRI(FI_E$HPG) > 250 )
AND
( PRI(PI_SAG$PR) - FRI(FI_E$PD) < -250 ) OR
( PRI(PI_SAG$PR) - FRI(FI_E$PD) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The safety guard pressure transducer is uncalibrated.
* The safety guard pressure transducer or its electronics is broken.

FCN 4.22 045 FRI(FI_E$HPG) DIFFER TOO MUCH FROM PRI(PI_SAG$PR)
AT 100 MMHG, NO FLOW [F]
General description of conditions for occuring:
The high pressure guard pressure and the safety guard pressure differs
more than 25 mmHg.

Technical description of conditions for occuring:
The high pressure guard pressure is regulated at 100 mmHg. The DIVA
valve is opened but TAVA valve is closed so that no flow passes
through the machine. FRI(FI_E$HPG), FRI(FI_E$PD) and PRI(PI_SAG$PR)
have all been stable for 5 seconds.
( FRI(FI_E$HPG) - PRI(PI_SAG$PR) < -250 ) OR
( FRI(FI_E$HPG) - PRI(PI_SAG$PR) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The high pressure guard transducer is uncalibrated.
* The high pressure guard transducer or its electronics is broken.
* The safety guard pressure transducer is uncalibrated.
* The safety guard pressure transducer or its electronics is broken.

FCN 4.22 046 FRI(FI_E$PD) DIFFER TOO MUCH FROM PRI(PI_SAG$PR) AT 100 MMHG,
NO FLOW [F]
General description of conditions for occuring:
The dialysis pressure and the safety guard pressure differs more than
25 mmHg.

Technical description of conditions for occuring:
The high pressure guard pressure is regulated at 100 mmHg.
The DIVA valve is opened but TAVA valve is closed so that no flow
passes through the machine.
FRI(FI_E$HPG), FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable
for 5 seconds.
( FRI(FI_E$PD) - PRI(PI_SAG$PR) < -250 ) OR
( FRI(FI_E$PD) - PRI(PI_SAG$PR) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The dialysis pressure transducer is uncalibrated.
* The dialysis pressure transducer or its electronics is broken.
* The safety guard pressure transducer is uncalibrated.
* The safety guard pressure transducer or its electronics is broken.

FCN 4.22 047 FLUID PRESSURES DIFFER TOO MUCH AT 100 MMHG, NO FLOW [F]
General description of conditions for occuring:
The high pressure guard pressure and the dialysis pressure differs
more than 25 mmHg
AND
The high pressure guard pressure and the safety guard pressure differs
more than 25 mmHg.
AND
The dialysis pressure and the safety guard pressure differs more than
25 mmHg.

Technical description of conditions for occuring:
The high pressure guard pressure is regulated at 100 mmHg. The DIVA
valve is opened but TAVA valve is closed so that no flow passes
through the machine.
FRI(FI_E$HPG), FRI(FI_E$PD) and PRI(PI_SAG$PR) have all been stable
for 5 seconds.
( FRI(FI_E$HPG) - FRI(FI_E$PD) < -250 ) OR
( FRI(FI_E$HPG) - FRI(FI_E$PD) > 250 )
AND
( FRI(FI_E$HPG) - PRI(PI_SAG$PR) < -250 ) OR
( FRI(FI_E$HPG) - PRI(PI_SAG$PR) > 250 )
AND
( FRI(FI_E$PD) - PRI(PI_SAG$PR) < -250 ) OR
( FRI(FI_E$PD) - PRI(PI_SAG$PR) > 250 )
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The high pressure guard transducer is uncalibrated.
* The high pressure guard transducer or its electronics is broken.
* The dialysis pressure transducer is uncalibrated.
* The dialysis pressure transducer or its electronics is broken.
* The safety guard pressure transducer is uncalibrated.
* The safety guard pressure transducer or its electronics is broken.

FCN 4.22 048 UNSTABLE FLUID PRESSURES AT 100 MMHG,NO FLOW [F]
General description of conditions for occuring:
It has for 1 minute not been possible to create a high pressure guard
pressure of 100 mmHg or at least one of the dialysis pressure, high
pressure guard pressure, and safety guard pressure have not been
stable for 1 minute.

Technical description of conditions for occuring:
All the conditions below have not been true within 1 minute:
* 950 <= FRI(FI_E$HPG) <= 1050
* The change of FRI(FI_E$HPG) during 1s is less than 100
* The change of FRI(FI_E$PD) during 1s is less than 100
* The change of PRI(PI_SAG$PR) during 1s is less than 100
The unit for all the pressures is 0.1mmHg.

Some possible explanations why the error has occured:
* The dialysis pressure transducer is uncalibrated.
* The high pressure guard transducer or its electronics is broken.
* The dialysis pressure transducer or its electronics is broken.
* The safety guard pressure transducer or its electronics is broken.
* The flow output pump is broken.
* The flow input pump is broken.

FCN 4.22 051 FRI(FI_E$HPG) DIFFER TOO MUCH AT 300 MMHG, NO FLOW [F]
Please refer to the description of FCN 4.22 041

FCN 4.22 052 FRI(FI_E$PD) DIFFER TOO MUCH AT 300 MMHG, NO FLOW [F]
Please refer to the description of FCN 4.22 042

FCN 4.22 053 FRI(FI_E$HPG) DIFFER TOO MUCH FROM FRI(FI_E$PD) AT 300 MMHG,
NO FLOW [F]
Please refer to the description of FCN 4.22 043

FCN 4.22 054 PRI(PI_SAG$PR) DIFFER TOO MUCH AT 300 MMHG, NO FLOW [F]
Please refer to the description of FCN 4.22 044

FCN 4.22 055 FRI(FI_E$HPG) DIFFER TOO MUCH FROM PRI(PI_SAG$PR) AT 300 MMHG,
NO FLOW [F]
Please refer to the description of FCN 4.22 045

FCN 4.22 056 FRI(FI_E$PD) DIFFER TOO MUCH FROM PRI(PI_SAG$PR) AT 300 MMHG,
NO FLOW [F]
Please refer to the description of FCN 4.22 046

FCN 4.22 057 FLUID PRESSURES DIFFER TOO MUCH AT 300 MMHG,NO FLOW [F]
Please refer to the description of FCN 4.22 047

FCN 4.22 058 UNSTABLE FLUID PRESSURES AT 300 MMHG,NO FLOW [F]
Please refer to the description of FCN 4.22 048

FCN 4.23, FLOW RESTRICTOR ESTIMATE FUNCTION (CPU D)
Purpose:
* Checks that the mainflow is one of the allowed mainflows in the monitor
* Calculates the low (negative) limit and the high (positive) limit for
the fluid pressures. The low limit is the flow output pressure, and
the high limit is the flow input pressure.
* Calculates restrictor coefficients for flow output pump and flow input
pump.
( PRESSURE = RESTRICTORCOEFF * FLOW * FLOW,
where PRESSURE is measured between the restrictor and the pump, and
FLOW is the flow through the restrictor. )
* Calculates calibration coefficients and calibration offsets for the
flow input pump and the flow output pump.
( DUTYCYCLE = CALCOEFF * DIFFPRESS + CALOFFSET,
DUTYCYCLE is converted to an output voltage for the pump.
FRI(FI_E$PUMP$OUT$DTCY) = 50 (=5%)
==> flow output pump voltage = 0.05 * max voltage.
FRI(FI_E$PUMP$OUT$DTCY) = 950 (=95%)
==> flow output pump voltage = 0.95 * max voltage.
1 unit of FRI(FI_E$PUMP$OUT$DTCY) = 0.1%
DIFFPRESS is the pressure over the pump.
DIFFPRESS over fl out pump =
FRI(FI_HPG$SET)-FRI(FI_E$PR$FLOW$OUT).
DIFFPRESS over fl in pump =
FRI(FI_E$PR$FLOW$IN) - FRI(FI_HPG$SET).
FRI(FI_E$PR$FLOW$OUT) is about -400mmHg.
FRI(FI_E$PR$FLOW$IN) is about +350mmHg.
1 unit of FRI(FI_E$PR$FLOW$OUT) = 0.1mmHg)
* Calculates other regulator parameters for the flow output pump and
flow input pump.

FCN 4.23 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.23 001 MAINFLOW ERROR [F]
General description of conditions for occuring:
The flow output pump restrictor can not create one of the mainflows
300 ml/min, 500 ml/min or 700 ml/min.

Technical description of conditions for occuring:
FRI(FI_E$PR$FLOW$OUT) SRI(10), FRI(FI_E$PR$FLOW$IN) SRI(9) and
FRI(FI_CH1$RATE) SRI(25) have been stable for 5s. During the following
5s FRR(FR_CH1$RATE) is outside the ranges 268.0 - 308.0, 453.0 - 525.0,
688.0 - 791.0
1 unit of FRR(FR_CH1$RATE) = 1 ml/min

Some possible explanations why the error has occured:
* The flow output pump restrictor is not correct, it might be dirty.
* The UF cell is badly calibrated.
* The flow output pump pressure transducer is badly calibrated.
* The UF cell or its electronics does not work.
* The flow output pump pressure transducer or its electronics does not
work.

Some hints of what to do if the error occurs:
Check if the flow output pump restrictor is dirty.
Enter diagnostic, pump diagnostic.
Regulate a flow output pump pressure that is -350 mmHg.
Check that the flow output pump pressure is -350mHg.
Check the flow through channel 1 of the UF cell.

FCN 4.23 002 FLOW OUTPUT PUMP TOO LOW DUTYCYCLE [F]
General description of conditions for occuring:
The flow output pump can not create a pressure over itself that is 20%
of the total pressure range even if it is told to be almost stopped.
(The flow output pump dutycycle is less than 5% when the differential
pressure over the flow output pump is 20% of the total pressure range.)

Technical description of conditions for occuring:
FRI(FI_E$PR$FLOW$OUT) SRI(10), FRI(FI_E$PR$FLOW$IN) SRI(9) and
FRI(FI_CH1$RATE) SRI(25) have been stable for 5s.
FRI(FI_E$PUMP$OUT$DTCY) < 50 when
FRI(FI_E$HPG$SET) = FRI(FI_E$PR$FLOW$OUT) +
0.20 * ( FRI(FI_E$PR$FLOW$IN) - FRI(FI_E$PR$FLOW$OUT) )
The unit for the dutycycle is 0.1% and for the pressures 0.1 mmHg.

Some possible explanations why the error has occured:
* The flow output pump is broken.
* The flow output pump motor is broken.
* The flow output pump electronics is broken.
* The high pressure guard pressure transducer is uncalibrated.
* The high pressure guard pressure transducer is broken.

FCN 4.23 003 FLOW OUTPUT PUMP TOO HIGH DUTYCYCLE [F]
General description of conditions for occuring:
The flow output pump can not create a pressure over itself that is 80%
of the total pressure range even if it is told to run as fast as it
can.
(The flow output pump dutycycle is greater than 95% when the
differential pressure over the flow output pump is 80% of the total
pressure range.)

Technical description of conditions for occuring:
FRI(FI_E$PR$FLOW$OUT) SRI(10), FRI(FI_E$PR$FLOW$IN) SRI(9) and
FRI(FI_CH1$RATE) SRI(25) have been stable for 5s.
FRI(FI_E$PUMP$OUT$DTCY) > 950 when
FRI(FI_E$HPG$SET) = FRI(FI_E$PR$FLOW$OUT) +
0.80 * ( FRI(FI_E$PR$FLOW$IN) - FRI(FI_E$PR$FLOW$OUT) )
The unit for the dutycycle is 0.1% and for the pressures 0.1 mmHg.

Some possible explanations why the error has occured:
* The flow output pump is dirty.
* The flow output pump is broken.
* The flow output pump motor is broken.
* The flow output pump electronics is broken.
* The high pressure guard pressure transducer is uncalibrated.
* The high pressure guard pressure transducer is broken.

FCN 4.23 004 FLOW INPUT PUMP TOO LOW DUTYCYCLE [F]
General description of conditions for occuring:
The flow input pump can not create a pressure over itself that is 20%
of the total pressure range even if it is told to be almost stopped.
(The flow input pump dutycycle is less than 5% when the differential
pressure over the flow input pump is 20% of the total pressure range.)

Technical description of conditions for occuring:
FRI(FI_E$PR$FLOW$OUT) SRI(10), FRI(FI_E$PR$FLOW$IN) SRI(9) and
FRI(FI_CH1$RATE) SRI(25) have been stable for 5s.
FRI(FI_E$PUMP$IN$DTCY) < 50 when
FRI(FI_E$HPG$SET) = FRI(FI_E$PR$FLOW$OUT) +
0.20 * ( FRI(FI_E$PR$FLOW$IN) - FRI(FI_E$PR$FLOW$OUT) )
The unit for the dutycycle is 0.1% and for the pressures 0.1 mmHg.

Some possible explanations why the error has occured:
* The flow input pump is broken.
* The flow input pump motor is broken.
* The flow input pump electronics is broken.
* The high pressure guard pressure transducer is uncalibrated.
* The high pressure guard pressure transducer is broken.

FCN 4.23 005 FLOW INPUT PUMP TOO HIGH DUTYCYCLE [F]
General description of conditions for occuring:
The flow input pump can not create a pressure over itself that is 80%
of the total pressure range even if it is told to run as fast as it
can.
(The flow input pump dutycycle is greater than 95% when the differential
pressure over the flow output pump is 80% of the total pressure range.)

Technical description of conditions for occuring:
FRI(FI_E$PR$FLOW$OUT) SRI(10), FRI(FI_E$PR$FLOW$IN) SRI(9) and
FRI(FI_CH1$RATE) SRI(25) have been stable for 5s.
FRI(FI_E$PUMP$IN$DTCY) > 950 when
FRI(FI_E$HPG$SET) = FRI(FI_E$PR$FLOW$OUT) +
0.80 * ( FRI(FI_E$PR$FLOW$IN) - FRI(FI_E$PR$FLOW$OUT) )
The unit for the dutycycle is 0.1% and for the pressure 0.1 mmHg.

Some possible explanations why the error has occured:
* The flow input pump is dirty.
* The flow input pump is broken.
* The flow input pump motor is broken.
* The flow input pump electronics is broken.
* The high pressure guard pressure transducer is uncalibrated.
* The high pressure guard pressure transducer is broken.

FCN 4.23 006 FLOW OUTPUT PUMP RESTRICTOR COEFF OUT OF RANGE [F]
General description of conditions for occuring:
The flow output pump restrictor coefficient is outside its allowed
limits.

Technical description of conditions for occuring:
FRI(FI_E$PR$FLOW$OUT) SRI(10), FRI(FI_E$PR$FLOW$IN) SRI(9) and
FRI(FI_CH1$RATE) SRI(25) have been stable for 5s.
FRR(FR_FOP$RESTR$COEFF) > -350.0 / (791.0 * 791.0 ) for 5s
or
FRR(FR_FOP$RESTR$COEFF) < -350.0 / (268.0 * 268.0 ) for 5s
The unit of the restrictor coeff=0.1mmHg/(1 ml/min*1 ml/min)

Some possible explanations why the error has occured:
* The flow output pump restrictor is not correct, it might be dirty.
* The UF cell is badly calibrated.
* The flow output pump pressure transducer is badly calibrated.
* The UF cell or its electronics does not work.
* The flow output pump pressure transducer or its electronics does not
work.

FCN 4.23 007 FLOW INPUT PUMP RESTRICTOR COEFF OUT OF RANGE [F]
General description of conditions for occuring:
The flow input pump restrictor coefficient is outside its allowed
limits.

Technical description of conditions for occuring:
FRI(FI_E$PR$FLOW$OUT) SRI(10), FRI(FI_E$PR$FLOW$IN) SRI(9) and
FRI(FI_CH1$RATE) SRI(25) have been stable for 5s.
FRR(FR_FIP$RESTR$COEFF) > 0.009 for 5s
or
FRR(FR_FIP$RESTR$COEFF) < 0.0002 for 5s
The unit of the restrictor coeff=0.1mmHg/(1 ml/min*1 ml/min)

Some possible explanations why the error has occured:
* The flow input pump restrictor is not correct, it might be dirty.
* The UF cell is badly calibrated.
* The flow input pump pressure transducer is badly calibrated.
* The UF cell or its electronics does not work.
* The flow input pump pressure transducer or its electronics does not
work.

FCN 4.24 UF AUTO CALIBRATION FUNCTION (CPU D)
Purpose:
* Reads the low level and high level signals from the UF calibration box
during automatical calibration of UF.
* Sends the following box modes to the UF calibration box: "manual mode",
"mode 0" (=closed), "mode 1" (=low level fillup),
"mode 2" (=high level fillup), "mode 3" (=high level drain),
and mode 4".(=low level drain)

FCN 4.24 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.28 BLOOD PUMP SEGMENT CONTROLLER (CPU A)

FCN 4.28 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.29, FLOW SUPERVISION FUNCTION (CPU D)

Purpose:

* Detect if flow transducer is broken. Test limits are

if uf control : Difference between measured uf-rate and set value
rate is less than -100 ml/min or bigger than
+250 ml/min for more than 30s.
if tmp control : Measured uf-rate is less than -100 ml/min or
bigger than +250 ml/min for more than 30s.

When detected the function will request for a self check of the flow
transducer. From the operators point of view this will look like an
ordinary self calibration on the panel except for the color of the
fluid path that will be orange.

FCN 4.29 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.30, UF LOCAL LOGGING (CPU D)

Purpose:

*Handle the logging of data concerning the uf-flowmeter
in the E2prom located on the uf measuring unit. Data
that is logged concerns the calibration parameters that
are estimated by the self calibrations during treatments
and the function 4.05 error codes. Data in the E2prom
can be dumped to an ASCII file by using a PC shell
program to the AK100 XL program. The shell program is
called UFLOG and can be ordered by Your local Gambro
office.

FCN 4.30 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.31, ONLINE VALVE CONTROL, OPTIONAL VALVE CONTROL (CPU D)

FCN 4.31 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.32, POST BLOOD PUMP STOP VOLUME CHECK (CPU D)

FCN 4.32 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.33, RESTRICTOR SUPERVISION OF MAINFLOW (CPU D)

FCN 4.33 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.33 001 Volume diff (flowmeter-restrictor) out of limit [F,T,D,S]

FCN 4.34, CENTRAL CONCENTRATE VALVE CONTROL (CPU D)

FCN 4.34 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.35, DUO PUMP SET VALUE FUNCTION (CPU D)
* Sets the duo pump speed

FCN 4.35 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.36, HDF NORMALIZATION (CPU A)
* Normalisation of the rawvalues from the scale (HDF100)

FCN 4.36 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.38, TOP PRIMING FUNCTION (CPU D)
* Controls TPVA and BCVA
* Reads level in BiCart trap

FCN 4.38 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 4.39, PBVA FUNCTION (CPU D)
* Controls PBVA

FCN 4.39 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

E2prom run-time meter control function. (CPU D).

FCN 4.41 000 = Case error. The program is not working properly.
Please refer to the description of FCN 1.00 000.

FCN 5.00, ARTERIAL PUMP CONTROL FUNCTION (CPU A)
Purpose:
(Please also refer to the description of FCN 1.06)
* Controls the speed of the arterial blood pump.
* Controls if the arterial blood pump should run or not.
* Reads if the arterial blood pump cover is open.
* Reads if the arterial blood pump is overloaded.
* Function check 1: Commands the arterial blood pump to run. The safe
bus is set in alarm mode which disconnects the 24V supply for the
blood pump. Function 5.00 checks that the blood pump is not moving.
* Function check 2: Commands the arterial blood pump to run. Checks that
it is moving.
* Function check 3: Sets the pump speed for the arterial blood pump to 0.
Enables the arterial blood pump by setting BPAE/ = 0.
* Function check 4: Sets a pump speed for the arterial blood pump.
Disables the arterial blood pump by setting BPAE/ = 1.
* Function check 5: Commands the arterial blood pump to run. CPU A does
not trigg the monostable multivibrator IC 26 on the BM CPU board which
results in that the 24V supply for the blood pump is disconnected.
* Function check 6: CPU B resets the monostable multivibrator IC 26 on
the BM CPU board, which results in that the 24V supply for the blood
pump is disconnected. Function 5.00 commands the blood pump to run,
and checks that it is not moving.

FCN 5.00 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 5.00 001 TIMER ERROR [F,T,D,S]
General description of conditions for occuring:
The arterial blood pump timer is not working properly.

Technical description of conditions for occuring:
The timer 9513 has returned one of the following error messages:
"Timer load to counter error", "Load register error",
"Mode register error" or "Hold register error".

Some possible explanations why the error has occured:
* The timer IC 104 on the BM CPU board (K11352) is broken.

FCN 5.00 002 ARTERIAL PUMP RUNNING WHILE SAFE BUS ALARMING ERROR [F]
General description of conditions for occuring:
The arterial blood pump was moving 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.
Function 5.00 commanded the arterial blood pump to run and no other
electronic signals tried to stop it. The arterial blood pump was
moving after 2s.
(The timer IC 104 on the BM CPU board K11352 had counted more than 10
units as the signal ATP0 indicated that the pump was moving.)

Some possible explanations why the error has occured:
* The relay K1 on the BM CPU board (K11353) is broken.
(this error is probable if the blood pump is moving)
* The timer IC 104 on the BM CPU board (K11352) is broken.
(this error is probable if the blood pump is not moving)

FCN 5.00 003 ARTERIAL PUMP STOP WHILE SAFE BUS NOT ALARMING ERROR [F]
General description of conditions for occuring:
The arterial blood pump was 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.
Function 5.00 commanded the arterial blood pump to run and no other
electronic signals tried to stop it.
The arterial blood pump was NOT moving after 5s.
(The timer IC 104 on the BM CPU board K11352 had counted less than 10
units as the signal ATP0 indicated that the pump was not moving.)

Some possible explanations why the error has occured:
* The arterial blood pump is broken.
* Some of the electronics on the arterial blood pump distribution board
K11345 is 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 overload sensor is broken.
* Some cablings are broken.
* The timer IC 104 on the BM CPU board K11352 is broken.
* The enable signal BPAE/ is 1.
* There is no current in the safe bus.
* CPU A does not trig IC 26 on the BM CPU board.
* CPU B resets IC 26 on the BM CPU board (PBPE = 0V).

FCN 5.00 004 ARTERIAL PUMP INHIBIT TEST ERROR [F]
General description of conditions for occuring:
The arterial blood pump was moving during function check even if the
protective system tried to stop it.

Technical description of conditions for occuring:
Function 5.00 stopped the blood pump for 2s.
CPU B reset the monostable multivibrator IC 26 on the BM CPU board
(PBPE=0V), which resulted in that the 24V supply for the pump was
disconnected. Function 5.00 commanded the blood pump to run. The blood
pump was moving after it has been commanded to run for 3s.
(The timer IC 104 on the BM CPU board K11352 had counted more than 10
units as the signal ATP0 indicated that the pump was moving.)

Some possible explanations why the error has occured:
* The relay K1 on the BM CPU board is broken.
* The monostable multivibrator IC 26 on the BM CPU board is broken.
* The timer IC 104 on the BM CPU board K11352 is broken.
* Some of the electronics on the arterial blood pump distribution board
K11345 are broken.

FCN 5.01, VENOUS PUMP CONTROL FUNCTION (CPU A)
Purpose:
Also refer to the descriptions of FCN 5.00 and FCN 1.06.
* Controls the speed of the venous blood pump.
* Controls if the venous blood pump should run or not.
* Reads if the venous blood pump cover is open.
* Reads if the venous blood pump is overloaded.
* Function check 1: Commands the venous blood pump to run. The safe bus
is set in alarm mode which disconnects the 24V supply for the blood
pump. Function 5.01 checks that the blood pump is not moving.
* Function check 2: Commands the venous blood pump to run. Checks that
it is moving.
* Function check 3: Sets the pump speed for the venous blood pump to 0.
Enables the venous blood pump by setting BPVE/ = 0.
* Function check 4: Sets a pump speed for the venous blood pump.
Disables the venous blood pump by setting BPVE/ = 1.
* Function check 5: Commands the venous blood pump to run. CPU A does
not trigg the monostable multivibrator IC 26 on the BM CPU board which
results in that the 24V supply for the blood pump is disconnected.
* Function check 6: CPU B resets the monostable multivibrator IC 26 on
the BM CPU board, which results in that the 24V supply for the blood
pump is disconnected. Function 5.01 commands the blood pump to run,
and checks that it is not moving.

FCN 5.01 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 5.01 001 TIMER ERROR [F,T,D,S]
Please refer to the description of FCN 5.00 001.

FCN 5.01 002 VENOUS PUMP RUNNING WHILE SAFE BUS ALARMING ERROR [F]
Please refer to the description of FCN 5.00 002.

FCN 5.01 003 VENOUS PUMP STOP WHILE SAFE BUS NOT ALARMING ERROR [F]
Please refer to the description of FCN 5.00 003.

FCN 5.01 004 VENOUS PUMP INHIBIT TEST ERROR [F]
Please refer to the description of FCN 5.00 004.

FCN 5.02, HEPARIN FLOW CONTROL FUNCTION (CPU A)
Purpose:
* Controls the speed of the heparin pump by letting the timer 4, IC85 on
the BM CPU board create a frequency.
The heparin pump speed set value, ORI(OI_HEP$SET) is used to calculate
the timer 4 set frequency.
* Controls if the heparin pump shall run or not.
* Checks if the heparin pump is overloaded because it has reached its end
position.
* Stops the heparin pump if it is overloaded or has any technical errors.
* Calculates how much the heparin pump has moved by letting the timer 5,
IC85 on the BM CPU board count pulses from the heparin pump encoder.
Checks that the number of counted pulses does not differ too much from
the estimated number of pulses.
* Checks that the heparin pump is moving when it is commanded to move
during the function checks.

GENERAL EQUATIONS:
Syringe area = 3.142 * (ORI(OI_HEP$SYR$DIAM)/10)/2 *
(ORI(OI_HEP$SYR$DIAM)/10)/2 [mm2]
Volume = (Syringe area * length)/1000 [ml]
Volume / time = ORI(OI_HEP$SET) / (10*3600) [ml/s]
Length / time = ORI(OI_HEP$SET) / (36*Syringe area) [mm/s]
Output frequency = 160*ORI(OI_HEP$SET)/Syringe area [Hz]
Length = Encoder pulses/50 [mm]

/FCN 5.02 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

/FCN 5.02 001 TIMER ERROR [F,T,(D,S)]
Please refer to the description of FCN 5.00 001.

Technical description of conditions for occuring:
ORI(OI_HEP$SET) > 0

Some possible explanations why the error has occured:
* The timer 4, IC 85 on the BM CPU board (K11352) is broken.

/FCN 5.02 002 TIMER ERROR [F,T,(D,S)]
Please refer to the description of FCN 5.00 001.

Technical description of conditions for occuring:
ORI(OI_HEP$SET) > 0

Some possible explanations why the error has occured:
* The timer 5, IC 85 on the BM CPU board (K11352) is broken.

/FCN 5.02 003 HEPARIN PUMP SPEED TOO LOW [F,T,(D,S)]
General description of conditions for occuring:
The heparin pump speed was too low compared to the estimated heparin
pump speed.

Technical description of conditions for occuring:
ORI(OI_HEP$SET) > 0
The heparin pump was commanded to run with the set speed,
ORI(OI_HEP$SET), which has the unit 0.1 ml/h.
BRI(BI_HEP$EST$ACC) - BRI(BI_HEP$ACC) >= 3 [*0.1ml]
BRI(BI_HEP$EST$ACC) = Time*ORI(OI_HEP$SET)/3600 [0.1ml]
(Estimated volume = Time*ORI(OI_HEP$SET)/(10*3600) [ml] )
BRI(BI_HEP$ACC)= Syringe area*Encoder pulses/5000 [0.1ml]
(Measured volume= Syringe area*(Encoder pulses/50)/1000 [ml])
Please also refer to "GENERAL EQUATIONS" above.

Some possible explanations why the error has occured:
* The heparin pump cog wheel does not follow the heparin pump belt.
* The heparin pump belt broke during the treatment.
* The heparin pump cog wheel is skidding. (The heparin pump axis does not
turn as fast as the heparin pump cog wheel).
* The heparin pump encoder is broken.
* The heparin pump motor is broken.
* One of the driver circuits IC117 or IC129 on the BM CPU board K11352 is
broken.
* The buffer, IC127 on the BM CPU board K11351 is broken.
* The timer, IC85 on the BM CPU board K11352 is broken.
* The PAL, IC126 on the BM CPU board K11351 is broken.
* IC87 on the BM CPU board K11352 is broken.

/FCN 5.02 004 HEPARIN PUMP SPEED TOO HIGH [F,T,(D,S)]
General description of conditions for occuring:
The heparin pump speed was too high compared to the estimated heparin
pump speed.

Technical description of conditions for occuring:
ORI(OI_HEP$SET) > 0
The heparin pump was commanded to run with the set speed,
ORI(OI_HEP$SET), which has the unit 0.1 ml/h.
BRI(BI_HEP$ACC)-BRI(BI_HEP$EST$ACC) >= 3 [*0.1ml]
BRI(BI_HEP$EST$ACC) = Time*ORI(OI_HEP$SET)/3600 [0.1ml]
(Estimated volume = Time*ORI(OI_HEP$SET)/(10*3600) [ml] )
BRI(BI_HEP$ACC)= Syringe area*Encoder pulses/5000 [0.1ml]
(Measured volume= Syringe area*(Encoder pulses/50)/1000 [ml])
Please also refer to "GENERAL EQUATIONS" above.

Some possible explanations why the error has occured:
* The heparin pump encoder is broken.
* The timer, IC85 on the BM CPU board K11352 is broken. The output
frequency is too high.
* The PAL, IC126 on the BM CPU board K11351 is broken.
* The buffer, IC127 on the BM CPU board K11351 is broken.

/FCN 5.02 005 SYRINGE DIAMETER ERROR [F,T,D,S]
General description of conditions for occuring:
The syringe diameter is incorrect.

Technical description of conditions for occuring:
ORI(OI_HEP$SYR$DIAM) < ORI(OI_HEP$SYR$DIAM$LL$LVL$3) [*0.1mm]
OR
ORI(OI_HEP$SYR$DIAM) > ORI(OI_HEP$SYR$DIAM$HL$LVL$3) [*0.1mm]
OR
Syringe area > 1020 [mm2]
Please also refer to "GENERAL EQUATIONS" above.

Some possible explanations why the error has occured:
* The program is not executing correctly.
* Data stored in the RAM, IC84 on the BM CPU board K11355 has changed in
an uncorrect way. If the error occures once again after the monitor has
been turned off and on again, then the RAM is probably broken.

/FCN 5.02 006 HEPARIN PUMP MOVING WHEN IT SHOULD NOT MOVE [F,T,D,S]
General description of conditions for occuring:
The heparin pump was moving even if it was commanded not to move.

Technical description of conditions for occuring:
The heparin pump was commanded to stop.
The pot counter counted more than 10 encoder pulses during 1s.
Please also refer to "GENERAL EQUATIONS" above.

Some possible explanations why the error has occured:
* One of the driver circuits IC117 or IC129 on the BM CPU board K11352 is
broken.
* The timer, IC85 on the BM CPU board K11352 is broken.
* The PAL, IC126 on the BM CPU board K11351 is broken.
* The buffer, IC127 on the BM CPU board K11351 is broken.

/FCN 5.02 007 HEPARIN PUMP FUNCTION CHECK FAILURE [F]
General description of conditions for occuring:
The heparin pump was commanded to move during the function checks, but
the detected movement was too small.

Technical description of conditions for occuring:
The heparin pump was told to run with the set value Heparin pump speed
= 10 ml/h and Syringe area = 254 mm2 during the function checks. The
pot counter counted less than 8 encoder pulses during 30s. It should
have counted 16 encoder pulses.
Please also refer to "GENERAL EQUATIONS" above.

Some possible explanations why the error has occured:
Please refer to the explanations of FCN 5.02 003.

FCN 5.03, TEMPERATURE FUNCTION (CPU D)
Purpose:
* Regulates how much the heating rods should be turned on. There is a
temperature drop from the temperature transducer in the heating vessel,
FRI(FI_TEMP) SRI(14) and the temperature transducer after the second
conductivity cell, QRI(QI_TEMP$B) SRI(16). The function creates a
dutycycle for the heating rods which gives FRI(FI_TEMP) the value
( ORI(OI_TEMP$SET) + temperature drop ).
If the dutycycle is 25%, then the heating rods are on 25% of the time.
The LEDS V43 or V44 on the FM CPU board K11303 are lit when the timer,
IC61 commands the heating rods to be on.
* CPU C commands the relay K1 on the relay board K11481 to break the
power supply for the heating rods during the function check. If the
temperature FRI(FI_TEMP) has not decreased at least 1 degree within
1 minute, then a technical alarm is given.

FCN 5.03 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 5.03 001 TIMER ERROR [F,T,D,S]
Please refer to the description of FCN 5.00 001.
The timer, IC61 on the FM CPU board K11303 is broken.

FCN 5.03 002 TEMP NOT DECREASING DURING FUNCTION CHECK [F]
General description of conditions for occuring:
The temperature did not decrease during the function checks when the
relay K1 on the relay board should break the power supply to the
heating rods.

Technical description of conditions for occuring:
The temparature FRI(FI_TEMP), SRI(14) [*0.01 degree C] is saved in a
variable called "Start temperature". FCN 5.03 commands the heating
rods to be on with 100% dutycycle. FCN 1.08 commands the relay K1 on
the relay board K11481 to break the power supply to the heating rods.
FRI(FI_TEMP) >= ( "Start temperature"-100 ) [*0.01 degree C] after
1 minute.

Some possible explanations why the error has occured:
* The heating rods are not connected to P2 on the relay board K11481.
* The mains cable from the relay board is not connected to the mains
connection at the power supply unit.
* The cable from the FM CPU board is not connected to P1 on the relay
board K11481.
* The overtemperature guard on top of the heating vessel has released.
* A 10A fuse in the AC / DC unit is broken.
* The relay K1 on the relay board K11481 is broken.
* Q4 on the FM CPU board K11304 is broken.
* IC58 on the FM CPU board K11304 is broken.

Some hints of what to do if the error occurs:
Check connections.

Fluid composition function. (CPU D).

FCN 5.04 000 = Case error. The program is not working properly.

FCN 5.04 001 = Timer handler error.

FCN 5.04 002 = Test of TPVA valve failed.
The test is done by comparing the conductivity cell A with conductivity
cell B (control). The conductivity in A-step must be more than 10 mS/cm.
The maximum difference allowed is 0.3 mS/cm. The difference must be
within the limit for 30 seconds. Maximum time (conductivity > 10 mS/cm)
for the test is 5 minutes.
Some possible explanations why the error has occured:
* TPVA valve is leaking.
* Conductivity cell A needs to be calibrated.
* Conductivity cell B needs to be calibrated.
* PBVA valve is leaking.

FCN 5.05, DEGASS PRESSURE FUNCTION (CPU D)
Purpose:
* Regulates the degassing pressure by creating a pulsewidth for
controlling the degassing motor. The degassing motor and the degassing
pump are connected with magnets. If it is not possible to regulate the
degassing pressure, it can depend on that the magnet in the pump does
not follow the magnet in the motor. If so is the case, the function
tries to stop the motor for 1 second and then to regulate again for
150 seconds.
* Checks that the degassing pressure is above a certain limit.

FCN 5.05 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 5.05 001 TIMER ERROR [F,T,D,S]
Please refer to the description of FCN 5.00 001.

FCN 5.05 002 TOO HIGH DEGASS PRESSURE [F,T]
General description of conditions for occuring:
The measured degassing pressure is greater than the set degassing
pressure for 15 minutes, and it is also greater than -500 mmHg for
15 minutes.

Technical description of conditions for occuring:
(FRI(FI_DEGASSPR) > ORI(OI_DEGASS$PR$SET) + 200) and
FRI((FI_DEGASSPR) > -5000)
for 150 continous seconds and after 300s, 450s, 600s, 750s and 900s.
1 unit of FRI(FI_DEGASSPR) = 0.1mmHg.

Some possible explanations why the error has occured.
* The degassing motor is broken.
* The degassing pump is not ok.
* The degassing pressure transducer is broken.
* The degassing pressure amplifier is broken.
* The A/D system is broken.

Some hints of what to do if the error occures
Check degass pressure with internal logging.
If the motorvoltage is > 20 volt, check for airleakage or check the
degassing pump.

FCN 5.06, DEGASS LEVEL FUNCTION (CPU D)
Purpose:
* Regulates the degass level in the bubble trap following the flow pump.
The degass level is regulated by letting a motor control how much the
recirculation valve should be opened.
* Checks that the degass level in the bubble trap is within certain
limits. An ultrasonic transducer is used to measure the degass level.

FCN 5.06 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 5.06 001 INCORRECT DEGASS LEVEL [F,T,S]
General description of conditions for occuring:
The degass level is incorrect if it is outside the limits 35mm-65mm
for 5 minutes.

Technical description of conditions for occuring:
(FRI(FI_DEGASS$LVL) < 350 or FRI(FI_DEGASS$LVL) > 650)
The total time that the degass level has been incorrect is 5 minutes
longer than the total time that it has been correct.
1 unit of FRI(FI_DEGASS$LVL) = 0.1 mm.

Some possible explanations why the error has occured:
* Problems with the ultrasonic transducer in the bubble trap.
* The motor controlling the recirculation valve is not working properly.
* The monitor can not create enough of fluid through the degassing pump.
* There are particles in the degassing chamber.
* The concentrate is too old.
* The bubble trap is not positioned completely vertically.
* The tube inside the chamber is not in the correct position.

Some hints of what to do if the error occurs:
Check degass level with internal logging. SRI(28).
The level should be about 50.0 mm. (+/- 2 mm.)
Look for particles in degassing chamber.
Check "Used before date" on concentrate container.

FCN 5.08, MAIN FLOW CONTROL FUNCTION (CPU D)
Purpose:
* Gives CPU E information about how fast CPU E shall run the flow output
pump. All information to CPU E is sent via the flow generator
communication function.
During treatment when the conductivity is above 11mS:
Gives CPU E a set value for FRI(FI_PR$FLOW$OUT) that will make the
main flow FRR(FR_CH1$RATE) correspond to the set main flow
FRI(FI_MAINFL$SET).
The set value is stored in SRI(56) and has the unit 0.5 mmHg.
FRI(FI_PR$FLOW$OUT) SRI(10) has the unit 0.1 mmHg.
FRR(FR_CH1$RATE) SRR(0) has the unit 1 ml/min.
FRI(FI_MAINFL$SET) is usually 5000 [*0.1 ml/min].
* During self calibrations in treatment or when the conductivity is
below 11mS:
Sends a constant set value for FRI(FI_PR$FLOW$OUT) to CPU E.
The set value is stored in SRI(56) and has the unit 0.5 mmHg.
* During other modes:
Sends a set value for FRI(FI_PR$FLOW$OUT) to CPU E.
The set value is stored in SRI(56) and has the unit 0.5 mmHg.
OR
Sends a set value for FRI(FI_E$HPG) to CPU E.
The set value is stored in SRI(56) and has the unit 0.5 mmHg.
OR
Sends a set value for FRI(FI_E$PD) to CPU E.
The set value is stored in SRI(56) and has the unit 0.5 mmHg.
OR
Sends a set value for the flow output pump voltage to CPU E.
The set value is stored in SRI(56). One unit is about 0.35mV.
* Sends calibration constants and regulator constants that have been
calculated in FCN 4.23 to CPU E.

FCN 5.08 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 5.08 001 MAIN FLOW TOO LOW ERROR [T,S]
General description of conditions for occuring:
The time that the flow output pump pressure has been below a minimum
limit is one minute longer than the time it has been above that
minimum limit.

Technical description of conditions for occuring:
Do once a second:
if (FRI(FI_PR$FLOW$OUT) < FRI(FI_PR$RANGE$LL) - 500) then
Error counter = Error counter - 1
else if ( FRI(FI_PR$FLOW$OUT) > 500 ) then
Error counter = Error counter + 1
else if ( Error counter > 0 ) then
Error counter = Error counter - 1
else if ( Error counter < 0 ) then
Error counter = Error counter + 1
Error counter <= - 60
FRI(FI_PR$FLOW$OUT) SRI(10) and FRI(FI_PR$RANGE$LL) SRI(44)
have the unit 0.1 mmHg.

Some possible explanations why the error has occured:
* The flow output pump restrictor is dirty.
* The flow output pump pressure transducer is badly calibrated.
* The flow output pump is dirty.
* The water filter after the heating vessel is dirty.
* The flow output pump pressure transducer is broken.
* The flow output pump motor electronics is broken.
* The flow output pump is broken.
* The flow output pump motor is broken.
* The degassing pressure transducer is broken.
* The degassing pump is dirty.
* The degassing pump motor electronics is broken.
* The degassing pump is broken.
* The degassing pump motor is broken.
* The ultra sonic transducer in the degassing chamber is broken.
* The pH measuring unit is not correctly mounted. High pressure drop.
* The flow path between the degassing chamber and the flow output pump
restrictor is dirty or not correctly mounted.
* The flow path between the flow output pump and the HPG pressure
transducer is dirty or not correctly mounted.
* The throttle before the degassing chamber is dirty.
* The degassing pressure transducer is badly calibrated.
* The flow output pump pressure transducer is badly calibrated.

Some hints of what to do if the error occurs:
Check and/or clean the flow output pump restrictor.
Check the flow output pump pressure transducer.

FCN 5.08 002 MAIN FLOW TOO HIGH ERROR [T,S]
General description of conditions for occuring:
The time that the flow output pump pressure has been above a maximum
limit is one minute longer than the time it has been below that maximum
limit.

Technical description of conditions for occuring:
Do once a second:
if (FRI(FI_PR$FLOW$OUT) < FRI(FI_PR$RANGE$LL) - 500) then
Error counter = Error counter - 1
else if ( FRI(FI_PR$FLOW$OUT) > 500 ) then
Error counter = Error counter + 1
else if ( Error counter > 0 ) then
Error counter = Error counter - 1
else if ( Error counter < 0 ) then
Error counter = Error counter + 1
Error counter >= 60
FRI(FI_PR$FLOW$OUT) SRI(10) and FRI(FI_PR$RANGE$LL) SRI(44)
have the unit 0.1 mmHg.

Some possible explanations why the error has occured:
* The flow output pump pressure transducer is badly calibrated.
* The flow output valve FOVA is leaking.
* The flow output pump pressure transducer is broken.
* The flow output pump electronics is broken.
(Commands the flow output pump to run too fast.)

FCN 5.08 003 FLOW OUTPUT PUMP RESTRICTOR ERROR [S]
General description of conditions for occuring:
The mainflow is less than 500 ml/min during UF calibration.

Technical description of conditions for occuring:
FRI(FI_MAIN$FL$SET) < 5000 [*0.1 ml/min] during UF calibration.

Some possible explanations why the error has occured:
* Incorrect flow output pump restrictor.
* The flow output pump restrictor is dirty.

FCN 5.10, Differential flow control function. (CPU D).

FCN 5.10 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 5.10 003 DIALYSATE PRESSURE TOO LOW OR TOO HIGH DURING [T]
THE DIRECT AND TARATION VALVE TEST.
General description of conditions for occuring:
PD was more than +50 mmHg or less than -50 mmHg during direct
valve or taration valve leakage tests. Should have been near
0 mmHg as RFVA is open and the tubes from heating vessel and
safety bypass unit is filled with air and the pressure in
heating vessel is 0 mmHg.

Technical description of conditions for occuring:
Functional check of CPU D was running.
Air was entered into the deairating chamber by opening the
recirculation flow valve (RFVA).
Direct and taration valve test was started.
The direct valve (DIVA) and tava valve (TAVA) were closed.
The recirculation flow valve (RFVA) was opened.
The dialysate pressure (Pd) was more than +50 mmHg or less
than -50 mmHg for more than 5 seconds.

Some possible explanations why the error has occured:
* Tubes was removed from Safety Bypass Unit before the functional
check was ready.
* TAVA broken, constantly open.
* DIVA broken, constantly open.
* Broken or bad calibrated dialysate pressure (Pd) transducer.
* Fluid path from heating vessel to Safety Bypass Unit obstructed.

FCN 5.10 004 ZERO PRESSURE CONTROL TIMEOUT DURING THE DIRECT AND [T]
TARATION VALVE LEAKAGE TESTS.
General description of conditions for occuring:
Not possible to control the high pressure guard (Phpg) pressure
to the value of the dialysate pressure (Pd) within 120 seconds.

Technical description of conditions for occuring:
Functional check of CPU D was running.
Direct and taration valve test was started.
The direct valve (DIVA) and tava valve (TAVA) were closed.
The recirculation flow valve (RFVA) was opened.
The Flow Input Pump starts to control high pressure guard
pressure (Phpg) to be equal to the pressure on the other side
of the direct valve (DIVA) and taration valve (TAVA) measured
by dialysate pressure transducer,Pd.
The controlled pressure (Phpg) differed more than +/5 mmHg for
more than 120 seconds from dialysate pressure (Pd).

Some possible explanations why the error has occured:
* FLOW OUTPUT PUMP RESTRICTOR: The restrictor is dirty.
* FLOW OUTPUT PUMP: The pump is not working properly.
* The flow system before bubble trap 1 causes an unstable level in
bubble trap 1.
* FLOW OUTPUT PUMP PRESSURE TRANSDUCER: Not working properly.
* FLOW INPUT PUMP RESTRICTOR: The restrictor is dirty.
* FLOW INPUT PUMP: The pump is not working properly.
* FLOW INPUT PUMP PRESSURE TRANSDUCER: Not working properly.
* Dialysate pressure (Pd) transducer not working properly (unstable
signal from the transducer itself).
* High pressure guard (Phpg) transducer not working properly (unstable
signal from the transducer itself).

Some hints of what to do if the error occurs:
Check if flow output pump pressure (SRI-10) is stable. The
pressure should be -350 to -425 mmHg and not vary more than
+/- 2 mmHg.

FCN 5.10 005 PRESSURE CONTROL TIMEOUT DURING THE DIRECT VALVE [T]
LEAKAGE TEST.

General description of conditions for occuring:
Not possible to control the high pressure guard (Phpg) pressure
within 120 seconds to the value requested by the direct valve
(DIVA) leakage test.

Technical description of conditions for occuring:
Functional check of CPU D was running.
Direct and taration valve test was started.
The direct valve (DIVA) and tava valve (TAVA) were closed.
The recirculation flow valve (RFVA) was opened.
The test was succesfully proceeded until the start of the
direct valve leakage test.
The Flow Input Pump starts to control high pressure guard
pressure (Phpg) to the requested value of the direct valve
leakage test. The test pressure was Pd - 300 mmHg or the minimum
allowed system pressure estimated during the Flow System
Calibration state of the functional check.
The controlled pressure (Phpg) differed more than +/5 mmHg
from requested value for more than 120 seconds.

Some possible explanations why the error has occured:
* TAVA leaking.
* DIVA leaking.
* FLOW INPUT PUMP RESTRICTOR: The restrictor is dirty.
* FLOW INPUT PUMP: The pump is not working properly.
* The flow system before bubble trap 1 causes an unstable level in
bubble trap 1.
* FLOW INPUT PUMP PRESSURE TRANSDUCER: Not working properly.
* FLOW OUTPUT PUMP RESTRICTOR: The restrictor is dirty.
* FLOW OUTPUT PUMP: The pump is not working properly.
* FLOW OUTPUT PUMP PRESSURE TRANSDUCER: Not working properly.
* Dialysate pressure (Pd) transducer not working properly (unstable
signal from the transducer itself).
* High pressure guard (Phpg) transducer not working properly (unstable
signal from the transducer itself).

Some hints of what to do if the error occurs:
Check if flow output pump pressure (SRI-10) is stable. The
pressure should be -350 to -425 mmHg and not vary more than
+/- 2 mmHg.

Check if channel 1 flow rate,SRI(25) is negative ( < -10 ml/min) or
unstable caused by air sucked through tubings from Safety Bypass Unit
then error is probably caused by big leakage of the DIVA valve.

Check if channel 2 flow rate,SRI(26) is positive ( > +10 ml/min) or
unstable caused by air sucked through tubings from Safety Bypass Unit
then error is probably caused by big leakage of the TAVA valve.

FCN 5.10 006 PRESSURE CONTROL TIMEOUT DURING THE TARATION VALVE [T]
LEAKAGE TEST.

General description of conditions for occuring:
Not possible to control the high pressure guard (Phpg) pressure
within 120 seconds to the value requested by the taration valve
(TAVA) leakage test.

Technical description of conditions for occuring:
Functional check of CPU D was running.
Direct and taration valve test was started.
The direct valve (DIVA) and tava valve (TAVA) were closed.
The recirculation flow valve (RFVA) was opened.
The test was succesfully proceeded until the start of the
taration valve leakage test.
The Flow Input Pump starts to control high pressure guard
pressure (Phpg) to the requested value of the taration valve
leakage test. The test pressure was Pd + 300 mmHg or the maximum
allowed system pressure estimated during the Flow System
Calibration state of the functional check.
The controlled pressure (Phpg) differed more than +/5 mmHg
from requested value for more than 120 seconds.

Some possible explanations why the error has occured:
* TAVA leaking.
* DIVA leaking.
* FLOW INPUT PUMP RESTRICTOR: The restrictor is dirty.
* FLOW INPUT PUMP: The pump is not working properly.
* The flow system before bubble trap 1 causes an unstable level in
bubble trap 1.
* FLOW INPUT PUMP PRESSURE TRANSDUCER: Not working properly.
* FLOW OUTPUT PUMP RESTRICTOR: The restrictor is dirty.
* FLOW OUTPUT PUMP: The pump is not working properly.
* FLOW OUTPUT PUMP PRESSURE TRANSDUCER: Not working properly.
* Dialysate pressure (Pd) transducer not working properly (unstable
signal from the transducer itself).
* High pressure guard (Phpg) transducer not working properly (unstable
signal from the transducer itself).

Some hints of what to do if the error occurs:
Check if flow output pump pressure (SRI-10) is stable. The
pressure should be -350 to -425 mmHg and not vary more than
+/- 2 mmHg.

Check if channel 1 flow rate,SRI(25) is positive ( > +10 ml/min)
then error is probably caused by big leakage of DIVA valve.

Check if channel 2 flow rate,SRI(26) is negative ( < -10 ml/min)
then error is probably caused by big leakage of TAVA valve.

FCN 5.11, DIALYZER DEAIRATING FUNCTION (CPU D)
Purpose:
* Opens the evacuation valve for 400ms if the measured fluid level in
bubble trap 2 is less than 15mm.
* Sends a technical error if the measured fluid level has been greater
than 68.5mm for 30s.
* Sends a major airleak attention if the evacuation valve has been
opened 15 times or more during 30s.
* Sends a minor airleak attention if the fluid level in bubble trap 2
has decreased more than 10 ml/min.

FCN 5.11 000 SOFTWARE ERROR [F,T,D,S]
Please refer to the description of FCN 1.00 000.

FCN 5.11 001 TOO BIG AIR LEAKAGE FROM THE BUBBLE TRAP 2 [T,S]
General description of conditions for occuring:
The measured fluid level in bubble trap 2 has been greater than 68.5mm
for 30s.

Technical description of conditions for occuring:
FRL(F_DEAIR$LVL$AH) = true for 30s AND
The evacuation valve has been closed for less than 10 min
OR
FRL(F_DEAIR$LVL$AH) = true for 30s AND
The the evvacuation valve has been closed for 10 minutes AND
more than 100 microliters / minute have been leaking.

Some possible explanations why the error has occured:
* The Evacuation valve (EVVA) is leaking.
* The ultrasonic transducer is not working properly.
* There has been a very high positive pressure in the chamber. This
pressure is > 400 mm Hg.
* The surface smoothener (the tube) inside the deairating chamber has
been removed or is not in the correct position.
* The evacuation tube from the top of the chamber is leaking.

Some hints of what to do if the error occurs:
Use an oscilloscope. 20 usec./div - 0.5 volt/div. The kick pulse and
the echo signal can be seen at R132 on the FM CPU board. It should be
above 1.5 volt. This check is not valid during heating.

Single needle generator. (CPU A).

FCN 5.12 000 = Case error. The program is not working properly.

Mean blood flow and control. (CPU A).

FCN 5.13 000 = Case error. The program is not working properly.
FCN 5.13 001 = Timer error.

Blood flow and volume measurement. (CPU A).

FCN 5.14 000 = Case error. The program is not working properly.
FCN 5.14 001 = Timer error type 1.
FCN 5.14 002 = Timer error type 2.
FCN 5.14 003 = Timer error type 3.
FCN 5.14 004 = Timer error type 4.
FCN 5.14 005 = Timer error.
FCN 5.14 006 = Timer error.
FCN 5.14 007 = Timer error.

BM fan function. (CPU A).

FCN 5.15 000 = Case error. The program is not working properly.

FM fan function. (CPU D).

FCN 5.16 000 = Case error. The program is not working properly.
Duty cycle was selected more than 99%.

FM Disinfectant and Cleaning agent supervision function. (CPU D).

FCN 5.17 000 = Case error. The program is not working properly.

Initialization function. (CPU A).

FCN 6.00 000 = Case error. The program is not working properly.
FCN 6.00 001 = Analog main board interface not connected.
FCN 6.00 002 = No communication contact with CPU B or/and CPU C.
FCN 6.00 003 = No communication contact with CPU D.
FCN 6.00 004 = Watchdog reset test timeout error.
FCN 6.00 005 = CPU A Power-up/Recovery string protocol error.
FCN 6.00 006 = CPU A Power-up/Recovery string timeout error.
*FCN 6.00 007 = Safe bus activation detected (by FCN809).

Reset handler function. (CPU B).

FCN 6.01 001 = Unexpected status from watchdog.
FCN 6.01 002 = Watchdog reset timeout test failure.
FCN 6.01 003 = Watchdog SAFE-bus control/status failure.

Reset handler function. (CPU C).

FCN 6.02 001 = Unexpected status from watchdog.
FCN 6.02 002 = Watchdog reset timeout test failure.
FCN 6.02 003 = Watchdog SAFE-bus control/status failure.

Initialization function. (CPU D).

FCN 6.03 001 = Watchdog reset test timeout error.
FCN 6.03 002 = Watchdog reset test SAFE-bus error.
FCN 6.03 003 = Undefined reset test string.
FCN 6.03 004 = CPU D Power-up/Recovery string protocol error.
FCN 6.03 005 = CPU D Power-up/Recovery string timeout error.

Master communication function. (CPU A).

FCN 7.00 001 = Removed.
Previously: Communication timeout.
FCN 7.00 002 = Removed.
Previously: Communication command error.
FCN 7.00 003 = Communication buffer too small.
FCN 7.00 004 = HDF communication buffer too small.

Communication function. (CPU C).

FCN 7.02 001 = Illegal communication, Hardware problem.

Local logging CPU A.

FCN 8.05 001 = Opcom part command error.
FCN 8.05 002 = Blood part command error.
FCN 8.05 003 = System logging command error.

Local logging CPU B.

FCN 8.06 001 = Protective system part command error.
FCN 8.06 002 = System logging command error.

Local logging CPU C.

FCN 8.07 001 = Protective system part command error.
FCN 8.07 002 = System logging command error.

Local logging CPU D.

FCN 8.08 001 = Protective system part command error.
FCN 8.08 002 = System logging command error.

FCN 8.09, CPU A SUPERVISORY TASK (CPU A)
Purpose:
* Supervises every 50 ms that all parts of the CPU A software is
executing within certain time intervalls. (task supervision) Sends the
error codes "E90" - "E9B" if any part of the software has not been
executing in time.
* Supervises every 50 ms that the CPU B supervisory task, FCN 8.10 has
been executing correctly within a certain time.
* Supervises every 50 ms that the CPU D supervisory task, FCN 8.12 has
been executing correctly within a certain time.
* Supervises every 50 ms that the operators communication state machine
in CPU A has been executing within a certain time. Sends the error
code "EA0" if it has not been executing.
* Supervises every 50 ms that the blood part state machine in CPU A has
been executing within a certain time. Sends the error code "EA1" if it
has not been executing.
* Calculates the checksums of the CPU A PROMs when CPU A is not doing
anything else.

How the CPUs are connected:
CPU A ===== CPU B ===== CPU C ===== CPU D (physical connections)
----> ----> (logical connections)
<---- <----
---------------------------->
<----------------------------
Example: CPU C is physically connected to CPU B and to CPU D.
CPU C is logically connected to CPU B.
A message from CPU C to CPU D is sent as follows:
From C to B, from B to A, from A via B and C to D.

Note! Sometimes the 8.09 errors can only be observed in the diagnostics
error buffer!

*FCN 8.09 001 CPU B SUPERVISORY TASK TIME OUT [F,T,D,S]
General description of conditions for occuring:
FCN 8.09 can not detect that the CPU B supervisory task, FCN 8.10 has
been executing within a certain time.

Technical description of conditions for occuring:
do every 50 ms:
if BRB(BB_A$B$TASK$SUPER$CNT) = PRB(PB_B$A$TASK$SUPER$CNT) + 1 then
( CPU B supervisory task has NOT executed )
Timeout counter = Timeout counter + 1
if Timeout counter > PB(EPB_B$TASK$TO$HL) then
Send the error code "FCN 8.09 001"
else
( CPU B supervisory task has executed and has set
PRB(PB_B$A$TASK$SUPER$CNT) = BRB(BB_A$B$TASK$SUPER$CNT) + 1 )
Timeout counter = 0
BRB(BB_A$B$TASK$SUPER$CNT) = PRB(PB_B$A$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* Hardware disturbances in the communication between CPU B and CPU C.
(IC55, IC56, R70, Q4, R71, Q5 on the BM CPU board K11354.
P111 on the BM CPU board K11356.
P134 and P133 on the BM power distribution board K11364.
P59 and P61 on the FM power distribution board K11330.
P4 on the FM CPU board K11306.
IC107, IC88, IC78 on the FM CPU board.)
* The CPU B software is not executing correctly.
* The CPU C software is not executing correctly.
* The CPU D software is not executing correctly.
* Communication hardware between CPU A and CPU B is broken or badly
connected. The error code FCN 8.09 001 would not have appeared if the
hardware was completely broken during the function checks.
> IC65 or IC66 on the BM CPU board K11354.
> IC81, IC98 or IC68 on the BM CPU board K11354.
> The memory bank board K13614 is badly connected to the BM CPU board.
* Communication hardware between CPU B and CPU C is broken or badly
connected. The error code FCN 8.09 001 would not have appeared if the
hardware was completely broken during the function checks.
> IC53 on the BM CPU board K11354.
> The memory bank board K13614 is badly connected to the BM CPU board.
> IC68, IC55, IC56, Q4, Q5, R70, R71 on the BM CPU board K11354.
> P111 on the BM CPU board K11356.
> P134 and P133 on the BM power distribution board K11364.
> P59 and P61 on the FM power distribution board K11330.
> P4 on the FM CPU board K11306.
> IC107, IC88, IC78, IC84 on the FM CPU board K11305.
> CPU C, IC103 on the FM CPU board K11305.
* Communication hardware between CPU C and CPU D is broken or badly
connected. The error code FCN 8.09 001 would not have appeared if the
hardware was completely broken during the function checks.
> IC83 or IC85 on the FM CPU board K11305.
> IC97, IC104, IC84, IC103 on the FM CPU board K11305.
* CPU B hardware is broken or badly connected. The error code
FCN 8.09 001 would not have appeared if the hardware was completely
broken during the function checks.
> IC2, IC3, IC4, IC5 on the memory bank board K13614.
> The memory bank board K13614 is badly connected to the BM CPU board.
> IC36, IC16, IC3, J1, IC6, IC39 on the BM CPU board K11354.
> All circuits that are connected to the CPU B data bus (PDAx or PAMx)
on the BM CPU board.
* CPU C hardware is broken or badly connected. The error code
FCN 8.09 001 would not have appeared if the hardware was completely
broken during the function checks.
> IC103, IC89, IC96, IC95, J13, IC110 on the FM CPU board K11305.
> The watchdog, IC73 on the FM CPU board K11303.
> All circuits that are connected to the CPU C data bus (PDAx or PAMx)
on the FM CPU board.
* CPU D hardware is broken or badly connected. The error code
FCN 8.09 001 would not have appeared if the hardware was completely
broken during the function checks.
> IC101, J4, IC81 on the FM CPU board K11301.
> The watchdog, IC73 on the FM CPU board K11303.
> All circuits that are connected to the CPU D data bus (ADMx) on the
FM CPU board.

Some hints of what to do if the error occurs:
Some of the LEDs on the BM CPU board and FM CPU board could give some
further explanations of the error.
Note! The lables beside the LEDs on old BM CPU boards are not correct.
The lables "V1, V2, .." under the LEDs are always correct.
CPU A executed correctly during the function checks and was
communicating with CPU B, CPU C and CPU D if:
All the LEDs V12 - V17 on the BM CPU board are off.
CPU A is executing if:
The LED V10 is flashing. (CPU A operators comm. state machine)
The LED V11 is flashing. (CPU A blood part state machine)
The LED V18 on the BM CPU board is flashing. (BM board watchdog)
CPU B is executing if:
The LED V1 on the BM CPU board is off. (CPU B start up test OK)
The LED V2 on the BM CPU board is lit. (CPU B start up test OK)
The LED V9 on the BM CPU board is flashing. (CPU B state machine)
The LED V18 on the BM CPU board is flashing. (BM board watchdog)
CPU C is executing if:
The LED V45 on the FM CPU board is flashing. (FM board watchdog)
The LED V52 on the FM CPU board is lit. (CPU C start up test OK)
The LED V53 on the FM CPU board is off. (CPU C start up test OK)
The LED V54 on the FM CPU board is flashing. (CPU C state machine)
CPU D is executing if:
The LED V41 on the FM CPU board is flashing. (CPU D state machine)
The LED V45 on the FM CPU board is flashing. (FM board watchdog)

If any of the CPUs are not executing then do the following:
* Turn off the monitor and turn it on again.
* Wait until the flow path on the operators panel is lit up.
* Remove the jumper J15 on the BM CPU board K11354.
* Remove the jumper J1 on the FM CPU board K11303.
* Wait until the error that caused the error code FCN 8.09 001
occurs once again. When this happens, one or more of the CPUs
will stop. (Please refer to the LED information above.)
CPU A errors are displayed as "Enn" on the time display.
CPU D errors are displayed on the LEDs V27 - V40 on the FM CPU
board. "Enn" errors as well as "V27-V40" errors are described at
the beginning of this document.
Note! The LEDs V27-V40 are used for other purposes than error
indication when the LEDs V41 and V45 are flashing!

FCN 8.09 002 CPU B SUPERVISORY TASK COUNT UP ERROR [F,T,D,S]
General description of conditions for occuring:
FCN 8.09 detected that the CPU B supervisory task, FCN 8.10 had been
executing, but that the variable PRB(PB_B$A$TASK$SUPER$CNT) had an
incorrect value. The CPU B supervisory task should have updated this
variable correctly.

Technical description of conditions for occuring:
do every 50 ms:
if BRB(BB_A$B$TASK$SUPER$CNT) <> PRB(PB_B$A$TASK$SUPER$CNT) + 1 then
( CPU B supervisory task has executed and should have set
PRB(PB_B$A$TASK$SUPER$CNT) = BRB(BB_A$B$TASK$SUPER$CNT) + 1 )
Timeout counter = 0
if PRB(PB_B$A$TASK$SUPER$CNT) <> BRB(BB_A$B$TASK$SUPER$CNT)+1 then
Send the error code "FCN 8.09 002"
BRB(BB_A$B$TASK$SUPER$CNT) = PRB(PB_B$A$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* The CPU B software is not executing correctly.
* The CPU B RAM, IC6 on the BM CPU board K11354 is broken.
* CPU B, IC2 on the memory bank board K13614 is broken.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001.

*FCN 8.09 003 CPU D SUPERVISORY TASK TIME OUT [F,T,D,S]
General description of conditions for occuring:
FCN 8.09 can not detect that the CPU D supervisory task, FCN 8.12 has
been executing within a certain time.

Technical description of conditions for occuring:
do every 50 ms:
if BRB(BB_A$D$TASK$SUPER$CNT) = FRB(FB_D$A$TASK$SUPER$CNT) + 1 then
( CPU D supervisory task has NOT executed )
Timeout counter = Timeout counter + 1
if Timeout counter > PB(EPB_D$TASK$TO$HL) then
Send the error code "FCN 8.09 003"
else
( CPU D supervisory task has executed and has set
FRB(FB_D$A$TASK$SUPER$CNT) = BRB(BB_A$D$TASK$SUPER$CNT) + 1 )
Timeout counter = 0
BRB(BB_A$D$TASK$SUPER$CNT) = FRB(FB_D$A$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
Please refer to the explanations of FCN 8.09 001.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001.

FCN 8.09 004 CPU D SUPERVISORY TASK COUNT UP ERROR [F,T,D,S]
General description of conditions for occuring:
FCN 8.09 detected that the CPU D supervisory task, FCN 8.12 had been
executing, but that the variable FRB(FB_D$A$TASK$SUPER$CNT) had an
incorrect value. The CPU D supervisory task should have updated this
variable correctly.

Technical description of conditions for occuring:
do every 50 ms:
if BRB(BB_A$D$TASK$SUPER$CNT) <> FRB(FB_D$A$TASK$SUPER$CNT) + 1 then
( CPU D supervisory task has executed and should have set
FRB(FB_D$A$TASK$SUPER$CNT) = BRB(BB_A$D$TASK$SUPER$CNT) + 1 )
Timeout counter = 0
if FRB(FB_D$A$TASK$SUPER$CNT) <> BRB(BB_A$D$TASK$SUPER$CNT)+1 then
Send the error code "FCN 8.09 004"
BRB(BB_A$D$TASK$SUPER$CNT) = FRB(FB_D$A$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* The CPU D software is not executing correctly.
* The CPU D RAM, IC98 on the FM CPU board K11301 is broken.
* CPU D, IC101 on the FM CPU board K11301 is broken.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001.

FCN 8.09 005 PROM ERROR CPU A IC103 [F,T,D,S]
General description of conditions for occuring:
The checksum calculation of the PROM IC103 failed.

Technical description of conditions for occuring:
FCN 8.09 calculated the checksum for the CPU A PROM IC103 on the BM
CPU board K11355. It differed from the checksum that was stored in
that PROM. (IC103 corresponds to the addresses 20000H-3FFFFH)

Some possible explanations why the error has occured:
* The CPU A PROM IC103 is broken.

FCN 8.09 006 PROM ERROR CPU A IC57 [F,T,D,S]
General description of conditions for occuring:
The checksum calculation of the PROM IC57 failed.

Technical description of conditions for occuring:
FCN 8.09 calculated the checksum for the CPU A PROM IC57 on the BM
CPU board K11355. It differed from the checksum that was stored in
that PROM. (IC57 corresponds to the addresses E0000H-FFFFFH)

Some possible explanations why the error has occured:
* The CPU A PROM IC57 is broken.

FCN 8.09 007 PROM ERROR CPU A IC73 [F,T,D,S]
General description of conditions for occuring:
The checksum calculation of the PROM IC73 failed.

Technical description of conditions for occuring:
FCN 8.09 calculated the checksum for the CPU A PROM IC73 on the BM
CPU board K11355. It differed from the checksum that was stored in
that PROM. (IC103 corresponds to the addresses A0000H-BFFFFH)

Some possible explanations why the error has occured:
* The CPU A PROM IC73 is broken.

FCN 8.10, CPU B SUPERVISORY TASK (CPU B)
Purpose:
* Commands the CPU B watchdog to turn on the current through the safe bus
during the function checks.
(Please refer to "How the safe bus is connected" below.)
* Trigs the CPU B watchdog every 3 seconds.
(The CPU B watchdog resets CPU A and CPU B if it is not trigged.)
* Supervises every 200 ms that all parts of the CPU B software is running
within certain time intervalls. (task supervision) Stops the blood
pump(s), closes the clamps and the direct valve and starts the buzzer
if any part of the software has not been executing in time.
(No errorcodes)
* Supervises every 200 ms that the CPU A supervisory task, FCN 8.09 has
been executing correctly within a certain time.
* Supervises every 200 ms that the CPU C supervisory task, FCN 8.11 has
been executing correctly within a certain time.
* Supervises every 200 ms that the CPU B state machine has been
executing within a certain time. (No errorcodes)
* At certain conditions: (please refer to FCN 8.10 007 below)
Commands the CPU B watchdog to reset CPU A and CPU B.
Commands the CPU B watchdog to turn off the safe bus current.
(Please refer to "How the safe bus is connected" below.)
* Calculates the checksum for the CPU B PROM when CPU B is not doing
anything else.

How the CPUs are connected:
CPU A ===== CPU B ===== CPU C ===== CPU D (physical connections)
----> ----> (logical connections)
<---- <----
---------------------------->
<----------------------------
Example: CPU C is physically connected to CPU B and to CPU D.
CPU C is logically connected to CPU B.
A message from CPU C to CPU D is sent as follows:
From C to B, from B to A, from A via B and C to D.

How the safe bus is connected:
The safe bus is a single conductor which lets current flow from a
current generator Q8 and V23 on the BM CPU board K11352 to a
terminator IC52 on the FM CPU board K11305. The safe bus has the
signal names SBSI and SBSO on the BM CPU board, and the signal names
SBSI, SBSF and SBSO on the FM CPU board. The LED V46 on the FM CPU
board K11305 is lit when NO current is flowing through the safe bus.
The following circuits control the current through the safe bus:
* The CPU B watchdog IC 36 on the BM CPU board K11354 uses the signal
SWBC to control the current generator.
* IC18 on the BM CPU board K11353 controlled by the CPU B watchdog and
the power supply alarm.
* IC77 on the FM CPU board K11305 controlled by the CPU C watchdog
IC73 on the FM CPU board K11303 and the power supply alarm.
The following optocouplers sense if current is flowing through the
safe bus:
* IC19 on the BM CPU board K11352.
The CPU B watchdog senses the safe bus status but takes no action.
* IC18 on the BM CPU board K11353.
The 24 volt supply for the blood pump(s) is turned off if no
current is flowing through the safe bus.
* IC39 on the FM CPU board K11306.
The 24 volt supply for the direct valve, the inlet valve, the flow
output pump and the flow input pump is turned off if no current is
flowing through the safe bus.
* IC77 on the FM CPU board K11305.
The CPU C watchdog IC73 on the FM CPU board K11303 senses the safe
bus status and resets CPU C, CPU D and CPU E if no current is
flowing through the safe bus.

Note! Sometimes the 8.10 errors can only be observed in the diagnostics
error buffer!

FCN 8.10 001 CPU A SUPERVISORY TASK TIMEOUT [F,T,D,S]
General description of conditions for occuring:
FCN 8.10 could not detect that the CPU A supervisory task, FCN 8.09
had been executing within a certain time.

Technical description of conditions for occuring:
do every 200 ms:
if PRB(PB_B$A$TASK$SUPER$CNT) = BRB(BB_A$B$TASK$SUPER$CNT) + 1 then
( CPU A supervisory task has NOT executed )
Timeout counter = Timeout counter + 1
if Timeout counter > PB(EPB_A$TASK$TO$HL) then
Send the error code "FCN 8.10 001"
else
( CPU A supervisory task has executed and has set
BRB(BB_A$B$TASK$SUPER$CNT) = PRB(PB_B$A$TASK$SUPER$CNT) + 1 )
Timeout counter = 0
PRB(PB_B$A$TASK$SUPER$CNT) = BRB(BB_A$B$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* Hardware disturbances in the communication between CPU B and CPU C.
Refer to the explanation of FCN 8.09 001 for further information.
* The CPU A software is not executing correctly.
* The CPU C software is not executing correctly.
* The CPU D software is not executing correctly.
* Communication hardware between CPU A and CPU B is broken or badly
connected. The error code FCN 8.10 001 would not have appeared if the
hardware was completely broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* Communication hardware between CPU B and CPU C is broken or badly
connected. The error code FCN 8.10 001 would not have appeared if the
hardware was completely broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* Communication hardware between CPU C and CPU D is broken or badly
connected. The error code FCN 8.10 001 would not have appeared if the
hardware was completely broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* CPU A hardware is broken or badly connected. The error code
FCN 8.10 001 would not have appeared if the hardware was completely
broken during the function checks.
> IC9, J5, IC5 on the BM CPU board K11355.
> The watchdog, IC36 on the BM CPU board K11354.
> All circuits that are connected to the CPU A data bus (ADMx) on the
BM CPU board.
* CPU C hardware is broken or badly connected. The error code
FCN 8.10 001 would not have appeared if the hardware was completely
broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* CPU D hardware is broken or badly connected. The error code
FCN 8.10 001 would not have appeared if the hardware was completely
broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001.

FCN 8.10 002 CPU A SUPERVISORY TASK COUNT UP ERROR [F,T,D,S]
General description of conditions for occuring:
FCN 8.10 detected that the CPU A supervisory task, FCN 8.09 had been
executing, but that the variable BRB(BB_A$B$TASK$SUPER$CNT) had an
incorrect value. The CPU A supervisory task should have updated this
variable correctly.

Technical description of conditions for occuring:
do every 200 ms:
if PRB(PB_B$A$TASK$SUPER$CNT) <> BRB(BB_A$B$TASK$SUPER$CNT) + 1 then
( CPU A supervisory task has executed and should have set
BRB(BB_A$B$TASK$SUPER$CNT) = PRB(PB_B$A$TASK$SUPER$CNT) + 1 )
if BRB(BB_A$B$TASK$SUPER$CNT) <> PRB(PB_B$A$TASK$SUPER$CNT)+1 then
Send the error code "FCN 8.10 002"
PRB(PB_B$A$TASK$SUPER$CNT) = BRB(BB_A$B$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* The CPU A software is not executing correctly.
* The CPU A RAM, IC84 on the BM CPU board K11355 is broken.
* CPU A, IC9 on the BM CPU board K11355 is broken.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001.

FCN 8.10 003 CPU C SUPERVISORY TASK TIMEOUT [F,T,D,S]
General description of conditions for occuring:
FCN 8.10 could not detect that the CPU C supervisory task, FCN 8.11
had been executing within a certain time.

Technical description of conditions for occuring:
do every 200 ms:
if PRB(PB_B$C$TASK$SUPER$CNT) = QRB(QB_C$B$TASK$SUPER$CNT) + 1 then
( CPU C supervisory task has NOT executed )
Timeout counter = Timeout counter + 1
if Timeout counter > PB(EPB_C$TASK$TO$HL) then
Send the error code "FCN 8.10 003"
else
( CPU C supervisory task has executed and has set
QRB(QB_C$B$TASK$SUPER$CNT) = PRB(PB_B$C$TASK$SUPER$CNT) + 1 )
Timeout counter = 0
PRB(PB_B$C$TASK$SUPER$CNT) = QRB(QB_C$B$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* Hardware disturbances in the communication between CPU B and CPU C.
Refer to the explanation of FCN 8.09 001 for further information.
* The CPU C software is not executing correctly.
* The CPU D software is not executing correctly.
* Communication hardware between CPU B and CPU C is broken or badly
connected. The error code FCN 8.10 003 would not have appeared if the
hardware was completely broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* Communication hardware between CPU C and CPU D is broken or badly
connected. The error code FCN 8.10 003 would not have appeared if the
hardware was completely broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* CPU C hardware is broken or badly connected. The error code
FCN 8.10 003 would not have appeared if the hardware was completely
broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* CPU D hardware is broken or badly connected. The error code
FCN 8.10 003 would not have appeared if the hardware was completely
broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001.

FCN 8.10 004 CPU C SUPERVISORY TASK COUNT UP ERROR [F,T,D,S]
General description of conditions for occuring:
FCN 8.10 detected that the CPU C supervisory task, FCN 8.11 had been
executing, but that the variable QRB(QB_C$B$TASK$SUPER$CNT) had an
incorrect value. The CPU C supervisory task should have updated this
variable correctly.

Technical description of conditions for occuring:
do every 200 ms:
if PRB(PB_B$C$TASK$SUPER$CNT) <> QRB(QB_C$B$TASK$SUPER$CNT) + 1 then
( CPU C supervisory task has executed and should have set
QRB(QB_C$B$TASK$SUPER$CNT) = PRB(PB_B$C$TASK$SUPER$CNT) + 1 )
if QRB(QB_C$B$TASK$SUPER$CNT) <> PRB(PB_B$C$TASK$SUPER$CNT)+1 then
Send the error code "FCN 8.10 004"
PRB(PB_B$C$TASK$SUPER$CNT) = QRB(QB_C$B$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* The CPU C software is not executing correctly.
* The CPU C RAM, IC96 on the FM CPU board K11305 is broken.
* CPU C, IC103 on the FM CPU board K11305 is broken.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001

FCN 8.10 005 CPU B WATCHDOG REPLY ERROR [F,T,D,S]
General description of conditions for occuring:
FCN 8.10 tried to trig the watchdog, but the watchdog did not reply
correctly.

Technical description of conditions for occuring:
FCN 8.10 tried to trig the CPU B watchdog IC36 on the BM CPU board
K11354. The watchdog reply was not one unit greater than the last
watchdog reply.

Some possible explanations why the error has occured:
* The CPU B watchdog, IC36 on the BM CPU board K11354 is broken.
* The CPU B RAM, IC6 on the BM CPU board K11354 is broken.

FCN 8.10 006 PROM ERROR CPU B IC 4 ON MEMORY BANK BOARD [F,T,D,S]
General description of conditions for occuring:
The checksum calculation of the PROM IC4 on the memory bank board
failed.

Technical description of conditions for occuring:
FCN 8.10 calculated the checksum for the CPU B PROM IC4 on the memory
bank board K13614. It differed from the checksum that was stored in
that PROM.

Some possible explanations why the error has occured:
* The PROM IC4 on the memory bank board K13614 is broken.

FCN 8.10 007 CPU B WATCHDOG RESET REQUEST ERROR [F,T,D,S]
General description of conditions for occuring:
The CPU B watchdog did not reset CPU B when it was commanded to do so.

Technical description of conditions for occuring:
FCN 8.10 commanded the CPU B watchdog IC36 on the BM CPU board K11354
to reset CPU A and CPU B and to turn off the safe bus current.
(Please refer to "How the safe bus is connected" above)
CPU B was not reset after 1 second.
Some reasons why FCN 8.10 commanded the watchdog reset:
* CPU A commanded FCN 8.10 to do a watchdog reset because the
operator exited the service mode.
CPU A commands a watchdog reset by setting
ORB(OB_SYS$RES$RQ$0) = 'R' , ORB(OB_SYS$RES$RQ$1) = 'E' ,
ORB(OB_SYS$RES$RQ$2) = 'S' , ORB(OB_SYS$RES$RQ$3) = 'R' ,
ORB(OB_SYS$RES$RQ$4) = 'Q'
* CPU A detected a transient error (marked "*FCN .... ..." in this
document) and commanded FCN 8.10 to do a watchdog reset.
* FCN 8.10 sent one of the error codes FCN 8.10 001, FCN 8.10 002,
FCN 8.10 003 or FCN 8.10 004 and CPU A did not command any
watchdog reset for 4 seconds.

Some possible explanations why the error has occured:
* The jumper J15 on the BM CPU board K11354 is not installed.
* IC38 on the BM CPU board K11354 is broken.
* IC68 on the BM CPU board K11354 is broken.
* The CPU B watchdog, IC36 on the BM CPU board K11354 is broken.

FCN 8.10 008 PROM ERROR CPU B IC 4 ON MEMORY BANK BOARD
General description of conditions for occuring:
The error code has been removed.

FCN 8.10 009 PROM ERROR CPU B IC 4 ON MEMORY BANK BOARD
General description of conditions for occuring:
The error code has been removed.

FCN 8.11, CPU C SUPERVISORY TASK (CPU C)
Purpose:
* Commands the CPU C watchdog to turn on the current through the safe bus
during the function checks.
(Please refer to "How the safe bus is connected" in the description
of FCN 8.10.)
* Trigs the CPU C watchdog every 3 seconds.
(The watchdog resets CPU C, CPU D and CPU E if it is not trigged.)
* Supervises every 200 ms that all parts of the CPU C software is running
within certain time intervalls. (task supervision) Turns off the heater
and closes the direct valve if any part of the software has not been
executing in time. (No errorcodes)
* Supervises every 200 ms that the CPU B supervisory task, FCN 8.10 has
been executing correctly within a certain time. If it has not then:
Commands the CPU C watchdog to reset CPU C, CPU D and CPU E.
Commands the CPU C watchdog to turn off the safe bus current.
(Please refer to "How the safe bus is connected" in the description
of FCN 8.10.)
* Supervises every 200 ms that the CPU C state machine has been
executing within a certain time. Turns off the heater and closes the
direct valve if any part of the software has not been executing in
time. (No errorcodes)
* Calculates the checksum for the CPU C PROM when CPU C is not doing
anything else.

How the CPUs are connected:
CPU A ===== CPU B ===== CPU C ===== CPU D (physical connections)
----> ----> (logical connections)
<---- <----
---------------------------->
<----------------------------
Example: CPU C is physically connected to CPU B and to CPU D.
CPU C is logically connected to CPU B.
A message from CPU C to CPU D is sent as follows:
From C to B, from B to A, from A via B and C to D.

Note! Sometimes the 8.11 errors can only be observed in the diagnostics
error buffer!

FCN 8.11 001
The error code has been removed.

FCN 8.11 002
The error code has been removed.

FCN 8.11 003 CPU B SUPERVISORY TASK TIMEOUT [F,T,D,S]
General description of conditions for occuring:
FCN 8.11 could not detect that the CPU B supervisory task, FCN 8.10
had been executing within a certain time.

Technical description of conditions for occuring:
do every 200 ms:
if QRB(QB_C$B$TASK$SUPER$CNT) = PRB(PB_B$C$TASK$SUPER$CNT) + 1 then
( CPU B supervisory task has NOT executed )
Timeout counter = Timeout counter + 1
if Timeout counter > PB(EPB_B$TASK$TO$HL) then
Send the error code "FCN 8.11 003"
Command the CPU C watchdog to reset CPU C, CPU D and CPU E.
Command the CPU C watchdog to turn off the safe bus current.
(Please refer to "How the safe bus is connected" in the
description of FCN 8.10.)
else
( CPU B supervisory task has executed and has set
PRB(PB_B$C$TASK$SUPER$CNT) = QRB(QB_C$B$TASK$SUPER$CNT) + 1 )
Timeout counter = 0
QRB(QB_C$B$TASK$SUPER$CNT) = PRB(PB_B$C$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* Hardware disturbances in the communication between CPU B and CPU C.
Refer to the explanation of FCN 8.09 001 for further information.
* The CPU B software is not executing correctly.
* The CPU D software is not executing correctly.
* Communication hardware between CPU B and CPU C is broken or badly
connected. The error code FCN 8.11 003 would not have appeared if the
hardware was completely broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* Communication hardware between CPU C and CPU D is broken or badly
connected. The error code FCN 8.11 003 would not have appeared if the
hardware was completely broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* CPU B hardware is broken or badly connected. The error code
FCN 8.11 003 would not have appeared if the hardware was completely
broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* CPU D hardware is broken or badly connected. The error code
FCN 8.11 003 would not have appeared if the hardware was completely
broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001.

FCN 8.11 004 CPU B SUPERVISORY TASK COUNT UP ERROR [F,T,D,S]
General description of conditions for occuring:
FCN 8.11 detected that the CPU B supervisory task, FCN 8.10 had been
executing, but that the variable PRB(PB_B$C$TASK$SUPER$CNT) had an
incorrect value. The CPU B supervisory task should have updated this
variable correctly.

Technical description of conditions for occuring:
do every 200 ms:
if QRB(QB_C$B$TASK$SUPER$CNT) <> PRB(PB_B$C$TASK$SUPER$CNT) + 1 then
( CPU B supervisory task has executed and should have set
PRB(PB_B$C$TASK$SUPER$CNT) = QRB(QB_C$B$TASK$SUPER$CNT) + 1 )
if PRB(PB_B$C$TASK$SUPER$CNT) <> QRB(QB_C$B$TASK$SUPER$CNT)+1 then
Send the error code "FCN 8.11 004"
Command the CPU C watchdog to reset CPU C, CPU D and CPU E.
Command the CPU C watchdog to turn off the safe bus current.
(Please refer to "How the safe bus is connected" in the
description of FCN 8.10.)
QRB(QB_C$B$TASK$SUPER$CNT) = PRB(PB_B$C$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* The CPU B software is not executing correctly.
* The CPU B RAM, IC6 on the BM CPU board K11354 is broken.
* CPU B, IC2 on the memory bank board K13614 is broken.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001

FCN 8.11 005 CPU C WATCHDOG REPLY ERROR [F,T,D,S]
General description of conditions for occuring:
FCN 8.11 tried to trig the watchdog, but the watchdog did not reply
correctly.

Technical description of conditions for occuring:
FCN 8.11 tried to trig the CPU C watchdog IC73 on the FM CPU board
K11303. The watchdog reply was not one unit greater than the last
watchdog reply.

Some possible explanations why the error has occured:
* The CPU C watchdog, IC73 on the FM CPU board K11303 is broken.
* The CPU C RAM, IC96 on the FM CPU board K11305 is broken.

FCN 8.11 006 PROM ERROR CPU C IC89 ON THE FM CPU BOARD [F,T,D,S]
General description of conditions for occuring:
The checksum calculation of the PROM IC89 on the FM CPU board failed.

Technical description of conditions for occuring:
FCN 8.11 calculated the checksum for the CPU C PROM IC89 on the FM CPU
board K11305. It differed from the checksum that was stored in that
PROM.

Some possible explanations why the error has occured:
* The PROM IC89 on the FM CPU board K11305 is broken.

FCN 8.12, CPU D SUPERVISORY TASK (CPU D)
Purpose:
* Supervises every 200 ms that all parts of the CPU D software is
executing within certain time intervalls. (task supervision) Indicates
on the LEDS V27 - V41 on the FM CPU board if some part of the software
has executed too late or too early. (Please refer to "INDICATION ON
LEDS FOR CPU D IN FM100 / FM102" at the beginning of this document.)
Stops all the pumps in the fluid monitor, turns off the heaters and
closes all the valves at such error conditions.
* Supervises every 200 ms that the CPU A supervisory task, FCN 8.09 has
been executing correctly within a certain time.
* Supervises every 200 ms that the CPU D state machine has been
executing within a certain time. Indicates on the LEDS V27 - V41 on
the FM CPU board if it has not been executing. Stops all the pumps in
the fluid monitor, turns off the heaters and closes all the valves at
such error conditions.
* Calculates the checksums of the CPU D PROMs when CPU D is not doing
anything else.

How the CPUs are connected:
CPU A ===== CPU B ===== CPU C ===== CPU D (physical connections)
----> ----> (logical connections)
<---- <----
---------------------------->
<----------------------------
Example: CPU C is physically connected to CPU B and to CPU D.
CPU C is logically connected to CPU B.
A message from CPU C to CPU D is sent as follows:
From C to B, from B to A, from A via B and C to D.

Note! Sometimes the 8.12 errors can only be observed in the diagnostics
error buffer!

FCN 8.12 001 CPU A SUPERVISORY TASK TIME OUT [F,T,D,S]
General description of conditions for occuring:
FCN 8.12 can not detect that the CPU A supervisory task, FCN 8.09 has
been executing within a certain time.

Technical description of conditions for occuring:
do every 200 ms:
if FRB(FB_D$A$TASK$SUPER$CNT) = BRB(BB_A$D$TASK$SUPER$CNT) + 1 then
( CPU A supervisory task has NOT executed )
Timeout counter = Timeout counter + 1
if Timeout counter > PB(EPB_A$TASK$TO$HL) then
Send the error code "FCN 8.12 001"
else
( CPU A supervisory task has executed and has set
BRB(BB_A$D$TASK$SUPER$CNT) = FRB(FB_D$A$TASK$SUPER$CNT) + 1 )
Timeout counter = 0
FRB(FB_D$A$TASK$SUPER$CNT) = BRB(BB_A$D$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* Hardware disturbances in the communication between CPU B and CPU C.
Refer to the explanation of FCN 8.09 001 for further information.
* The CPU A software is not executing correctly.
* The CPU B software is not executing correctly.
* The CPU C software is not executing correctly.
* Communication hardware between CPU A and CPU B is broken or badly
connected. The error code FCN 8.12 001 would not have appeared if the
hardware was completely broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* Communication hardware between CPU B and CPU C is broken or badly
connected. The error code FCN 8.12 001 would not have appeared if the
hardware was completely broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* Communication hardware between CPU C and CPU D is broken or badly
connected. The error code FCN 8.12 001 would not have appeared if the
hardware was completely broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* CPU A hardware is broken or badly connected. The error code
FCN 8.12 001 would not have appeared if the hardware was completely
broken during the function checks.
> IC9, J5, IC5 on the BM CPU board K11355.
> The watchdog, IC36 on the BM CPU board K11354.
> All circuits that are connected to the CPU A data bus (ADMx) on the
BM CPU board.
* CPU B hardware is broken or badly connected. The error code
FCN 8.12 001 would not have appeared if the hardware was completely
broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.
* CPU C hardware is broken or badly connected. The error code
FCN 8.12 001 would not have appeared if the hardware was completely
broken during the function checks.
Refer to the explanation of FCN 8.09 001 for further information.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001.

FCN 8.12 002 CPU A SUPERVISORY TASK COUNT UP ERROR [F,T,D,S]
General description of conditions for occuring:
FCN 8.12 detected that the CPU A supervisory task, FCN 8.09 had been
executing, but that the variable BRB(BB_A$D$TASK$SUPER$CNT) had an
incorrect value. The CPU A supervisory task should have updated this
variable correctly.

Technical description of conditions for occuring:
do every 200 ms:
if FRB(FB_D$A$TASK$SUPER$CNT) <> BRB(BB_A$D$TASK$SUPER$CNT) + 1 then
( CPU A supervisory task has executed and should have set
BRB(BB_A$D$TASK$SUPER$CNT) = FRB(FB_D$A$TASK$SUPER$CNT) + 1 )
if BRB(BB_A$D$TASK$SUPER$CNT) <> FRB(FB_D$A$TASK$SUPER$CNT)+1 then
Send the error code "FCN 8.12 002"
FRB(FB_D$A$TASK$SUPER$CNT) = BRB(BB_A$D$TASK$SUPER$CNT) + 1

Some possible explanations why the error has occured:
* The CPU A software is not executing correctly.
* The CPU A RAM, IC84 on the BM CPU board K11355 is broken.
* CPU A, IC9 on the FM CPU board K11355 is broken.

Some hints of what to do if the error occurs:
Please refer to the hints for FCN 8.09 001.

FCN 8.12 003 PROM ERROR CPU D IC105 [F,T,D,S]
General description of conditions for occuring:
The checksum calculation of the PROM IC105 failed.

Technical description of conditions for occuring:
FCN 8.12 calculated the checksum for the CPU D PROM IC105 on the FM
CPU board K11301. It differed from the checksum that was stored in
that PROM. (IC105 corresponds to the addresses 20000H-3FFFFH)

Some possible explanations why the error has occured:
* The CPU D PROM IC105 is broken.

FCN 8.12 004 PROM ERROR CPU D IC80 [F,T,D,S]
General description of conditions for occuring:
The checksum calculation of the PROM IC80 failed.

Technical description of conditions for occuring:
FCN 8.12 calculated the checksum for the CPU D PROM IC80 on the FM
CPU board K11301. It differed from the checksum that was stored in
that PROM. (IC80 corresponds to the addresses E0000H-FFFFFH)

Some possible explanations why the error has occured:
* The CPU D PROM IC80 is broken.

DAC logging (CPU A) (funnction removed).

FCN 8.13 000 = Removed.
FCN 8.13 001 = Removed. Command type error.
FCN 8.13 002 = Removed. Type error.

DAC logging (CPU B) (function removed).

FCN 8.14 001 = Removed.

DAC logging (CPU C) (function removed).

FCN 8.15 001 = Removed.

DAC logging (CPU D) (function removed).

FCN 8.16 001 = Removed. Command type error.
FCN 8.16 002 = Removed. Type error.

External logging opcom traco (CPU A).

FCN 8.18 000 = Case error.

External logging blood traco. (CPU A).

FCN 8.19 000 = Case error.

External logging (CPU B).

FCN 8.20 000 = Case error.

External logging (CPU C).

FCN 8.21 000 = Case error.

External logging (CPU D).

FCN 8.22 000 = Case error.

Conductivity and temperature supervision (CPU D).

FCN 8.25 000 = Case error.

FCN 8.25 001 = FRI(FI_COND) and PRI(PI_COND$2$G) differ more
than 0.7 mS/cm.

FCN 8.25 002 = FRI(FI_TEMP) - PRI(PI_TEMP$B) > 3 deg or < -0.5 deg.
Removed in PROM 3.40 and higher.

FCN 8.25 003 = FRI(FI_TEMP$A) - PRI(PI_TEMP$B) > 3 deg or < -0.5 deg.
Removed in PROM 3.40 and higher.

FCN 8.25 004 = FRI(FI_TEMP) - FRI(FI_TEMP$A) > 1.5 deg or < -0.5 deg.
Removed in PROM 3.40 and higher.

FCN 8.25 005 = FRI(FI_TEMP) - FRI(FI_TEMP$A) > 3 deg or < -0.5 deg.
Removed in PROM 3.40 and higher.

FCN 8.25 006 = PRI(PI_TEMP$B) < 41 deg. Temp should be higher.
Only valid during disinfection.

FCN 8.25 007 = FRI(FI_TEMP) - PRI(PI_TEMP$B) > 3 deg or < -1 deg.
Removed in PROM 3.90 and higher.

FCN 8.25 008 = FRI(FI_TEMP$A) - PRI(PI_TEMP$B) > 3 deg or < -1 deg.

FCN 8.25 009 = FRI(FI_TEMP) - FRI(FI_TEMP$A) > 1.5 deg or < -1 deg.
Only valid during acetate mode.

FCN 8.25 010 = FRI(FI_TEMP) - FRI(FI_TEMP$A) > 3 deg or < -1 deg.
Only valid during bicarbonate mode.

FRI(FI_TEMP) = Heating vessel temperature.
FRI(FI_TEMP$A) = Conductivity cell A temperature. (small cell.)
PRI(PI_TEMP$B) = Conductivity cell B temperature.
FRI(FI_COND) = Total conductivity, control system.
FRI(FI_COND$A) = Acid conductivity, control system. (small cell.)
PRI(PI_COND$2$G)= Total conductivity protective system.

System EEPROM handling. (CPU A).

FCN 8.26 000 = Case error.
FCN 8.26 001 = CRC error boolean segment (1)
FCN 8.26 002 = CRC error byte segment (2)
FCN 8.26 003 = CRC error word segment (3)
FCN 8.26 004 = CRC error integer segment (4)
FCN 8.26 005 = CRC error real segment (5)
FCN 8.26 006 = CRC error segment (6)
FCN 8.26 007 = CRC error segment (7)
FCN 8.26 008 = CRC error segment (8)
FCN 8.26 009 = Illegal command parameter
FCN 8.26 010 = Illegal segment parameter
FCN 8.26 011 = Illegal boolean length parameter
FCN 8.26 012 = Illegal byte length parameter
FCN 8.26 013 = Illegal word length parameter
FCN 8.26 014 = Illegal integer length parameter
FCN 8.26 015 = Illegal real length parameter
FCN 8.26 016 = Illegal seg 6 length parameter
FCN 8.26 017 = Illegal seg 7 length parameter
FCN 8.26 018 = Illegal seg 8 length parameter
FCN 8.26 019 = CNTRL program request time-out
FCN 8.26 020 = Non-owned CNTRL program release
FCN 8.26 021 = Write error boolean segment (1)
FCN 8.26 022 = Write error byte segment (2)
FCN 8.26 023 = Write error word segment (3)
FCN 8.26 024 = Write error integer segment (4)
FCN 8.26 025 = Write error real segment (5)
FCN 8.26 026 = Write error segment (6)
FCN 8.26 027 = Write error segment (7)
FCN 8.26 028 = Write error segment (8)
FCN 8.26 029 = Illegal segment reference in SAFE-area
FCN 8.26 030 = Boolean write src/dest verify error
FCN 8.26 031 = Byte write src/dest verify error
FCN 8.26 032 = Word write src/dest verify error
FCN 8.26 033 = Integer write src/dest verify error
FCN 8.26 034 = Real write src/dest verify error
FCN 8.26 035 = Boolean transient array write error
FCN 8.26 036 = Byte transient array write error
FCN 8.26 037 = Word transient array write error
FCN 8.26 038 = Integer transient array write error
FCN 8.26 039 = Real transient array write error
FCN 8.26 040 = Boolean transient array write error
FCN 8.26 041 = Byte transient array write error
FCN 8.26 042 = Word transient array write error
FCN 8.26 043 = Integer transient array write error
FCN 8.26 044 = Real transient array write error
FCN 8.26 045 = Illegal key for write inhibit unlock request
FCN 8.26 046 = Unlock attempt on unlocked write inhibit protection

System recovery handling. (CPU A).

FCN 8.27 000 = Case error. Illegal program control parameter.
FCN 8.27 001 = Index table error.
Recovery data bank longer then the defined
recovery data.
Cause: 1. Program error.
2. Faulty safe memory.

FCN 8.27 002 = No correct recovery bank found.
Both recovery data banks has CRC error.
Cause: 1. Recovery was active when new proms
was instaled.
2. Power failure before a complete
history collection.
3. Faulty safe memory.

FCN 8.27 003 = Incorrect CRC (checksum) of reset request.
Indicates that the content of the battery-backed
RAM has been distorted either by means of a dis-
turbance or a component failure.

System recovery handling. (CPU D).

FCN 8.29 000 = Case error..Illegal program control parameter.
FCN 8.29 001 = Index table error.
Recovery data bank longer then the defined
recovery data.
Cause: Program error.
FCN 8.29 002 = No correct recovery bank found.
FCN 8.29 003 = Cpu D recovery data too long for communication.

FCN 8.30 SXX = Task stack overflow where XX is:

0 = INIT TASK STACK
1 = COM TASK STACK
2 = ADC TASK STACK
3 = AOTRC TASK STACK
4 = ABTRC TASK STACK
5 = SERRLG TASK STACK
6 = FCN TASK 0 STACK
7 = FCN TASK 1 STACK
8 = FCN TASK 2 STACK
9 = ASUPERTASKHIGH STACK
10 = ASUPERTASKLOW STACK
11 = INFODISP TASK STACK
12 = FCN TASK 3 STACK
13 = RECOVERY TASK STACK
14 = AATRC TASK STACK
15 = AERRLG TASK STACK

IEC CONTROL function (CPU A)

FCN 8.35 000 = Case error..Illegal program control parameter.

FCB 8.35 000 = Instruction test of CPU A failed.
FCB 8.35 001 = Variable outside IEC-limits not confirmed or
variable inside IEC-limits uncorrectly confirmed.

SYSTEM RECOVERY function (CPU B)

FCN 8.36 000 = Case error..Illegal program control parameter.
FCN 8.36 001 = No correct memory bank found.

External F logging. This function redirects logging blocks from
GSS port (ASYDRV) to FCN822 in CPU D, and vice versa.

FCN 8.37 ... = no errors defined.

Description over functions used in different function tasks. CPU A.
From PROM 3.52A
AFCN 0 = 1 SEC TASK (priority = 80)

FCN$3$45 Remaining time calculation. (CPU A).
FCN$3$46 Passed time calculation. (CPU A).
FCN$3$47 Non-diffusion time (bypass time) calculation. (CPU A).
FCN$3$48 UF volume predict. (CPU A).
FCN$3$49 TMP - UF transition. (CPU A).
FCN$3$08 UF gain control (CPU A)
FCN$3$10 Access code control. (CPU A).
FCN$3$52 Fluid bypass (DIVA bus). (CPU A).
FCN$3$62 Heparin auto stop limit. (CPU A).
FCN$3$63 Linear transducer calibration calculation. (CPU A).
FCN$3$64 Real time calculation. (CPU A).
FCN$3$67 Internal support default set function
FCN$3$68 BATTERY TEST FUNCTION
FCN$3$71 Conductivity function. (CPU A).
FCN$3$74 Bicarb. time function. (CPU A).
FCN$3$80 Conductivity profiling function.
FCN$3$82 UF equation and UF profiling.
FCN$4$17 Service strap supervision.
FCN$5$02 Heparin flow control. (CPU A).
FCN$5$15 BM fan function. (CPU A).
FCN$8$35 IEC-control. (CPU A).
LOCAL$LOGGING$FCN
LOGG$DAC$FCN
CHECK$STACKS

AFCN 1 = 300 ms TASK (priority = 90)

FCN$2$00 Arterial pressure guard supervision. (CPU A).
FCN$2$05 ARTERIAL TIDAL VOLUME SUPERVISION
FCN$2$07 Arterial pump supervision function. CPU A).
FCN$2$08 Venous pump supervision function. CPU A).
FCN$2$10 Optional pressure function. (CPU A).
FCN$2$11 Presure transducer supervision.
FCN$2$12 HDF supervision. (CPU A).
FCN$5$14 Blood flow and volume measurement. (CPU A).
FCN$3$53 Venous pressure auto alarm limits adjust. (CPU A).
FCN$3$54 Extra pressure auto alarm limits adjust. (CPU A).
FCN$3$55 TMP auto alarm limits adjust. (CPU A).
FCN$3$59 Machine off. (CPU A).
FCN$3$65 Select chemical mode function
FCN$4$28 Pump segment control
FCN$8$33 Data conversion

AFCN 2 = 100 ms TASK (priority = 210)

FCN$2$03 level detector
FCN$2$04 priming detector
FCN$5$13 blood flow calculation

AFCN 3 = 300 ms TASK (priority = 50)

FCN$3$66; parallell EEPROM
FCN$3$70; Preset calculation
FCN$3$72; Concentrate preset mode and alternative
FCN$4$16; I2C (serial) EEPROM

INFO DISP = 300 ms TASK (priority = 95)

FCN$3$09; information display function
REMOTE$DISPLAY$FCN

RECOVERY = 200 ms TASK (priority = 70)

FCN$8$27; recovery function

AOTRCT = 200 ms TASK (priority = 150)

REMOTE$CONTROL$FCN (if configured)
FCN$3$58 Manual data input. (CPU A).
FCN$3$57 Keyboard input. (CPU A).
FCN$3$61 Blood potentiometer data input. (CPU A).
REMOTE$FCN remote panel display
TRANS$AOTRC
TRANS$AOSTRC
TRANS$APTRC
FCN$3$73 Attention function.
FCN$3$79 Profiling parameter set function.
EXT$O$LOGGING$FCN;

ABTRCT = 300 ms TASK (priority = 155)

FCN$2$01 Extra pressure supervision. (CPU A).
FCN$2$02 Venous pressure supervision. (CPU A).
FCN$5$12 Single needle generator. (CPU A).
TRANS$ABTRC
TRANS$ABSTRC
FCN$4$03 Clamp controller. (CPU A).
FCN$5$00 Arterial pump control. (CPU A).
FCN$5$01 Venous pump control. (CPU A).
TMP$FCN
FCN$3$BAR
FCN$3$LMP
FCN$3$56 Time display. (CPU A).
FCN$3$60 Main buzzer control. (CPUA).
EXT$B$LOGGING$FCN;

AATRCT = 400 ms TASK (priority = 100)

TRANS$AOATRC

Description over functions used in different function tasks. CPU A.
Before 3.52A but after PROM 3.20
AFCN 0 = 1 SEC TASK

FCN$3$45 Remaining time calculation. (CPU A).
FCN$3$46 Passed time calculation. (CPU A).
FCN$3$47 Non-diffusion time (bypass time) calculation. (CPU A).
FCN$3$48 UF volume predict. (CPU A).
FCN$3$49 TMP - UF transition. (CPU A).
FCN$3$08 UF gain control (CPU A)
FCN$3$10 Access code control. (CPU A).
FCN$3$52 Fluid bypass (DIVA bus). (CPU A).
FCN$3$62 Heparin auto stop limit. (CPU A).
FCN$3$63 Linear transducer calibration calculation. (CPU A).
FCN$3$64 Real time calculation. (CPU A).
FCN$3$67 Internal support default set function
FCN$3$68 BATTERY TEST FUNCTION
FCN$3$71 Conductivity function. (CPU A).
FCN$3$80 Conductivity profiling function.
FCN$4$17 Service strap supervision.
FCN$5$02 Heparin flow control. (CPU A).
FCN$5$15 BM fan function. (CPU A).
LOCAL$LOGGING$FCN
LOGG$DAC$FCN
CHECK$STACKS

AFCN 1 = 300 ms TASK

FCN$2$00 Arterial pressure guard supervision. (CPU A).
FCN$2$05 ARTERIAL TIDAL VOLUME SUPERVISION
FCN$2$07 Arterial pump supervision function. CPU A).
FCN$2$08 Venous pump supervision function. CPU A).
FCN$2$10 Optional pressure function. (CPU A).
FCN$2$11 Presure transducer supervision.
FCN$2$12 HDF supervision. (CPU A).
FCN$5$14 Blood flow and volume measurement. (CPU A).
FCN$3$53 Venous pressure auto alarm limits adjust. (CPU A).
FCN$3$54 Extra pressure auto alarm limits adjust. (CPU A).
FCN$3$55 TMP auto alarm limits adjust. (CPU A).
FCN$3$59 Machine off. (CPU A).
FCN$3$65 Select chemical mode function
TMP$FCN

AFCN 2 = 100 ms TASK

FCN$2$03
FCN$5$13

AFCN 3 = 300 ms TASK

FCN$3$66;
FCN$3$70; Preset calculation
FCN$3$72; Concentrate preset mode and alternative
FCN$4$16;

AOTRCT = 300 ms TASK

FCN$3$BAR
FCN$3$LMP
FCN$3$56 Time display. (CPU A).
FCN$3$60 Main buzzer control. (CPUA).
FCN$3$58 Manual data input. (CPU A).
FCN$3$57 Keyboard input. (CPU A).
FCN$3$61 Blood potentiometer data input. (CPU A).
TRANS$AOTRC
TRANS$AOSTRC
TRANS$APTRC
FCN$3$73 Attention function.
FCN$3$79 Profiling parameter set function.
REMOTE$DISPLAY$FCN Remote display function FCN377. (CPU A).

ABTRCT = 300 ms TASK

FCN$2$01 Extra pressure supervision. (CPU A).
FCN$2$02 Venous pressure supervision. (CPU A).
FCN$5$12 Single needle generator. (CPU A).
TRANS$ABTRC
TRANS$ABSTRC
FCN$4$03 Clamp controller. (CPU A).
FCN$5$00 Arterial pump control. (CPU A).
FCN$5$01 Venous pump control. (CPU A).

Before PROM 3.20
Description over functions used in different function tasks. CPU A.
FCN 0
-----
FCN$3$45
FCN$3$46
FCN$3$47
FCN$3$48
FCN$3$49
FCN$3$58
FCN$3$08
FCN$3$10
FCN$3$BAR
FCN$3$LMP
FCN$3$56
FCN$3$57
FCN$3$52
FCN$3$53
FCN$3$54
FCN$3$55
FCN$3$59
FCN$3$60
FCN$3$61
FCN$3$62
FCN$3$63
FCN$4$17
LOCAL$LOGGING$FCN

FCN 1
-----
FCN$2$00
FCN$2$01
FCN$2$02
FCN$2$04
FCN$3$64
FCN$4$03
FCN$5$00
FCN$5$01
FCN$5$02
FCN$5$12
FCN$5$14
FCN$5$15
TMP$FCN

FCN 2
-----
FCN$2$03
FCN$5$13

I2C BUS ID
----------

BUS ADR, LOCAL EEPROM ADDRESS, TYPE OF ERROR
FOR EXPLANATION OF TYPE OF ERROR REFER TO THE CORRESPONDING
FUNCTIONS

X Y Z
-------

0 0 Z MAIN BOARD CPU D.
0 1 Z HPG. HIGH PRESSURE GUARD.
0 2 Z UFM. UF-CELL.
0 3 Z C1C. CONDUCTIVITY CELL No 1. CPU D. TEMPERATURE
INCLUDED.
0 4 Z PH. PH-CELL.
0 5 Z AU0. AUXILLIARY CHANNEL NO 0.

1 1 Z THV. TEMPERATURE TRANSDUCER IN HEATING VESSEL.
1 2 Z C2C. CONDUCTIVITY CELL No 2. CPU D.
1 3 Z PFO. PUMP FLOW OUT PRESSURE.
1 4 Z PFL. DEGASSING PRESSURE.
1 5 Z FLM. NOT USED.
1 6 Z PFI. PUMP FLOW IN PRESSURE.

2 0 Z MAIN BOARD CPU C.
2 1 Z C2G. CONDUCTIVITY CELL No 2. CPU C. TEMPERATURE
INCLUDED.
2 2 Z AUP. AUXILLARY CHANNEL. CPU C.
2 3 Z BLD. BLOOD LEAK DETECTOR.
2 4 Z SAG. SAFETY BYPASS GUARD.
2 5 Z PD1. DIALYSIS PRESSURE.

3 0 Z MAIN BOARD CPU A.
3 2 Z EXTRA PRESSURE.
3 3 Z VENOUS PRESSURE.
3 4 Z OPTIONAL PRESSSURE.
3 CMOS CLOCK

4 0 Z MAIN BOARD CPU B.

x WATCH DOG CPU B.
x WATCH DOG CPU C.

* A K 1 0 0 A T T E N T I O N E X P L A N A T I O N *

Fluid tubes not in safety bypass.

1. Fluid tubes not coupled to safety bypass.
2. Blood leak cover not tightend enough.
3. Air is leaking into the fluid path somewhere else.
4. A valve is NOT CLOSED when it should. Check DIVA, BYVA, ZEVA.
5. A valve is CLOSED when it should not. Check TAVA, DIVA.
6. Fluid "pump in" is filled with air and can't create any negative
pressure.
7. A bad fluid pump.
8. A bad pressure transducer. PSAGS or PD.

Insufficient water supply.

1. Water supply is not connected.
2. A filter outside AK 100 is occluded.
3. The RO unit can not deliver all the water that AK 100 needs.
4. Inlet water valve does not open.
5. The safe bus has closed the inlet water valve.
6. Broken inlet water valve.
7. Float valve in heating vessel does not open.

* A K 1 0 0 I N C O R R E C T O P E R A T I O N *

Unstable conductivity.

1. The ultrasonic transducer in the degassing chamber is not
working properly. Check the level with internal logging. It is
measured in 1/10 mm and should be between 48.0 and 52.0 mm. The
signal can also be checked with an oscilloscope on R 139 and
should be above 1.5 volt. This check is NOT valid during heat
disinfection.
2. Air coming in through the concentrate sticks.
3. Degassing pump oscillating.