Validating a design

The three checks

Run validation on the design page, or Deploy in the editor, runs three checks and shows every issue with the node it belongs to:

1. The editor's rules: wiring, required settings, address forms, register maps that overlap, a Condition with no rules.
2. The io-tags document: tag definitions, addresses and duplicates.
3. The runtime itself: the compiled configuration is handed to the real edge runtime binary, whose own validator, every protocol driver's address checks, the route steps' checks (an expression that does not compile, a regex that does not, a cast to a type it does not know), licence limits and topic rules decide. The runtime is asked to judge as a Professional licence would, because that is the licence a device gets.

A design that validates is marked so; editing it makes it a draft again. Validation says nothing about whether a device is reachable: that is proven on site by the runtime's own diagnostics, or beforehand by the Modbus Scanner or against the Modbus Simulator.

Warnings worth reading

• A source not wired to any output: its tags are polled and sent nowhere.
• An output with nothing wired into it.
• A Debounce, Batch, Template or Throttle on the way to a server-style output: left off, because a server holds the present value.
• A converter that forwards writes: any master that reaches its port can change the bus.
• MQTT in and HTTP in on the canvas: not gateway features, left out.