You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Lars thinks that they just get passed through to the ground.
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.
The text was updated successfully, but these errors were encountered: