neuron-explorer
Qwen3.5‑4B 전용 조향형 뉴런 탐색기, 모든 MLP 뉴런을 밀어 결과를 보관·탐색
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기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.