Issue with conformance tool on OPC UA Server 2

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

Moderator: uasdknet

Post Reply
stephenTissot
Full Member
Full Member
Posts: 9
Joined: 24 Jan 2022, 17:13

Issue with conformance tool on OPC UA Server 2

Post by stephenTissot »

Hello again.
Still some issues with the CTT tool :
- Base information test
- Base info diagnostics, test 019 (Test sessions are added SessionDiagnosticsSummary) Result is red, expected 6 but got 7
- Base info ResendData Method, test 002 (Verify DataChangeNotifications ...)
, result is red, expected 1 but got 0
- Monitor Item Services
- Monitor basic, test Err-041 (Specify 2d IndexRange "2:3,1:2" on a single dimension Array. Test was run on a string array :
string[] stringArray = { "00000", "00001", "00002", "00003", "00004", "00005", "00006", "00007", "00008", "00009" };
Result is red, Received: Good -2143879168 (??)
For index requests, I am just using the default ApplyIndexRangeAndEncoding method

Does someone have any idea ?

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

Re: Issue with conformance tool on OPC UA Server 2

Post by Support Team »

Hi,

the .NET SDK was tested for compliance years ago. Best chance you have, is to test with latest CTT and latest .NET SDK, however there is no guaratee that every single test will succeed.
Reason:
1) CTT is permanently creating new tests cases
2) CTT is permanently updating, changing existing test cases
3) .NET SDK continously gets new features und updates
4) .NET SDK is certified only as a snapshot, approx. every 3 years
Procedure:
Always first verification is to run the CTT individual test case "alone", so that there are no interferences with previous running test cases. If you still have errors you should switch back to the original DemoServer as delivered with the SDK, with that you can verify if the issue is in your own code, or was already in the original delivery. In the Demoserver you find an extra address space "CTT" which contains all the nodes you can use for test configuration of the test tool. If you than still have errors, you need to analyze those issues with the CTT developers first (most common issue is statuscode mismatch), which from a compliance perspective is a bug, but from a SDK product perspective is low priority error (no major impact on functionality). All bugs found in the SDK must be reported via the customer support form on our website, and will be fixed according to priority (and backward compatibility).
Best regards
Unified Automation Support Team

Post Reply