SOMATOM

• Sending to a new PACS node is not configured in the protocol editor
• Network/DICOM adapter settings were lost, for example after moving a backup to different host hardware
• Corrupted local databases (partial series sent)

1. Check the send configuration window and the auto-send rules in the protocol editor for the PACS node
2. Re-create the DICOM rule and run verification
3. Verify the connection from both sides, including on the PACS side
4. Check the network adapter settings, especially after a hardware migration or backup restore

Field fixes: set up sending for the new PACS in the protocol editor; restore or reconfigure the network adapter settings. In the case where only one image per series was sent, all databases were removed. Before that, the required series were extracted as ISO images through the file section into /service/extraction/.

• The previous session was not shut down properly. On the next start the software sees the improper-shutdown flag and repairs the damaged program file
• The SRS/host profile or network settings were disrupted after the DVD drive was replaced and its drive letter changed
• A problem with the csageneric process (the exact cause was not found)

1. Do a full system restart
2. Reseat the LAN cables at the operator desk, the switch and the scan room. In one case this was not the cause
3. After a drive-letter change, check the Satellite/local profile and the IP address and hostname in local devices
4. Check the hard disks
5. Locate a valid backup or system image before reinstalling

A full reboot fixed the hang after an improper shutdown, and a reboot is advised if it happens again. After the drive-letter change, switching the Satellite profile to local and entering the IP address and hostname got syngo running again. For syngo dropping to the desktop, the likely path is a disk check, then restoring the system image or reinstalling the software. This was not confirmed.

• A stuck Del key on an extra PS/2 keyboard someone has connected
• BIOS settings lost or reset after the BIOS battery was replaced or went flat

1. Look for extra keyboards or peripherals connected to the host and disconnect them
2. Before any BIOS work, photograph all current BIOS settings
3. Measure the BIOS battery (one low battery read 2.9 V) and replace it if needed
4. Load BIOS defaults, then restore the original settings by hand from the photos

Confirmed in one case: removing the extra keyboard with the stuck Del key fixed it. After battery replacement, the likely fix is to load defaults and restore the recorded BIOS configuration by hand.

• The UMAS unit has failed
• The Stop Report loop signal is lost somewhere in the chain
• No 24 V supply to UMAS
• A stuck button on the control panel (Emotion)
• Suspected in one case but not confirmed: board D301 or the communication board in the ICS (Emotion)

1. Check UMAS power and the 24 V indication
2. Trace the Stop loop with the manual's loop diagram to find where the signal drops
3. Check the inverter cabinet and how the MCI board behaves
4. Check the control panel buttons for one that is stuck
5. Firmware reloading was considered pointless when the UMAS does not boot

The likely fix for a dead UMAS is to replace the unit. As a temporary measure, disassembling it, renewing the thermal pads and reseating the boards may revive it briefly. On Emotion, a similar case was solved by finding and fixing a stuck control-panel button. This is likely, not confirmed for the case in question.

• Detector modules degrading with age
• Temperature swings during long shutdowns, for example air conditioning switched off over holidays
• Contrast contamination of the detector area

1. Compare the event log against the dates when modules failed
2. Use the per-module signal graph to find the failing modules
3. Open and visually inspect the detector block, checking for contamination by contrast
4. Inspect the collimator

The likely fix is to replace the failing detector modules, choosing them from the signal graph. Keep room climate stable during long shutdowns.

• Tube arcing turning oil into gas
• A leak in the cooling circuit (oil can evaporate without leaving traces)
• Not enough tube cooling
• Checkup with getter activation not done regularly
• Collimator out of adjustment after tube work

1. Check the logs for cooling pressure and temperature errors and for arcing
2. Check that the tube cooling works properly
3. Check that the checkup procedure (getter activation) is run regularly
4. After tube work, check and adjust the collimator before repeating Tune-up

For air in the circuit, the recommendation was to replace the tube and cooling system, under warranty where it applies. For short tube life, ensure proper cooling and run checkup with getter activation regularly; no software limit on tube life was found. For Tune-up failures after a tube repair, collimator adjustment was recommended. All of these are probable fixes.

• Faulty encoder on the vertical lift motor
• Brake relay (one participant guessed position ~13)
• Lift screw not lubricated
• Flat encoder battery (GM400.E16 encoder)
• Lost communication with the PMM

1. Review the logs and check the vertical lift motor encoder through service access
2. Check whether horizontal calibrations reset after power-off, and check the encoder battery
3. Find the lift's lubrication nipple
4. To reach parts under a fully lowered table, use the manual lift mechanism at the bottom of the table

Probable fixes: replace the vertical lift motor encoder (a similar case was solved this way), or check the brake relay. Lubricate the lift through its built-in nipple with a non-graphite oil. Replace the encoder battery and check the result.

• The exchangedatabase (intermediate database on drive D) is cluttered
• A disk problem, for example after a disk replacement

1. Check the disks and hardware
2. Confirm the databases are re-created and images are deleted from all three disks
3. Find out whether disks were replaced before the problem started

The likely fix is to stop the cleanb processes in Task Manager, then remove the exchangedatabase on drive D with the utilities as administrator. The alldbremove batch file was also used to clean the databases.

• A faulty USB extender, the USB 3.0 to fiber optic cable

1. Review the error logs
2. Test the peripherals plugged in at the gantry
3. Check the cable between the ICS and the monitor, and the monitor's USB hub

The likely fix is to replace the USB extender (USB 3.0 to fiber optic cable), as in a colleague's similar case.