$PGLOR,2,PFM,HAL,P,0,0,0.0,0.0,RF,P,125.,0.0,0,RTC,40.0,P,STO,F,LTO,-,SW,P,CNTIN,MP,220,OSC,P,F,P*76
1 2 3 4 5 6 7 8 9 A C D E F G H I J K L
The fields are:
- 2 - Sentence version [2]
- HAL performance has items 2 through 6:
- 2 - Passed/Failed/Inconclusive P/F/-
- 3 - Number of detected Tx errors 0 to 999 Must be 0 to pass
- 4 - Number of detected Rx errors 0 to 999 Must be 0 to pass
- 5 - Packets with latency less than 300 ms 0 to 100% Must be 0% to pass
- 6 - Packets with latency more than 1000 ms 0 to 100% Must be 0% to pass
- RF performance has items 7 through A:
- 7 - Passed/Failed/Inconclusive P/F/-
- 8 - Maximum signal strength [dBm] -180 to -120 Must be -125 or higher to pass. Measures GPS antenna performance.
- 9 - GPS WER (on SV >-135 dBm) 0 to 100 [%] Must be 0% to pass
- A - Clock stability P/F/- 40ppb/first 10s; 10ppb/10s; 5ppb/s. See PGLOR,STA for details
- RTC results have two items:
- C - RTC error [ppm]
- D - Pass/Fail/Not confirmed P/F/-
- STO - Non volatile storage
- E - Pass/Fail/Not confirmed P/F/-
- LTO - LTO
- F - Pass/Fail/Not confirmed P/F/-
- SW - Software
- CNTIN - TCXO Calibration
- H - Status:
- ST - started
- NM - not measured. Failure of the HAL or RILD.
- MP - measured and passed.
- MF - measured and failed.
- CP - measured and passed, then offset subsequently confirmed within offset uncertainty by GNSS clock measurements.
- CF - measured and passed, then offset subsequently confirmed to be wrong.
I - Calibration clock offset report in units of PPB. If the CNTIN status in field H indicates "NM", then the field "I" will be one of below error strings:
- UNUSED - CNTIN was not used
- OOR - Calculated Frequency out of range
- NOIN - No input frequency was detected on CNTIN pin
- UDEAD- HAL failed to call RefFreqStatus() on GlEngineOnFreqUpdate callback request
- UCANCEL - User reported refrence frequency as unreliable during the CNTIN interval
- MOLD - User measurement of the calibration frequency is too old
- MUNC - User measurement of the calibration frequency is too uncertain
- UNK - Unknown error
OSC - Reference Clock Drift 'Pass/Fail/,,(untested)' for three time spans, where the thresholds and reporting time spans are: In below explanation, "operation" refers to the time of "first valid reference clock update".
- J - drift within the first 10s of operatation should be less than 40ppb
- K - drift after the second 10s (and any subsequent 10s thereafter) of operatation should be less than 10ppb
- L - drift should be less than 5ppb/s (after the initial 10s)
To test the reference clock stability on a platform using the clock drift P/F,please make sure following is true of test setup.
- Test should be done on a simulator/open sky with signal strengths between -130dBm to -140dBm.
- A cold start test should be run with clean NVRAM with atleast 30 valid fixes as a pre-test.
- Let the device to cool down for 5 minutes.
- Run hot starts on the device and validate reference clock stability based on the PFM.
See PGLOR,STA for specific clock offsets.
SW,F indicates the GLL had a recoverable internal error. If possible enable full logging, repeat the test conditions, and send the log file to your Broadcom GPS AE or FAE.
[Version: 2]
Previous versions:
[Version: 1] $PGLOR,1,PFM - Platform Status
[Version: 0] $PGLOR,0,PFM - Platform Status
[Version: before GLL v18] $PGLOR,PFM - Platform Status