ADCS: extract and log magnetometer data

[parker-research]

@JohnathanBurchill requested, as potentially beneficial to science mission

Waiting on ADCS Drivers in #13

[DeemDeem52]

Getting magnetometer values is something I can do at the driver level for the ADCS; indeed, I think that's one of the functions I'm implementing anyway! I'll get back to you with more details.

[DeemDeem52]

Okay! Looking through the firmware reference manual and code, there are a few commands which will be relevant here:

Implemented in the branch based on commissioning manual:

• Deploy Magnetometer
• Set Mode of Magnetometer Operation
• Set/Get Magnetometer Configuration
• Set/Get Estimation Parameters (magnetometer noise, etc)
• Get Raw Magnetometer Values

Unimplemented (not required by commissioning manual):

• Secondary Magnetometer Raw Measurements
• ADCS Temperatures (temperature of magnetometer)
• Redundant Magnetometer Configuration
• Current ADCS State (whether there's been an error)

@JohnathanBurchill Which of these do you think would be most helpful?

[JohnathanBurchill]

@JohnathanBurchill Which of these do you think would be most helpful?

All the implemented functions look useful. The raw mag values would be what I was thinking of. All the unimplemented stuff would be useful too, particularly ADCS state and secondary mag raw measurements.

Does the ADCS documentation specify the measurement resolution / accuracy / precision of the magnetometer?

What might make sense is to have a housekeeping_data() telecommand which would download a log or binary file of the ADCS, GPS, etc. measurements recorded during the MPI operation.

[DeflateAwning]

@DeemDeem52, which function(s) in your ADCS branch solve this issue? I'm sure they're there; just want to make sure they're explicitly denoted as such.

[DeemDeem52]

@DeemDeem52, which function(s) in your ADCS branch solve this issue? I'm sure they're there; just want to make sure they're explicitly denoted as such.

I wrote in my above comment the five functionalities which are explicitly implemented as telecommands; the other ones which I mentioned are not implemented in my pull request -- however, the generic telecommand and telemetry functions should allow use to use those functionalities anyways.

I suppose that means that we can either:

• close the issue when the PR is merged,
• keep the issue open and merge the PR,
• implement the rest of the functions explicitly (should be pretty easy) and then merge the PR.

As for Dr. Burchill's suggestion of a housekeeping_data command... that might be a bit trickier to implement using the telecommand structure since we only receive data from the ADCS when we explicitly ask for it. I think that would be something to work on separately from the existing PR.

[DeflateAwning]

Thanks, I missed those messages above. I think what I've gathered is that the really useful command/function is probably ADCS_Get_Raw_Magnetometer_Values.

A "log unified GPS/ADCS data useful for MPI data collection" command/periodic action (proposed as housekeeping_data() above) will be easy enough to implement; it will simply query the GPS and ADCS several times each with different commands as necessary, keep only the info we want for the mission (to save space), and then log it (probably as JSON). We will save that implementation for another issue though.

I think this issue is "fixed" by PR #151, because that PR implements the ADCS_Get_Raw_Magnetometer_Values function.