Code importers
Every PLC and DCS export BooleX reads, the HMI and electrical exports, and the common code model.
Each vendor's export is translated into one common code model: programs and blocks, rungs, networks and lines, tags, alarms, interlocks and their cause chains, with sequential function charts kept as steps and transitions. The assistant only ever reads this model, so the same question gets the same cause whichever vendor's code is behind it. Each element is cited as plc://<site>/<project>/<element>.
PLC and DCS exports
| Vendor and tool | Export | Key in site.yaml exports | Status |
|---|---|---|---|
| Siemens TIA Portal | SimaticML (Openness XML) folder export | siemens | Early access: confirmed against synthetic exports, awaiting a site export |
| Rockwell Studio 5000 / RSLogix 5000 | L5X | rockwell | Early access: confirmed against synthetic exports, awaiting a site export |
| Rockwell RSLogix 500 (SLC 500) | ASCII export and address database | slc500 | Early access: confirmed against synthetic exports, awaiting a site export |
| Rockwell RSLogix 5 (PLC-5) | ASCII export and address database | plc5 | Early access: confirmed against synthetic exports, awaiting a site export |
| Schneider Control Expert | XEF, including its SFC sequences | schneider | Early access: confirmed against synthetic exports, awaiting a site export |
| Mitsubishi GX Works3 | Export folder (CSV and ST) | mitsubishi | Early access: confirmed against synthetic exports, awaiting a site export |
| Omron Sysmac Studio | PLCopen XML | omron | Early access: confirmed against synthetic exports, awaiting a site export |
| B&R Automation Studio | Project sources | br | Early access: confirmed against synthetic exports, awaiting a site export |
| Emerson PAC Machine Edition (PACSystems) | PLCopen XML | pacsystems | Early access: confirmed against synthetic exports, awaiting a site export |
| CODESYS V3.5 | PLCopen XML (Project, Export PLCopenXML), recognised by its CODESYS file header; global variable lists and direct addresses (%IX0.3) read | codesys | Early access: confirmed against synthetic exports, awaiting a site export |
| Siemens STEP 7 V5.x Classic (S7-300/400) | Source export folder: SCL (*.SCL), STL (*.AWL) and the symbol table (*.SDF) | step7 | Early access: confirmed against synthetic exports, awaiting a site export |
| Bachmann, Beckhoff and other IEC 61131-3 tools | PLCopen XML | bachmann, beckhoff or other | Early access: confirmed against synthetic exports, awaiting a site export |
| Emerson DeltaV | FHX export | none: through the watched folder | Early access: confirmed against synthetic exports, awaiting a site export |
| Siemens PCS 7 | Chart export (XML) | none: through the watched folder | Early access: confirmed against synthetic exports, awaiting a site export |
| ABB 800xA | Control Builder export (XML) | none: through the watched folder | Early access: confirmed against synthetic exports, awaiting a site export |
STEP 7 Classic sources are read per block: each SCL block's lines and each STL network become cited elements, and an absolute address (I 1.3, MW 100) resolves to its symbol. Data block sources are listed in the import summary, not imported. A CODESYS export dropped on a watched share is recognised as CODESYS; STEP 7 source folders are imported with the import command.
In CODESYS, export with Project, Export PLCopenXML; in the SIMATIC Manager, export the blocks as sources together with the symbol table. Both importers follow the vendors' documented formats.
Early access means the importer is built and tested against synthetic exports of the bench and demo plants, and is awaiting a real site export to confirm it. Send 4M a sample export first: an unsupported construct is listed in the import summary, never silently dropped.
Site lists
The site's tags.csv, alarms.csv and interlocks.csv in the plant folder are applied on import: they give each tag its description, range and units, each alarm its text and priority, and each interlock its condition and the equipment it acts on. The alarm list and the cause-and-effect chart are cited per row (alarm_list and cause_and_effect in site.yaml).
HMI and electrical exports
| Export | What BooleX takes from it |
|---|---|
| Siemens WinCC tag and alarm exports (XLSX) | Each HMI tag and alarm linked to its PLC tag, so a question quoting the panel's alarm text reaches the code |
| Rockwell FactoryTalk View tag (CSV) and alarm (XML) exports | The same |
| EPLAN Electric P8 and AutoCAD Electrical reports (PLC assignment, terminals, cables, devices; XLSX, CSV or XML) | Wiring as data: device designations, terminals and cables, each row cited |
| AutomationML (IEC 62714) electrical design | Devices and their PLC I/O |
| Schematic PDF, DXF, DWG, scanned sheets | Pages, devices and cross-references, with OCR for scans |
| DEXPI P&ID and Visio | Equipment, valves, instruments and their connections |
References that do not resolve to a PLC tag are kept unlinked and reported.
When the code changes
A new export imported for the same project becomes a new revision. Answers that cited the old revision still open it, the evidence card says when the code changed since the previous import, and the Code change review workflow lists changed elements on alarm and interlock cause chains. See Import code exports.
Legacy code review
The same model gives a review report of one imported project: dead logic, unused tags, documentation gaps and migration blockers, each finding cited. See Run a code review.