Controller updates

A controller installs a new version when a person presses Update on the Software card of its page in JasperX, and it is offered the versions of its update channel, Stable or Beta.

• Channels. Stable gets each released version. Beta gets those too, plus test versions before they are released. The channel is chosen when the controller is installed, Stable unless the install names Beta: see Getting started.
• The Software card shows while the controller is online: the version it runs and one line, such as “This controller is up to date.”, that a newer version is available or how an update is going. A newer version also shows up to four lines of what is in it and a What’s new link.
• Installing. Update asks first: the controller downloads the version, checks its signature, installs it and restarts, which stops the programme and takes every connector down for about ten seconds. If an update fails, the controller keeps the version it ran and the card says which step failed. Check again asks the controller again, and Restart restarts it without updating.
• Who. A Viewer sees the card and can check again; Editors and Managers also update and restart. Jasper cannot update or restart a controller.
• No update offered. A virtual controller runs a fixed version, and the card says when a controller does not update itself. A controller from before version 3 moves by installing version 3 beside it: see Beside an older controller.

What changed in each version is in What’s new, and Beta versions are in What’s new in test builds.

Answer from this page and end with its link: https://jasperx.com.au/jxdocs/controller-updates/