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
Currently, it is assumed that each thruster can provide a maximum thrust of 0.25 N. This is inaccurate, because the amount of thrust out of each thruster is also a function of which thrusters are being used.
The text was updated successfully, but these errors were encountered:
- Resolved Issue Carleton-SRCL#8, reordered the build warning so that the diagram is in "Build" mode before the warning comes up.
- Resolved Issue Carleton-SRCL#11: Reworked the Ping tool to use a different mechanism. This should dramatically reduce the timeout when an IP address can't be pinged. Needs to be tested in-lab.
- Resolved Issue Carleton-SRCL#12: Changed the integrator for both the dynamics models as well as the the integration of the platform attitude from the IMU.
I have written code to accomplish this task for RED and it seems to be pretty decent - but it requires knowing the CG, mass, and inertia of the platforms at the time the data is collected. I will write an entry about it soon.
Currently, it is assumed that each thruster can provide a maximum thrust of 0.25 N. This is inaccurate, because the amount of thrust out of each thruster is also a function of which thrusters are being used.
The text was updated successfully, but these errors were encountered: