EtherLab R Version 2.1.0

Transcription

1 ther ab EtherLab R Version created by Ingenieurgemeinschaft Essen January 2013

2 Ingenieurgemeinschaft IgH Heinz-Bäcker-Str. 34 D Essen Tel.: Fax.:

3 Contents 1 Introduction 4 2 License 4 3 Concept 4 4 Installation Development Environment Prerequisites Installation Library Setup Runtime Environment Prerequisites Installation The EtherLab Library 8 6 Creation of EtherLab Models 8 7 Starting of EtherLab Applications 9 List of Figures 1 EtherLab Architecture EtherLab Library EtherCAT Blockset Realtime Workshop Configuration Solver Configuration

4 1 Introduction A blockset was created for the real time connection of EtherCAT R components in MATLAB/Simulink R. EtherCAT slaves can be selected from the etherlab_lib in MAT- LAB/Simulink and directly included into the model. After that, the model is translated to C code and compiled to a realtime application, that can be executed in context of a Linux OS. To achieve hard real-time operation, a kernel with realtime preemption [1] is recommended. 2 License EtherLab is licensed under the GPL, version 3 [4]. The name EtherLab is a registered trademark of Ingenieurgemeinschaft IgH, Heinz- Bäcker-Straße 34, Essen, Germany. 3 Concept EtherLab R is a system to create controllers using EtherCAT hardware, that run with the EtherLab s EtherCAT master [2]. The user is able to create models using the MATLAB/Simulink library etherlab_lib, that are compiled to a realtime application by traversing Simulink Coder (former Realtime Workshop) and EtherLab. Figure 1 shows the development and runtime environment and the additional components. The EtherLab technology can be subdivided into the components listed below: The etherlab_lib for MATLAB/Simulink. It contains all necessary blocks for the creation of Simulink models with EtherCAT slaves. The support code, that compiles an executable of the output of Simulink Coder. This happens in background and is not visible to the user. The PdServ library [5], that adds non-realtime process data server functionality to the realtime application. 4 Installation The installation procedure is separated for the development and runtime environments, which do not necessarily have to be on the same system. In the following sections it is assumed, that EtherLab components are installed in /vol/opt/etherlab. If this directory does not exist, it can be created with the commands below, which also allow members of the group users to write to that directory: 4

5 Figure 1: EtherLab Architecture 5

6 1 # mkdir -p /vol/opt/etherlab 2 # chown root:users /vol/opt/etherlab 3 # chmod 775 /vol/opt/etherlab 4.1 Development Environment Prerequisites Prerequisites for the installation of EtherLab on the development system: Matlab 2009b (or newer) Simulink Simulink Coder (former Realtime Workshop) GNU C Compiler Collection (GCC) [3] cmake Installation Installation is done after copying the EtherLab tarball from the EtherLab CD (or downloading from etherlab.org, like in the below example) as normal user according to the commands below. The last command installs EtherLab into the directory /vol/opt/etherlab/rtw. 1 $ mkdir /vol/opt/etherlab/src 2 $ cd /vol/opt/etherlab/src 3 $ wget 4 $ tar xjf etherlab tar.bz2 5 $ mkdir etherlab build 6 $ cd etherlab build/ 7 $ cmake -DPREFIX=/vol/opt/etherlab../etherlab $ make 9 $ make install Library Setup As a prerequisite for the setup_etherlab command (see below) to succeed, the file toolbox/local/pathdef.m inside the MATLAB installation directory must be writable for the user running MATLAB. Enter the below commands (as root) to make it writable for all users in the group users (substitute the variable MATLABDIR with the correct path first): 1 # chown :users $MATLABDIR/toolbox/local/pathdef.m 2 # chmod 664 $MATLABDIR/toolbox/local/pathdef.m 6

7 To setup the EtherLab library etherlab_lib for the use in MATLAB, the below commands must be entered (out of MATLAB). 1 >> cd /vol/opt/etherlab/rtw 2 >> setup etherlab Now, the EtherLab library can be used acc. to section Runtime Environment Prerequisites The EtherLab software itself does not have to be present on the runtime system. In order to compile and run EtherLab-generated realtime applications, the below software has to be available: Linux-Kernel 2.6 (RT-Preemption [1] recommended) GNU C Compiler Collection (GCC) [3] PdServ Library [5] with dependencies: Log4plus Library [6] CommonCpp2 Library [7] YAML Library [8] IgH EtherCAT Master 1.5 [2] (optional) Installation The realtime application executables created by EtherLab are linked against the PdServ library and optionally the EtherCAT master library 1. The PdServ library has a few dependencies. There are RPM packages for opensuse available in the download directory of the EtherLab homepage both for the library itself. The log4cplus, Common C++ and YAML libraries are quite common and usually available as packages for Linux distributions. To build and compile PdServ, the below commands can be used: 1 $ cd /vol/opt/etherlab/src 2 $ wget 3 $ tar xjf pdserv tar.bz2 4 $ mkdir pdserv build 5 $ cd pdserv build/ 6 $ cmake -DCMAKE INSTALL PREFIX=/vol/opt/etherlab../pdserv $ make 8 $ make install 1 For installation instructions, please refer to the EtherCAT master documentation. 7

8 5 The EtherLab Library The EtherLab library etherlab_lib was designed to allow the creation of EtherLab models. It contains blocks for all supported EtherCAT slaves, plus a generic slave block for slaves that are not (yet) in the library. To show the library window (see Figure 2), the commands below have to be entered in MATLAB: 1 >> etherlab lib Figure 2 shows the window containing the etherlab_lib, while Figure 3 shows the EtherCAT-specific blockset. Each block has a configuration dialog, that shows up after double-clicking on the block area. There is a Help button in all of the configuration dialogs, that provides detailed help concerning the dialog elements. Figure 2: EtherLab Library On the left side of the EtherCAT subsystem in Figure 3 there are subsystems with EtherCAT slave blocks of different vendors and, on top, the generic slave block that includes an arbitrary EtherCAT slave. The special blocks on the right side do not correspond to certain slaves: Master State This block allows to query information from a certain EtherCAT master (like number of slaves, etc.). Domain State This block allows to query information from a certain process data domain (see EtherCAT master documentation). This is important to get to know, if process data are exchanged correctly. 6 Creation of EtherLab Models To create a new model using EtherLab blocks, a few model parameters have to be set up (menu Simulation/Configuration Parameters... ): The input field Realtime Workshop System target file must contain the file name etherlab.tlc. It can be chosen via the Browse... button (see Figure 4). 8

9 Figure 3: EtherCAT Blockset The input field Solver Fixed-step size must contain the period time of the realtime cycle, for example 0.01 meaning 100 Hz (see Figure 5). At this time, the model can be edited as usual. When finished, the shortcut Ctrl+B will generate the C code and build the realtime application executable. If the executable shall be compiled on another host, the option Generate code only has to be checked and the following command on the build host can be used to create the executable: 1 $ make -C <myapp> etl hrt -f <myapp>.mk 7 Starting of EtherLab Applications The simplest way to start the realtime application is the following command, where myapp corresponds to the Simulink model name. 1 #./<myapp> At best the application outputs nothing and stays in foreground and can be quitted via pressing Ctrl-C. Error messages are printed to the console. The EtherLab application template creates a few command-line parameters: 9

10 Figure 4: Realtime Workshop Configuration 10

11 Figure 5: Solver Configuration 1 $./myapp -h 2 Usage : myapp [ OPTIONS ] 3 Options : 4 -- priority - p < PRIO > Set task priority. Default : RT pdserv - config - c < PATH > PdServ configuration file help - h Show this help. With the --pdserv-config option, that path to a PdServ configuration file can be passed, that allows to configure the MSR protocol, for example. 11

12 References [1] RT PREEMPT HOWTO. PREEMPT_HOWTO, [2] IgH EtherCAT Master for Linux [3] GCC, the GNU Compiler Collection [4] GNU General Public License, Version html [5] PdServ Library [6] Logging Framework for C++. Home/, [7] GNU Common C [8] YAML Ain t Markup Language