Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
100 views5 pages

IDT GPC Error

Uploaded by

rostik gromyk
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
100 views5 pages

IDT GPC Error

Uploaded by

rostik gromyk
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

PHILIPS MEDICAL SYSTEMS

Mx8000 IDT Systems

GPC Error Messages

May 2002

ALL PAGES OF THIS DOCUMENT CONTAIN PROPRIETARY AND CONFIDENTIAL INFORMATION OF PHILIPS MEDICAL SYSTEMS
(CLEVELAND), INC. THE DOCUMENTS ARE INTENDED FOR CURRENT PHILIPS MEDICAL SYSTEMS’ PERSONNEL OR ARE LICENSED TO
PHILIPS MEDICAL SYSTEMS’ CUSTOMER FOR USE BY THE CUSTOMER'S IN-HOUSE SERVICE EMPLOYEE ON EQUIPMENT LOCATED AT THE
CUSTOMER'S DESIGNATED SITE. COPYING, DISCLOSURE TO OTHERS OR OTHER USE IS PROHIBITED WITHOUT THE EXPRESS WRITTEN
AUTHORIZATION OF PHILIPS MEDICAL SYSTEMS’ LAW DEPARTMENT. REPORT VIOLATIONS OF THESE REQUIREMENTS TO PHILIPS
MEDICAL SYSTEMS’ LAW DEPARTMENT, HIGHLAND HEIGHTS, OHIO

Service Publications, Philips Medical Systems (Cleveland) Inc., Highland Hts., OH


44143
© 2002 All rights reserved under the copyright laws of the United States
P 30 Design Specification
GPC

1.1.1 Error List


The GPC errors are shown in the following table:

byte0 byte1 byte2 byte3 description parameter


E 10 03 10 GPC_INTERNAL_ERROR: Par1, Par2 :
This is a GPC internal error or • 1, TimerStartValue :
diagnostic message. It will not Too much internal tasks started
influence correct GPC operation. • 2, TaskIndex :
Task [TaskIndex] is called with disabled interrupts
(EAL=0)
• 3, Layer2Index :
Layer2 communication index is greater than 1
• 4, x : n.a.
• 5, x : n.a.
• 6, ComReceiveErrorBits :
Low Level communication error bits :
0x10 : BREAK error
8 : framing error
4 : parity error
2 : Overflow error
• 7, ComError :
Layer2 communication error of COM1
• 8, ComError :
Layer2 communication error of COM2
• 9, x : n.a.
• 10, x : n.a.
• 11, BufferQueueLength :
The Transmission buffer for the serial panel
communication has overflowed.
• 12, x : n.a.
• 13, IIR-Register of 16450 (EPLD) :
The ISR of the 16450_EPLD was terminated with a
stuck IIR-Register
• 14, KeyCode (only MARCONI):
An illegal Light Marker KeyCode was detected
• 15, wrong state :
A internal state machine has detected an illegal
state (source line line number in Debug
Parameters)

E 10 2 12 KEY_MAT_ERROR: Par 1, Par 2 hold the bit mask of the sticking key(s) :
Sticking Key or key is pressed
during the initialization time ( 10 sec) Par 1 :
in INIT and RESET WORKING on
1 KEY_TILT_POS
any of the following panels :
• Control-Box 2 KEY_TILT_NEG
• Service Panel (on GPC board) 4 KEY_LM_TOGGLE
• Rear Panel 8 KEY_LM_DIFF
• Footswiches
0x10 KEY_PATIENT_RELOAD
• Joystick
0x20 KEY_HORI_ZERO

Par 2 :
1 KEY_HOR_IN
2 KEY_HOR_IN_FAST
4 KEY_HOR_IN_STEP
8 KEY_HOR_OUT
0x10 KEY_HOR_OUT_FAST
0x20 KEY_HOR_OUT_STEP
0x40 KEY_VER_UP
0x80 KEY_VER_DOWN

E 10 2 13 PANEL1_ERROR Par 1 :
If the connection to the panel1 is • 0x20 :
corrupted, this error is send. An illegal Telegram was received from the Panel
(wrong checksum, wrong identifier, wrong frame...)
• 0x40 :
Line Check timeout , Panel does not respond during
P 30 Design Specification
GPC

byte0 byte1 byte2 byte3 description parameter


the initialsation period of 20 sec
• 0x60 :
Key Demand timeout, the Panel did not respond in
time (approx. 450 ms) to a Key Demand telegram of
the GPC
• 0xC0 :
to much Errors, panal will be marked as defect, no
more panel operation until INIT or RESET:

Par 2:
<ErrorCounter> is incremented ( may be 1...3 )

E 10 2 14 PANEL2_ERROR Par 1 :
If the connection to the panel 2 is • 0x20 :
corrupted, this error is send. An illegal Telegram was received from the Panel
(wrong checksum, wrong identifier, wrong frame...)
• 0x40 :
Line Check timeout , Panel does not respond during
the initialsation period of 20 sec
• 0x60 :
Key Demand timeout, the Panel did not respond in
time (approx. 450 ms) to a Key Demand telegram of
the GPC
• 0xC0 :
to much Errors, panal will be marked as defect, no
more panel operation until INIT or RESET:

Par 2:
<ErrorCounter> is incremented ( may be 1...3 )

E 10 0 15 XRAY_ERROR: n.a.
If the signal Xray is active during
state INIT, this error is send.
E 10 0 16 WRONG_SLICE_DIFF n.a.
The slice difference in the init table
is outside bounds [-20010,0[ or the
speed for slice difference is outside
bounds ]5, 2000[ .
E 10 0 17 WRONG_SCAN_NUMBER Par 1, Par 2:
• 0x91, <Scan Number > :
The Scan Number in the SL is greater than 0x25.
• 0x92, <Scan Number > :
The Scan Number in the SL is not found in the
cycle table
• 0x94, <ScanExecuteNr> :
The SE argument does not match to the SL
argument (Scan Number)
E 10 0 18 WRONG_KOLLISION_TABLE n.a.
The values contained in the collision
table are not correct, if table is sent
in RESET WORKING or later.
E 10 2 19 PROCESS_ERROR Parameter 1 - bits:
A position is selected, while a move • 0x80 : horizontal axis
is active or • 0x40 : vertical axis
a GO-command is received during • 0x20 : tilt axis
actual movement
Parameter 2 - bits:
• 0x02 : SELECT_DURING_MOVE (A position is
selected, while a move is active)
• 0x01 : GO_DURING_MOVE (no GO-command
allowed during actual movement)

E 10 0 1A MOVE_ERROR Parameter 1 - bits:


A CAN component starts a move in • 0x80 : horizontal axis
a direction which is not allowed. • 0x40 : vertical axis
• 0x20 : tilt axis
Parameter 2 - bits:
• 0x04 : WRONG_MOVE_IN_STATE_1 (movement
is disabled by mode table switch4)
• 0x08 : WRONG_MOVE_IN_STATE_2 (auto
movement not allowed)
• 0x10 : WRONG_MOVE_IN_STATE_3 (movement
P 30 Design Specification
GPC

byte0 byte1 byte2 byte3 description parameter


detected in illegal state )
• 0x20 : NO_SELECT_STOP (Selected position
reached, but not stopped)
• 0x40 : KOLLISION_MOVE_1 (Start of movement
disabled due to collision test)
• 0x80 : KOLLISION_MOVE_2 (Movement not
allowed due to collision test)

E 10 0 1B POSITION_ERROR n.a.
Wrong direction in running position
during movement
E 10 0 1C SELECTPOS_ERROR n.a.
The direction and position in a
received selected position command
do not correspond.
E 10 0 1D TIMEOUT_ERROR Parameter 1 - bits:
During the movement GPC detects • 0x80 : horizontal axis
a timeout between movement- • 0x40 : vertical axis
commands.(only if a movement • 0x20 : tilt axis
controller is not in service mode) • 0x10 : GO-RUN-Timeout
• 0x08 : RUN-RUN-Timeout
• 0x04 : BREAK-HALT-Timeout
E 10 2 1E KOLLISION_ERROR n.a.
The GPC detects a violation of a
movement against the actual
collision diagram.
E 10 0 1F PANELS_DEFECT Par 1 : last error code of Panel 1
Both gantry panels are defect or not Par 2 : last error code of Panel 2
connected.
E 10 2 20 TABLE_WARNING Par 1, Par 2 :
Any of the tables T16, T1B or T1C • 0x0B, 1 :
was not loaded correctly in a state Slice Table (T1B) corrupted: Slice Diff < -20010
before RESET. This Table is • 0x0B, 2 :
requested again in state RESET. Slice Table : Slice Diff is positive
• 0x0B, 3 :
Slice Table : SLice Speed > 2000
• 0x0B, 4 :
Slice Table : Slice Speed < 5
• 0x0C , 1..7 :
Speed Table (T1C) corrupted
• 0x06 , 1..5 :
Collision Table (T16) corrupted
E 10 0 21 ILLEGAL_GO_FROM_HOST: Parameter 1:
A Go – Comand from ICS was • 2:
received and currently no position is Tilt (GT from ICS )
selected. • 3:
Horizontal ( GH from ICS )
E 10 0 22 SPEED_TABLE_ERROR: Parameter 1:
Table T1C was not loaded correctly • 1 : A wrong speed
in state >= RESET. • 2 : Illegal panel type
• 3 : Step time threshold < 50 ms
• 4 : Horizontal StepWidth is not [0,250]
• 5 : Vertical StepWidth is not [0,250]
• 6 : Tilt StepWidth is not [0,10] (0° , 5°)
• 7 : UnloadMode is not [0,1]
E 10 0 23 MODE_TABLE_ERROR: Par 1 :
A corrupted mode table is received 0x10 : TF0
(corrupted because its length is not 0x12 : TF2
a multiple of 13)
Par 2: Number of received table fragments
E 10 0 25 STOP_BY_GPC: n.a.
GPC has opened the stop circuit.
E 10 0 26 ERR_FLEXLOAD Par 1 : internal error code
The load procedure of the FLEX
circuit (FPGA) on the GPC board Par 2 : n.a.
has failed
E 10 0 27 AD-CONVERSION: Par 1 :
The AD-conversion of the Supply • 0: 2.5 V supervision error
voltages on the MCB2 has failed • 1: 3.3 V supervision error

Par 2 : Error Code of AD Conversion (internal)


P 30 Design Specification
GPC

byte0 byte1 byte2 byte3 description parameter


E 10 0 28 ERR_SUPPLY_VOLTAGE_SUPER Par 1 :
VISION • 0: the 2.5 V is corrupted
Any of the supply voltage(s) of the • 1: the 3.3 V is corrupted
GPC board is corrupted
Par 2 :
• 0 : voltage is below 90 % of nominal value
• 1 : voltage is above 110% of nominal value
E 10 2 29 PANEL_ERRTG: Par 1 : Error Code of Panel (copied from telegram)
An error telegram of the serial panel
is received Par 2 : Identifier of telegram source:
• 0x80: PDIS
• 0x81: Key Panel 1
• 0x82: Key Panel 2
E 10 0 30 SEND_QUEUE_FULL n.a.
Internal GPC-Error : The send
queue for CAN-objects is full.
E 10 0 31 STOP_OPEN: n.a.
Stop_report loop is open in state
RESET-WORKING
E 10 0 32 YS_ERROR: n.a.
An YS-command (Lifecheck) was
not received within the specified time
E 10 0 33 STOP_TEST: n.a.
Is sent in Scan Execute on special
test mode (0x12 : Stop test)

Table 1 :GPC Runtime Errors

Byte 2 (Prioritity) contains the GPC default priorities. These priorities may be overwritten by the Error Table
T14, which may be sent to the GPC during TABLE_LOAD.

You might also like