AutomationDesk. Remote control of calibration, measurement, and diagnostic tools such as CalDesk. Open COM API to remote-control test execution

Transcription

1 AutomationDesk 2.0 Automated Hardware-in-the-Loop (HIL) Testing New-Look of User Interface NEW: Advanced Sequence Builder NEW: Offline Test Execution & Development NEW: Enhanced Multi-User Support dspace

2 Test and Experiment Software AutomationDesk Environment for powerful and convenient test automation Key Features Automated hardware-in-the-loop (HIL) testing Remote control of calibration, measurement, and diagnostic tools such as CalDesk Open COM API to remote-control test execution Real-time testing using Python scripts Version Control Interface New appearance of user interface NEW: Advanced Sequence Builder NEW: Offline test execution and development NEW: Enhanced multi-user support Description Key Benefits AutomationDesk is a powerful front end for automated hardware-in-the-loop (HIL) testing of the application software or diagnostic functions of electronic control units (ECUs). Controller functions are tested either in blackbox tests, or in whitebox tests that measure the ECU s internal variables. Measurement data from test benches or test drives can be replayed, and test maneuvers are driven precisely. With the AutomationDesk test automation tool, tests can be executed at any time, for example at night or over the weekend. This increases test coverage and the quality of the ECU software while saving time and costs. Comprehensive Test Environment With AutomationDesk you can create test automation tasks either graphically or via script programming and run them on the host PC of your HIL simulator. In addition to the graphical Sequence Builder, AutomationDesk makes it easy to organize the handling of tests, test data, and test results. AutomationDesk provides libraries containing a wide range of automation blocks to develop complex tests or to access further hardware and software. Their functionality can be easily extended by using multiple custom libraries if required. 2

3 AutomationDesk Functionality Overview Functionality Advanced Sequence Builder Test management and execution Automation libraries Open architecture Test documentation Real-time testing with Python scripts Description Graphical test development Increased information density Bookmarks and overview window for fast and easy navigation Zooming Print and picture export Using drag & drop for test development Accessing real-time simulations from within the automation sequences Managing test projects, data, and results Offline test execution and development Setting up individual project structures Seamless integration into the development process Consistency checks before run-time Real-time stimulus Replay measurement data (in real time) Report library to define the contents of the generated report Access to real-time simulation models Remote control of ControlDesk Access to electrical failure simulation Access to Softing s Diagnostic Tool Set DTS7 Access to remote calibration (COM) with INCA, CANape, and CalDesk, via ASAM-MCD 3MC automation interface Remote Diagnostics (COM) Library, compliant with ASAM-MCD 3D (Version 2.0.1) Test Framework library to simplify the development of complex tests Access to MATLAB Open COM API to remote-control test execution Calling Python scripts from within AutomationDesk Extendable libraries Im- and export of custom libraries Support of Microsoft Source Code Control (SCC) Interface to integrate version control systems Interfacing to third-party-tools via COM/DCOM (on request) Automated generation of test reports in PDF or HTML Python tests executed synchronously to simulation model Read and write access to model variables in every simulation step possible Concurrent execution of several independent test scripts No need for simulation model modification Order Information Product AutomationDesk AutomationDesk - Automation Server Order Number AUD AUS Relevant Software and Hardware Software Required Operating system: compatibility Order Number Hardware Order Number Required Minimum PC system Pentium III processor, 1 GHz Memory 512 MB RAM 350 MB free disk space Recommended PC system Pentium 4 processor, 2.0 GHz or higher Memory 1024 MB RAM 350 MB free disk space 3

4 Test and Experiment Software Test Development AutomationDesk s Sequence Builder Graphical and Python-based Test Development AutomationDesk s Sequence Builder provides a graphical, UML-compliant environment for developing automation sequences. The Sequence Builder and its overview panel help you keep track of even very large sequence structures. AutomationDesk combines and integrates graphical and Python-based test development. Typically, graphical development is used to describe the control flow and to access devices like hardware or further software. Python scripts are used for implementing algorithms or for userspecific extensions. Developing and managing automation sequences with AutomationDesk. Editor for Python-based test steps. Reusing Automation Tasks If a test sequence or single test steps need to be reused for similar automation tasks in other projects or sequences, they can be stored in custom libraries. The custom libraries will gradually grow to contain more and more reusable elements, so you can benefit from accumulated know-how in future projects. This method speeds up the test development process and increases efficiency. Different custom libraries can be shared between different AutomationDesk installations via the file system or via a version control system. Create your own libraries in the Custom Library node. Functional Overview Development of test sequences Predefined test steps Edit and maintain program flows Block layout based on UML standard Zoom and bird s eye view Print and picture export Bookmarks in program flows for fast navigation User control via mouse, short-cut keys and toolbars Different layout profiles Integrated Python Editor 4

5 AutomationDesk Test Management and Execution Managing Project Data AutomationDesk s Project Manager provides a way of organizing the sequences, data, and results of test projects in a structured representation. It also enables you to reproduce tests, for example, to perform them repeatedly ( regression testing ). The criteria for structuring tests can include different functions to be tested, different ECUs in a network, different development stages, and different users involved in a project. Project Manager in AutomationDesk. AutomationDesk s Project Manager Offline Test Execution & Development AutomationDesk s libraries can be set to offline mode, so that tests that use these libraries are executable even if required external software or hardware is not available. The test steps then use default behavior so that test execution is not blocked. For example, tests can be executed without a hardware-in-the-loop simulator being connected to AutomationDesk. The default behavior is defined by default return values either by the user or by recording them in an online test execution run. Libraries in AutomationDesk. Automatic Report Generation AutomationDesk can automatically generate report documentation based on the test results. You can select from a library of report test steps (such as AddText, AddTable, or AddPicture) to specify the report content. Additionally, there are various options for controlling the level of detail and the format of the reports. Reports are usually generated in HTML or PDF format, but almost any kind of output format can be generated by using additional XML style sheets. Typical test report generated automatically by AutomationDesk. Version Control of Projects and Custom Libraries With the AutomationDesk version control interface, you can integrate version control systems offering the Microsoft Source Code Control (SCC) interface, for example, Microsoft Visual SourceSafe, MKS Source Integrity, or IBM Rational ClearCase. Version control interface. 5

6 Test and Experiment Software Open Architecture Integration Into Customer-Specific Environments System Architecture A major objective of AutomationDesk is to be usable for a wide range of application areas. It has therefore been designed as a tool with open interfaces. AutomationDesk can be customized and integrated into customer-specific development environments. AutomationDesk provides a graphical user interface for creating and modifying test projects and test sequences. The user interface makes use of existing Python libraries, but hides the Python world. Due to its open architecture, it is possible to integrate new or third-party hardware and software components into AutomationDesk. Application programming interfaces (APIs) such as a DLL or COM interface can be wrapped into AutomationDesk s cooperation layer and thus used from within AutomationDesk. System architecture of AutomationDesk. 6

7 AutomationDesk Remote Control of AutomationDesk COM/DCOM Interface AutomationDesk has a COM-based application programming interface (API) for remote-controlling and automating selected Automation- Desk functions. These are some of its typical use cases: Programming batch processes (with Python, Visual Basic, C++, etc.): You can program flexible control structures which skip single test sequences if necessary or which execute test projects successively. Designing interactive GUIs: You can create your own test GUIs according to your requirements, for example, to provide a less complex user interface. Connecting other tools to AutomationDesk: Parameterize your test data, for example, in Microsoft Excel, and call the corresponding test sequences in AutomationDesk from Excel. The COM interface is language-independent and can be used to call almost all the functions available in AutomationDesk s Project Manager. These include: Loading and saving AutomationDesk projects Exporting and importing AutomationDesk projects Creating project trees Parameterizing data objects of Int, Float, and String type Executing projects, folders, and test sequences Querying the current execution status Querying test results (passed, failed, undefined) Generating test reports Test sequences from the Custom Library can also be instantiated via the COM API. However, test sequences cannot be edited via the COM API. Remote-controlled test runs Example of a client application for test execution via COM/ DCOM interface. Automation Server Variant of AutomationDesk The AutomationDesk - Automation Server, as an alternative to the full version of AutomationDesk, is a server variant without its own user interface. The Automation Server is accessed and remotecontrolled via the COM/DCOM interface, so the same functions are available as for the full version of AutomationDesk. This run-time version has the advantage of reduced license costs, making it useful wherever the comprehensive functions of the full version are not required, for example, in automated test execution on hardware-in-theloop simulators. 7

8 Test and Experiment Software Single-Source Testing and Diagnostics Remote control of CalDesk diagnostics Complies with ASAM-MCD 3D (Version 2.0.1) ODX-based diagnostics Diagnostics and hardware-in-the-loop (HIL) testing are brought together in AutomationDesk. You can use AutomationDesk to remote-control and automate the diagnostics functionality of CalDesk, dspace s universal measurement and calibration software. This means you have a completely integrated tool chain for HIL testing, ECU calibration, measurement tasks, and diagnostics from a single source, and difficult compatibility problems are a thing of the past. Diagnostics and HIL Testing Come Together Successful integration of ECU diagnostics into the hardware-in-the-loop (HIL) testing of ECU software is increasingly important. Automation- Desk is a standard solution for automated HIL testing that can address a variety of software tools: These include CalDesk, the measurement, calibration, and diagnostic tool, and diagnostic tools such as DTS and EDIABAS from Softing, and VAG Tester and DiagRA from RAConsult. Interfaces between AutomationDesk and CalDesk. Remote Control for Diagnostics with CalDesk AutomationDesk can be used to automate and remote-control CalDesk s ODX-based diagnostic functionality, as well as for automating measurement and calibration tasks as previously. AutomationDesk accesses CalDesk via the ASAM- MCD 3D automation interface. You can build test sequences graphically in the familiar way in AutomationDesk, using the Remote Diagnostics (COM) Library. This is an AutomationDesk library of the blocks needed for automating access to CalDesk s diagnostic functionalities. All Tools from One Source By using CalDesk and AutomationDesk, you avoid the difficult compatibility problems that often arise in practice when tools from different vendors have to be integrated. dspace offers you HIL systems plus measurement, calibration, and diagnostic tools from a single partner, with no complications. The smooth interaction between AutomationDesk and CalDesk is the basis for successful HIL testing. 8

9 AutomationDesk AutomationDesk s Process Integration Capabilities Tracing Test Specifications Across Tools The traceability of requirements is a key issue in developing software for electronic control units (ECUs). Tools like Telelogic DOORS support the management of any kind of requirement. The specifications for software tests are also frequently handled with DOORS. A special integration solution couples AutomationDesk with Telelogic DOORS. Test specification structures from DOORS can be transferred automatically to AutomationDesk test projects. The test results from AutomationDesk are also available in DOORS. This greatly improves traceability and coverage analysis in the software development process. AutomationDesk DOORS Connect & Sync Module The connection between AutomationDesk and DOORS is made by the AutomationDesk DOORS Connect & Sync Module. This synchronizes the data and structures of the two tool worlds, and exchanges parameters between them. Users can run AutomationDesk tests from within DOORS. Test results from AutomationDesk can be displayed in DOORS. The link between the two tools means that DOORS always has the current state of the requirements and the associated test results and thus the current quality status is available in one central document. Connection to DOORS Two-Way Exchange Individual DOORS objects correspond to specific, identically structured elements in Automation- Desk. If several test specifications have the same structure, based on predefined templates, the Connect & Sync module can convert them into AutomationDesk elements automatically. Test implementation in AutomationDesk no longer needs to be performed from scratch, as structures and parameters from the DOORS test specification can be used. Data flow between AutomationDesk and DOORS. 9

10 Test and Experiment Software On Request: Connection to Mercury Quality Center / TestDirector A Seamless Test Process AutomationDesk can be connected to the Webbased test management tool Mercury Quality Center (or Mercury TestDirector ) to provide the benefits of both tools. The result is a seamless tool-based test process from test requirement specification to defect tracking. Tests can be managed and selected in Quality Center and remotely executed in Automation- Desk. Quality Center is used to organize and manage all the phases of the test process, including test requirement specification, test planning, test runs, and defect tracking. Directly test-related tasks like test implementation, test execution, result analysis, and report generation are performed with AutomationDesk, which provides access to hardware-in-the-loop platforms, and to measurement, calibration, and diagnostics systems. Benefits of Both Tools Combining AutomationDesk with Mercury Quality Center provides the features and benefits of both tools: Seamless test process from test requirement specification to defect tracking Quality Center s process management facilities Graphical test development and access to dspace Simulator with AutomationDesk Central data storage within Mercury Quality Center Access to all AutomationDesk tests and results from any Quality Center client Test process with Quality Center and AutomationDesk collaboration. 10

11 Python-Based Testing The Interaction Mercury Quality Center consists of clients and a server (a database containing tests, defects, workflows, etc.). AutomationDesk and Quality Center are connected via a COM interface. Projects from AutomationDesk can be exported and added to the Quality Center database. Automa- tiondesk projects can be viewed, parameterized, and executed in the Quality Center client. AutomationDesk s test results and reports are added to the Quality Center database and can be viewed on any Quality Center client. On Request: Connection to Mercury Quality Center / TestDirector AutomationDesk can be integrated with test process management tools like Mercury Quality Center. 11

12 Test and Experiment Software Python-Based Test Automation Script Based Test Implementation Functional Overview Powerful script language Python for advanced applications, including script modules for a variety of applications Remote control of a complete hardwarein-the-loop environment, for example, for automated ECU testing Remote control of the Simulink simulation Interface to Microsoft Word and Excel Support of Python dspace Python libraries eters, control the electrical failure simulation hardware, remote control third party tools and much more. Extensive libraries based on the powerful scripting language Python serve as automation interfaces to ControlDesk and third-party tools like MATLAB and Microsoft Excel. This includes COM-based tool automation libraries as well as access libraries for real-time simulation hardware and several automotive ECU communication channels. Maximum of Flexibility and Extendability A common approach for automated testing is to implement test programs in the form of an executable python script ( You can simply write Python scripts in a text editor or using a standard Python development environment. Since you can define your own library modules this provides a maximum in terms of flexibility and extendability. There exist several library modules, e.g. to access a real-time model running on dspace Simulator, access diagnostic tools, read and write ECU calibration paramdspace Simulator Automation RTPLib Access to simulator variables, states and parameters SDMLib Description and generation of stimulus signals, import and replay of measurement data Diagnostics DTSLib VAGTLib 1) VASTLib 1) EDIABASLib 1) Access to the SOFTING Diagnostic Tool Set DTS Remote control of the VAG tester tool VAG1552 Access to the SOFTING EDICcard-based diagnostic interface VAS5163 Access to the SOFTING EDIABAS diagnostic tool Communication Interface RS232Lib Communication via the PC s serial port interface ASAP/ASAM Interface ASAP3Lib Remote control of external calibration tools (ASAM-MCD tools) using the ASAM-MCD 3MC (formerly ASAP3) interface ControlDesk Interface cdautomationlib Almost all classes and functions for automating ControlDesk are provided by cdautomationlib Further Program Interfaces wordlib To report to Microsoft Word documents via OLE automation excellib To report to Microsoft Excel spreadsheets via OLE automation matlablib To exchange data between MATLAB and the Python Interpreter, invoke MATLAB functions or to access files in the MATLAB file format 1) Available on request 12

13 Python-Based Testing Python-Based Real-Time Test Automation 100% reproducible real-time tests synchronously executed with simulation model Model variables can be observed and changed in every simulation step Real-time tests are implemented in Python (user-extensible via libraries) Several independent test scripts can be executed concurrently Dynamic test loading during model and test execution No model modification necessary for realtime testing Real-time test management by scripting and dedicated graphical user interface Easy integration into customer test frameworks (like AutomationDesk or others) Available for DS1005 and DS1006 (with multiprocessor support on single nodes) NEW: Python objects can be exchanged between real-time tests and PC Python script NEW: CAN support of real-time tests (based on RTI CAN MultiMessage Blockset) NEW: Support of Python Python for Real-Time Testing Describing Real-Time Tests in Python Automated testing usually is performed by executing tests on a standard PC connected to the hardware-in-the-loop (HIL) system. However, this method often cannot cope where greater timing precision is required for example, if ECU interaction has to be captured and responded to in a range of milliseconds. Python scripts for real-time testing coming with AutomationDesk are the answer. They run on the processor board of the HIL system in real time, i.e., synchronously with the model, so all test actions are performed on a real-time basis. This opens up expanded test options with dspace simulator. Reactive tests which respond to changes in model variables within the same simulation step can be implemented. Time measurements in tests are also far more precise, as there are no latencies in communication. Simulation step size is now the only limit to the maximum time resolution of measurements. Real-time-capable Python interpreter for the processor board. 13

14 Test and Experiment Software Python for Real-Time Testing Real-Time-Capable Python Interpreter A real-time Python interpreter, running on the processor board along with the model, allows the script to execute synchronously with the model. The interpreter can execute several real-time tests simultaneously and independently of one another. The tests can interact with the simulation model in real-time via the memory on the processor board. You can therefore observe and influence the ECUs connected to the HIL simulator in every individual simulation step. The Python interpreter is added to the application during the translation process via a Real-Time Workshop build option. You can formulate realtime tests using standard Python scripts from the real-time testing libraries provided with AutomationDesk (for example, for accessing model variables and executing several test branches within one real-time test in parallel). You can also create your own Python libraries and reuse them in several tests. The tests you have created can be loaded from the PC to the simulator s processor board and executed regardless of whether there is a real-time test already running. Even though executing the real-time tests requires additional memory capacity and computing time, it is no problem to implement typical test scenarios, which run in parallel to complex engine and vehicle dynamics models, at simulation step sizes of 1 ms. Managing real-time tests with the Real-Time Test Manager. Example Use Cases for Real-Time Testing Testing reactivity in a range of milliseconds Time-precise stimulation of several model signals Time-precise measurement of model changes Reliable determination of minimum and maximum values of model variables Dynamic execution of a Python restbus simulation not included in the simulation model Exact replay of recorded bus communication (like CAN or FlexRay log files) Parallel execution of several independent ECU tests 14

15 Python-Based Testing Scripting Example A common test case is the detection of an event being generated by the real-time model. An event is specified by a condition referencing one or more real-time model variables. As soon as the event has been detected, a test action is triggered in the same sample step. In this example, the real-time script observes the speed of a simulated vehicle and reacts by performing an emergency stop maneuver immediately when the vehicle exceeds 80 km/h. This test case can be easily implemented by a real-time Python script. The condition is observed continuously within a While loop. The included yield command has the effect that the test execution is paused and afterwards resumed in the next simulation step. This means the script can easily be time-controlled. When the speed exceeds 80 km/h, the While loop is left, and the brake maneuver is initiated by setting the associated model parameter in the same simulation step. Python for Real-Time Testing from rttlib import variable velocity = variable.variable(r Model Root/Velocity/Out1 ) brake_pedal = variable.variable(r Model Root/Brake/Value ) def MainGenerator(): while(velocity.value <= 80.0): yield None brake_pedal.value = Implementing a Real-Time Test in Python. 15

16 Headquarters in Germany dspace GmbH Technologiepark Paderborn Tel.: Fax: info@dspace.de dspace United Kingdom dspace Ltd. Unit B7. Beech House Melbourn Science Park Melbourn Hertfordshire. SG8 6HB Tel.: Fax: info@dspace.ltd.uk Japan dspace Japan K.K. 10F Gotenyama Trust Tower Kitashinagawa Shinagawa-ku Tokyo Tel: Fax: info@dspace.jp France dspace Sarl Parc Burospace Bâtiment 20 Route de la Plaine de Gisy Bièvres Cedex Tel.: Fax: info@dspace.fr USA and Canada dspace Inc Pontiac Trail Wixom. MI Tel.: Fax: info@dspaceinc.com 12/2007 Copyright 2007 by dspace GmbH. All rights reserved. Written permission is required for reproduction of all or parts of this publication. The source must be stated in any such reproduction. dspace is continually improving its products and reserves the right to alter the specifications of the products contained within this publication at any time without notice. Brand names or product names are trademarks or registered trademarks of their respective companies or organizations.