-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Leader Uplink Command Log #852
Comments
Leader MTMSN 1 Invalid, sent before mission by accident. |
MTMSN 12,13,14 pan state to manual downlink.toggle_id to 11, radio.max_wait to 10420 (approx 30 mins), havt_disable18 disables the gyro heaters. This is a power-saving measure. This also assumes i2c comms with the ADCS is working. Noteworthy, if we see the havt disable later report heater as non functional, we know i2c is working with adcs. adcs.state to 1 to ensure ADCS stays passive. gomspace.piksi_off to turn off piksi as a power saving measure. It's not reliably reporting pos/vel anyway, and we don't need it during this checkout stage of the mission.
Queue'd 3 times at 2:59 AM ET on 01/17/2022. |
MTMSN 15 This is one more uplink of PowerSaving2 to the leader. The rational for each of the fields in this command remains the same as MTMSN 12,13, and 14. We are sending one more of these uplinks as we saw a promising increase in voltage in the most recent downlink and we want to see if the trend remains.
PowerSaving2 Queue'd 1 time at 7:56 PM ET on 1/17/2022 |
MTMSN 16
PowerSaving3 This introduces two new power-saving measures:
Modifications from PowerSaving2:
Queue'd 1 time at 11:37 PM ET on 1/17/2022 |
MTMSN 17 Keeping the ignore_sun_vectors flag the same, since it seems that it was not set to false by the previous uplink. This implies that the MTMSN number that Quake reports in its downlink emails is not indicative of the last message received by the spacecraft. Queued 1 time at 12:19 AM ET on 1/18/2022 |
MTMSN 18, 19, 20, 21 No apparent change in rate of bootcounts over time. Queued 1 time at 2:02 AM ET on 1/18/2022 |
MTMSN 22 The leader's vbatt has been oscillating between ~6700 and 7100. The boot count rate seems to have stayed the same Queued at 10:18 AM PST/1:18 EST on 1/18/2022 |
MTMSN 23
PowerSaving3 queued with |
MTMSN 24 PowerSaving3 queued at 11:30am EST on January 19th and set ignore sun vector to false |
MTMSN 26 PowerSaving3 queued at 3:10 EST on 01/19. Set ignore sun vector to |
MTMSN 27 PowerSaving3 queued 7:42pm pacific time, ignore sun vector to true. |
MTMSN 28 PowerSaving3 queued 8:51pm pacific time, ignore sun vector set to false |
MTMSN 29 PowerSaving3 queued at 9:36pm pacific time, ignore sun vector set to true |
MTMSN 30 PowerSaving3 queued at 12:01am pacific time, ignore sun vector set to false |
MTMSN 31 PowerSaving3 queued at 12:55am pacific time (two commands are now in the queue to account for the three hour gap in shift coverage), ignore sun vector set to false. This should have been true but was sent as false by accident, so we won't be able to tell from this flag whether this command has been applied. |
MTMSN 32 PowerSaving3 uplinked to leader at 8:34pm EST 1/20/22 with the following additions:
This would help us see what gomspace.wdt_i2c_time_left is. Because of this addition, I also dropped this part of PowerSaving3:
|
MTSN 33
|
MTMSN 34
Repeated same commands just to get the same PowerSaving3 and attempt to get the new telemetry points |
MTMSN 35, PowerSave3 with sun_vectors true
|
MTMSN 36, PowerSave3, sun_vectors false
|
MTMSN 37, PowerSave3, sun_vectors true
|
MTMSN 38, requed PowerSaving3 with sun_vectors false
|
MTMSN 39 sun_vectors true { |
MTMSN 40 ignore_sun_vectors false
|
Sent 12:34 ET on 01/23
PowerSaving3 + ADCS Power Cycle We keep the two radio commands of power saving 3, as we know we've seen 2nd frames with power saving 3 settings. Thus, let's continue. Keeping the gyro off is fine. We mainly want to see i2c reboot with ADCS, the gyro heater is not requisite for I2C functionality. Keeping adcs.state 1 is fine because it keeps its actuators disabled. Does not prevent I2C functionality. Keeping Piksi and DCDC's off is fine, not required for I2C, continued power saving. Flipping Sun vector ignore as usual. We stay in **We set |
Sent 08:13 ET on 01/24 PowerSaving3 + ADCS Power Cycle Rationale: Repeat the same PowerSavind3 + ADCS Power Cycle command in hopes of seeing established communications with the ADCS Computer. |
Sent 12:13 ET on 01/24 PowerSaving3 + ADCS Power Cycle Rationale: " " |
Sent 17:28 ET on 01/24 [ Rationale: No significant change in values, sent same PowerSaving3 + ADCS Power Cycle |
Sent 7:34 ET on 01/25 PowerSaving3 + ADCS Power Cycle Rationale: " " Sent 8:16 ET on 01/25 PowerSaving3 + ADCS Power Cycle Rationale: " " |
Sent 2:15 ET, 1/26 |
Sent 02:26 AM ET on 01/27 PowerSaving3 + ADCS Power Cycle Rationale: " " |
Some time on 02/01, changed to this default uplink:
PowerSaving3 + ADCS Power Cycle + Mag Debug Rationale: Moved flow 19 up in order to get more raw magnetometer measurements |
On 2/18,
The goal of this command was to force the satellite into Detumble, hence the The power saving commands from previous uplinks were removed in this more aggressive command in order to receive more downlinks. We noticed we were receiving more comms and even mag data without shifting flows. Since we believe ADCS may be functional, the power cycling command was also removed. |
On 04/17/2022 on Sunday at 12:04 PM ET, sent a command to do 100ms prop firing out of valve 1. |
On Thursday 04/21/22 at 3:25 PM sent another command for 500ms out of valve 1 |
On Friday 04/29/22 at 1:36 PM sent 3 commands for 900ms out of valve 1 (2700ms total) |
Goal:
Put every uplink sent to spacecraft as a new comment and post rationale for each packet sent.
The text was updated successfully, but these errors were encountered: