TroubleshootingData Transfer (MUDAT)TroubleshootingTroubleshoot
Diagnose an abnormal image caused by the MUDAT
When a scan comes back with streaks, rings, or a meaningless image and you suspect the gantry data-transfer link rather than the detector or DAS itself, this atom is the source's own reasoning for why a MUDAT fault looks the way it does on the image (§5.3, p.69) and its top-level decision tree for chasing that image fault back to a specific board or test (§5.3.1, p.70-71).
Applies to
Aquilion 16 (TSX-101A) — Data Transfer (MUDAT) section, source volume 2D201-059
Personnel
1 technician · Intermediate — reading the manufacturer's image-artifact/LED/raw-data decision tree to route a MUDAT-related abnormal image toward the right follow-on check (manual check, raw data check, DAS power-supply check, VT check, DAS test mode, console test) and, where the tree points there, on to a DAS/detector, PRE, GCIFA PWB, or SS/ADI2 PWB replacement (skill assessment derived from procedure content — not an OEM-stated skill level)
Steps
1 step
Source
2D201-059E*D p.69-71
Full step-by-step for Diagnose an abnormal image caused by the MUDAT
All 1 steps are documented in the FSELIB Aquilion 16 (TSX-101A) service manual — re-authored, web-first, with the real figures from the source.
Open the full procedureRelated Data Transfer (MUDAT) guides
DAS test mode and View Trigger (VT) check9 stepsDisassemble the MUDAT7 stepsCheck LED luminescence with the IR converter (ROT and SOT)7 stepsManual check and console test for locating MUDAT faults14 stepsOperation check after MUDAT work0 stepsTroubleshoot control-system data communication errors20 steps
View all Aquilion 16 (TSX-101A) guidesSource: 2D201-059E*D p.69-71. Preview re-authored by FSELIB — the full procedure with figures and steps is in the paid service manual.