Turn an AutomationView project into deployable PLC code in five stages: declare variables, bind hardware channels, validate addresses, configure export targets, and export the project.
| Stage | Goal | Where / Command |
|---|---|---|
| 1. Declare | Create or auto-discover project variables | Machine Editor Variables tab or Sequence Editor |
| 2. Link | Bind variables to hardware module channels | Machine Editor Architecture tab |
| 3. Address | Assign and validate %I and %Q addresses |
Assign Addresses Automatically / Validate All Addresses |
| 4. Translate | Preview generated PLC source code | Translate to Target Language |
| 5. Export | Export deployable project files | Export Project (automationview/export/<target>/) |
Create and manage variables using any of these workflows:
main.machine and select the Variables tab..seq files.main.machine.| Category | Typical Use |
|---|---|
Input (%I) |
Sensors, push-buttons, limit switches |
Output (%Q) |
Solenoid valves, motor contactors, indicator lamps |
| Local | Internal flags, timers (TON), counters (CTU), custom STRUCT / ENUM instances |
Bind logical variables to physical hardware channels in the Machine Editor:
main.machine and select the Architecture tab.profinet, ethercat, ethernet-ip, io-link, modbus-tcp, modbus-rtu, canopen, profibus, as-interface, or opc-ua).%I / %Q address based on channel direction, bit width, and offset.%I and %Q addresses to unassigned channels and opens the Architecture tab.| Variable | Direction | Computed Address |
|---|---|---|
S_HOME |
Input | %IX0.0 |
S_OUT |
Input | %IX0.1 |
Y_EXTEND |
Output | %QX1.0 |
Y_RETRACT |
Output | %QX1.1 |
Run AutomationView: Validate All Addresses to check for duplicate hardware addresses or unassigned channels before exporting.
main.machine and select the Project tab..seq file and click the Translate icon in the editor title bar (or run AutomationView: Translate to Target Language).Run the project export from the Machine Explorer title bar or the Command Palette:
| Goal | Command |
|---|---|
| Export complete project bundle | AutomationView: Export Project |
| Export all sequences as source files | AutomationView: Export All Sequences |
| Export sequence diagram as PDF | AutomationView: Export PDF |
Exported files are written to automationview/export/<target>/:
project-root/
automationview/
main.machine
sequences/
main.seq
export/
codesys/
project.xml
siemens/
main.scl
| Setting | Default | Description |
|---|---|---|
automationview.export.includeComments |
true |
Include step, transition, and action comments in generated code |
automationview.export.commentLanguage |
en |
Comment language (en, fr, de, es, pt) |
automationview.export.autoExport |
false |
Automatically export the project when any .seq changes |
automationview.export.autoExportDebounceMs |
2000 |
Delay in ms before auto-export runs |
automationview.export.autoExportOnSave |
false |
Export modified sequences on every save |
| Target IDE | Import Procedure |
|---|---|
| CODESYS V3 | Right-click the Application node -> Add Object > Import PLCopenXML -> select the exported .xml file |
| Siemens TIA Portal | Import the generated .scl source or Openness .xml blocks into Program blocks |
| Rockwell Studio 5000 | Click File > Import Component / Routine and select the exported .L5X file |
main.machine.yaml scenarios