View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000363010000-004: ServicesSpecpublic2016-12-06 17:292020-03-18 08:40
ReporterJim Luth Assigned ToMatthias Damm  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0003630: Handling of NaN
Description

In 5.2.2.3 the statement was added:
... This means a NaN value for a Variable always produces a DataChange each time the SamplingInterval elapses.

I do not understand why NaN shall always produce DataChange notification.
Once notified is enough. Obviously the normal operators "==" / "<" / ">" cannot be used, some special handling has to be implemented.

What shall happen for SamplingRate 0?
Automatically fill up the monitored item queue?
Already queued values can be lost!

TagsNo tags attached.
Commit Version
Fix Due Date

Relationships

related to 0003475 closedrandyarmstrong 10000-006: Mappings Handling of NaN 
related to 0005534 closedSebastian Allmendinger Compliance Test Tool (CTT) Unified Architecture Data Access / Data Access AnalogItemType / 023: CTT expects DataChange Notification for different NaN Values 

Activities

Thomas Merk

2016-12-06 17:29

reporter   ~0007438

Issue was meant for Specification Part 6.
Accidentially added here - plese move it.

Jim Luth

2016-12-06 17:29

administrator   ~0007439

Clarify that Sample Rate of 0 - means exception reporting so only the change of state in and out of NAN would cause the variable to report. Also allow similar "state change" testing for other Sample Rates.

randyarmstrong

2016-12-06 17:29

administrator   ~0007440

Added errata and update to Part 6 1.04 DRAFT 09.

randyarmstrong

2016-12-06 17:29

administrator   ~0007441

Discussed in call on 12/6.

Agree to remove all mention from sampling from Part 6 and add it to Part 4.
The text is here:

This means a NaN value for a Variable always produces a DataChange each time the SamplingInterval elapses if the standard logic is used. Servers shall check for NaN and only produce a DataChange when the value enters or leaves the NaN state.

Jim Luth

2016-12-06 17:29

administrator   ~0007442

Will require a 1.03 Errata.

Jim Luth

2016-12-06 17:29

administrator   ~0007443

Need to clone to Part 4

Matthias Damm

2016-12-09 20:23

developer   ~0007484

Added following clarification on DataChangeFilter::trigger STATUS_VALUE_1:
For floating point values a Server shall check for NaN and only report a Notification when the value enters or leaves the NaN state.

Made changes in document version OPC UA Part 4 - Services 1.04 Specification Draft 02.docx

Jim Luth

2016-12-15 23:04

administrator   ~0007597

Agreed to changes in meeting.

Issue History

Date Modified Username Field Change
2016-12-06 17:29 Jim Luth New Issue
2016-12-06 17:29 Jim Luth Status new => assigned
2016-12-06 17:29 Jim Luth Assigned To => randyarmstrong
2016-12-06 17:29 Jim Luth Issue generated from: 0003475
2016-12-06 17:29 Jim Luth Relationship added related to 0003475
2016-12-06 17:30 Jim Luth Assigned To randyarmstrong => Matthias Damm
2016-12-06 17:30 Jim Luth Project 10000-006: Mappings => 10000-004: Services
2016-12-09 20:23 Matthias Damm Note Added: 0007484
2016-12-09 20:23 Matthias Damm Status assigned => resolved
2016-12-09 20:23 Matthias Damm Resolution open => fixed
2016-12-15 23:04 Jim Luth Note Added: 0007597
2016-12-15 23:04 Jim Luth Status resolved => closed
2016-12-15 23:04 Jim Luth Fixed in Version => 1.04
2020-03-18 08:40 AlexanderAllmendinger Relationship added related to 0005534