Historical Access #1559
johannwesely
started this conversation in
General
Replies: 3 comments 1 reply
-
Hmm, currently operation level Bad_HistoryOperationUnsupported is returned. I'm not sure it's required that the service level return Bad_ServiceUnsupported just because there happen to be no nodes that are currently history-enabled. |
Beta Was this translation helpful? Give feedback.
0 replies
-
S. Allmendiger said here : "Either nodes must be present to test the services or ServiceLevel BAD_SERVICE_UNSUPPORTED must be thrown." |
Beta Was this translation helpful? Give feedback.
1 reply
-
For now, something like this: server.addServiceSet(
"",
new DefaultAttributeServiceSet(server) {
@Override
public HistoryReadResponse onHistoryRead(
ServiceRequestContext context, HistoryReadRequest request) throws UaException {
throw new UaException(StatusCodes.Bad_ServiceUnsupported);
}
@Override
public HistoryUpdateResponse onHistoryUpdate(
ServiceRequestContext context, HistoryUpdateRequest request) throws UaException {
throw new UaException(StatusCodes.Bad_ServiceUnsupported);
}
}); |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
here is Another Point from the certification process:
"Historical Access:
Service calls do not return Bad_ServiceUnsupported. No node with Historizing == True or AccessLevel == History Read/Write could be found within the address space of the server. "
So we have actually no nodes with historical Access do i need to deactivate this Service somehow to avoid the error?
Greetings Johann
Beta Was this translation helpful? Give feedback.
All reactions