Vivid

• Faulty PC power supply, e.g. the 3.3 V rail reading too high (seen in the logs on a Vivid E9)
• Faulty main power supply (MPS) that does not start the ultrasound part of the system
• Dried-out capacitors in the power supply, so the 5 V enable signal is missing after the unit has been fully off for a long time (Vivid 7)
• 3.3 V missing on the computer board (Vivid S5)
• Faulty component on the motherboard in the power-on circuit (Vivid E9)
• Dirty contacts on the BEP / control panel side of the power button circuit (Vivid 7 Dimension)

1. Read the system logs and the service menu voltage readings (3.3 V, 5 V)
2. Check the LEDs on the ultrasound boards, above the motherboard and on the BEP/VER block to see which section has no power
3. Measure the voltages at the power supply connector and check whether the relay that feeds the modules switches on
4. Trace the power-button signal through the I/O board to the motherboard, drawing the circuit if needed
5. Look at the ultrasound board nearest the power supply for burnt capacitors
6. Swap in a known-good power supply to confirm or rule it out
7. Clean the contacts on the BEP

Solved in one case by replacing the PC power supply that had the 3.3 V overvoltage error; the errors went away. In other cases the likely fixes were replacing the MPS (the system started with a substitute supply), recapping the power supply when the fault appears after long idle periods, cleaning the BEP contacts, or repairing or replacing the motherboard (in one case reheating a bridge chip brought the unit back only temporarily, with a motherboard replacement still pending). Forcing the supply on is a diagnostic step only, not a repair.

• Interference coming in on the mains power cable (the same probes worked fine on another system)
• Fault in a port or the probe board (image came back after swapping probes between ports)
• Faulty Relay board when only the linear probe is affected and convex/sector probes are normal (Vivid 7)
• No high voltage (HV) from the power supply, or a beamformer board fault, when there is no live echo on any probe (Vivid T8)
• Faulty crystal module inside the probe (3Sc artifacts in all modes, probe serial/info lost)
• Unstable TGC slider readings causing a cyclic band on all probes (Vivid E95)

1. Move the suspect probes to a known-good system to tell probe faults from system faults
2. Swap probes between ports
3. Try other rooms and outlets, or run the system from an online UPS
4. Check whether all probes are affected or only one probe type
5. Reset the software, run the DC offset calibration and the system tests that are available
6. Move the TGC sliders to their end positions and use the front-panel diagnostic utility to see whether the slider values stay steady or jump around
7. Check the HV supply and the beamformer board when there is no live image

Solved in one case by fitting ferrite rings on the mains cable. In the other cases the likely fixes were repairing or replacing the Relay board (and checking the related resistors), replacing the probe's crystal module, checking the power supply HV and the beamformer board, or investigating the port/probe board further after a port swap brought the image back.

• Probe plugged into the rear tee connector upside down (cable pointing up instead of down) (Vivid iq)
• Mechanically damaged probe connectors: hit against the couch while the system was moved with a probe attached, or worn out over time (Vivid S5/S6)
• Dead backup battery causing boot loops after service tests (Vivid E90)

1. Check how every probe is plugged in, including the tee connector on the cart
2. Disconnect the probe connector board (PSB) and see whether the system then boots normally
3. Take the probe connectors apart and inspect them
4. Disconnect the battery
5. Reseat the ultrasound and PC boards; reinstall the software only after hardware causes have been ruled out

Solved by plugging the probe in the right way round, and in another case by repairing or replacing the damaged probe connectors. For the boot loop after service tests, disconnecting the battery is the likely fix (a known cause is a dead battery).

• Faulty IC (possibly a solder defect) on the encoder board of the keyboard (Vivid S6)
• Liquid spilled on the keyboard (suspected, not confirmed)

1. Inspect the boards for dirt and liquid
2. Reseat the ribbon cables
3. Run the system without the control panel, then with the encoder board disconnected, to find the source
4. Press every key in turn and watch for stuck keys

Solved by replacing the faulty IC on the keyboard board. In the suspected spill case, disconnecting the keyboard and working the keys restored normal operation.

• Failed diode in the optical trackball (suspected; Vivid S5)
• Dirt in the trackball well

1. Find out whether the trackball is optical or mechanical
2. Try blowing it out with compressed air
3. On the Vivid E9 the trackball is reached from the inside: remove the lower monitor, then the top panel

Cleaning access through the lower monitor and top panel worked on the Vivid E9. For the optical trackball that fails on one axis, replacing the trackball is the likely fix.

• Dust in the lower fan unit even though the rest of the system was cleaned and the fans spin (Vivid E9)
• Clogged filters and dust throughout the system (Vivid S70)

1. Look at the errors in the service menu
2. Check that all fans are running
3. Take out the lower fan unit and inspect it

Likely fixed by taking out and cleaning the lower fan unit, or by fully stripping the system, cleaning every filter and blowing it out.

• Faulty DC/DC block or power supply whose onboard memory has lost its identification data

1. Run the built-in test
2. Check what the system shows about the power supply

Likely fixed by replacing the faulty memory chip or the DC/DC block. If the data keeps getting lost, replace the block or update the system software to the latest version, which was said to depend less on this data. Use only manufacturer-approved methods.

• Motherboard fault (suggested from a similar case)

1. Inspect the cable between the front-end and back-end and its pins

The motherboard is the likely cause. Not confirmed (single case).

• Errors in the database partition on the old hard disk (Vivid 7/S5/S6)
• Failed hard disk (Vivid E9)
• Newer PC module with a SATA hard disk that does not see a USB stick or DVD as boot media (Vivid q)
• Screen-rotation hotkeys in the graphics card utility triggered by accident (Vivid S60)
• No user preset saved (Vivid E9)

1. Check the hard disk and its database partition
2. Look for the original software media: in an envelope under the system's covers (under the black cover or on the left by the CD drive)
3. For USB boot problems: use a USB hub with its own power supply, check whether the PC has an IDE or SATA disk, and consider a dual-layer DVD if the image is small enough
4. Check the graphics utility hotkeys for screen rotation
5. Create a user preset with the required settings

Solved in one case by temporarily changing the computer name in the settings, rebooting and changing it back, after moving to a new disk. The other fixes are likely: reinstall from the original media, replace the hard disk, set the screen rotation back with the hotkeys (a horizontal offset remained), or save a custom preset.