Difference between revisions of "Edge Gateway OPC UA Adapter"
(→Noting OPC UA url) |
|||
| Line 58: | Line 58: | ||
== Noting OPC UA url == | == Noting OPC UA url == | ||
| + | |||
| + | [[File:Ua-2-new.png|800x800px]] | ||
== Adding Edge certificate to the trusted list == | == Adding Edge certificate to the trusted list == | ||
Latest revision as of 07:52, 19 July 2018
Edge Gateway Home > OPC UA Adapter
Contents
OPC UA Protocol Connection
| server_url | String | URL address of the OPC UA server e.g. opc.tcp://localhost:12686/example |
| is_secure | Boolean | Signifies whether the connection to OPC UA server is secure or not. If it is true then cert_alias option will be used |
| cert_alias | String | Alias of the client certificate used for secure communication with OpcUA server. The private and public key of the certificate in .pem format has to be
updated via Settings→Device SSL Certificate. The alias mentioned for certificate must match with the one specified in config-json. A default alias named opcua is available, its certificate can be found at {install_location}\aliot-4.0\data\keystore\opcua.pem |
| discover_endpoints | Boolean | true value denotes that the connection endpoints will be discovered from the server_url and endpoint matching with security policy will be used for connection.
false value means the endpoint will be the same as server_url. Default value is true. |
| security_policy_uri | String | Possible values are http://opcfoundation.org/UA/SecurityPolicy#None, http://opcfoundation.org/UA/SecurityPolicy#Basic128Rsa15, http://opcfoundation.org/UA/SecurityPolicy#Basic256,
http://opcfoundation.org/UA/SecurityPolicy#Basic256Sha256. The uri ending with None means no security policy is applied. Default value is Basic128Rsa15 uri. |
OPC UA Read Tag
| tag_id | String | Unique tag id defined in the context of the current thing_config. This is used further in metric_mappings or derived_tags or scan_tag_ids or monitor_tag_ids to refer to this tag value. |
| node_id | String | The OPC UA tag definition which is present at OPC UA server e.g. ns=2;s=Channel1.Machine1.Tag1 or ns=0;i=2259. The format for tag is as follows:
ns=<namespace id>;s=<string identifier of the tag> OR ns=<namespace id>;i=<integer identifier of the tag> For example: ns=2;s=Channel1.Machine1.Tag1 |
OPC UA Write Tag
| tag_id | String | Unique tag id defined in the context of the current thing_config. This is used in Datonis instruction json to address this OPC UA tag. |
| node_id | String | The OPC UA tag definition which is present at OPC UA server e.g. ns=2;s=Channel1.Machine1.Tag1 or ns=0;i=2259. This tag must be writable i.e. Client Access property must be set to Read/Write. The format for tag is as follows:
ns=<namespace id>;s=<string identifier of the tag> OR ns=<namespace id>;i=<integer identifier of the tag> For example: ns=2;s=Channel1.Machine1.Tag1 |
Launching OPC UA configuration screen
Noting OPC UA url
Adding Edge certificate to the trusted list
On configuring the Datonis Edge Gateway, it will error out with a certificate error: ServiceResultException: Bad_CertificateInvalid (0x80120000) "The certificate provided as a parameter is not valid.
In the OPC UA configuration window, select the Trusted Clients tab, you will find a new entry for 'OPC UA Adapter'. Right click it and select “Trust”. Disable and enable Gateway again.
