UA-.NET-Legacy | OPC Foundation Unified Architecture .NET Reference | DevOps library

by OPCFoundation C# Version: 1.03.342 License: No License

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | UA-.NET-Legacy Summary

UA-.NET-Legacy is a C# library typically used in Devops, Framework applications. UA-.NET-Legacy has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

OPC Foundation Unified Architecture .NET Reference Implementations

Support

Quality

Security

License

Reuse

Support

UA-.NET-Legacy has a low active ecosystem.

It has 315 star(s) with 268 fork(s). There are 80 watchers for this library.

It had no major release in the last 12 months.

There are 56 open issues and 83 have been closed. On average issues are closed in 113 days. There are 10 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of UA-.NET-Legacy is 1.03.342

Quality

UA-.NET-Legacy has 0 bugs and 0 code smells.

Security

UA-.NET-Legacy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

UA-.NET-Legacy code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

UA-.NET-Legacy does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

UA-.NET-Legacy releases are available to install and integrate.

It has 868422 lines of code, 0 functions and 2172 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of UA-.NET-Legacy

Get all kandi verified functions for this library.

UA-.NET-Legacy Key Features

No Key Features are available at this moment for UA-.NET-Legacy.

UA-.NET-Legacy Examples and Code Snippets

No Code Snippets are available at this moment for UA-.NET-Legacy.

Community Discussions

Trending Discussions on UA-.NET-Legacy

TranslateBrowsePathsToNodeIds() OPC-UA method with Simatic ProcessHistorian

QUESTION

TranslateBrowsePathsToNodeIds() OPC-UA method with Simatic ProcessHistorian

Asked 2018-Feb-09 at 12:57

I'm trying to call TranslateBrowsePathsToNodeIds method (defined on View Service Set of OPC-UA standard) using OPC-UA client against Simatic ProcessHistorian (Simatic PCS 7 version 8.1).

When I browse the server with Sample Client from UA-.NET I can see two nodes under Objects root:

Server
Process Historian {7a3ea44f-b495-414c-84f9-7498095d43bd}

For Server node the method works fine but I can't figure out a way how to get nodes down the tree starting from Process Historian {7a3ea44f-b495-414c-84f9-7498095d43bd} (which is actually the data model).

The code looks like this (C#):

...

ANSWER

Answered 2018-Feb-06 at 03:21

I found that RelativePath.Parse follows the string format found in Part 4 - Services Annex A.2.

Try prefixing with forward slash, eg "/3:Process Historian {7a3ea44f-b495-414c-84f9-7498095d43bd}"

ps. i see that if you leave off the "3:" the server will assume you meant "0:"

pps. Use the version of Parse with only arguments string, ITypeTable. You don't need to translate Namespaces in this case.

ppps: Most browse names i see have no whitespace. I wonder why?

Try reading the server object?

Source https://stackoverflow.com/questions/48565658

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install UA-.NET-Legacy

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: