Thanks for the video. Can you explain that how the phase center measurement error of the GNSS antenna can affected the accuracy of detection the exact position?
I can try :) As I'm sure you already know, the phase center of a GNSS antenna is different from the actual physical center of the antenna and this is concern in applications that require extremely high position accuracy. The difference between the phase center and physical center changes based on numerous factors such as the position of the SV (azimuth and elevation) as well as the frequency of the received signal (e.g. L1 vs L2 vs L5 in GPS). In order to minimize this error, calibration of the GNSS receiver antenna can be used. One way of doing this calibration is by sending signals into the antenna at various azimuth and elevation values (in a shielded chamber or at an open air range) and using a vector network analyzer to measure and record the phase differences so that these can be removed in the final navigation solution. Hope that's helpful!
So if the code is used to determine positioning, why is precise timing via atomic clocks required for PNT? Is it just for accurate timing, (the T in PNT)?
The short answer is the GPS is really about timing, not positioning :) Position is determined (by the receiver) based on the time it takes the signal to travel from the well-known positions of multiple satellites to the receiver. Most people tend to think about GPS as providing a "position", but I would say that most (behind-the-scenes) applications of GPS are really more about having a precise time source.
If you read the US government ICD's for GPS (e.g. IS-GPS-200), you'll see they are using "L" to abbreviate "link", e.g. "GPS for radio frequency (RF) link 1 (L1) and link 2 (L2)." GPS is in the L-band, but that's not where the abbreviation comes from :)
You incorrectly utilized the "cross-correlation" term. Aligning the codes is simply correlation, or perhaps autocorrelation. Cross-correlation is the interference effect between multiple codes. Typically when this happens the codes are mistakenly aligned, causing the receiver to track one satellite, but believe it to be another.
Thanks for the feedback. In retrospect, I probably should have just said "(code) correlation," since the distinction between cross-correlation and auto-correlation is not often made (or rigidly adhered to) in the GNSS literature. But I do stand by my use of "cross correlation" since this is the more general description of the process of comparing two time displaced series, regardless of whether they are supposed to be the same or not :)
Great fundamentals video on GPS. Once again, nice job Paul.
I don't know who Paul is, but yeah well done Paul !
You guys make the fundamentals amazing! Awesome video...
Thank you!
Your work is truly awesome. You make it interesting. Thank you very much.
Thank you - it is a labor of love :)
Thanks for the video, I understand now how the gps (and others) system works.
Thanks for the feedback! Glad it was helpful
Great video
Great video. Very informative.
Thank you!
Thanks for the video. Can you explain that how the phase center measurement error of the GNSS antenna can affected the accuracy of detection the exact position?
I can try :) As I'm sure you already know, the phase center of a GNSS antenna is different from the actual physical center of the antenna and this is concern in applications that require extremely high position accuracy. The difference between the phase center and physical center changes based on numerous factors such as the position of the SV (azimuth and elevation) as well as the frequency of the received signal (e.g. L1 vs L2 vs L5 in GPS). In order to minimize this error, calibration of the GNSS receiver antenna can be used. One way of doing this calibration is by sending signals into the antenna at various azimuth and elevation values (in a shielded chamber or at an open air range) and using a vector network analyzer to measure and record the phase differences so that these can be removed in the final navigation solution. Hope that's helpful!
So if the code is used to determine positioning, why is precise timing via atomic clocks required for PNT? Is it just for accurate timing, (the T in PNT)?
The short answer is the GPS is really about timing, not positioning :) Position is determined (by the receiver) based on the time it takes the signal to travel from the well-known positions of multiple satellites to the receiver. Most people tend to think about GPS as providing a "position", but I would say that most (behind-the-scenes) applications of GPS are really more about having a precise time source.
How do you get the "length" of the code in meters?
lambda = c/f
🙏🙏🌹🌹
I always tought that L1, L2, L5... referred to L-band 1, L-band 2, etc.
The L-band refers to the 1 - 2 GHz spectrum,
If you read the US government ICD's for GPS (e.g. IS-GPS-200), you'll see they are using "L" to abbreviate "link", e.g. "GPS for radio frequency (RF) link 1 (L1) and link 2 (L2)." GPS is in the L-band, but that's not where the abbreviation comes from :)
You incorrectly utilized the "cross-correlation" term. Aligning the codes is simply correlation, or perhaps autocorrelation. Cross-correlation is the interference effect between multiple codes. Typically when this happens the codes are mistakenly aligned, causing the receiver to track one satellite, but believe it to be another.
Thanks for the feedback. In retrospect, I probably should have just said "(code) correlation," since the distinction between cross-correlation and auto-correlation is not often made (or rigidly adhered to) in the GNSS literature. But I do stand by my use of "cross correlation" since this is the more general description of the process of comparing two time displaced series, regardless of whether they are supposed to be the same or not :)