| name | machine-expert-reference |
| description | Offline ME/CODESYS terminology, ST syntax, and bundled Schneider PDF manuals — read before writing PLC code or answering ME/M262 questions; do not search the web for basics covered here. |
| metadata | {"sylo":{"category":"automation","icon":"book"}} |
Machine Expert / CODESYS — offline reference
Before writing or refactoring Structured Text, read the bundled files under this package (no web search for syntax or ME naming):
| File | Read via |
|---|
| Terminology & paths | references/machine-expert/terminology-me-codesys.md (under Pi agent dir after bootstrap) |
| ST syntax cheat sheet | references/machine-expert/st-syntax-codesys.md |
| Index | references/machine-expert/README.md |
| Operator PDF manuals | references/machine-expert/operator-docs/*.pdf — catalog in operator-docs/README.md |
Dev monorepo: same tree at packages/sylo-machine-expert/references/. Prefer the Pi agent copy when present so paths work regardless of cwd.
Bundled PDFs (ME / M262 / motion / SoftStruxure)
When the operator asks about Machine Expert UI, M262 hardware or programming, motion, OPC UA / Symbol Configuration in ME, device repository, or SoftStruxure templates:
- Read
operator-docs/README.md for which PDF fits the question.
- Read the matching PDF from
references/machine-expert/operator-docs/ (or monorepo packages/sylo-machine-expert/references/operator-docs/).
- Answer from that material; cite the manual name, not random web pages.
- Still use
st-syntax-codesys.md for IEC ST syntax — PDFs are not the primary ST cheat sheet.
When to load
- First ST edit in a chat about Machine Expert.
- Operator asks “how do I … in ST / ME / CODESYS?”
- ME product UI, M262, motion, or SoftStruxure (consult
operator-docs/ PDFs).
- Unclear POU type, file extension, or FBS folder name.
- Reviewing
IF / CASE / FOR / FB call syntax.
Pair with machine-expert skill
- machine-expert-reference — what words and syntax mean.
- machine-expert — where files live (workspace →
.fbsproj → Application.application.xml.v3^).
me_fbs_discover — resolve actual paths on this PC.
Rules
- Do not fetch IEC 61131-3 or CODESYS help URLs for basic syntax covered in
st-syntax-codesys.md.
- Do read neighboring project POUs for naming, libraries, and task wiring.
- Do not invent Studio 5000 ladder idioms; target is IEC ST for ME.
- Paraphrase this reference in answers; the operator does not need the full standard quoted back.
Never suggest (removed workflows)
| Stale | Use instead |
|---|
me_cds_export_text / me_cds_import_text | FBS: reload project in ME after disk edits |
Project_daemon.py, ScriptDir scripts | Not used for .fbsproj |
sync/project-view/ | Edit under Application.application.xml.v3^ |
| GitHub / Platform git setup for editing | Optional; not required to edit ST |
See machine-expert skill → Disk ↔ IDE sync.
Refresh (operator / maintainer)
Optional update from vendor help:
python packages/sylo-machine-expert/scripts/fetch_reference_help.py
Requires network; rewrites references/_fetched/ snapshots only — curated files stay the agent default.
