User Documentation

ManualsBrandsWeidmueller ManualsAutomation & SoftwareUC20-SL2000-EC Currently only available in combination with Runtime-License (2638920000).

Table Of Contents

Table of contents
1 Introduction
- 1.1 Purpose of the document
- 1.2 Requirements
- 1.3 Intended use
- 1.4 Notes on this document
  - 1.4.1 Contents of the document
  - 1.4.2 Not contained in this document
- 1.5 Further documentation
- 1.6 Relevant countries and registrations
2 Safety instructions
- 2.1 Representation
- 2.2 General safety information
- 2.3 Personnel safety
- 2.4 Safety instructions for projecting
3 System overview
- 3.1 Hardware architecture
- 3.2 Software structure
- 3.3 Network design
- 3.4 u-control - CPU modules
- 3.5 Buses
- 3.6 u-create studio Toolsuite
- 3.7 Libraries and interfaces
4 Operating behavior
- 4.1 Start-up
5 Software installation
- 5.1 Install firmware of the control
6 Configuration
- 6.1 Data exchange between control and visualization
7 Program development
- 7.1 Task priorities
- 7.2 Fast control
- 7.3 Device Service
8 Licensing
- 8.1 Trial license
  - 8.1.1 Activation of a trial license (single user license)
  - 8.1.2 Activation of a trial license (runtime license)
- 8.2 Activating a single-user license (software on the PC)
- 8.3 Activating a runtime license (software on the device)
- 8.4 License status and license overview
- 8.5 Device replacement
  - 8.5.1 PC replacement (single-user license)
  - 8.5.2 Device replacement (runtime license)
- 8.6 Reset the license information
9 Device Administration (DevAdmin)
- 9.1 Tab "Diag."
- 9.2 Tab "Config."
- 9.3 Tab "Backup/Restore"
- 9.4 Tab "Plugins"
  - 9.4.1 Add plugin to DevAdmin
- 9.5 Change password for DevAdmin
10 Software units
- 10.1 Creating a software unit
- 10.2 Example meta.xml
11 OPC UA Server
- 11.1 Overview of variants
- 11.2 Establishing a connection
- 11.3 Server configuration
- 11.4 Generic variable tree
- 11.5 Creating an information model
- 11.6 Logging of server operation
12 Node-RED
13 LongtermDiagnosticMonitor
- 13.1 Monitor
14 Data recorder
- 14.1 Configuration
- 14.2 Data recording
- 14.3 Reading out the buffer
- 14.4 Recording callback from the application
- 14.5 Data locality and real-time
- 14.6 Size limitations
- 14.7 Appendix: C interface
15 Diagnostics
- 15.1 Control diagnosis
  - 15.1.1 Error codes
- 15.2 Diagnosis data for Weidmüller
  - 15.2.1 Status report
  - 15.2.2 Access to flash storage medium
- 15.3 USB via Ethernet adapter
16 Maintenance
- 16.1 Executing a firmware update of the system components
  - 16.1.1 Firmware-Update for devices
  - 16.1.2 Automatic update during boot-up
17 Technical data
18 Directives and standards
19 Appendix: Tutorial - creating an IEC project
- 19.1 Creating a new project
- 19.2 Creating a simple program
- 19.3 Saving u-create studio project
- 19.4 Load firmware onto device
- 19.5 Configuration of the control
- 19.6 Compiling project and uploading onto control
- 19.7 Starting the project
20 Appendix: Addressing in the Ethernet (basics)
21 Appendix: Tutorial FoE
22 Appendix: Tutorial - call C function from IEC
- 22.1 Preconditions and needed components
- 22.2 Task
- 22.3 Creating the C function and download
- 22.4 Calling the IEC funtion in the IEC application and download
Index

OPC UA Server

System manual

2696790000/02/04.2020

Attribute Description

NodeId

Defines the node ID of the current instance, and this must be unique.

This server version only supports numeric node IDs.

BrowseName

Internally used name for node addresses.

DisplayName

Displayed name for the OPC UA client.

AccessLevel

(only variables)

Defines the access rights for the Value attribute of a variable. By

default, no access is allowed. The attribute is specified as hexadeci-

mal number and interpreted as AccessLevelType defined in the

OPC UA specification 3. Example: "0x01" = CurrentRead, "0x03" =

CurrentRead and CurrentWrite.

ValueConstant

(only variables)

Allocation of a constant.

ValuePath

(only variables)

Path to a system variable. The path can be displayed in the u-create

studio browser after successful login.

In the following example, an OPC UA Boolean-type variable is instanced in

the server address space and linked to a variable on the controller. When

defining the Node ID, the namespace index was not specified in the exam-

ple. This uses the default namespace (if NamspaceUris is defined in the en-

try).

<Variable DataType="0:Types.0:DataTypes.0:BaseDataType.0:Boolean"

NodeId="i=1002" BrowseName="MyBool" DisplayName="MyBool"

ValuePath="APPL.system.vBOOL" AccessLevel="0x01"/>

Instead of a variable path, constants defined in the XML file can also be

linked. All data types specified above are supported, except DateTime.

In the following example, an OPC UA Boolean-type variable is instanced

and the value is linked to a constant:

<Variable DataType="0:Types.0:DataTypes.0:BaseDataType.0:Boolean"

NodeId="i=1003" BrowseName="MyBool" DisplayName="MyBool"

ValuePath="true" AccessLevel="0x03"/>

Arrays

Information

The OPC UA Server supports only one-dimensional arrays with basic data

types and variable mapping (Attribute ValuePath).

For instantiating arrays, another entry, ArrayDimension, and the following

additional attribute is needed:

Attribute Description

ValueRank="1"

Determines the number of array dimensions. Only the value "1" is

supported.

In the following example, the entire IEC array is instantiated in the server as

an OPC UA array.

<Variable DataType="0:Types.0:DataTypes.0:BaseDataType.0:Boolean"

NodeId="i=10" BrowseName="bool array" DisplayName="bool array"

AccessLevel="0x03" ValueRank="1">