____________________________________________________________________
G1000 System Maintenance Manual
Page 5-67
190-00903-00
Rev.
A
5.1.6.20
GTX 33/33D Advisory Messages
Advisory Message
Possible Cause
Recommended Actions
XPDR1 CONFIG – XPDR1
configuration error. Config
service req’d.
XPDR2 CONFIG – XPDR2
configuration error. Config
service req’d.
The G1000 has detected a
GTX 33 configuration
mismatch.
a.
Perform a SET>ACTV
configuration reset on the GTX
Config page and verify the
aircraft registration is present.
b.
If error is still present, reload
config files from a loader card.
c.
If problem persists, replace
master configuration module,
check config module harness
for faults and replace if
necessary.
NOTE
New Terrain/Obstacle cards,
Jeppesen Aviation Database and
other optional features (i.e. TAWS
unlock card) will need to be
replaced if the master configuration
module is changed. The G1000
System ID number will change to a
new number when installing a new
master config module. The old
Terrain and other cards will no
longer work as they will remain
locked to the old System ID
number.
MANIFEST – GTX1 software
mismatch. Communication
Halted.
The system has detected an
incorrect software version
loaded in GTX 33 #1.
MANIFEST – GTX2 software
mismatch. Communication
Halted.
The system has detected an
incorrect software version
loaded in GTX 33 #2.
Load correct software version
XPDR1 SRVC – XPDR1 needs
service. Return unit for repair.
The G1000 has detected a
failure in GTX 33 #1.
Replace GTX 33D #1.
XPDR2 SRVC – XPDR2 needs
service. Return unit for repair.
The G1000 has detected a
failure in GTX 33 #2.
Replace GTX 33/33D #2.
XPDR1 FAIL – XPDR1 is
inoperative.
GTX 33D #1 is not
responding.
•
Troubleshoot for a failed
datapath using Section 5.1.5.
•
Replace GTX 33D #1
XPDR2 FAIL – XPDR is
inoperative.
GTX 33/33D #2 is not
responding.
•
Troubleshoot for a failed
datapath using Section 5.1.5.
•
Replace GTX 33/33D #2.
BACKUP PATH – Transponder
using backup data path.
The GTX 33 is using a
backup RS-232 data path.
Troubleshoot for a failed datapath
using Section 5.1.5.