ProcedureX-ray Generator/HVTroubleshootingTroubleshoot

Retrieve and decode the XC PWB error log (direct RS-232C read + system-software XL30 console log)

The XC PWB (XCS1 or XCS2) keeps its own error-information log in backup memory — 47 entries on the XCS1 PWB, 64 entries on the XCS2 PWB — independent of the system's own hardware error-log function. Normally the system's hardware error-log function is enough, but some error statuses are better diagnosed by reading the XC memory log directly. This page covers the two ways to retrieve that log and h

Applies to

Activion16 (TSX-031A). Method A (direct RS-232C 'P'-command read of the XC memory-resident error log) applies to the XCS1 PWB and, per source, the GCIF PWB — but explicitly NOT the XCS2 PWB (source states the log cannot be collected this way from the XCS2 PWB; see the fidelity note on the GCIF/status-signal wording in §1 below). Method B (system-software/console XL30 log) applies to BOTH the XCS1 and XCS2 PWB — source states the data structure and error-code meaning are identical for both.

Personnel

"Not specified in source manual for this section"

Steps

11 steps

Source

2D201-113EN*J §1.11.6 XC error log reference procedures (§1.11.6.1 Outline, §1.11.6.2 XCS PWB/GCIF PWB direct RS-232C read, §1.11.6.3 system-software XL30 console log), pp.112-122

Tools & parts

Item	Part number	Qty
PC with RS-232C port (9-pin D-sub connector)	n/a in source
"term.com" (DOS) or Windows Terminal	n/a in source
Maintenance cable (for use with GTS)	n/a in source
XCS PWB toggle switch SW4	n/a in source

Safety

WARNING

Hazard: Connecting the maintenance cable directly to the XCS PWB (CNN3, in the rotation section) while the gantry remains powered ON

Consequence: a person or the cable can be caught in the rotation section — entanglement/crushing injury — because power stays ON while the maintenance cable is connected to the rotation section

Avoidance: be extremely careful to avoid anyone or the cable being caught in the rotation section before and during this connection (source prints this as a CAUTION; reclassified WARNING here per ANSI Z535 severity — rotation-section entanglement is treated as a potential-serious-injury hazard elsewhere on this platform, e.g. the slip-ring troubleshooting atom)

NOTICE

Hazard: Entering any character other than the documented P-read command (e.g. PD400) at the XCS terminal prompt

Consequence: the source states a memory-WRITE command also exists at this prompt; an unintended character could overwrite XC backup memory, including the stored error log itself

Avoidance: enter only the documented P command; do not experiment with other characters at the terminal prompt

Full step-by-step for Retrieve and decode the XC PWB error log (direct RS-232C read + system-software XL30 console log)

All 11 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 procedure

Related X-ray Generator/HV guides

Adjust the If (filament) value remotely from the console31 steps Check the X-ray generator power-on and power-off sequence2 steps Check the X-ray tube current with the tube ammeter (MA-1201D)4 steps Check the X-ray tube voltage with the tube voltage meter (kV-201 bleeder)5 steps Handle the high-voltage cable — removal, cleaning, and silicone-oil reassembly (CLAYMOUNT)15 steps Replace the X-ray generator fuse2 steps

View all Activion16 (TSX-031A) guides

Source: 2D201-113EN*J §1.11.6 XC error log reference procedures (§1.11.6.1 Outline, §1.11.6.2 XCS PWB/GCIF PWB direct RS-232C read, §1.11.6.3 system-software XL30 console log), pp.112-122. Preview re-authored by FSELIB — the full procedure with figures and steps is in the paid service manual.