Standard Component
Avoid choking networks and hard drives with meaningless data.
Most other SCADA software products require you to periodically offload older Historical data to a backup device. While this helps to avoid filling the hard drive that hosts the Historian, it prevents users from benefitting from the full view of their application’s history in their trends and reports. VTScada allows you to sidestep this this problem.
First, configure your polling Driver tags with a reasonable polling interval. Not every data point needs to be polled every millisecond. Choose a rate for each I/O tag that makes sense for how its data will be used.
Second, VTScada allows you to easily set deadbands to avoid filling Historians with irrelevant data. For example, wind ripples on the surface of a pond can produce minor changes in the value of the pond level. There are two kinds of deadband.
Analog I/O tag Deadbands improve performance by not logging changes below a chosen threshold to the Historian.
PLC Driver Deadbands – VTScada also uses deadbands at the driver level to prevent insignificant changes from loading down the CPU performance and using network bandwidth.