Modes and approval
Each controller runs in Setup, Commissioning or In service, and the mode decides when a person must approve Jasper’s change before the controller takes it (sign-off, in the Terms of Use).
- Setup, while the controller is being built and nothing it controls can cause harm: Jasper’s changes need no approval, except a change to the code a hardware connector already runs.
- Commissioning: “Jasper’s changes to what already runs wait for approval, tested one level downstream.”
- In service: “Jasper’s changes to what already runs wait for approval, tested all the way downstream.”
What already runs, in Commissioning and In service:
- logic already applied
- a tag that applied logic or a connector reads or drives, a value Jasper sets included
- a connector that drives the field or writes what running logic reads
- a connector’s code
New tags, and new logic on tags no running logic or connector uses, never wait.
The controller holds the change and shows a card in the chat listing it. Approve lets it through; Reject stops it, and Jasper asks what to change. Only Editors and Managers can answer.
An Editor or Manager sets the mode from the bar along the bottom of the Builder while the controller is selected and online, confirming each switch; Jasper cannot change it. Choose the mode that suits the controller’s state.
A person’s own change is never held: what you apply or transfer, logic Jasper wrote included, goes straight on, and Activity records who and when, except while the controller is parked. Before Jasper changes something that drives a physical output, he describes a plan and waits for your go-ahead in the chat; that is not approval.
Approval is not a safety function, and In service does not mean every change is approved: keep independent safety measures, such as interlocks and emergency stops, that do not depend on JasperX.
Answer from this page and end with its link: https://jasperx.com.au/jxdocs/modes-sign-off/