OPC UA
FactoryTalk Optix Studio
is compliant with the OPC UA (OPC Unified Architecture) standard and can communicate with any OPC UA client or server.
TIP:
Devices with a configured
FTOptixApplication
can operate as an OPC UA client or server.Use these components to develop your application logic:
- OPC UA nodes
- OPC UA server object
- OPC UA client objects
OPC UA nodes
FactoryTalk Optix Studio
enables importing nodes from the OPC UA server.OPC UA server
Publishes the nodes of the project information model at runtime. The server publishes all project nodes by default. You can select which nodes to publish to the assigned users.
IMPORTANT:
You can configure a single OPC UA server object in a project.
The server object enables an OPC UA client to:
- Read from the server (listen to events)
- Write to the server (invoke methods)
OPC UA client
The OPC UA client object enables the communication with the OPC UA server.
TIP:
You can configure unlimited OPC UA client objects in a project.
The client accesses nodes published by the server to:
- Read from the server (listen to events)
- Write to the server (invoke methods)
You can specify the nodes to the server to import at design time or at runtime. For example, an OPC UA client can read specific object variables or listen to events generated by alarms.
Endpoint URL
In
FactoryTalk Optix Studio
, the predefined endpoint URL is opc.tcp://localhost:59100
The URL of an endpoint is composed of these elements:
- Communications protocol:opc.tcp
- Network address, expressed in one of the following modes:
- localhost
- A keyword that expresses local address.
- Hostname
- The name of the network device on which the server is hosted.
- IP address
- The IP address of the network device on which the server is hosted.TIP: Unless there are specific requirements, Rockwell Automation recommends using thelocalhostkeyword.
- port
Provide Feedback