Server configuration

• Device Ethernet interface
• Cycle rate
• Security

Communication settings

• IP address / Port
• Number of sessions
• Reverse connect (client to server)

Data setup

• Upload of all variables in the application
• Access rights
• Data types
• Engineering units
• Ranges
• Sample rates

The telecontrol package enables the use of the CODESYS PLC as an IEC 60870-5-104 server. All relevant features of the IEC 60870-5-104 protocol are implemented:

• See the interoperability list below
• Library written in IEC61131-3
• Configurator as CODESYS PlugIn

Functionality

• Support of information objects for the following groups:
  • Monitoring direction: SP, DP, ST, BO, ME, IT
  • Control direction: SC, DC, RC, SE, BO

    For detailed information on protocol features, see the Interoperability List.
• Features of the telecontrol configurator:

Notice

Check the licensing options of your controller with the free CODESYS Device Reader.

The OPC DA server is able to communicate with V3 and V2.3 controllers at the same time. In addition, a missing controller can be simulated. Then, instead of accessing the controller’s symbol pool, a symbol file with the symbol pool is made available to the OPC DA server. (XML file or SDB file).

A detailed description of the range of functions and commissioning can be found in the user manual for the CODESYS OPC DA solution (part of the setup).

The OPC DA server is able to communicate with V3 and V2.3 controllers at the same time. In addition, a missing controller can be simulated. Then, instead of accessing the controller’s symbol pool, a symbol file with the symbol pool is made available to the OPC DA server. (XML file or SDB file).

A detailed description of the range of functions and commissioning can be found in the user manual for the CODESYS OPC DA solution (part of the setup).

In addition to client/server communication , communication via the OPC UA Pub/Sub protocol provides another option for exchanging data between network participants in accordance with the rules of the OPC UA Foundation . The structure of the data ( ) can be freely defined and is agreed upon in advance between sender and receiver. This eliminates the need to transport additional (meta) data. Data is transferred using the OPC UA PubSub SL library via UDP/IP according to the rules defined for UADP . A so-called publisher publishes its data to an unknown number of subscribers . The sender and receiver do not know each other. The number of recipients therefore has no effect on the sender. In principle, the protocol cannot provide feedback to the sender as to whether its messages have reached the recipient. If required, such feedback must be managed on an application-specific basis. The data is transmitted in a binary format in accordance with the rules of the OPC UA Foundation . The OPC UA PubSub SL library converts the IEC data types into the corresponding OPC UA data types and vice versa . The implementation follows the following profiles:DataSet

• Publisher: PubSub Publisher UADP Periodic Fixed Settings
• Subscriber: PubSub Subscriber UADP Periodic Fixed Settings

The length of the messages is limited to 1500 bytes (MTU) ( Chunked NetworkMessages not supported ). As long as the rules for a time-sensitive network are not yet available, hard real-time conditions cannot be met. However, the implementation of the OPC UA PubSub SL library tries to keep the jitter as low as possible.

The CODESYS OPC UA Client can be used to connect to any OPC UA server and exchange data with them. The client provides an API to connect to an OPC UA server and execute the different types of OPC UA requests.

The OPC UA Client API supports the following services:

Discoveries:

• GetEndpoints
• FindServers
• FindServersOnNetwork

Session:

• CreateSession
• ActivateSession
• DeleteSession

View:

• Browse
• BrowserNext
• RegisterNodes
• UnregisterNodes
• TranslateBrowsePathsToNodeIds

Attributes:

• Read
• Write

Subscriptions:

• CreateSubscription
• ModifySubscription
• SetPublishing
• Publish
• DeleteSubscription

MonitoredItems:

The client is able to handle both types of monitored elements (events and sampling). The only difference in handling is the callbacks that are called for both types.

• CreateMonitoredItems
• DeleteMonitoredItems
• ModifyMonitoredItems
• SetMonitoringMode

Security: The OPC UA client uses the existing security-relevant runtime system interfaces to handle the encryption algorithms and certificates. The client registers itself in the certificate store to facilitate the configuration of the client certificates.

SecurityProfiles:

• None
• Basic256Sha256 (Sign, Sign_and_Encrypt)
• Aes128_Sha256_RsaOaep
• Aes256_Sha256_RsaPss

User token policy:

• Anonymous
• Username

An example of using the API is available in the CODESYS Store: ‘OPC UA Client Example’.

Additionally, it is possible to connect the OPC UA client to an OPC UA server within the CODESYS IDE via the “Data Source Manager” object. OPC UA servers can be added online or offline.

Online: The client connects to the server via the IP address and detects the existing variables and types. The user can select the objects to be searched.

Offline: Using a description file, the client reads the variables and types from the information model. A connection to the server is not required.

See also [CODESYS Online Help]( https://content.helpme-codesys.com/en/CODESYS%20Communication/_cds_obj_data_source_communication_opc_ua_server.html ).

The OPC UA server makes it easy to make PLC variables available in the OPC UA address space. Clients can read, write and monitor the PLC values. Custom information models can be imported and linked to the PLC application. This also enables clients to execute PLC methods.

Certification

The “OPC Foundation Certified for Compliance” logo is a trademark of the OPC Foundation and may only be used with the written permission of the OPC Foundation. Any unauthorized use of the “Certified for Compliance” logo is prohibited.

The “OPC Foundation Certified for Compliance” logo indicates that this product has been tested by an independent certification laboratory and certified for compliance with the following OPC UA profiles, which are part of the OPC UA specifications:

• Micro Embedded Device 2017 Server Profile
• Method Server Facet
• SecurityPolicy [B] – Basic256Sha256
• SecurityPolicy [A] – Aes128-Sha256-RsaOaep
• SecurityPolicy – Aes256-Sha256-RsaPss
• User Token – Anonymous Server Facet
• User Token – User Name Password Server Facet

Supported features

The OPC UA Server supports the following functions:

• Browsing data types and variables
• Standard services for reading and writing
• Notification of value changes (Subscription and Monitored Item Services)
• No limit on the number of sessions, monitored objects and subscriptions (the number depends on the performance of the respective platform)
• Support of events
• Support for full access to structures
• Encrypted communication with an OPC UA client
• Support for multitasking
• Support for OPC UA methods
• Support for Alarms&Conditions

Supported profiles: The OPC UA server currently supports the “Micro Embedded Device Server Profile”. This server profile allows reading, writing and subscribing to items.

Supported information models: OPC UA allows the definition of different data types. The combination of customer-specific data types, object types and reference types enables the definition of your own information model. An information model describes how the data should be made available to the address space.

• PLCopen information model
• Custom information models (companion specifications)

See also [CODESYS Online Help]( https://content.helpme-codesys.com/en/CODESYS%20Communication/_cds_using_opc_ua_information_models.html ).

Security:

• signed and encrypted communication
• User management

SecurityProfiles:

• No
• Basic256Sha256 (Signing, Signing_and_Encrypting)
• Aes128_Sha256_RsaOaep
• Aes256_Sha256_RsaPss

User token policy:

• Anonymous
• user name