GPS Debugging
Irvin Jacobson
Reference documents:
FSM GPS SW Design: T:\RnD\SW\Release Docs\SR14.20\sw_fsm_GPS.docx
XLP GPS SRS: T:\RnD\SW\Release Docs\SR12.00 (all 3 documents therein)
SRS for AS12: \\Fs11\dfs\PLM\SystemEng\SRS\docs\AS12-Overview
From lteCli:
db get gpsStatus
In logs and in the db table, the state is mentioned by number:
Example: gps_status=3 means GPS is in state modeLocked
# GPS_modeUnknown 0
# GPS_modeInitialising 1
# GPS_modeLockedWarmUp 2
# GPS_modeLocked 3
# GPS_modeLockedWtrDegraded 4
# GPS_modeLockedWtrExpired 5
# GPS_modeHoldoverGuaranteed 6
# GPS_modeHoldoverDegraded 7
# GPS_modeHoldoverExpired 8
db get nodeSyncTraps
|index||nodeSyncAlarmStatus|nodeSyncLockStatus|nodeGPSReceiverStatus|
| 1|| 0| 2| 1|
In able to enable and view logs for GPS on the eNB you need to send the following:
This is for FSM
logger threshold set process=gpsMngr std_out=0
This will provide you with the current status and results of the GPS System.
For example:
Here you can see the SVs seen and their tracking status.
28-11-2017-18:24:01:592: :08/10/2017 00:49:10:310 <gpsMngr:GPS HIGH>
_syncMgrEventIndCb(),eventIndId=34
28-11-2017-18:24:01:592: :08/10/2017 00:49:10:885 <gpsMngr:GPS HIGH> SV INFO report:
altitudeAssumed = 1, svListValid = 1, svListNum = 19
28-11-2017-18:24:01:593: :08/10/2017 00:49:10:885 <gpsMngr:GPS MEDIUM> id=0, valid=251, system
= 1, gnssSvId=5, healthStatus=0, tracked=3, snr=35.10, elevation=37.00, azimuth=292.00
28-11-2017-18:24:01:593: :08/10/2017 00:49:10:885 <gpsMngr:GPS MEDIUM> id=1, valid=251, system
= 1, gnssSvId=7, healthStatus=0, tracked=3, snr=27.80, elevation=46.00, azimuth=37.00
28-11-2017-18:24:01:594: :08/10/2017 00:49:10:885 <gpsMngr:GPS MEDIUM> id=2, valid=251, system
= 1, gnssSvId=8, healthStatus=0, tracked=3, snr=30.50, elevation=15.00, azimuth=64.00
28-11-2017-18:24:01:594: :08/10/2017 00:49:10:885 <gpsMngr:GPS MEDIUM> id=3, valid=251, system
= 1, gnssSvId=9, healthStatus=0, tracked=3, snr=37.30, elevation=39.00, azimuth=112.00
28-11-2017-18:24:01:594: :08/10/2017 00:49:10:885 <gpsMngr:GPS MEDIUM> id=4, valid=251, system
= 1, gnssSvId=13, healthStatus=0, tracked=3, snr=35.50, elevation=11.00, azimuth=307.00
28-11-2017-18:24:01:595: :08/10/2017 00:49:10:885 <gpsMngr:GPS MEDIUM> id=5, valid=155, system
= 1, gnssSvId=17, healthStatus=0, tracked=3, snr=22.80, elevation=0.00, azimuth=0.00
28-11-2017-18:24:01:595: :08/10/2017 00:49:10:885 <gpsMngr:GPS MEDIUM> id=6, valid=251, system
= 1, gnssSvId=23, healthStatus=0, tracked=3, snr=34.70, elevation=8.00, azimuth=120.00
28-11-2017-18:24:01:595: :08/10/2017 00:49:10:885 <gpsMngr:GPS MEDIUM> id=7, valid=251, system
= 1, gnssSvId=28, healthStatus=0, tracked=3, snr=22.30, elevation=64.00, azimuth=181.00
28-11-2017-18:24:01:596: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=8, valid=251, system
= 1, gnssSvId=30, healthStatus=0, tracked=3, snr=40.30, elevation=62.00, azimuth=347.00
28-11-2017-18:24:01:596: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=9, valid=155, system
= 3, gnssSvId=128, healthStatus=0, tracked=3, snr=34.20, elevation=0.00, azimuth=0.00
28-11-2017-18:24:01:598: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=10, valid=155, system
= 1, gnssSvId=27, healthStatus=0, tracked=2, snr=0.00, elevation=0.00, azimuth=0.00
28-11-2017-18:24:01:616: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=11, valid=251, system
= 5, gnssSvId=14, healthStatus=0, tracked=3, snr=20.30, elevation=28.00, azimuth=248.00
28-11-2017-18:24:01:618: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=12, valid=251, system
= 5, gnssSvId=2, healthStatus=0, tracked=3, snr=24.30, elevation=56.00, azimuth=163.00
28-11-2017-18:24:01:634: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=13, valid=251, system
= 5, gnssSvId=13, healthStatus=0, tracked=3, snr=18.00, elevation=61.00, azimuth=310.00
28-11-2017-18:24:01:798: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=14, valid=251, system
= 5, gnssSvId=12, healthStatus=0, tracked=3, snr=14.20, elevation=26.00, azimuth=30.00
28-11-2017-18:24:01:798: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=15, valid=251, system
= 5, gnssSvId=3, healthStatus=0, tracked=3, snr=22.30, elevation=63.00, azimuth=317.00
28-11-2017-18:24:01:799: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=16, valid=251, system
= 5, gnssSvId=4, healthStatus=0, tracked=3, snr=11.90, elevation=9.00, azimuth=330.00
28-11-2017-18:24:01:799: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=17, valid=251, system
= 5, gnssSvId=22, healthStatus=0, tracked=2, snr=0.00, elevation=3.00, azimuth=75.00
28-11-2017-18:24:01:800: :08/10/2017 00:49:10:886 <gpsMngr:GPS MEDIUM> id=18, valid=155, system
= 5, gnssSvId=1, healthStatus=0, tracked=2, snr=0.00, elevation=0.00, azimuth=0.00
28-11-2017-18:24:01:800: :08/10/2017 00:49:10:886 <gpsMngr:GPS HIGH> SV INFO report:
numTrackedStaellites = 9, numVisibleSatellites=10, averageSnr=31, snrSum=282
28-11-2017-18:24:01:801: :08/10/2017 00:49:10:886 <gpsMngr:GPS HIGH>
QMI_LOC_EVENT_POSITION_REPORT_IND_V02 >>> received ind 0x0024 from handle 0x1b2bb8
28-11-2017-18:24:01:801: :08/10/2017 00:49:10:886 <gpsMngr:GPS HIGH> sessionStat = 0, [valid = 1]
latitude = 31.987536, [valid = 1] longitude = 34.912507
28-11-2017-18:24:01:801: :[valid = 1] altitudeSeaLevel = 87.000000, [valid = 0] timeUnc = 0.000000,
[valid = 1] timeSrc = 7
28-11-2017-18:24:01:801: :
Here you see that Qualcomm is reporting that everything is OK:
28-11-2017-18:24:01:802: :08/10/2017 00:49:11:285 <gpsMngr:GPS HIGH> validInfo=1,
comms_status=0, sessionStat=0,gpsOamStatus=0, enteredHoldover=0, self->oamGpsStatus=0
28-11-2017-18:24:01:802: :08/10/2017 00:49:11:286 <gpsMngr:GPS HIGH> latitude=0, longitude=0,
height=0, oamLockStatus=0, comms_status=0
28-11-2017-18:24:01:802: :08/10/2017 00:49:11:286 <gpsMngr:GPS HIGH> syncLocked=0,
oamLockStatus=0, communication_status=0 gps_status=1
28-11-2017-18:24:01:803: :08/10/2017 00:49:11:286 <gpsMngr:GPS HIGH> TrackTimeout:
commsLostCount=0 comms_status=0 locked_sts=1 snr_sts=0 rfBehaviour=1
28-11-2017-18:24:01:803: :08/10/2017 00:49:11:286 <gpsMngr:GPS HIGH> GPS_SetTimer
TrackStatusTimeout [RegistrationId = 502 timeout=2000[sec]
The value for srcTimeUnc should be as small as possible < 350, in order to achieve a fix:
28-11-2017-18:24:02:524: :08/10/2017 00:49:12:307 <gpsMngr:GPS HIGH> CLOCK_REPORT: Client (7)::
[valid=1]freqError=-0.45, [valid=1]freqUnc=3.54, [valid=1]srcTimeUnc=31, [valid=0]ftmTimeError=0
If all this is valid and you are still unable to achieve a fix, then you have a bug