Script

Quote from mm_dev on 24/04/2023, 15:48

The Script block is a powerful tool to add customized control, measurement and data analysis functionality to the RTSA-Suite PRO:

Left hand side Input:

• Input 1 (customizable)
• Input 2 (customizable)
• Input 3 (customizable)
• Input 4 (customizable)

Right hand side Output:

• Output 1 (customizable)
• Output 2 (customizable)
• Output 3 (customizable)
• Output 4 (customizable)

Note: Up to 16 additional inputs or outputs can be created at runtime.

The Script block is a powerful tool to add customized control, measurement and data analysis functionality to the RTSA-Suite PRO. This can be done by writing program code using the JSIQA scripting language, a customized JavaScript variant. Please see the JavaScript Support section for more details about the language and its functions.

Besides the editor window for entering the code, the Script block also provides various controls to adjust its appearance and the execution environment:

In the Interpreter menu you can find the controls for control the code execution, memory settings and debugging. When enabling the "Auto Start" option, the block will start executing its code as soon as it is loaded from a mission or after code changes. This should be enabled when shipping a Script block into production, but disabled during development and testing. "Cleanup Memory" will reset the internal memory, this can be used to remove graphics and outputs from the last code run.

The Block Config contains options to adjust the appearance of the Script block. In particular you can disable, rename and change the datatype of the predefined inputs and outputs to match the function the customized block will perform. Here it is also possible to enable/disable the editor and console (for production use) and disable access to the configuration of the block completely (except for options defined by the code itself). Note: The "Hide Script Config" option is also available in the hamburger menu of the standard Block configuration menu.

The Script Config section acts as container for configuration options added by Mission.addConfig(), though usually all relevant settings should also be mapped into the Main section using Mission.mapConfig().

Finally, when using predefined DSP processing blocks with configuration settings, those are made available in the Script Block Config.