SAS control modified for probe use instead of main vessel use.Scripts for de-orbit maneuver and re-entry procedures.New spacecraft commands for science and battery operation.This is useful for when a spacecraft changes configuration, such as decoupling a segment that included parts that were being accessed for data to be logged New utility function removeAddlLogData that can be used to delete a key from the lexicon or even all the keys if not passed a key.Companion to the already-existing pointingAt function that looks at a similar value but makes a determination and returns T/F instead of the value New helper function pointingFrom that will return the raw value of the difference between the current steering angle and the passed target angle.Removed getCommStatus() as it is not possible in general to determine whether a comm antenna is off or on (unless it can be deployed/retracted).Fixed issue that would not properly retract antenna when entering hibernation.This lets the control system properly deploy/retract any antennas that are specified through setCommStatus() Now the whole part is saved not just the transmitter module. Internal change to how communication parts are stored.Updated several system references to be compatible as this code was last used in mid-2019.Ascent profile no longer includes a coast between first and second stages.Radiation belt detection routine can now handle possible scenario where rocket does not reach high enough to enter the outer belt.Changed hibernation time back to 60s from 30s.Replaced specific staging instructions with stage command to allow for better fuel use tracking.You can now pass an optional second parameter to pointingAt() if you don't want to use the default angle of within 2° to decide if true or false is returned.Better detection of engine malfunctions.Ascent abort code expanded to allow for return of entire second stage if needed.Additional logging added for radiation and target pitch. ![]() Fixed improper chute deployment handling in deorbit code.Ascent code modified to use internal staging.Based largely off the operational files of the last Mk2 mission.Past commits include the operational code for previous missions as well. ![]() Have a look in the Operations folder for mission examples to get a better idea of how the AFCS and its accompanying libraries can be used for anything from sub-orbital to orbital to kerbed and unkerbed missions. Here is a flowchart for how the vessel operates under the AFCS (slightly outdated - backup ops refers to any ops stored on the vessel): It will continuously run fuctions that are stored in its operation queue which allows for the spacecraft to perform many parallel functions while keeping these operations encapsulated in code and easy to read and maintain, allowing for operations to be ported to other vessels in bits and pieces to share code. It simply creates the environment for the spacecraft to operate from and still needs mission-specific scripts for the spacecraft to carry out its objectives. Operational Frameworkīy itself, the AFCS does nothing. Video demonstrations of the command uplink can be found in this twitter thread that also gives some details of the commands that can be used. BAT is run when using the AFCS and changes the name of the command file to include the name of the vessel so that the AFCS sees it on the Archive and grabs it for parsing
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |