Novatel MT 3060 U User manual

90029335
MT 3060 U
Troubleshooting Guide
Version1.00 Draft A March 7, 2016

NOVATEL WIRELESS COPYRIGHT STATEMENT
©2016 NovatelWireless,Inc. Allrights reserved. Theinformationcontainedinthis document issubject
to change without noticeand shouldnot beconstruedas acommitment byNovatelWireless, Inc.
NOVATEL WIRELESS TRADEMARKS AND SERVICE MARKS
NovatelWireless isa trademark ofNovatelWireless,Inc., andtheother trademarks,logos,andservice
marks (collectivelythe“Trademarks”)usedin this user manualarethepropertyofNovatelWireless or
their respectiveowners.Nothingcontainedinthis user manualshouldbeconstruedas grantingby
implication, estoppel, orotherwise,alicenseor right ofuseofNovatelWireless or any other Trademark
displayedinthis user manualwithout thewrittenpermissionofNovatelWireless or its respective
owners.
NovatelWireless, andtheNovatelWireless logo arealltrademarksofNovatelWireless, Inc.
MiFi® andtheMiFilogo areregisteredtrademarks ofNovatelWireless,Inc.

iii
Contents
Introduction.........................................................................................................................................4
MT 3060 Models............................................................................................................................................2
Prerequisites..................................................................................................................................................3
Initial Steps ...............................................................................................................................................3
Troubleshooting...................................................................................................................................4
GPSIssues ...................................................................................................................................................10
GPS Drift Issue.........................................................................................................................................10
GPS Lock Issue........................................................................................................................................10
OBDIssues...................................................................................................................................................11
Device Reports an Incorrect VIN ............................................................................................................11
Device Reports a Corrupted VIN............................................................................................................11
OBD Device Does Not Correctly Report Ignition On Or Off ..................................................................11
OBD Device LEDs Do Not Blink ..............................................................................................................12
Troubleshooting Conclusions.....................................................................................................................13
Extended Debug................................................................................................................................14

1
1
Introduction
MT 3060 Models
Prerequisites

MT 3060 U Troubleshooting Guide 2
MT 3060 Models
The NovatelWireless MT3060 comes in three models:
§MT 3060G
§
MT 3060 R
§MT3060U
ThistroubleshootingguidereferstotheMT 3060U, which contains a micro SIM.TheMT 3060G is similar,
butcontainsaminiSIM.TheMT 3060R doesnot include a SIM.
Top View

MT 3060 U Troubleshooting Guide 3
Prerequisites
Beforesubmittingarequest foran RMA, basicdiagnosticsteps shouldbeperformed.
§The device must be available on thedevice manager and data collection server.
□You canperform mostbasic troubleshooting stepson thedevice itself before
reporting to a server,where device indicators and basic information can be retrieved.
§Use a test jig to acquire more detailed debug information. This requires you to set up a
separate test area or usean OBD extension cableto power up the device. You will needthe
following to do this:
□Mini-jig
□OBD extension cable
□Access to the pogo pin holes by removing the top lid label
□A terminal program to communicate to the device
Initial Steps
First determine if the device is reporting data. If the device is reporting to the cloud-based DM server
and local server, continue to troubleshoot the GPS or OBD relatedissues described in the next chapter.

MT 3060 U Troubleshooting Guide 4
2
Troubleshooting
GPS Issues
OBD Issues
Troubleshooting Conclusions

MT 3060 U Troubleshooting Guide 10
GPS Issues
Perform the troubleshooting steps below if the device is reporting, but no valid GPS coordinates are
obtained.
GPS Drift Issue
1. Verify whether the device ever had a valid GPS lock.
2. If thedevicereportsalocation,butit isinaccurate, verify that the lid of the device is properly
secured. This isimportant because the GPS antenna is built-in.
3. Marginal GPS reception can be affected bya less than optimal environment (such as a parking
garage or in avehicle without a good line of sight to the sky). Changing the device location
can improve GPS performance.
4. If GPS performanceis continually poor,even indifferent in different vehicles, the cause may
be related to GPSlock, as described below.
GPS Lock Issue
1. If thedevice has difficultygetting a GPS fix, or cannot fix at all, check the GPS antenna pins.
Bent pins can occur whena SIM is replaced and the device is opened.
2. If the cannot obtain a GPSlock, verify that the pins are not making contact withthe copper
pads on the main board.

MT 3060 U Troubleshooting Guide 11
OBDIssues
Perform the troubleshooting steps below if the device is reporting, but the On-BoardDiagnostic
(OBD) information, such as the VIN, is incorrect.
NOTE: Before testing, be sure that the device isinstalled in the vehicle with the ignitionoff. Do
not plug in thedevice when the vehicle is already running. This may result in indeterminate
results if the device has not detected all protocols.
NOTE: Dependingon thenetwork, it can take up to 2.5 minutes for the device to register on
the network andobtain an IP address after power up.
Device Reports an Incorrect VIN
1. Compare the VINofthe physical vehicle to the reported VIN.
a. If the reportedVIN is incorrect, try the devicein a other vehicle.
b. Determineifthe deviceID matches the vehicle it is plugged into.
Device Reports a Corrupted VIN
1. Verify whether the VIN is consistentlyincorrect.
a. If the VIN is partially correct, it is possible that the vehicle is noton the vehicle
compatibility list.
b. If the vehicle ison the list:
i. Try a different vehicle to see ifthe devicereports correctly.
ii. Try a different device in the same vehicle.
c. If the vehicle isnot on thelist:
i. Contact NVTL Tech Support to learn if any issueshave been reported against the
vehicleanddevicecombination.
OBD Device Does NotCorrectlyReport Ignition On Or Off
1. Verify whether the device has reported anymessages to theserver.
a. If not, thiscouldbe the result of a vehicle compatibility issue.
i. If other vehicles ofthe same year,make, and model do nothave theissue, it
could be an OBD MT3060 device issue.

MT 3060 U Troubleshooting Guide 12
ii. Try a different devicein the same vehicle.
b. The vehicle starter can cause a voltage increase to charge the battery of the vehicle.
Using a voltmeter, with the ignition on and the car running, make surethe battery
voltage is over 13.15V.
i. Ignition detection is based on multiple conditions:
1. A voltage of over 13.15V needs to be generated.
2. When the device has ECU protocol detect, itwilllookforRPMand/or
ECU speed to be present in order for the vehicle to declare the
ignitionon.
3. Forignitionoff,the opposite is needed: voltage below 13.15V and no
RPM and/or ECU speed detected
4. The voltage required to wake the device is set by AT$OBDIV. The
default is 13.15V. (See Chapter 3 formore information onusing AT
commands via a terminal connection.)
OBD Device LEDs Do Not Blink
1. Verify whether the device is in the correct state for lighting LEDs.
a. The device will turnoff allLEDs when in deepsleep or after five minutes, depending
on a timer setting to save vehicle batter power.
i. If the LEDs don’t lightor only the red LED blinks, the issue might be with the
device.
1. Verify that device has been unpluggedfor morethan five minutes.
The device could beoperating in battery backup mode without the
LEDs on.
2. If the device has been offfor more thanfive minutes,reinsert the
device and verify that all lights start blinking when ignition is turned
on.
a. If thedevice registers with the network, the green LED
should start blinkingslowly.
b. The yellow LED indicatesGPS lock. If the yellow LED blinks
quickly, thereisno GPS lock.
c. The red LEDis for protocol detect between the OBDdevice
and the vehicle ECU. When the device detects the protocol of
the vehicle,it will blink slowly.

MT 3060 U Troubleshooting Guide 13
TroubleshootingConclusions
The following conditions might indicate fault with the device:
§If the devicenever obtains a GPS lock andthe antenna pins arenot bent.
§If the device never registers on the livenetwork, a SIM isinserted in thedevice,and the SIM
was verified to be active and the correct SIM.
§If the device never gets OBD protocol detectand thevehicle works with adifferent MT 3060.
If device is found to be defective basedon the aboveinformation,follow the RMA procedure,
providinga clear description of theissue found, procedures used to detect the issue, and theID of
the device.

MT 3060 U Troubleshooting Guide 14
3
Extended Debug
In order to communicate with thedevice locally, you will need afixture and away to power thedevice.
The device can beinstalled in a vehicle. This requires that the device connected to an OBDextender
cable, in order to use the fixture and enable communicate with a terminal program on a laptop.
You can also communicate with the devicein the fixture using the provided power supply, but this will
limit the capabilities of thedevice. Certainfunctions,such as protocol detect or ignitionon/off,would
have to be simulated separately.
NOTE: Remove the top label to access the pin holes.
The following section shows AT examples that can be used for debug. This assumes that you are using a
fixture and drivers areinstalled to enable communication with thedevice via a terminal program. (For
more details, see the MT 3060 AT CommandReference.)
AT > Send an AT command
OK > Response OK terminal
at$pkg > Get Firmware version for radio of device
2-D7
OK
at$obdver? > Get Firmware version for OBD of device
$OBDVER: 1-D8
OK
at$nwgmr? > Get detailed version information
Chipset: QSC6270
Radio: 20.2.2.51
Smart Agent: 22.5
App: 3.5
HW Rev: 0,0,1
PRI Info: 90029243 Rev 1 MT 3060 HT NA V2-D7
PRI Version: 1

MT 3060 U Troubleshooting Guide 15
OK
at+csq > Get signal strength (8 is marginal signal (-97dBm) up to 0-31,99 [Unknown]
+CSQ: 8,99 9 = -95 dBm every step up is 2 dBm signal
OK
AT+CREG? > Registration status 0,1 = registered home network 0,5 = registered roaming
+CREG: 0,1 0,2 = scanning for network for UMTS and GSM (MT3060U + MT3060G)
OK
0 = not registered, ME is not currently searching a new operator to register to
1 = registered, home network
2 = not registered, but ME is currently searching a new operator to register to
3 = registration denied
4 = unknown
5 = registered, roaming
AT$CREG > +CREG: <n>,<stat>[,<lac>,<ci>] Registration status similar
$CREG: 1,3,7082,1
OK
$CREG status is synthesized from CDMA information and approximates the GSM
+CREG:
0 = airplane mode
1 = registered on home network
2 = registration in progress
3 = no service
4 = unknown
5 = registered roaming
AT+CGDCONT? > Check the APN setting tied to the account and SIM for data
+CGDCONT: 1,"IP","apn.sim.com","",0,0
OK
at$areg? > Check if device will get an IP connection automaticly (2)
$AREG: 2
OK
at$netip? > Check for IP address
$NETIP: "10.204.113.18","10.20.3.20","10.10.3.20"
OK
at$msglogrd? > Check if messages are send (3)
$MSGLOGRD: 0, 3, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
OK
at$msglogrd? > 2,x,x means 2 messages in the que to be send
$MSGLOGRD: 2, 5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0
OK
at$evtqry=178 > Check ignition status 1= on 0= off
$EVTQRY: 178=0 (bInit=1)
OK
at$obdtyp? > Check OBD protocol detect (if hooked to ECU) 3 = ISO 15765 500 kHz 29 bit
$OBDTYP: 3, 0
OK
AT$OBDTST=17 > Returns some useful OBD information. Not all OBD parameters support buy all vehicles
OBD prot 255, state 0, std 0, volts 12247, air temp 0
MAF 0, SSC 0, mil_on 0, DCC 0

MT 3060 U Troubleshooting Guide 16
Mode 1 Pid 2 FzDTC 0000, Mode 2 Pid 2 FzDTC 0000
Fuel: Sts 0, input 0, pres 0, type 0, eth 0
Engine: load 0, temp 0, rpm 0, time 0, kmh 0
VIN: , odo 0 vin msg 0:0:0