FYI Advanced Modbus with Persistance Bug: Point value and last state being logged to history
This is just an FYI. It is in the Developers pipeline to fix, and I do not know if this bug exist in other versions then GS2020, or affects any other point types, or drivers.
We discovered that after upgrading from CS2015R1 to GS2020 that the Modbus digital points with persistence enabled the Historic logging behavior changed.
In the 2015 version the state and value change were logged after the persistence time had passed.
In the 2020 version it started logging when a new value came in, it logs the new value and the previous state for every poll until the persistence had been exceeded, or if the value returned to the previous value. It would then log the final value and state..
The configuration of the states is 0 = OFF and 1 = ON (Alarm) persistence is INTO State 30s for both states.
CS2015R1 was like this: The current value was logged 8/5/2021 11:59:21.675 AM, a value change reported at 8/5/2021 2:09:52.549 PM, and Logged into history at 8/5/2021 2:10:23.018 PM after the persistence.
8/5/2021 11:59:21.675 AM
8/5/2021 2:10:23.018 PM
GS2020 has 30 extra records with polling set to every second.
There is a fix for it, but it still does not record history as it previously did.
It now only records one record with the value changed but the state not changed.
While I can see this as useful in some situations it is not for my client. They do not want or need a record unless the persistence has been exceeded.All the entries I put in bold would not be recorded the way it worked in the 2015 version.