Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

From stack v1.04, the SourceTimestamp of the children variables of ServerStatus variable is not equal to ServerTimestamp. Is this behavior expected? #2771

Open
2 of 5 tasks
GhislainPr opened this issue Sep 23, 2024 · 1 comment
Assignees

Comments

@GhislainPr
Copy link

Type of issue

  • Bug
  • Enhancement
  • Compliance
  • Question
  • Help wanted

Current Behavior

From stack v1.05, the SourceTimestamp and ServerTimestamp of the children (CurrentTime for example) variables of ServerStatus variable are not equal.

Expected Behavior

Like in stack v1.04, the SourceTimestamp and ServerTimestamp of the children (CurrentTime for example) variables of ServerStatus variable should be equal.

Steps To Reproduce

No response

Environment

- OS:Windows11
- Environment: VS2022
- Runtime:.NET 4.6.2
- Nuget Version:
- Component:
- Server:Reference Server
- Client: UA Expert

Anything else?

No response

@GhislainPr
Copy link
Author

GhislainPr commented Sep 30, 2024

Hi Martin, thanks a lot for your help !
You can find as attached files the screenshots.
It shows that the SourceTimestamp is updated once and is frozzen after.
v1.04 :
CurrentTime104
v1.05
CurrentTime105
This difference of behavior comes from the difference of the code in this method : ServerStatusValue.OnRead_CurrentTime
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants