Raylux 0.27.0: historian trend aggregation
Long trends stop dragging their whole history across the network, plus a batch of driver and interface fixes. Wide trend windows are now summarised inside the database, so a long trend never leaves it as raw rows.
· Pre-release · All releases
Long trends stop dragging their whole history across the network, plus a batch of driver and interface fixes.
Trend aggregation
Wide trend windows are now summarised inside the database, so a long trend never leaves it as raw rows. A chart measures its own width and asks for that many points, keeping a minimum/maximum envelope by default so a spike survives being summarised instead of being averaged away.
Measured against the case this was built for: a 30-day trend on a tag logged four times a second — 10,368,000 readings — returns 900 points instead of all of them.
Found and fixed along the way: the trend query had never actually reached a live gateway, in three independent ways.
Also
- Data-quality checks on incoming values: range, rate-of-change and stuck-value detection.
- Tag access defaults to open unless a tag is explicitly restricted, matching the stated security model.
- Allen-Bradley: fixed-length string structures, 32- and 64-bit floats read correctly, structure names shown instead of an internal id, and one bad tag no longer stalls a whole device's polling.
- Studio: importing tags from a device no longer forces the PLC's own folder structure on you, and folders can be ticked as a group.
- Buttons can write back in one-shot, momentary and toggle modes.
Next step
Run the latest release.
Every 1.0 release installs over the one before it and keeps your projects, tags, history and users. Follow new ones in a feed reader, no email needed.