Multiple Recorders in CANape Version Application Note AN-AMC-1-112

Transcription

1 Version Author(s) Restrictions Abstract Shrimant Saxena; Gernot König Released document This application note explains the concept of multiple recorders in the measurement configuration of CANape. A recorder is a virtual device which stores data related to the measurement in progress in a dedicated measurement file. The start and end of a recording are not dependent upon the measurement sequence. Table of Contents 1.0 Overview Concept/Feature Overview Measurement Configuration Measurement Options Measurement Options Measurement Start Measurement Options Measurement Measurement Options Measurement Stop Measurement Signals Recorder List Event List Audio Outputs Using Multiple Recorders in CANape Contacts Overview The purpose of this document is to explain the concept of using multiple recorders for logging measurement data in CANape. Using multiple recorders allows CANape to create multiple log files (*.mdf) during one measurement. Each log file can contain specific signals or events captured during the measurement. Note: The multiple recorder concept is supported since CANape 7. This documentation is based on CANape Concept/Feature Overview The following accommodate multiple recorders in CANape: It is possible to measure the same signal in different recorders with the same measurement raster. Note: Multimedia signals can only be assigned to one recorder Every recorder in the Measurement configuration saves to a unique measurement file. Every recorder has unique start and optional stop trigger conditions. Trigger events are defined at a central place in the Measurement configuration window, and recorders contain only references to these trigger events. Recorder-Specific and Signal-specific data reduction is available. Copyright Vector Informatik GmbH Contact Information: or

2 3.0 Measurement Configuration The Measurement configuration dialog can be opened from the menu or with the <F4> shortcut key. This window provides access to measurement start and stop conditions, measurement runtime configuration, and any signals, devices, functions, or variables associated with the project s measurements. It also contains the configuration dialog box for setting up multiple recorders, along with options for configuring the start and stop conditions and events for each recorder. Finally, it contains settings for audio outputs. In the Multirecorder demo, click the Measurement menu option and then click Measurement Configuration, or press the <F4> key, to bring up the Measurement Configuration window. Then, click Measurement signals. The Measurement configuration dialog is shown in Figure 1. Figure 1: Measurement Configuration Window Note: The signal-to-recorder mappings are clearly shown. RPM_HIGHER_4000 is only recording certain signals while Complete_Measurement is recording the majority of the signals. Both are separate recorders and will generate individual MDF files with unique measurements. Each can be individually triggered by separate events. 3.1 Measurement Options The first subsection of the Measurement Configuration window tree at the left is called Measurement options. The measurement options are valid for the entire measurement. The measurement runs independently of the trace made by any recorder. In addition to measurement values, the calibration operations performed during a measurement can also be recorded. The comment added to the measurement file for new recorders can be configured in this section of the window Measurement Options Measurement Start In the Measurement start dialog (see Figure 2), it is possible to specify which devices have their calibration options or parameter sets saved during the measurement or before the measurement is started. Additionally, the 2

3 initial setup of the time axis and the Y axis of Graphic windows can be configured in the Measurement start dialog. Figure 2: Measurement Start Dialog Measurement Options Measurement The size of CANape s measurement buffer can be set in the Measurement dialog (the second dialog down in the tree), as well as scrolling and other display behavior of Graphic windows in CANape during a measurement. This dialog is shown in Figure 3. 3

4 Figure 3: Measurement Dialog Measurement Options Measurement Stop In the Measurement stop dialog, the stop condition for the measurement can be changed from manual to a time limit or an event trigger. Additionally, the Graphic window behavior when a measurement stops can be configured here. This dialog is shown in Figure 4. 4

5 Figure 4: Measurement Stop Dialog In the Comment template dialog, the default comment for log files can be set, and the post-measurement comment prompt can be turned on or off. The Comment template of the measurement options is used only as a template for new recorders or for measurement files saved from the display buffer or Graphic window after measurement has stopped. The comment template for existing recorders can be modified in the options for each recorder. 3.2 Measurement Signals The Measurement signals dialog (see Figure. 1) shows all of the measurement signals in the Measurement Configuration. It is the second subsection of the Measurement Configuration window. This includes device signals, CANape functions, global variables, MATLAB/Simulink model signals, bypass functions, stimulations, and multimedia signals. The columns shown in the Measurement signals dialog can be changed by the user. The order of the columns can be also be set. The names of any configured recorders can be seen in this dialog and different signals can be set to be captured by these recorders. In this example, there are two recorders: Complete_Measurement and RPM_HIGHER_4000. The check mark next to the floppy disk icon indicates that the recorder is capturing for that specific signal. For example, Complete_Measurement will be measuring OutputTorque but RPM_HIGHER_4000 will not. Similarly, the signal Write is measured by RPM_HIGHER_4000 but not by Complete_Measurement. When a new recorder is created, the corresponding column is added automatically to the Measurement signals list. The measurement mode for each signal is defined here, but each recorder may have data reduction when recording a signal. 5

6 3.3 Recorder List The third subsection of the Measurement Configuration window tree is the Recorder list. A recorder is a uniquely named virtual device which stores data relating to the measurement in progress in a dedicated measurement file. By default, a new project will have one recorder named Recorder. In this example, there are two recorders: Complete_Measurement and RPM_HIGHER_4000. Each recorder stores its own subset of data from its own selection of signals in a uniquely named file. The Recorder list dialog shows the name, status, trigger condition, and measurement file name for each recorder in the configuration. In the dialog for each individual recorder, the recorder name can be set, as well as a comment for that recorder. Also, the name of the measurement file is set here, with an optional macro for incrementing the file name during consecutive measurements. The macro for Complete_Measurement is {RECORDER}_{YEAR}-{MONTH}- {DAY}_{HOUR}-{MINUTE}-{SECOND}.MDF will ensure that each consecutive measurement has its own uniquely named measurement file. The recorder for RPM_HIGHER_4000 has the same macro to define its measurement file names, but since the recorders themselves have different names, the files will still be uniquely named (see Figure 5). Figure 5: Recorder List Dialog Options 6

7 Each recorder in the configuration has pages for options, triggers, and signal lists. The behavior of the recorder at the start, stop, and the duration of the measurement can be configured on the Recorder Options page (see Figure 6). Figure 6: Recorder Options Page 7

8 A trigger for the recorder can be configured on the Trigger page (see Figure 7). Figure 7: Trigger Page The signals saved by the recorder are set on the All recorder signals page. Figure 8: All Recorder Signals 3.4 Event List The fourth subsection of the Measurement Configuration window tree is called the Event list. Many measurement operations (such as the start of a recording via a trigger, the output of an audio signal or the stopping of a measurement) can be controlled by events. An event can be a change to a measurement signal, the input of a key combination by the operator, or a system message relating to the measurement or the installed device drivers. These events are linked to various actions in the configuration so that when they occur, the associated actions are triggered. 8

9 Events that are dependent on the value of a signal in the Measurement Configuration can be defined on the Signal events page. An example signal event is shown in Figure 9. Figure 9: Signal Event In the Keyboard events page, events can be defined as a combination of keyboard inputs. The System events page displays the events generated by system messages from CANape or connected hardware. These events are defined by CANape. They cannot be modified. Algebraic events can also be defined by the user. By using these types of events, the user can create rules and simple functions as an alternative to signal conditions. In some scenarios, this can provide much more versatile recorder triggers options than a simple signal event would. For example, defining an audio measurement using a logarithmic or trigonometric condition, or defining a logic based trigger using positive/negative edge and logical conditions. A simple example of the RPM_HIGHER_4000 condition can be seen as an algebraic condition in Figure 10. 9

10 Figure 10: Algebraic Event for RPM_HIGHER_ Audio Outputs The fifth subsection of the Measurement Configuration window tree is called Audio outputs (see Figure 11). Audio outputs (system sounds, audio files, or spoken text) are triggered by specific events, and are only available during active measurement. System sounds, audio files, and text strings can be output by CANape. The text string output is dependent on the text-to-speech voices installed in Windows. 10

11 Figure 11: Audio Output Setup 4.0 Using Multiple Recorders in CANape The Multi-recorder project is already configured to use multiple recorders. As we have seen, one recorder is configured to measure all data. The other recorder is configured to start recording specific signals when the simulated engine s RPM exceeds 4000 RPM. In the project, set the Throttle slider to maximum. Click the lightning bolt icon or the <F9> button to start the measurement. The recorder Complete_Measurement starts recording data. As the simulated car accelerates, the RPM increases. When the RPM increases past the 4000 limit, it triggers an event which causes the recorder RPM_HIGHER_4000 recorder to start recording specific signals. Lower the throttle slider and click the brakes. As the engine RPM decreases past the 1500RPM limit, another event is triggered and causes the recorder RPM_HIGHER_4000 to stop recording. Once the speed reaches 0mph, stop the measurement by using the stop button or pressing the Esc key. The full results of the measurement are shown in the Graphic window as shown in Figure

12 Figure 12: Complete Measurement Results The measurement files are stored in two separate files. One is from recorder Complete_Measurement and the other is from recorder RPM_HIGHER_4000. When loading the file from the Complete_Measurement recorder by selecting Analysis Show values from measurement file, you will see signal values for the whole measurement. See figure 13. Figure 13: All signal values 12

13 If you select the measurement file from the RPM_Higher_4000 recorder by selecting Analysis Show values from measurement file you will see the values between the start and the stop event only. The trigger events are shown by the green lines. See figure 14. Figure 14: Signal values between triggered events only 5.0 Contacts Germany and all countries not named below: Vector Informatik GmbH Ingersheimer Str Stuttgart GERMANY Phone: Fax: France, Belgium, Luxemburg: Vector France S.A.S. 168, Boulevard Camélinat Malakoff FRANCE Phone: Fax: information@fr.vector.com Sweden, Denmark, Norway, Finland, Iceland: VecScan AB Theres Svenssons Gata Göteborg SWEDEN Phone: Fax: info@se.vector.com United Kingdom, Ireland: Vector GB Ltd. Rhodium, Central Boulevard Blythe Valley Park Solihull, Birmingham West Midlands B90 8AS UNITED KINGDOM Phone: Fax: info@uk.vector.com China: Vector Automotive Technology (Shanghai) Co., Ltd. Sunyoung Center Room 1701, No.398 Jiangsu Road Changning District Shanghai P.R. CHINA Phone: Fax: info@cn.vector.com India: Vector Informatik India Pvt. Ltd. 4/1/1/1, Sutar Icon, Sus Road, Pashan, Pune INDIA Phone: Fax: info@in.vector.com USA, Canada, Mexico: Vector CANtech, Inc Orchard Hill Place, Suite 550 Novi, MI USA Phone: Fax: info@us.vector.com Japan: Vector Japan Co. Ltd. Tennozu Yusen Bldg. 16F Higashi-shinagawa, Shinagawa-ku, Tokyo JAPAN Phone: Fax: info@jp.vector.com Korea: Vector Korea IT Inc. 5F, Gomoas bldg. 12 Hannam-daero 11-gil, Yongsan-gu Seoul, REPUBLIC OF KOREA Phone: Fax: info@kr.vector.com 13