etas rtpc-eve v6.0 installation guide for target pc€¦ · etas rtpc-eve v6.0 - installation guide...

ETAS RTPC-EVE V6.0Installation Guide for Target PC

2

Copyright

The data in this document may not be altered or amended without special noti-fication from ETAS GmbH. ETAS GmbH undertakes no further obligation in rela-tion to this document. The software described in it can only be used if thecustomer is in possession of a general license agreement or single license. Usingand copying is only allowed in concurrence with the specifications stipulated inthe contract.

Under no circumstances may any part of this document be copied, reproduced,transmitted, stored in a retrieval system or translated into another languagewithout the express written permission of ETAS GmbH.

© Copyright 2013 ETAS GmbH, Stuttgart

The names and designations used in this document are trademarks or brandsbelonging to the respective owners.

Document XY999999 V6.0 R05 EN - 06.2013

ETAS RTPC-EVE V1.0 - Installation Guide for Target PC 3

Contents

ETAS Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Target Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.1 Delivery Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.2.1 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2.2 Special BIOS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82.3.1 Installing RTPC-EVE Target PC on the Real-Time PC . . . . . . . . . . . . . 92.3.2 Hardware Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3.3 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3.4 Resetting the Boot Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3.5 Cloning Installed Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.3.6 Clock Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2.4 PCI CAN Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1 Operating Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3.1.1 ”Simulation Controller” Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1.2 ”Idle/Configuration” Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153.1.3 ”Power Down” Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

3.2 CPU Core Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.3 Benchmark Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

4 Configuration for EVE Use Cases on the Target PC . . . . . . . . . . . . . . . . . . . . . . . . 194.1 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

4.1.1 Model-in-the-Loop (MiL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194.1.2 Hardware-in-the-Loop (HiL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

ETAS RTPC-EVE V1.0 - Installation Guide for Target PC4

Contents ETAS

4.1.3 Hardware-in-the-Loop with Measuring and Calibration Access (M&C)19

4.1.4 Hardware-in-the-Loop with Load and Error Simulation. . . . . . . . . . 204.1.5 Massive I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

4.2 The Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.2.1 Access to the Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.2.2 Navigation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.2.3 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

5 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

6 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356.1 The Real-Time PC in a Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

6.1.1 Configuring the VMware Network Adapter . . . . . . . . . . . . . . . . . . 356.1.2 Creating the Virtual PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

6.2 How to integrate the Virtual Box for RTPC - Setup of Oracle VirtualBox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386.2.1 System Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386.2.2 Setup and Configuration of VirtualBox . . . . . . . . . . . . . . . . . . . . . 38

6.3 Setup of VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396.3.1 Setup and Configuration of VMware Player . . . . . . . . . . . . . . . . . . 39

6.4 Install the RTPC-EVE license via HTTP Interface: . . . . . . . . . . . . . . . . . . . . . . 41

7 ETAS Contact Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45


ETAS Introduction

1 Introduction

This chapter is intended, on the one hand, for all users who install, maintain anduninstall RTPC-EVE on the target PC, and, on the other, for system administratorswho make RTPC-EVE available on a file server for installation via the network. Itprovides important information on the delivery scope, hardware and softwarerequirements for single station and network installation as well as on how toprepare the installation. The sequence of both the installation and uninstallationof RTPC-EVE is described.

1.1 Target Group

This manual addresses qualified personnel working in the fields of automobilecontrol unit development and calibration. Specialized knowledge in the areas ofmeasurement and control unit technology is required. Users not yet familiar withautomotive software descriptions based on the AUTOSAR framework areadvised to get a suitable training upfront.

ISOLAR-EVE users should be familiar with the Microsoft Windows XP, WindowsVista, or Windows 7 operating system. All users should be able to execute menucommands, enable buttons, etc. Furthermore, the users should be familiar withthe Windows file storage system, especially the connections between files anddirectories.

The users have to know how to use the basic functions of the Windows FileManager and Program Manager or the Windows Explorer, respectively, and theyshould be familiar with the "drag-and-drop" functionality.

Knowledge about the general features and operation of Eclipse based softwareproducts will be beneficial but is not mandatory.


Introduction ETAS


ETAS Installation

2 Installation

This chapter includes information on the following topics:

• "Delivery Scope" on page 7

• "System Requirements" on page 7

– "Hardware Requirements" on page 7

• "Installation" on page 8

– "Installing RTPC-EVE Target PC on the Real-Time PC" on page 9

– "Hardware Integration" on page 10

– "System Configuration" on page 10

– "Resetting the Boot Setting" on page 12

– "Cloning Installed Versions" on page 12

– "Clock Synchronization" on page 13

– "Clock Synchronization" on page 13

• "PCI CAN Board" on page 14

For Command Line Installation see manual "setup.pdf. This manual contains anerror code list.

2.1 Delivery Scope

The delivery scope of the RTPC-EVE Target PC includes

• RTPC-EVE Target PC Software DVD

• This User's Guide

• Possibly a PC from ETAS – for PC order data, please contact ETAS.

2.2 System Requirements

You need the following to install and run the RTPC-EVE software:

• RTPC-EVE Software DVD

• RTPC-EVE Target PC software license

• Suitable PC hardware (see ”Hardware Requirements” below)

• Ethernet crossover cable (2x RJ45 socket) for the connection between the host PC (tooling) and the target PC. Not necessary for VMware solution.

2.2.1 Hardware Requirements

RTPC-EVE Target PC is compatible with most standard PCs. To run the software,the following requirements must be fulfilled:

Processor Intel Core i family

Ethernet adapter for the connection to the user PC

Onboard Ethernet adapter. Most standard types are supported, e.g. Realtek 8139, SiS900, Intel PRO/100 (8255x Ethernet Controller) and particularly all Ethernet adapters supported by Linux kernel 2.6.33.

CPU min. Dual Core PC (please configurate)


Installation ETAS

For more precise details on the compatibility of PCs made by different manufac-turers, refer to the compatibility list (http://192.168.40.14/documentation/).

2.2.2 Special BIOS Settings

To ensure that the installation from DVD works, the system’s BIOS has to beconfigured so that the PC boots from the DVD (”primary boot device = DVD”). Ifyou want to use the PC later without a keyboard, you also have to specify thissetting (”no halt on keyboard”). The names of the settings in brackets may vary- for more details, refer to your PC’s User’s Guide.

2.3 Installation

The installation of RTPC-EVE Target PC is divided into four parts which are eachdescribed in the sections below:

• "Installing RTPC-EVE Target PC on the Real-Time PC" on page 9

• "Hardware Integration" on page 10

• "System Configuration" on page 10

• "Clock Synchronization" on page 13

RAM Min. 2 GB

Hard disk IDE or SATA, min. 80 GB

Graphic VGA-compatible

Monitor Is only required for basic installation

Keyboard PS/2 or USB, is only required for basic installation

DVD drive IDE or SATA, is only required for basic installation (bootable)

Operating system Not necessary

Note

During RTPC-EVE Target PC operation, success or error messages are emitted in the form of sound. If your PC does not have an output device for acoustic signals, you can access information on the current status via the web interface (see section 4.2 on page 21).

Note

ETAS also offers RTPC-EVE Target PC as a preinstalled version on PC hardware recommended and tested by ETAS. In this case, please start by reading the section "Hardware Integration" on page 10.


ETAS Installation

2.3.1 Installing RTPC-EVE Target PC on the Real-Time PC

If RTPC-EVE Target PC has already been installed by ETAS, please continue withthe next section "Hardware Integration" on page 10.

• Connect the monitor and keyboard to the PC hard-ware.

• Switch the PC and the monitor on.

• Insert the RTPC-EVE Target PC Software DVD into the PC’s DVD drive.

The PC boots the RTPC-EVE Target PC installation.

• Wait until the RTPC-EVE Target PC installation dia-log box is displayedSelect the option [Install RTPC-EVE Target PC software] using the cursor keys.

• Press <ENTER>.

• Confirm the warning by selecting the option[Yes, continue with installation].

• Wait until the RTPC-EVE Target PC installation has been completed (takes about 5 minutes).

• Remove the RTPC-EVE Target PC Software DVD.

• Select the option [Reboot].

The PC reboots.

• Wait until the PC plays an ascending sequence of notes.

RTPC-EVE Target PC has been installed successfully.

• Shut down the PC by quickly pressing the on/off switch.

After just a few seconds, the PC plays a descending sequence of notes and shuts down.

This indicates that RTPC-EVE Target PC has been shut down correctly and can be disconnected from the mains.

Note

All data on the hard disk is deleted by the RTPC-EVE Target PC installation!

Real-Time PC


Installation ETAS

For more details on these acoustic signals, refer to the chapter "Operation" on page 15.

• Remove monitor and keyboard (see "Special BIOS Settings" on page 8).

2.3.2 Hardware Integration

This section describes the integration of the real-time PC into a Hardware-in-the-Loop test system (HiL). Other configurations, such as Model-in-the-Loop or HiLsystem with measuring and calibration access, are described in the section"Applications" on page 19.

RTPC-EVE Target PC uses the identifier Eth0 (Host) for the onboard Ethernetinterface – the Ethernet board has the identifier Eth1 (HW).

2.3.3 System Configuration

RTPC-EVE Target PC is easy to configure from the user PC via a Web browser (e.g.Internet Explorer or Mozilla Firefox). The configuration dialog can be accessed viathe IP address 192.168.40.14.

Carry out the steps described below to configure RTPC-EVE Target PC . For moredetails on configuration modes refer to the section "Applications" on page 19.

To open the configuration dialog

• Launch the real-time PC by pressing the on/off switch on the front.

• Switch the chassis with the I/O hardware on.

• Wait a few seconds until you hear the ascending sequence of notes.

• Launch a Web browser on the user PC.

• Invoke the URL http://192.168.40.14.

The RTPC-EVE Target PC configuration dialog opens.

Note

RTPC-EVE Target PC uses a robust file system, but hardware and software can still be damaged when powered off without shutting down or during a sud-den voltage drop. ETAS thus recommends shutting down RTPC-EVE Target PC by briefly pressing the on/off switch to avoid these problems.

Note

You can also assign this IP address an alias which is easier to remember – for more details refer to the section 4.1 on page 19.


ETAS Installation

The simulation controller has to be stopped to configure the RTPC-EVE Target PCSoftware (see "”Simulation Controller” Mode" on page 15).

To stop the simulation controller

• Click the Stop Simulation Controller button.

• Click the Main Page link.

To run the configuration

• Click the Configure RTPC-EVE Target PC link.

• Click the Autoconfigure button.

The autoconfiguration is run and the result is set in the ”RTPC_USAGE_ETH1” box.

To restart the simulation controller

• Click the Main Page link.

• Click the Simulation Controller link.

• Click the Start Simulation Controller button.

When you hear the ascending sequence of notes, the simulation controller is active again.

The configuration has now been carried out successfully. For more details onother configuration modes refer to the section "Troubleshooting" on page 31.

• To finalize the procedure, click Reboot.

Note

As long as the simulation controller is running, the Main Page link is inactive!

Note

If instead you hear the sequence of error notes, the simulation controller could not be started. For more details refer to the chapter "Troubleshooting" on page 31.

Note

When the system is booted from one partition that contains a version < V5.x, the two new partitions are no longer visible and the versions of RTPC-EVE Tar-get PC on them therefore can no longer be booted. Ensure that one of the first two partitions (e.g. sda5 and sda6) always contains a version V5.0 or higher.


Installation ETAS

2.3.4 Resetting the Boot Setting

If there are problems when changing boot settings (e.g. after repartitioning),these settings can be reset.

To reset boot settings

• Select Main Page >> Configuration.

• Go to the ”System Boot Settings” section.

• Select a version

• Click Set Boot Version.

2.3.5 Cloning Installed Versions

You can clone versions of RTPC-EVE Target PC that have already been installed bygenerating an installable file (*.tgz) and downloading this file to your operatingPC.

To clone a version

• Select Main Page >> Installation / Update >> dClone Installed Version.

• Select one of the installed versions.

• Enter a name for the clone to be created.

• Click Generate Clone Image.

The procedure is started and the progress displayed in the web interface.

• Once the procedure has been completed, you can download the clone to use on your operating PC.

To download a clone

• Click the Return to Installation / Update link.

• Go to ”Download Software Image”.

• Select the version just created.

• Click Download.

A download dialog box opens in which you can save this file.

Note

The currently active version cannot be cloned!


ETAS Installation

• If you want to delete this file from your real-time PC, select the clone under ”Delete Installed Software Images”.

• Click Delete.

The file is deleted from your real-time PC.

2.3.6 Clock Synchronization

To synchronize the time on the user PC and the real-time PC, you can activatethe NTP1 server integrated in Windows.

Activation takes place by making entries in the Windows registry – you will findthe file for setting the relevant keys via the web interface at

http://192.168.40.14/tools/NTP/NTP-LocalParameter.reg

This configures the Windows service ”ws32time” – the server must be rebootedafter the keys have been modified.

To reboot the NTP server

• Select Settings ∅ Control Panel ∅ Administrative Tools ∅ Services.

• Select the ”Windows Time” service.

• Open the shortcut menu by pressing the right-hand mouse button.

1. Network Time Protocol


Installation ETAS

• Select Restart.

2.4 PCI CAN Board

For communication between the model and the ECU, you can purchase a PCICAN board for the ETAS real-time PC.

For details of order data, please contact ETAS.

Note

Please note that when the service has been rebooted, it can take a few minutes until the time is precise enough to be made available to other clients.


ETAS Operation

3 Operation

This chapter includes information on working with VAP Target PC V1.0.

The individual sections are:

• "Operating Modes" on page 15

• "CPU Core Load" on page 17

• "CPU Core Load" on page 17

• "Benchmark Indicator" on page 17

3.1 Operating Modes

VAP Target PC V1.0 has four operating modes, one of which is always active:

• Simulation Controller

• Idle/Configuration

• Power Down

Use the Web interface to configure which operating mode is to be activatedwhen the real-time PC is switched on.

3.1.1 ”Simulation Controller” Mode

The "Simulation Controller" mode is used to run real-time models. An ascendingsequence of notes indicates that the simulation controller has been started suc-cessfully.

The simulation controller is activated automatically by default when the real-timePC is powered up.

Eight identically pitched notes indicate that the simulation controller cannot bestarted because of a configuration problem.

In this case, RTPC-EVE Target PC is automatically set to ”Idle/Configuration”mode (see "”Idle/Configuration” Mode" on page 15).

Possible causes of error can be found in the chapter "Troubleshooting"on page 31.

3.1.2 ”Idle/Configuration” Mode

The ”Idle/Configuration” mode is used to configure RTPC-EVE Target PC and toupdate the software (Update). RTPC-EVE Target PC cannot run real-time modelsin this mode.

Note

A VMEbus reset takes place every time the simulation controller is started!


Operation ETAS

3.1.3 ”Power Down” Mode

The ”Power Down” operating mode is activated either by quickly pressing theon/off switch on the front of the real-time PC or via the Web interface. RTPC-EVETarget PC shuts down the system, plays a sequence of notes (four descendingnotes) and switches the real-time PC off.

The real-time PC can then be disconnected from the mains.

Note

RTPC-EVE Target PC uses a robust file system, but hardware and software can still be damaged when powered off without shutting down or during a sudden voltage drop. ETAS thus recommends shutting down RTPC-EVE Target PC by briefly pressing the on/off switch to avoid these problems.


ETAS Operation

3.2 CPU Core Load

The distribution of the process load to the processor cores can be issued in anXML file using

http://192.168.40.14/cgi-bin/cpu-load[?detail=n]

Depending on the degree of detail, the XML file contains different information:

• detail=0 (default)

This only issues the CPU load (in %):

<?xml version="1.0" encoding="UTF-8" ?>

- <load>

<cpuload cpu="0" load="73.9" loadunit="%" />

</load>

• detail=1

The total load and the distribution to the individual simulation tasks are issued.

• detail=2

In addition, all real-time processes are issued.

• detail=3

In addition, all non-real-time processes are issued.

• detail=4

In addition, all commands are issued.

3.3 Benchmark Indicator

To compare the simulation performance of RTPC-EVE Target PC on different PCs,a standardized calculating routine can be used.

Include the header file

rtpc-benchmark.h

in any C code module and run one of the following routines:

double rtpc_benchmark_standard1(double salt);

double rtpc_benchmark_standard2(double salt);

The first routine calculates 2000 variables with 8000 instructions, the second 50variables with 400 instructions – arguments and return values have no signifi-cance.


Operation ETAS


ETAS Configuration for EVE Use Cases on the Target PC

4 Configuration for EVE Use Cases on the Target PC

This chapter describes the uses and configuration of RTPC-EVE Target PC withthe web interface.

4.1 Applications

There are three applications for RTPC-EVE Target PC:

1. Model-in-the-Loop (MiL)

2. Hardware-in-the-Loop (HiL)

3. Hardware-in-the-Loop with Measuring and Calibration Access (M&C)

4.1.1 Model-in-the-Loop (MiL)

In component tests, the Unit-under-Test consists of a model of a controller func-tionality written in software. No I/O hardware is necessary.

The following setting has to be made:

Tab. 4-1 Setting for MiL Use

4.1.2 Hardware-in-the-Loop (HiL)

Complete ECU SW tests are the standard application for RTPC-EVE Target PC. InHiL operation, the Unit-under-Test exists as hardware. It is connected to the testsystem via I/O boards.

The real-time PC addresses the I/O hardware via an Ethernet connection. Nor-mally, the Eth1 (HW) port of the real-time PC is used.


Tab. 4-2 Setting for HiL Use

4.1.3 Hardware-in-the-Loop with Measuring and Calibration Access (M&C)

With ”HiL with measuring and calibration access”, it is possible to access the UuTsimultaneously during test operation using serial protocols (e.g. XCP).

Measuring and calibration access can be realized using a compact ES590 ECUinterface module. The ES590 and RTPC are connected directly to the user PC viaan ES600 network module.

Parameter Setting

RTPC_USAGE_ETH1...RTPC_USAGE_ETHn

Off...Off

Parameter Setting

RTPC_USAGE_ETH1 ES1130


Configuration for EVE Use Cases on the Target PC ETAS


Tab. 4-3 Settings for HiL Use with Measuring and Calibration

4.1.4 Hardware-in-the-Loop with Load and Error Simulation

If an ES4408 system is used to simulate loads or an ES4440.1 Compact FailureSimulation Module to simulate errors, these modules communicate with the real-time PC via Realtime UDP (rtudp).

The following settings then have to be made for the relevant Ethernet ports onthe real-time PC:

Tab. 4-4 Settings for Systems for Load or Error Simulation

4.1.5 Massive I/O

Massive I/O means that the HiL system can be assigned a large number of I/Ochannels. With VAP Target PC V1.0, this means that up to four VME/VXI I/O sys-tems (ES4100, ES4105, ES4300) are supported.

Each system is controlled by a System Controller Board. To ensure real-time datatransfer, there is a a point-to-point connection between the real-time PC andeach I/O system. The DVE model thus has access to all I/O boards regardless ofthe system the individual board is contained in.

The following settings have to be made:

Tab. 4-5 Settings when Using Several I/O Systems (Massive I/O)

Parameter Setting

RTPC_USAGE_ETH1 ES1130

Note

For details of ordering of measuring and calibration hardware, refer to the ordering information

Parameter Setting

RTPC_USAGE_ETHn rtudp_x (x = 0...4)

Parameter Setting

RTPC_USAGE_ETHn ES1130, ES1130_1, ES1130_2 or ES1130_3



4.2 The Web Interface

You can do the following via the RTPC-EVE Target PC web interface:

• configure RTPC-EVE Target PC

• install software updates

• display status messages and system information

The access to the web interface, navigation within the interface and the func-tions are described in this section.

4.2.1 Access to the Web Interface

You can access the web interface of VAP Target PC V1.0 via the URL

http://192.168.40.14

Simply launch a web browser on the user PC and navigate to this address.

Instead of the IP address 192.168.40.14, you can also use the alias ”rtpc” ifyou declare it in the Windows system file hosts. Depending on the operatingsystem, this file is in one of the following directories:

Add the following line to the existing entries:

This makes it possible to reach the web interface of RTPC-EVE Target PC via theURL http://rtpc.

4.2.2 Navigation

The navigation line directly under the blue headline is an orientation guide in theweb interface Y

You can also return (when the simulation controller is stopped) to higher-orderpages, e.g. the ”Main Page”, quickly using the navigation line.

Not all functions of the web interface can be invoked in the operating modes”Simulation Controller” and ”Ethernet Bridge”. Once the web interface hasbeen started, you are automatically led to the relevant subpages.

The following functions are available when the simulation controller is running:

• System Info

This is where you obtain information on the system and find log files. For more details, refer to the section "System Info" on page 29.

• Runtime Trace

This is where you can start runtime traces in which processes and tasks are logged on the real-time PC.

• CAN Trace

The CAN Trace functionality enables the monitoring of CAN traffic to and from the IXXAT CAN cards.

Operating System Directory Path

Windows XP C:\WINDOWS\system32\drivers\etc\hosts

Windows 2000 C:\WINNT\system32\drivers\etc\hosts

192.168.40.14 rtpc



• Model Step

This function enables step-by-step execution of the simulation.

• Power Control

This is where you can shut down or reboot the system (see "Power Con-trol" on page 23).

4.2.3 Functions

The following figure shows an overview of the RTPC-EVE Target PC web interfacestructure and how the different web pages can be accessed in the relevant oper-ating modes.

Fig. 4-1 Structure of the Web Interface

The individual pages are described in detail below.

SimulationController

Main Page

Ethernet Bridge

Power Control

Configuration

Installation /Update

System Info

Documentation

ApplySoftware Update

InstallSoftware Image

Idle / ConfigurationMode


Ethernet Bridge


Mode

EthernetBridgeMode

Power DownMode

Tools

LicenseManagement



Main Page

All functions of the RTPC-EVE Target PC web interface can be selected via theMain Page.

Simulation Controller, Ethernet Bridge

These menu items are used to start the relevant operating modes ”SimulationController” and ”Ethernet Bridge”. The operating modes have already beendescribed in the section "Operating Modes" on page 15.

Once an operating mode has been activated, only the relevant subpages can beaccessed.

Power Control

If the on/off switch on the real-time PC is not accessible or does not exist, RTPC-EVE Target PC can be shut down or rebooted using this web interface link.

To boot RTPC-EVE Target PC via the network (”Wake-On-LAN”), you require acorresponding tool on the relevant network PC to send the ”magic packets”(e.g. the free tool ”WOL - Magic Packet Sender 2007”). Data on how to config-ure this tool can be found under ”Wake On LAN Settings”.

Configuration

This is the configuration dialog of RTPC-EVE Target PC which consists of fourparts:

• Automatic Configuration (”Configuration Support”)

– Automatic Component Configuration

Automatically configures the Ethernet connection(s) (Eth1...Ethx). The real-time Ethernet connection is checked and – if a component is con-nected – the ”RTPC_USAGE_ETH1“ parameter is set to the value ”es component”.

Refer to "To run the configuration" on page 11 for a description of autoconfiguration.

– Component Detection

Checks whether the connection to the component works.

Note

The ”RTPC_USAGE_ETHn” parameter is only displayed if the relevant Ethernet interface has also been configured.



• RTPC-EVE Configuration

The ”RTPC-EVE Target PC Configuration” section is used for setting the configuration mode and activating the debug options.

– RTPC_USAGE_ETHn

This parameter is used to configure the Ethernet connections of the real-time PC to the ES1130 Simulation Controller Board. The Ethernet connections are referred to in the real-time PC as ”Eth0”, ”Eth1”, etc..

”Eth0” is used for the connection of the real-time PC to the user PC – ”Eth1”, ”Eth2” etc. can be used to connect a component.

– Details on the real-time UDP (rtudp) driver API can be found on the web interface at http://192.168.40.14/api/rtudp.html. Individual Ethernet connections can be configured in Bridge mode here (see sec-tion 3.1.3 on page 16).

– RTPC_POWER_UP_MODE

This parameter specifies the operating mode for RTPC-EVE Target PC after start.

The following values can be set:

idle: RTPC-EVE Target PC starts in ”idle” mode. This mode is used for configuration and system update.

simulate: RTPC-EVE Target PC starts in simulation mode. RTPC-EVE Target PC cannot be configured in this mode.

bridge: RTPC-EVE Target PC starts in ”Ethernet Bridge” mode, i.e. the Ethernet interfaces of RTPC-EVE Target PC are connected logically. RTPC-EVE Target PC cannot be configured in this mode.

– RTPC_MODEL_AUTOSTART

This parameter is used to determine whether the simulation model is launched as soon as RTPC-EVE Target PC has been booted.

Possible values are ”yes” and ”no”. If ”yes” has been selected, the simulation model last downloaded is automatically started.

Note

To identify the card assigned to the Ethernet interface ”Eth_n”, use the mouse to click Blink.

Note

However, without the experiment environment, the functions - downloading parameter files - configuring inports - controlling signal generators - operating the Data Logger - changing the setting of modules for signal conversion

are not available.



– RTPC_LOG_LEVEL

Events are logged and written to a file during RTPC-EVE Target PC operation. The level for the events to be logged can be set here – ”debug” logs all events, ”emerg” only logs those that make the sys-tem unusable. A useful setting for normal operation is ”warning” or ”error”.

– RTPC_TASK_MONITOR_0/1

The task monitor makes it possible to monitor two tasks during run-time. The task to be monitored can be selected here by its number.

While the task is active, the relevant bit (0 or1) at the LPT interface is set to ”High”. This can be monitored using an oscilloscope. Note that using the task monitor causes a processor load on the RTPC-EVE Target PC. To deactivate the task monitor, set the values to ”-1”.

The following table lists the assignment of the relevant pins of the 25-pin DSUB connector, LPT.

– RTPC_TASK_TIMING_STATISTIC

This parameter defines the recording frequency (in seconds) for the statistics of the task runtimes. ”0” deactivates recording.

The statistics contain the following information:

- minimum/maximum time dt (in ns) between two task activations

- minimum/average/maximum runtime (in ns) of the task

Note

The automatic starting of the simulation model only works if the ”RTPC_POWER_UP_MODE” option (see above) has been set to ”simulate”.

Pin Function

2 Data bit 0

3 Data bit 1

18 - 25 Ground

Note

The statistics are not output in real-time mode to prevent any distur-bances of real-time behavior. The measuring functions are not imple-mented atomically. Individual events may therefore go missing.

Note

The recorded events depend on the value of the ”RTPC_LOG_LEVEL” parameter (see page 25).



– RTPC_INVALID_CPU_CORE_HANDLING

This parameter determines how to handle an invalid specification of CPU cores. Possible values are "warn" (default) and "stop".

"warn": If, in the OS Configuration, non-existent cores are specified, a warning is issued in the RTPC-EVE Target PC log file and all real-time tasks are run on a single CPU core.

"stop": In the case of an invalid specification of CPU cores, the real-time model does not start and an error message is issued in the RTPC-EVE Target PC log file.

– RTOS_TASK_STACKSIZE

RTPC-EVE Target PC uses a separate stack for each running task. The size of this stack (in kB = 1024 Byte) can be defined using this param-eter. A useful value is 1024 kB.

– RTOS_TRACE_BUFFERSIZE

RTPC-EVE Target PC has an automatic internal serial protocol which is useful when, for example, tests are carried out to assess the perfor-mance of simulation models.

This parameter is used to determine the size of the buffer (in the unit ”number of events”) before the data is written to a protocol file (*.rtt). This file can be accessed using Main Page ∅ Simulation Controller ∅ Trace File Access and then displayed and analyzed with RTA-TRACE.

– RTPC_COMPILE_OPTIMIZATION

RTPC-EVE Target PC uses the GNU C Compiler ”gcc”.

Code generation optimization can be set in 4 steps (0 ... 3) which cor-respond to the gcc compiler options -O0 ... -O3. The larger the num-ber, the better the optimization - this does, however, also mean that more time is required for compilation.

If you are not sure about this setting, select ”1” or ”2”.

– RTPC_COMPILE_LINK_DEBUG

If you set this parameter to ”yes”, the compiled object files and the executable file are assigned debug information. This can be useful when detecting errors in the simulation model (see "Debug/Disassem-ble" on page 30).

Note

If models with lots of tasks are used, the stack size may have to be reduced due to the limited size of the RAM.

Note

Only set this option if it is absolutely necessary as the executable file becomes very large as a result.



• RTPC_COMPILE_SWAPSPACE_MB

When using large Simulink models, the C files generated can be very large. This can lead to the computer not having enough disk space available.

This parameter enables you to make additional disk space available for the compilation phase. This space is in the compile.swapfile file and is only used for the compilation of the model, not for the simula-tion.

Possible values are 0, 256, 512, 768 and 1024 - these figures specify the size of the swap file on the hard disk in megabytes.If the value is set to 0, any swap file created previously is deleted. The value is set to 0 by default - if there are no problems during compila-tion, continue to use this setting.

– RTPC_NAME

This is where the particular real-time PC can be assigned a name. This name is helpful if the user is working with several RTPC-EVE Target PC systems - it is shown both on all web interface pages and in the browser title.

The selected settings are saved using the Save Configuration button.

• PCI Express® Hardware Configuration

This is where the logical IDs of the ESX335 instances are assigned to the physically available ES1335 boards (in the VME system) and ES5335 boards (in PCIe slots) (see ES5335.1 User’s Guide).

• System Configuration

This part is used to configure the PC hardware. The options are automat-ically set correctly the first time RTPC-EVE Target PC is booted. Modifica-tion is therefore not necessary.

If an Ethernet interface is installed at a later date, the ”RTPC_SYS_ETHn” (n = 1 ... 4) option has to be changed from ”None” to ”present”.

Save your selection by clicking the System Configuration button.

• System Boot Settings

RTPC-EVE Target PC saves two complete software versions on separate partitions of the real-time PC. This enables a risk-free return to a familiar software version.

You can select which software version is to be used when the system is next booted in the selection box. This selection is saved using the Set Boot Version button.

Reboot System restarts RTPC-EVE Target PC with the selected software version.

Installation/Update

• Apply Update

The current RTPC-EVE Target PC version can be updated with software updates via the web interface. These software updates can be obtained directly from ETAS.



• Under ”Upload Update File” click the Browse... button to select the file with the update (extension *.tgz).

• Select Upload to transfer the file to the real-time PC.

The uploaded file is now selected under ”Select Update to Apply”.

• If several updates have been uploaded, select the relevant update to be activated.

• Under ”Select System to Update” select the soft-ware version to be updated. The software version currently active is shown (”Active”).

• Click the Apply Update button.

Updates carried out to date are listed under ”Applied Updates”.

Under ”Delete Installed Update Files” you can delete files no longer required.

• Activate the files to be deleted and click Delete.

• Install New Version

The ”Install New Version” function is used to execute a complete new installation. RTPC-EVE Target PC saves all software versions installed to date from DVD on the hard disk of the real-time PC. These versions can be written back to any partition.

There are two ways of making installation files available on the hard disk of the real-time PC:

– ”Copy Software Image from Installation DVD to Hard Disk”

The image of the DVD in your workstation is transferred to the real-time PC.

– ”Upload Image file”

An image (on your local system or on a network resource) is trans-ferred to the real-time PC.

The images provided in this way can now be selected using ”Select Soft-ware Image” (see below).

• Select the partition installation should take place in under ”Install Partition”.

Every partition except the active one can be over-written.

• Select which version is to be installed under ”Select Software Image”.

• Use the ”Use the existing configuration....” option to specify whether the existing configuration of RTPC-EVE Target PC is to be used for this version or whether standard values are to be used.



• If you leave the ”Skip implicit updates” option dis-abled, all available updates for the relevant soft-ware version are also automatically installed.

• Click Install.

The version to be booted is selected in ”Configure RTPC” (see "System Boot Settings" on page 27).

The repartitioning of the hard disk, which from VAP Target PC V1.0 can contain four (instead of the previous two) partitions, can be executed under ”Repartition Hard Disk”.

Images on the hard disk of the real-time PC which are no longer needed can be marked under ”Delete Installed Software Images” and then deleted using Delete.

• Clone Installed Version

You can clone versions of RTPC-EVE Target PC that have already been installed by generating an installable file (*.tgz) and downloading this file to your operating PC. For a detailed description of this procedure, refer to the section "Cloning Installed Versions" on page 12.

System Info

The ”System Info” function shows various information on the status of RTPC-EVETarget PC. If an error occurs, this page can be saved and used for analysis pur-poses.

• Log File messages

The messages recorded are shown in this window. It is also possible

– to have the complete file displayed (View complete log file),

– to generate a ZIP archive which contains the log file as well as other files with system information (Generate ZIP file report) or

– to generate an encrypted ZIP archive (Encrypted ZIP).

• Realtime Process Report

This provides detailed information on running real-time processes.

• System Information

System information of the real-time PC is shown here.

• CPU Performance Monitor

Uses the "CPU Performance Monitor" registers to analyze CPU perfor-mance.

• I/O Hardware Information

This provides detailed information on the connected I/O hardware.

• Applied Updates

Contains information on installed updates.

Note

As the ETAS firewall only accepts encrypted ZIP files, you must select this option if you want to send a report archive to ETAS by e-mail.



• Debug/Disassemble

If the ”RTPC_COMPILE_LINK_DEBUG” parameter has been set (see page 26), the model can be examined here for errors.

Documentation

The hyperlink ”Documentation” leads you to a directory containing the follow-ing documents:

– The manuals (English) on VAP Target PC V1.0

– The current release notes

– A list of PCs approved by ETAS

– Two documents with information on the BIOS settings of the PCs from ETAS


ETAS Troubleshooting

5 Troubleshooting

This chapter presents the description of some typical problems with possiblesolutions.

When the RTPC-EVE Target PC is started up, the sequence of error notes is played

Cause. The Simulation Controller could not be started.

Remedy.

The RTPC-EVE Target PC Web interface cannot be accessed

Cause. Ethernet connection does not exist, is defective or the settings are incor-rect.

Remedy 1. Execute the command ping 192.168.40.14. If you receive ananswer from the RTPC-EVE Target PC, check the settings of your Web browser(e.g. proxy settings).

Remedy 2. If you do not receive an answer from the RTPC-EVE Target PC, checkthe Ethernet cable. Make sure that you are using a crossover cable.

Remedy 3. If the cable is OK, check the configuration of the Ethernet interface(IP address: 192.168.40.240, net mask: 255.255.255.0)

Remedy 4.

In your Internet configuration, a proxy server is configured for the LAN. To beable to access the the RTPC-EVE Target PC web interface, the IP address of thereal-time PC (192.168.40.14) must be included in the list of exceptions thatshould not use the proxy server.

To do so, proceed as follows:


Troubleshooting ETAS

• In the Windows Start menu, select Settings ∅ Control Panel ∅ Internet Options.

The "Internet Properties" window opens.

• Select the "Connections" tab and click LAN set-tings.

The "Local Area Network (LAN) Settings" window opens.


ETAS Troubleshooting

• Click Advanced in the "Proxy server" field.

The "Proxy Settings" window opens.

• Enter the IP address of the real-time PC in the "Exceptions" field (192.168.40.14).

• Close one window after the other with OK.


Troubleshooting ETAS


ETAS Appendix

6 Appendix

6.1 The Real-Time PC in a Virtual Machine

This section describes how to create a “virtual” real-time PC. This kind of virtualreal-time PC is useful for all test and configuration procedures which do notrequire test hardware.

You require:

• An installed version of VMware Workstation

• The supplied files for the virtual machine (configuration and virtual disk image)

• The disk image of the RTPC-EVE Target PC installation DVD

6.1.1 Configuring the VMware Network Adapter

After the installation of VMware Workstation and the subsequent reboot of thehost operating system, you will find two new network adapters in the Start menuunder Settings ∅ Control Panel ∅ Network Connections:

• VMware Network Adapter VMnet1

• VMware Network Adapter VMnet8

Note

The application case described below was developed by ETAS engineers and is particularly suitable for training and practice purposes. It can happen that functionality is not available in full on certain systems or is no longer available after a change of software versions. ETAS cannot provide support in this case.

Note

If you use a real Ethernet board for the connection to your RTPC-EVE system (see “HW” in the figure), disable it as it could otherwise cause a conflict.


Appendix ETAS

To configure the network adapter

• Double-click “VMware Network Adapter VMnet1”.

The “VMware Network Adapter VMnet1 Status” window opens.

• Click Properties.

The “VMware Network Adapter VMnet1 Proper-ties” window opens.

• Disable all components apart from “Internet Proto-col (TCP/IP)”.

• Select the “Internet Protocol (TCP/IP)” component and click Properties.

The “Internet Protocol (TCP/IP) Properties” window opens.


ETAS Appendix

• Enter the following information:

– IP address: 192.168.40.241

– Subnet mask: 255.255.255.0

• Click OK and exit the network configuration.

6.1.2 Creating the Virtual PC

To create your virtual PC, proceed as follows:

• Copy the zip file RTPC-VmwareImage-Empty20GBDisk.zip into a new directory in your file system and unzip it there.

Your directory then contains two files:

– RTPC.vmx

The configuration file of the virtual machine.

– RTPC.vmdk

The virtual image file of the hard disk – this describes a PC with 256 MB RAM and an empty 20 GB hard disk.

• Open the RTPC.vmx file in a text editor. You will find the following line in it:

.....

ide1:0.filename="path to image file (*.iso)"

.....

• Adjust the path to correspond to where you have saved your RTPC-EVE Target PC image file and then save the file.

To boot the virtual PC

• Double-click the RTPC.vmx file.

The VMware application opens. As the virtual hard disk contains no operating system, the system is booted from the virtual CD-ROM drive (i.e. the *.iso file specified previously).

• Select “Standard Install” and follow the instructions displayed by the installation program.

• If you are prompted to reboot the real-time PC, click on the CD-ROM icon to disable this drive.

• Reboot the system.

• The virtual PC now boots from the virtual drive with the RTPC-EVE Target PC software.

To test the reachability of RTPC-EVE Target PC

• Toggle to the host.


Appendix ETAS

• Select Run from the Start menu.

• Enter “cmd”.

The command prompt opens.

• Enter the following:ping 192.168.40.14

• Alternatively, you can open the web interface (http://192.168.40.14) in your browser.

6.2 How to integrate the Virtual Box for RTPC - Setup of Oracle VirtualBox

This chapter describes how to setup Oracle VirtualBox as container for an ETASVirtual ECU.

6.2.1 System Preparation

If you are using an Intel Multicore System, it is necessary to enable Intel Virtual-ization Technology in the BIOS in order to run a Dual core based virtual machine.The necessary steps vary depending on the PC-manufacturer, the general actionsare described below.

Enabling Intel Virtualization Technology in the PC/Notebook BIOS

• Power off the notebook.

• Power on and enter the BIOS setup (common keys are e.g. <DEL>, <F10>, <F2>).

• Select Config, Select CPU and enable the features Intel Virtualization Technology and Intel VT-d Feature.

• Save changes and leave the BIOS.

• Power off the computer completely and reboot.

6.2.2 Setup and Configuration of VirtualBox

1. Install VirtualBox. The installation of VirtualBox is provided with ISOLAR-EVE.Be sure to check the corresponding checkbox during ISOLAR-EVE setup process.During installation select all installation packages offered by the installer.

2. Prepare VirtualBox


ETAS Appendix

Open VAP-RTPC DualCore 80GB Disk.vbox from the ISOLAR-EVE installation folder: C:\Program Files\ETAS\ISOLAR-EVE1.0\virtualbox-RTPC-EVE 80GB Disk

• Set as shown below, choose Datei für virtuelle CD/DVD… RTPC-EVE-V1.0.0#9574.iso and click OK. The RTPC-EVE .iso image will be delivered by ETAS.

• Note, if you start the Virtual Machine for the first time, you might get a different dialogue which will enable you to select the RTPC .iso image file

• Click Start. Now the RTPC will be boot after a short timeout – if any dia-log boxes and warning pop up, just say OK.

3. In the virtual console window select Install RTPC software. This will run theinstallation of RTPC in the VirtualBox. This might take a while.

4. Reboot RTPC.

5 Set the IP address of the “VirtualBox Host-Only Network” – Adapter in theWindows system settings as shown in the following screenshot.

.

6. You can now access the RTPC by typing http://192.168.40.14 into your webbrowser.

6.3 Setup of VMware

This chapter describes how to setup VMware for an ETAS Virtual ECU.

6.3.1 Setup and Configuration of VMware Player

Open VMware Player, create a new virtual machine and select the RTPC-EVE ISOimage provided to you by ETAS with the settings shown below:


Appendix ETAS

Operating system type for RTPC-EVE when creating a new virtual machine inVMware Player.

In the next step, configure 80GB as the Maximum disk space (GB) and select theoption Store virtual disk as a single file.

After that, you can configure the hardware settings for the virtual machine. Here,configure the network adapter as a Host-only adapter as shown in the nextscreenshot.

Host-only network adapter configuration in VMware Player.

Now, you should be able to configure the IP address settings for TCP/IPv4 in theWindows settings. Make sure to use the same IP address as described before(192.168.40.240 / 255.255.255.0).


ETAS Appendix

6.4 Install the RTPC-EVE license via HTTP Interface:

Before being able to work productively on the RTPC-EVE, you need to upload alicense to the RTPC-EVE. For doing this, go to the Web interface of the RTPC-EVEand follow the steps below:

• Stop simulation controller

• Main Page

• License Management

• Upload license file

• Main Page

• Simulation Controller

• Start Simulation Controller

The RTPC should now be available as a target in ISOLAR-EVE.


Appendix ETAS


ETAS ETAS Contact Addresses

7 ETAS Contact Addresses

ETAS HQ

ETAS GmbH

ETAS Subsidiaries and Technical Support

For details of your local sales office as well as your local technical support teamand product hotlines, take a look at the ETAS website:

Borsigstraße 14 Phone: +49 711 89661-0

70469 Stuttgart Fax: +49 711 89661-106

Germany WWW: www.etas.com

ETAS subsidiaries WWW: www.etas.com/en/contact.php

ETAS technical support WWW: www.etas.com/en/hotlines.php


ETAS Contact Addresses ETAS


ETAS Index

IndexAAutomatic configuration 23

BBenchmark indicator 17BIOS

Settings 8

CCAN Board 14Clock Synchronization 13Clone

install versions 29Configuration 19CPU Core Load 17CPU Performance Monitor 29

DDelivery scope 7

EETAS Contact Addresses 43

HHardware requirements 7Hardware-in-the-Loop (HiL) 19

IInstallation 8

MMassive I/O 20Model-in-the-Loop (MiL) 19

OOperating mode

Ethernet Bridge 16Idle/Configuration 15Power Down 16Simulation Controller 15

PPCI Express Hardware Configuration

27

RRealtime Process Report 29RTOS_TASK_STACKSIZE 26RTOS_TRACE_BUFFERSIZE 26RTPC_COMPILE_LINK_DEBUG 26RTPC_COMPILE_OPTIMIZATION 26RTPC_COMPILE_SWAPSPACE_MB 27RTPC_INVALID_CPU_CORE_HANDLING

26RTPC_LOG_LEVEL 25RTPC_MODEL_AUTOSTART 24RTPC_NAME 27RTPC_POWER_UP_MODE 24RTPC_TASK_MONITOR_0/1 25RTPC_TASK_TIMING_STATISTIC 25


Index ETAS

RTPC_USAGE_ETHn 24

SSystem Boot Settings 27System configuration

HiL test system 10System requirements 7

TTroubleshooting 31

VV1.0 R01 EN - 06.2012 2V1.0 R01 EN - 10.2012 2VMEbus reset 15

WWeb interface 21

functions 22navigation 21

etas rtpc-eve v6.0 installation guide for target pc€¦ · etas rtpc-eve v6.0 - installation guide...

Documents