How it fits
Ladder leaves CLICK as readable source, gets tested in Python, and comes back through the clipboard. The project file changes only when you save it in CLICK Programming Software.
-
CLICK
Save the project
Draw ladder as usual. Save
Machine.ckp. -
ClickNick
Source refreshes
Every save regenerates the ladder as pyrung text. Your tests and notes stay put.
-
pyrung
Test offline
Run scans, write pytest cases, trace cause and effect. No hardware.
-
ClickNick → CLICK
Paste back
Preview Changes shows the rung diff. Copy to Click puts the rungs you pick on the clipboard. Paste in CLICK, save.
.ckp.
The project file changes only when you save it in CLICK Programming Software. Everything else is a copy you can regenerate.
ClickNick
The app
Nickname autocomplete, program checks, an offline Console, and your ladder (as Python) after every save, beside CLICK Programming Software. Windows.
pyrung
The engine
A Python DSL that reads like ladder and scans like a CLICK, with pytest, a VS Code debugger, cause/effect tracing, and exhaustive checks. Also generates CircuitPython for the P1AM-200.
laddercodec
The codec
The compatibility layer for CLICK ladder data. Reads and writes CLICK's native representations and enables reliable round-tripping between CLICK and the pyrung/ClickNick toolchain.
pyclickplc
The wire
Modbus TCP client and server for CLICK PLCs, plus the data I/O for addresses and DataView files. Both pyrung and ClickNick are built on it.