Open the editor as described in Quick start.
Editor controls
Section titled “Editor controls”| Control | What it does |
|---|---|
| Deploy | Compiles the program and loads it with fresh timers, counters and memory |
| Run / Stop | Starts cyclic scanning, or stops it. Stop keeps all values, so Run continues where it stopped |
| Step | Runs exactly one scan, useful while the simulation is paused |
| Reset | Resets timers, counters and memory to their start values |
| Status | stopped, running or error. Hover the status to read the error message. The scan time in ms is shown next to it |
| Insert signal | Opens a signal browser and inserts the chosen signal into the program (see Signals and variables) |
| Export / Import | Saves the program as a .st file, or loads one |
| Program list | In a model with several programs: every program in scan order with its state and scan time. Pick one to edit it |
The watch list below the code shows the current values of all signals the program uses and the outputs of its timers and counters, such as tDwell.Q or cycles.CV. Hover a name in the code to see its type, value and signal. Inline values and the watch list use the same read-only display: integer types in decimal, bit strings as width-padded hex (WORD 16#00A5) with a binary tooltip, REAL/LREAL with three decimal places, and TIME in seconds. Deployed AST declarations include every name in a, b : USINT;, regardless of line breaks or comments.
Saving and sharing
Section titled “Saving and sharing”Each program is stored in the model, on its PLC Program component. Changes are saved with the model and can be undone. If you cannot write to a project, such as the public demo, use Export to save a .st file. Use Import to load it again later.
A program whose Active field is set starts automatically when the model loads, in every workspace. With Active off, the program only loads into the editor; click Deploy and Run to start it. Programs run in an isolated sandbox inside the browser and can only read and write signals.