Artis Zee
Artis Zee
Troubleshooting Guide
System
System Troubleshooting with SW VC14
2 Document Version / Disclaimer / Copyright
Document Version
Siemens reserves the right to change its products and services at any time.
In addition, manuals are subject to change without notice. The hardcopy documents cor‐
respond to the version at the time of system delivery and/or printout. Versions to hard‐
copy documentation are not automatically distributed.
Please contact your local Siemens office to order a current version or refer to our website
http://www.healthcare.siemens.com.
Disclaimer
Siemens provides this documentation “as is” without the assumption of any liability under
any theory of law.
The content described herein shall be used by qualified personnel who are employed by
Siemens or one of its affiliates or who are otherwise authorized by Siemens or its affiliates
to use such documents.
Assemblers and other persons who are not employed by or otherwise directly affiliated
with or authorized by Siemens or one of its affiliates are not entitled to use this documen‐
tation without prior written authority.
Copyright
“© Siemens, 2009” refers to the copyright of a Siemens entity such as:
Siemens Healthcare GmbH - Germany
Siemens Aktiengesellschaft - Germany
Siemens Shenzhen Magnetic Resonance Ltd. - China
Siemens Shanghai Medical Equipment Ltd. - China
Siemens Healthcare Private Ltd. - India
Siemens Medical Solutions USA Inc. - USA
Siemens Healthcare Diagnostics Inc. - USA and/or
Siemens Healthcare Diagnostics Products GmbH - Germany
1 General Remarks 7
1.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1.1 Required Aids and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.1.2 Additionally Required Documents . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.2 Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.1 General Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.2 Product-specific Safety Information . . . . . . . . . . . . . . . . . . . . . . . 8
1.2.3 Conventions and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2.4 Tolerance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2 System Troubleshooting 14
3 AXCS 45
4 CAN 51
7 Power Distributor 89
9 Procedures 285
12 Index 306
1.1 Requirements
1.2 Remarks
1.2.2.1 System
WARNING
If there is a computer crash during “Service Radiation ON”, radiation is not auto‐
matically stopped.
If there is a computer crash, immediately press the on-site system emergency
off switch.
WARNING
[hm_serv_NoteProtectEyes]
Laser Class 3B units having a maximum output of 500 mW. This kind of laser is
used for the image transfer
a) from the FD to the RTC
L
b) from the RTC to the Image System.
The laser beam is invisible, dangerous to the human eye, and in some cases, to
the skin.
Proper use must be observed.
Required safety equipment must be used.
M The safety information for AXIOM Miyabi, ( AXIOM Miyabi / AXA4-000.860.01) must be
observed.
WARNING
Artis zee floor MN and Artis zee biplane MN Systems with Magnetic Navigation
(NIOBE):
M The two permanent magnets are installed by the Stereotaxis Company. Magnetic
objects can be attracted by the two permanent magnets and can fly through the
air like shots.
The safety information in the technical documents from the Stereotaxis Com‐
pany absolutely must be observed.
WARNING
[hm_serv_LabelPowerPresent]
Even after switching off the system (Shutdown), power is still present at the con‐
trol cabinet and generator.
If not observed, death or serious bodily injury can occur.
Observe the warning signs in the cabinets.
Switch off the power supply to the X-ray system with the on-site on/off
switch.
2
3
When performing service work in the table, serious injury can occur if there is uninten‐
tional lowering or tilting of the table. To prevent this, it is absolutely necessary to use the
following safety aids:
n Lift Safety Stud
Move the table all the way up, insert the lift safety stud ( 1/Fig. 2 Page 10) into the
table base from the outside and secure it with 2 cotter pins ( 2/Fig. 2 Page 10).
n Safety Brackets
For tilting tables, set the max. Trendelenburg position and insert the two safety brack‐
ets ( 3/Fig. 2 Page 10). Secure the two safety brackets with 2 cotter pins each.
1.2.2.6 Generator
WARNING
Risk of Accident!
As a rule, measurements using the oscilloscope may be performed only with
the ground wire connected. Disconnecting the ground wire without an isola‐
tion transformer is always forbidden. The ground wire may be rendered inef‐
fective via an isolation transformer only if voltages of no more than 25 V AC
or 60 V DC can occur on metal parts that can be touched. For measurements in
which ground loops can have a disturbing effect on the measurement result,
an isolation amplifier (e.g. GOULD Contec 9000 or TEKTRONIX A6902B) must
be used.
DANGER
Power is supplied to the cooling unit for about 20 minutes even if the system is
turned off!
Turn off the F1 breaker at the power distributor (MD) in the system cabinet.
1.2.2.8 FD Detector
WARNING
The FD cooling unit is supplied with line voltage and the FD with 24V DC even
when the system is switched off. To switch power of to these components:
switch off the "FD cooling unit" F13 fuse and the "FD Power Supply" F8 fuse in
the power distributor, or
switch off power to the complete power distributor with the F1 power switch,
or
set the system switch to the OFF position to switch power off to all compo‐
nents in the system.
1.2.3.1 Abbreviations
MC = Motor Controller
MCM = Motor Controller
MCU = Motor Control Unit
MD = Mains Distributor (power distributor)
MLC = Midsize Lab Cockpit
MNP = Managed Node Package (System Management)
PUD = Generator Polydoros A100
RAC = Rotating Anode Control
RTC = System Real Time Controller
SCM = Stand Control Module
SRS = Siemens Remote Service
SW = Wrench size
TBL = Table
TCM = Table Control Module
ULI = User Location Interface
Abbreviations related to the Imaging System can be found in the “Imaging System Soft‐
ware Installation Guide.”
DANGER
After switching off the system (shutdown), there is still voltage present in the sys‐
tem control cabinet and in the generator.
When performing service work:
- observe the warning labels in the cabinets.
switch power off to the radiographic system at the main on/off switch.
All pictures shown in this document are sample pictures. They may differ from the SW
Version actually installed.
The system does not power off. n If the power off from the D90 “Off switch” works, continue trou‐
bleshooting in the image system.
There is a boot problem with n Continue troubleshooting the image system( Boot Prob‐
“Black screen” lems / AXA4-000.840).
While the Imaging System is booting up, several system hardware tests are performed.
The system is in “Bypass Mode” n If the Image System does not show ready, check the error log
and an AXCS component is not for more messages.
“READY” n If the ANG (Angiomatic) does not show ready, check the error
log for AX_ANG messages.
If the error message points to the power unit, continue with the
PUD troubleshooting guide.
n If the SCU (stand control unit) does not show ready, check the
error log for AX_STD messages.
n If the SYC (system controller) does not show ready, check the
error log for AX_SYC messages.
- Download the SYC SW again.
If this is unsuccessful, replace the RTC.
n If the ACU (acquisition control unit) does not show ready, check
the error log for AX_ACU messages.
- If the error message points to the image pre-processing part,
check the LED status on the DIPP board.
- Download the ACU SW.
n If the CCU (collimator control unit) does not show ready, check
the error log for AX_COL messages.
There is a message “NO XRAY, n Check the error log for more messages.
please wait,” which does not re‐
cover.
There is a radiation problem n Troubleshooting X-ray radiation release
n Troubleshooting the power unit
With any X-Ray release, the sys‐ n Check the error log to see if the problem is reported from the
tem goes into “Bypass” image system or from an RTC component.
n Troubleshooting the image system( AXIS Image System
VC14 / AXA4-000.840.19).
n Troubleshooting video pre-processing.
There is no movement n Reset the SYC system controller from the SCM by pressing the
“override” button combination, then press and release the emer‐
gency stop button.
Fig. 4: Button combination for the “Override” function.
There is a movement problem. n If the SIRC board does not receive the DMG signal (check green
The movement has stopped and LED DM_Out), continue troubleshooting with DMG trouble‐
it is not possible to start the shooting guide.
movement again. n If the red LED "Emergency Stop" lights up on the SIRC board,
- check all red Stop buttons
- Continue troubleshooting in the emergency stop circuit; use
the circuit diagram
n If the quick stop LED lights up on the SIRC board, it could be
caused by the following:
- a collision
- activation of a limit switch
- activation of a contact safety switch
Continue troubleshooting in the quick stop circuit, use the wir‐
ing diagram.
n Analyze the error log for AX_SCU messages.
n Brief high-speed movement with an immediate stop could be
caused by a defective encoder.
n Check whether the movement command is evaluated from the
control module. See the Stand/Table Troubleshooting Guide for
the affected system:
- Patient Table ( Table Control Module / AXA4-000.840.05)
- Floor Stand ( Stand Control Module / AXA4-050.840.01)
- Second Plane ( Stand Control Module, Second Plane (biplane
systems only) / AXA4-050.840.01)
- MP ( Table Control Module / AXA4-410.840.01) and
( Stand Control Module / AXA4-410.840.01)
- Ceiling Stand ( Stand Control Module / AXA4-060.840.01)
- zeego ( No Movement with RCM / LCM is possi‐
ble / AXA4-040.840)
n Continue troubleshooting the stand / table.
n Troubleshoot the collimator and camera rotation
- Go to linearity adjustment for collimator and camera rotation.
- Check whether the reference tag is detected during the line‐
arity adjustment.
Movements can be performed, Check for error conditions that limit the movements.
but only at reduced speed. n The collision calculator has detected a possible collision.
n Only slow speed movement is allowed because of some error
conditions (e.g. a faulty position sensor, Motor encoder,...).
Continue troubleshooting the stand / table.
n If DMG is detected as active during startup, the speed is reduced
for all movements; the user is informed about the reason for the
reduced speed. Check whether the DM LED at the SIRC remains
on.
Movements can be performed, n If the Quick Stop LED lights up on the SIRC board, it could be
but only when the “override” caused by the following:
button combination is used. - possibility of a collision
Fig. 5: Button combination for the
“Override” function. - a limit switch has been reached
- Check the contact safety switches.
- Continue troubleshooting in the Quick stop circuit, use the
wiring diagram.
n A drive is beyond its SW limit. A new adjustment is recommen‐
ded.
n The collision calculator has detected a possible collision.
In this mode, the reduced over‐ - Check whether there is a real risk of collision.
ride speed is used. - Check whether the potentiometer values are correctly repor‐
ted.
- Check whether the configuration of the stand is OK.
The X-Ray image has poor quali‐ n If previously recorded images are OK, continue troubleshooting
ty FD.
There is an image processing n Continue troubleshooting the image system ( Decision Find‐
problem. ing / AXA4-000.840.19).
There is a general network con‐ n General Troubleshooting of Network Problems ( Network No‐
nectivity problem. des / AXA4-000.843.04).
It is not possible to search for n Continue troubleshooting the image system ( Decision Find‐
patients at remote network no‐ ing / AXA4-000.840.19).
des with the patient browser.
It is also not possible to transfer
patient images to a remote net‐
work node.
It is not possible to send images, n Continue troubleshooting configuration network nodes ( Net‐
but the remote node is accessi‐ work Nodes / AXA4-000.843.04).
ble with ping and C_ECHO
It is not possible to transfer pa‐ n Continue troubleshooting configuration network nodes ( Net‐
tient images to a remote net‐ work Nodes / AXA4-000.843.04).
work node.
But it is possible to search for
patients at remote network no‐
des with the patient browser.
Printing images to a DICOM n Continue troubleshooting configuration network nodes ( Net‐
printer is not possible. work Nodes / AXA4-000.843.04).
Other network communications
are OK.
It is not possible to receive im‐ n Continue troubleshooting configuration network nodes ( Net‐
ages from a remote network work Nodes / AXA4-000.843.04).
node.
Other network communications
are OK.
It is not possible to receive a n Continue troubleshooting DICOM Worklist ( HIS/RIS no‐
worklist. des / AXA4-000.843.04).
There is a problem with CAN n Troubleshoot the CAN components ( CAN / Page 51).
communication. (A CAN compo‐
nent is not accessible.)
There is a problem with AXCS n Troubleshoot the AXCS components ( AXCS / Page 45).
communication.
There is a problem with the n Troubleshoot the power distributor ( Power Distribu‐
power distributor. tor / Page 89).
There is a problem with the n Troubleshoot the power distributor ( Power Distribu‐
On/Off circuit. tor / Page 89).
Use the "On/off switch circuit 1 and 2" wiring diagram for trouble‐
shooting this subject.
The Resource Monitor warning Open Local Service UI (Level 7) to enable the Service Resource Mon‐
icon appears. itor. Left click the Resource Monitor Icon (Pie chart) to view the
Fig. 6: Resource Monitor Warning Icon Service Resource Monitor. For detailed information on the Service
Resource Monitor see ( Resource Monitor (Service) / Page 24).
Temporary Storage:
Fig. 7: Resource Monitor (not enough space left for temporary storage of data)
There is a problem with a serv‐ n Check for more messages in the Event log ( Event Log
ice procedure. / Page 267).
The Service mode of the Resource Monitor is available when Local Service is opened with
Level 7 or higher. Left click the Resource Monitor Icon (Pie chart) to open the Resource
Monitor window. The Resource Monitor is updated every 5 seconds.
The Blob files of the SchedulerStore database are typically stored in E:\IMAGE\3..... (e.g. E:
\IMAGE\3.0.34904)
The Exchangeboard and SchedulerStore folders are typically empty when there are no
queued or pending jobs (e.g. Film sheets, Archive to Net, etc.)
2. Select Settings > Control Panel > Administrative Tools > Performance.
The Performance window is shown.
3. Right click the right pane of the Performance window (the graph is shown here)
The context menu is shown
4. Select Properties....
The System Monitor Properties dialog box is shown
5. Select the General tab
6. Select Report from the View group.
7. Select the Data tab
8. Click the Add... button
the Add Counter dialog box is shown
9. Select Memory from the Performance object dropdown box
10. Select the Select counters from list radio button
11. Select Commit Limit, press and hold the Ctrl key and select Committed Bytes
12. Click the Add button
13. Click the Close button on the Add Counter dialog box.
14. Click the Apply button on the System Monitor Properties dialog box.
15. Click the OK button on the System Monitor Properties dialog box.
The values are shown
Total Virtual Memory = Commit Limit
Free Virtual memory = Commit Limit - Committed Bytes
2.1.1.13 C:\Temp
monitors the free space on the C: drive. Typically, C:\Temp accumulates unnecessary files.
However, there are other location on the C: drive that can fill up with unnecessary files:
n C\Windows\Temp\
typically there are no required files in this folder. The system (Win XP) may have some
files IN USE which are prevented from being deleted. This is normal.
n C:\Axiom\Axis\
typically *.DMP files can be deleted. It may be useful to keep the most recent files for
escalation if the problem continues.
n C:\Axiom\log\
typically *_ERR.LOG files can be deleted. It may be useful to keep the most recent logs
for troubleshooting.
Every contact safety switch that is pressed will latch the Quick_Stop circuit. The signal
goes "Low".
Every change of the proximity status is reported via CAN to the SCU software.
If a contact safety switch changes from active to inactive, the SCU sends a Quick Stop re‐
lease. If one contact safety switch holds the quick stop and another contact safety switch
is pressed and released again, the quick stop LED will be briefly turned off and on again.
This is because release of a switch will release the quick stop but the other switch that is
still active will set the quick stop circuit again.
The quick stop signal is normally at high level.
There is a problem with fluoro n To check the dose measurement circuit, it is recommended to
only start the PDA test that can be found in the service UI under Test
Tools > Hardware Tests>.
n Check the footswitch signals (use wiring diagram).
n Are the footswitch signals OK? - Check the RTC/SIRC signals (use
wiring diagram).
There is a problem with expo‐ n Check the footswitch signals by using the wiring diagram.
sure only n Are the footswitch signals OK? - Check the RTC/SIRC signals (use
wiring diagram).
There is a problem with the n Use the Control Fluoro or Control Exposure function to exclude a
dose or dose rate PUN error ( Control Fluoro / Page 123).
n Go to ( Dose and Dose Rate Troubleshooting Guide
/ Page 35).
The tube voltage is out of all n Check whether the problem is “focus-related”
proportion to the object (UT n Check the filament circuit / tube unit
too high).
With thicker objects, the mes‐
refer to tube unit troubleshooting guide ( MEGALIX
CAT ...-121... with the Klüver Cooling Unit Troubleshoot‐
sage “dose less than 5%” is dis‐
ing / AX71-020.840.02).
played.
There is no release signal received at the n Check the footswitch signals according to the Wiring
SIRC board. Diagram.
There is no radiation release. Check the signals at the SIRC board of the RTC (use wir‐
ing diagram).
Link to measurement examples ( SIRC Board in RTC
/ Page 43)
The XRQ signal is missing Check the DIPP (video pre-processing) for error messag‐
es and function.
A footswitch radiation release signal is received by the SIRC board as the SUM_REL signal.
Together with the XRQ signal from the video pre-processing part, the radiation will be
triggered.
The signal SWR or STRT_INV is responsible starting the high voltage inverter in the PUN.
The end of an X-Ray pulse usually is determined by the dose counter.
But the mass counter or the safety time counter can also stop an X-Ray pulse.
If there are dose or dose rate-related problems, it is recommended to run the dose ad‐
justment procedure for troubleshooting purposes without saving the results.
The dose is too high n Perform a new dose adjustment and compare the results with the
values from the previous adjustment or the original initial adjust‐
ment. There might be a difference, but the tendency should be
the same.
The dose varies or it is unsta‐ n Run the control fluoro, control exposure generator tests ( Con‐
ble. trol Functions / Page 33) . If the dose / dose rate is reproducible,
the error is not located on the power unit side.
n Run the control fluoro ( Control Functions / Page 33) generator
test and check the different profiler settings for proper function.
Follow the AX_CCU messages as well.
n Check the FD and FD power supply ( FD with System SW
VC14 / AXA4-110.840.04).
The CAREWATCH reading is n Check according to the Adjustment Instructions.
not OK.
2.8 Collimator
2.8.1 Collimator
There are warning messages n Check the error log for AX_CCU and AX_CAN messages.
about dose or skin dose. - If there are messages with the ID 110, identify the cause of the
warning according to the code given in the free text [xxxx] and
the explanation listed in the information box
Check the prefilter function with the control fluoro mode
( Control Fluoro / Page 123) . Here it is possible to set all
filters individually. Open the collimator housing and closely
watch the physical movement of the filter. Check the X-ray
image as well to verify that no filter stops somewhere be‐
tween the in and out position.
The collimator is doing contin‐ n Reload the Collimator Software via SW Manager.
uous “search runs”
2.10 Carewatch
No dose area product value at n Check whether the ionization chamber is properly connected.
system monitor. n If the yellow HV LED on the front panel lights up, the high voltage
On the front panel of the Dia‐ for the chamber is out of tolerance and no pulses are generated
mentor the power supply LED (HV error).
is on. - If the LED remains on with detached ionization chamber
replace the Diamentor.
- If the LED goes off with a disconnected ionization chamber, the
fault is located in the cable or in the chamber
- Disconnect the ionization chamber on the collimator side to see
if the fault is located in the cable.
No dose area product value at n Check whether there is a dose reading while activating the test
system monitor. button under fluoro.
On the front panel of the Dia‐ - If there is still no reading of the dose area product value,
mentor, the power supply LED replace the Diamentor.
is on.
- If there is a reading of the dose area product value, replace the
The HV LED is off ionization chamber or the cable.
n With the 1-channel Diamentor K1-S , all signals of plug X1 are
parallel available at X2.
Dose area product value at Check the Angiomatic configuration and save the configuration
system monitor shows “???”. again.
There are no dose counts dur‐ n Check whether the Diamentor pulses are available at the Diamen‐
ing the calibration procedure tor control unit X1/2 Pin 6 and 1 and at the SIRC board (Plug X7
(with activation of test but‐ between Pin 6 and 1).
ton). Replace the Diamentor control unit.
DK1/2.X1
Stecker 1
OUTPUT1
On HV-Error
Cal
Chamber
DK1/2.X2
Stecker 2
OUTPUT2
Test
SUPPLY
DK1/2.X3
Stecker 3
DK1/2.X1
Stecker 1
OUTPUT1
On HV-Error
Cal A
Chamber A
DK1/2.X2
Stecker 2
OUTPUT2
Cal B
Chamber B
Test
SUPPLY
DK1/2.X3
Stecker 3
(1) X-RAY signal (this signal is generated if 75% of the nominal tube voltage is present)
(2) STRT_INV (this is the start and stop signal for the high voltage inverter circuit)
(3) IT_FRQ (this is the actual tube current signal after U/F conversion)
_______________________________________________________________________
There is no communication to an ECC n Do a check of the error log. Error messages are expected
module. for this group of errors.
n Do a check of the physical connections at the ECC, ULI
board, and RTC switch.
n For more detailed troubleshooting, connect the ECC to an‐
other switch port.
n Continue troubleshooting using the ECC Troubleshooting
Guide.
There is no communication to a data n Do a check of the error log. Error messages are expected
display. for this group of errors.
n Do a check of the physical connections at DDIS and the
RTC switch.
n For more detailed troubleshooting, connect the DDIS to
another switch port.
n Continue troubleshooting using the ECC Troubleshooting
Guide.
There is no communication to the RTC n Do a check of the error log. Error messages are expected
(but ECC and DDIS are OK) for this group of errors.
n Do the AXCS test ( AXCS TEST / Page 49).
n Use the ping command to make sure the connection with
the RTC is functional( PING / Page 291).
n Reload the RTC software.
resistor (120 Ohm). This is done with a termination plug or jumpered on a board. If this
is not observed, communication reliability will be reduced, sporadic errors may occur or
the communication will not work at all.
Sporadically there is no communication to n Check the event log for AX_CCU error 202 “VCI Driver
any CAN node. Error“ (App log/Warning/Developer)
- The absence of VCI Driver Error is a good indication
that the problem is on the SIRC (defective board,
cabling or connectors).
- This message is reported when the System, RTC, or
a CAN-device is powered On/Off. These can be ig‐
nored when caused by service actions.
- When the System , RTC, or CAN-device is not pow‐
ered On/Off, this message indicates a problem with
the CAN-bus (cable, connector, or CAN-device).
n Check the CAN branch line termination.
- Remove the CAN connectors labeled "in" on the
SIRC board of RTC A and the connectors labeled
"out" on the SIRC board of RTC B and measure the
resistance between pins 2 and 7. The expected
reading is 120 Ohm with about 15% tolerance.
n Check the CAN cables and sub-D connectors.
n Oscillographic CAN activity level measurement (ap‐
prox.2 V [1.5 - 3 V] differential)
( trace/Fig. 19 Page 55)
( trace/Fig. 20 Page 55)
A software download to the PUD is not n Check the 7-segment display status from D600, con‐
possible. tinue TSG Polydoros A100.
n Check the cabling and connector panel in the PUN
cabinet.
It is NOT possible to connect a Control Module straight to the RTC since there is no power supply at
the CAN connectors on the SIRC board.
There is no communication to a motor n Check the error log. Error messages are expected for
controller module. this group of faults.
n Check the physical connections from the SIRC board
to the controller. Use the wiring diagram.
n Try to reload the motor controller software. If this can
be done successfully, CAN communication is ok. Con‐
tinue troubleshooting for the particular drive (Stand
or Table TSG).
There is no communication to a power n Check the error log. Error messages are expected for
unit (PUD). this group of errors.
n Check the physical connections from the SIRC board
to the PUN. Use the wiring diagram.
n Check the cabling and connector panel in the PUN
cabinet.
n Try to reload the PUN software. If this can be done
successfully, CAN communication is ok. Continue us‐
ing the PUD troubleshooting guide.
n If a D600 board is replaced, check for the correct
node ID jumper settings on the board.
When the CAN is download or the CAN Bus Test is finished, the RTC has to reboot again
into its normal mode. This takes place automatically when the button “Finish” is pressed.
Please note that the DDO and edge enhancement window settings can lead to a differ‐
ent appearance.
Please note that the DDO and edge enhancement window settings can lead to a differ‐
ent appearance.
6.3 Spots
Please note that the DDO and edge enhancement window settings can lead to a differ‐
ent appearance.
6.4 Lines
Please note that the DDO and edge enhancement window settings can lead to a differ‐
ent appearance.
Spot
Line
Please note that the DDO and edge enhancement window settings can lead to a differ‐
ent appearance.
Please note that the DDO and edge enhancement window settings can lead to a differ‐
ent appearance.
Fig. 44: Temperature island with annotation n Start a new FD calibration ( FD Cali‐
bration / AXA4-110.842.03).
Use the wiring diagram for troubleshooting the power distributor (fuse table / mains dis‐
tributor)
There are 2 line power distributor models used in VCxx systems.
Use the table matching the model.
Tab. 13 Troubleshooting with D90 board indications (new style line power distributor)
Tab. 14 Troubleshooting with D90 board indications (old style line power distributor)
It is recommended to use the "On/off switch circuit control" wiring diagram for trouble‐
shooting this component.
CAUTION
Voltages of up to 24 V can be present on the brown connectors.
Voltages from 110 to 220 V can be present on the white connectors.
Do not touch the connectors.
X600
X41 RTC (X4) Safety Interface (safe stop)
X42 ALI 2 Board Safety Interface
7.4.4 Relay
Relevant relays on the RCU board:
Relay Definition
K4 Quick stop override; when the override
switch is pressed on the RCM, this relay
switches
K5 Contact safety device is controlled by
the RPIF board
LED Definition
Green Normal status, output voltage is present
Red ““Overload”
Possible causes:
n Short circuit at the input
n Short circuit at the output
n Power supply defective
The service user interface corresponds to the standard Syngo service UI. Here, the follow‐
ing functions have been taken unchanged from Syngo:
n Backup and Restore
n DICOM Tests
n File and Image Tools
n Auto Report
n Utilities
n Reports
n Help
n Software Distribution
The following syngo functions have been adapted to the requirements of Artis zee:
n Configuration
n Tune Up
n Report Generation
n Control
n Quality Assurance
n Test Tools
n Event Log
All standard service functions can be performed in this user interface. The Service UI is
remote access capable. All functions that do not generate radiation or that trigger a unit
movement can be performed via remote.
There are also what are called “Factory Diagnostics” for the image system. Here, even
more diagnostic capabilities for the image system are integrated. First, the Syngo applica‐
tion must be ended to use the factory diagnostics.
8.2 Configuration
See the Configuration Guide ( Configuration Main Menu + System Op‐
tions / AXA4-000.843.04).
Perform the “Backup” only when the System is not in “Bypass mode”
Here you can back up predefined packages and restore the packages or groups within a
package. The backup/restore location can be a local drive, removable medium (CD/DVD)
or network drive.
This is for the syngo Backup and Restore of the system and the configuration data.
This is not the Acronis Backup and Restore of the IVS/IAS system drives.
8.3.1 Backup
8.3.1.1 Drives
Select the drive. The archive will be written to the root of the selected drive.
n [-A-] Floppy Disk
- IVS floppy drive
n [-F-] DVD
- ACE CD/DVD burner
n [-R-] DVD
- IVS CD/DVD reader
n [-C-] FIXED
- IVS system drive
n [-D-] FIXED
- IVS database drive
n [-E-] FIXED
- IVS image pixel drive
n \\10.1.1.16\DataBackup
- IAS-A Service disk - standard network drive ( Set Network Drive / Page 107)
8.3.1.2 Packages
Select the package. For details on package content, see ( Tab. 16 Page 105)
n Clone package
n Configuration
n Exam sets
n FD data
n FileExport
n Security settings
n SW distribution
8.3.2 Restore
8.3.2.1 Drives
Select the drive. The list of archives will be read from the root of the selected drive.
n [-A-] Floppy Disk
- IVS floppy drive
n [-F-] DVD
- ACE CD/DVD burner
n [-R-] DVD
- IVS CD/DVD reader
n [-C-] FIXED
- IVS system drive
n [-D-] FIXED
- IVS database drive
n [-E-] FIXED
- IVS image pixel drive
n \\10.1.1.16\DataBackup
- IAS-A Service disk - standard network drive ( Set Network Drive / Page 107)
8.3.2.2 Archive
Select the archive. There are 7 possible types of archives (packages) to restore. Only those
on the root of the selected drive will be listed. There can be more than 1 archive of a par‐
ticular type (e.g. different date and/or time).
The format for the archive name is:
<host name>_<system serial number>_<Package>_<Date>_<Time>_ok.ar
n host name - as configured under Configuration > (Local Host) TCP/IP Lan > (Identi‐
fication) Computer name
n system serial number - as configured under Configuration > (Local Host) Site Info>
(System) Serial No
8.3.2.3 Groups
Select the group or groups to be restored. Multiple groups can be selected. The list of
groups depends on the archive that is selected.
Tab. 16 Restore package groups
Packages
Configuration
Exam sets
FD data
Clone package
SW distribution
Security settings
Groups
All\ X X
ecc_ddis\ecc\ X
host\axiom\ X
host\ddisxp\ X
host\pms\ X
host\rep\ X
IQAP\ X
PMS_Backup_Log\ X X X
rtc_a\acu_a\ (rtc_b\acu_b\)1 X X
rtc_a\ang_a\ (rtc_b\ang_b\)1 X
rtc_a\ccu_a\ (rtc_b\ccu_b\)1 X
rtc_a\csf_a\ (rtc_b\csf_b\)1 X
rtc_a\scu\ (rtc_b\scu\)1 X
rtc_a\syc\ (rtc_b\syc\)1 X X
Packages
Configuration
Exam sets
FD data
Clone package
SW distribution
Security settings
Groups
rtc_a\wcu\ (rtc_b\wcu)1 X
Service\Applications\CorRea\ X X
Service\Applications\MBoxIntegration\ X
Service\Applications\MPPS\ X X
Service\Applications\PatientRegistration\ X X
Service\Applications\Viewer\ X
Service\Applications\WorklistResults\ X X
Service\Database\DBOffset\ X X
Service\Database\SateliteConsole\ X X
Service\DICOM\General\ X X
Service\DICOM\HISRISNodes\ X X
Service\DICOM\ImportExportDirectories\ X X
Service\DICOM\LocalNode\ X X
Service\DICOM\LUTFiles\ X X
Service\DICOM\NetworkNodes\ X X
Service\DICOM\OfflineDevices\ X
Service\DICOM\PrintDevices\ X X
Service\DICOM\StructuredReport\ X X
Service\EPRI\Server\ X X
Service\ExternalDevices\PaperPrinter\ X X
Service\ExternalDevices\PS_LUTFiles\ X X
Service\LocalHost\Modality\ X
Service\LocalHost\MonitorType\ X X
Service\LocalHost\Routing\ X X
Service\LocalHost\SiteInfo\ X X
Service\LocalHost\Users\ X
Packages
Configuration
Exam sets
FD data
Clone package
SW distribution
Security settings
Groups
Service\Security\GSMConfiguration\ X X
Service\Service\AutoTransfers\ X X
Service\Service\Eventlog\ X X
Service\Service\FTP\ X X
Service\Service\Hosts\ X X
Service\Service\Licensing\ X
Service\Service\Mail\ X X
Service\Service\SecConfig\ X X
Service\Service\SystemMgmt\ X X
Service\TCPIP\LAN-Settings\ X X
Service\TCPIP\PersistentRoutes\ X
Service\TCPIP\RAS-Settings\ X
System_Configuration\ X
UserSettings\ X X
8.3.3.3 Password
(See: CS Knowledge Base ID 13982, AX PASSWORD LIST)
8.4 Tune Up
See the system adjustment instructions ( Adjustments and Final Work
Steps / AXA4-000.814.31).
8.5.1 General
n It is recommended to run general reports whenever a new config or adjustment is per‐
formed
n The system must be “up and running” when the “Generate Reports” tool is started, this
can be found under: Local service UI, Report Generation >
8.6 Control
All service switches are set back when leaving the program.
Switch Description
PUN HW SS: Displays the current status of the safety switch on the D30 power unit board. The switch
has to be set to "ON" for normal operation.
SIRC Radiation Enable: Displays the current status of the service switch on the RTC SIRC connection
board. The switch has to be set to "OFF" for normal operation.
SW-SS The safety breaker is switched off in the X-ray generator power unit so
there is no power supply to the inverter and therefore no high voltage.
Switch Description
The selection range is automatically set, depending on the radiation mode selection (Fluoro/
Exposure).
Testimage Camera = Test patterns from the camera head can be selected (if I.I. system).
Camera Test Pattern They are used to check the entire video system.
Only with I.I. Systems When a test pattern is selected, the "SS switch" is automatically turned
off.
Please note that the window settings, DDO, AGC, Global Gain, Gamma
and edge enhancement can lead to a different appearance.
n Analog Head Pattern
The analog test pattern is fed into the video system just after the CCD
chip. It is used to check the entire video system. The test pattern dis‐
play depends on the selected frame rate. For frame rates up to 15 fps,
the pattern uses the full screen. At 30 fps, the test pattern is split ver‐
tically into two parts and the two parts are also inverted. The basic
test pattern is a trapezoid from black to white and back to black.
n Digital Head Pattern
The digital head pattern is fed into the video system behind the A/D
converter. The test pattern is a ramp from white to black.
Switch Description
Test Image CCB = Test patterns can be selected from the camera control board (located in
CCB Test Pattern the RTC)
Only with I.I. Systems When a test pattern is selected, the "SS switch" is automatically switched
off.
Please note that the window settings, DDO, AGC, Global Gain, Gamma
and edge enhancement can lead to a different appearance.
n Correction Pattern
The correction pattern is fed into the video system at the input of the
CCB board. The pattern is a ramp from black to white.
n Defective Pixel Map
The defective pixel pattern is used to see the number of defective pix‐
els of the CCD chip.
Test image FD There are several test patterns available from the FD ( Test Pattern Selec‐
With FD Systems tion for FD Systems / Page 116).
Please note that window settings, DDO, AGC, Global Gain, Gamma and
edge enhancement can lead to a different appearance.
Testimage DIPP Test patterns (ramp and level) can be selected from the video processing
boards (located in the RTC) ( Test Pattern Selection for FD Sys‐
tems / Page 116).
The <Ramp> test pattern is a combination of gray values and different
ramp signals.
DIPP test patterns will work correctly only with frame rates of <7.5 F/s
If the “level” test pattern is selected, a homogeneous image is generated.
The <Level> test pattern is a homogeneous gray pattern which is adjusta‐
ble in the service software.
The signal level can be selected with the gray level setting in the next
line.
The range is between 0 (black) and 4095 (white).
This test can be used to find out whether image artifacts are caused by
postprocessing or by the acquisition components.
When a test pattern is selected, the "SS switch" is automatically switched
off.
Please note that window settings, DDO, AGC, Global Gain, Gamma and
edge enhancement can lead to a different appearance.
Gray level The gray level for the homogeneous image can be specified.
0 = max. dark, 4095 = max. bright
Note: Appearance depends on the AGC and on the Gamma selection.
Load image from disk Test patterns from the RTC. This function can be used only when images
were previously downloaded to the RTC.
When a test pattern is selected, the "SS switch" is automatically switched
off.
Switch Description
Video Output The following outputs can be selected
n AXIS
n Graphics card/bypass monitor
n RTC disk
Save image to disk Images can be saved to RTC to memory location RTC0 ....5
Gamma Video gain characteristics. γ =1 is a linear gain.
γ =0.2 is a logarithmic gain. The value behind the Gamma is the signal
peak reduction in percent.
e.g. 1/100 means a gamma of 1 and no peak reduction.
e.g. 0.6/80 means a Gamma of 0.6 and a peak reduction of 60% of a
4095 gray value. Afterwards the signal is expanded to the maximum of
4095.
CMA Grey Value Intensity of the circle overlay for the overframing factor.
CMA Ofr. Factor Overframing factor for the circle overlay.
Global Gain It is possible to set the Global Gain to “auto” or to a fixed factor for FD sys‐
tems.
For test images set global gain to 1.
DIPP Filter 1 Factor EVE filter (extended vessel enhancement)
DIPP Filter 1 Kernel Kernel size for EVE filter
MEC inhibit “ON” will inhibit the memory effect correction.
ISY Postblanking Postblanking of the image system can be switched off to see the position
of the collimator plates.
Fluoro/Exposure defines the X-ray mode which is released with start X-ray. To activate
the control switch setting, an X-ray mode is required.
Fig. 60: Digital static horizontal pattern Digital static horizontal pattern
Fig. 61: Digital static vertical pattern Digital static vertical pattern
Fig. 62: Digital dynamic horizontal pattern Digital dynamic horizontal pattern
Fig. 65: Static horizontal ramp from analog board Static horizontal ramp from analog
board
Fig. 66: Static vertical ramp for the analog board Static vertical ramp from analog board
Fig. 67: Static Mapix gray level pattern from analog board Static Mapix gray level pattern from an‐
alog board
Fig. 68: Static diagonal black/white pattern from analog board Static diagonal black/white pattern
from analog board
Fig. 69: Static diagonal lines from the analog board Static diagonal lines from analog board
Fig. 70: Static pseudo random pattern from analog board Static pseudo random pattern from an‐
alog board
Please note that the window settings, DDO, AGC, Global Gain, Gamma and edge en‐
hancement can lead to a different appearance.
Fig. 71: DIPP ramp test pattern Dipp test pattern
DIPP Test Pattern “Level” will show a homogeneous image with a gray level that is de‐
fined under <level>
To use Control Fluoro, the service switch on the SIRC board (SRV_RAD, front-end RTC)
must be active.
Control Fluoro This mode is used to release fluoro with predefined parameters. The cur‐
rently used exam set will be replaced by a specific fluoro program for service. All parame‐
ter entries are monitored from the system control to ensure the X-ray tube will not be
overloaded.
Fluoro A/B Defines the plane where fluoro will be released. For biplane fluoro select, "Flu‐
oro A" and "Fluoro B" at the same time.
Start/Stop X-ray Key to release X-ray and disable X-ray. The name of the key will toggle,
depending on the current mode.
Exit Exits the Service Switches dialog box and returns to the Control window. All service
switches are reset to their default values.
When all tests are completed, set the service switch on the SIRC board back to "OFF".
To use Control Acquisition, the service switch on the SIRC board (SRV_RAD, front-end
RTC) must be active.
To call up the Control Acquisition, select the path Control > Control Acquizition >.
Fig. 73: Controlled acquisition
When all tests are completed, set the service switch on the SIRC board back to "OFF".
8.6.4 Auxiliary
This mode is for lab use only! It is necessary to get special information to set the correct
parameter.
With the "AXCS Trace Control" tool, it is possible to record the last 1000 AXCS objects to a
readable file. It is possible to trigger a certain event or initiate an immediate trace dump.
In both cases the recorded file can be viewed in the report viewer.
Domain ID: Enter the Domain ID of the error which will be used as the trigger.
Use up to a max. of 3 characters (e.g. SCU) as the input.
Only the following Domain IDs (Error Sources) will trigger an AXCS trace:
Component Explanation
ACU Acquisition Control Unit (RTC)
ANG Angiomatic (RTC)
CCU Collimator Control Unit (RTC)
CSF Common Software Functions (RTC)
PMS Service (customer log user messages)
REP Error Reporting
SCU Stand Control Unit (RTC)
SF Support Functions (Service)
SYC System Controller (RTC)
n Exit
Exits "Auxiliary" and returns to the "Control" menu.
If no more trace files are required, delete the boxes with the Error ID and Domain ID.
Select Drive
Select the drive. The Organ Program file will be written to the root of the selected drive.
n [-A-] Floppy Disk
- IVS floppy drive
n [-C-] FIXED
- IVS system drive
n [-D-] FIXED
- IVS database drive
n [-E-] FIXED
- IVS image pixel drive
n [-F-] DVD
- ACE CD/DVD burner
n [-R-] DVD
- IVS CD/DVD reader - not useful for export.
Select the Organ Program Modes to be exported. Multiple modes can be selected. The
available modes depend on the system type and the options that are installed and config‐
ured.
Select the organ program(s) to be exported. A list of the organ programs is shown for
each OGP Mode selected in the previous menu (List of OGP Modes)
Organ programs for the Fluoro and Roadmap Modes are selected for export as triplets.
For all others modes (e.g. DR mode, DSA mode, ...), organ programs are selected sepa‐
rately for export.
Select Drive
Select the drive. The list of Organ Program files is read from the root of the selected drive.
n [-A-] Floppy Disk
- IVS floppy drive
n [-C-] FIXED
- IVS system drive
n [-D-] FIXED
- IVS database drive
n [-E-] FIXED
- IVS image pixel drive
n [-F-] DVD
- ACE CD/DVD burner
n [-R-] DVD
- IVS CD/DVD reader
Select File
Select the Organ Program file from the list. Only the Organ Program files on the root of
the selected drive will be listed. There can be more than 1 file (e.g. different date and/or
time).
The details of the selected Organ Program file are shown:
Select the Organ Program Modes to be imported. Multiple modes can be selected. The
available modes depend on the contents of the OGP file to be imported.
Select the organ program(s) to be replaced. A list of the organ programs is shown for
each OGP mode selected in the previous menu (List of OGP Modes). The message "OGP
Present in system" is shown if the organ program already exists in the system.
Organ programs for the Fluoro and Roadmap modes are selected for import as triplets.
For all other modes (e.g. DR mode, DSA mode, ...), organ programs are selected sepa‐
rately for import.
For a manual restore of the IVS/IAS-A/B using the Acronis boot CD, see:
n IVS ( Restore of the IVS (PC/System Drive replaced or corrupt Software)
/ AXA4-000.841.19)
n IAS A ( Restore of IAS A (PC/System Drive replaced or corrupt Software)
/ AXA4-000.841.19)
n IAS B ( Restore of IAS B (PC/System Drive replaced or corrupt Software)
/ AXA4-000.841.19)
Only manual backup/restore of the KPC (Zeego) using the Acronis Image Management
Console is possible. See ( KPC Backup/Restore / AXA4-000.816.04).
8.6.6.1 Backup
For details, see ( Creating a System Disk Backup / AXA4-000.816.04).
8.6.6.2 Restore
For details, see ( Restoring a System Disk Backup / AXA4-000.816.04).
When a SW package is installed using this method, the BE (Backend) is not notified of
the status of the SW installation.
This function can be found under Service GUI > Control > Offline SW Pkg Import.
The page can be exited safely after “LSS Import Package extracted successfully...” is
shown in the status bar at the lower left.
Fig. 80: SD Icon in Status bar
The syngo SD icon should be shown in the right bottom of the screen within 15 minutes.
After the syngo SD icon is shown, follow the Software Distribution/Installation workflow,
see ( SD User Interface / Page 264).
For further information, see the system quality assurance( Quality Assurance with Sys‐
tem SW VC14 / AXA4-000.820.08).
1. To call up the Quality Assurance Tests, select the path <Quality Assurance> .
2. Click Save.
3. Type the name for the new Self Defined test
- It is recommended to give the test a descriptive name so that its purpose is clear.
4. Click Save.
The new Self Defined test is selectable from the Self Defined drop down
menu.
8.8.1.2 Components
ECC 1(2/3):
The joystick functionality is tested. This is an interactive test which requires physical
movement of the joystick and buttons.
For details, see ( ECC Joystick Test / AXA4-000.840.07).
Stand:
The brakes of the particular stand are tested.
For details, see ( Hardware Tests / AXA4-410.840.01).
In SW versions < VC14G, the cmd shell window closes automatically when complete.
The test can be started manually (C:\AXIOM\rtc\callcannetinfor.bat). The cmd shell win‐
dow stays open when complete and waits for the press of a key to close.
If the ping is unsuccessful, the Connect to 10.1.1.120 window is not shown and the sys‐
tem returns to the Third-party Tests selection page.
8.9.1 General
8.9.1.2 Layout
1. Navigation bar
2. DICOM Service and Mode selection frame (navigation frame)
3. Specific selection frame (navigation frame)
4. Function frame
5. Action bar
8.9.1.3 Features
This chapter provides an overview of the tools supported by DICOM Services.
DICOM Services
n Verify Network:
Network connection on TCP/IP level (ping) and on DICOM level (DICOM Verification (C-
ECHO)) can be tested either for a certain destination or for all configured DICOM no‐
des.
n Storage:
The trace level for the DICOM logfile (merge_stu.log) can be extended to display, e.g.,
the association negotiation (T3), the command set of a DICOM message (T7), and the
data set of a DICOM message (T2).
In addition, a test receiver may be started to capture original DICOM images on the
hard disk. A test sender can be used to check the receiving functions of the local or
remote DICOM application.
n Basic Print:
A test basic print provider may be started and images may be sent to this process. The
message transfer and the film may be displayed.
The trace level for the DICOM logfile (merge_hc.log) may be extended to display, e.g.,
the association negotiation (T3), the command set of a DICOM message (T7), and the
data set of a DICOM message (T2).
n Query/Retrieve:
The trace level for the DICOM logfile (merge_stu.log) may be extended to display, e.g,
the association negotiation (T3), the command set of a DICOM message (T7), and the
data set of a DICOM message (T2).
n Storage Commitment:
The trace level for the DICOM logfile (merge_stu.log) may be extended to display, e.g,
the association negotiation (T3), the command set of a DICOM message (T7), and the
data set of a DICOM message (T2).
n Modality Worklist:
The trace level for the DICOM logfile (merge_HRI.log) may be extended to display,
e.g., the association negotiation (T3), the command set of a DICOM message (T7),
and the data set of a DICOM message (T2).
n Modality Performed Procedure Steps:
The trace level for the DICOM logfile (merge_HRI.log) may be extended to display,
e.g., the association negotiation (T3), the command set of a DICOM message (T7),
and the data set of a DICOM message (T2).
Activate the configured process by clicking the Go on the Action bar (5).
The results are displayed in the function frame (4).
The Analysis platform may be activated from the Navigation bar (1). The analysis frame
layout is identical to the DICOM service platform.
If you want to save the captured messages (including images) and logfiles, you need to
click the Cancel button.
8.9.2 Functions
Verify Network
Fig. 85: DICOM Verification of a single destination
Verify Network performs a TCP/IP ping. If this ping is successful, the DICOM Service DI‐
COM Verification sends a C-ECHO request to a DICOM destination process (AET) on the
local or remote system.
DICOM verification may be performed for a specific DICOM node or simultaneously for all
configured DICOM nodes (verify all AETs).
This test consists of 2 steps: the first step is the TCP/IP ping, and the second step is the C-
ECHO command on the DICOM level.
You can stop the test by clicking the Abort button in the Action bar.
Storage
The storage service class determines how DICOM images and other objects (waveforms,
LUTs, overlays) are sent (SCU) or received (SCP). The DICOM Standard defines several
transfer syntaxes, each of which is a set of encoding rules for communication (e.g., byte
ordering, compression).
The DICOM implementation is based on a toolkit from Merge Technologies. This toolkit
includes a mergecom.log file designed as a ring buffer. Certain trace levels may be ena‐
bled to receive more detailed information regarding the latest DICOM communications.
The respective mergecom.log file can be displayed under Analysis at “Examine Logs -
merge_stu.log”. To interpret the log files, basic knowledge of DICOM is necessary.
Storage, Storage Commitment, and Query/Retrieve use the same mergecom.log file, as
they belong to the same syngo Service.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
When incoming associations are automatically rejected (IP address not known), log
messages will be displayed at this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.
Send Images
This menu item can be used to send DICOM images (stored on the hard disk via the test
receiver or, e.g., FTP) to a user-specified DICOM receiver. By sending these images to the
local DICOM receiver, you are able to import images into the database and display them
in the user interface.
n Transfer Syntax
This pull-down list lets you choose transfer syntaxes that will be enabled after restart
of the DICOM processes. It provides additional troubleshooting options, as you can
limit the settings for the next associations.
Before selecting other DICOM Services or functions, or before finishing the DICOM
Test Tools, “abort” the “Send Images” function. The original transfer syntaxes will be
set again.
n Image Data
Displays a list of DICOM images located in the %MEDHOME%\service\dst\img directory.
The test receivers (see Simulate/Add Local/Remote Receiver) will copy all received im‐
ages to this directory. Images copied to this directory manually (ftp) will also be dis‐
played. Certain default DICOM images will be delivered with the DICOM Test Tools for
test purposes.
n AET of Sender
The sending AET is, by default, the AET of the local storage SCP. Usually it is not neces‐
sary to change this value.
n Host Name
Host name of the destination system. The system itself (host name) may be selected
as well. When selecting the logical name or AET (next two buttons), the appropriate
host name will be displayed automatically.
n Logical Name
Select the logical name of the destination system. When selecting the AET (next but‐
ton) first, the appropriate logical name will be displayed automatically.
n AET
Select the storage AET of the destination system. Please note: The Send function will
fail, if you, e.g., select the Query/Retrieve AET of the remote system instead of the
storage AET.
n Merge Trace Level
The following trace levels may be enabled to provide more detailed information in the
log file merge_stu.log. This log file may be displayed under “Analysis - Examine Logs”.
See also the example of an association with trace level T2, T3, T7 and T9 in the
appendix.
- T1
This trace level does not affect the mergecom.log file.
- T2 Data Set
This trace level shows the attributes of the transferred message, e.g. the image
header attributes or the attributes within a DICOM message.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
When incoming associations are automatically rejected (IP address not known), log
messages will be displayed on this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.
- T6 Mergecom Configuration Files
At this trace level, the related mergecom.ini, mergecom.pro, mergecom.app, and
mergecom.srv files will be written to the mergecom.log file. This may be helpful in
analyzing the log file, however, note that analysis requires a large amount of space
in the log file.
- T7 Command Set
Following the association negotiation, a command set (attributes with group 0) will
be transferred. Before sending, for example, an image, the command set will tell
the remote system the type of image object (SOP Class UID such as CT, RF, ...) to be
transferred, including the UID of the image.
The response command set after each image will show the status of the transfer,
where status = 0 means a successful transfer.
- T8 Streaming Messages
Log messages relating to the streaming in and out of messages and file objects are
displayed on the T8 level.
-T9 PDU Level
The entire DICOM association is displayed on the PDU level (Protocol Data Unit).
Each PDU with a maximum size defined during the association negotiation will be
displayed in one line.
The association negotiation will be shown in greater detail.
T9 provides the only possibility of displaying the Association Release request and re‐
sponse at the end of an association.
Patient Data Access
In case of remote access to the DICOM Service Tools, viewing patient-relevant data
(name, id, ..) is not permitted. However, if you enable trace level T2, patient data will be
displayed in the log file. Therefore, the customer has to provide additional access rights,
allowing the service engineer to view patient-relevant data. To obtain these rights, the
service engineer has to enter his name and send a “Patient Data Access” request to the
customer"s user interface.
n Please enter your name
Enter the name of the local service engineer logged in remotely who requires Patient
Data Access rights.
n Request PDA
Selecting this button initiates that an additional selection item (Patient Data Access)
will be activated in the customer user interface under “Option - Remote Access”. Addi‐
tionally, the name of the service engineer will be displayed. The customer has to se‐
lect this menu item to permit trace level T2 to be activated in the log file.
Before selecting other DICOM Services or functions, or before finishing the DICOM Test
Tools, “abort” the “Send Images” function.
When this menu item is selected, the Test Receiver provided by the DICOM Test Tools is
started to simulate a remote DICOM receiver. You will receive a list of all DICOM AETs con‐
figured on your system. Select the AET you would like to replace with the Test Receiver.
All images sent by the local sender to this destination will be received by the Test Receiver
and stored on the hard disk in DICOM format.
Fig. 90: Storage - Simulate Remote Receiver diagram
Under analysis, the received images can be evaluated: an image header dump may be
performed, or the image can be displayed.
The received images and the log files may be removed when exiting the DICOM Service
Tools.
The storage test tools may only be started remotely in “Full Access Mode”. In this case, no
user interaction is possible, and, therefore, it is also not possible to send / print images or
to perform a query request. Since these user interactions are necessary to receive the ap‐
propriate messages in the mergecom.log files, the DICOM Test Tools provide the possibili‐
ty of enabling user interaction even in full access mode.
n Release Host
Select this item in the Action bar to work with the user interface (identical to limited
access). The “Remote Access Control Window” can be iconized.
n Back to Full Access
After the images have been transferred or a Query/Retrieve has been performed, this
function disables interaction at the user interface to perform further tasks in the DI‐
COM Test Tools.
n Host Name
Host name of the destination system. The system itself (host name) may be selected
as well. When selecting the logical name or AET (next two buttons), the appropriate
host name will be displayed automatically.
n Logical Name
Select the logical name of the destination system. When selecting the AET (next but‐
ton) first, the appropriate logical name will be displayed automatically.
n AET
Select the storage AET of the destination system. Please note: The Send function will
fail, if you, e.g., select the Query/Retrieve AET of the remote system instead of the
storage AET.
n Merge Trace Level
The following trace levels may be enabled to provide more detailed information in the
log file merge_stu.log. This log file may be displayed under “Analysis - Examine Logs”.
See also the example of an association with trace level T2, T3, T7 and T9 in the
appendix.
- T1
This trace level does not affect the mergecom.log file.
- T2 Data Set
This trace level shows the attributes of the transferred message, e.g. the image
header attributes or the attributes within a DICOM message.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
If incoming associations are automatically rejected (IP address not known), log mes‐
sages will be displayed on this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.
When this menu item is selected, a Test Receiver provided by the DICOM Test Tools is star‐
ted using the same AET and port number as the application DICOM receiver. The original
application receiver will be stopped. All images sent by remote senders will be stored in
DICOM format to the hard disk.
None of the images received by the Test Receiver will be stored to the database. To avoid
losing images, select the AET of the sending system. All other senders will be rejected.
The received images may be analyzed with the tools provided by “Dicom Analysis”.
The received images and the log files may be removed when exiting from the DICOM
Service Tools.
n Host Name
Host name of the sending system. For data security, only images from this AET will be
received by the Test Receiver. All other systems will be rejected. The system itself
(host name) can also be selected. When selecting the logical name or AET (next two
buttons), the appropriate host name will be displayed automatically.
n Logical Name
Select the logical name of the sending system. When selecting the AET (next button)
first, the appropriate logical name will be displayed automatically.
n AET
Select the storage AET of the sending system. Please note: The Send function will fail,
if you, e.g., select the Query/Retrieve AET of the remote system instead of the storage
AET.
n Merge Trace Level
The following trace levels may be enabled to provide more detailed information in the
log file merge_stu.log. This log file may be displayed under “Analysis - Examine Logs”.
See also the example of an association with trace level T2, T3, T7 and T9 in the
appendix.
- T1
This trace level does not affect the mergecom.log file.
- T2 Data Set
This trace level shows the attributes of the transferred message, e.g. the image
header attributes or the attributes within a DICOM message.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
If incoming associations are automatically rejected (IP address not known), log mes‐
sages will be displayed on this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.
- T6 Mergecom Configuration Files
At this trace level, the related mergecom.ini, mergecom.pro, mergecom.app, and
mergecom.srv files will be written to the mergecom.log file. This may be helpful in
analyzing the log file, however, note that analysis requires a large amount of space
in the log file.
- T7 Command Set
Following the association negotiation, a command set (attributes with group 0) will
be transferred. Before sending, for example, an image, the command set will tell
the remote system the type of image object (SOP Class UID such as CT, RF, ...) to be
transferred, including the UID of the image. The response command set after each
image will show the status of the transfer, where status = 0 means a successful
transfer.
- T8 Streaming Messages
Log messages relating to the streaming in and out of messages and file objects are
displayed on the T8 level.
-T9 PDU Level
The entire DICOM association is displayed on the PDU level (Protocol Data Unit).
Each PDU with a maximum size defined during the association negotiation will be
displayed in one line.
The association negotiation will be shown in greater detail.
T9 is the only way of displaying the association release request and response at the
end of an association.
Patient Data Access
In case of remote access to the DICOM Service Tools, viewing patient-relevant data
(name, id, ...) is not permitted. However, if you enable trace level T2, patient data will be
displayed in the log file. Therefore, the customer has to provide additional access rights,
allowing the service engineer to view patient-relevant data. To obtain these rights, the
service engineer has to enter his name and send a "Patient Data Access" request to the
customer's user interface.
The objects (images) captured with the Test Receiver will normally be anonymized.
If patient-relevant data is required for troubleshooting (not anonymized), it is neces‐
sary to obtain the “Patient Data Access” rights from the customer's user interface.
n Please enter your name
Enter the name of the remotely logged in local service engineer who requires Patient
Data Access rights.
n Request PDA
When you select this button, an additional selection item (Patient Data Access) is acti‐
vated in the customer user interface under “Option - Remote Access”. Additionally, the
name of the service engineer will be displayed. The customer has to select this menu
item to permit trace level T2 to be activated in the log file.
Before selecting other DICOM services or functions, or before finishing the DICOM Test
Tools, “abort” the “Simulate Remote Receiver” function.
This option lets you select an additional DICOM receiver that is used for test purposes on‐
ly. The AET of this test receiver has to be entered during Configuration. The Test Receiver
is listening under the port 110. It may be used to receive images from the local applica‐
tion, as well as any remote system (as long as this AET is configured there).
You can only send from specifically selected AETs. All other remote nodes can still send to
the original DICOM receiver.
None of the images received by the Test Receiver will be stored to the database. To avoid
losing images, select the AET of the sending system. All other senders will still send to
the original local DICOM receiver.
To send to the additional Test Receiver, configure this Test Storage SCP (port: 110, AET
will be defined in the Test Tools) at the remote system (SCU).
Fig. 94: Storage - Add Local Receiver diagram
The received images may be analyzed with the tools provided by “DICOM Analysis”.
The images received and the log files may be removed when exiting from the DICOM
Service Tools.
n AET
You need to define an AET for the additional Test Receiver. At the remote system, you
need to configure this AET with the appropriate port number 110.
n Merge Trace Level
The following trace levels may be enabled to provide more detailed information in the
log file merge_stu.log. This log file may be displayed under “Analysis - Examine Logs”.
See also the example of an association with trace level T2, T3, T7 and T9 in the
appendix.
- T1
This trace level does not affect the mergecom.log file.
- T2 Data Set
This trace level shows the attributes of the transferred message, e.g. the image
header attributes or the attributes within a DICOM message.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system SCP. The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
If incoming associations are automatically rejected (IP address not known), log mes‐
sages will be displayed on this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.
- T6 Mergecom Configuration Files
At this trace level, the related mergecom.ini, mergecom.pro, mergecom.app, and
mergecom.srv files will be written to the mergecom.log file. This may be helpful in
analyzing the log file, however, note that analysis requires a large amount of space
in the log file.
- T7 Command Set
Following the association negotiation, a command set (attributes with group 0) will
be transferred. Before sending, for example, an image, the command set will tell
the remote system the type of image object (SOP Class UID such as CT, RF, ...) to be
transferred, including the UID of the image. The response command set after each
image will show the status of the transfer, where status = 0 means a successful
transfer.
- T8 Streaming Messages
Log messages relating to the streaming in and out of messages and file objects are
displayed on the T8 level.
-
T9 PDU Level
The entire DICOM association is displayed on the PDU level (Protocol Data Unit).
Each PDU with a maximum size defined during the association negotiation will be
displayed in one line.
The association negotiation will be shown in greater detail.
T9 is the only way of displaying the association release request and response at the
end of an association.
Patient Data Access
In case of remote access to the DICOM Service Tools, viewing patient-relevant data
(name, id, ...) is not permitted. However, if you enable trace level T2, patient data will be
displayed in the log file. Therefore, the customer has to provide additional access rights,
allowing the service engineer to view patient-relevant data. To obtain these rights, the
service engineer has to enter his name and send a “Patient Data Access” request to the
customer's user interface.
The objects (images) captured with the Test Receiver will normally be anonymized.
If patient-relevant data is required for troubleshooting (not anonymized), it is neces‐
sary to obtain the “Patient Data Access” rights from the customer's user interface.
n Please enter your name
Enter the name of the remotely logged in local service engineer who requires Patient
Data Access rights.
n Request PDA
When you select this button, an additional selection item (Patient Data Access) will be
activated in the customer user interface under “Option - Remote Access”. Additionally,
the name of the service engineer will be displayed. The customer has to select this
menu item to permit trace level T2 to be activated in the log file.
Before selecting other DICOM services or functions, or before finishing the DICOM Test
Tools, it is necessary to “abort” the “Simulate Remote Receiver” function.
Print Devices
This menu provides tools for testing the Basic Print function of the local DICOM Basic Print
process. You may start a Test Basic Print provider, which replaces the remote Basic Print
provider (usually a laser camera). After printing a film from the user interface to the Test
Basic Print process, you can analyze the log files and display the film using the tools provi‐
ded under Analysis.
The DICOM implementation is based on a toolkit from Merge Technologies. This toolkit
includes a mergecom.log file designed as a ring buffer. Certain trace levels may be ena‐
bled to receive more detailed information regarding the latest DICOM communications.
The respective mergecom.log file can be displayed under Analysis at “Examine Logs -
merge_hc.log”. To interpret the log files, basic knowledge of DICOM is necessary.
Location and name of the mergecom.log file for Basic Print:
C:\%MEDHOME%\log\merge_hc.log Basic Print (hardcopy)
The print test tools may only be started remotely in “Full Access Mode”. In this case, no
user interaction is possible, and, therefore, it is also not possible to send / print images or
to perform a query request. Since these user interactions are necessary to receive the ap‐
propriate messages in the mergecom.log files, the DICOM Test Tools provide the possibili‐
ty of enabling user interaction even in full access mode.
n Release Host
Select this item in the Action bar to work with the user interface (identical to limited
access). The "Remote Access Control Window" can be iconized.
n Back to Full Access
After the images have been sent to the camera, disable interaction at the user inter‐
face to perform further tasks in the DICOM Test Tools.
n Transfer Syntax
This pull-down list lets you choose transfer syntaxes that will be used for the associa‐
tion negotiation after restart of the DICOM processes. It provides additional trouble‐
shooting options, as you can limit the settings for the next associations. Before select‐
ing other DICOM services or functions, or before finishing the DICOM Test Tools,
"abort" the Extend Trace Level function. The original transfer syntaxes will be set
again.
n Host Name
Host name of the camera. The system itself (host name) may be selected as well.
When selecting the logical name or AET (next two buttons), the appropriate host
name will be displayed automatically.
n Logical Name
Select the logical name of the camera. When selecting the AET (next button) first, the
appropriate logical name will be displayed automatically.
n AET
Select the AET of the camera.
n Merge Trace Level
The following trace levels may be enabled to provide more detailed information in the
log file merge_stu.log. This log file may be displayed under “Analysis - Examine Logs”.
See also the example of an association with trace level T2, T3, T7 and T9 in the
appendix.
- T1
This trace level does not affect the mergecom.log file.
- T2 Data Set
This trace level shows the attributes of the transferred message, e.g. the image
header attributes or the attributes within a DICOM message.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
If incoming associations are automatically rejected (IP address not known), log mes‐
sages will be displayed on this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.
- T6 Mergecom Configuration Files
At this trace level, the related mergecom.ini, mergecom.pro, mergecom.app, and
mergecom.srv files will be written to the mergecom.log file. This may be helpful in
analyzing the log file, however, note that analysis requires a large amount of space
in the log file.
- T7 Command Set
Following the association negotiation, a command set (attributes with group 0) will
be transferred. Before sending, for example, an image, the command set will tell
the remote system the type of image object (SOP Class UID such as CT, RF, ...) to be
transferred, including the UID of the image. The response command set after each
image will show the status of the transfer, where status = 0 means a successful
transfer.
- T8 Streaming Messages
Log messages relating to the streaming in and out of messages and file objects are
displayed on the T8 level.
-T9 PDU Level
The entire DICOM association is displayed on the PDU level (Protocol Data Unit).
Each PDU with a maximum size defined during the association negotiation will be
displayed in one line.
The association negotiation will be shown in greater detail.
T9 is the only way of displaying the association release request and response at the
end of an association.
Patient Data Access
In case of remote access to the DICOM Service Tools, viewing patient-relevant data
(name, id, ...) is not permitted. However, if you enable trace level T2, patient data will be
displayed in the log file. Therefore, the customer has to provide additional access rights,
allowing the service engineer to view patient-relevant data. To obtain these rights, the
service engineer has to enter his name and send a “Patient Data Access” request to the
customer's user interface.
n Please enter your name
Enter the name of the remotely logged in local service engineer who requires Patient
Data Access rights.
n Request PDA
When you select this button, an additional selection item (Patient Data Access) will be
activated in the customer user interface under “Option - Remote Access”. Additionally,
the name of the service engineer will be displayed. The customer has to select this
menu item to permit trace level T2 to be activated in the log file.
Simulate Camera
Fig. 96: Print Devices - Simulate Camera menu
When this menu item is selected, the Test Basic Print SCP provided by the DICOM Service
Tools is started in place of the Camera (remote Basic Print SCP). You will receive a list of
all configured Basic Print AETs. Select the appropriate laser camera. All films sent from the
user interface to the corresponding laser camera will then be received by the Test Basic
Print SCP.
Fig. 97: Basic Print - Simulate Camera diagram
The Test Basic Print SCP is not identical to the laser camera. As a result, its behavior may
be different from the remote Basic Print SCP.
The Print Test Tools may only be started remotely in “Full Access Mode”. In this case, no
user interaction is possible, and, therefore, it is also not possible to send / print images or
to perform a query request. Since these user interactions are necessary to receive the ap‐
propriate messages in the mergecom.log files, the DICOM Test Tools provide the possibili‐
ty of enabling user interaction even in full access mode.
n Release Host
Select this item in the Action bar to work with the user interface (identical to limited
access). The “Remote Access Control Window” can be iconized.
n Back to Full Access
After the images have been sent to the camera, disable interaction at the user inter‐
face to perform further tasks in the DICOM Test Tools.
n Host Name
Host name of the camera. The system itself (host name) may be selected as well.
When selecting the logical name or AET (next two buttons), the appropriate host
name will be displayed automatically.
n Logical Name
Select the logical name of the camera. When selecting the AET (next button) first, the
appropriate logical name will be displayed automatically.
n AET
Select the AET of the camera.
n Merge Trace Level
The following trace levels may be enabled to provide more detailed information in the
log file merge_stu.log. This log file may be displayed under “Analysis - Examine Logs”.
See also the example of an association with trace level T2, T3, T7 and T9 in the
appendix.
- T1
This trace level does not affect the mergecom.log file.
- T2 Data Set
This trace level shows the attributes of the transferred message, e.g. the image
header attributes or the attributes within a DICOM message.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
If incoming associations are automatically rejected (IP address not known), log mes‐
sages will be displayed on this trace level.
Storage Commitment
Storage Commitment sends a list of image UIDs to the configured destination and waits
for the response of the remote provider.
For this service, it is only possible to extend the trace level of the appropriate merge‐
com.log file. Storage Commitment uses the same DICOM process as Storage and there‐
fore also the same log file, which is stu_merge.log. In this response, trace level T2 shows
whether or not the images were successfully stored at the destination.
This DICOM implementation is based on a toolkit from Merge Technologies. This toolkit
includes a mergecom.log file designed as a ring buffer. Certain trace levels may be ena‐
bled to get more detailed information regarding the latest DICOM communications. The
respective mergecom.log file can be displayed under Analysis at "Examine Logs -
merge_stu.log". To interpret the log files, basic knowledge of DICOM is necessary.
Storage, Storage Commitment, and Query/Retrieve use the same mergecom.log file, as
they belong to the same syngo Service.
C:\%MEDHOME%\log\merge_stu. logs Storage, Storage Commitment, and Query/Retrieve
The DICOM Test Tools may only be started remotely in “Full Access Mode”. In this case, no
user interaction is possible, and, therefore, it is also not possible to send / print images or
to perform a query request. Since these user interactions are necessary to receive the ap‐
propriate messages in the mergecom.log files, the DICOM Test Tools provide the possibili‐
ty of enabling user interaction even in full access mode.
n Release Host
Select this item in the Action bar to work with the user interface (identical to limited
access). The “Remote Access Control Window” can be iconized.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
If incoming associations are automatically rejected (IP address not known), log mes‐
sages will be displayed on this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.
- T6 Mergecom Configuration Files
At this trace level, the related mergecom.ini, mergecom.pro, mergecom.app, and
mergecom.srv files will be written to the mergecom.log file. This may be helpful in
analyzing the log file, however, note that analysis requires a large amount of space
in the log file.
- T7 Command Set
Following the association negotiation, a command set (attributes with group 0) will
be transferred. Before sending, for example, an image, the command set will tell
the remote system the type of image object (SOP Class UID such as CT, RF, ...) to be
transferred, including the UID of the image. The response command set after each
image will show the status of the transfer, where status = 0 means a successful
transfer.
- T8 Streaming Messages
Log messages relating to the streaming in and out of messages and file objects are
displayed on the T8 level.
-T9 PDU Level
The entire DICOM association is displayed on the PDU level (Protocol Data Unit).
Each PDU with a maximum size defined during the association negotiation will be
displayed in one line.
The association negotiation will be shown in greater detail.
T9 is the only way of displaying the association release request and response at the
end of an association.
Patient Data Access
In case of remote access to the DICOM Service Tools, viewing patient-relevant data
(name, id, ...) is not permitted. However, if you enable trace level T2, patient data will be
displayed in the log file. Therefore, the customer has to provide additional access rights,
allowing the service engineer to view patient-relevant data. To obtain these rights, the
service engineer has to enter his name and send a “Patient Data Access” request to the
customer's user interface.
n Please enter your name
Enter the name of the remotely logged in local service engineer who requires Patient
Data Access rights.
n Request PDA
When you select this button, an additional selection item (Patient Data Access) will be
activated in the customer user interface under “Option - Remote Access”. Additionally,
the name of the service engineer will be displayed. The customer has to select this
menu item to permit trace level T2 to be activated in the log file.
Query/Retrieve
For this service, it is only possible to extend the trace level of the appropriate merge‐
com.log file. Query/Retrieve uses the same DICOM process as Storage and therefore also
the same log file, which is stu_merge.log. The Query request and response message at‐
tributes may be displayed on trace level T2.
This DICOM implementation is based on a toolkit from Merge Technologies. The toolkit
includes a mergecom.log file designed as a ring buffer. Certain trace levels may be ena‐
bled to get more detailed information regarding the latest DICOM communications. The
respective mergecom.log file can be displayed under Analysis at “Examine Logs -
merge_stu.log”. To interpret the log files, basic knowledge of DICOM is necessary.
Storage, Storage Commitment, and Query/Retrieve use the same mergecom.log file, as
they belong to the same syngo Service.
C:\%MEDHOME%\log\merge_stu.log1 Storage, Storage Commitment, and Query/Retrieve
The DICOM Test Tools may only be started remotely in “Full Access Mode”. In this case, no
user interaction is possible, and, therefore, it is also not possible to send / print images or
to perform a query request. Since these user interactions are necessary to receive the ap‐
propriate messages in the mergecom.log files, the DICOM Test Tools provide the possibili‐
ty of enabling user interaction even in full access mode.
n Release Host
Select this item in the Action bar to work with the user interface (identical to limited
access). The "Remote Access Control Window" can be iconized.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
If incoming associations are automatically rejected (IP address not known), log mes‐
sages will be displayed on this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.
- T6 Mergecom Configuration Files
At this trace level, the related mergecom.ini, mergecom.pro, mergecom.app, and
mergecom.srv files will be written to the mergecom.log file. This may be helpful in
analyzing the log file, however, note that analysis requires a large amount of space
in the log file.
- T7 Command Set
Following the association negotiation, a command set (attributes with group 0) will
be transferred. Before sending, for example, an image, the command set will tell
the remote system the type of image object (SOP Class UID such as CT, RF, ...) to be
transferred, including the UID of the image. The response command set after each
image will show the status of the transfer, where status = 0 means a successful
transfer.
- T8 Streaming Messages
Log messages relating to the streaming in and out of messages and file objects are
displayed on the T8 level.
-
T9 PDU Level
The entire DICOM association is displayed on the PDU level (Protocol Data Unit).
Each PDU with a maximum size defined during the association negotiation will be
displayed in one line.
The association negotiation will be shown in greater detail.
T9 is the only way of displaying the association release request and response at the
end of an association.
Patient Data Access
In case of remote access to the DICOM Service Tools, viewing patient-relevant data
(name, id, ...) is not permitted. However, if you enable trace level T2, patient data will be
displayed in the log file. Therefore, the customer has to provide additional access rights,
allowing the service engineer to view patient-relevant data. To obtain these rights, the
service engineer has to enter his name and send a “Patient Data Access” request to the
customer's user interface.
n Please enter your name
Enter the name of the remotely logged in local service engineer who requires Patient
Data Access rights.
n Request PDA
When you select this button, an additional selection item (Patient Data Access) will be
activated in the customer user interface under “Option - Remote Access”. Additionally,
the name of the service engineer will be displayed. The customer has to select this
menu item to permit trace level T2 to be activated in the log file.
Basic Worklist
For this service, it is only possible to extend the trace level of the appropriate merge‐
com.log file. The Worklist request and response message attributes may be displayed on
trace level T2.
This DICOM implementation is based on a toolkit from Merge Technologies. The toolkit
includes a mergecom.log file designed as a ring buffer. Certain trace levels may be ena‐
bled to get more detailed information regarding the latest DICOM communications. The
respective mergecom.log file can be displayed under Analysis at “Examine Logs -
merge_wl.log”. To interpret the log files, basic knowledge of DICOM is necessary.
The DICOM Test Tools may only be started remotely in “Full Access Mode”. In this case, no
user interaction is possible, and, therefore, it is also not possible to perform a worklist re‐
quest from the user interface. Since these user interaction is necessary to receive the ap‐
propriate messages in the merge_HRl.log files, the DICOM Test Tools provide the possibili‐
ty of enabling user interaction even in full access mode.
n Release Host
Select this item in the Action bar to work with the user interface (identical to limited
access). The “Remote Access Control Window” can be iconized.
n Back to Full Access
After the Worklist request has been performed, disable interaction at the user inter‐
face to perform further tasks in the DICOM Test Tools.
n Transfer Syntax
This pull-down list lets you choose transfer syntaxes that will be used for the associa‐
tion negotiation after restart of the DICOM processes. It provides additional trouble‐
shooting options, as you can limit the settings for the next associations. Before select‐
ing other DICOM services or functions, or before finishing the DICOM Test Tools,
“abort” the Extend Trace Level function. The original transfer syntaxes will be set
again.
n Merge Trace Level
The following trace levels may be enabled to provide more detailed information in the
log file merge_stu.log. This log file may be displayed under “Analysis - Examine Logs”.
See also the example of an association with trace level T2, T3, T7 and T9 in the
appendix.
- T1
This trace level does not affect the mergecom.log file.
- T2 Data Set
This trace level shows the attributes of the transferred message, e.g. the image
header attributes or the attributes within a DICOM message.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
If incoming associations are automatically rejected (IP address not known), log mes‐
sages will be displayed on this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.
- T6 Mergecom Configuration Files
At this trace level, the related mergecom.ini, mergecom.pro, mergecom.app, and
mergecom.srv files will be written to the mergecom.log file. This may be helpful in
analyzing the log file, however, note that analysis requires a large amount of space
in the log file.
- T7 Command Set
Following the association negotiation, a command set (attributes with group 0) will
be transferred. Before sending, for example, an image, the command set will tell
the remote system the type of image object (SOP Class UID such as CT, RF, ...) to be
transferred, including the UID of the image. The response command set after each
image will show the status of the transfer, where status = 0 means a successful
transfer.
- T8 Streaming Messages
Log messages relating to the streaming in and out of messages and file objects are
displayed on the T8 level.
This DICOM implementation is based on a toolkit from Merge Technologies. The toolkit
includes a mergecom.log file designed as a ring buffer. Certain trace levels may be ena‐
bled to get more detailed information regarding the latest DICOM communications. The
respective mergecom.log file can be displayed under Analysis at “Examine Logs -
merge_HRI.log”. To interpret the log files, basic knowledge of DICOM is necessary.
The DICOM Test Tools may only be started remotely in “Full Access Mode”. In this case, no
user interaction is possible, and, therefore, it is also not possible to perform a worklist re‐
quest from the user interface. Since user interaction is necessary to receive the appropri‐
ate messages in the merge_HRI.log files, the DICOM Test Tools provide the possibility of
enabling user interaction even in full access mode.
n Release Host
Select this item in the Action bar to work with the user interface (identical to limited
access). The “Remote Access Control Window” can be iconized.
n Back to Full Access
After the Worklist request has been performed, disable interaction at the user inter‐
face to perform further tasks in the DICOM Test Tools.
n Transfer Syntax
This pull-down list lets you choose transfer syntaxes that will be used for the associa‐
tion negotiation after restart of the DICOM processes. It provides additional trouble‐
shooting options, as you can limit the settings for the next associations. Before select‐
ing other DICOM services or functions, or before finishing the DICOM Test Tools,
“abort” the Extend Trace Level function. The original transfer syntaxes will be set
again.
n Merge Trace Level
The following trace levels may be enabled to provide more detailed information in the
log file merge_stu.log. This log file may be displayed under “Analysis - Examine Logs”.
See also the example of an association with trace level T2, T3, T7 and T9 in the
appendix.
- T1
This trace level does not affect the mergecom.log file.
- T2 Data Set
This trace level shows the attributes of the transferred message, e.g. the image
header attributes or the attributes within a DICOM message.
Trace level T2 also shows patient data in the log file. For this reason, “Patient Data Ac‐
cess” is required for remote access.
- T3 Association Negotiation
Every DICOM communication starts with the association negotiation. The initiator
(SCU) sends a list of all supported image objects and transfer syntaxes to the re‐
mote system (SCP). The AETs of both systems are also displayed on the T3 level.
The SCP responds with the status (accept or reject) of the image objects and selects
one of the proposed transfer syntaxes.
- T4 Rejection of Incoming Messages
If incoming associations are automatically rejected (IP address not known), log mes‐
sages will be displayed on this trace level.
- T5 Regular and Extended Regulations
Logs messages relating to regular and extended regulations.
- T6 Mergecom Configuration Files
At this trace level, the related mergecom.ini, mergecom.pro, mergecom.app, and
mergecom.srv files will be written to the mergecom.log file. This may be helpful in
analyzing the log file, however, note that analysis requires a large amount of space
in the log file.
- T7 Command Set
Following the association negotiation, a command set (attributes with group 0) will
be transferred. Before sending, for example, an image, the command set will tell
the remote system the type of image object (SOP Class UID such as CT, RF, ...) to be
transferred, including the UID of the image. The response command set after each
image will show the status of the transfer, where status = 0 means a successful
transfer.
- T8 Streaming Messages
Log messages relating to the streaming in and out of messages and file objects are
displayed on the T8 level.
-
T9 PDU Level
The entire DICOM association is displayed on the PDU level (Protocol Data Unit).
Each PDU with a maximum size defined during the association negotiation will be
displayed in one line.
The association negotiation will be shown in greater detail.
T9 is the only way of displaying the association release request and response at the
end of an association.
Patient Data Access
In case of remote access to the DICOM Service Tools, viewing patient-relevant data
(name, id, ...) is not permitted. However, if you enable trace level T2, patient data will be
displayed in the log file. Therefore, the customer has to provide additional access rights,
allowing the service engineer to view patient-relevant data. To obtain these rights, the
service engineer has to enter his name and send a “Patient Data Access” request to the
customer's user interface.
n Please enter your name
Enter the name of the remotely logged in local service engineer who requires Patient
Data Access rights.
n Request PDA
When you select this button, an additional selection item (Patient Data Access) will be
activated in the customer user interface under “Option - Remote Access”. Additionally,
the name of the service engineer will be displayed. The customer has to select this
menu item to permit trace level T2 to be activated in the log file.
Dump Message
The image header information of images captured by the Test Receiver (simulate local/
remote receiver) and sent via “Export to Offline” from the own customer user interface or
copied manually into the %MEDHOME%\service\dst\img directory, will be displayed by
different header dump tools. The image has to be selected from a given selection list.
Please note that all saved files may be removed when exiting the DICOM Test Tools (se‐
lectable).
Fig. 103: Dicom Dump Message mc3list
Verify Message
The image header information of images captured by the Test Receiver (simulate local/
remote receiver) and sent via “Export to Offline” from the own customer user interface or
copied manually to the %MEDHOME%\service\dst\img directory, will be evaluated for
DICOM conformity. Please note that not all image header attributes marked "Error" are in
violation of the DICOM Standard. For example, missing or wrong attributes will be dis‐
played even if they are optional attributes. The tool provides a means of identifying the
nature of such “Error” messages. Each indicated header attribute should also be verified
manually using the DICOM Standard.
Compare Message
Two images captured by the Test Receiver (simulate local/remote receiver) and sent via
“Export to Offline” from the own customer user interface or copied manually to the
%MEDHOME%\service\dst\img directory, will be compared. The message has to be se‐
lected by the user from a given selection list.
The following example shows a possible test scenario:
n Send an image to a remote DICOM node.
n Simulate the remote node and resend the same image. This image will be stored on
the hard disk in DICOM format.
n Simulate the local receiver and send the image from the remote system to the local
system. This image will also be stored on the hard disk in DICOM format.
n Compare the sent image with the received image.
Examine Logs
This menu item displays the log directory including the mergecom.log files of the appro‐
priate DICOM services. Choose the process for which you want to see the log file:
Merge log files
The log file is displayed when you click the appropriate file name.
Fig. 108: Dicom Examine Logs menu
Display Image
DICOM images captured by the Test Receiver (simulate local/remote receiver) and sent via
"Export to Offline" from the own customer user interface or copied manually to the
%MEDHOME%\service\dst\img directory, will be displayed. The image has to be selec‐
ted by the user from a given selection list.
The viewer is a Java applet that does not support all types of DICOM images. If the
images cannot be displayed properly, you need to transfer them to your PC and display
them with other viewer applications, such as the MV300 Viewer.
- Multiframe images - only the frame in the middle of the sequence will be displayed
- Images that do not have the attributes of group 2 (part 10 header for offline images)
Display Print
With this option, the bitmaps generated by the camera simulator will be displayed on the
screen. Please note that the bitmap is exactly like the scanning array of the laser camera,
i.e., the images are mirrored, since the image is printed on the back side of the film. The
pictures are in BMP (Windows bitmap) format. They are also located in the %MEDCOM%
\service\dst\img directory, and may be copied to a floppy disk for further evalua‐
tion.
8.10.1 General
8.10.1.1 Introduction
The service application File & Image Tools provides functionality for transferring file(s)
and medical image(s) from a syngo-based system to a remote computer, e.g., a remote
server or a service laptop, and vice versa. Raw data can be handled the same way as im‐
ages if they are stored as a DICOM object in the database.
8.10.1.2 Features
The File & Image Tools functionality can be divided into the following main features:
n Transfer file(s) and image(s) from the system to a remote computer and vice versa
n Extract file(s) or image(s) to be transferred
n Display the image header
n Display / modify the Transfer List of the extracted file(s) and image(s)
The following transfer modes are available:
n Transfer to system, by means of a transfer from a remote computer (e.g., Remote
Server) to the system.
n Transfer from system, by means of a transfer from the system to the remote comput‐
er.
n The Transfer Manager mechanism supports two transfer start times: immediate
(transfer begins when you select a file and then activate the transfer with the ’Go’ but‐
ton) and preferred (transfer is scheduled for a later date).
8.10.2 Functions
n Source
The Source selection box contains a list of applications that can be executed within
the File & Image Tools service function. When you select an item from the Source
list, the Action button is added to the Navigation frame.
n Navigation bar
- Home
Brings you back to the Home Page.
- Help
Launches the Online Help window.
8.10.2.2 Modes
The File & Image Tools function allows a bi-directional transfer of any file from the sys‐
tem to a remote location, such as a Remote Server or PC, or vice versa. A modem and
router connection is supported. User interaction takes place via the Action item and sup‐
ports two transfer modes (Transfer from system / Transfer to system).
n Configuration
Please note that the File & Image Tool requires the FTP Target information from the
remote computer. When a transfer is initiated, the remote computer data is verified in
the target list. The target list has to be configured in the Configuration menu. Please
refer to the Online Help of the Configuration/Service/FTP service function for more
information on adding or modifying FTP targets. Also, refer to the Remote Server doc‐
umentation (not part of Service Software Online Help) for detailed information re‐
garding the prerequisites for adding a system to the Remote Server.
n FTP Protocol
All transfers are based on the FTP protocol. Once a transfer is started, the system ini‐
tiates an FTP session to the remote computer and logs into the rdiagftp account. If
authentication is successful, the transfer becomes active.
When the error message A connection with the server could not be established ap‐
pears in a pop-up window, verify that the FTP server (receiver) on the remote computer
has been started and configured properly. Also, ensure that the FTP account password
has been configured correctly.
n File Name
The transferred file name on the remote computer has the following format:
<modality><serial number>_<original filename>
Example: mr275_AcrobatInstall.log
<material-number>_<serial number>_<original filename>
Example: 01234567_275_AcrobatInstall.log
The transferred DICOM object name on the remote computer has the following for‐
mat:
<modality><serial number>_<DICOM object Loyd-number>.img
Example: mr275_2.0.21456.img
<material-number>_<serial number>_<DICOM object Loyd-number>.img
Example: 01234567_275_2.0.21456.img
Transferred data is not encoded or compressed by the File & Image Tool transfer mech‐
anisms.
n Immediately
Starts the transfer once you select a file/image and click the Go button.
If transfer is interrupted, e.g., the communication line is hung up, the Transfer Manag‐
er will respond by re-attempting to transfer the file/image to the remote computer. In
this case, the transfer behaves like a preferred transfer.
When you start the service software as a local user, the system first establishes a con‐
nection to the remote computer. Afterwards, you can select the file to be transferred.
For remote users, the existing connection is used for file exchange.
n Preferred
Initiates an unattended batch transfer.
Once the user has initiated a preferred transfer time, a batch transfer queue is added
to the Transfer Manager, and the system will try and establish a connection to the re‐
mote computer at the pre-defined time (local time + selected hour(s)). A transfer will
be restarted automatically if the transfer was not completed successfully (e.g., the line
was disconnected, or remote access was set to “No Access”).
At first, an immediate retry is attempted 5 times. If this is not successful, the retry is
queued again after 1, 6, 12, and 24 hours or when the system is booted. The 24 hour
retry is performed for a maximum of 7 days.
The Transfer to system function is available only in connection with a Remote Serv‐
er. Refer to the Remote Server manual for information on how to add a system on the
Remote Server.
n Source
The Source selection box contains a list of applications that can be executed within
the File & Image Tools service function. When you select select an item from the
Source list, click the Action button to add the Patient Data Access section to the nav‐
igation frame.
n Action
The Action selection box is context-sensitive and contains all Action items available
for the selected Source. When you select an item from the Action list, the contents of
the function frame (right-hand screen) will change accordingly.
n Patient Data Access
Patient Data Access controls whether the patient name or the Loyd number is dis‐
played to select the patient images.
- Enabled
The patient name is displayed.
- Disabled
The Loyd number is displayed.
- Please enter your name
Enter your name.
- Request PDA
When you click the Request PDA (Patient Data Access) button, the request for ac‐
cessing and displaying the patient name in the function frame will be sent to the
local operator.
n Navigation bar
- Home
Brings you back to the home page.
-Help
Launches the Online Help file.
The following step-by-step instructions show the procedure to enable Patient Data Ac‐
cess.
Request from the remote user
The service technician is logged in remotely and needs to transfer images with Patient
Data Access disabled. If he continues without requesting Patient Data Access, the pa‐
tient images can be selected by the Loyd number. If the correct Loyd number is not avail‐
able, he has to submit a request for Patient Data Access to the local operator by entering
his name in the Please enter your Name field and clicking the Request PDA button.
Fig. 115: Patient Data Access Request (PDA)
When you confirm the pop-up, the following File & Image Tools/Image window will be
automatically displayed.
Patient Data Access is now enabled, and patient information will be displayed. Patient
Data Access is active for the duration of the remote service session. For example, if you
exit the File & Image Tools to perform another service function and then come back to
the File & Images Tools, the Patient Data Access remains active until the remote user
closes the remote service session.
8.10.3 Source
8.10.3.1 Image
This chapter contains all Action items with regard to the transfer of DICOM Objects (e.g.,
images and raw data).
There is no difference between extracting and transferring a medical DICOM image or a
raw data object since both DICOM objects are stored in the syngo database and are trea‐
ted the same way.
Patient information can only be accessed remotely if the customer has released the Pa‐
tient Data Access. Therefore, the graphical user interface looks different depending on
whether Patient Data Access is enabled or disabled (see chapter ( Patient Data Ac‐
cess / Page 203) for more details).
All confidential patient information is removed from the DICOM object header prior to an
image/raw data transfer or when you use the Extract only image function.
n Source
The Source selection box contains a list of applications that can be executed within
the File & Image Tools service function. When you select select an item from the
Source list, click the Action button to add the Patient Data Access section to the nav‐
igation frame.
n Action
The Action selection box is context-sensitive and contains all Action items available
for the selected Source. When you select an item from the Action list, the contents of
the function frame (right-hand screen) will change accordingly.
n Patient Data Access
When the Files & Image Tools are started locally, Patient Data Access is always ena‐
bled and cannot be disabled.
n Navigation bar
- Home
Brings you back to the home page.
- Help
Launches the Online Help file.
n Patient
The Patient selection box contains a list of all patients available on the system. When
you select an item from the patient list, the Study list is automatically updated.
n Study
The Study selection box contains a list of all studies available for the selected patient.
When you select an item from the Study list, the Series list is automatically updated.
n Series
The Series selection box contains a list of all series available for the selected study.
When you select an item from the Series list, the image thumbnails will be displayed
automatically if the Show Thumb Nails box has been checked.
n Selected Images
Here, you will find the images already selected for transfer to the remote computer.
You can select an image by clicking the image icon or the corresponding image num‐
ber.
n Images
The image icons will be displayed here. Below the image, you will find the image
number and the Loyd number. The Loyd number identifies the image in the syngo da‐
tabase. The Images menu also supports multiple selections. To make multiple selec‐
tions, press and hold the CTRL key and click the images you want to select.
n To Target
Identifies the remote computer. This is either the Remote Server identification (if you
are logged in through the Remote Server) or the remote PC identification. Targets can
be added or modified in the configuration using Service/FTP.
n When
Select the appropriate transfer start time. Either immediately (start now) or prefer‐
red (start later at 22:00). For more details on the transfer start time, see chapter
( Start Time / Page 202).
n Action Bar
- Delete
The highlighted image in the Selected Images menu will be removed from the
transfer list once Delete is clicked.
- Reset
Removes all entries from the transfer list in the Selected Images menu.
- Go
When a rather large file is transferred, a new window, which shows the file transfer
progress, is opened. Each file selection will open another window in order to trans‐
fer files in parallel.
Fig. 123: Tranfer progress
n Target
Identifies the remote computer. This is the Remote Server identification (if you are
logged in through the Remote Server) or the remote PC identification. Targets can be
added or modified in the configuration using Service/FTP.
n % done
Indicates the progress of the file transfer in percent.
n Retry Count
Shows the number of immediate transfer retries. The immediate transfer will be stop‐
ped after 5 attempts, and the job will be queued for a preferred transfer. Please refer
to chapter ( Start Time / Page 202) for more details on the immediately/preferred
transfer start time.
n Transfer Status
Displays the actual status of the transfer. This can be an error message or information
regarding the transfer itself.
n Abort
Aborts the file transfer function and removes it from the transfer manager queue.
Extract Only
The Extract Only function prepares images for transmission, so that they can be picked
up later on request. For this purpose, the selected images are copied to the %medhome%
\service\extract1 directory. Use the Extract List / Transfer from system (see chapter
( Extract List / Page 223)) functions to transfer the extracted images, or use the Trans‐
fer list / Show/Delete (see chapter ( Transfer List / Page 227)) function to show or de‐
lete the extracted DICOM objects.
Fig. 124: Image Extract only
n Patient
The Patient selection box contains a list of all patients available on the system. When
you select an item from the patient list, the Study list is automatically updated.
n Study
The Study selection box contains a list of all studies available for the selected patient.
When you select an item from the Study list, the Series list is automatically updated.
n Series
The Series selection box contains a list of all series available for the selected study.
When you select an item from the Series list, the image thumbnails will be displayed
automatically if the Show Thumb Nails box has been checked.
n Selected Images
Here, you will find the images already selected for the transfer to the remote comput‐
er. You can select an image by clicking the image icon or the corresponding image
number.
n Images
The image icons will be displayed here. The image number and the Loyd number are
displayed below the image. The Loyd number identifies the image in the syngo data‐
base. The Images menu also supports multiple selections. To make multiple selec‐
tions, press and hold the CTRL key and click the images you want to select.
n to Target
Identifies the remote computer. This is either the Remote Server identification (if you
are logged in through the Remote Server) or the remote PC identification. Targets can
be added or modified in the configuration using Service/FTP.
n Show Thumb Nails
Images are displayed as image thumbnails by default. If you expect too many images
and want to save transfer time, you can deselect this option to display the image
numbers instead of the images.
Fig. 125: Image numbers only
n Action Bar
- Delete
The highlighted image in the Selected Images menu will be removed from the
transfer list once Delete is clicked.
- Reset
Removes all entries from the transfer list in the Selected Images menu.
- Go
When a rather large file is transferred, a new window, which shows the file transfer
progress, is opened. Each file selection will open another window in order to trans‐
fer files in parallel.
Fig. 126: Tranfer progress
Display Header
To find system errors without viewing the whole image, only the anonymous header in‐
formation of an extracted DICOM object (image or raw data) will be displayed. The extrac‐
ted header information will be displayed in a separate browser window.
First, select the appropriate image with the header information that you are interested in:
n Patient
The Patient selection box contains a list of all patients available on the system. When
you select an item from the patient list, the Study list is automatically updated.
n Show Thumb Nail checkbox
Images will be displayed as image thumbnails by default. If you expect too many im‐
ages and want to save transfer time, you can deselect this option to display the image
numbers instead of the image thumbnails.
n Study
The Study selection box contains a list of all studies available for the selected patient.
When you select an item from the Study list, the Series list is automatically updated.
n Series
The Series selection box contains a list of all series available for the selected study.
When you select an item from the Series list, the image thumbnails will be displayed
automatically if the Show Thumb Nails box has been checked.
n Images
The image icons will be displayed here. The image number and the Loyd number are
displayed below the image. The Loyd number identifies the image in the syngo data‐
base.
Once you click on the image thumbnail or the image number, a separate browser win‐
dow will be opened with the detailed DICOM header information.
There is a difference between how the local and the remote access mode present the
header information, as shown in the figures below. In remote access mode, the partic‐
ular patient information is anonymized to comply with legal regulations.
Use the Exit button in the Navigation bar to close this window.
8.10.3.2 File
This chapter contains all Action items regarding the transfer of a File.
Only files that are not allocated by the system can be transferred. If you need to transfer
an allocated file, you need to find out which application is allocating the file. Stop that
application with the appropriate service tool.
Images and raw data cannot be transferred with the File function. Please refer to chap‐
ter ( Image / Page 207) for more details on the image transfer functions.
n Source
The Source selection box contains a list of applications that can be executed within
the File & Image Tools service function. When you select an item from the Source
list, the Action button is added to the Navigation frame.
n Action
The Action selection box is context-sensitive; it contains all Action items that are
available for the selected Source. When you select an item from the Action list, the
contents of the function frame (right-hand screen) will change accordingly.
n Navigation bar
- Home
Brings you back to the home page.
- Help
Launches the Online Help file.
Transfer to system
The Transfer to system function transfers files from a remote computer to the system.
All files will be transferred to the %medhome%\service\incoming 1 directory.
Make sure that the file(s) you want to transfer is/are located on the remote computer. The
file(s) must be located in the <anonymous FTP>/outgoing/<modality> (xx is the
syngo modality; it is to be replaced with the modality, for example, MR or CT) directory on
the remote computer.
Fig. 132: File transfer to the system
n File Type
This selection box cannot be changed.
n from Source
Identification of the remote computer. This must be the remote computer that you
want to transfer the files from.
n Remote Directory
Here you can browse through the directory structure of the remote computer, similar
to Microsoft Windows Explorer. As a default, the system points to the <anonymous
FTP>/outgoing/<modality> (xx is the syngo modality; it is to be replaced with the mo‐
dality, for example, MR or CT) directory on the remote computer.
Directories are enclosed with “<>”. Click a directory name only once to open its con‐
tents.
At least one file has to be selected before the Go button in the Navigation bar be‐
comes functional. To select a file for a file transfer, click the file to highlight it. Multi‐
ple file selections are also supported. To select multiple files, press and hold the CTRL
key and click the next file to be selected. To select a range of files, select the first file,
press and hold the SHIFT key, and click the last file to be selected.
n Filter
With the dialog box, you can filter the files to be displayed; e.g., *.txt: all files with the
extension ’.txt’ are displayed.
n Refresh
Refreshes the contents of the Remote Directory.
n Go
When a rather large file is transferred, a new window, which shows the file transfer
progress, is opened. Each file selection will open another window in order to transfer
files in parallel.
Fig. 133: Tranfer progress
Extract Only
The Extract Only function prepares files for transmission, so that they can be picked up
later on request. For this purpose, the selected files are copied to the %medhome%\serv-
ice\extract1 directory. Use the Extract List / Transfer from system (see chapter
( Extract List / Page 223)) functions to transfer the extracted files, or use the Transfer
List / Show/Delete (see chapter ( Transfer List / Page 227)) function to show or delete
the extracted files.
Images and raw data cannot be extracted using the File / Extract Only function. Please
use Image / Extract Only (see chapter ( Image / Page 207) for more detailed informa‐
tion).
n File Type
This selection box cannot be changed.
n Site Directory
Here you can browse through the directory structure of the system, similar to Micro‐
soft Windows Explorer.
Directories are enclosed with “<>”. Click a directory name only once to open its con‐
tents.
At least one file has to be selected before the Go button in the Navigation bar be‐
comes functional. To select a file for a file transfer, click the file to highlight it. Multi‐
ple file selections are also supported. To select multiple files, press and hold the CTRL
key and click the next file to be selected. To select a range of files, select the first file,
press and hold the SHIFT key, and click the last file to be selected.
n Filter
With this dialog box, you can filter the files to be displayed; e.g., *.txt: all files with the
extension ’.txt’ are displayed.
n Action Bar
- Refresh
Refreshes the contents of the Site Directory.
n Source
The Source selection box contains a list of applications that can be executed within
the File & Image Tools service function. When you select an item from the Source
list, the Action button is added to the navigation frame.
n Action
The Action selection box is context-sensitive; it contains all Action items that are
available for the selected Source. When you select an item from the Action list, the
contents of the function frame (right-hand screen) will change accordingly.
n Navigation Bar
- Home
Brings you back to the home page. .
- Help
Launches the Online Help file.
Show/Delete
The Download List / Show/Delete function displays the files that have been transferred
to the system. Please refer to chapter ( Transfer to system / Page 218) for more informa‐
tion on how to transfer files to the system.
Fig. 136: Download List Show/Delete
n Site Directory
Here you can browse through the directory structure of the system, similar to Micro‐
soft Windows Explorer.
Directories are enclosed with “<>”. Click a directory name only once to open its con‐
tents.
At least one file has to be selected before the Go button in the Navigation bar be‐
comes functional. To select a file for a file transfer, click the file to highlight it. Multi‐
ple file selections are also supported. To select multiple files, press and hold the CTRL
key and click the next file to be selected. To select a range of files, select the first file,
press and hold the SHIFT key, and click the last file to be selected.
n Filter
With this dialog box, you can filter the files to be displayed; e.g., *.txt: all files with the
extension ’.txt’ are displayed.
n Action Bar
- Refresh
Refreshes the contents of the Site Directory.
- Delete
The highlighted image in the Selected Images menu will be removed from the
transfer list once Delete is clicked.
n Source
The Source selection box contains a list of applications that can be executed within
the File & Image Tools service function. When you select an item from the Source
list, the Action button is added to the navigation frame.
n Action
The Action selection box is context-sensitive; it contains all Action items that are
available for the selected Source. When you select an item from the Action list, the
contents of the function frame (right-hand screen) will change accordingly.
n Navigation Bar
- Home
Brings you back to the home page.
- Help
Launches the Online Help file.
n to Target
Identifies the remote computer. This is either the Remote Server identification (if you
are logged in through the Remote Server) or the remote PC identification. Targets can
be added or modified in the configuration using Service/FTP.
n When
Select the appropriate transfer start time. Either immediately (start now) or prefer‐
red (start later at 22:00). For more details on the transfer start time, refer to chapter
( Start Time / Page 202).
n Site Directory
Here you can browse through the directory structure of the system, similar to Micro‐
soft Windows Explorer.
Directories are enclosed with “<>”. Click a directory name only once to open its con‐
tents.
At least one file has to be selected before the Go button in the Navigation bar be‐
comes functional. To select a file for a file transfer, click the file to highlight it. Multi‐
ple file selections are also supported. To select multiple files, press and hold the CTRL
key and click the next file to be selected. To select a range of files, select the first file,
press and hold the SHIFT key, and click the last file to be selected.
n Filter
With this dialog box, you can filter the files to be displayed; e.g., *.txt: all files with the
extension ’.txt’ are displayed.
n Refresh
Refreshes the contents of the Site Directory.
n Go
When a rather large file is transferred, a new window, which shows the file transfer
progress, is opened. Each file selection will open another window in order to transfer
files in parallel.
Fig. 139: Tranfer progress
Show/Delete
With Show/Delete, you can display and/or delete previously extracted images, raw data,
and other files from the extract list. Refer to Image / Extract Only and File / Extract Only
for more information on extracting DICOM objects and files.
All files in the %medhome%\service\extract1 directory will be available for selection.
Scroll up and down the menu to browse through the entire list.
Fig. 140: Extract List Show/Delete
n Site Directory
Here you can browse through the directory structure of the system, similar to Micro‐
soft Windows Explorer, beginning at the %medhome%\service\incoming directory.
Directories are enclosed with “<>”. Click a directory name only once to open its con‐
tents.
At least one file has to be selected before the Go button in the Navigation bar be‐
comes functional. To select a file for a file transfer, click the file to highlight it. Multi‐
ple file selections are also supported. To select multiple files, press and hold the CTRL
key and click the next file to be selected. To select a range of files, select the first file,
press and hold the SHIFT key, and click the last file to be selected.
n Filter
With this dialog box, you can filter the files to be displayed; e.g., *.txt: all files with the
extension ’.txt’ are displayed.
n Action Bar
- Refresh
Refreshes the contents of the Site Directory.
- Delete
The highlighted image in the Site Directory menu will be removed from the trans‐
fer list once Delete is clicked.
n Source
The Source selection box contains a list of applications that can be executed within
the File & Image Tools service function. When you select an item from the Source
list, the Action button is added to the navigation frame.
n Action
The Action selection box is context-sensitive; it contains all Action items that are
available for the selected Source. When you select an item from the Action list, the
contents of the function frame (right-hand screen) will change accordingly.
n Navigation Bar
- Home
Brings you back to the home page.
- Help
Launches the Online Help file.
Show/Delete
Show/Delete displays the transfer manager jobs pending for the specified target and may
remove these jobs from the transfer list.
To display or remove pending batch jobs for a specific target, select the appropriate pend‐
ing batch job. Only one pending batch job can be selected at a time.
n Transfer Status
Indicates the progress of the transfer.
- queued
Has been added to the transfer manager queue.
- done
Has been executed successfully and will be automatically removed from the queue
after approximately 5 minutes.
- failed
When a transfer fails, the system will retry automatically. Please refer to chapter
( Start Time / Page 202) for more details on the image transfer functions.
- cancelled
If a transfer is aborted, the job will be relegated to cancelled status.
- initial
The transfer manager initializes the queue job. When the queue job is successfully
initialized, the job will be relegated to queued or active status.
- active
The queued job is executing.
- dialing
The system establishes a modem connection to the remote computer.
- connecting
The TCP/IP connection to the remote computer is being established.
- transferring
The file is being transferred (copied) to/from the remote computer.
- disconnecting
The TCP/IP connection to the remote computer is being disconnected.
- hanging up
The modem connection is being disconnected.
n Transfer Status Details
Displays the actual status of the transfer. This can be an error message or information
regarding the transfer itself.
n Abort Flag
- Queued
This job is entered to the transfer manager queue.
- Aborted
The queued job will be removed from the transfer manager queue.
n Total Bytes to Transfer
Amount of bytes that have to be transferred to the remote computer.
n Actually Transferred Bytes
Total amount of bytes transferred to the remote computer.
n Retry Limit
Shows the number of retries allowed; the number has been fixed to 5 retries.
n Retry Count
Shows the number of transfer retries. The transfer will be stopped after 5 attempts.
n Transfer Time
Shows the time when the file was transferred.
n Action Bar
- Refresh
Refreshes the content of the transfer manager queue.
- Delete
The highlighted selection in the transfer manager queue will be removed from the
transfer list once Delete is clicked.
8.11.1 General
8.11.1.1 Introduction
AutoReport is used during various work functions:
n Once configured and enabled, AutoReport is automatically activated when the various
filter criteria are met. This supports the service person during troubleshooting. In par‐
ticular, sporadic problems can be located and reported to the Service Center.
n In addition, AutoReport can trigger a preferred file transfer to collect certain system
reports for further evaluation at the Service Center.
n The AutoReport tool can send a system report to any mail account at Service Head‐
quarters.
n FTP (File Transfer Protocol) is used for file transfer.
n SMTP (Simple Mail Transfer Protocol) is used for mail communication.
8.11.1.2 Features
AutoReport tool features:
n Sending of various notifications, from mail only to mail messages including command
output or file attachments, to a particular user at the Service Center.
n Definition of simultaneous, multiple reports.
n Monitoring of selectable files, Time Triggered and Event Triggered.
- Time Triggered means that the AutoReport application searches for a word or a
combination of words in a defined ASCII file or the event log at an adjustable time.
- Event Triggered means that AutoReport becomes active when a defined event oc‐
curs, e.g., the event DISK_FULL triggers AutoReport to send mail to Headquarters,
or when a file has changed.
n Collecting of system data at an adjustable time and sending it to Headquarters at flexi‐
ble intervals.
8.11.2 Functions
n REPORT
The Report selection box contains a list of system-specific reports.
n Enabling Status
The Enabling Status selection box indicates whether the report is enabled or disa‐
bled. To change the status, you have to open the report via the REPORT selection box
and modify the Active checkbox. When this box is checked, the report is enabled.
When you click Save in the Action bar, the status under Enabling Status will be upda‐
ted.
When a report or a template form has been selected from the REPORT selection box, the
full status of the report is shown in the function frame.
Fig. 144: Example - Auto Report Template
n Active
This checkbox is used to enable or disable a report. The action takes effect when the
change is saved via the Save button in the Action bar. The status of this checkbox is
also displayed in the left frame under Enabling Status.
n Name
When the TEMPLATE has been selected, you must enter the name of the report to be
created. If you have selected an existing report and then changed the name, a new
report will be created when the Save button is clicked.
When you rename a report, the “old” report that has been used as a template does not
get removed or modified in any way.
n Target
Displays the remote computer to which the mail is to be sent. It must be configured in
the Service Configuration function. Mail can be sent to a modality-specific account
on the Remote Server (e.g., rdiag_ct) or to a specific user (e.g., Dieter.Muster‐
[email protected]) at the Service Center.
n Save
When you click Save in the Action bar, the changes made to the currently selected re‐
port are stored.
n Delete
The currently displayed report will be removed when you click Delete.
n Begin
The Begin selection box allows you to define the start date of the reporting period.
When using the Report TEMPLATE, the default start date is the creation date.
n End
The End selection box allows you to define the end date of the reporting period. When
using the Report TEMPLATE, the default end date is one year after the Begin date.
n Source
You may choose between Event Log as the default or any File to be monitored. When
Event Log is selected, all events that are recorded in the event log / customer log will
be sampled and evaluated. When File is selected, pattern matching of the file con‐
tents will be performed. The file name must be entered in the Sample what? frame.
The file option only works with ASCII files.
If the Event Log is selected in the Sample source? frame, all events that are recorded in
the event log files will be sampled and evaluated. Various filter criteria (Severity, Message
ID, Source, Domain) that are also used in the Event Log Reader application can be selec‐
ted. For detailed information on these filters, please refer to the Online Help for the
Event Log Reader.
Fig. 146: Sample what? (Sample Source: Event Log)
n Severity
Classification of the error message. Possible selections are Error, Warning, Informa‐
tion, or All.
n Search Pattern
When a text string is entered, pattern matching is performed with the message text in
the event log file. Wild cards are supported.
n Message ID
Filters on specific Message IDs in the event log file. In the example above, the Mes‐
sage ID 102, which will send a message to Headquarters when the user successfully
logs into the service software, was entered.
n Mode
Toggles between Time Triggered and Event Triggered. If Event Triggered is selected,
the AutoReport will be activated as soon as the defined event occurs; the frame Sam‐
ple when? displays Continuously only. If Time Triggered is selected, the system will
perform pattern matching at the time that has been set in the parameters in the Sam‐
ple when? frame.
n Domain
Allows you to select events from a certain domain (Application, CustomerLog, Se‐
curity, or System).
n Source
Allows you to specify different system software components, e.g., CSA_SAM (SAM ap‐
plication).
2) Sample source? is set to File
If File is selected in the Sample source? frame, the Sample what? frame displays fields that
are necessary for sampling a defined file with a particular search pattern.
Fig. 147: Sample what? (Source: File)
n File Name
Specify the name of the file which is to be sampled. Wild cards are supported.
n Search Pattern
When no Search Pattern is entered, AutoReport will send a mail when the file has
been created or changed; otherwise, a mail will be sent when the Search Pattern has
been found by a sample.
n Mode
Toggles between Time Triggered and Event Triggered. If Event Triggered is selected,
the AutoReport will be active as soon as the defined event occurs; the Sample when?
frame displays Continuously only. If Time Triggered is selected, the system will per‐
form pattern matching at the time that has been set in the parameters in the Sample
when? frame.
n Lines
When a search pattern is entered and the Mail: with partial attachment parameter in
the Send what? frame is selected, this value defines the number of Lines to be added
to the mail. The occurrence of the Search Pattern is in the center of the added lines.
n Continuously
Sampling is performed continuously; AutoReport starts sending the mail when the
event defined by the filters in the Sample what? frame meets the conditions.
2) Mode: Time Triggered
Fig. 149: Sample when? Time Triggered
n Continuously
Specifies a time for continuous sampling and can be adjusted with the Sample times
parameters.
It is also possible to enter several sample times.
Use a semicolon (;) to separate the entered values, e.g., 14:45;15:00;15:15.
n Daily
Select hours and minutes from the corresponding menus.
n Weekly
Select the day of week and the hours and minutes from the corresponding menus.
n Monthly
Select the day of month and the hours and minutes from the corresponding menus.
n Mail
with no attachment only sends a notification mail with the name of the file that was
entered in the Sample what? frame.
with full attachment sends the whole file attached to the mail.
Partial attachment only sends those lines of the sampled file which meet the filter
criteria that were entered in the Sample what? frame.
as separate file(s) forwards the selected report file(s) to a remote computer using
FTP file transfer, and sends a mail to the remote target. In this case, the FTP target
address can be specified in a selection box. If you cannot find the proper FTP target,
you have to add the FTP target in the Service Configuration function.
as separate file(s) without mails forwards the selected report file(s) to a remote
computer using FTP file transfer, and does not send a mail to the remote target. In
this case, the FTP target address can be specified in a selection box. If you cannot find
the proper FTP target, you have to add the FTP target in the Service Configuration
function.
The various Mail options only work with the Sample source? mode file.
n Command
The output from the executed application or DOS command entered will be added to
the mail message.
n At once
The AutoReport is generated and sent immediately to the selected target.
n Daily
If Dailyis selected, the selection boxes Hour and Minute will appear. Select hours and
minutes from the corresponding menus.
n Weekly
If Weeklyis selected, the selection boxes Day, Hour, and Minute will appear. Select
day of week, hours, and minutes from the corresponding menus.
n Monthly
If Monthlyis selected, the selection boxes Day, Hours, and Minute will appear. Select
day of month, hours, and minutes from the corresponding menus.
The forms are fully interactive and the parameters are interdependent.
n Check and, if necessary, adjust the information entered into the Sample source?,
Sample what?, Sample when?, and Send when? fields according to your require‐
ments.
n Verify the Enabling Status, Begin, and End date of the new job and the notification
target.
n Finally, save the modified job by clicking the Save button. A message box appears to
confirm that the data was saved successfully, and the new AutoReport name immedi‐
ately appears under Enabling Status and is marked “Active” by default.
n Close the AutoReport by clicking the Home button in the Navigation bar.
8.12 Utilities
8.12.1 General
8.12.1.1 Introduction
This section describes the Utilities functions.
Fig. 154: Source
8.12.1.2 Features
With Escape to OS, you can enter any command at the OS level.
Send Message is useful for sending a message to the site.
The Session List provides information about the active sessions.
The Process List shows all active processes.
8.12.2 Functions
8.12.2.1 Escape To OS
This function enables you to execute a command-driven program on the system. It pro‐
vides the capabilities of a regular Command Prompt on the local system. Several prede‐
fined commands are available:
CAUTION
This function is mainly used with the support of Headquarters.
Some commands may effect the syngo functionality.
You need to enter your name. This name is used in the log file to indicate who accessed
the patient data.
This is necessary to ensure patient data security.
Fig. 159: SAM requests Patient Data Access at the remote system
SAM requests patient data access at the system and the user at the system can enable the
access.
Then, the following pop-up window is displayed:
Fig. 160: Patient Data Access changed to enabled
NT Command Interpreter
Starts a new instance of the Windows NT command interpreter CMD.EXE. This command
interpreter accepts commands as they are typed in the Command Prompt window. Any
program can be started, even programs with a graphical user interface. The GUI, of
course, will be started on the local system only.
Helpful Commands
For network tests:
Various commands:
The following items are checked and displayed: user environment, system environment,
current user, database environment, previous successful startups, and free space on disk.
After the first installation of the syngo software, the system will generate a checksum.
When you start this utility, the system will generate another checksum and compare it
with the previously created one.
This is a simple check to ensure that the system is not infected with viruses.
Create ServiceSaveLog
Fig. 164: Escape to OS - Create ServiceSaveLog
The description of the ServiceSaveLog is the same as for the SaveLog customer.
Please go to Back to overview and then Customer -> SaveLog.
System Information
Fig. 165: Escape to OS - System Information
System Info shows the network IP address, hostname, NT version, and service pack, as
well as the stopped and running processes.
Directory Usage
Fig. 166: Escape to OS - Directory Usage
DIRUSE displays a list of disk usage for a directory tree(s). Required parameters are listed.
To obtain the corresponding list, click Go without a parameter.
All of the system hard disks can be checked using this command.
Show Internet address will display the so-called MAC address from the Ethernet card of
the PC.
It is possible to send a message to the customer during a remote session. The CSE simply
needs to enter a text in the message text area and click the Send button to send the mes‐
sage.
As a result, the following message box will be displayed on the console.
Fig. 171: Send message - Received message from the CSE
The message box must be confirmed by the customer by clicking the OK button. The mes‐
sage text will be logged in the event log.
n Session Key
This is a session ID and does not contain the service key.
n Service Level
The service level of the remote access is displayed for each session.
n Started
The date and time at which the session is started will be displayed.
n Last Access
The date and time of the last access from each session is displayed.
n Status
Shows the actual status of a session.
n Client
Shows the IP address of the remote client.
All current sessions are displayed. Click Refresh to refresh the list.
To close all sessions, go to menu item Options -> Remote access, and switch to “no ac‐
cess”! (see also Customer UI -> Remote Service)
n Pid
Displays the ID of a process.
n Process Name
Name of the running process.
n Processor Time
Estimated processor time for a certain process.
n Privileged
Load in % of the Kernel mode.
n User
Load in % of the User mode.
n Mem Usage
Memory used for certain process.
Information is provided about the currently running process. Click Refresh to refresh the
list.
n Lifetime
Specifies the estimated lifetime of a component or process.
n Lifetime value
A number based on the "Lifetime" parameter
Fig. 175: Component Manager List - Scolled to the right
n Faults
A count of how often a component or process was terminated. Note: It is not consid‐
ered an error if, e.g., a batch file terminates a component or process.
n Path type
Type of executable. This can either be an external, backend, or frontend executable.
n On exit
Specifies whether the component or process should be restored in case of an excep‐
tion.
n Cwd
Current working directory
8.12.2.6 System
“Tune CD Burning” checks the performance of a system to ensure the data stream for CD
burning.
This information is used to ensure that the user can work properly while burning a CD.
During the burning process, data is stored at a specific location on the hard disk.
“Tune CD Burning” requires approx. 5 minutes and runs in background. The system has to
be booted after it is finished.
Fig. 178: Popup message after approx. 5 minutes.
CAUTION
When “Tune CD Burning” is running,
CDs may not be burned at the same time!
Monitor Calibration
with Minolta Luminance Meter LS100
Fig. 179: Calibrate Monitor
After selecting Go, the ActiveX control for receiving data from the LS100 is displayed.
Fig. 181: Calibrate Monitor #2
Select the COM port the luminance meter is connected to, and activate this port with the
Com Port Open button.
The calibration mode of the LS100 has to be set to “PRESET”, and the measuring mode
to“ABS”. Otherwise, a warning will be displayed.
The 17 GSDF test patterns “ddl_01.dcm” to “ddl_17.dcm” must be loaded into the syngo
viewer.
Fig. 182: Calibrate Monitor #3
To measure the luminance of the target (square region in the middle of the image), each
image must be displayed with view options “a 1:1” and “No text”.
Fig. 183: Calibrate Monitor #4
Minimize the service UI so that only the calibration image is displayed on the screen. Only
the status window that will be displayed on the right side of the screen should remain
visible.
Click the Start button to measure the first value.
The value is displayed and may be accepted or rejected.
If the value is rejected, the last measurement will be repeated.
Next, a list of all measured values will be displayed.
If the values are accepted, they will be saved in a temporary file and a monitor correction
LUT will be calculated.
The LUT file will be saved to “%medhome%\config\common\LUT\monitor.lut” and a reboot
will be initiated to activate the monitor correction.
Remove
Fig. 185: Utilities - Remove Database
You can select all databases or you can select only one database (store).
Enter one number (1-4) into the Parameters field and then click “Go”.
n 1 = All databases
Removes (2) Local Database, (3) Scheduler store and (4) Archive store.
n 2 = Local database
This is the database for patient images and patient data
n 3 = Scheduler store
The HIS / RIS orders will be stored to that store. If it is removed, a new store will be
created with the next HIS / RIS order.
n 4 = Archive store
When reading a CD, the data is stored to this archive store for fast read.
This store will be deleted automatically when you start the system or by using this fea‐
ture (Remove Database with parameter 4).
8.12.2.10 Recover CD
The customer is able to store several sessions on a single CD.
On rare occasions, it is possible that the newest session cannot be recorded correctly. In
this case, the entire CD is unreadable.
The CSE can use the “Recover CD” tool to create a new session with pointers to the last
“good” session and close the current session.
The last (“bad”) session will be lost, but all the others will be readable.
This procedure requires sufficient space on the CD and requires that the previous session
is still readable.
8.13.1 General
8.13.1.1 Introduction
Software Distribution is one of the Siemens Enhanced Productivity Services which al‐
lows remote system software updates and any other kind of remote software distribution
and installation.
Software Distribution is provided by Siemens Remote Service and requires a broadband
connection to the SRS, as well as an activated System Management Package (LSS includ‐
ing MNP) in the system.
8.13.1.2 Features
Software Distribution differs slightly in how the package transfer is initiated. The software
package can be automatically pushed to each system, triggered by the Software Distribu‐
tion Server or it can be pulled by the system from the Software Distribution Server, trig‐
gered by the software catalog in the syngo service software.
The package can not only be automatically transferred to the system, it can also be silent‐
ly installed in the system without any notification, depending on the modality type. This
is allowed only for certain kinds of software packages (e.g. virus pattern updates) and re‐
quires a one-time acceptance by the user (UI checkbox), which of course, can be modified
by the user at any time.
The software catalog can be accessed during a remote session. However, "Full Access” is
required for downloads and installations.
For systems that do not have and SRS connection, it is possible to import a software
package manually.
See ( Offline SW Pkg Import / Page 133).
8.13.2 Functions
8.13.2.1 Overview
Using the Software Distribution button from the Home Menu, the Overview Window of
the Software Catalog is automatically launched and shows the status of the actual soft‐
ware packages assigned for that system.
If the Catalog is not up-to-date (system dependant value, e.g. 24 hours), an information
pop-up is displayed.
Fig. 189: Information catalog is not up-to-date
The catalog can be refreshed by clicking the Update Catalog button in the lower right
corner of the window. The system then retrieves the actual assigned software packages
from the Software Distribution Sever and updates the table.
The following conditions can be displayed:
n available
The software package is available for download.
n transferred
The software package has already been transferred and is ready for installation.
n transfer in Progress
The download of that particular software package is in progress.
n installed
The software package is already installed.
n error
The software package has not been installed successfully.
By moving the mouse pointer over the software package name in the catalog table, a
short description of the package content is displayed in the form of a tool tip. If the pack‐
age name is clicked, a pop-up window containing a description of the package content is
shown.
In addition to the package name, the table also contains the package version, package
size, and the date of the currently shown status.
If a package is transferred and ready for installation, a notification (with a max. delay of
15min) is sent to the system user in the form of an icon in the syngo Status bar.
Fig. 190: SD Icon in Status bar
8.13.2.2 Download
The download of any software package, shown as available in the Overview menu, can
be started in the Download menu. The checkbox of the respective package has to be
marked and the download can be started by clicking the Download Button in the lower
right corner of the window.
If the link to the Download menu is disabled, the catalog needs to be updated from the
Overview menu.
The progress of the download is shown in precentage in the “progress” column of the ta‐
ble. If the download finishes successfully, the job is removed from the table and the fol‐
lowing pop-up is displayed.
Fig. 192: Download Successful pop-up
Closing or leaving the Download window, for any reason, will not interrupt the current
downloads.
The frequent refreshing of the UI is normal because of the periodical query of the down‐
load progress.
All successfully downloaded software packages are stored on the system in the “sd_store”
folder.
8.13.2.3 Install
Transferred software packages can be installed from the Install menu by clicking the In‐
stall button in the “Action” column located on the right-hand side of the table.
Fig. 193: SD Install Window
8.13.2.4 Uninstall
Previously installed software packages can be uninstalled from the Uninstall menu by
clicking the Uninstall button in the “Action” column located on the right-hand side of the
table. An additional pop-up asking for your approval is displayed before the action is per‐
formed. This only works if an uninstallation routine was provided by the installed soft‐
ware package.
Successfully uninstalled packages are removed from this table and are added to the table
in the Install Menu again.
Only those software packages, which have an unistallation routine or have been instal‐
led by Microsoft Installer (MSI-packages), are displayed in the table for uninstallation .
During normal operation, the user is informed via the icon in the syngo Status bar that a
software package has been received and is waiting for installation.
By clicking the icon, the SD User Interface is opened, so that the user can install the soft‐
ware package whenever his workflow allows it.
All the information in the UI is provided by the package itself. Without any user action,
the UI stays on the screen for a specified time period, as shown in the bottom of the UI.
After this time period elapses, the software installation request is still shown in the form
of the icon in the syngo Status bar, where it can be called up at anytime.
The action buttons available in the SD User Interface may differ depending on the pack‐
age content, e.g., a Defer button is not provided in cases of a mandatory security update,
which cannot be delayed.
Description of the action items in the SD User Interface:
n Description
Shows the detailed description of the software package content or its meaning; can
also be a complete software installation instruction.
n Install
Starts the installation of the software package. The UI, with the click of a button, then
extends to display the installation log used to follow the installation process. A pro‐
gress bar is shown as well.
Fig. 197: Installation Extended View
n Defer
The SD User Interface is closed, which means that the installation is postponed and
that the user will be requested to install the package at the next system startup or the
user can invoke it again through the icon in the Status bar.
n Defer All
If more than one package needs to be installed, several SD User Interfaces are dis‐
played consecutively. With this button, all outstanding installations are deferred.
n “Accept Silent Installation” checkbox
With this checkbox, the user can decide to no longer show the SD User Interface for
additional software packages of the current package type. This function should be
used, e.g., for frequently reoccuring virus pattern updates. The user can revoke the
approval any time via the general syngo configuration (Menu: Option/Configuration/
Software Distribution)
Fig. 198: Accept Silent Installation
For system problems, it is best to exit the "domain" at the default ‘application’
8.15 Reports
8.15.1 General
8.15.1.1 Introduction
The Report function is used to get an overall overview of the actual configuration.
It provides further access to important system log files (also via remote connection) .
8.15.1.2 Features
The information and log files are clustered in groups as follows:
n SiteInfo
n Tune-Up/QA/Tests
n Startup Process
n Remote Diagnostics
n System Management
Fig. 201: Report Overview
8.15.2 Functions
8.15.2.1 Handling
n Activate the Reports button in the Service Home Menu Navigation bar to open a sepa‐
rate window. Available log files of service programs are shown in the left frame of the
opened window. You can select an entry by clicking one of the specific reports as re‐
quired.
n Activate the Help button in the Reports Navigation bar to get context-sensitive help
information.
n Activate the Exit button in the Reports Navigation bar to close the Reports window.
8.15.2.2 SiteInfo
This menu entry provides information about the license, SAM and the configuration for
this specific site.
License
Important license information is displayed, such as hardware ID, current service key, and
the status of all available application licenses.
Fig. 202: Sample - License Report
About SAM
Displays the current version of the "Service Access Manager" (SAM). The SAM controls all
the activities within the syngo service software packages and their modules.
Configuration
A system configuration report is displayed. The report is divided into several options. Click
an option to obtain the corresponding information. The white arrow within the subtitle
bar brings you back to the top of the page.
Fig. 204: Configuration
Press “Ctrl+P” to print out the content of the Configuration Report on a local or network
printer, if configured.
Firewall
Displays the current Windows XP firewall (security) configuration. The firewall configura‐
tion displays which ports and programs are enabled on the system.
Fig. 206: Firewall Info Screen
8.15.2.3 Tune-Up/QA/Tests
This menu entry provides you with information about the status of the system with re‐
gard to:
n Tune-up
n Quality Assurance
n Test Functions (e.g. results of the latest measurements)
n Backup & Restore
n syngo startup log
Session history
Use these links for viewing the session log file. It displays the history of all measurements,
quality assurance and tests performed.
Fig. 207: Report Session History
This report shows which files / directories were saved and which programs were execu‐
ted.
Fig. 209: Backup Log
Process diagnostics
The Process Diagnostics provide central access to all available startup process log files.
An overview of all the corresponding log files is displayed in the right frame of the win‐
dow. Click one of the hyperlinks to view the desired log file.
Fig. 211: Sample Process Diagnostic
Customer Log
Use this link for viewing the Remote Diagnostics customer log which contains:
n Login trails
n Date and time of login
n Date and time of logout
n Who terminated the service session (local or remote service user)
n Service activities as defined within each service program
Click the ID number for more information about this specific message.
Fig. 214: Message Description
Sysmgmt Diagnostics
The Sysmgmt Diagnostics provides a link to all the available MNP-related log files. The log
files are located in the c:\sysmgmt\Log directory. Those files can be remotely accessed via
this link.
8.16 Help
8.16.1 General
8.16.1.1 Introduction
This section describes the Help function of the syngo service software package.
It provides brief information on the Help function.
8.16.1.2 Features
Online help is not provided in VC14.
See CB-DOC for information
8.16.2 Functions
8.16.2.2 Documentation
CB DOC:
A pop-up window appears, when you click the Documentation button in the Navigation
bar of the Help Window or within the Home Menu under Help. A default URL address for
the Online Documentation CD-ROM is displayed. Click the OK button to start the Home
Page of the Computer-Based Documentation (CB-Doc) in a separate window.
If you are logged in remotely, the default will automatically point to any local drive.
In either case, whether you are logged in remotely or locally at the customer site, you can
always change the default to access any other Web server on the network. To do so, you
have to change the URL address from file:///<CD drive>/default.htm to
http://<web_address>.
Fig. 217: URL for Online Documentation
n If the password is correct, access is granted for the Service Software application.
Fig. 221: Syngo service homepage
The <Save as> window appears behind all other open windows. Minimize the open win‐
dows until the window becomes visible.
The Log Zip tool is installed on the Artis zee system to enable automatic extraction and
compression (zip) of event logs and other logs to a specified directory in the system.
Detailed Function Description:
The following functions are performed automatically with the AXSaveLogs tool:
- with each “switch on” of the system or at 01:30 am, the event logs from the previous
day and from the current day are extracted and zipped. In addition, the files AX‐
IS_ERR.log, Dr. AXIS.log, version, Config check, Configuration Report, and some other
logs are zipped into the same file.
- All these files are zipped and saved into the file with the following naming convention:
xa100xx_tt_mm_yyyy_LogFiles.zip
- This file is saved in the directory C:\AXIOM\Log and in C:\AXIOM\Service\outgoing
- Up to 30 files (for 30 days) are saved, so when more system power-ons are performed,
the oldest file is overwritten (ring buffer). If you switch on the system more than once a
day, the file that already exists for this day is overwritten.
- The *.zip file can be created with the following command:
C:\AXIOM\AxZipTool\AxSaveLogs.vbs
or the following key combinations:
<Ctrl> + <Alt> + s
<Ctrl> + <Shift> + l
9.5.1 PING
The “PING” is used to check whether a component can be reached via the network. There
are two possible answers to the command:
n Reply; The component answers the question (“is alive”), and
n Timeout; The component cannot be reached. An answer was not transmitted within
the time window. In this instance, the configuration and the network connection for
this component must be checked.
This ping uses the host name. The corresponding IP number is used from the “hosts file”.
This file contains the mappings of IP addresses for host names.
Each entry is kept on an individual line. The IP address is placed in the first column fol‐
lowed by the corresponding host name. The IP address and the host name are separated
by at least one space.
Fig. 224: Ping with DICOM network verification
After a successful “ping”, the higher level test “DICOM ECHO” is started automatically.
Escape to OS
Pinging 157.163.196.1 with 32 bytes of data:
Parameters
-t Pings the specified computer until interrupted.
-a Resolve addresses to computer names.
-n count Sends the number of ECHO packets specified by the count. The de‐
fault is 4.
-l length Sends ECHO packets containing the amount of data specified by
length. The default is 64 bytes; the maximum is 8192.
-f Sends a Do not Fragment flag in the packet. The packet will not be
fragmented by gateways along the route.
-i ttl Sets the Time To Live field to the value specified by ttl.
-v tos Sets the Type Of Service field to the value specified by tos.
Parameters
-r count Records the route of the outgoing packet and the returning packet
in the Record Route field. A minimum of 1 and a maximum of 9
computers may be specified by the count.
-s count Specifies the time stamp for the number of hops specified by count.
-j computer list Routes packets via the list of computers specified by computer list.
Consecutive computers may be separated by intermediate gate‐
ways (loose source routed). The maximum number allowed by the
IP is 9.
-k computer list Routes packets via the list of computers specified by computer list.
Consecutive computers may not be separated by intermediate gate‐
ways (strict source routed). The maximum number allowed by the
IP is 9.
-w timeout Specifies a timeout interval in milliseconds. The destination list
specifies the remote computers to ping.
9.5.2 Netstat
This command is available only if the TCP/IP protocol has been installed.
Parameters
-a Displays all connections and listening ports; server connections are nor‐
mally not shown.
-e Displays Ethernet statistics. This may be combined with the -s option.
-n Displays addresses and port numbers in numerical form (rather than at‐
tempting name look-ups).
-s Displays per-protocol statistics. By default, statistics are shown for TCP,
UDP, ICMP, and IP; the -p option may be used to specify a subset of the
default.
-p protocol Shows connections for the protocol specified by the protocol; the proto‐
col may be tcp or udp. If used with the -s option to display by protocol
statistics, the protocol may be tcp, udp, icmp, or ip.
-r Displays the contents of the routing table.interval. Redisplays selected
statistics, pausing several seconds between each display. Press CTRL+C to
stop redisplaying statistics. If this parameter is omitted, netstat prints the
current configuration information once.
9.7.1.1 1. Generating an AXCS Trace using a Button in the <Control> <Auxiliary> Menu
n Open the menu located under <Control> <Auxiliary>.
n Click the <Dump> button to initiate an immediate dump of the last 1000 AXCS ob‐
jects.
A trace file (file name: “date_timeMANUAL_TRC.trc”), which holds the last 1000
AXCS objects, is generated under C:\AXIOM\Service\Log\AxcsTrace.
The evaluation of AXCS traces requires specific knowledge and should be performed by
development experts.
9.7.4 Problems
Generate Reports shows failures The system must be “up and running” when starting an adjustment.
n Run the AXCS test ( AXCS TEST / Page 49)and check if compo‐
nents are not ready
If one component shows not ready, mark it and use the
Reset function
If all components are not ready, switch off the RTC and
turn it on again
n Repeat the “Generate Reports” function again, if necessary.
Following Generate Reports, no After a new software installation, the tune-up results for FD calibra‐
tune-up results are visible tions are not visible unless a new calibration is performed.
Generate AXCS Trace If a REP_ERR event which was set as a trigger under Control > Aux‐
iliary > has occurred, an html file is created. This file contains the
last 1000 AXCS events prior to the trigger event.
Chapter Changes
General Remarks The following sections were changed:
n Remarks > Conventions and Abbreviations > Abbreviations:
( Abbreviations / Page 11)
- Added MLC = Controller Artis zee Cockpit
B Backup
Acronis ..................................................................................................................133
Backup & Restore (syngo) ...........................................................................................103
Backup & Restore Reports ...........................................................................................277
Backup (syngo) .......................................................................................................... 103
Boot problems
Black screen ............................................................................................................ 15
Error tab card .......................................................................................................... 15
sub-components ......................................................................................................15
Bypass ......................................................................................................................... 16
Bypass (momentarily) .................................................................................................. 18
G Gamma ......................................................................................................................115
Global Gain ................................................................................................................ 115
GND ............................................................................................................................ 12
Gray level .................................................................................................................. 114
K KPC ..............................................................................................................................11
R R+ ................................................................................................................................13
R- .................................................................................................................................13
RAC ............................................................................................................................. 12
Radiation Function Test ................................................................................................33
radiation problem ........................................................................................................ 18
Radiation Problems ...................................................................................................... 32
Radiation Release ......................................................................................................... 34
Remote Diagnostics Reports ....................................................................................... 280
Report Generation ......................................................................................................110
Reports ...................................................................................................................... 273
About SAM ............................................................................................................ 274
Backup & Restore ...................................................................................................277
Component ........................................................................................................... 303
Configuration ........................................................................................................ 275
Customer Log ........................................................................................................ 280
Firewall ................................................................................................................. 276
Functions .............................................................................................................. 273
General ................................................................................................................. 273
License ..................................................................................................................274
Process diagnostics ................................................................................................279
Remote diagnostics ............................................................................................... 280
Session history ...................................................................................................... 277
SiteInfo ................................................................................................................. 274
Startup Process ......................................................................................................279
syngo startup log ...................................................................................................278
Sysmgmt Diagnostics .............................................................................................281
System Management .............................................................................................281
Tune-Up/QA/Tests .................................................................................................. 277
Required Aids and Tools ................................................................................................. 7
Restore
Acronis ..................................................................................................................133
Restore (syngo) ..........................................................................................................103
ROT ............................................................................................................................. 13
RTC ..............................................................................................................................12
RTC A DIPP FRU .......................................................................................................... 140
RTC A(B) DIPP FRU ...................................................................................................... 140
RTC A(B) Interface ...................................................................................................... 140
RTC B DIPP FRU ...........................................................................................................140
T TBL .............................................................................................................................. 12
TCM .............................................................................................................................12
Test Pattern ............................................................................................................... 113
Test Pattern Selection for FD Systems ......................................................................... 116
Test Pattern, FD ......................................................................................................... 114
Test tools
AXCS tests ............................................................................................................. 140
Hardware tests ...................................................................................................... 137
SIRC status ............................................................................................................ 143
Stand & table tests .................................................................................................142
Third-party tests .................................................................................................... 141
Test Tools .................................................................................................................. 137
Third-party tests .........................................................................................................141
ACRONIS Image Management Console ...................................................................141
Mount/unmount the backup/restore drive .............................................................. 141
Trumpf service program .........................................................................................142
VDX configuration ................................................................................................. 142
Third-party Tests
Can Net Test ..........................................................................................................141
Managed Network Switch ......................................................................................142
Trumpf service program ............................................................................................. 142
Tune Up .....................................................................................................................109
Tune-Up/QA/Test Reports ........................................................................................... 277
U UDC_act .......................................................................................................................13
UDC_nom .................................................................................................................... 13
ULI ...............................................................................................................................12
URö ist ......................................................................................................................... 13
URö soll ....................................................................................................................... 13
Utilities ...................................................................................................................... 239
UT_act ......................................................................................................................... 13
UT_nom .......................................................................................................................13
UZ ist ........................................................................................................................... 13
UZ soll ......................................................................................................................... 13
W WD .............................................................................................................................. 13
X XRAY ........................................................................................................................... 13
XRQ ............................................................................................................................. 12
healthcare.siemens.com/services
siemens.com/healthineers