You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Reference Server offers a node with node id ns=3;i=2808 with browse path:
Objects -> Data -> Dynamic -> Scalar -> Int32Value
which has the attribute 'Historizing' set to true, but which does not allow access to historical data. When you try to look at the history in UAExpert in the History Trend View the error "Added item does not support historizing" comes up.
The node is configured as historizing in the TestDataNodeManager.cs file in the Quickstarts.Servers project,
line 198ff (method CreateAddressSpace).
Expected Behavior
The expected behaviour is that the node is recognized as history enabled by a client.
Just a guess why it does not work: the HistoricalAccessServer in the Samples solution provides history enabled nodes. If you look at the source code you will note that the nodes are created as ArchiveItems/ArchiveItemStates, while, in the reference server, they aare created as ScalarValues/ScalarValueObjectStates.
The text was updated successfully, but these errors were encountered:
ThomasNehring
changed the title
Node in ReferenceServer is tagged as historizing, but does allow historical access
Node in ReferenceServer is tagged as historizing, but does not allow historical access
Feb 14, 2024
Type of issue
Current Behavior
The Reference Server offers a node with node id ns=3;i=2808 with browse path:
Objects -> Data -> Dynamic -> Scalar -> Int32Value
which has the attribute 'Historizing' set to true, but which does not allow access to historical data. When you try to look at the history in UAExpert in the History Trend View the error "Added item does not support historizing" comes up.
The node is configured as historizing in the TestDataNodeManager.cs file in the Quickstarts.Servers project,
line 198ff (method CreateAddressSpace).
Expected Behavior
The expected behaviour is that the node is recognized as history enabled by a client.
Steps To Reproduce
No response
Environment
Anything else?
Just a guess why it does not work: the HistoricalAccessServer in the Samples solution provides history enabled nodes. If you look at the source code you will note that the nodes are created as ArchiveItems/ArchiveItemStates, while, in the reference server, they aare created as ScalarValues/ScalarValueObjectStates.
The text was updated successfully, but these errors were encountered: