8.3.5 pulled, 8.3.6 Emergency Release

Ignition
1

Ignition 8.3.5 has been removed from our website and will be replaced with 8.3.6 soon. A change was made to prevent inactive redundant gateways from writing tag history, but in certain configurations that fix can cause gateways to silently lose tag configuration details on every restart, leading to incorrect historical trends. At this time we have decided to pull the release, fix the new issue, then re-release as 8.3.6 early next week.

3

Unsure if this is related - a new error has appeared on a gateway which I updated from 8.3.2 to 8.3.5. I'm unable to update the History Datasource for a remote tag provider. I'm getting an error: Failed to fetch options: TypeError: r.t2.includes is not a function, and I'm unable to save a valid configuration from the UI.

image
image405×103 4.65 KB

However, I am able to write the correct settings using the API (without allowInvalidReferences=true on the Modify Tag Providers endpoint).

4

While not the primary cause of the release being pulled, it was also something identified and will be resolved as part of 8.3.6.

5

Hi Sreis,

I wonder if 8.3.6 release will have the S&F settings at the Edge Gateway? Those settings got disappear on 8.3.5 release. Also the Real Tag Provider at the Standard Gateway does have an error. Regards, Luz Aguilar.

6

The Store & Forward metrics page was in fact removed in 8.3.3 as it was misleading; Edge doesn't leverage Store & Forward for its local data storage. You can find more information on this topic here: Store and Forward Engine on Storage only - #3 by Kurt.Larson

We do have an internal ticket to address the limitation for viewing Edge Historian capacity and aiming to have that released within the next 1-2 releases.

7

When you say "lose tag configuration details on every restart" are you talking about all tag configuration details such as data type and value too? or just the tag configuration details related to tag history?

8

History and tag configuration settings were being persisted properly in 8.3.5.

The issue was a setting that determines the manner historical values are queried was getting flip-flopped from Direct to Analog depending on when a tag was started on the Gateway if both of the following were True:

  1. Your tag was a Float or Double datatype
  2. The Historical Deadband Style was set to Discrete.

For redundant Gateways, it was more evident than independent Gateways as new rows were being added to the sqlth_te table on each failover.