UT_REPORT — Report by exception (IoT / SCADA)

Decides when a value is worth sending: it has changed by more than a deadband,
its quality has changed, a heartbeat time has passed with no change, or you force it.
It also enforces a minimum interval so a noisy signal can't flood a cellular link.
Use Report to trigger an MQTT/BeeBus publish. For a whole list of values in one
block, use UT_REPORT_ARRAY.

Pins

Record UT_REPORT_DATA

How it works

• A change or Force that arrives during minInterval isn't lost: it's reported as soon
  as the interval ends, with the value at that moment, so the final value is always sent.
  A held-back Force wins over a change (Reason FORCED).
• In that is not a number (NaN, infinity) is sent once as quality UT_Q_BAD with the
  last good value; the next real number is sent with Quality again.
• A held Force reports once; a Force held through Enable off doesn't report.
• Nothing is kept over a power cut; after one the block reports FIRST again. The
  block's memory is in the record (the mem fields), but it starts fresh on the
  block's first scan, so a record declared RETAIN (to keep its settings) reports
  FIRST after a power cut too.
• resolution rounds to the nearest step (2.26 → 2.3 at 0.1; 1234.4 → 1230 at 10).
  A value of more than 10¹⁵ steps is sent as it is.
• Send the value with Data.quality, and bind the SCADA metric to Value (or
  lastValue), the value held from the report, not to In.

Using it

LevelRpt(In := WetWell.Value, Quality := WetWell.Quality, Data := LevelRptCfg);
IF LevelRpt.Report THEN
  (* publish LevelRpt.Value with LevelRptCfg.quality *)
END_IF;