Documente Academic
Documente Profesional
Documente Cultură
Forever Login
News: The Ne w (a nd im prove d) Sie m e ns X-R a y Equipm e nt Se rvice r's Te chnica l Forum . More fe a ture s, m ore
Search
inform a tion a nd m ore he lp for Sie m e ns Im a ging Equipm e nt se rvice provide rs a nd support pe rsons.
Siemens X-Ray Equipment Servicer's Technical Forum > Siemens X-Ray > ICONOS R 100 / R 200 > Error Massages Iconos R 100 ( step by step )
« previous next »
Pages: [1] PRINT
Author Topic: Error Massages Iconos R 100 ( step by step ) (Read 3733 times)
P osts: 22
Error list of XCU ( AP-ID 240 )
Internal SW-error: system call failed. A Timer or setting an event flag did not work. A function of the above mentioned task
returned a fatal error. The XCU tries to repeat the
function. If this fails, attempt will be repeated three times. If still unsuccessful the system shuts down. In this case the
hardware oftheXCU is defective. This error is fatal,
there is no work around.[/center]
Internal SW problem: error during receiving telegram. A telegramm that has been received in the dual port RAM of D320 or
D200 has released an interrupt but cannot be
read. Maybe defective D320 or D200.
Internal SW problem: error during sending telegram. This error is caused by sending an telegram while the ARCNET is busy.
If there is no positive feedback in between 1
second, the error will be logged. The telegram will then be sent a second time. There is no work around.
No function available for telegram received. An unknown telegram has been received. The function will not be
executed.[/center]
Invalid Telegram parameter. The Telegram parameter is out of range or the telegramm length anounced in telegram
mismatches the real telegram length or the parameter
in telegramm has no correspondent bit in the config data base. No work around.
The system mode, that the XCU is demanding is not confirmed by the gantry or the stand in between a timeout of 5
seconds. In particular this could be:
SIRESKOP CX: the position of the tube is not set to the selected target (e.g. the tube is pointing to a spot film device
while the wall stand has been selected by the user)
ICONOS R100: tomo mode is selected but tomo cannot be set at the gantry because tomo is not possible because the SID
is not in the position where tomo is possible
or the room height is limited below the value where tomo is allowed.
SIRESKOP SX: Another reason is, that the Spotfilm device is in park position but spot film device is selected by the user.
What to do: Put the tube manually in the correct position or select the correct SID or put the SFD in the correct position.
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
If the room height is set wrong, the service
technician must enter in service mode another value.
Internal SW problem: error during initializing telegram receive. The XCU cannot access the task processing telegrams.
There is no workaround.
Remote Service
The Remote Service Access is set to permanent access by the user. This means a service technician can login remotely
any time the X-ray system is alive.
Remote Service
The Remote Service Access is set to temporary access by the user. This means, a service technician can login remotely
as long as the system will be powered off the next
time. The next turn of the system will reset the remote acess state to denied.
Remote Service
The Remote Service Access is set to denied access by user. This means, a service technician cannot login remotely
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
XCU (AP-ID 240) error # 025
These messages (26 = OFF, 27 = ON) are displayed in order to tell the user, that he now can demonstrate the function
(audible alarm and percentage display) of the
tubeload calculator without doing a real exposure. To get this message, you have to do the following:
- Watch HU display. The HU display should be increased. For getting a feeling, how kV and mAs influences the HU display,
look on this example:
Tube: OPTITOP
Max HU: 580 000 J (= 580 kWs)
Voltage: 125 kV
mAs 400 mAs
Energy of that exposure: 125kV x 0,4 As = 50kJ.
Amount %HU: 50kJ / 580 kJ = 8,6%.
As soon as either another organ program is selected, or SS is turned on or the Telephone button is pressed a second time,
the simulation is turned off.
Now it is possible to demonstrate the tube load calculator without stressing the tube.
Remark: It is not possible to reset the calculator. If it is one heated up no matter if by real exposures or by the simulation,
you must wait the amount of time that is
necessary to cool down the tube.
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
XCU (AP-ID 240) error # 027
Remote Service
The Remote Service Access is set to temporary full access by the user. This means, a service technician can login
remotely as long as the system will be powered off the
next time. The next turn of the system will reset the remote acess state to denied. Full access means, that the service
technician is allowed to invoke the service of the
fluorospot top without assistance of the user
Remote Service
The Remote Service Access is set to permanent full access by the user. This means a service technician can login
remotely any time the X-ray system is alive. Full access
means, that the service technician is allowed to invoke the service of the fluorospot top without assistance of the user
Reconfiguration of ARCNET
ARCNET low level network has reported an error. The reset of the ARCNET (forced by any other partner in the ARCNET) has
been. This error occurs-
if an arcnet controller (D350 of FL TOP, ASU, Generator ...) has been reset by itself or because it is not responding and
has been reset by the network
The error is always created if an imaging system (Fluorospot TOP, Fluorospot Compact, RADIS) has been turned on while
the other components of the system are
already alive. The error may than occur more than once in a row.
P osts: 22
Error list of XCU ( AP-ID 240 )
---This error is equivalent to the display <55> or <56> on D320/D200 of XCU ---
Low Battery
Reason
Battery on slot CPU = SX control unit (P/N 58 95 292 only, not CPU-HD unit) is empty, not completely inserted or missing.
Action
Remove cover of XCU. Search for slot CPU, which is located on the fourth (the utmost right) slot. Look for Battery which is
a ¾ inches by 1 inch integrated circuit having
four pins. The print on the cover shows <TIMEKEEPER> and <LITHIUM BATTERY>. It is located between the four red LEDs
and the plug from the power supply, having
lots of coloured wires.
- Is a battery inserted? --> if not, look for it in the housing of the XCU. If found, insert it. The marking (white dot on
cover of battery, located on the lower left, should point
in direction of HDD/Floppy cabling) and the battery is placed over an IC on the slot CPU.
if not found order a new one. (Battery type: M4T32-BR12SH1 from ST Microelectronics (www.st.com)).
The only restriction without battery is, that the time/date is wrong. All other functions should work properly.
remove battery
- check for PINs. Are all PINs OK or is one or more broken or bended?
- is voltage OK? The voltage should be measured between the PINs separated with a small black nose. Nominal voltage is
2.8 V, voltage of a new battery is app. 3.4 V.
Replace battery is voltage is below 2.0V, malfunctions (invalid date and time settings) apply below 1.0V.
Power fail detected although the power supply has not been turned off.
This means that the power supply (AC line) has been interrupted for at least 50 ms up 1.5 sec. (After 1.5 sec the XCU
power supply has no more energy and will
terminate and cannot enter the error in the errorlog data base.)
This may be caused
by the customer by rapidly turning off and on or
by interferencies on D160 board or
by a bad emergency power supply, that requires several 10 ms to take over energy supply.
If this happens, the errorlog may show several unexplainable errors, because the components are confused. Due to power
fail for some time, the memory gets mixed, but
the power on reset will not get active because interrupt was too short.
In order to find out, whether the system is working properly, you may check power fail by unplugging X1 on D320 while
system is running. D320 should light up <F4> in ist
HEX-Display and the error 39/240 should be entered in errorlog. If not either D160 or D320/D200 or cabling is defective. For
D200 it is not easy to unplug, because X1
is also supplying the 5 V to the D200. If you want to check, you have unplug Pin 2 when system is running. (Pin 2 must be
connected during start-up)
This message is always created when the High End XCU is turned on in order to find out, whether specific errors have been
occured once or many times before the system
has been turned off. The Power on message is created when all components are alive and the system is ready (first system
selection button on the control console lights
up) or if the system does not get ready in between this time-out - after 120 seconds. Any time an imaging system (RADIS
or FL TOP or FL Comp [with the exception of FL
H, which is fast enough]) is in the current site, the 120 sec timeout will hit.
This message is always created when the service PC logs in the XCU. So you may find out, if specific errors occur only in
service mode. No error, for information only.
This message is always created when the service PC logs OUT the XCU. So you may find out, if specific errors occur only in
service mode. No error, for information only.
This means that, D200 or D320 do not detect an ARCNET carrier signal. This may be caused by many various things:
causes:
Jumper X5 in Videomed SX D16 is in position END and termination resistor at XCS.X22 of Videomed SX is fitted
Duplicate node - ID
Two ARCNET partner do have the same physical board adress. This may be caused by jumper setting. Which Partner has
the wrong ID can be checked by the tool
usrshell.exe on this SSW.
An ARCNET package could not be sent in between the timeout given by the host program and has to be repeated. This
error can be ignored. It only indicates that the
transmission took more time, than estimated by the developper of the program. If the error occurs very often in a row it
might indicate, that the controller is too busy.
This message is always created when the service PC logs in the XCU via Modem. So you may find out, if specific errors
occur only in service mode. No error, for
information only.
This message is always created when the service PC logs OUT after a REMOTE session. So you may find out, if specific
errors occur only in service mode. No error, for
information only.
XCU - FD-TASK
XCU - FD-TASK
XCU - FD-TASK
XCU - FD-TASK
XCU - FD-TASK
XCU - FD-TASK
XCU - FD-TASK
XCU - FD-TASK
XCU - FD-TASK
Acquisitions are blocked, because start up offset running. If the user tries to make an exposure during the offset
calibration this error is created and the exposure is denied.
XCU - FD-TASK
XCU - FD-TASK
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
XCU - FD-TASK
XCU - FD-TASK
XCU - FD-TASK
XCU - FD-TASK
Calibration request. The XCU requests the user to perform a calibration, because the calibration inverval has expired.
XCU - FD-TASK
XCU - FD-TASK
Exposure release is blocked, because imaging system RADIS does not send the status as ready for exposure. This may be
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
caused by serveral reasons:
- RADIS in not (yet) ready with booting --> wait for end of boot
- RADIS is in service mode --> terminate RADIS service session
- no patient selected ---> select a patient
- RADIS is suffering from an internal problem and will not release the exposure ---> check RADIS error conditions. If no
error appears, restart RADIS.
- The calculation of the last image is still in progress. ---> Wait for end of calculation
- The offset calibration is currently active ---> Waít for end of calculation
XCU - FD-TASK
Exposure release is blocked, because offset calibration is in progress ---> Wait for end of offset calibration
XCU - FD-TASK
This message indicates, that X-ray release switch has been pushed twice in between 2 secondes. For usual FD systems
do not accept several demands for exposures
in short period of time. Therefore the XCU locks the demand for seconds after the last OFF for exposure. Causes:
- User is gambling with the exposure release switch ---> stop him from doing that
- Switch or cabeling of swich is defective ---> replace X-ray release switch
Logge d
P osts: 22
GENERAL
Invalid telegram parameter for organ programs or fluoro
SPECIFIC
Reason:
The Fluorospot H cannot send exposure data, because there are no data programed.
Action:
2.Select the organ program, Press PAT DIR on FL H, F5 for tools, F1 for Organ Program, enter the specific data in the FL H
and store the program using F2.
2. Deinstall the after flash option in Configure Site Structure: In component selection click the Videomed DI, then click
OPTION and configure NO for the after flash
Illegal Configuration. The Configuration of meas. fileds, TV Parameter oder LTI moder are inconsistent. This error is caused
for instance, if the configuration excludes image
freq. 7.5 i/s for pulse fluoro and FL TOP selects the frequency via Organ program.
The user has pressed the button for image flip and the camera does not confirm that it did flip the image. The error is
cleared automatically, if the error condition is
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
cleared.
Reason:
Software or timing error in the camera.
Action:
Check SW version of camera and the corresponding XCS-Interface
No confirmation of image flip command in between on second. (If the confirmation is received afterwards, the error is
deleted automatically.)
Horizontal image flip in progress. (If the confirmation is received , the error is deleted automatically.
The user has pressed the button for image flip and the camera does not confirm that it did flip the image.
Reason:
Software or timing error in the camera.
Action:
Check SW version of camera and the corresponding XCS-Interface
The generator has reached the maximum voltage output and wants the camera to take over the AVR. However the camera
does not reply. The error will interrupt fluoro.
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
As soon as the error has been confirmed by the user, fluoro is possible but only with 110 kV. The system must be switched
off and on to restore fluoro funtionality.
Reason:
Software or timing error in the camera.
Action:
Check SW version of camera and the corresponding XCS-Interface
Cycle power of system.
Logge d
P osts: 22
Error list of XCU ( AP-ID 240 )
Illegal Configuration: Number of possible subdivisions is invalid or number cass progs is invalid
No cassette inserted. This Message is created if a the attempt is made to expose, although no cassette is inserted or the
casstte is already exposed.
Reason
A cassette is in the X-ray beam and would be exposed, if the fluoro is turned on.
Action:
Remove the cassette
Internal SW problem: System call returned illegal value, see error 000
X-ray blocked
Active tube is not the selected tube. Generator selects another tube than the desired one. Acq are disabled now.
Internal SW problem with finding values in a table of the tube. When transforming normal value to BP there is the need of
tables. If a value outside a table has to be found,
this error is created. In most cases it is harmless and may be ignored.
Internal SW error: water equivale t value in BP is below 0. Probably the water equivalent calibtration has not been done
carefully.
Internal SW error: water equivalent value in BP is above Maximum. Probably the water equivalent calibtration has not been
done carefully.
No grid correction value for selected grid. This error is caused by a wrong configuration. Somebody removed the grids in
the site structure dialog but the grid is still in the
system. As soon as it selected by organ program or manually this error is created. The error is internally ignored and the
XCU assumes no grid.
The error is only a problem if the fluoro is done without and the exposure is done with grid. You may solve the problem in
the site structure by clicking on the stand (Polystar,
Iconos, Sireskop, Siregraph ...) and click edit and set the grid to <available>.
No filter correction value for selected filter. This error is caused by a wrong configuration. Somebody removed the filters in
the site structure dialog but the filters are still in
the system. As soon as it is selected by organ program or manually this error is created. The error is internally ignored and
the XCU assumes no filter. You may solve the
problem in the site structure by clicking on the stand (polystar, siregraph, sireskop, iconos) and set the filters to
<available>.
unknown exposure technique selected. Valid exposure techniques are: DR, Tomo, DSA, Peri, 2-pt, 3 pt .... If a SW selects
another than a valid technique this error is
created.
No exposure curve for selected system. In an organ programm there is an unknown exposure curve selected. For usual C0
to C99 are valid. Sometimes also C100. Any
other curve will create that error.
Calculated value in exposure table is not OK. The exposure will be blocked.
Wrong value in tube load calculation. Tube data are not ok, XCU continues with default data for a 30 kW tube.
No value for foil sensitivity available. This indicates an invalid configuration of HUD in the site structure (no ionotomat
configured, but organ program wants an ionotomat
technique). Check configuration of OGP and availability of ionotomat in the system (no 1 pt technique program in system
without ionotomat.)
No water equivalent table found: no exposure curve for selected system. In an organ programm there is an unknown
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
exposure curve selected. For usual C0 to C99 are
valid. Sometimes also C100. Any other curve will create that error.
Addition of all exposure points is wrong. Wenn calculating the water equivalent value the checksum is wrong. XCU will
continue working with almost correct data
No grid data for selected grid. Probably the grid has not been configured. Call configure, select in the component list the
stand (e.g. Sireskop or Polystar) and press the
EDIT button. The next or next plus one window should show up the grids configuration. Enable the grid checkbox, select
the grid of your X-ray system and save the
configuration
XCU (AP-ID 240) error # 292 / 293 / 294 / 295 /296 /297
An exposure has been terminated by releasing the HK switch or by opening the door while radiation is on. If this error is in
the errorlog and the customer complaints
about some films being too bright (under-exposed), the filming was terminated because the X-ray switch has been released
by the customer before the radiation was
terminated.
The error also may be a follow-up error of a generator error, caused during radiation is on because the radiation will be
terminated by the error and not by Iontomat,
mAs-relais or ms - relais.
The error is logged system specific (see table below). The error is logged only for cassette and DR single shots with fixed
kV. For DR series the generator will not
terminate an exposure in progress before exposing is finished. In DR-0-pt-technique single the generator will terminiate but
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
will not that error.
Logge d
P osts: 22
Error list of XCU ( AP-ID 240 )
The user has pressed the button for image flip and the camera does not confirm that it did flip the image. The error is
cleared automatically, if the error condition is
cleared.
Reason
Software or timing error in the camera.
Action:
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
Check SW version of camera and the corresponding XCS-Interface
This error might be caused by a defective starter or a defective cable to the starter. Another indicator of this error might
be that the generator shows on the D100 the 3.
Action: Check cabling.
- when Polydoros Service SW is running (Generator is in service mode) and you select another system at the generator
desk. In Service mode the generator does not
answer to standard telegrams, so the request for confirmation current tube or changing to new tube will not be answered.
- when the generator will not come up when X-ray system is powered on(due to missing SW on D100, or missing XCS-
cabling or XCS network problem) this error will
be shown 1 to 2 minutes after power on.
Internal SW problem: System call returned illegal value, see error 000
In the Polydoros LX/lite only 125, in the SX only 990 organ programs can be stored.
Reason
Somebody has tried to store more then the possible max number of organ programs
Action:
Another organ program has to be deleted to store the new one
Illegal Configuration, the error might derive from the attempt of the user, to store an OGP in the FL Comp, while the system
selection is set to bucky, cassette ...
Save operation of organ programs not completed. During saving an organ program, which lasts for about a second, the user
attempts to store the next organ program.
DFR organ without DFR option set. Problem fix: Call configure site structure on service PC, confirm all dialogs with OK and
save the configuration. This should cure the
problem.
DFR organ block without DFR mark set in parent organ program. Problem fix: Call configure site structure on service PC,
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
confirm all dialogs with OK and save the
configuration. This should cure the problem.
Organ program for table specific parameters without init data 66. Problem fix: Call configure site structure on service PC,
confirm all dialogs with OK and save the
configuration. This should cure the problem.
Organ program for stand without main organ program. Problem fix: Call configure site structure on service PC, confirm all
dialogs with OK and save the configuration. This
should cure the problem.
Organ program not stored because organ data are kept external. This error will happen, if a FL H imaging system is
configured, but a FL TOP or FL Compact organ storing
operation is done.
Table specific organ data not stored because no main organ program. Problem fix: Call configure site structure on service
PC, confirm all dialogs with OK and save the
configuration. This should cure the problem.
Organ data mismatches system type. After acknowledging this message by the user the exposure will be done using default
data. This error is caused especially in service
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
IQAP or IMAC, if a system selection is done while IQAP is active and IQAP saves an OGP for DR although DR tomo is now
active.
Organ programming is disabled because the system has been configured or a restore has been performed and since the
configuration the XCU has not been booted.
Boot the XCU by cycling power. OGP programming will then be allowed.
The reason for that behavior is, that the configuration is storing a new OGP structure to disk and the copy of the disk in
the RAM of the XCU is no longer a real copy. If
someone now store OGP Nr. 7 this OGP might be on location 5 on disk. And what would happen is, that the XCU places the
data for OGP 7 on the space of OGP 5 on
the disk. Because Nr. 5 can also be in another system (e.g. Cassette tomo instead of the DR standard) the consequences
would be fatal. Therefore storing OGP is not
allowed, if configuration has been made through.
Because IRIS adjust, IQAP and IMAC of FL TOP are doing also an OGP store, IQAP and IMAC are not possible, as soon as
the configuration has been entered.
If the XCU powers on, the OGP on disk are completely copied to the RAM and everything is fine again.
Logge d
P osts: 22
Error list of XCU ( AP-ID 240 )
Internal SW problem: System call returned illegal value, see error 000
Acquisition not possible because a component is not ready: The system is not ready for exposure because one or more
components are no longer ready. This error is also
caused, if a spotfilm device is parked or a 3D stand is not in park position.
- a tube selection is in progress (up to 8 sec after a system selection) --> wait
- door contact is open (door is not closed) --> close door or shorten contact if no door is present
- generator is in service mode and an acquisition should be released at the console ---> leave service mode on service
PC)
- generator is in limit function (acquistion has been terminated due to exceeding max time or max mAs) ---> confirm limit
on console
- X-ray disable switch is activated ---> close x-ray disable switch or if no disable switch is present, make sure that D160
and D320 in generator do match (both new or
both old) and that the X-ray disable input is set to enable X-ray
- <emergency power> contact is closed ---> wait until emergency power is replaced by regular power or if no emergency
power is available, make sure that D160 and
D320 in generator do match (both new or both old) and that the emergency input is set to <enable X-ray>
- An error of the generator of the filament or of the iontomat (e.g. error 550of AP ID 80has been confirmed by the user
and the generator has reset filament or
iontomat which lasts up to 10 seconds. If an acquistion is requested in between this time, this error is displayed.
- In case of LX, that may mean that simple DR has been selected by switching to organ program #1 in region 1 but there
was no preceeding fluoro before invoking the
exposure.
- The cassette is not completely inserted --> remove cassette (might also happen in DR)
- Cassette has no more free images ---> insert new cassette
- Cassette is not inserted --> insert new cassette
- Cassette has been in stand during power up ---> remove and re-insert cassette
First three possible error causes should be cleared automatically after 1 - 2 seconds. Last cause will not cure.
Acquisition blocked by invalid device / Stand position. The device for Peri or Tomo is not in the correct position or the user
did not perform fluoro before starting peri.
same as 420
same as 421
same as 422
same as 423
same as 424
same as 421
same as 422
same as 423
same as 424
same as 421
same as 422
same as 431
same as 432
same as 433
same as 434
same as 423
same as 424
same as 421
same as 422
same as 423
same as 424
same as 422
same as 423
same as 424
same as 421
same as 422
same as 423
same as 424
same as 421
same as 423
same as 424
same as 421
same as 422
same as 423
same as 424
- no patient selected
- no more memory available on DFR
- storing of images in progress
- deleting of images in progress
- imaging system is in error condition
- background job is being prepared
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
- the last acquitition has been terminated only 1.5 seconds before (recovery time)
same as 462
same as 462
same as 462
same as 462
same as 462
same as 462
same as 462
same as 462
same as 462
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
XCU (AP-ID 240) error # 472
same as 420
same as 420
Fluoro turned on during exposure. The generator denied turning off the fluoro for beginning next exposure. The error is
cured with the next fluoro.
Acquisition blocked by FD-Detector . The FD detector is not ready for acquisition. It will take a long time until this message
is generated, because there is no Telegram for
the FD to say not ready. The only way to say not ready is to net say ready.
same as 475
same as 475
same as 475
The organ program contains only default data, has never been stored by the customer. The acquisition is blocked. Fix the
error by storing the organ program at the
Fluorospot. This message has been inserted for safety reasons. Because it is possible to store an organ program name from
the control console without organ data for DR
systems, the user might be confused if he is using the organ program with a name called DSA but will get default data
instead of DSA parameters. Therefore acquisition is
blocked.
Reasons:
- no patient selected
- no organ program selected
- still engaged with reading image data
- still booting
same as 480
P osts: 22
Error list of XCU ( AP-ID 240 )
2.) This error might occur, if the user selects in a Fluorospot TOP organ program a fluoro program that has not been
configured for pulsed, but the user selects for this
specific program the pulsed property.
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
To get rid of this problem: configure the specific program with pulsed fluoro in CONFIGURE of the XCS SSW
- door is open
- X-ray disable swich is on
- tube switching is in progress after a system selection (takes about 8 sec for heating up the tube)
- problems with its hardware
- limit is not confirmed by the user
Reasons
The Spotfilm device is in park position and II is not in one line with the tube.
The SID of Iconos R100 is not at one of its marked positions.
Action:
Put the device in the correct position or put the SID to the end.
FLUORO blocked by Cassette. (Cassette or cassette device would be in fluoro image, because cassette is not completely
inserted).
Insert cassette completely or remove cassette
Reason
Fluoro cannot be released, because the collimators do not send the telegram that they have reached theif final position.
The collimator may only block fluoro, if the fixed
size diaphragmas are moving so that they cover all of the image or if the collimator is doing a seach for its zero position
(will be performed once per hour). The error
should be cured by itself after app. 2 seconds.
Action:
Check the collimators mechanically if they have been problems in moving
Check the grid, if there is a problem with the switch or the reversing
- door is open
- X-ray disable swich is on
- tube switching is in progress (takes about 10 sec for heating ab the tube)
- problems with its hardware
- Limit has not been confirmed
FLUORO blocked because maximum Fluoro time has been exceeded. Bell for short time reset or 0-button on generator desk
for long time reset has to be pressed or
re-release Flouoro-Switch
This signal is generated by the D320/D160. So it also may be caused by a problem in the cabling of those boards or by
using not matching samples of these two boards.
Internal SW problem: System call returned illegal value, see error 000
Illegal configuration. This error is caused for instance, if an organ program requires a copper filter although no filters are
configured in site structure.
Configure these filters by calling site structure, click the stand (Polystar, Sireskop, Iconos ...), click edit and say in filter:
available.
Auto filter has been selected by the user or by organ program but there are no filters configured. Configure these filters by
calling site structure, click the stand (Polystar, Sireskop, Iconos ...), click edit and say in filter: available.
Logge d
P osts: 22
Error list of XCU ( AP-ID 240 )
Internal SW problem: System call returned illegal value, see error 000
Invalid Telegram parameter in a service telegram. Invalid telegram length or invalid group-id.
Illegal Configuration. This error is normal in a system that is not yet configured
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Error copying init blocks for region name to HD. Possible causes
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Internal SW problem: System call returned illegal value, see error 000
P osts: 22
Error list of XCU ( AP-ID 240 )
Internal SW problem: System call returned illegal value, see error 000
Illegal configuration: Standard error message in case XCU is not yet configured.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Illegal configuration
Logge d
P osts: 22
Error list of XCU ( AP-ID 240 )
Internal SW problem: System call returned illegal value, see error 000
Illegal configuration
Low on image memory, less than two images at start of acquisition or end of scene time reached.
Internal SW problem: System call returned illegal value, see error 000
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
General error
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Causes:
- disk of XCU defective --> replace XCU
- disk of XCU is cross-linked because power fail signal (D320/X1) is not working (see error 039) properly and disk is turned
off during write. You may insert a VGA
graphic card into XCU and try to perform per bootable floppy a DOS scandisk to repair. Also you should check the operation
of the power fail
- disk is full, which might be caused by starting a telegram trace via service PC, that has become too large, so that the
disk is full. Start another trace and terminate it
immediately, so that the new trace file is shorter.
Use our professional PDF creation service at http://www.htm2pdf.co.uk!
- SW error --> no workaround
Logge d
« previous next »