The AI-era control platform for WEG and Mitsubishi drives.
A clean-room implementation of both vendors' tool chains — compilers, linkers, the real transfer protocols — plus a digital twin, offline simulation, a connectivity gateway and fleet management. One browser tool that programs, flashes, mirrors and simulates a machine: on a desk with no hardware, on a bench, or over LTE.
Five faces of one tool
cyclePanel began as PLC migration in three days. Building the migration built the tool chain underneath it — and the tool chain is the product: complete control of the machine, from the first rung to the fleet map.
Four editors
WLP clone for the CFW500, FR Developer and FR Configurator clones for the FR‑E800, a GTX editor for the GOT. Ladder, parameters, screens, scripts, recipe — in the browser.
Real protocols
CFW500 SoftPLC download with its password handshake, FR ladder over USB and Modbus/TCP, GOT package read and write over USB and Ethernet. Python, any OS, no vendor DLL.
Mirror the machine
Drives and the GOT's own screens, live from a running machine — through the panel's Ethernet gateway or the TRB's register block. Watch step, state, lamps, faults.
Run it without hardware
A soft‑PLC executes the real ladder, a plant model supplies every input, a panel model draws the screens. Add a bench and the same inputs drive the real drives.
Gateway node
Teltonika TRB: LTE, GNSS, I/O relay for flashing with the panel held off, MQTT uplink. Every router page inside the suite. Sites → machines → nodes, five verbs on each.
Clean-room, byte-exact, vendor tool as the oracle
The vendor IDE is used to verify, never to build. Our compilers reproduce the vendor object byte for byte; our file writers produce projects the vendor tools open with zero errors.
WLP clone — cycleWLP
Ladder + parameters in one project. Spec → ladder → pages → macro → .ldd/.mld/.bkp. Rung contract, power-flow linters calibrated against WLP, then WLP's own verdict. Byte-exact compiler (compile_program) — cost a rewrite offline, no WLP, no drive. The 7680 B program cap measured on the drive, not read from a manual.
FR Developer clone — cycleFR
The .fgw project of the drive's built-in PLC decoded byte-exact: dual-address labels, one-hot step chain, 16.16 rung geometry, local/global parameters. Edited and written back; FR Configurator2 accepts it. Ladder read off the real drive over USB.
FR Configurator clone
The .frc drive parameter set. Parameters live over USB and Modbus/TCP (Pr = register − 944, unit 0). The file editor ships with the Windows build.
GTX editor
Screens, comment tables in seven languages, scripts No.10–13, recipe, device repoint (Mitsubishi → WEG addresses, station notation @2:1-2). Package read over USB and Ethernet with zero differences; the write protocol — fragments, manifest, delete list — decoded from captures.
The same program, three places
Desk — no hardware
Simulation supplies every input the machine would: end stops with real carriage timing, door, thermal chain, drive-to-drive link. Event-based software hooks stand in for sensors and actuators. The program walks all its steps; you watch the GOT screens change and the inverters run.
Bench — real drives
The simulation forces the bench's inputs and reads its outputs: bench builds replace physical inputs with markers the twin writes (the same trick the GOT uses). Most of the code runs on the real hardware; the desk only supplies the world.
Machine — monitoring
Digital-twin mode mirrors a running machine exactly: drives and panel screens, read-only apart from the GOT's own buttons. On a desk it correctly shows "Fehler Endschalter" — the inputs really are missing. Once wired, it is the machine.
Bus rule, learned the hard way: one master per RS‑485 pair. With the panel powered, the suite reads through the panel's gateway and injects simulation inputs through the panel; flashing happens with the panel held off by the gateway's relay.
MQTT over the internet, Modbus on the desk
cyclepanel.com · fleet dashboard · AI copilot
│ MQTT — the gateway initiates (carrier‑NAT is no obstacle)
┌─────────┴──────────┐
│ TRB gateway node │ LTE · GNSS · DO relay · Ethernet (TRB246)
│ Modbus RTU st.3 · raw serial · REST/uci · MQTT gateway
└───┬──────────┬─────┘
RS‑485 pair │ │ Ethernet
┌───────────────┴──┐ ┌───┴──────────────┐
│ CFW500 st.1/st.2 │ │ GT2104‑R panel │ gateway :502 · transfer 5015
│ FR‑E820 │ │ (RS‑485 master) │
└──────────────────┘ └──────────────────┘
▲ desk: cyclePanel server — editors · compilers · twin · simulationEvery router page, inside the suite
The Teltonika's web UI is a Vue app over its REST API; the router exposes the same API on ubus. cyclePanel crawled all 123 pages — menu, sections, fields, tables and the 220 endpoints each page reads — and renders them itself, answered live by the router over the SSH key. Mobile, SIM, APN, Modbus roles, I/O, VPN, firmware: read live, write when armed. No screen-scraping, no password on the suite side.
Fleet tree
Site → machine → nodes (drives, panel, gateway). Click a node: monitor (live values, faults, the twin), configure (parameters, screens, network), flash (program, package, firmware), backup (read and keep). The same verbs on every node, backed by the transport that node actually has. GNSS from the gateway puts each machine on the map.
Status, as of 7 September 2026
No claims without evidence. Everything below was measured on a real bench: two CFW500 drives, one GT2104‑R, a TRB145, the cycleWASH Pro program.
| component | state | evidence |
|---|---|---|
| WLP clone: spec → ladder → .bkp | proven | six programs at WLP 0 errors (GO_KB 4224 B · PRO_KBG 7536 B · PRO_S 1648 B · V2.06 and bench variants); .bkp restores byte-identical |
| CFW500 download + commissioning | proven | both bench drives commissioned (user-parameter areas → ladder → run → setpoints); flash through the stick 15.8 s, through the gateway 5.5 s |
| FR Developer clone (.fgw) | proven | decoded byte-exact, edit written back, FR Configurator2 accepts; ladder read off the real FR‑E820 over USB |
| FR Configurator clone (.frc) | partial | parameters over USB + Modbus/TCP proven; file editor with the Windows build |
| GOT package read | proven | Ethernet and USB, 0 differences, 171 objects, 4.17 MB |
| GOT package write | decoded | 415 checks + fake-panel round trip; one deliberate write on the real panel is next |
| Digital twin via GOT gateway / TRB block | proven | unit 0 gateway live; shared register file on the gateway proven both ways |
| Simulation: no hardware · bench GOT‑off · bench GOT‑on | proven · proven · route built | 16 twin tests; injected markers followed by the real drives; GOT sim-input coils read in 23 ms |
| Gateway TRB145 → TRB246 | TRB145 done | LTE up, roles proven, relay, all 123 config pages cloned; TRB246 (Ethernet, 3 DO, GNSS) on the bench 8 September |
| MQTT uplink | next | router side present (MQTT‑Modbus gateway, data sender, broker); platform broker and subscriber are the next build |
PLC migration in three days. Browser simulator included.
Move machine logic between vendors without a six-month consulting project. Mitsubishi ↔ WEG today; Siemens and Allen‑Bradley next. Fixed price from €4,990. No EPLAN, no vendor IDE seat — your team opens a URL and the machine runs.
cycleWASH Pro: FR‑E800 → CFW500 SoftPLC
Reverse: CFW500 → FR‑E800
Try the intake with a sample PDF → · Watch the four-stage pipeline →
From one machine to the standard
Phase 1 — cycleWASH on cyclePanel · now
Everything in the proof table. Last items: bench build commissioned, Windows bootstrap on the next laptop.
Phase 2 — full circle · 8 September
TRB246 wired (relay, SIM, Ethernet to the panel), GOT package read then one real write, panel copies simulation inputs into the drives, bench simulation with the panel on, power-cycle test.
Phase 3 — the platform
- MQTT: platform broker, gateway profiles, twin over the internet
- Fleet dashboard with GNSS map, five verbs per node
- AI copilot: spec → ladder, rung explainer, fault-to-cause — every rung checked by the byte-exact compiler and the twin before flashing
- Cloud login, per-customer fleets
Phase 4 — the standard
- Second machine family, Siemens and Allen‑Bradley importers
- Vendor-neutral portable ladder as the interchange format
- Verified function-block marketplace, certification pack with twin evidence per release
Engineers who run Mitsubishi and WEG drives deserve one platform that programs, verifies, flashes and watches their machines — with AI that writes ladder from a spec and is checked, rung by rung, by a byte-exact compiler and a digital twin before anything touches hardware.
cyclePanel is that platform: a clean-room tool chain for both vendors and the panel between them, built and proven on a real machine, now growing into programming, monitoring, digital twin, connectivity, dashboard and fleet management. The aim is plain: bring the AI era to these two ecosystems and make this the way industrial machinery is created and controlled.