HotLoop Flow 2.11.0 release notes
HotLoop Flow 2.11.0 makes FlowLab easier to build in and safer to command equipment from: a real editor for case structures, a way to cut a selection out into a sub-diagram, a layout that keeps wires off nodes, named wires, zoom to 400 percent, symbols on every diagram node, a node that sets panel objects by name, and a node that writes to equipment only through HotLoop’s write gate.
What’s new
Section titled “What’s new”- A case structure editor. A case structure’s cases are rows of a case name and a diagram picker, with a second picker for the default case, instead of a JSON box. The property that names the diagram a loop or a sub-diagram runs is a picker too. The pickers list the FlowLab diagrams of the flow file. A name written by hand in an older flow file shows as that tab and saves as its id, and the stored values are the same JSON as before.
- Selection to sub-diagram. With nodes selected on a diagram, the diagram bar’s Selection to sub-diagram asks for a name and cuts them out into a tab of their own, with a sub-diagram node where they were. The inputs and outputs are worked out from the wires that cross the edge of the selection, it is one undoable edit, and nothing is saved until you deploy.
- Tidy layout. The tab bar’s Tidy layout lays a diagram out in columns so data reads left to right, gives wires that skip columns a lane, and moves a node that is in the way of a wire’s drawn curve. It keeps the block’s top left corner and is one undoable edit. On a 30 node test diagram no wire runs through a node.
- Wire names. A wire of a diagram is named at its middle by the output it comes from, beside its type when one is declared. Hovering still shows the last value it carried. Message flows are drawn as before.
- Zoom to 400 percent. The canvas zooms from 5 to 400 percent about the pointer.
- Symbols. Every FlowLab node type is drawn with a symbol of our own at the middle of its body, beside its text label. They are plain strokes drawn for Flow, not an icon font or anyone’s artwork.
- Set a panel object by name.
dia-panel-setchangesvisible,enabled,color,label,minormaxof a control or an indicator while the diagram runs, by its label or id. A disabled control refuses what an operator sets, a hidden object is not drawn, and the panel an operator has open follows. A name that matches no object, or more than one, is a problem at deploy when it is typed on the node, and an error on the wire when it is wired in. A run starts from the panel as it was designed. - The diagram write gate.
dia-hotloop-writewrites its value to a tag in HotLoop (device/tag) through HotLoop’s write gate, which decides that writes are switched on, that the tag is armed and that the value is in range. HotLoop records every attempt, refused or not, with the reasonflow:<diagram>/<node id>. A refusal is an error on the node’s error wire with the gate’s own reason (error code 5006), and so is a HotLoop that cannot be reached; in both cases the write does not happen. The node refuses to deploy with no HotLoop selected, so it is never a way around the gate.
What changed
Section titled “What changed”- The gate’s scope, as shipped. Flow’s raw serial and instrument nodes (
dia-serial-write,dia-instr-queryand the rest) are not gated yet. They talk to bench instruments such as meters, supplies and loads, which have no tag in HotLoop, sodia-hotloop-writedoes not cover them. A diagram that commands equipment on a plant’s network does it withdia-hotloop-write, and until the next release a diagram can still drive an instrument directly. A per-instrument write switch, off by default, comes next: no diagram will drive a supply, a hipot or any instrument output until someone with the right permission turns that instrument’s writes on, and reads will stay open. - Nothing else behaves differently from 2.10.2. Flow files from 2.10.2 load and save byte for byte.
New settings
Section titled “New settings”dia-hotloop-write takes a hotloop connection and a tag. dia-panel-set takes a target and a property. The case editor and the diagram pickers store the same properties as before.
Upgrade
Section titled “Upgrade”A plain helm upgrade to the 2.11.0 image and chart, or the new tag in your Quadlet unit. Nothing happens on first start and nothing needs migrating. This release is amd64 first, with the arm64 build following in 2.11.1, so an arm64 box stays on 2.10.2 until then.
Image: ghcr.io/hotloop-io/hotloop-flow:2.11.0, linux/amd64 first, with arm64 following in 2.11.1. Chart: https://hotloop.io/hotloop-flow/. The README at this tag has the rest, with pictures: https://github.com/HotLoop-io/hotloop-flow/blob/v2.11.0/README.md