node-opcua-htmlpanel | small HTML panel to display a OPCUA | Socket library

by node-opcua JavaScript Version: v0.0.13 License: MIT

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

kandi X-RAY | node-opcua-htmlpanel Summary

node-opcua-htmlpanel is a JavaScript library typically used in Networking, Socket, Nodejs, Express.js applications. node-opcua-htmlpanel has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

small HTML panel to display a OPCUA monitored variable based on node, express, socket.io and node-opcua. ![alt text] "…"). This steps describe how you can install and test the application on a linux box, such as ubuntu. The application is also working on Windows, instructions left to the reader to adapt. Now visit ‘``on your web browser.

Support

Quality

Security

License

Reuse

Support

node-opcua-htmlpanel has a low active ecosystem.

It has 42 star(s) with 22 fork(s). There are 5 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 9 have been closed. On average issues are closed in 1092 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of node-opcua-htmlpanel is v0.0.13

Quality

node-opcua-htmlpanel has 0 bugs and 0 code smells.

Security

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

node-opcua-htmlpanel code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

node-opcua-htmlpanel 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

node-opcua-htmlpanel releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

It has 82 lines of code, 0 functions and 6 files.

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

Top functions reviewed by kandi - BETA

kandi has reviewed node-opcua-htmlpanel and discovered the below as its top functions. This is intended to give you an instant insight into node-opcua-htmlpanel implemented functionality, and help decide if they suit your requirements.

Create an IO client .
Iterate over the circle
Stop the client .
find a truth condition
internal helper function
variable type
get y value by type
match filter function
Higher order function .
top - left - right

Get all kandi verified functions for this library.

node-opcua-htmlpanel Key Features

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

node-opcua-htmlpanel Examples and Code Snippets

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

Community Discussions

Trending Discussions on node-opcua-htmlpanel

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 node-opcua-htmlpanel

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: