Endpoint control
The Endpoint Control node (OpcUa-Endpoint-Control) changes the OPC UA connection of a running flow. You do not need to deploy again. The help of the node in the Node-RED editor gives the quick start. These pages give the details.
- Send values in a message
- The password and the certificate
- Advanced settings
- Safety
- Errors
- Connection events
- What the status and the result contain
Words used on these pages
| Word | Meaning |
|---|---|
| endpoint | the OpcUa-Endpoint2 node: it holds the connection settings. The field endpoint in a message is the server address, not this node |
| server address | the address of the OPC UA server, for example opc.tcp://line-b:4840 |
| login | how the node logs in: Anonymous, user name and password, or certificate |
| session | the open connection to a server |
| message | the Node-RED message that comes into the node |
| error message | one entry of the list findings on output 2: { field, message } |
| Same as the endpoint | the value of the endpoint is used |
| in use | the value that the connection uses now |
| switch | the change from the old settings to the new settings, when you send Connect or Reset |
| revision | a counter that grows each time the settings change |
| node | a Node-RED node, unless the text says OPC UA node |
| PEM | a certificate or a key as text, with lines such as -----BEGIN CERTIFICATE----- |
| thumbprint | a short code that identifies a certificate |
| PKI | the folder of the trusted certificates of this Node-RED instance |
| namespace, alias | a namespace is a group of OPC UA node ids. An alias is a short name for a namespace, for example plant |
| GetEndpoints | the question to the server: which security modes, policies and logins do you offer? |
The dialog in detail
The dialog shows only what the action uses.
- Name: when it is empty, the node has the name of its action and its endpoint. Examples:
connect · Plant 1andmsg.action · Plant 1. The Name field shows that text. - Endpoint: the OpcUa-Endpoint2 to control. The other fields are inactive until you choose one.
- Action: one field with a list: Connect (
connect), Check (no change) (validate), Reset to the endpoint settings (reset), Disconnect (disconnect), Get the settings (get), Get the status (status) and Let the message decide (msg).- A new node starts with Connect.
- A node that was saved without an action does what Let the message decide does.
- With Let the message decide, a text field appears in the Action field. It names the property of the message that holds the action,
actionby default.
- Server address, Security mode and Security policy: for Connect, Check and Let the message decide. An empty field, or "Same as the endpoint", uses the value of the endpoint. The policy shows only when the mode is not None.
- Login: for the same actions. The choices are Same as the endpoint, Anonymous (no login), User name and password, and Certificate. User name shows for User name and password.
- Allowed servers, under More options: see Safety.
- Show the message this node sends: a read-only box with a copy button. It shows a message that gives the same result. A secret shows as
msg.... For a fixed action,msg.actionis a comment, because the node ignores it.
A sentence under the Action tells what the node does with the values of the dialog.
Reset shows a sentence and the licence line. Disconnect, Get the settings and Get the status show a sentence. A field that the dialog hides keeps its value. The node does not check this field, and it cannot stop a deploy.
The canvas label shows name · msg.action, or name · connect in italics for a fixed action. Without a name, it shows msg.action · endpoint name or connect · endpoint name.