PROBLEM:
When loading databases to a Garmin panel mount device, the device displays one of these messages:
DB MISMATCH
LRU Navigation DB mismatch.
[GDU name] navigation database mismatch
[GDU name] obstacle database mismatch
[GDU name] terrain database mismatch
CROSSFILL ERROR GTN Navigation DB mismatch.
CAUSE:
G1000 NXiGTN Xi SeriesGPS 175/GNX 375/GNC 355/355AG3XG3X TouchG2000, G3000, G5000 series |
G1000 NXi
(Garmin G1000 NXi Pilot’s Guide for the Cessna Nav III, GDU 20.05)
Message | Comments |
---|---|
DB MISMATCH – Navigation database mismatch. Xtalk is off. | The PFD and MFD have different navigation database versions or types installed. Crossfill is off. Check the Aux-System Status Page to determine versions or regions. Also, check the Aux-System Status Page for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
DB MISMATCH – Obstacle database mismatch. | The PFD and MFD have different obstacle database versions or types installed. Check the Aux-System Status Page to determine versions or regions. Also, check the Aux-System Status Page for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
DB MISMATCH – Standby Navigation database mismatch | The PFD and MFD have different standby navigation database versions or types installed. Check the Aux-System Status Page to determine versions or regions. Also, check the Aux-System Status Page for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
DB MISMATCH – Terrain database mismatch. | The PFD and MFD have different terrain database versions or types installed. Check the Aux-System Status Page to determine versions or regions. Also, check the Aux-System Status Page for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
NOTE: When loading database updates, the ‘DB Mismatch’ message will be displayed until database synchronization is complete, followed by turning system power off, then on. Synchronization can be monitored on the ‘Aux – Databases’ Page
GTN Xi Series
(GTN Xi Series Pilot’s Guide, Software v20.40)
ADVISORY | CONDITION | CORRECTIVE ACTION |
---|---|---|
CROSSFILL ERROR GTN Navigation DB mismatch. | Navigation databases do not match between GTNs, resulting in a loss of communication between the two units. | Verify that the database version specified by both GTNs is up to date. Update the database if needed. |
Database Conflicts
FEATURE LIMITATIONS
Applicable to the following installations only.
- Dual GTN Xi
- GTN Xi/GDU TXi 1
- GTN Xi/GI 275 2
(1 Applicable only to GDU TXi software v3.30 and later. 2 Applicable only to GTN Xi software v20.30 and later & GI 275 software v2.60 and later.)
Conflicts occur when the database of a configured GTN Xi, GDU TXi, or GI 275 is corrupt, missing, or past its expiration date.
When this happens:
- A caution indication appears on the start-up page of the primary GTN Xi. Depending on the type of conflict, a selectable information key may appear next to the database name.
- The database list displays on the appropriate LRU (remote confirmation is no longer available for that unit).
- The database name appears in yellow on both the primary GTN Xi and the associated LRU.
Resolve database conflicts when they occur.
DATABASE MISMATCH
Tapping Database Mismatch displays all databases of that particular type and their associated LRUs. Expired or corrupt databases appear in yellow at the top of the list.
GPS 175, GNC 355, GNX 375
(GPS 175 GNC 355 GNX 375 Pilot’s Guide, Software v3.20)
ADVISORY | CONDITION | CORRECTIVE ACTION |
---|---|---|
LRU Navigation DB mismatch. | Navigation databases do not match between crossfill navigators, resulting in a loss of communication between the two units. | Verify that the database version specified by both crossfill navigators is up to date. Update the database if necessary. |
G3X
(G3X Pilot’s Guide, Software v11.80)
Message | Comments |
---|---|
[GDU name] obstacle database mismatch | The PFD and MFD have different obstacle database versions installed. Install the correct obstacle database on all displays for proper terrain/obstacle alerting. |
[GDU name] terrain database mismatch | The PFD and MFD have different terrain database versions installed. Install the correct terrain database on all displays for proper terrain/obstacle alerting. |
[GDU name] navigation database mismatch | The PFD and MFD have different navigation database versions installed. Install the correct navigation database on all displays for proper navigation. |
G3X Touch
(G3X Touch Pilot’s Guide, Software v8.60)
Message | Comments |
---|---|
[GDU name] obstacle database mismatch | The PFD and MFD have different obstacle database versions installed. Install the correct obstacle database on all displays for proper terrain/obstacle alerting. |
[GDU name] terrain database mismatch | The PFD and MFD have different terrain database versions installed. Install the correct terrain database on all displays for proper terrain/obstacle alerting. |
[GDU name] navigation database mismatch | The PFD and MFD have different navigation database versions installed. Install the correct navigation database on all displays for proper navigation. |
G2000, G3000, G5000 Series
(Garmin G2000 Pilot’s Guide for the Cessna T240, GDU v3.09)
Message | Comments |
---|---|
DB MISMATCH – Navigation database mismatch. Xtalk is off. | The GDUs have different navigation database versions or regions installed. Crossfill is off. Check the Avionics Status Screen to determine versions or regions. Also, check the Avionics Status Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
DB MISMATCH – Obstacle database mismatch. | The GDUs have different obstacle database versions or regions installed. Check the Avionics Status Screen to determine versions or regions. Also, check the Avionics Status Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
DB MISMATCH – Standby Navigation database mismatch | The GDUs have different standby navigation database versions or regions installed. Check the Avionics Status Screen to determine versions or regions. Also, check the Avionics Status Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
DB MISMATCH – Terrain database mismatch. | The GDUs have different terrain database versions or regions installed. Check the Avionics Status Screen to determine versions or regions. Also, check the Avionics Status Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
NOTE: When loading database updates, the ‘DB Mismatch’ System Message will be displayed until database synchronization is complete, followed by turning system power off, then on. Synchronization can be monitored on the Avionics Status Screen on the Touchscreen Controller.
(Garmin G3000 Pilot’s Guide for the Daher TBM 930, GDU v20.92)
Message | Comments |
---|---|
DB MISMATCH – Navigation database mismatch. Xtalk is off. | The GDUs have different navigation database versions or regions installed. Crossfill is off. Check the Avionics Status Screen to determine versions or regions. Also, check the Avionics Status Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
DB MISMATCH – Obstacle database mismatch. | The GDUs have different obstacle database versions or regions installed. Check the Avionics Status Screen to determine versions or regions. Also, check the Avionics Status Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
DB MISMATCH – Standby Navigation database mismatch | The GDUs have different standby navigation database versions or regions installed. Check the Avionics Status Screen to determine versions or regions. Also, check the Avionics Status Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
DB MISMATCH – Terrain database mismatch. | The GDUs have different terrain database versions or regions installed. Check the Avionics Status Screen to determine versions or regions. Also, check the Avionics Status Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
NOTE: When loading database updates, the ‘DB Mismatch’ system message will be displayed until database synchronization is complete, followed by turning system power off, then on. Synchronization can be monitored on the ‘Database Status’ Screen.
(Garmin G5000 Pilot’s Guide for the Citation Excel/XLS (Textron 560XL), GDU v32.31.20)
Message | Comments |
---|---|
1 DATABASES MISMATCHED – Restart displays to correct mismatch. | The GDUs have different database versions or regions. Restart the system to move the standby databases to active status. |
1 DB MISMATCH – Obstacle database mismatch. | The GDUs have different obstacle database versions or regions installed. Check the ‘Database Status’ Screen to determine versions or regions. Also, check the ‘Avionics Status’ Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
1 DB MISMATCH – Terrain database mismatch. | The GDUs have different terrain database versions or regions installed. Check the ‘Database Status’ Screen to determine versions or regions. Also, check the ‘Avionics Status’ Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
1 DB MISMATCH – Navigation database mismatch. Xtalk is off | The GDUs have different navigation database versions or regions installed. Crossfill is off. Check the ‘Database Status’ Screen to determine versions or regions. Also, check the ‘Avionics Status’ Screen for a database synchronization function not completed. After synchronization is complete, power must be turned off, then on. |
1 AVIONICS FAULT’ related System Message. Does not trigger the MSG Button on the Touchscreen Controller.