Bummer. As you know we had funny data loss issues with our launch as
well. GPS is hard!
You should be able to get very accurate ephemerides straight from the
Air Force (I don't have a link though). So correct, no need at all to
read out the navigation message. Should be able to do position fixes
with only ~1 or 2 ms of data (length of one chipping cycle).
But we can't run tracking loops across the data gap and get anything
useful, which is too bad. Still, I'm more interested in the exact
moment the acceleration goes from 0 to full burn vertical. Should be
really interesting to see what the tracking loops do at that moment.
To some degree the rest of the flight is boring ;p
-Nathan
On Mon, Dec 21, 2015 at 6:17 PM, Paul Breed <paul@xxxxxxxxxx> wrote:
yes it means data was lost....
However we have a starting GPS solution and exact times so we should be
able to use that to get orbital parameters
and a position solution with as little as 2msec of good data,......
On Mon, Dec 21, 2015 at 6:04 PM, Nathan Bergey <nathan.bergey@xxxxxxxxx>
wrote:
Great work! Thank you for posting the data, well be chewing on it here
at PSAS too.
from time to time it had a FPGA fifo error and the sampler would restart
Does that mean you lost data during the fallover to the next file?
-Nathan
PSAS
On Mon, Dec 21, 2015 at 9:42 AM, Monroe L. King Jr.
<monroe@xxxxxxxxxxxxxxxxxx> wrote:
Damn Paul don't know what to say about all that!
-------- Original Message --------
Subject: [AR] GPS saga...
From: Paul Breed <paul@xxxxxxxxxx>
Date: Mon, December 21, 2015 9:56 am
To: arocket@xxxxxxxxxxxxx
http://unreasonablerocket.blogspot.com/2015/12/flight-of-12-19-15.html