Test data generation device
The test data generation device addresses inefficiencies in existing systems by allowing users to visually edit and modify acquired data, resulting in efficient test data creation for controller development.
Patent Information
- Application Number
- JP2023182559
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-10-24
- Publication Date
- 2025-05-09
AI Technical Summary
Existing test data generation devices are inefficient in creating test data for controller development, as they lack the ability to edit and modify acquired data in a visually intuitive and flexible manner.
A test data generation device that includes storage means for acquired data, a display device for visual representation, and a data editing device that allows users to adjust playback speed, edit, and modify acquired data in real-time, converting it into test data.
Enables the efficient creation of test data by allowing users to visually edit and modify acquired data, improving the development and debugging process of controllers by providing realistic and customizable test scenarios.
Smart Images

Figure 2025072059000001_ABST
Abstract
Description
[Technical field]
[0001] The technology disclosed in this specification relates to a test data generator that generates data for a test signal to be provided to a controller of a device. [Background technology]
[0002] When developing a controller for a device, a method is known in which a test signal is given to the controller to check the operation of the controller. In some cases, the entire test signal is pseudo, but in other cases, a signal obtained from the device with some modifications is used. Patent Document 1 discloses a simulation test device used in the development of a controller. The simulation test device of Patent Document 1 generates data (test data) of a simulation signal (test signal) to be input to an electronic control unit (controller) by synthesizing an artificial signal with a signal obtained from an actual device. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2016-50826 A Summary of the Invention [Problem to be solved by the invention]
[0004] The present specification provides an apparatus capable of generating test data more efficiently than ever before. [Means for solving the problem]
[0005] The test data generating apparatus disclosed in this specification includes a storage means for storing a signal acquired from a device as acquired data, a display device for playing back and displaying the stored acquired data, and a data editing device. The data editing device can adjust the playback speed of the acquired data, and can change any part of the displayed acquired data based on a user's instruction, and stores the changed acquired data in a storage device as test data.
[0006] By using the test data generation device disclosed in this specification, a user can create test data by visually editing acquired data. Details and further improvements of the technology disclosed in this specification will be described in the following "Description of Embodiments of the Invention". [Brief description of the drawings]
[0007] [Figure 1] FIG. 2 is a block diagram of a test data generator connected to a device. [Diagram 2] 13 is a flowchart of a procedure for generating test data. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0008] A test data generating device 10 according to an embodiment will be described with reference to the drawings. The test data generating device 10 according to the embodiment is used for developing a controller 101 of an electric vehicle 100. The test signal means a pseudo input signal to the controller 101 (or a simulator of the controller 101). The test data means the test signal stored as data. The test signal is output by converting the test data into a signal of the same type as the sensor output signal of the electric vehicle 100.
[0009] FIG. 1 shows a block diagram of a test data generating device 10 connected to an electric vehicle 100. The electric vehicle 100 is equipped with various sensors 102, and a controller 101 controls the electric vehicle 100 based on signals (sensor signals) from the sensors 102. More specifically, the controller 101 controls a motor that drives the wheels, an inverter that converts DC power from a battery into AC power for driving the motor, a cooler that cools the motor, the battery, and the inverter, and the like. The test data generating device 10 is connected to a communication line between the sensor 102 and the controller 101. The output (sensor signal) of the sensor 102 is input to the test data generating device 10. The test data generating device 10 can acquire the sensor signal as data, and edit and store the acquired data. The sensor signal that is captured and converted into data is called acquired data, and the edited acquired data is called test data.
[0010] The test data generator 10 can output test data as a test signal. The test signal is sent to the input terminal of the controller 101 to which a sensor signal is normally input. By checking the operation of the controller 101 in response to the test signal, it is checked whether the controller 101 is operating as designed. If the operation of the controller 101 differs from the design, the program of the controller 101 is adjusted.
[0011] The various sensors 102 equipped in the electric vehicle 100 include, for example, a sensor for measuring the accelerator opening, a sensor for measuring the motor output, a sensor for measuring the remaining battery charge, a sensor for measuring the battery temperature, etc. In addition to these sensors, the electric vehicle 100 is equipped with many other types of sensors. The test data generation device 10 can simultaneously acquire output signals from these multiple sensors 102.
[0012] The electric vehicle 100 is placed on a test bench 103, and the wheels of the electric vehicle 100 can be driven by a motor without changing its position. While moving the electric vehicle 100 on the test bench 103, the test data generator 10 acquires signals from various sensors 102.
[0013] The test data generation device 10 includes a storage 11 that stores data, a display device 12 such as a monitor, a data editing device 13, an input device 14, and an output device 15. A sensor signal output from a sensor 102 while the electric vehicle 100 is in operation is digitized and stored in the storage 11. The sensor signal stored in the storage 11 is referred to as acquired data. The test data generation device 10 acquires the sensor signal output from the sensor 102 in real time while the electric vehicle 100 is in operation.
[0014] After the sensor signal has been taken as the acquired data, the electric vehicle 100 is stopped. Then, editing of the acquired data is started. In the test data generating device 10, the data editing device 13 displays the acquired data stored in the storage 11 on the display device 12. The data editing device 13 is actually a computer. The acquired data is time-series data, and the data editing device 13 can arbitrarily change the playback speed of the acquired data. The user specifies the playback speed using the keyboard 14a or the like. For example, when the user specifies a playback speed of 1 / 10, the data editing device 13 plays and displays, for example, 100 seconds of sensor signal data (acquired data) over 1000 seconds.
[0015] 1, the accelerator opening, motor output, remaining battery charge, and battery temperature are displayed in graph form as the acquired data to be displayed on the display device 12. By adjusting (typically slowing down) the playback speed of the acquired data, the user can easily understand the change over time in the acquired data (i.e., the change over time in the sensor signal).
[0016] The data editing device 13 can also hold the acquired data of any time width displayed in a graph on the display device 12. The data editing device 13 can also stop the playback of the acquired data midway. The acquired data that has been played back remains displayed in a graph on the display device 12. Furthermore, the data editing device 13 can also arbitrarily change the time width corresponding to the horizontal axis of the graph of the acquired data to be displayed. For example, the time width that can be displayed on the display device 12 can be changed to 100 seconds / 10 seconds / 1 second. When the acquired data of a short time width is displayed in the entire display area of the display device 12, minute changes in the acquired data (i.e. minute changes in the sensor signal) can be easily seen. Conversely, when the acquired data of a long time width is displayed in the display area of the display device 12, the overall movement of the acquired data can be easily seen.
[0017] The data editing device 13 can change any part of the displayed acquired data based on a user's instruction. The user's instruction can be given to the data editing device 13 through various input devices 14. As examples of the input devices 14, a keyboard 14a, a mouse 14b, a trackball 14c, and a game controller 14d are connected to the data editing device 13 in FIG. 1. The user can freely change any part of the displayed acquired data by making full use of these input devices 14. In this specification, changing a part of the acquired data is expressed as "editing the acquired data."
[0018] For example, the user edits the displayed graph of the acquired data by cutting or dragging a part of the graph or changing a curve of the graph to a different curve using the input device 14. Editing the acquired data includes inserting pseudo data, which is separately prepared, into any part of the acquired data. For example, data simulating a sensor signal that is expected to be output when a sensor breaks down is prepared as pseudo data.
[0019] 1 shows an example of editing the sensor signal data (acquired data) of the battery temperature. The battery temperature (data actually obtained from the sensor 102) from time T1 to T2 is shown by a solid line graph G1. In other words, the acquired data of the battery temperature from time T1 to T2 appears in the solid line graph G1. The user uses the input device 14 to change the graph of the battery temperature from time T1 to T2 from the solid line graph G1 to the dashed line graph G2.
[0020] When the displayed graph is changed, the acquired data on which the graph is based is also changed accordingly. The acquired data after the change is stored as temporary data in storage 11 separately from the original acquired data. Changing the displayed graph corresponds to editing the acquired data.
[0021] The user can arbitrarily change (edit) a different graph (i.e., different acquired data) for a different time period. Each time the user changes the graph, the temporary data is updated. When the user has finished editing the data, he or she issues a "save" command to the data editing device 13 using the input device 14, and the data editing device 13 stores the temporary data (the acquired data reflecting the changes to the graph) in the storage 11 as test data.
[0022] The test data is used for development and debugging of the controller 101. For development and debugging of the controller 101, there are a method using an actual electric vehicle 100 and a method using a simulator 200. When the electric vehicle 100 is used, the test data generation device is used as follows. After finishing generating the test data, the user disconnects the communication line between the sensor 102 and the controller 101, and connects the output device 15 of the test data generation device 10 to the sensor input terminal of the controller 101 (imaginary line A in FIG. 1). The user starts the electric vehicle 100. The test data generation device 10 outputs the stored test data as a test signal from the output device 15 to the controller 101. The signal type included in the test signal is adjusted to be the same as the type of the sensor signal output from the sensor 102. The playback speed of the test signal is adjusted to be the same as the speed of the sensor signal sent from the sensor 102. The controller 101 recognizes the test signal as a sensor signal and controls the electric vehicle 100 based on the test signal. The user checks the operation of the controller 101 from the movement of the controller 101 with respect to the test signal.
[0023] The simulator 200 is software that simulates the overall operation of the electric vehicle 100 including the controller 101. When the simulator 200 is used, the output device 15 of the test data generation device 10 is connected to the simulator 200 (imaginary line B in FIG. 1). The test data generation device 10 outputs stored test data as a test signal from the output device 15 to the simulator 200. The operation of the controller 101 (the controller on the simulator) is checked from the operation of the simulator 200 based on the test signal, and the program of the controller 101 is adjusted as necessary.
[0024] In the example of Fig. 1, the battery temperature from time T1 to T2 is changed to a higher temperature (dashed line graph G2) than the actual value (solid line graph G1: value acquired by the sensor). The controller 101 receives the test signal in which the battery temperature has been changed to a higher value and controls the cooler to suppress the battery temperature. If the battery temperature of the actual electric vehicle 100 (or the battery temperature in the simulator 200) is not suppressed, the user will determine that the controller 101 is not operating as designed and will adjust the software of the controller 101.
[0025] In this way, the user can provide the acquired data (i.e., test data) edited in various ways using the test data generating device 10 to the controller 101 as a test signal. The test data is typically generated so as to include an abnormal output value of the sensor. By providing the test data including the abnormal value of the sensor 102 as a test signal to the controller 101 and checking the behavior of the controller 101, the user can check whether the controller 101 is responding appropriately to the abnormal value.
[0026] The test data generation device 10 can edit any part of the acquired data while adjusting the playback speed of the acquired sensor signal (i.e., acquired data). The user can edit the acquired data while visually checking it. The test data generation device 10 can generate test data more efficiently than ever before.
[0027] FIG. 2 shows a flowchart of the test data generation procedure. The test data generation procedure will be described again with reference to FIG. 2. As a preliminary step, the electric vehicle 100 is placed on the test bench 103. The test data generation device 10 is connected to a signal line between the sensor 102 of the electric vehicle 100 and the controller 101 (step S2). In step S3, the electric vehicle 100 on the test bench 103 is operated to acquire a sensor signal, which is then stored in the storage 11 (the sensor signal is stored as acquired data). At this time, the controller 101 controls the electric vehicle 100 based on the sensor signal. The result of the control appears in the sensor signal. The test data generation device 10 acquires the sensor signal and stores it as acquired data.
[0028] When the sensor signals have been acquired, the electric vehicle 100 is stopped. The user operates the input device 14 of the data editing device 13 to set the playback speed of the acquired data (step S4). In the next step S5, the user starts playback of the acquired data and changes any part of the acquired data being played back. Alternatively, the user additionally inputs any signal to any part of the acquired data being played back. In other words, the user edits a part of the acquired data displayed on the display device 12. The user can edit the acquired data using various input devices 14.
[0029] When editing is completed, playback of the acquired data is stopped (step S6). The user checks the edited portion and determines whether further changes (editing) are necessary (step S7). If the user determines that re-editing is necessary, the process returns to step S4 and the same operation is repeated (step S7: YES, S4). If another edit is necessary in another portion of the acquired data, the process returns to step S4 and the same operation is repeated.
[0030] If it is determined that re-editing is not necessary, the data editing device 13 stores the edited acquired data as test data in the storage 11 (steps S7: NO, S8). As described above, the stored test data is used for development and debugging of the controller 101. The test data stored in the storage 11 can be repeatedly output as a test signal any number of times.
[0031] The advantages of the test data generating device 10 are described below. The test data generating device 10 can play back acquired data at any speed and edit the acquired data while viewing the display screen. In other words, by using the test data generating device 10, the user can create test data by editing the acquired data while visually checking a graph of the time change of the acquired data (sensor signal data). The user can easily create test data by using the test data generating device 10. For example, there are cases where the user wants to insert signal data (abnormal signal data) assuming a failure of the sensor 102 into part of the acquired data. The user can input the abnormal signal data to be newly added from the input device 14 while actually playing back and checking the sensor signal data (acquired data) output by the sensor 102 on the screen of the display device 12, and record the input result, thereby easily adding the desired abnormal signal data to the acquired data.
[0032] In addition, by appropriately selecting the type of input device 14 according to the user's skill, etc., it is possible to generate complex test data in a short time (for example, a case where multiple abnormal signals occur simultaneously while multiple pseudo abnormal signals return to normal signals in a specific order, or a case where the pseudo abnormal signals change in an analog manner). As the input device, various devices such as a game controller or a musical instrument can be used. It is also preferable to use an input device for a DAW (Digital Audio Workstation).
[0033] The data editing device 13 can set the playback speed of the acquired data as desired. The test data generating device 10 can play back the acquired data at the same speed as the speed at which the sensor 102 actually outputs a sensor signal (real-time speed), or at a speed much slower than the real-time speed. By slowing down the playback speed, the user can easily check changes in the data (i.e., changes in the sensor signal) even for data that has an extremely short time span in real time (e.g., 1 millisecond or 1 microsecond). By adjusting the playback speed, the user can add any signal even within a short time span.
[0034] As shown in the flowchart of FIG. 2, by using the test data generation device 10 of the embodiment, re-input and manual adjustments can be repeatedly performed as necessary, making it possible to generate desired test data.
[0035] Below, points to note regarding the technology described in the embodiment will be described. The data editing device 13 can adjust the playback speed of the acquired data. In other words, the data editing device 13 can play back the acquired data at any speed. The data editing device 13 can change any part of the displayed acquired data based on the user's instruction. Specifically, the acquired data in any time period can be freely modified. Furthermore, the data editing device 13 can insert any data at any time into the acquired data. A typical example of the arbitrary data to be inserted is data simulating a sensor signal that is expected to be output when a sensor fails.
[0036] The test data generating device 10 generates a test signal to be provided to a controller of a device. The electric vehicle 100 of the embodiment is an example of the device. The device to which the test data generating device 10 can be applied is not limited to the electric vehicle. The storage 11 of the embodiment is an example of a storage means.
[0037] Although specific examples of the present invention have been described above in detail, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples exemplified above. The technical elements described in this specification or drawings exhibit technical utility alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technology exemplified in this specification or drawings can achieve multiple objectives simultaneously, and achieving one of these objectives is itself technically useful. [Explanation of symbols]
[0038] 10: Test data generation device 11: Storage 12: Display device 13: Data editing device 14: Input device 14a: Keyboard 14b: Mouse 14c: Trackball 14d: Game controller 15: Output device 100: Electric vehicle 101: Controller 102: Sensor 103: Test bench 200: Simulator
Claims
[Claim 1] a test data generator that generates test data to be provided to a controller of a device, A storage means for storing a signal acquired from the device as acquired data; a display device for reproducing and displaying the acquired data; a data editing device capable of adjusting a playback speed of the acquired data, modifying any portion of the displayed acquired data based on an instruction from a user, and storing the modified acquired data in the storage means as test data; A test data generating device comprising:
Citation Information
Patent Citations
Simulation test device and simulation signal generation program
JP2016050826A