Space Exploration Stack Exchange is a question and answer site for spacecraft operators, scientists, engineers, and enthusiasts. It only takes a minute to sign up.
Sign up to join this community
How does NASA know the exact position of James Webb Space Telescope at a given time? NASA has to be able to issue the mid course correction burns.
Since they are now up to MCC2, how do they determine the exact time and force required to enter the L2 halo orbit? Is it a matter of good old fashioned dead reckoning?
How does NASA know the exact position of James Webb Space Telescope at a given time?
Now that it has launched, NASA doesn't know the exact position of the JWST at any point in time. The three sigma position and velocity errors at MCC-2 were estimated to about 29 km and 21 cm/s, respectively. That's not exactly "exact".
Since they are now up to MCC2, how do they determine the exact time and force required to enter the L2 halo orbit?
Fortunately, NASA doesn't need to know the exact time and force. The project would be toast if they did. (Any project that needs "exact" position and velocity would be toast.) What NASA doesn't want to is to push the spacecraft so hard that a subsequent correction burn would require the vehicle to rotate to such an extent that the cold side becomes sun-facing. On the other hand, a slight undershoot is okay. I suspect the JWST Flight Dynamics Team will err on the side of caution and target a slight undershoot. (Or probably did err on the side of caution side as MCC-2 has now been performed.)
Is it a matter of good old fashioned dead reckoning?
TL;DR synopsis
Absolutely not. Relying on dead reckoning and nothing else is a good way of ensuring that the vehicle will soon be dead. I do not see any references that indicate that the JWST uses dead reckoning at all.
Details
I see zero evidence that the JWST self-navigates its translational state. Instead what I see are papers going back to 2003 trying to determine whether the JWST needs accelerometers at all. If the spacecraft does have accelerometers, it would only be for the purpose of determining when to terminate a delta V maneuver. In particular, accelerometers would not be needed if the JWST Secondary Combustion Augmented Thrusters (SCAT thrusters) are so precise that the error between predicted and actual delta V is within 1.5%, but absolutely would be needed if the error is over 5% (three sigma).
I've yet to see a thruster whose predicted - actual delta V is less than 1.5%. Ive seen many where predicted - actual delta V exceeds 5%. My guess is that the JWST does have accelerometers, but that's just a guess. The literature on the onboard sensors JWST related to propulsion is rather scant. There's lots of literature on attitude and attitude rate sensors, but almost none on sensors related to propulsion.
In any case, I see no literature crowing about the JWST's onboard translational navigation capabilities. If the JWST was using dead reckoning, augmented of course by occasional corrections from NASA, there would be paper upon paper upon paper crowing about this new capability.
Stealing a term from software, YAGNI (You Aren't Gonna Need It) and KISS (Keep It Short and Simple) apply in droves to capabilities on a spacecraft. Most spacecraft do not know where they are because they don't need to do so and because Guidance, Navigation, and Control software oftentimes is the most complex and expensive software on vehicles that do need it.
The Space Shuttle and International Space Station software are extreme examples. Counting all of the people who wrote flight software, wrote unit tests of that flight software, wrote simulation code to further test that flight software, people who maintained the test environment, testers who ran the tests, and evaluators who poked and prodded at everything, the Shuttle and ISS flight software was written at the mind numbing pace of one line of code per person per week. I suspect the JWST flight software was written at the more typical rate of one line of code per person per day, or maybe even per hour. One line of code per person per hour would be phenomenal.
Even at this phenomenal rate of one line of code per person per hour, YAGNI and KISS would dictate that eliminating the many thousands of lines of mathematically complex, error prone, and computationally expensive flight software code needed for a spacecraft to self-navigate via dead reckoning is a good idea if that capability is not needed. And it's not needed in the case of the JWST.
What the JWST does need to do, with very high precision, with very high accuracy and with very high smoothness, is to know where to point itself and to point its telescope with respect to the "fixed" stars. There is lots and lots of literature on this JWST capability. The JWST team crows about these capabilities, and that crowing is very well justified.
What the JWST does not need to do is to know where it is. Knowing where the JWST is is a collaboration between NASA's Deep Space Network (DSN), managed by the Jet Propulsion Laboratory, and the JWST Flight Dynamics Team, managed by and hosted at the Goddard Space Flight Center. The DSN measures range (distance to the spacecraft) and range rate (time derivative of range) extremely precisely. Additional precise measurements can be made when multiple DSN ground stations can communicate with the spacecraft simultaneously.
The DSN provides these precise measurements to the JWST Flight Dynamics Team, which is responsible for determining the JWST state (position and velocity) and for planning mid-course corrections, orbit maintenance maneuvers, and momentum dumping maneuvers. This is the antithesis of dead reckoning. Techniques for precision orbit determination go back to Gauss, and the techniques have improved markedly since Gauss's time. Gauss's techniques involved azimuth and elevation measurements only; range and range rate were not available. Range and range rate are so precise for spacecraft beyond low Earth orbit that modern precision orbit determination techniques oftentimes ignore azimuth and elevation measurements as overly noisy parameters.
References
Anne Long et al., "Navigation concepts for the James Webb space telescope," 2003 Flight Mechanics Symposium (2003)
Sungpil Yoon et al., "James Webb Space Telescope Orbit Determination Analysis," (2014).
J. Levi et al., "The JWST Flight Dynamics Operations Concept and Flight Dynamics Ground System," 2020 IEEE Aerospace Conference (2020).
Range is measured by radio. The base station at Earth sends a coded signal which is repeated back by the satellite. The delay time is a measure of distance and can be measured accurately on ground. It is not quite as easy as that as the returned signal is sent on a different frequency at a fixed ratio (signal is divided) and the ground station is on Earth and does move with Earth's rotation plus for a short while the signal moves through Earth's atmosphere at a slightly different speed compared to space.
The best description I have seen on how this is done (although an older technical version used in Apollo) is in the YouTube video Apollo Comms Part 1 starting at about 03:45. A further description (quite technical) is found in JWST sequential ranging.
Relative speed is measured by the Doppler effect. The returned signal has a fixed frequency ratio (which is as designed) in the satellite, but it will be shifted by the Doppler effect. And again, the ground station is moving with Earth's rotation, but this is a known factor that is compensated for.
Direction to the satellite is measured in relation to the "fixed" stars using optical (rarely) and radio telescopes. As both direction and distance then is known it is possible to calculate the "position".
--- further additions to the answer ---
As for dead reckoning: it is sort of used, but based on the measurements. Distance, relative speed (compared to earth) and relative direction can all be measured with high accuracy. As the Newton "laws" of movement are well known this can be used to update the state vector (3 x position, 3 x movement) between measurements, a sort of dead reckoning but updated / corrected when new data is available. Comparing the state vector to the wanted trajectory is used to calculate burns by ground based computers. The spacecraft is then ordered to orient itself in relation to known fix stars (star trackers used) and then run thruster X for Y seconds. The spacecraft as such does not need to know its position as all calculations are done on earth. As the burns are never totally accurate, after the burn a period of detailed measurements are done again to update the maximum error of the state vector. In mid flight the measurements can be done less often and/or with methods having higher maximum errors.
An anecdote that hints at the way the DSN measures the range to space.
Back in the 1980/90s, I was an engineer working on signal generators. NASA had bought a number of our signal generators a few years ago to use in satellite ranging by carrier phase triangulation, and wanted a repeat order.
We had stopped making the model they bought last time, so offered an 'improved' model. This had better 1 kHz offset phase noise (important for the communications applications we were mainly targeting), by including an internal 10 MHz crystal oscillator, phase locked to the external standard, to clean up standard noise at that offset.
They evaluated this new signal generator, and rejected it. DC drift in the phase detector that locked the noise cleanup oscillator meant that they had poorer tracking of output carrier phase between several generators locked to the same reference standard.
Once we introduced a switch to bypass the new filter, they bought 24. That shows that carrier phase accuracy is indeed important for that particular method.
