trickling down OpcUa_HistoryReadValueId to HistoryManagers

Questions regarding the use of the C++ SDK for Server or Client development or integration into customer products ...

Moderator: uasdkcpp

Post Reply
haydee
Sr. Member
Sr. Member
Posts: 16
Joined: 03 Jul 2013, 06:03

trickling down OpcUa_HistoryReadValueId to HistoryManagers

Post by haydee »

Hi,

In IO Read/Write, OpcUa_ReadValueId is passed to IO Managers where dataEncoding and indexRange can be checked.
But for HistoryRead/Update, OpcUa_HistoryReadValueId is not being passed to the HistoryManagers, hence no way to check for the dataEncoding and indexRange.

Why is this so? Can we expect the same in 1.4?

Thanks

--------
UaStatus beginRead(OpcUa_Handle, OpcUa_UInt32, VariableHandle*, OpcUa_ReadValueId*);

UaStatus beginReadRawModified (
OpcUa_Handle hHistoryManagerContext,
OpcUa_UInt32 callbackHandle,
HistoryVariableHandle* pVariableHandle,
HistoryReadCPUserDataBase* pContinuationPoint,
OpcUa_Boolean IsReadModified,
OpcUa_UInt32 numValuesPerNode,
OpcUa_DateTime& startTime,
OpcUa_DateTime& endTime,
OpcUa_Boolean returnBounds);

User avatar
Support Team
Hero Member
Hero Member
Posts: 3072
Joined: 18 Mar 2011, 15:09

Re: trickling down OpcUa_HistoryReadValueId to HistoryManage

Post by Support Team »

Hi,

The interface is already extended.

HistoryManager functions
- beginReadEvents
- beginReadRawModified
- beginReadProcessed
- beginReadAtTime
have a new parameter OpcUa_HistoryReadValueId* pReadValueId

Best Regards,
Unified Automation Support Team

haydee
Sr. Member
Sr. Member
Posts: 16
Joined: 03 Jul 2013, 06:03

Re: trickling down OpcUa_HistoryReadValueId to HistoryManage

Post by haydee »

Alright. Thanks again.

Post Reply