opcua-commander | a opcua client | Networking library

by node-opcua TypeScript Version: 0.37.0 License: MIT

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

kandi X-RAY | opcua-commander Summary

opcua-commander is a TypeScript library typically used in Networking applications. opcua-commander has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

a opcua client with blessed (ncurses)

Support

Quality

Security

License

Reuse

Support

opcua-commander has a low active ecosystem.

It has 154 star(s) with 39 fork(s). There are 15 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 24 have been closed. On average issues are closed in 210 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of opcua-commander is 0.37.0

Quality

opcua-commander has 0 bugs and 0 code smells.

Security

opcua-commander has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

opcua-commander code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

opcua-commander is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

opcua-commander releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

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 opcua-commander

Get all kandi verified functions for this library.

opcua-commander Key Features

No Key Features are available at this moment for opcua-commander.

opcua-commander Examples and Code Snippets

No Code Snippets are available at this moment for opcua-commander.

Community Discussions

Trending Discussions on opcua-commander

Connection configuration loops - Prosys OPC UA Client

QUESTION

Connection configuration loops - Prosys OPC UA Client

Asked 2018-Mar-23 at 09:15

I'm using sample codes from documentation and I'm trying to connect to server using Prosys OPC UA Client. I have tried opcua-commander and integration objects opc ua client and it looks like server works just fine.

Here's what is happening:

After entering endpointUrl, client adds to url -- urn:NodeOPCUA-Server-default.
Client asks to specify security settings.
Client asks to choose server - only 1 option and it's urn:NodeOPCUA-Server-default.

And it goes back to step 2 and 3 over and over.

If I just minimize prosys client without closing configuration after some time I get this info in terminal: Server: closing SESSION new ProsysOpcUaClient Session15 because of timeout = 300000 has expired without a keep alive \x1B[46mchannel = \x1B[49m ::ffff:10.10.13.2 port = 51824

I have tried this project and it works -> node-opcua-htmlpanel. What's missing in sample code then?

After opening debugger I have noticed that each Time I select security settings and hit OK, server_publish_engine reports:

server_publish_engine:179 Cencelling pending PublishRequest with statusCode BadSecureChannelClosed (0x80860000) length = 0

...

ANSWER

Answered 2018-Mar-23 at 08:47

The issue has been handled at the Prosys OPC Forum:

The error happens because the server sends different EndpointDescriptions in GetEndpointsResponse and CreateSessionResponse.

In GetEndpoints, the returned EndpointDescriptions contain TransportProfileUri=http://opcfoundation.org/UA-Profile/Transport/uatcp-uasc-uabinary. In CreateSessionResponse, the corresponding TransportProfileUri is empty.

In principle, the server application is not working according to specification. The part 4 of the OPC UA specification states that “The Server shall return a set of EndpointDescriptions available for the serverUri specified in the request. … The Client shall verify this list with the list from a DiscoveryEndpoint if it used a DiscoveryEndpoint to fetch the EndpointDescriptions. It is recommended that Servers only include the server.applicationUri, endpointUrl, securityMode, securityPolicyUri, userIdentityTokens, transportProfileUri and securityLevel with all other parameters set to null. Only the recommended parameters shall be verified by the client.”

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

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

Vulnerabilities

No vulnerabilities reported

Install opcua-commander

if you have EACCES error on linux,.

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: