The OpcUaHandling library provides you the function blocks to implement the OPC UA client functionality in your application. The OPC UA client itself is a component in the runtime system (controller firmware). The function blocks are applied to control and monitor the client from the application, and thus to implement the data exchange with the OPC UA server.
For more information about the OPC especially OPC UA, refer to the official webpage of the OPC Foundation at https://opcfoundation.org.
Also refer to General Information on Function Blocks.
Characteristics of the Library
The table indicates the characteristics of the library:
Characteristic |
Value |
---|---|
Library title |
OpcUaHandling |
Company |
Schneider Electric |
Category |
Communication |
Component |
OPC UA Handling |
Default namespace |
SE_OPC |
Language model attribute |
|
Forward compatible library |
NOTE: For this library, qualified-access-only is set. This means, that the POUs, data structures, enumerations, and constants have to be accessed using the namespace of the library. The default namespace of the library is SE_OPC.
The OPC UA library is supported by the Modicon M262 Logic/Motion Controllers (TM262L20MESE8T, TM262M25MESS8T, TM262M35MESS8T).
The function blocks and data types provided with the library are compliant with the PLCopen specification PLCopen OPC-UA Client for IEC61131-3 version 1.1.
|
EXCHANGED DATA INCOMPATIBILITY |
Verify that the exchanged data are compatible because data structure alignments are not the same for all devices. |
Failure to follow these instructions can result in death, serious injury, or equipment damage. |
NOTE: Schneider Electric adheres to industry best practices in the development and implementation of control systems. This includes a "Defense-in-Depth" approach to secure an Industrial Control System. This approach places the controllers behind one or more firewalls to restrict access to authorized personnel and protocols only.
|
UNAUTHENTICATED ACCESS AND SUBSEQUENT UNAUTHORIZED MACHINE OPERATION |
oEvaluate whether your environment or your machines are connected to your critical infrastructure and, if so, take appropriate steps in terms of prevention, based on Defense-in-Depth, before connecting the automation system to any network. oLimit the number of devices connected to a network to the minimum necessary. oIsolate your industrial network from other networks inside your company. oProtect any network against unintended access by using firewalls, VPN, or other, proven security measures. oMonitor activities within your systems. oPrevent subject devices from direct access or direct link by unauthorized parties or unauthenticated actions. oPrepare a recovery plan including backup of your system and process information. |
Failure to follow these instructions can result in death, serious injury, or equipment damage. |