FlightJAS Editor

FlightJAS Editor is an extension to Visual Studio Code providing syntax and database linking to support parameter, command, and telemetry for MAX Flight Software.

STK SOLIS is drive by MAX Flight Software.

Installation

FlightJAS Editor is released and managed through the VS Extension Marketplace. After installation, an FJ icon will appear in the Activity Bar and all .fj files will be associated with the editor.

Use

• Click the FJ icon in the Activity Bar
• Click the Load Target Directory button, browse to a Target Directory of your choice
• Open any .fj files you'd like to edit and return to the FlightJAS Editor extension

FlightJAS Keywords

Like any other language, FlightJAS contains keywords to perform various actions. For a complete list of Keywords see FlightJAS Documentation.

• Start typing in any .fj file to get information and syntax for Keywords

Command Explorer

Command Explorer utilizes the command database to provide intelligence on commands that exist in the system (which can differ based on how the flight software is configured). Using this feature, you will find information about the command and automatic population of argument syntax.

To add a command to your .fj sequence:

• Type CMD
• Browse to the command in the Command Explorer and click the Insert icon
• Edit any necessary arguments

CMD "MDC_SLEW_TRACK" (SLEWTIME_S,SLEWMODE,TRACKMODE,CLOCKINGOPTION)

The example above will send the MDC_SLEW_TRACK command. It is the responsibility of the user to enter the four arguments.

Telemetry Explorer

Telemetry Explorer utilizes the telemetry database to provide intelligence on telemetry mnemonics that exist in the system (which can differ based on how the flight software is configured). Telemetry is often used to test if a condition is met before proceeding or to assign a variable to perform calculations.

CHECK(TM("MDC_ACMODE") == "SunTrack")

The example above gets the value of the MDC_ACMODE mnemonic and compares it against "SunTrack". The sequence will not proceed until this statement is true.

PROC MySeq
REAL alt_m
BEGIN

alt_m = TM("EPH_ALTITUDE")

The example above assigns a variable alt_m to the EPH_ALTITUDE mnemonic from telemetry. alt_m is declared as a variable prior to the BEGIN statement of the procedure.

Parameter Explorer

Parameter Explorer utilizes the parameter database to provide intelligence on components and parameters that exist in the system (which can differ based on how the flight software is configured). The Insert functionality from the Parameter Explorer inserts a MISC_CONFIG_PARSE statement, which can be used to change a parameter value.

CMD "MISC_CONFIG_PARSE" ("FSW_ActProc_MT_Magnetic_Torquers_Set.B_QuiescentIfMTOff = 1;")

The example above changes the B_QuiescientIfMTOff parameter in the FSW_ActProc_MT_Magnetic_Torquers_Set to 1 (True).

Target Directory

The term Target Directory refers to the directory containing the structure shown below. Each MAX instance is setup with this type of structure to contain it's Configuration Files, Parameter Database, Command Database, Telemetry Databases, and FlightJAS Sequences.

.
├── <Target Directory>
│   ├──cfg
│   |   └── <.cfg configuration files>
│   ├──cmd_tlm_db
│   |   ├── FswCmdMaster.csv
│   |   ├── FswCmdDetail.csv
│   |   ├── FswCmdEnum.csv
│   |   ├── FswTlmMaster.csv
│   |   ├── FswTlmDetail.csv
│   |   ├── FswTlmEnum.csv
│   |   └── FswParamDB.xml
│   └──seq
|       └── <.fj FlightJAS sequences>