Hi, my name is Heiner Hild. I am Product Manager for the VT System, which I will briefly introduce to you today. The VT System is a product from Vector that extends the test automation capabilities of CANoe specifically for I/O tests. With this system we can integrate ECUs like this as a Device Under Test in CANoe. In so doing all components required for testing ECU inputs or outputs are integrated in modules. Based on scalability, test systems with different complexity and functionality can be configured: large cabinets like this as well as small desktop systems for developer work stations. With the help of the VT System, developers are able to manipulate I/O interfaces of ECUs during function tests and to record and transfer data to CANoe. In addition, we have the capability to run automation programs and simulate ECU models in CANoe. This is what it looks like in CANoe: By using VT modules we can directly access system variables, which are then automatically created. Let me explain this with an example: What we have in front of us is a configuration dialog. Let’s assume a typical VT component such as, for example, this simulation module, which can manipulate inputs of an ECU. The functional blocks of the module can be seen in the graphical display: here a voltage generation component, there a decade resistor for sensor simulation. Application example for this: a temperature sensor. If this sensor becomes warmer, the resistance changes. We can reproduce that here. Instead of a real resistor, a simulated resistor can be used. Of course, the whole thing can be configured. Here you can manually set the switch state of the module. The corresponding program code for automation of the configuration is then visualized in various programming languages in this window: in CAPL, C#, or even Visual Basic .NET. All measured variables or I/O variables are visible as system variables on the right side and are thus also available in CANoe. A special feature: The namespace can be individually adapted. This means: By using descriptive names you can document the project-specific configuration of the module and recognize exactly where you are at the programming level. In this way you can reproduce the entire I/O configuration, create a stimulation / simulation of the environment, and start a test automation in combination with CANoe that runs automatic test scripts. Here is a small example: What we see in front of us is a so-called Panel. This is a feature of CANoe that is used to manually control tests from a graphical user interface. If, for example, you activate a switch in this program window, a signal will be generated in the simulated ECU that is subsequently transferred to a real bus and is received as a real CAN signal by the ECU in the HIL cabinet. The ECU that you see here contains functionality that generates a corresponding output at a pin that causes the light to illuminate or flash. At the same time, the VT System measures the output at the pin and displays that actual measurement on the computer. In this case we have a PWM-simulated signal. We could now adapt the duty cycle. You see that the brightness of the flashing phase changes. The set value is displayed here and the value measured by the VT System at the ECU output can be seen here in the Duty Cycle. This loop is now practically closed. That is why we also refer to this as “Hardware-in-the-Loop”. Here is what we have done; We have integrated an ECU – a so-called Device Under Test – into a complete circuit and linked it with CANoe from the simulation / stimulation side. From the automation side you can also create entire test programs. With vTESTstudio, the test design tool from Vector, you have full access to the signal as well as to the system variable database. Automated ECU tests can therefore be easily programmed with this development environment. Let’s look at the whole thing using an example. Here we have a pre-programmed script that is currently running. You see occasional flashing and the relays are switching: the system is in use. During the test run it is displayed where we are in the program flow, how much time has passed, and whether the test results are positive or negative. In other words: whether the verdict is “passed” or “failed”. After conclusion of the test, an HTML report is generated in which you can see everything once again. This was a brief outline of the possible applications of the VT System, which fits seamlessly into the Vector world based on its architecture and configuration. It can be used separately or in combination with CANoe. Due to its full integration in the Vector test tool landscape, it can also be used in combination with the vTESTstudio test design tool and the vTESTcenter test data management. So far, so good. That’s it from me on the VT System. Thank you very much!