Skip to content
This repository was archived by the owner on Nov 3, 2026. It is now read-only.
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion doc/source/command_intro.rst
Original file line number Diff line number Diff line change
Expand Up @@ -115,11 +115,16 @@ AIT supports relative time sequences that can be executed as ground sequences or

.. code-block:: text

%echo 'first'
1.5 NO_OP
%echo 'second'
5 NO_op
%echo 'third'
0.5 NO_OP

The above sequence will send a NO_OP command 1.5 seconds after invocation of the sequence, then wait 5 seconds and send another NO_OP command, and finally wait 0.5 second and send a final NO_OP command.
The above sequence will echo the number of each command in between every NO_OPT; a shell command can be added in the sequence by supplying `%` before it. It will send a NO_OP command 1.5 seconds after invocation of the sequence, then wait 5 seconds and send another NO_OP command, and finally wait 0.5 second and send a final NO_OP command.

**Security Note:** Users are responsible of restricting access of operational locations where these sequences live and whom can execute them. Users should thoroughly review sequences and the shell commands embedded in those sequences.

AIT Sequences can be used as ground sequences to automate common tasks during testing and operations or they can be encoded for upload to your payload. Ground sequences can be run via the Sequences component in the UI or via the CLI.

Expand Down
Loading