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
I am wondering whether there is a bug in the BskSim scenario scenario_AttEclipse. I am attempting to simulate a CubeSat on a highly elliptical orbit with sun pointing and eclipses. I need to use thrusters and I tried to build the scenario based on scenario_AttEclipse, replacing reaction wheels with thrusters as an actuation method. I was unable to make the thrusters to work and I thought that this was because mrpFeedback module was not calculating control torque for the thrusters, since its output mrpFeedbackControl.cmdTorqueOutMsg was always flat zero.
But then I added debug prints to the original scenario_AttEclipse and I noticed that even there the control torque for the reaction wheels calculated by the rateServo module (rateServo.cmdTorqueOutMsg) is always zero, even though the reaction wheels clearly work as they are intended and the input torque rwMotorTorque.vehControlInMsg for rwMotorTorque module is not zero.
What is going on? Is it a bug or am I missing something in the execution flow? The basilisk documentation for scenario_AttEclipse seems to be out of date, because it says that flight software uses mrpFeedback module to calculate the control torque, but in the scenario code on 'sunSafePoint' mode mrpFeedback module is inactive and mrpSteering and rateServoFullNonlinear are used instead.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello everyone.
I am wondering whether there is a bug in the BskSim scenario scenario_AttEclipse. I am attempting to simulate a CubeSat on a highly elliptical orbit with sun pointing and eclipses. I need to use thrusters and I tried to build the scenario based on scenario_AttEclipse, replacing reaction wheels with thrusters as an actuation method. I was unable to make the thrusters to work and I thought that this was because mrpFeedback module was not calculating control torque for the thrusters, since its output mrpFeedbackControl.cmdTorqueOutMsg was always flat zero.
But then I added debug prints to the original scenario_AttEclipse and I noticed that even there the control torque for the reaction wheels calculated by the rateServo module (rateServo.cmdTorqueOutMsg) is always zero, even though the reaction wheels clearly work as they are intended and the input torque rwMotorTorque.vehControlInMsg for rwMotorTorque module is not zero.
What is going on? Is it a bug or am I missing something in the execution flow? The basilisk documentation for scenario_AttEclipse seems to be out of date, because it says that flight software uses mrpFeedback module to calculate the control torque, but in the scenario code on 'sunSafePoint' mode mrpFeedback module is inactive and mrpSteering and rateServoFullNonlinear are used instead.
Beta Was this translation helpful? Give feedback.
All reactions