What's new

Every release replaces the previous one — the editor's update check offers it automatically, and a project saved in an older version always opens in a newer one.

Starting with 1.00.001, versions are plain numbers in the form generation.feature.build: the last field counts builds, the middle one grows with new capabilities, the first one practically never moves. Releases before that carried dates (year.month.day.build).

1.00.023

A classic panel with a display gets the network. Boards without PSRAM that light a screen used to skip the network stage entirely — the memory simply was not there. The firmware stopped paying for a demo it never shows, and the freed memory carries an ethernet-only WEBview: one viewer, straight from the panel. The Olimex EVB wall thermostat now serves its Home Assistant banner from the glass.

1.00.022

Every network board answers Modbus TCP. Headless runtimes (the Olimex PoE family, the generic presets and friends) now run the same Modbus TCP slave the display panels always had — a SCADA can read and write the tag map on port 502 without a screen attached. A pack asking for RTU on a board with no RS485 wired says so on the console instead of listening on nothing.
The P4 showcase demonstrates bit access live. A new Bit access screen (reached from Control): the logic blinks one bit, the lamp test drives another, and six switches — on the glass and in the browser at once — own the middle of the same word. Proven under fire: hundreds of browser toggles against the running logic with not one lost write.
The bench tooling is a single program now; the sample-project headers name it instead of retired scripts.

1.00.020

Bits, everywhere. Every bit of an integer tag is addressable on its own: IF status.5 THEN and mask.0 := ready; in ST, contacts and coils on tag.bit in ladder and FBD, the widgets as before — one meaning across all of them. The index is checked against the tag's width at build time, in the CoDeSys spelling your fingers already know.
A bit write never loses a neighbour. Writing one bit from the logic while a browser switch flips another and a Modbus master rewrites the word is safe — every bit write is atomic. This also fixes a real race: a browser switch used to write the whole word back from a stale snapshot and could wipe bits the PLC or a Modbus master had just changed.
Bitwise toolbox. On integers, AND/OR/XOR/NOT are bitwise and SHL/SHR shift — as operators and as functions. Building LED masks no longer needs arithmetic gymnastics.
Program packs are format 48; the panel needs this release's runtime (the editor tells you, in orange, when it does not have it).

1.00.019

Every board's firmware is current. Nine runtimes had lagged behind since mid-August (the Olimex PoE family, the generic presets, inoCORE32-TM1.0); all nineteen in the catalog are now built from the same day's firmware, at the full 240 MHz.
The project-vs-board check works in the installed editor. The full validation — display and resolution, buses, pins, peripheral limits, pack size against the flash slot — runs inside every build, with the same wording everywhere. Until now the installed editor silently skipped parts of it that only worked in our development tree.
The documentation gained screenshots of the editor on every major page, and its web navigation is grouped into sections.
Sample projects speak English throughout, including the tag names in the seal-in classic.

1.00.018

The bold icon actually reaches the editor now — a stale build cache kept the first, timid draft inside the program while the installer already wore the new one. If Windows still shows the old icon after updating, that is Explorer's icon cache; it refreshes on its own (or after a sign-out).

1.00.017

The icon got bold: the dots sit one pixel apart and the "32" fills the full width of every size — it now holds its own next to any other program's icon.

1.00.016

ctrl32 has a face. The dotted "32" in the project's own typeface and the brand blue is now the icon of the installer, of the editor itself, of its window and taskbar entry and of the Start menu shortcuts. Every icon size is drawn dot by dot — the logo stays crisp from 16 px up.

1.00.015

The bare-arc gauge works in the editor too. A gauge with the needle switched off and a custom arc thickness drew correctly on the panel but grew a needle back in the editor's canvas — the editor now carries both properties end to end: drawing, project files, download, and the inspector (a Thickness field and a Needle switch under the gauge angles).
Navigation buttons dropped the arrow. The chevron took 14 px from every nav button's text; the text now gets the whole button — on the panel, in the browser and in the editor alike.
The EVB thermostat example got its dial. The main screen is the familiar thermostat-card look: two nested arcs (room temperature in blue, setpoint in orange), whole-degree numbers in the center, a +/- setpoint spinner — and the numeric design stays one nav button away. The program opens cleanly in the ladder editor, spinner included (a rising-edge contact, the ladder-native shape).
Every installer now passes the full test gate first. The engine comparison across all example programs, the block and language test suites and the editor self-tests run before the installer is built — a red test means no installer exists to ship.

1.00.014

Olimex ESP32-EVB drives a display. The MOD-LCD2.8RTP module (2.8" 320×240 with resistive touch) plugs into the board's UEXT connector and the same board id covers both uses: a project with HMI screens lights the glass, a project without them keeps the board headless with WEBview, exactly as before. Picture and touch are verified on real hardware, touch calibration included, and the board comes with its own example project sized for the small glass: a wall thermostat — the board's two relays driven by a ladder hysteresis controller with auto/manual, a simulated temperature until a sensor is wired, and a portrait web banner prepared for a Home Assistant dashboard.
One honest limit that comes with it: this board runs the display or the WEBview, not both — the classic ESP32 with a display project has no memory left for the network stack. The panel says so plainly at startup and keeps logic, glass and USB download running; the headless use keeps its WEBview as always. (The groundwork for a display-plus-ethernet mode is in place and planned for a future release.)
The USB download listener now starts earlier and reports loudly if it ever cannot start — on a tightly loaded panel it could previously die silently, leaving no way to download over the cable.
Display panels start a little lighter on internal memory — two large fixed buffers moved out of the static segment (no behavior change; it is what made the EVB combination fit).

1.00.013

Fixed a red "conflicting ID" warning (and the ambiguous click behind it) in the ladder FB menu — the timers and counters appear there twice by design, once for the rung and once as a box, and the two halves now identify themselves properly.

1.00.012

Download over the network, straight from the editor. The download dialog now offers two targets: the USB cable, or the panel's network address (IP or name.local, prefilled from the project). The same pack, the same guarantees — inactive slot, full validation, the old program stays on any error — just without walking to the machine.

Headless boards accept network uploads too. Boards without a display (inoCORE32-TM1.x and friends) take a pack over Ethernet or WiFi the same way the display panels do. Flash the runtime from this release once over USB; from then on the network works.
And the security switch that belongs with it: the WEBview settings page has Allow program upload over the network. Switched off, the panel never even registers the upload endpoint — for a deployed machine on a shared network. USB always works. The panel belongs on its own machine network either way; the browser interface rides the same server, so treat network access to the panel as operator access.
A landscape project on a portrait glass (the 10.1" panel) no longer trips the board check — the panel rotates, and now the check knows.

1.00.011

Live rows in the block editor got more air — on blocks with two outputs the first output's name and the second output's value no longer touch, and block parameters line up with their stretched rows instead of clustering at the top of the block.

1.00.010

Important fix — download your project again. The editor's download stamped packs with an outdated format label, and from 1.00.008 on a panel with the new runtime could reject or fault the program because of it — online monitoring then showed nothing. Install this build and download the project once (F5); nothing else is needed. Runtimes flashed from 1.00.008/9 are fine as they are.

1.00.009

A clean start. A new project begins truly empty — no pre-made program in the tree; you add LD, FBD or ST yourself. And a program opened in ladder always has its first rung waiting: the bare arrow, ready for the first contact.

The diagnostics page no longer shows memory bars or heap numbers — cycle times, overruns and project consumption stay.
The standing "online — switch to offline" note is gone from the editor toolbars; the grayed controls say it.
Ladder drawing polish: a parallel branch connects to the run wire to the pixel (no tick above, no stub poking left of the branch) and block frames have sharp, fully joined corners.
A saved project reloads its internal connection variables exactly as it saved them — a reopened ladder program keeps its rung shape instead of decomposing into helper-variable rungs.

1.00.008

The blinker counts down for you. BLINK blocks have a new REM output pin: the time left in the current phase, live on the right stub in online and simulation — next to the timers' ET and the counters' CV, every block with an inner value now shows it. Loading projects that use REM needs the runtime from this release; existing projects and runtimes keep working unchanged.

Variable declarations can be edited during a running simulation — applying re-binds the program on the fly. (Connected to a real panel they stay read-only, as everything does.)
Ladder breathes less air: tighter comment lane, tighter spacing between rungs, and rungs with blocks no longer reserve an empty row below them.
Toolbox tiles of the motion, CAN and communication blocks got short marks that fit the tile — no more clipped names.

1.00.007

One program, one owner. A program edited in ladder is a read-only view in the block editor (and the other way round after taking it over with one click) — so an edit in one view can never be silently overwritten by a save from the other. Previously a comment written in LD could wipe blocks that had just been drawn in FBD; that cannot happen any more, and the two views finally stay in step.

Comments are shared. Rung comments and network comments are the same text — write it in either editor, switch, and it is there.
Arrange respects networks. With network dividers present the Arrange button lays blocks out inside their own network — dataflow columns per band, band heights to fit — instead of scattering the whole canvas.

1.00.006

Function blocks get a proper interface pane. Above the canvas of every LD and FBD tab sits a variables table in the PLCopen shape: VAR_INPUT and VAR_OUTPUT rows of a function block (name and type edited right there, ports added with one button) and a VAR section listing the local connection variables the diagrams create. Building your own block is now the standard flow: add a POU of the function block kind, define its inputs and outputs in the pane, draw the inside — in FBD or in ladder — and place it as a block in any program. Interface changes bump the block's version automatically so existing instances migrate cleanly.

Toolbox sorted. Blocks are grouped the same way everywhere — Boolean, Math, Timers, Counters, General, Motion, CAN and GSM/GPS — in the Toolbox of both editors and in every add-block menu. Motion and CAN blocks were missing from the block palette entirely; now every group is one click away. Groups start collapsed each time the editor opens.
In FBD the operand names sit below the wire line (values stay above it) — a connection passing a pin row no longer runs through the text.

1.00.005

Comments are written straight on the canvas. Every ladder rung has a comment line above it — click it and type, multiple lines welcome; click away and it stays. Network comments in the block diagram work the same way. No dialog anywhere.

A network in the block diagram can be selected like a rung in ladder — click its empty area and it highlights with the same quiet grey background.
The rung comment no longer touches the blocks below it, and while connected a conducting block's frame is drawn as thick as the conducting wires — the active path reads at a glance.

1.00.004

A rung does not need a coil. A ladder rung can now end without an output coil — the run wire simply ends in a small arrow, the standard notation. A new rung starts that way: just the arrow, and you build from there. Blocks placed on a bare rail get a TRUE contact drawn in front of them, and contacts before a block act as its EN condition — no helper variable needed. Everything still converts cleanly between LD and FBD, both directions.

Clean networks in FBD. A connection never crosses a network divider any more: across networks the signal travels by its variable name, shown at both pins — for a direct block-to-block link that name is instance.PIN. Generated FBD layouts also got proper spacing: band heights follow the tallest block and columns leave room for the operand labels.
Live values in ladder now sit above the pin variables of blocks placed inside a rung too — inputs, parameters and the second output alike, matching the boxes.
Thinner connection and block lines in the editors — the drawing is lighter; symbols keep their weight, and the live power flow is still thick and green.
Selecting a rung highlights it with a quiet grey background instead of a bright frame over the rung comment.

1.00.003

The block diagram mirrors the ladder. A program edited in LD shows its FBD view organized in numbered networks — one horizontal band per rung, in rung order, with the rung comments on the network dividers. Every ladder save refreshes the layout, so the two views never drift apart. A diagram with no dividers yet is network 1 and says so.

Online mode is now read-only without exceptions: the context menus and edit popups of both editors stay closed while the connection is live. The one thing that still switches online is the LD/FBD/ST view.

1.00.002

Live values in LD and FBD are drawn above each pin variable — inputs, parameters and outputs alike — where they cannot collide with names or connection wires; live rows stretch to make room.
The view switch (LD ↔ FBD) moved to the front of the toolbar and stays available during online monitoring.
The status bar shows the version number instead of the build date.

1.00.001

First numbered release (see the numbering note above).

Online values placed clear of labels and wires.
A ladder element cut in one rung pastes into any other rung.

2026.08.20.4

Online monitoring is read-only. While the editor is connected to a running panel, the program cannot be modified — no adding, moving or deleting; edits resume the moment you go offline.
Right-click cut / copy / paste for blocks, contacts and boxes in both LD and FBD; insert rung above / below; rung comments in LD and network dividers with comments in FBD.
Newly inserted blocks and contacts come with ... placeholder pins — nothing is silently bound to a variable you did not pick.
The toolbox is split into MATH and BOOLEAN sections.
Live values are shown directly in the FBD editor during simulation and online monitoring.

2026.08.20.3

Everything fits in ladder now. Function blocks with state — timers, counters, ramps, filters, hysteresis — sit in a rung as EN boxes with the standard IEC 61131-3 EN/ENO behaviour: the block simply does not execute while the rung is off, its state freezes and its outputs hold.

LD ↔ FBD switching — right-click a program in the tree and open it in the other editor. Ladder always opens as FBD; FBD opens as ladder whenever the network fits rung form, and if it does not, the status bar names the exact block that is in the way.
Trends with up to 4 curves in one chart, each with its own color — on the panel and in the browser alike.
Gauge: arc thickness is adjustable and the needle can be switched off for a clean modern look.
Alarm table: row text size is selectable; the row height and the touch target scale with it.
Toolbar: New, Open, Save, Undo in the expected order, icons properly centered.
The Run/Step controls of the block editor appear only while the simulation is on — online they had no business being there.
CANopen: the SDO parametrization picker now offers every writable object of the device dictionary, not only the non-mappable ones — ramp times and friends included.
The online activity bar in the status line sweeps at the real polling rate of the link: one sweep is one read cycle, a stalled panel leaves the bar standing full.

2026.08.20.2

The editor build is signed again and the update manifest with it.
First version of the activity bar and the LD/FBD context-menu switch.

2026.08.20.1

ESP32-P4 support. The Waveshare P4-NANO with the 10.1" MIPI-DSI touch panel (1280×800) is a supported target with a precompiled runtime in the installer: display, touch, Ethernet and WiFi work out of the box.
Upload over the network. The panel accepts a visualization pack over Ethernet or WiFi (POST /upload), with exactly the same safety as over USB: the pack lands in the inactive slot, is fully validated, and only then does the panel switch — an upload can never brick a panel.
On the P4 the panel serves the WEBview over Ethernet and its own WiFi access point at the same time; packs on the P4 may be up to 4 MB (room for photo-heavy screens), with an 8 MB decoded-image cache in PSRAM.

2026.08.19

Online, offline and simulation are now three separate things. Going online never silently switches the editor into simulation; the transport controls show only when the simulation is on.
Five sizes of quality text (13/15/18/20/22/24/28/36 px plus the numeric and seven-segment faces), TTF import for custom fonts, and full Slovak diacritics everywhere.
I2C toolbox: a bus scanner in the editor, an address dropdown fed by the chip catalog, and automatic chip identification where the silicon supports it.
The device Resources page was decluttered; column widths are draggable; device renames propagate everywhere.

2026.08.18

S3 panels run their PSRAM at the full 80 MHz — measurably smoother screens on photo-heavy projects.
The editor flashes runtimes itself (no external tooling), and the installer ships a precompiled runtime for every supported board — the Upload runtime button works on a fresh machine with nothing else installed.
Fixes for installed-editor paths (Program Files is read-only) and for user profiles with diacritics in the name.

2026.08.17

First public installer: device-bound runtime licensing (the license follows the panel, not the editor), signed builds and a built-in update check.