Smart completion gives the Sequence editor context-aware suggestions for transition conditions and action operands.
Note: This is not AI and it is not a Python language-server feature. It is a deterministic, rule-based index built inside the AutomationView extension from your project's own data. It filters and ranks symbols that already exist in your project - it does not predict or generate code, and the suggestions do not come from the Python language server.
AutomationView builds an in-memory index of your project's own model: variables (with their types and properties), steps (per-sequence and global), and SFC operators. The index rebuilds when variables change, when a file is executed, or when resolved sequences change.
As you type in a transition-condition or action-operand field in the Sequence editor, it suggests entries from that index, matched and ranked by simple rules:
timer. lists that variable's properties)condition inputs, and operand suggestions right after a comparison or logical operatorEvery suggestion is a symbol that already exists in your project. Nothing is invented.
When writing transition conditions or action targets, AutomationView suggests matching variables from your IO configuration and local declarations. Variables are managed through the Variable Management feature.
Action condition and code are no longer typed as free text. You pick operand variables from autocomplete instead, so each operand references a real variable rather than a typed string.
Type a qualifier letter and see the full list with descriptions. AutomationView supports all standard IEC 61131-3 qualifiers:
See the Qualifiers Overview for detailed behavior of each qualifier.
Get suggestions for all supported PLC instructions:
When creating transitions, get suggestions for existing steps in the current Sequence or macro step context.
IEC 61131-3 time literals with the T# prefix are autocompleted when you start typing:
T#5s -> 5 seconds
T#100ms -> 100 milliseconds
T#1m30s -> 1 minute 30 seconds
T#2h -> 2 hours
Action duration and preset values accept a variable operand (a reference to a numeric variable) as well as a literal. Use a literal such as T#5s, or pick a numeric variable from autocomplete to drive the duration from a variable.
Completion is fast because cached results are shown immediately and refreshed in the background.
If completions do not appear, make sure your file is saved and that your project has been properly loaded. AutomationView needs a valid project structure to provide suggestions.