Skip to content
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

MCB TC Q's #10

Open
MisterMartin opened this issue Dec 20, 2024 · 1 comment
Open

MCB TC Q's #10

MisterMartin opened this issue Dec 20, 2024 · 1 comment
Assignees
Labels
question Further information is requested

Comments

@MisterMartin
Copy link
Contributor

MisterMartin commented Dec 20, 2024

  • Why are there so many TCs that the MCB can respond to, for currents, voltages, temps, etc., that RACHUTS does not use? Are they there just for the debug serial interface?

Lars thinks that they just get passed through to the ground.

  • MCB has TCs for velocity and acceleration parameters. Will we use these?

Velocity is stored on the EEPROM of the MCB. Needs to be set once, 10 for RATS. 250 for RACHUTS.

  • The RATS state diagram specifies deploy/retract in terms of revolutions, but the MCB TC uses length. (DEPLOYx. Should really be DEPLOYz :-)

  • Take a look at TCs in telecommand.h, and cherry pick the ones for RATS.

Ok.

@MisterMartin MisterMartin added the question Further information is requested label Dec 20, 2024
@MisterMartin MisterMartin self-assigned this Dec 20, 2024
@MisterMartin
Copy link
Contributor Author

Incidentally, I added one for GETMCBVOLTS. Since there hadn't seemed to be a need for these in the past, we may want to remove it.

@MisterMartin MisterMartin changed the title Unused MCB TCs MCB TC Q's Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant