Skip to content
This repository has been archived by the owner on Sep 1, 2022. It is now read-only.

DNPTime.quality always INVALID for g2v2 event #377

Closed
sidhoda opened this issue May 26, 2020 · 3 comments
Closed

DNPTime.quality always INVALID for g2v2 event #377

sidhoda opened this issue May 26, 2020 · 3 comments

Comments

@sidhoda
Copy link
Contributor

sidhoda commented May 26, 2020

When sending a g2v2 unsolicited event to a opendnp3 master (v3.0.1), TypedMeasurement.time.quality is always INVALID whereas info.tsquality is SYNCHRONIZED. The expected behaviour is that DNPTime.quality and HeaderInfo.tsquality are always in sync.
@jadamcrain
Copy link
Member

After spirited debate, we've decided how to resolve this discrepancy. This will result in 3.0.2 being released this week.

@jadamcrain
Copy link
Member

Have a look at this PR @sidhoda:

#379

@jadamcrain
Copy link
Member

Resolved in #379

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jadamcrain @sidhoda