1 Installation and Troubleshooting Guide
33
1.13.7 Power Cycle/Cold Reset procedure for M-Nav800
Hold the power button down for at least 8 seconds, device will reboot.
1.13.8 Hardware Swap Procedure: determining faulty piece of hardware
1. Verify that the Qube is functional and reporting to Online AVL2.
2. Call Navman Support to have the Qube’s serial port set to communicate with the M-Nav.
If problem persists, proceed to next step.
3. Take Malfunctioning M-Nav and plug into Good Vehicle. If problem persists, contact Nav-
man Support to arrange for M-Nav replacement. If Malfunctioning M-Nav works normal
in Good Vehicle, proceed to next step.
4. Replace the cradle in Malfunctioning Vehicle, test and note any change in M-Nav beha-
vior. If problem persists, proceed to next step.
5. Replace the power/data cable in Malfunctioning Vehicle, test and note any change in M-
Nav behavior. If problem persists, proceed to next step.
6. Replace the Qube in Malfunctioning Vehicle with a spare or a known working Qube, test
M-Nav and note any change.
7. Once failed hardware component is isolated, contact Navman Support for return/re-
placement.
1.13.9 Power: M-Nav will not power, M-Nav loses power unexpectedly, M-Nav
turns on and off while in use.
Most likely cause: No power/loose connections at the Qube; M-nav not cradled properly; pins
on cradle stuck or unclean; faulty cradle; faulty PND cable, Qube’s data port must be set to M-
Nav mode (call Support).
1.13.10 Messaging: M-Nav can’t send or receive messages
Most likely cause: Qube needs serial port set to M-Nav mode (call Support); faulty cradle; faulty
PND cable.
1.13.11 Driver ID: Driver Logon function not working
Most likely cause: New Qube or M-Nav in use & Driver ID settings not yet re-pushed through
both devices in AVL2 (call Support); no power and/or cell connection on the Qube.
To Next Page
Loading...
Need help?
General
