history
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| history [2026/08/31 07:20] – pkovar | history [2026/10/09 12:46] (current) – pkovar | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== pNav History ====== | ====== pNav History ====== | ||
| - | The pNav GPS receiver project began in 2013. The Czech Technical University students planned to participate in the QB50[[https:// | + | The pNav GPS receiver project began in 2013. The Czech Technical University students planned to participate in the QB50[[https:// |
| I appreciated this initiative, as our university launched a new aerospace study program in which I was responsible for teaching radio navigation and radio communication. | I appreciated this initiative, as our university launched a new aerospace study program in which I was responsible for teaching radio navigation and radio communication. | ||
| - | Unfortunately, | + | Unfortunately, |
| ---- | ---- | ||
| Line 12: | Line 12: | ||
| The Witch Navigator was a research dual-frequency GNSS receiver designed as a PCMCIA card for a PC. Witch Navigator is absolutely incompatible with a 1U CubeSat platform! | The Witch Navigator was a research dual-frequency GNSS receiver designed as a PCMCIA card for a PC. Witch Navigator is absolutely incompatible with a 1U CubeSat platform! | ||
| - | At that time, I had defined the following **high-level requirements** on the **new navigation receiver** for a CubeSat that I respected for all years of development of the pNav L1 receiver: | + | At that time, I had defined the following **high-level requirements** on the **new navigation receiver** for a CubeSat |
| + | that guided the entire | ||
| * The CubeSat navigation receiver should be as simple as possible | * The CubeSat navigation receiver should be as simple as possible | ||
| - | * It should integrate all necessary parts for navigation in the LEO Orbit, but not more | + | * It should integrate all necessary parts for the navigation in Low Earth Orbit (LEO), but not more |
| - | * It should be compatible with a 1U CubeSat platform, | + | * It should be compatible with a 1U CubeSat platform, |
| * The applied signal and measurement processing algorithms should be simple and very robust | * The applied signal and measurement processing algorithms should be simple and very robust | ||
| Line 22: | Line 23: | ||
| ===== pNav Milestones ===== | ===== pNav Milestones ===== | ||
| - | pNav receiver | + | pNav receiver |
| The receiver is marketed by the company SkyFox of Jaroslav Laifr. | The receiver is marketed by the company SkyFox of Jaroslav Laifr. | ||
| Line 31: | Line 32: | ||
| * **2016: Introduction to the market** - GPS L1 C/A receiver with the 15 GPS L1 E-L correlators. Serial acquisition based on N of M algorithm. The typical receiver' | * **2016: Introduction to the market** - GPS L1 C/A receiver with the 15 GPS L1 E-L correlators. Serial acquisition based on N of M algorithm. The typical receiver' | ||
| - | * **2017: Acquisition unit ** The problem of the pNav receiver from the beginning till the introduction of pNav2 is a problematic | + | * **2017: Acquisition unit ** From its inception until the introduction of pNav2, one of the main limitations of the pNav receiver was its slow cold start and position |
| | | ||
| * **2018: Buying and implementation of a GPS software simulator ReGen** by IPSolutions. | * **2018: Buying and implementation of a GPS software simulator ReGen** by IPSolutions. | ||
| Line 39: | Line 40: | ||
| * **2022: Application of the orbital position propagator** with the aim of overcoming GPS position dropout and improving the receiver reacquisition. | * **2022: Application of the orbital position propagator** with the aim of overcoming GPS position dropout and improving the receiver reacquisition. | ||
| | | ||
| - | * **2026: Last update of the original pNav of Almanach | + | * **2026: Last update of the original pNav of Almanac |
| | | ||
| * **2026: Introduction of [[Start|pNav2]]** | * **2026: Introduction of [[Start|pNav2]]** | ||
| Line 54: | Line 55: | ||
| * **Long lifetime** in LEO thanks to the conservative design and selection of the components | * **Long lifetime** in LEO thanks to the conservative design and selection of the components | ||
| * **Matured design ** | * **Matured design ** | ||
| - | * **Heritage** in Laucy 7 CubeSat and satellites of our customers | + | * **Heritage** in Lucky 7 CubeSat and satellites of our customers |
| < | < | ||
| Line 62: | Line 63: | ||
| === Weaknesses === | === Weaknesses === | ||
| - | * **Problematic acquisition and reaqusition** due to the low performance signal processor. The receiver | + | * **Problematic acquisition and reacquisition** due to the low performance signal processor. The receiver |
| * **Basic handling of the navigation signals reception errors** | * **Basic handling of the navigation signals reception errors** | ||
| * **Non-configurable NMEA protocol** | * **Non-configurable NMEA protocol** | ||
| </ | </ | ||
| - | [[Versions Comparison|pNav Comparison]]. | + | /* detailed comparison of pNav and pNav2 can be found here [[Versions Comparison|pNav Comparison]].*/ |
| ---- | ---- | ||
| ===== Conclusion ===== | ===== Conclusion ===== | ||
| Line 75: | Line 76: | ||
| * Increasing the robustness of the software. Consistent verification of the navigation message reception with the aim of detecting undetected errors through channel coding. Verification of the position input and output data and proper function of the position, velocity, and time algorithm. | * Increasing the robustness of the software. Consistent verification of the navigation message reception with the aim of detecting undetected errors through channel coding. Verification of the position input and output data and proper function of the position, velocity, and time algorithm. | ||
| * Development of the high-performance, | * Development of the high-performance, | ||
| - | * Reliable positioning of the unstabilized, | + | * Reliable positioning of unstabilized, |
history.1788153609.txt.gz · Last modified: by pkovar
