If you wish to contribute or participate in the discussions about articles you are invited to contact the Editor
Lock Detectors: Difference between revisions
Rui.Sarnadas (talk | contribs) (Created page with "{{Article Infobox2 |Category=Receivers |Title={{PAGENAME}} |Authors=GMV |Level=Advanced |YearOfPublication=2011 |Logo=GMV }} Category:Receivers") |
No edit summary |
||
| Line 7: | Line 7: | ||
|Logo=GMV | |Logo=GMV | ||
}} | }} | ||
In nominal situations, GNSS receivers continuously output a navigation solution using the measurements generated by the tracking loops. The receiver must therefore ensure that the tracking loops are following correctly the incoming signal and that they have not diverged away from the solution. This is the purpose of the lock detectors that produce quality factors to assess how good the signal is being tracked. | |||
==Concept== | |||
The objective of the lock detectors is to assess whether the incoming signal is being correctly tracked at channel level or not. For that purpose, the GNSS receiver evaluates quality pre-defined quality parameters in order to assess: | |||
*Code lock of the [[Delay Lock Loop (DLL)|DLL]] | |||
*Phase lock of the [[Phase Lock Loop (PLL)|PLL]] | |||
*Frequency lock of the [[Frequency Lock Loop (FLL)|FLL]] | |||
These quality parameters may be obtained from the correlators’ outputs or cross-checking of internal information, as detailed hereafter. | |||
After computing these quality parameters, the receiver checks their values against pre-defined thresholds, which may depend on the application. As an example, if the receiver is targeting high accuracy, these thresholds might be tighter, whereas if the priority is on availability, then these thresholds are more likely relaxed. | |||
Once loss of lock is declared, the receiver may react in different ways. If only one of the loops loses lock (e.g. the PLL), then the receiver may decide to keep the other loops closed and to restart only this loop. Conversely, the receiver may decide that this loss of lock is unrecoverable and switch back to acquisition, see also [[Receiver Operations|Receiver Operations]]. | |||
These decisions are closely related to the receiver design and they are often the result of all the performance trade-offs related to the target application. | |||
==Code Lock Detectors== | |||
The concept behind the code lock detector is that, if the DLL is working correctly, then the received signal power is high. Since the received signal is noisy, code lock is often assessed by comparing the estimated Carrier to Noise ratio, <math>/est{C}/N_0</math>, with a pre-defined threshold. | |||
==Related articles== | |||
*[[Generic Receiver Description]] | |||
*[[Digital Signal Processing]] | |||
*[[Multicorrelator]] | |||
*[[Baseband Processing]] | |||
==References== | |||
<references/> | |||
[[Category:Receivers]] | [[Category:Receivers]] | ||
Revision as of 13:46, 3 May 2011
| Receivers | |
|---|---|
| Title | Lock Detectors |
| Author(s) | GMV |
| Level | Advanced |
| Year of Publication | 2011 |
In nominal situations, GNSS receivers continuously output a navigation solution using the measurements generated by the tracking loops. The receiver must therefore ensure that the tracking loops are following correctly the incoming signal and that they have not diverged away from the solution. This is the purpose of the lock detectors that produce quality factors to assess how good the signal is being tracked.
Concept
The objective of the lock detectors is to assess whether the incoming signal is being correctly tracked at channel level or not. For that purpose, the GNSS receiver evaluates quality pre-defined quality parameters in order to assess:
These quality parameters may be obtained from the correlators’ outputs or cross-checking of internal information, as detailed hereafter.
After computing these quality parameters, the receiver checks their values against pre-defined thresholds, which may depend on the application. As an example, if the receiver is targeting high accuracy, these thresholds might be tighter, whereas if the priority is on availability, then these thresholds are more likely relaxed. Once loss of lock is declared, the receiver may react in different ways. If only one of the loops loses lock (e.g. the PLL), then the receiver may decide to keep the other loops closed and to restart only this loop. Conversely, the receiver may decide that this loss of lock is unrecoverable and switch back to acquisition, see also Receiver Operations.
These decisions are closely related to the receiver design and they are often the result of all the performance trade-offs related to the target application.
Code Lock Detectors
The concept behind the code lock detector is that, if the DLL is working correctly, then the received signal power is high. Since the received signal is noisy, code lock is often assessed by comparing the estimated Carrier to Noise ratio, [math]\displaystyle{ /est{C}/N_0 }[/math], with a pre-defined threshold.