LOGIQ

• Damaged probe channel boards (GTX3/GTX4 on LOGIQ E9), possibly after a probe cable was pinched or run over
• Faulty beamformer board (DDBF128 on LOGIQ 7)
• Poor connection between the PC part and the ultrasound part, including a badly seated board stack on LOGIQ F6, where boards are mounted as a 'sandwich' instead of on ribbon cables

1. Check the power indicators and look for LV/HV problems in the test/info screens
2. Check the power supply and try other probes and no probe, to rule out a single-probe fault
3. Check the cable/connection between the ultrasound part and the computer (beamformer side)
4. Inspect the MRX192 / GFI boards and the probe channel boards
5. On LOGIQ F6, if reinstalling the software did not help, review logs, RAM and the drive, then suspect the board stack

Solved on LOGIQ E9 by replacing the faulty GTX3 and GTX4 boards. On LOGIQ 7, a beamformer board (DDBF128) fault was likely, after checking the interconnect. On LOGIQ F6, fully dismantling the unit and reassembling (reseating) the board stack likely restored communication.

• Replacement disk is smaller than the original (an image from a 500 GB disk restored onto a 320 GB disk on LOGIQ E)
• Bootloader missing or corrupted after the software install (LOGIQ Book XP)
• Problems with a cloned image instead of a clean install from the original media

1. Confirm the new disk is at least as large as the source disk of the image
2. Confirm the image and software version match the system
3. Check whether the bootloader was installed; on older systems, check the disk interface type (for example SCSI on LOGIQ 500 Pro)

Solved on LOGIQ E by fitting a disk of the original size or larger (500 GB or more) instead of the smaller one. On LOGIQ Book XP, restoring the bootloader likely fixed the black screen. If cloned images keep stopping at the bootloader, a clean install from the original installation media is likely the more reliable path.

• CPU overheating caused by a thermal pad of the wrong thickness or with poor contact pressure under the heatsink
• Low-quality thermal paste on the CPU
• Dust build-up or a failed fan on the single-board computer (LOGIQ Book XP)
• Failed cooling fan on the graphics card (LOGIQ P5)

1. Clean the air filters and remove dust
2. Check that all fans run
3. Check the CPU temperature in BIOS (about 58 °C at idle was reported as normal)
4. Check heatsink contact and the thickness of the thermal interface material

Likely fixed by restoring proper CPU heat transfer. Use a thermal pad of the correct thickness and compressibility, or good-quality thermal paste, then confirm temperatures in BIOS. On LOGIQ Book XP, cleaning, checking the fan and renewing the paste are the likely remedy. On LOGIQ P5, a failed graphics-card fan was replaced with a matching fan.

• Main power supply not delivering the +24 V rail (the log showed +24V at about 3.6 V) on LOGIQ E9
• Power supply protection tripping because of a faulty load (LOGIQ P5)
• External adapter failure on portable units; laptop adapters with the same nominal rating overheat under load

1. Review the logs, including the housekeeping voltage readings
2. Run the DC offset test and check the GFI board
3. Swap in a known-good main power supply if one is available
4. For a clicking or protection-tripping supply, connect the loads one at a time to find the faulty branch

On LOGIQ E9, replacing the main power supply is the likely fix: in a similar case, fitting a supply from another unit cured it. On LOGIQ P5, the supply is likely in protection, so the faulty load needs to be found. For portable units, use the original adapter (20 V, 5 A on LOGIQ e); a high-quality industrial supply with the correct connector was mentioned as an alternative.

• A burnt HV2201 component in the high-voltage transmit block (ghosting on all probes)
• Faulty analog receive/front-end board (BF192 suspected on LOGIQ S8)
• Faulty probe (colour Doppler flooding seen on one probe)
• Mains interference or poor grounding; presets not adjusted for the user

1. Repeat on several probes: if all show the fault, the probe is not the cause
2. Run the system tests, including the analog RX test, to find bad channels
3. Inspect the connector-area board for burn marks
4. Run without the UPS and on UPS only with the mains cables disconnected; check grounding; try another room
5. Tune gain, frequency and power presets with the clinician and save them

Ghosting was likely fixed by finding and replacing the burnt HV2201 component. For the colour Doppler flooding, a replacement probe was ordered for diagnosis, with no outcome reported. Noise complaints were likely partly normal for the system class; check interference and grounding, then optimise the presets.

• Dust on the Y-axis optical sensor under the ball
• Misaligned or faulty optocoupler in the trackball mechanism

1. Remove the ring and inspect the rollers, holders and sensor
2. Connect a wired mouse to confirm the system cursor itself works
3. Check the trackball board

Solved by cleaning the trackball and its optics (missing Y axis). The inverted Y axis was solved by dismantling the trackball, realigning the optocoupler and resoldering it.

• Case labelled as one model (LOGIQ A5) while the internals are another (LOGIQ P5), so the wrong model was chosen during installation
• Rear cover from a newer hardware version fitted to an older unit (LOGIQ E8)

1. Check the BIOS at boot to identify the actual platform
2. Compare the label and serial number with the internal hardware and documentation; open the unit if needed

Solved on LOGIQ A5/P5 by installing the software for the actual platform, identified from the BIOS rather than the label (the A5/P5 software discs are shared). On LOGIQ E8, the mismatch was likely found by opening the unit and comparing the hardware with the documentation.

• Faulty touch panel
• Loose interface/USB connections at the BEP side
• A duplicated display driver after a software update

1. Run touch calibration and verification from the service menu
2. Dismantle and check for debris between the housing and the touch panel
3. Check the Windows display settings and look for a duplicated display driver
4. Check that only the two displays are on the USB ports, with nothing extra connected

For dead or intermittent touch areas, replacing the touch panel is likely needed (part ordered). For drifting interface graphics, reseating all interfaces on the BEP side likely fixed it; removing a duplicated display driver was also suggested.

• Flat BIOS battery (2.8 V measured on LOGIQ E9)
• BIOS settings reset to defaults after the battery was replaced (LOGIQ Alpha 200)
• Power supply fault if the panel power button does not light

1. Measure the BIOS battery voltage; on LOGIQ E9 the battery sits on the side of the motherboard, near the top
2. Check whether the power button on the panel lights; if it does not, check the power supply
3. Check the battery type before replacing it (a 3 V lithium coin cell with leads on LOGIQ XP)

On LOGIQ E9, a flat BIOS battery is the likely cause of the total failure to start, so replace it. On LOGIQ Alpha 200, the hang was likely cleared by restoring factory defaults: set SW1, let the system boot, switch off, then return SW1 to its original position. On LOGIQ XP, fit a 3 V lithium coin cell with leads and connector and insulate it with heat-shrink. In one case where the BIOS could not be reflashed, the motherboard was replaced.