AutomationView translates .seq Sequences into the native source format your downstream programming tool expects - CODESYS ST, Siemens SCL, Rockwell ST or Ladder, and Fanuc TP - and can export full projects to deployable files such as CODESYS PLCopen XML, Rockwell L5X, and Siemens Openness XML.
Each translation provider ships as a separate extension. Providers register at startup and become available targets in the Translate to Target Language command. The official plugins:
| Plugin | Translation target | Source format |
|---|---|---|
| AutomationView - CODESYS | CODESYS V3 | Structured Text (.codesys-st) |
| AutomationView - Siemens | TIA Portal (S7-1200, S7-1500) | SCL (.siemens-scl) |
| AutomationView - Rockwell | Studio 5000 (ControlLogix, CompactLogix) | Structured Text (.rockwell-st), Ladder / RLL (.rockwell-ladder) |
| AutomationView - Fanuc | Fanuc robot controllers | TP language (.fanuc-tp) |
Translation produces vendor source text. Project export (covered below) produces deployable files such as CODESYS PLCopen XML, Rockwell L5X, and Siemens Openness XML. See the PLC Target Matrix for the full split between translation and export.
With a .seq file open, run AutomationView: Translate to Target Language from the Command Palette, or click the Translate icon that appears in the editor title bar for .seq files. If more than one provider is installed, you are prompted to pick a target.
The Translate command only appears once at least one translation provider is installed. Install a provider extension from the marketplace to enable it.
Two export settings shape the generated source text regardless of target:
| Setting | Default | Effect |
|---|---|---|
automationview.export.includeComments |
true |
Include step and transition comments in the generated code |
automationview.export.language |
en |
Language of generated comments - en, fr, de, es, pt |
export.language is separate from the editor interface language. See the Export Settings reference for the full list.
Live translation re-translates the active Sequence as you work, so the generated source stays in step with the diagram. Start it from the Translate flow, then run AutomationView: Stop Live Translation to end the session.
Two flavours, both available from the Machine Explorer title bar or the Command Palette:
.seq under the project to the configured default format, one output file per Sequence.Trigger bulk export automatically on file changes:
| Setting | Default | Description |
|---|---|---|
automationview.export.autoExport |
false |
Auto-export the full project whenever any .seq changes |
automationview.export.autoExportDebounceMs |
2000 |
Delay (ms) before auto-export fires |
automationview.export.autoExportOnSave |
false |
Export every Sequence on save (lighter, per-file) |
autoExportOnSave is the cheaper option for CI-style workflows where every save should produce an artefact.
Exports land in an out/ folder at the project root, one file per source Sequence:
project-root/
sequences/
fill_station.seq
empty_station.seq
out/
fill_station.xml
empty_station.xml
The file extension depends on the provider: CODESYS export writes .xml (PLCopen), Siemens writes .xml (Openness) or .scl, Rockwell writes .L5X. Translation output uses the provider's source extension (for example .codesys-st, .siemens-scl, .fanuc-tp).
When translation fails, AutomationView shows a notification and writes details to the Output panel under the AutomationView Translation channel. The usual suspects:
| Diagnostic | Meaning | Fix |
|---|---|---|
| Missing instruction support | The target vendor does not implement an instruction used in your Sequence | Replace the instruction or pick another target |
| Scope mismatch | A variable is referenced in a scope the target cannot map | Promote the variable - see Variable Scope |
| Unknown equipment | A channel references an equipment ID not registered in any provider | Install the missing equipment provider or re-bind the channel |
| Address conflict | Two variables resolve to the same physical address | Run AutomationView: Validate All Addresses |
| No translation provider | No provider installed for the requested target | Install the matching provider extension |
Re-run translation after fixing the issue. Watch mode resumes on the next save.