I've done my usual IBEX-Hi processing and I found no issues -- if you hadn't told me the s/c clock had reset, I wouldn't have noticed.

The CEU clock is still plugging away on its own slightly drifty MET, and it's tagged all the payload packet times correctly.  I do check for invalid times and time jumps in the CEU clock in my processing.  It would be very unusual for the CEU to report a time circa 1970 inasmuch as its Epoch is GPS time and AFAIK it represents time as a uint32_t and so cannot report times prior to 1980.  1970 is Unix Epoch.  Anyhow, it doesn't look like the s/c clock told the CEU to reset its time.

I'll send out my usual status report later today.  I note star tracker lost tracking circa morning of Aug 20.


Paul Janzen.
From: Isocops <isocops-bounces@lists.sr.unh.edu> on behalf of NIgel Angold <nangold@princeton.edu>
Sent: August 27, 2021 9:21 AM
To: Perry, Timothy E [US] (SP) <Timothy.Perry@ngc.com>
Cc: Chubin, Eric [US] (SP) <Eric.Chubin@ngc.com>; Ken Fairchild (kwfairchild@gmail.com) <kwfairchild@gmail.com>; Eric Christian <eric.r.christian@nasa.gov>; Bobbett, James E [US] (SP) <James.Bobbett@ngc.com>; ISOC at New Hampshire <isocops@lists.sr.unh.edu>; Leonard, Benjamin Y [US] (SP) <Benjamin.Leonard@ngc.com>; Ken Fairchild UNH (Ken.Fairchild@unh.edu) <Ken.Fairchild@unh.edu>; Fleming, Ed [US] (SP) <Ed.Fleming@ngc.com>; Wesley, Sheral R [US] (SP) <Sheral.Wesley@ngc.com>; Tyler, Ryan S [US] (SP) <Ryan.Tyler@ngc.com>; Ibex Mission Operations <ibexops@gmail.com>; Dave McComas <dmccomas@princeton.edu>; Cavallo, John A [US] (SP) <John.Cavallo@ngc.com>; Wynn, Reese [US] (SP) <Reese.Wynn@ngc.com>; Bret Hautamaki <bhautama@gmail.com>; IBEX FDG Group (ADS-IBEX@l3harris.com) <ADS-IBEX@l3harris.com>
Subject: [Isocops] IBEX Spacecraft Clock Issue FRB Notes
 
Attendees:
Reese Wynn, Carol Weaver, Tim Perry, Sheral Wesley, Eric Chubin, Nigel Angold, Harald Kucharek, Ryan Tyler, Jim Conway, Eric Christian, Ken Fairchild, Ben Leonard

SOC processing looks ok !!! Where does the time data come from? Ken will dig deeper into processing code - looks like there's a different time stamp around the time of the problem, but somehow the code copes with it.
Ryan: 1970 value looks like the ground doesn't know how to interpret the data it's receiving.
Tim: valid time stamps until August 24 at ~07:50 UTC.

There's no urgency to load the orbit 540 ATS: there are 2 more scheduled uplink opportunities before the commands onboard run out on 5 September.
The Master Reset Timer was reset last night.
We'll upload a test no-op time-tagged command.
We'll try to set the spacecraft clock.

Running order for activities during next contact

Party line will be up about 30 minutes before BOT. 888-330-1716 # 4895952

We'll use MAESTRO2.

Post-pass Zoom at 1:30 pm EDT. Details below.

Future planning - TBD

--------

Nigel Angold is inviting you to a scheduled Zoom meeting.

Topic: IBEX Spacecraft Clock Post-Contact Tag-up
Time: Aug 27, 2021 01:30 PM Eastern Time (US and Canada)

Join Zoom Meeting
https://princeton.zoom.us/j/92545810618

Meeting ID: 925 4581 0618
One tap mobile
+16699006833,,92545810618# US (San Jose)
+12532158782,,92545810618# US (Tacoma)

Dial by your location
        +1 669 900 6833 US (San Jose)
        +1 253 215 8782 US (Tacoma)
        +1 346 248 7799 US (Houston)
        +1 646 558 8656 US (New York)
        +1 301 715 8592 US (Washington DC)
        +1 312 626 6799 US (Chicago)
        877 853 5247 US Toll-free
        888 788 0099 US Toll-free
Meeting ID: 925 4581 0618
Find your local number: https://princeton.zoom.us/u/acdQ7sUci8

Join by SIP
92545810618@zoomcrc.com

Join by H.323
162.255.37.11 (US West)
162.255.36.11 (US East)
115.114.131.7 (India Mumbai)
115.114.115.7 (India Hyderabad)
213.19.144.110 (Amsterdam Netherlands)
213.244.140.110 (Germany)
103.122.166.55 (Australia Sydney)
103.122.167.55 (Australia Melbourne)
64.211.144.160 (Brazil)
69.174.57.160 (Canada Toronto)
65.39.152.160 (Canada Vancouver)
207.226.132.110 (Japan Tokyo)
149.137.24.110 (Japan Osaka)
Meeting ID: 925 4581 0618