AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
翻译准备中
个人 GitHub 账号下公开仓库的所有者可以登录并验证所有权,自行管理介绍,无需管理员批准。
登录并生成验证文件,在 30 分钟内将其提交到此仓库的默认分支。其他分支或分叉仓库中的文件无效。然后在下方检查文件,即可无需管理员批准直接管理项目。请保留文件以维持管理权限。
如需登录,将前往登录页面。登录后请回到此处,再次点击所选的验证按钮。
在项目文件夹中运行 /nomorevibe verify,即可验证所有权并自行管理介绍。
一分钟完成验证Write PLC programs in ladder or Structured Text and run them on open hardware. An IEC 61131-3 compiler with a browser ladder editor that also reads Rockwell L5X, TwinCAT and PLCopen projects.
翻译准备中
取自仓库 README
正在加载完整 README。 以下为已保存的摘录。
Write PLC programs in ladder or Structured Text, and run them on open hardware.
plcc is an open-source compiler for IEC 61131-3, the standard language family of
industrial controllers. It turns ladder logic and Structured Text into native
machine code for whatever chip you have, and reads the project files engineers
already use: Rockwell Studio 5000, Beckhoff TwinCAT, CODESYS, and OpenPLC.
Open plcc studio → the ladder editor, in Chrome or Edge.查看完整 README ↗Write PLC programs in ladder or Structured Text, and run them on open hardware.
plcc is an open-source compiler for IEC 61131-3, the standard language family of industrial controllers. It turns ladder logic and Structured Text into native machine code for whatever chip you have, and reads the project files engineers already use: Rockwell Studio 5000, Beckhoff TwinCAT, CODESYS, and OpenPLC.
Open plcc studio → the ladder editor, in Chrome or Edge.
XIC Start XIO Stop OTE Motor),
simulate them, and watch a real PLC live over USB. Nothing to install; projects stay in
your browser..L5X, Beckhoff TwinCAT projects, and PLCopen XML
(exported by CODESYS, OpenPLC and others) compile as they are.flowchart LR
subgraph Sources
studio["plcc studio<br/>(ladder editor)"]
st["Structured Text<br/>.st"]
l5x["Rockwell<br/>.L5X"]
tc["Beckhoff TwinCAT<br/>.plcproj"]
xml["PLCopen XML<br/>CODESYS, OpenPLC"]
end
plcc{{"plcc<br/>check · translate · compile"}}
subgraph Runs on
opta["Arduino Opta<br/>and other ARM PLCs"]
linux["Linux PLCs<br/>and PCs"]
sim["Browser<br/>simulator"]
end
studio --> plcc
st --> plcc
l5x --> plcc
tc --> plcc
xml --> plcc
plcc --> opta
plcc --> linux
plcc --> sim
manifest[("device manifest<br/>I/O, flashing, console")] -.-> plcc
A compiled program doesn't know which board it runs on. It reads inputs and writes
outputs through a standard process image (%I, %Q, %M), and a small runtime
written once per board connects that image to the real terminals.
plcc compile motor.st -o motor.o --device arduino-opta
Building plcc and every other command: docs/development.md and
docs/cli.md.plcc is young and moving fast. What has been shown to work:
Still experimental: the studio's online connection to real hardware, flashing from the browser, compiling inside the browser, and plcrt, our own bare-metal runtime. Known gaps are listed in docs/known-issues.md.
| Language support | What compiles, the standard library, targets |
| Command line | Every plcc command and input format |
| Running programs | The runtime contract and hardware abstraction layer |
| Ladder · Translation | Ladder formats, IEC ↔ Rockwell mapping |
| Rockwell L5X · TwinCAT · CODESYS | Vendor formats and behaviour |
| Device manifests | Describing a board |
| Developing plcc | Layout, building, tests |
Mozilla Public License 2.0, with a compiler output exception: programs you compile with plcc carry no license obligation, and you can link the runtime into a proprietary product. Improvements to plcc's own files come back under the MPL. Device manifests are CC0.
Contributions are welcome, signed off under the DCO. No CLA.