output.opc-ua

Opc Ua Output File

oneOf

OpcUa Write Output

OpcUa Write Output

OpcUa Method Output

OpcUa Method Output

OpcUa Write Output

type

object

properties

  • type

type

string

enum

Write

default

Write

  • templateId

The id of the template to use for this file

type

string

  • templateVariables

The variables and their values to be replaced from the template

type

object

additionalProperties

  • variablesFiles

The variables files to use to replace the variables. The first file of the list will take precedence over the following one. Template variables take precedence over the contents of the files.

type

array

items

type

string

  • isTemplateGeneratedByOspComposer

If the value is set to true, manual editing of this file should be avoided, as the composer will override the value in the next generation.

type

boolean

  • linkedDevice

The OPC UA device device.opc-ua ↗️ that this owner will use to get the value.

For example, root.opcua.device1 could be the OnSphere path of the OPC UA device.

type

string

  • nodeId

Node ID is an identifier for a node in an OPC server’s address space. OPC Unified Architecture allows the OPC server to choose one or more types of node IDs for representation of its nodes.

A node Id is not, by itself, a string. It’s primarily an object, containing a namespace and the identifier. Node IDs can be numeric (a 32-bit integer), string, a GUID (globally unique identifier, 128 bits), or opaque (a binary data blob). Depending on the type of Node Id, the node id may have one of the following forms:

  • ns=namespace;i=integer

  • ns=namespace;s=string

  • ns=namespace;g=guid

  • ns=namespace;b=base64string

Here below is a example of how it could look in this configuration file:

"nodeId": {
    "ns": "example",
    "s":"10"
}

But OPC UA also have a string representation that you can use as well to describe a node Id. Meaning you could freely describe the same node id as:

"nodeId": "ns:example;s:10"

Both of theses examples represent the same node id. You are free to use the representation that suits you best

Learn more about OPC UA ↗️.

additionalProperties

False

OpcUa Method Output

type

object

properties

  • type

type

string

enum

Method

default

Method

  • templateId

The id of the template to use for this file

type

string

  • templateVariables

The variables and their values to be replaced from the template

type

object

additionalProperties

  • variablesFiles

The variables files to use to replace the variables. The first file of the list will take precedence over the following one. Template variables take precedence over the contents of the files.

type

array

items

type

string

  • isTemplateGeneratedByOspComposer

If the value is set to true, manual editing of this file should be avoided, as the composer will override the value in the next generation.

type

boolean

  • linkedDevice

The OPC UA device device.opc-ua ↗️ that this owner will use to get the value.

For example, root.opcua.device1 could be the OnSphere path of the OPC UA device.

type

string

  • methodObjectNodeId

Node ID is an identifier for a node in an OPC server’s address space. OPC Unified Architecture allows the OPC server to choose one or more types of node IDs for representation of its nodes.

The method object identifier is the NodeId of the object node that contains the method. This is the node representing the object or component to which the method belongs.

A node Id is not, by itself, a string. It’s primarily an object, containing a namespace and the identifier. Node IDs can be numeric (a 32-bit integer), string, a GUID (globally unique identifier, 128 bits), or opaque (a binary data blob). Depending on the type of Node Id, the node id may have one of the following forms:

  • ns=namespace;i=integer

  • ns=namespace;s=string

  • ns=namespace;g=guid

  • ns=namespace;b=base64string

Here below is a example of how it could look in this configuration file:

"nodeId": {
    "ns": "example",
    "s":"10"
}

But OPC UA also have a string representation that you can use as well to describe a node Id. Meaning you could freely describe the same node id as:

"nodeId": "ns:example;s:10"

Both of theses examples represent the same node id. You are free to use the representation that suits you best

Learn more about OPC UA ↗️.

  • methodNodeId

Node ID is an identifier for a node in an OPC server’s address space. OPC Unified Architecture allows the OPC server to choose one or more types of node IDs for representation of its nodes.

The method identifier is the NodeId of the method node. It uniquely identifies the method within the address space of the OPC UA server.

A node Id is not, by itself, a string. It’s primarily an object, containing a namespace and the identifier. Node IDs can be numeric (a 32-bit integer), string, a GUID (globally unique identifier, 128 bits), or opaque (a binary data blob). Depending on the type of Node Id, the node id may have one of the following forms:

  • ns=namespace;i=integer

  • ns=namespace;s=string

  • ns=namespace;g=guid

  • ns=namespace;b=base64string

Here below is a example of how it could look in this configuration file:

"nodeId": {
    "ns": "example",
    "s":"10"
}

But OPC UA also have a string representation that you can use as well to describe a node Id. Meaning you could freely describe the same node id as:

"nodeId": "ns:example;s:10"

Both of theses examples represent the same node id. You are free to use the representation that suits you best

Learn more about OPC UA ↗️.

additionalProperties

False