Voluson E6 / E8 / E10
Premium cart-based ultrasound system built around 3D/4D volume imaging, used mainly in obstetrics, gynaecology and fetal medicine departments.
About 430 manual-derived fault and procedure records and about 900 parts-list lines across the Voluson E6/E8/E10 entries, plus roughly 20 usable field cases out of 66 engineers' chat threads mentioning Voluson.under engineering review
Architecture
PC back end (BEP)
A Windows-based industrial PC runs the user application, image processing, archive and DICOM. It contains the motherboard, RAM, graphics card, HDD/SSD and the CMOS battery. Most 'it hangs' and 'it won't boot' calls end here: tired hard disks, mismatched RAM, failing graphics chips, dead CMOS batteries and overheated chipsets.
Front end and beamformer
The beamformer module carries the transmit and receive electronics as a stack of plug-in sub-boards (receiver sub-boards such as the RSR family) on a common carrier, plus the front-end interface board (RFI) that also runs the start-up hardware check and the 3D/4D probe motor control. Board names and the number of sub-boards change with the BT software/hardware generation, so always confirm against the manual for your BT version. Typical failures are channel dropouts (black lines), streaky or noisy images, and start-up hardware-check errors caused by a contaminated or badly seated sub-board.
Probe connector panel and relay matrix
The probe ports feed the front end through a relay switching matrix; you hear the relays click during start-up and when probes are selected. Dust or bent pins in a probe port, or a shorted probe, can produce probe-not-recognised messages, image noise or even a transmit-power error that stops the whole system. On some E8/E10 generations one physical port is only a parking socket, not a working port.
Power supply chain
Mains enters a primary power supply that feeds secondary supplies for the front end and the PC (RTP/RTN/RSP families depending on generation). A failing secondary supply often shows as 'system boots but no image on any probe' or as front-end hardware-check failures, while a primary-side fault shows as no start or protective trips. Status LEDs inside the supply and test points listed in the service manual are the first thing to look at.
User interface console
The operator panel combines the hard-key keyboard, encoders, a touch panel and a USB hub board that ties them to the PC. On the E10, electrostatic discharge from users is a known killer of the USB hub chip, giving a dead touch screen or random 'phantom' key presses. Encoders and hard keys wear mechanically and are replaced as parts.
Video path and monitors
The graphics card drives the main LCD over a long DVI cable through the console arm; the touch panel has its own path. No picture with a running system is usually the graphics card, the DVI cable or the monitor's own electronics, and a failed monitor firmware update can leave the main monitor blank while a standard external monitor still works.
Lifting column and console mechanics
The operator console rides on a motorised lifting column with its own motor controller and power feed from the power supply. Up/down failures come from loss of the column's supply, a failed motor controller board, or mechanical jamming. Full disassembly of the column is a long job, so diagnose the electrical side first.
Cooling
Fan trays and filters cool the card cage and the PC. Clogged air filters and worn fans are the root cause behind many random freezes, overheat warnings and premature component failures. The air filter is a routine maintenance item, not an afterthought.
Faults and how to find them
System freezes completely during scanning at random moments; often cannot even be shut down with the power button. RAM and HDD may already have been swapped without result.field case
- Overheating from clogged air filters or failed fans
- Replacement RAM not matching the original type or speed (mixed modules)
- Failing hard disk with slow or bad sectors
- Failing graphics card
- Motherboard fault: chipset, CPU socket contact or voltage regulator overheating
- Loose or wrongly routed internal USB cables
- Clean the air filters and confirm all fans spin; note whether freezes follow room temperature
- Pull the system logs to a USB stick and read them before replacing anything
- Check that all RAM modules are the same type and speed as specified for this BT version
- Run a surface scan of the HDD; test with a fresh drive and a clean software install rather than the old disk
- Re-seat and check routing of internal USB cables
- Inspect the motherboard for swollen capacitors and measure temperatures around the voltage regulator, CPU and chipset
- If it still hangs, reproduce on the bench with the PC alone and swap graphics card, then motherboard
In field cases the freezes were resolved by matching RAM speed, replacing the HDD or replacing the graphics card or motherboard. Clean the cooling path first; it is free and often part of the cause.
System powers on (fans, button light) but the main monitor shows 'No signal' or nothing; the system does not reach the application.field case
- Graphics card failure
- Long DVI cable to the monitor damaged in the console arm
- Main monitor electronics or monitor firmware
- Motherboard or CPU fault preventing POST
- Check the monitor power and that DVI pins are not bent
- Connect a standard external monitor directly to the graphics card output
- If the external monitor works, swap the long DVI cable, then the monitor
- If there is no picture even directly from the graphics card, try a known-good graphics card
- If still no POST, strip the PC down on the bench (CPU, one RAM module, graphics) to separate motherboard from CPU
Replace the failed graphics card, DVI cable or monitor. In one field case on a related Voluson model every BIOS and cabling step failed and only a motherboard replacement fixed it. Reheating the graphics chip with hot air gave only a few weeks of operation and is not a repair.
Main monitor goes blank after running a monitor firmware update; an ordinary external monitor shows a normal picture.field case
- Interrupted or incompatible firmware update left the monitor controller unusable
- Confirm the picture is fine on an external monitor and on the same model monitor from another unit
- Confirm the firmware package matched the BT software version before retrying
Treat it as a monitor-side problem: re-flash with the correct package if the service tool still sees the monitor, otherwise replace the monitor controller or monitor. Always check firmware compatibility before updating monitors.
Interference pattern (fan-shaped or streaky noise) on one probe only, e.g. a cardiac phased array, while another probe of a similar type is clean.field case
- External electromagnetic interference at the frequency band of that probe
- Poor mains earth or noisy shared mains circuit
- Contaminated or poorly seated receiver sub-board in the beamformer
- Dust in the probe port
- Switch off other electrical equipment in the room and neighbouring rooms
- Move the system to another room and another mains outlet
- Lay the probe down instead of holding it, to see whether the noise changes
- Inspect and gently blow out the probe port
- Run the front-end tests and use the receiver-board selection in the test to see which sub-board the noise follows
- Re-seat the receiver sub-boards one at a time
In the confirmed field case, after external causes were excluded, the noise was traced to one receiver sub-board; cleaning that board with alcohol and refitting it cured the image. Replace the sub-board if cleaning does not help.
Black vertical lines or dropouts in the 2D image (missing channels), or generally poor image quality on all probes.reference
- Defective probe elements
- Sub-boards in the beamformer not fully inserted or tilted
- Bent pins on the beamformer carrier connectors
- Mixed or mismatched receiver sub-board revisions
- Failed beamformer module
- Try a second probe of the same type; if the lines follow the probe, the probe is defective
- Check the same probe on all probe ports
- Run the frontend test for missing channels or elements
- Check that all sub-boards are fully inserted, parallel and locked by their holders
- Inspect connector pins on the carrier boards
- Confirm all receiver sub-boards are the correct, matching revision for the system
Re-seat or replace the mismatched or failed sub-board; replace the beamformer module only after the probe and seating have been excluded.
Hardware-check error during start-up; the system stops before the scanning application. Often seen after the unit has stood unpowered for a long time.field case
- Discharged CMOS battery and lost BIOS settings
- Failing hard disk
- Front-end sub-board not making contact
- Front-end interface board (RFI) fault, since this board runs the hardware check
- Measure the CMOS battery; replace it if weak
- Record the BIOS settings before touching anything, load defaults, then restore the recorded settings
- Read the exact error text and the logs
- Re-seat the front-end boards
- Test with a known-good HDD carrying a correct software image
Battery and BIOS settings first, then disk, then front-end boards. A board-level repair or exchange of the front-end interface board is the last step.
After a software restore or a BIOS battery change the system boots, but there is no image from the probes and an error is shown.field case
- No image on 2D probes as well: secondary power supply for the front end
- Error only with the 3D/4D probe: defective 3D/4D probe (motor or electronics)
- Connect a plain 2D probe and check for an image
- If no 2D image, check the power supply status LEDs and test-point voltages listed in the service manual
- If 2D is fine, test the 3D/4D probe on another system
An experienced field engineer's rule: a restore or battery change does not by itself cause this. No image on any probe points to the power supply; an error with only the volume probe points to the probe.
After cleaning, dusting or transport the system shows a system error at start-up or stops detecting probes; the probe relays may not click.field case
- Boards or sub-boards partly pulled out or not fully re-inserted
- Cable disturbed while the card cage or filters were moved
- Mechanical shock during transport
- Ask exactly what was moved or removed during the cleaning
- Re-seat all boards in the card cage and check the sub-board holders
- Check cables and connectors near the area that was worked on
- Read the logs if the problem persists; swapping boards from another unit is the last resort
In field cases a board that was not fully inserted produced exactly this picture. When cleaning, open the blocks and look, rather than blowing air blindly, and photograph cable routing before removing anything.
Touch panel does not load or is unresponsive, or keys appear to press themselves, on an E10. Recurs roughly yearly on the same unit.field case
- USB hub chip on the user-interface board damaged by electrostatic discharge
- Confirm that the PC and application load normally
- Check the UI USB cabling
- Check the USB hub board and its supply
Replacing the USB hub board restored normal operation in the confirmed case. To reduce recurrence, address static in the room (humidity, footwear and clothing, an earthed operator chair) rather than the system earth, which was found to be fine.
Operator console up/down buttons do nothing; the console is stuck at one height. Everything else works.field case
- Loss of supply to the lifting column
- Failed column motor controller board
- Mechanical jam
- Fully power down, disconnect from mains for a few minutes, then restart
- Try the controls with the console at its extreme positions
- Remove the rear cover and check the supply cable from the power supply to the column
- Check internal power connectors: on one E8 a power plug inserted into the connector intended for another region's mains configuration produced the same symptom
- Check the column motor controller board
In field cases the column motor controller board was repaired or replaced. Allow about two hours for the strip-down and photograph every step inside the column, because reassembly mistakes are common.
Hard disk failed with no backup and no install media; a clone from a 'similar' donor system boots to the Voluson splash screen, then shows a black screen.field case
- Software image tied to a different hardware configuration (different motherboard type)
- CMOS battery or BIOS settings not matching
- Compare the donor and target hardware configuration board by board
- Check the CMOS battery and BIOS settings
Cloned images often fail even on apparently identical hardware and almost never work across different motherboard types. The reliable route is a proper software installation for that system's configuration through the service software. Prevention: make a full system and options backup when the system is commissioned.
After a particular probe is connected, a transmit-power error appears and the whole system stops working, including with other probes.field case
- Shorted or damaged probe loading the transmit supply
- Damaged pins or debris in the probe port
- Coincidental power-supply failure
- Inspect the probe connector and the system port with a light and magnifier
- Remove the suspect probe and restart with known-good probes only
- If the fault persists, check the transmit supply voltages as described in the service manual
Engineers have seen a faulty probe take the whole Voluson down. Isolate the probe before replacing any board, and do not reconnect it to another system until it has been checked.
Overheating warning, fan error, or probe connectors getting hot.reference
- Clogged air filters
- Worn or failed fan or fan box
- Fan box cable disconnected
- A probe whose connector is heating up
- Clean the filters and check airflow
- Check every fan and the fan box cable
- Disconnect all probes and reconnect them one by one to find the one whose connector heats up
Clean filters, reconnect or replace the fan box, and replace the probe whose connector heats.
Start-up message: hardware check reports memory extension missing.reference
- One of the RAM modules missing, unseated or failed
- Confirm both RAM modules are installed and fully seated
- Swap modules between slots to find the bad one
Re-seat or replace the RAM with the correct specified type.
Preventive maintenance
| Check operator console movement (height and swivel) through the full range | daily (user check) |
| Inspect probe cables, connectors and system cables; confirm cables are secured | weekly |
| Clean monitor, touch panel, alphanumeric keyboard and function keys | weekly |
| Inspect wheels, casters and brakes | weekly |
| Remove dust from all probe connectors and ports | at each preventive maintenance visit |
| Remove and clean the air filter grid | annually, or more often in dusty rooms |
| Open the rear covers and remove dust from inside the system (vacuum, not just compressed air) | annually |
| Inspect the mains cable, plug and appliance inlet for damage | annually |
| Inspect probe housings and lenses for cracks or holes | at each preventive maintenance visit |
| Verify all imaging modes (2D, M, colour, power Doppler, PW/CW, 3D, 4D), keyboard test and monitor/touch panel function | at each preventive maintenance visit |
| Check image quality: axial and lateral resolution, gain and TGC response, brightness uniformity | as required / at each preventive maintenance visit |
| Check the software version and update if required | as required |
| Document test results and corrective actions | every visit |
Parts worth keeping on the shelf
| CMOS/BIOS lithium coin cell | Flat batteries after long storage or power-off cause BIOS loss and start-up hardware-check errors; cheap and fixes a surprising number of 'won't boot' calls. |
| Hard disk with a verified software image for each BT version you support | Disk failure is the most common cause of freezes and boot failures, and images from other systems often do not work. |
| Air filter grid and fan set | Overheating drives freezes and early board failure; filters and fans are routine maintenance items. |
| RAM modules of the exact specified type and speed | Mismatched RAM causes random freezes; you need known-good matching modules to rule it out. |
| Graphics card (generation-specific) | Failed graphics cards are a frequent cause of no picture or hang at boot, and reheating the chip is not a lasting fix. |
| User-interface USB hub board (E10) | Prone to electrostatic damage; a known repeat failure that leaves the touch panel dead. |
| Long DVI video cable | Lets you quickly separate a cable fault from a graphics card or monitor fault on 'no signal' calls. |
Field notes
Before blaming the machine for image noise, switch off everything else in the room, move the unit and change the outlet. If the noise survives that, it is inside, and in one case it was a single dirty receiver sub-board that alcohol cleaning cured.
Software images do not travel well between Voluson systems. A clone from a donor with a different motherboard booted to the splash screen and stopped. Back up the system and options on day one.
A recurring dead touch panel on an E10 was static, not the earth: the USB hub chip on the UI board failed about once a year. The fix was the board; prevention is about the room and the users.
When a dusting job ends in a system error, assume something was not pushed back in. Open the blocks and look instead of only blowing air, and photograph before you pull anything.
Reheating a graphics chip with hot air brings the unit back for weeks, not months. Quote a replacement.
Allow two hours to strip the lifting column and photograph every step; reassembly mistakes there are common.
Check whether a 'dead' probe port is real: on some E8/E10 generations one socket is only a parking position.
A faulty probe can take the whole system down with a transmit-power error. Remove the suspect probe before you start changing boards.
After any repair, run the manufacturer's full checkout and performance verification before the device goes back to patients.