What's new

Plain-language highlights for each stable release.

[2.1.0] — 2026-10-15

New

2.1.0 is the first stable JasperX controller: claim it into JasperX, build and change its programme in the cloud, and download it to the controller; changes to logic that already runs wait for your approval outside Setup.
The controller’s old local IDE is gone. For when JasperX cannot be reached, the controller now has a plain local web page that lists tags and their values and downloads or uploads the backup; it opens with the password shown once when the controller is claimed.

Improved

Deploying logic now works it out at once on live values, so outputs move at the press to what the new logic says; with the logic stopped, it runs at Start.
Pressing Start or powering up now works the logic out in chain order, so an output no longer pulses for a moment and a downstream script no longer starts from an upstream’s stale value.
After a download, Start now drives the outputs to what the new programme says rather than to the old programme’s values, and logic you stopped stays stopped.
With the logic stopped, Run once is refused with “The logic is stopped; press Start first.” and nothing is written.
Jasper’s changes now meet one approval, on the controller: new logic that touches nothing running goes live at once, and a change to logic that already runs or to a connector’s tag waits for the red card outside Setup.
Jasper no longer says a script runs before it is deployed, and after a deploy he reports what moved instead of running the logic again.
Jasper now lays out a new programme by the plant’s areas and equipment, shows you the folder tree in his plan, and gives each tag one of the ten tag types.
Jasper now calls the controller’s modes Setup, Commissioning and In service.
In JasperX, Jasper now talks about logic, Apply and approvals, the words on screen, instead of scripts, deploys and gates.

[2.0.3] — 2026-09-29

Fixed

Adding or editing a connector whose output is a tag one of your scripts already drives could restart the whole controller, with every connector down for about ten seconds. The connector is now created as usual and the controller keeps running, whether you or Jasper made the change.
A controller on the Beta update channel is not offered 2.0.3; set its update channel to Stable to receive 2.0.x patches.

[2.0.2] — 2026-09-22

Fixed

When Jasper tests a script change on a commissioning or production node, it is told once which downstream scripts must join the test, not one more layer on every run.
A script test that hits a limit now says which step and which tag it stopped on and what to change, instead of failing silently.
Jasper’s script-test replies are much shorter, with the same facts, so each turn costs less.
When a tag rounds its value to a set number of decimals, Jasper sees that and tests against it, instead of failing a correct test.
In Agent (with approvals), Jasper changing only a tag’s description no longer stops for your approval; a value, type, decimals or boot-behaviour change still does.
After you approve a deploy, Jasper no longer spends extra turns re-reading what it just put live.
After you approve or reject a deploy in the card, Jasper is always told, so it no longer looks stuck waiting for an answer you already gave.
A node running in Docker now tells you how to update it: one line to paste for your operating system if the installer set it up, or the exact steps if you started it with your own docker run command.

[2.0.1] — 2026-09-15

Fixed

A node could only hold about a thousand number and true/false tags. Past that, new tags failed with a misleading “owned by another connector” message and a connector install could be wrongly quarantined. A node now holds 65,536 by default, warns at 80 % full, and when the table is full every message — tag creation, restore, connector install — says so and how to raise the limit (JN_DT1_SLOTS in /etc/jaspernode.env). Jasper sees how full the table is from 50 % up.
Creating or deleting hundreds of tags at once — a big MQTT device coming online, deleting a folder, restoring a project — could freeze the node for two to three seconds, long enough to put field connectors at risk of dropping to their safe state. These operations now run in small steps, and the database housekeeping that used to hold up tag saves now runs in the background, so nodes with flash storage (such as JasperMate) no longer pause for it.
When Jasper tested a script change, the node could pause for about two seconds and log a late heartbeat warning. Testing now runs in the background without pausing the node.
When an MQTT Sparkplug device announces more metrics than the node can take, the MQTT connector now reports one clear line saying how many failed and why, instead of one misleading error per metric. Update MQTT to 2.3.2 after updating the core; the Modbus, S7, EtherCAT, Serial and JasperMate updates carry the same clearer messages.

[2.0.0] — 2026-09-14

New

Connectors install on demand from JasperNode’s signed catalogue, so a new or fixed connector reaches your node without a JasperNode update. The 2.0 roster: Modbus TCP/RTU, Serial, EtherCAT, S7, JasperMate I/O and LiDAR on the field side; MQTT (with Sparkplug B), an MQTT broker, InfluxDB, a Modbus server and a browser HMI on the IT side. Name the ones you need at install time with CNTR=modbus,s7, add the rest from the Connectors page, and a restored program brings its own connectors with it, switched off until you turn them on.
Jasper, the AI agent, works on the node from the chat: Ask mode to explain and troubleshoot, Agent mode to change things with your approval, auto-run when you trust it. It reads and edits tags in bulk, probes a Modbus device or scans an EtherCAT segment with tools the connector itself provides, and names tags and connectors as clickable chips that jump to them.
Logic changes by Jasper are drafts until you deploy them. Jasper tests a set of drafts against a copy of your live program, has to say in advance what each step should produce, and the whole set then lands in one step or not at all. Anything that changes running logic or touches a tag wired to a device asks you first: an amber Consent card in development, the red Deploy Gate on a commissioning or production node. Field-side actions — writing to a device, updating a connector that drives equipment — always wait for your Approve and say what will physically happen.
Each node runs in one of three modes — development, commissioning or production — switched from the status bar by a person, never by Jasper. The mode decides how much Jasper must test and who must sign off before its changes reach the machine.
Logic lives on tags as scripts that run when the tags they watch change, reading other tags without triggering, with PLC-style timers and a state cache. The Logic Cycle warns when scripts would trigger each other in a loop or faster than it can keep up, and the node logs when its own heartbeat runs late — the window in which a field connector drops to its safe state.
The browser IDE gives you the tag tree, a script editor with a Flow view, a page per connector instance, an Overview with a card per connector, HMI dashboards from the HMI connector, and a basic phone layout for checking a node and talking to Jasper on the move.
A node updates itself: it follows the Stable or Beta channel you pick in System Config, downloads the signed build in the background, verifies the signature and installs it, keeping tags, logic, connector configuration and its Node ID. Connectors update from the same page, several in one restart, and a connector that keeps crashing is switched off with the reason rather than restarted forever. Container nodes update by pulling the new image.
If you ran the beta: 2.0.0 is the 2.0.0-beta.22 build, unchanged. Nodes on the Beta channel receive it as a normal update; switch them to Stable in System Config → Software updates afterwards if you no longer want test builds. From 2.0.0 on, every 2.x update keeps your programs and connector settings working — a change that would break them would be a 3.0.0.