Malfunction of DAS data communication — cause investigation (streak/ring artifacts)
Use this page when a scan shows a streak or ring artifact and you need to determine whether the fault is in the DAS data path or in the MUDAT/GCIFA data-transmission path. Source presents this as one short orienting explanation, a 2-page fault-isolation flowchart, and five numbered sub-procedures the flowchart invokes: (1) raw data check, (2) manual check, (3) console test, (4) DAS test mode, and
Tools & parts
| Item | Part number | Qty |
|---|---|---|
| GCIFA PWB | n/a in source | |
| OPCONTA PWB | n/a in source | |
| KGTSM (PWB / maintenance panel) | n/a in source | |
| SS/ADI2 PWB | n/a in source | |
| DAS | n/a in source | |
| Detector | n/a in source | |
| PRE | n/a in source |
Full step-by-step for Malfunction of DAS data communication — cause investigation (streak/ring artifacts)
All 26 steps are documented in the FSELIB Activion16 (TSX-031A) service manual — re-authored, web-first, with the real figures from the source.
Open the full procedureRelated Data Transmission guides
Source: 2D201-113EN*J §3.5.3 'Malfunction of DAS data communication' / §3.5.3.1 'Investigating the cause of abnormal image' (pp.367-373) + (4) DAS test mode / (5) VT check (p.389). The GCIFA console test pattern tables printed between (pp.374-388) are out of scope for this atom — see §3.5.3b, toshiba-ct-activion16-dtu-reference-console-test-patterns.. Preview re-authored by FSELIB — the full procedure with figures and steps is in the paid service manual.