@opcua/for-node-red 2.0.0 → 2.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +110 -0
- package/all.js +14173 -14181
- package/package.json +5 -4
- package/resources/endpoint-edition.png +0 -0
- package/resources/endpoint-subscriptions.png +0 -0
- package/resources/endpoint-verification.png +0 -0
- package/resources/node-palette.png +0 -0
- package/resources/nodeid-as-browse-path.png +0 -0
- package/resources/opcu-client2-read.png +0 -0
- package/resources/opcua-client2-monitor.png +0 -0
- package/resources/use-node-browser-to-select-node-id.png +0 -0
package/README.md
ADDED
|
@@ -0,0 +1,110 @@
|
|
|
1
|
+
@opcua/for-node-red (Preview Version)
|
|
2
|
+
|
|
3
|
+
:rotating_light: this product is currently provided as beta version.
|
|
4
|
+
|
|
5
|
+
|
|
6
|
+
This node is the second next generation OPCUA Node for NodeRED build by Sterfive, the company that develops the [NodeOPCUA](https://node-opcua.github.io/) stack.
|
|
7
|
+
|
|
8
|
+
Ir brings the following OPCUA Client features
|
|
9
|
+
- Read
|
|
10
|
+
- Write
|
|
11
|
+
- Browse
|
|
12
|
+
- Monitor
|
|
13
|
+
- Call
|
|
14
|
+
|
|
15
|
+
The community edition works with one connection to one OPCUA server and can hanldes up to 100 simulatenous operation per nodes.
|
|
16
|
+
|
|
17
|
+
The professional edition works with multiple connections to multiple OPCUA servers and have no limitation on the number of simultaneous operations per nodes, exxcept the one imposed by the OPCUA server itself.
|
|
18
|
+
|
|
19
|
+
It has been designed with the following goals in mind:
|
|
20
|
+
|
|
21
|
+
- easy to use, easy to configure; no deep OPCUA knowledge required.
|
|
22
|
+
- provide visual tools to pick up nodeId by browsing the OPCUA server
|
|
23
|
+
- handle nodes address with either nodeId or browse path, or both.
|
|
24
|
+
- works well with complex OPCUA servers, exposing complex data structures (extension objects)
|
|
25
|
+
- arbitraty number of node sharing the same connection
|
|
26
|
+
- support for multiple connections to multiple OPCUA servers.
|
|
27
|
+
- handles automatically transactions optimisation by grouping or splitting operations based on actual OPCUA server capabilities.
|
|
28
|
+
- handles automatically reconnections in case of network failure, in a way that works
|
|
29
|
+
- do not consume Client session unexpectedly on the OPCUA server side.
|
|
30
|
+
- handles automatically OPCUA server certificate management
|
|
31
|
+
|
|
32
|
+
## Getting Started
|
|
33
|
+
|
|
34
|
+
To install the node execute the following command inside the `.node-red`` directory:
|
|
35
|
+
|
|
36
|
+
```console
|
|
37
|
+
npm install @opcua/for-node-red
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
|
|
41
|
+
### Node palette
|
|
42
|
+
|
|
43
|
+
|
|
44
|
+
|
|
45
|
+
|
|
46
|
+
|
|
47
|
+
|
|
48
|
+
### specifying a endpoint connection
|
|
49
|
+
|
|
50
|
+
|
|
51
|
+
|
|
52
|
+
> the `check connection` button allows you to immediatly test your connection parameters and provide useful feedback to help you fix commonly found issues.
|
|
53
|
+
|
|
54
|
+
|
|
55
|
+
Three default subscriptions are automatically created for you:
|
|
56
|
+
Default (1 seconde), Fast (500ms) and Slow(5 secondes). They provide differents publishing intervals for the most common scenarii we usually find in typical IIoT applications. You can customize the parameter or delete or add new subscriptions if you wish.
|
|
57
|
+
Most of the time, only a few subscriptions are needed.
|
|
58
|
+
|
|
59
|
+
Note: The default subscription cannot be deleted, it serves as a mechanism to keep the connection always active with the server by handligng a keepalive packet, and serves as well in the automatic reconnection mechanism, in case of a network outage.
|
|
60
|
+
|
|
61
|
+
|
|
62
|
+
## setting up custom certificate
|
|
63
|
+
|
|
64
|
+
We provide a single PKI location shared with all Client connections.
|
|
65
|
+
The PKI is located in the following folder:
|
|
66
|
+
|
|
67
|
+
- Linux: `~/.node-red/opcua-for-node-red/PKI` folder
|
|
68
|
+
- macOS: `~/Library/Preferences/opcua-for-node-red-nodejs/PKI`
|
|
69
|
+
- Windows: `%APPDATA%\opcua-for-node-red-nodejs\PKI` (for example, `C:\Users\USERNAME\AppData\Roaming\opcua-for-node-red-nodejs\PKI`)
|
|
70
|
+
|
|
71
|
+
|
|
72
|
+
## Read
|
|
73
|
+
|
|
74
|
+
|
|
75
|
+
|
|
76
|
+
**NodeId** : you can specify here a nodeId or a browsePath (originated from the /Objects folder) or both.
|
|
77
|
+
|
|
78
|
+
For instance:
|
|
79
|
+
|
|
80
|
+
- ns=1;s=Temperature
|
|
81
|
+
- /2:MyDevice/1:MyTemperatureSensor/2:ParameterSet/3:Temperature
|
|
82
|
+
- \[/2:MyDevice/1:MyTemperatureSensor/2:ParameterSet/3:Temperature\](ns=1;s=Temperature)
|
|
83
|
+
|
|
84
|
+
|
|
85
|
+
|
|
86
|
+
You can also client on the `...` button to browse the OPCUA server and pick up the nodeId you are interested in.
|
|
87
|
+
|
|
88
|
+
|
|
89
|
+
|
|
90
|
+
|
|
91
|
+
**Note**: NodeID can also be left empty, if you intend to inject the NodeId by the `topic` attribute of an Inject node or with a OpcUa-Item.
|
|
92
|
+
|
|
93
|
+
|
|
94
|
+
|
|
95
|
+
## Write
|
|
96
|
+
|
|
97
|
+
## Call
|
|
98
|
+
|
|
99
|
+
## Monitor Variable
|
|
100
|
+
|
|
101
|
+
|
|
102
|
+
## Monitor Event
|
|
103
|
+
|
|
104
|
+
|
|
105
|
+
## Getting access to the professional edition
|
|
106
|
+
|
|
107
|
+
- send your request to contact@sterfive.com to claim access to the professional edition
|
|
108
|
+
|
|
109
|
+
|
|
110
|
+
|