4 ms·

> You need a precise clock for any form of GNSS[0] to function How precise? I assume that inaccuracy in the clock produces imprecision in location - how much t

> You need a precise clock for any form of GNSS[0] to function How precise? I assume that inaccuracy in the clock produces imprecision in location - how much time inaccuracy produces how much location inaccuracy? > And anyway, modern GNSS chips are.. $1? Cheaper? No way you wouldn't use GNSS already deployed and working (and you are not paying for it) in a commercial product. Rather than using the Starlink satellites as an alternative to GPS - get a location fix using both Starlink and GPS, and compare them. Even given the former is going to be significantly less accurate - suppose GPS is accurate to within 5 metres and Starlink is accurate to within 5000 metres - well, if the two differ by 50,000 metres, you know something is going wrong, and the terminal might decide to disable itself in such a situation.

justsomehnguy 3y ago
> How precise GNSS satellites orbits are between 20000km and 30000km. 20kkm is 0.06671s of c, 30kkm is 0.10007s, 5km is 0.000016678. So a very precise, that's why they have an atomic clock on board instead of cheap quartz one. > if the two differ by 50,000 metres, you know something is going wrong Like what your imprecise methods give you a very rough estimate where is the terminal and your legitimate customers in the nearby areas (not even doing anything for or against) are saying thanks for their shut off terminals. https://upload.wikimedia.org/wikipedia/commons/b/b4/Comparison_satellite_navigation_orbits.svg https://upload.wikimedia.org/wikipedia/commons/b/b4/Comparis... https://www.omnicalculator.com/physics/light-year https://www.omnicalculator.com/physics/light-year