[Isocops] [Ibexops] Orbit 598 Contact Statuses

NIgel Angold nangold at princeton.edu
Fri Feb 24 09:38:51 EST 2023


If we perform a successful Firecode Reset but the spacecraft does not 
accept other commands, then the answer to your question is unknown. The 
Tx would  be off and the Master Reset Timer would most likely be reset 
so we'd be back to waiting for ~18 days for a Master Reset to occur, but 
this time in the blind. We could possibly do additional Firecode Resets 
before then but maybe with the same result. At this point, I would be 
hoping that the problem was a thermal one and that letting the 
transponder cool down with the Tx of would fix the problem.

I hope to prepare a slide or two discussing the possible plans for each 
potential outcome for this afternoon's telecon.

Thanks,
Nigel
> kayton.lane at L3Harris.com <mailto:kayton.lane at L3Harris.com>
> February 24, 2023 at 09:25
>
> Hi Nigel,
>
> In the instance of the fire code reset, how long would we be going 
> without tracking data from the downlink?
>
> As far as planning for additional tracking data, any and all extra 
> passes that you could schedule before that occurs would be helpful, as 
> close to the time of the reset as possible.
>
> Thanks,
>
> Kayton
>
> *Kayton Lane*
>
> *Astrodynamics Engineer*
>
> *Space & airborne systems / L3HARRIS TECHNOLOGIES*
>
> w +1 321 729 1809**
>
> m +1 218 431 0586
>
> L3Harris.com / _Kayton.Lane at L3Harris.com 
> <mailto:Kayton.Lane at L3Harris.com>_
>
> Palm Bay, FL 32905 / USA
>
> *From:*NIgel Angold <nangold at princeton.edu>
> *Sent:* Thursday, February 23, 2023 8:45 PM
> *To:* Lane, Kayton (US) - SS <kayton.lane at L3Harris.com>
> *Cc:* angoldconsulting at earthlink.net; ibexops at lists.sr.unh.edu; 
> kwfairchild at gmail.com; don.gittle at sscspace.com; dhobel at uspacenet.com; 
> Sheral.Wesley at ngc.com; Timothy.Perry at ngc.com; Reese.Wynn at ngc.com; 
> Looney, Caeley (US) - SS <Caeley.Looney at L3Harris.com>; Byrd, Reneisha 
> (US) - SS <Reneisha.Byrd at L3Harris.com>; Dykes, Andy (US) - SS 
> <Andy.Dykes at L3Harris.com>; Dave McComas <dmccomas at princeton.edu>; 
> Scott Weidner <sweidner at princeton.edu>; Carol Weaver 
> <carol.weaver at unh.edu>
> *Subject:* [EXTERNAL] Re: Orbit 598 Contact Statuses
>
> *WARNING: *Email originated from an *EXTERNAL* source. Do NOT click 
> links, open attachments or reply unless you recognize sender and know 
> the content is safe.
>
> Thanks Kayton.
>
> So the tracking data post-anomaly looks good too. That's excellent 
> news. I'm pretty sure that means the downlink is coherent. Let me know 
> if you or others at L3Harris disagree.
>
> Also, Tim took a successful test pass with AK today to validate the 
> fixes that SSC made. So he scheduled two contacts for tomorrow 
> (Friday) morning and hopefully we can get good tracking data from them 
> too. We've shifted the HI01 apogee contact on Monday 27 Feb later 
> because it conflicted with the time slot earmarked for the follow-up 
> ARB (10:00 am eastern). Again, we hope it will provide more good 
> tracking data.
>
> Before the next perigee and potential Master Reset due to the 18 day 
> command loss timer on 4 March, if we decide to perform a Firecode 
> Reset that could result in no downlink for a while, would ~30 minutes 
> of tracking data before the reset be helpful in providing an orbit 
> determination that's as up to date as possible before losing visibility?
>
> Nigel
>
> NIgel Angold <mailto:nangold at princeton.edu>
> February 23, 2023 at 20:44
> Thanks Kayton.
>
> So the tracking data post-anomaly looks good too. That's excellent 
> news. I'm pretty sure that means the downlink is coherent. Let me know 
> if you or others at L3Harris disagree.
>
> Also, Tim took a successful test pass with AK today to validate the 
> fixes that SSC made. So he scheduled two contacts for tomorrow 
> (Friday) morning and hopefully we can get good tracking data from them 
> too.We've shifted the HI01 apogee contact on Monday 27 Feb later 
> because it conflicted with the time slot earmarked for the follow-up 
> ARB (10:00 am eastern). Again, we hope it will provide more good 
> tracking data.
>
> Before the next perigee and potential Master Reset due to the 18 day 
> command loss timer on 4 March, if we decide to perform a Firecode 
> Reset that could result in no downlink for a while, would ~30 minutes 
> of tracking data before the reset be helpful in providing an orbit 
> determination that's as up to date as possible before losing visibility?
>
> Nigel
>
> kayton.lane at L3Harris.com <mailto:kayton.lane at L3Harris.com>
> February 23, 2023 at 16:45
>
> Hello everyone,
>
> Below are the statuses for the o598 primary contacts.
> DOY 049 15:00 UTC contact w/ USHI-02 (apogee): Pass for Doppler
>
> DOY 049 18:00 UTC contact w/ USHI-02 (Recovery Contact): Pass for Doppler
>
> DOY 050 20:20 UTC contact w/ USHI-01 (Recovery Contact): Pass for Doppler
>
> DOY 052 19:00 UTC contact w/ USHI-02 (Recovery Contact): Pass for Doppler
>
> DOY 052 21:25 UTC contact w/ AUWA-01 (Recovery Contact): Pass for Doppler
> DOY 054 02:00 UTC contact w/ USHI-01 (P/D): Pass for Doppler
> DOY 054 11:00 UTC contact w/  USHI-02 (P/A): Pass for Doppler
>
> Thanks,
> Kayton Lane
> IBEX FDG
>
>
>
> CONFIDENTIALITY NOTICE: This email and any attachments are for the 
> sole use of the intended recipient and may contain material that is 
> proprietary, confidential, privileged or otherwise legally protected 
> or restricted under applicable government laws. Any review, 
> disclosure, distributing or other use without expressed permission of 
> the sender is strictly prohibited. If you are not the intended 
> recipient, please contact the sender and delete all copies without 
> reading, printing, or saving.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.sr.unh.edu/pipermail/isocops/attachments/20230224/97374482/attachment-0001.htm>
-------------- next part --------------
Please restrict discussions on this email list to non-ITAR sensitive topics.
_______________________________________________
Ibexops mailing list
Ibexops at lists.sr.unh.edu
https://lists.sr.unh.edu/mailman/listinfo/ibexops


More information about the Isocops mailing list