FYI Advanced Modbus with Persistance Bug: Point value and last state being logged to history

[geoffpatton]

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.

Time	Value	State	Quality	Reason	Status	Suppression Type
8/5/2021 11:59:21.675 AM	0	OFF	Good	Current Data		None
8/5/2021 2:10:23.018 PM	1	ON	Good	Current Data		None

GS2020 has 30 extra records with polling set to every second.

Time	Value	State	Quality	Reason	Status	Suppression Type
8/5/2021 11:59:21.675 AM	0	OFF	Good	Current Data		None
8/5/2021 2:09:52.549 PM	1	OFF	Good	Current Data		None
8/5/2021 2:09:53.565 PM	1	OFF	Good	Current Data		None
8/5/2021 2:09:54.580 PM	1	OFF	Good	Current Data		None
8/5/2021 2:09:55.596 PM	1	OFF	Good	Current Data		None
8/5/2021 2:09:56.612 PM	1	OFF	Good	Current Data		None
8/5/2021 2:09:57.627 PM	1	OFF	Good	Current Data		None
8/5/2021 2:09:58.643 PM	1	OFF	Good	Current Data		None
8/5/2021 2:09:59.658 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:00.674 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:01.690 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:02.705 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:03.721 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:04.737 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:05.752 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:06.783 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:07.783 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:08.799 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:09.815 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:10.830 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:11.846 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:12.877 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:13.893 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:14.893 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:15.909 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:16.924 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:17.940 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:18.956 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:19.971 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:20.987 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:22.003 PM	1	OFF	Good	Current Data		None
8/5/2021 2:10:23.018 PM	1	ON	Good	Current Data		None

[sbeadle]

Thanks Geoff, we expect this to be resolved in the September updates.

[geoffpatton]

@sbeadle 

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.

Time	Value	State	Quality	Reason	Status	Suppression Type
10/8/2021 10:25	1	State 1	Good	Current Data		None
10/8/2021 10:25	0	State 1	Good	Current Data		None
10/8/2021 10:09	1	State 1	Good	Current Data		None
10/8/2021 10:09	1	State 0	Good	Current Data		None
10/8/2021 10:06	0	State 0	Good	Current Data		None
10/8/2021 10:06	0	State 1	Good	Current Data		None
10/8/2021 10:05	1	State 1	Good	Current Data		None