Shift Notes

[tanishqaggarwal]

Here's a place to place records of notable spacecraft activity (and potentially our overall response strategy) towards them.

[tanishqaggarwal]

Shift: Jan 17 Night

Rotator: Tanishq Aggarwal

Spacecraft Activity:

• Eclipse (zero cursun) and low battery (~6600 mV)
• Eventually bounced back to 7100 mV
• Got bootcause: 2 (I2C WDT reset) at about 2:30 AM EST 1/18

Commanding

• Reduce radio wait cycles and transceive cycles (PowerSave3)

Concerns:

• Continue to watch behavior of PowerSave3 on spacecraft
• Is bootcount rate correlated with Gomspace voltage? Need to check what we designated as crit power threshold on flight units

[fatimayousuf]

Shift: January 18 Morning

Rotator: Fatima Yousuf

Spacecraft Activity:

• Battery voltage oscillating between 6700 and 7100
• No change in boot count rate
• Got another downlink from follower

Commanding

• Sent PowerSave3 to leader again

[shihaocao]

Shift: Jan 18 Evening

Rotator: Shihao Cao

Spacecraft Activity:

Nothing new. Leader has had no comms for the last 8 hours. The previous longest recorded gap is 12 hours.

Concerns:

Continue to watch the behavior of PowerSave3. It's looking pretty good for the spacecraft, but lets confirm through testing.
Since we have on call right now, let's continue to not have more than one command in the queue at a time. Requeue PowerSave3 whenever we get confirmation it's doing ok. Otherwise, discuss in #mission-ops

[stewartaslan]

Shift: Jan 18/19 Night

Rotator: Stewart Aslan

Spacecraft Activity:

• Received one downlink from Leader at 6:56pm pacific time. Battery voltage of 6.695V is close to the lowest ever measured, which was 6.685V on Jan 18.
• A PowerSave3 command was in the queue at that time, so that command should have been applied to the spacecraft.
• Queued up another PowerSave3 command.
• Queued a second PowerSave3 command to account for the three hour gap in coverage 1-4am pacific time. There are two commands in the queue at the end of this shift.

Concerns:

• Battery voltage is low
• Searched for a really long time through google drive, github, my laptop, my brain.... can't find what the gomspace i2c wdt timeout is set to. Having this info would be very helpful for diagnosing reboots.

[govindchari]

Shift: Jan 19 Morning

Rotator: Govind Chari

Spacecraft Activity:

• Received two downlinks from Leader in the span of one hour. One at 9:00 am EST and one at 9:53am EST

• Battery voltage went up from yesterday's all time low of 6.685V to 6.995V

• Queued PowerSaving3

[shihaocao]

Shift: Jan 19 Noon

Rotator: Shihao Cao

Spacecraft Activity:

Voltage restabilizing, back up to 7.0V

Queued PowerSaving3 with Claudia

[stewartaslan]

Shift: Jan 19/20 Night

Rotator: Stewart Aslan

Spacecraft Activity:

• Received 5 downlinks from Leader (MOMSN 51-55), two sets of which were on the same boot
• Two bootcause data points both have a value of 2 (I2C WDT reset), confirming that this is the cause of frequent reboots
• Queued five PowerSave3 commands (MTMSN 27-31), two commands in the queue at end of shift to account for three hour gap in shift coverage.
• Based on the ignore_sun_vectors flag and GOMSpace bootcause telemetry, MTMSN 26 and 27 were received, however ignore_sun_vectors did not flip from true to false in MOMSN 55, indicating that MTMSN 28 was not received or not applied. Worth keeping an eye on this for future commands.

Concerns:

• Battery voltage appears to be in a somewhat stable oscillation between approximately 6750mV and 7050mV, which is quite low
• Battery temperature is definitely trending downwards and is not clearly stabilizing, however the GOMSpace datasheet indicates an operating temperature range of -40C to 85C, so we should be ok for a while.
• Not all commands are being received, we should make sure to keep track of which commands are received and be diligent about switching the ignore_sun_vectors flag.

[govindchari]

Shift: Jan 20 Morning

Rotator: Govind Chari

Spacecraft Activity:
Have not received a downlink in 11 hours

[fatimayousuf]

Shift: Jan 20 Afternoon/Evening

Rotator: Fatima Yousuf

Spacecraft Activity:

• Received three downlinks from leader, none from follower
• Sent an uplink to leader that shifted flow 36 to 2nd in the flow order so that we can get data on gomspace.wdt_i2c_time_left (MTMSN 32)

[kylekrol]

Shift: Jan 20/21 Night

Rotator: Kyle

Spacecraft Activity:

• Received just one message from the leader and continued queueing the power saving commands (MTMSN 33) in addition to the flow changes Fatima implemented above. Not much else to note.
• Batter reported to be at 7.06 V for the leader.

[samuelqian01]

Shift: Jan 21 Morning

Rotator: Samuel Qian

Spacecraft Activity:

• Received three downlinks (7:28 AM, 9:59 AM, 10:31 AM)
• Queued PowerSaving3 with Shihao
• Battery voltage dropped from 7.180V to 6.785V after briefly fluctuating between ~7 AM est to ~10 AM est

[jer296]

Shift: Jan 21-22 Night

Rotator: Josh

Spacecraft Activity:

• Received one downlink from Follower 10:06PM EST 01/21
• Follower battery voltage reported as 6.720V
• Queued PowerSaving3 with ~24-hour max_wait_time (500k)
• Received one downlink from Leader 12:59AM EST 01/22
• Leader battery voltage reported as 7.015V
• Queued PowerSaving3 with nominal max_wait_time

[afoarce]

Shift: Jan 21 Afternoon

Rotator: Andreea

Spacecraft Activity:

• Received two downlinks from Leader (2:12PM, 6:47PM)
• Battery voltage fairly stable, went from 6.785 to 6.780
• Queued PowerSaving3 each time with flow reordering

[millie-schwartz]

Shift: 21-22 night (thru 1 am, finished by tanishq)

Rotator: Millie

Spacecraft Activity:

• Received 3 packets from Follower and 1 from leader between 10:50-11:20
• Follower vbatt decreased from previous packet, once again faulted
• Queued PS3 for both with ignore_sun_vectors flipped from previous uplink for both

[tanishqaggarwal]

Shift: Jan 22, 1 AM - 4 AM EST

Rotator: Tanishq Aggarwal

Spacecraft Activity:

• No telemetry in these three hours.

Commanding:

• Powersave3 re-queued for leader as a wakeup contingency.