🧠🧠🧠 ATTIQUB v0.0 - Unresolved outstanding features to build #1
Description
My own notes on current outstanding and unresolved problems with ATTIQUB
-
Body-frame intersatellite comms (ISC) antenna beam direction vector is currently hard-coded, since I just wanted to test if the ISC pointing scenario would work or not. Should have an option to specify the body frame orientation of the intersatellite comms antenna
-
Reaction wheel configuration currently only works if [RW] spin axis matrix is the identity [ 1 0 0 ; 0 1 0 ; 0 0 1 ]. In reality, the final control torque needs to be mapped to the reaction wheel envelope (i.e. 3D torque, but how do I distribute that torque to a set of 6 reaction wheels for example).
-
The current file structure is also confusing. For example, if the user opens attiqub.m and runs it, the program will be unable to find the current directory if the user selects "Adds to Path". This will not be a problem if the user selects the "Current Folder" though. Need to explore some MATLAB best practices to overcome this.
-
Attitude coordinates, frame definitions, control laws, and Lyapunov control theory needs to be introduced and properly documented. ATTIQUB will probably need a much more comprehensive documentation.
-
Custom attitude control mode needs to be accessible (in the case where NUS STAR wishes to use it, that would be the MPC algorithm).
-
Explore the possibility of including gravity gradient torque in the mechanics? Long shot. Not sure if I should do this...