User Documentation

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

119

120

121

122

123

124

125

126

127

128

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

Appendix: Tutorial - call C function from IEC

System manual

2696790000/02/04.2020

124

22 Appendix: Tutorial - call C function from IEC

The u-create system offers the possibility to call C functions in IEC created

with u-create studio C++.

Therefore a template with a predefinded interface for data exchange exists

in u-create studio C++. It is recommanded to create a function in IEC which

takes care of the call of the C function and the correct data exchange. The

data exchange itself takes place on a shared memory area. Because of this

only adresses on the memory area are transfered. The data types from IEC

and C are not compatible, so on transfer of the parameters it must be payed

attention on the correct type convertion.

Information

There is no automatically type checking. The user himself is responsible for

the correct mapping. E.g. if the size of the data types does not match, a

wrong memory area is accessed.

The example in this chapter describes the creation of a C function in u-cre-

ate studio C++ and the call in a IEC application created inu-create studio.

22.1 Preconditions and needed components

The following components are necessary:

● u-create studio C++

● u-create studio

● u-create studio project with an executable IEC application

● Fitting hardware

The creation of this example requires basic knowledge in dealing with u-cre-

ate studio and u-create studio C++.

22.2 Task

In this example application a self made C function should be called via an

IEC function in the IEC application. The IEC function provides 3 local vari-

ables with different data types (DWORD, STRING[106] and REAL) and a global

variable of type DWORD. The values of the variables should be changed in the

C function as follows:

● The global variable of type DWORD should be summated with the variable

of type DWORD

● The variable of type REAL should be multiplicated with 3.

● The variable of type STRING[106] should be extended with characters.

● The return value of the C function should be twice as much as the vari-

able of type DWORD.