Test device
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- KOKUSAI DENKI ELECTRIC INC
- Filing Date
- 2024-01-12
- Publication Date
- 2026-06-05
Smart Images
Figure 00000000_0000_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a test apparatus for measuring the performance of a wireless device or the like having a plurality of modules, and more particularly to a test apparatus capable of efficiently performing defect analysis and maintenance work on modules of equipment to be maintained.
Background Art
[0002] [Prior Art] Electronic devices (units) mounted on aircraft and the like include a plurality of modules and are tested by a test apparatus. When an electronic device fails, which module among the plurality of replaceable modules constituting the electronic device has failed is identified (cause analysis), and adjustment, repair, or replacement of the identified failed module is performed.
[0003] The test apparatus has a function of creating a log file of the test results. In the log file, for each piece of equipment to be maintained (module), instructions output by the test apparatus to the measuring instrument and the equipment to be maintained, data acquired from the measuring instrument and the equipment to be maintained, test results (pass / fail, measurement results), etc. are recorded in time series.
[0004] The number of log files output varies depending on the tests performed, and may exceed 100 files in a day. Conventionally, when an abnormality is determined by a test, the data necessary for cause analysis has been manually extracted (taken out, selected) from the log file by the maintenance staff, which has taken time.
[0005] Also, conventionally, the test results that can be confirmed on the display unit of the test apparatus only remain the data for which the maintenance staff has performed operations such as saving. Therefore, for example, when the test results are normal, there is little data, and it is insufficient for determining the tendency of performance degradation of the module by comparing with past test results.
[0006] [Related Art] As related prior art, there is Japanese Patent Application Laid-Open No. 2017-041127, "Testing Device" (Patent Document 1). Patent Document 1 shows that when a device under test is connected to a testing device, the control unit of the testing device acquires the version information of the device under test, determines whether there is an update for the test target item, and executes the test when an update is not required.
Prior Art Documents
Patent Documents
[0007]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0008] Thus, in the conventional testing device, when analyzing the cause of a defect, the maintenance staff has to manually select the past test results of the equipment to be maintained from the log file, which takes time and makes it impossible to quickly analyze the cause of the defect and perform maintenance work.
[0009] In addition, Patent Document 1 does not describe a configuration in which data for analyzing a defect is extracted from a log file as analysis data and the analysis data is sorted and stored in a file corresponding to the equipment to be maintained and the test type.
[0010] The present invention has been made in view of the above situation, and an object of the present invention is to provide a testing device that can easily extract and display the past test results of defective equipment to be maintained from a huge log file and can efficiently analyze the cause of the defect and perform maintenance work.
Means for Solving the Problems
[0011] The present invention for solving the problems of the above-described conventional examples is a test apparatus that measures the performance of replaceable maintenance target equipment of a device under test and conducts a test, including a plurality of measuring instruments that output a test signal and measure the output from the maintenance target equipment, a switching unit that connects any one of the measuring instruments and the device under test, and a test control unit that inputs and analyzes data of measurement results from the plurality of measuring instruments. The test control unit attaches the date of measurement to the data of the measurement results, stores it as a log file in a log folder, extracts data for analyzing defects from the log file as analysis data, generates an analysis data file corresponding to the maintenance target equipment and the test type, and distributes and accumulates the analysis data to the analysis data file according to the maintenance target equipment and the test type.
[0012] Further, in the present invention, in the above test apparatus, the test control unit generates a folder with the name of the maintenance target equipment in advance, generates a folder with the name of the test type within the folder, generates an analysis data file within the folder with the name of the test type, and uses a serial number corresponding to the manufacturing number for the name of the analysis data file.
[0013] Further, in the present invention, in the above test apparatus, the test control unit causes the display unit to display a list of analysis data files corresponding to the name of the maintenance target equipment, the name of the test type, and the serial number for the tested maintenance target equipment, and causes the display unit to display the analysis data selected from the list as a test result.
[0014] Further, in the present invention, in the above test apparatus, when the test control unit displays the test result, it displays the test result in a cell corresponding to the test item for each date, and changes the color of the cell according to whether the test result is good, abnormal, or corresponds to the boundary value of the measured value.
[0015] Further, in the present invention, in the above test apparatus, when the test control unit displays the test result, it displays the test result in a cell corresponding to the test item for each date, and changes the color of the cell according to whether the test result is good, abnormal, or corresponds to the boundary value of the measured value.
Effects of the Invention
[0016] According to the present invention, there is provided a test apparatus that measures the performance of replaceable maintenance target equipment of a device under test and conducts a test. The test apparatus includes a plurality of measuring instruments that output test signals and measure outputs from the maintenance target equipment, a switching unit that connects any one of the measuring instruments to the device under test, and a test control unit that inputs and analyzes data of measurement results from the plurality of measuring instruments. The test control unit attaches the date of measurement to the data of the measurement results, stores it as a log file in a log folder, extracts data for analysis as analysis data from the log file, generates an analysis data file corresponding to the maintenance target equipment and the test type, and accumulates the analysis data by sorting it into the analysis data file according to the maintenance target equipment and the test type. Therefore, during failure analysis, based on the maintenance target equipment and the test type, the analysis data necessary for analysis can be quickly selected and displayed, and the effects of efficiently analyzing the cause of failure and performing maintenance work can be achieved.
[0017] Also, according to the present invention, the test control unit generates a folder with the name of the maintenance target equipment in advance, generates a folder with the name of the test type within the folder, generates an analysis data file within the folder with the name of the test type, and uses a serial number corresponding to the manufacturing number for the name of the analysis data file. Therefore, individual maintenance target equipment can be specified and the analysis data can be displayed, and the effects of efficiently analyzing the cause of failure and performing maintenance work can be achieved.
[0018] Further, according to the present invention, the test control unit causes the display unit to display a list of analysis data files corresponding to the name, test type name, and serial number of the equipment to be maintained that has been tested, causes the display unit to display the analysis data selected from the list as test results, and when displaying the test results, displays them in a comparable manner with the past test results stored in the selected analysis data file. Therefore, for individual equipment to be maintained, it is possible to easily compare the past test results with the current test results. For example, it is possible to easily determine whether the cause of the defect is due to aging deterioration or other factors.
Brief Description of Drawings
[0019]
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Embodiments for Carrying Out the Invention
[0020] Embodiments of the present invention will be described with reference to the drawings. [Outline of Embodiment] The test apparatus (this test apparatus) according to an embodiment of the present invention is a test apparatus that measures the performance of a device under test equipped with replaceable maintenance target equipment (module) and conducts a test. The test apparatus includes a plurality of measuring instruments that output a test signal and measure the output from the maintenance target equipment, a switching unit that connects any one of the measuring instruments to the device under test, and a test controller that inputs and analyzes the measurement result data from the plurality of measuring instruments. The test controller attaches the measurement date to the measurement result data and stores it as a log file in a log folder. From the log file, data for analyzing defects is extracted as analysis data and distributed and stored in an analysis data file corresponding to the maintenance target equipment and the test type. During defect analysis, if the maintenance target equipment and the test type are specified, data available for the desired defect analysis can be quickly selected and displayed from the accumulated analysis data files, enabling efficient defect analysis and maintenance work.
[0021] [Configuration of This Test Apparatus: Figure 1] The configuration of this test apparatus will be described with reference to Figure 1. Figure 1 is a schematic configuration diagram of this test apparatus. As shown in Figure 1, the test apparatus (this test apparatus) 1 is connected to the device under test (device under test) 2 via a network and conducts various tests. The test apparatus 1 includes a test controller 20, n measuring instruments 10-1, 10-2,...~10-n that perform various measurements (sometimes referred to as measuring instrument 10), and a switching unit 30. Note that the test controller 20 corresponds to the test control unit described in the claims.
[0022] The measuring instruments 10-1, 10-2,...~10-n output a test signal to the device under test 2 via the switching unit 30 according to the instructions of the test controller 20, receive and measure the output signal from the device under test 2, and output the measurement result to the test controller 20. The switching unit 30 is connected to the test controller 20 by a switching unit control line and switches the measuring instrument 10 connected to the device under test 2 according to the switching control signal from the test controller 20.
[0023] The test controller 20 is a computer that controls the entire test. Basically, it includes a control unit that performs processing, a storage unit that stores processing programs and data, and an interface unit that connects to a network or the like. Further, the test controller 20 includes a display unit and an input unit. The various processes described in the embodiments to be described later are executed when the control unit of the test controller 20 activates the processing program stored in the storage unit.
[0024] Also, the storage unit of the test controller 20 stores a log file to be described later and an analysis data file of data (analysis data) that is extracted from the log file and used for defect analysis at a later date. The analysis data file will be described later. The test controller 20 is connected to the measuring instrument 10, the switching unit 30, and the device under test 2 via a network. Note that the test controller 20 may include a database as an external storage device, and perform generation of a log file and various files, writing of data, reading of data, etc. with respect to the database.
[0025] The device under test 2 is, for example, an electronic device (equipment) mounted on an aircraft or the like, and is the equipment to be the object of the test executed by the test apparatus 1. Further, the device under test 2 includes a plurality of replaceable modules 21-1, 21-2,... 21-n (which may also be referred to as module 21). The device under test 2 may also be referred to as a unit. Also, each module 21 corresponds to the maintenance target equipment described in the claims. The device under test 2 is connected to the test controller 20 via a network and transmits and receives information necessary for the test. For example, the test controller 20 sets various test conditions for the device under test 2, and the device under test 2 transmits a response.
[0026] And as a feature of this test apparatus, the test controller 20 extracts and stores, as analysis data, the data to be used for defect analysis from the accumulated log data, and stores it so that the maintenance staff can easily view the necessary analysis data from the operation screen.
[0027] Furthermore, the test controller 20 displays, in response to an instruction, the analysis data regarding a specific module and test type as a list on the display unit. In this way, the operation of extracting, classifying, and accumulating the data necessary for defect analysis, and displaying the desired analysis data as a list from the accumulated test results in response to an instruction is referred to as execution history analysis.
[0028] [Memory section of test controller: Figure 2] Here, before explaining the details of the operation of the test controller 20, the schematic configuration of the memory section for storing the analysis data will be explained with reference to Figure 2. Figure 2 is a schematic explanatory diagram showing a configuration example of the memory section of the test controller 20. As shown in Figure 2, in the memory section 5 of the test controller 20 of this test apparatus, a log data storage section 6 for storing log data and an analysis data storage section 7 for storing the analysis data extracted therefrom are provided.
[0029] The log data storage section 6 stores, in chronological order, log data including the date, module name (model number), serial number, test type, and measurement result (numerical value or good / bad) when measurements are performed on each module 21 of the device under test 20. Here, it is assumed that log folders 61 are generated for each date, and the log data is stored as a log file for each module 21 in the log folder 61. Note that the serial number is an identification number (manufacturing number) for distinguishing each individual module 21, and even for modules of the same model number, different numbers are assigned to each individual.
[0030] Then, in response to the instruction, the test controller 20 extracts the log data stored in the log data storage unit 6 and distributes and stores it in an appropriate file in an appropriate folder of the analysis data storage unit 7. The analysis data storage unit 7 stores analysis data. In FIG. 2, an example of the folder configuration is shown, but another configuration may be used.
[0031] The folder configuration of the analysis data storage unit 7 will be described. The analysis data storage unit 7 includes module name folders 8A, 8B,... (sometimes referred to as module name folder 8) that store analysis data for each module name of the test target. Here, the module name folder 8A is a folder that stores analysis data for module A, the module name folder 8B is a folder that stores analysis data for module B, and so on. That is, the number of module name folders 8 provided is equal to the number of types of modules to be maintained.
[0032] Furthermore, in each module name folder 8, test type folders (a) 81a, test type folders (b) 81b,... (sometimes referred to as test type folder 81) that store analysis data for each test type are provided. Here, the test type folder (a) 81a stores analysis data for test type (a), and the test type folder (b) 81b stores analysis data for test type (b).
[0033] And in each test type folder 81, analysis data files (referred to as data files in the figure) 82a_001, 82a_002,... are stored for each serial number of module 21. In the analysis data file 82a_001, analysis data for the module with serial number 001 is stored as the test result of test type (a) for module A, and in the analysis data file 82a_002, analysis data for the module with serial number 002 is stored.
[0034] Similarly, the analysis data for test type (b) of module A is stored in the analysis data files 82b_001, 82b_002, … (not shown) within the test type folder (b) 81b. When not distinguishing individual analysis data files, they may also be referred to as analysis data file 82.
[0035] That is, the analysis data file 82 is provided corresponding to the combination of module name, test type, and serial number. Once the combination of module name, test type, and serial number is determined, the analysis data file 82 will be specified.
[0036] Thus, during the failure analysis of an individual module, by specifying the combination of module name, test type, and serial number, the analysis data file 82 for the corresponding module can be identified from the analysis data, enabling the maintenance staff to quickly view the data within the required analysis data file.
[0037] Then, the test controller 20 extracts the analysis data according to the instruction from the log data which is the result of various tests on the device under test 2, classifies it into the folders provided in the analysis data storage unit 7, and stores it. The log data extracted as analysis data includes not only the data determined to be defective in the test but also the normal data for comparison.
[0038] When sorting the analysis data extracted by the test controller 20, the module name folder 8 is specified according to the module name, then the test type folder 81 within the module name folder 8 is specified according to the test item, and then it is stored in chronological order in the analysis data file 82 corresponding to the serial number within the test type folder 81.
[0039] [Processing of Test Controller 20] Then, the test controller 20 of this test apparatus extracts necessary data from the log data, performs an analysis data extraction process of attaching a file name and storing it as analysis data, and during defect analysis, selects analysis data (reference data) necessary for actual defect analysis, etc. from the data stored as analysis data, and performs a list display process of displaying it as a list, and further performs a module-by-module test result display process of displaying detailed data in chronological order for the reference data selected from the list. These processes will be described later.
[0040] [Execution History Analysis Screen: Figure 3] The test controller 20 of this test apparatus is equipped with an execution history analysis screen as an operation screen operated by a maintenance staff to perform the various processes described above. The execution history analysis screen will be described with reference to Figure 3. Figure 3 is an explanatory diagram showing an example of the execution history analysis screen. When an instruction to display the execution history analysis screen is input from the input unit, the test controller 20 displays the execution history analysis screen shown in Figure 3 on the display unit.
[0041] As shown in Figure 3, the execution history analysis screen 50 includes a search folder selection section 51, a search folder reference button 52, an output file selection section 53, an output file reference button 54, execution buttons 55, 56, and an end button 57.
[0042] The search folder selection section 51 is a part for designating a folder from which to extract log data or analysis data. The search folder reference button 52 is a button for displaying candidates for the folder selected in the search folder selection section 51.
[0043] The output file selection section 53 is a part for designating the output destination file when extracting analysis data from the log data. The output file reference button 54 is a button for displaying candidates for the file selected in the output file selection section 53. The selection of the output file will be described in the distribution process described later.
[0044] The execution button 55 is a button for instructing the execution of the analysis data extraction process. Also, the execution button 56 is a button for instructing the execution of the list display process for displaying the test result list. The end button 57 is a button for instructing the end of the display of the execution history analysis screen 50.
[0045] [Analysis Data Extraction Process (1): Figure 4] Next, the analysis data extraction process (1) in the test controller 20 will be described with reference to FIG. 4. FIG. 4 is a flowchart showing the analysis data extraction process (1). The analysis data extraction process (1) is a process of storing the test results of a specific test day as analysis data.
[0046] In the analysis data extraction process (1), the test controller 20 designates a specific log folder 61 in the log data storage unit 6 as a search folder from the execution history analysis screen 50 shown in FIG. 3, designates the analysis data file 82 corresponding to the module name, test item, and serial number as an output file, and when the execution button 55 is clicked, the process starts.
[0047] Note that the log folder 61 is designated by specifying a date. The designated log folder 61 becomes the log folder to be extracted.
[0048] Then, the control unit of the test controller 20 (hereinafter simply referred to as the test controller 20) determines whether there is a log folder 61 to be extracted (S11). If not (in the case of No), the process ends with no extraction target. Also, in process S11, if there is a designated log folder 61 (in the case of Yes), the test controller 20 extracts the log data in the designated log folder 61 as analysis data (S12). The analysis data to be extracted includes all the test results executed on that day.
[0049] Then, the test controller 20 reads one piece of analysis data (S13), and based on the module name, test item, and serial number, determines whether it matches (corresponds to the output destination file) the module name, test item, and serial number of the analysis data file 82 specified in the output destination file (S14). If they do not match, it discards the data as not to be saved (S15) and proceeds to process S17.
[0050] Also, in process S14, if the module name, test item, and serial number of the read analysis data match (correspond to the output destination file) the module name, test item, and serial number of the analysis data file 82 specified in the output destination file (Yes), the test controller 20 stores the analysis data in the analysis data file 82 specified as the output destination (S16). At this time, it may be stored in chronological order.
[0051] After processes S15 and S16, the test controller 20 determines whether the check has been completed for all the extracted analysis data (S17). If not (No), it returns to process S13 to repeat the process. Also, in process S17, if the check has been completed for all the extracted analysis data (Yes), the process ends. In this way, the analysis data extraction process (1) for saving only the test results of a specific test day as analysis data is performed. For example, it is performed when saving the test results at the time of defect occurrence as analysis data.
[0052] [Analysis Data Extraction Process (2): Figure 5] Next, the analysis data extraction process (2) will be described with reference to FIG. 5. FIG. 5 is a flowchart showing the analysis data extraction process (2). The analysis data extraction process (2) is a process for sorting and storing individual pieces of analysis data in appropriate analysis data files 82 for a plurality of pieces of analysis data in which various module names, test types, and serial numbers are mixed.
[0053] In this case, in the execution history analysis screen 50 shown in FIG. 3, when the execution button 55 is clicked with a specific log folder 61 in the log data storage unit 6 designated as the search folder and no output file specified, the following processing is performed.
[0054] As shown in FIG. 5, since the processes S21 and S22 are the same as the analysis data extraction process (1) shown in FIG. 4, the description thereof is omitted. When the analysis data is extracted in process S22, the test controller 20 performs a distribution process of distributing the extracted analysis data to an appropriate analysis data file 82 (S23). The distribution process will be described later.
[0055] Then, based on the result of the distribution process, each analysis data is stored in the analysis data file 82 of the distribution destination (S24), and the process ends. In this way, the analysis data extraction process (2) is performed. In FIG. 5, for the sake of clearly showing the state of distribution, process S24 is shown separately from the distribution process, but it may be included in the distribution process.
[0056] [Distribution Process: FIG. 6] Next, the distribution process shown in process S23 of FIG. 5 will be described with reference to FIG. 6. FIG. 6 is a flowchart of the distribution process. As shown in FIG. 2, the analysis data is stored, for example, in time series in the analysis data file 82 for each serial number corresponding to the module name and the test type. In the distribution process, it is specified which analysis data file 82 the analysis data extracted from the log folder is to be stored in. In the process of FIG. 6, it is assumed that the process of storing the analysis data in the specified analysis data file 82 is also performed.
[0057] As shown in FIG. 6, the test controller 20 reads the module name, test item, and serial number from the head data among the analysis data read in process S22 of FIG. 5 (S31), identifies the module name folder 8 based on the module name (S32), and further identifies the test type folder 81 based on the test type (S33).
[0058] Then, the analysis data read in process S31 is distributed to the analysis data file 82 corresponding to the serial number and stored in chronological order (S34). As a result, the analysis data file 82 stores the records for each test conducted on an individual module in the order of the test dates.
[0059] In addition, in process S34, if there is no analysis data file 82 corresponding to the serial number in the corresponding test type folder 81, a new analysis data file 82 is created with the serial number as the file name and stored. Then, it is determined whether all the extracted analysis data has been distributed (S35). If not (No), the process returns to S31 to read the next analysis data. Also, if the distribution of all the analysis data is completed in process S35 (Yes), the process ends. In this way, the distribution process is performed.
[0060] For example, when an abnormality occurs during a test, by specifying the log folder for that day and executing the analysis data extraction process (2), not only the data of the abnormal module 21 but also the data of another normal module 21 that was tested on the same day and the data for another test item of the abnormal module can be saved as analysis data. Since the normal data is used as comparison data during defect analysis, it is desirable to save it appropriately so as not to strain the storage capacity.
[0061] [Operation during defect analysis] Next, the operation during defect analysis in this test apparatus will be described. During defect analysis, data of the module 21 that has become abnormal this time and is the target of defect analysis is selected and displayed from the accumulated analysis data, and the maintenance staff estimates the cause of the defect while referring to it. Therefore, the test controller 20 of this test apparatus performs a list display process of searching the analysis data storage unit 7 based on an instruction from the execution history analysis screen 50 in FIG. 3, reading out the instructed analysis data, and displaying it as a list (a list of tested maintenance target equipment).
[0062] [List display process: FIG. 7] The list display process by the test controller 20 will be described with reference to FIG. 7. FIG. 7 is a flowchart of the list display process. The list display process is executed when, in the execution history analysis screen 50 in FIG. 3, for example, the execution button 56 of "display test result list" is clicked with the module name folder 8 selected by the search folder selection unit 51.
[0063] As shown in FIG. 7, when the module name folder 8 to be searched is selected by the search folder selection unit 51 of the execution history analysis screen 50 and the execution button 56 is clicked, the test controller 20 checks whether the module name folder 8 to be searched exists in the analysis data storage unit 7 (S41). If not (in the case of No), the process ends.
[0064] If the module name folder 8 to be searched exists in process S41 (in the case of Yes), the test controller 20 checks whether there is an analysis data file 82 in the module name folder 8 (S42). If not (in the case of No), the process ends.
[0065] In process S42, if there is an analysis data file in the specified module name folder 8 (Yes), list data is generated based on the module name, test type, and serial number of the analysis data file in the module name folder 8 (S43), a list (a list of tested equipment to be maintained) is displayed (S44), and the process ends.
[0066] In addition, when the process of FIG. 7 is continuously performed, the information of the analysis data file 82 obtained in the current process is added to the information of the analysis data file 82 obtained in the previous process to generate list data, and the analysis data files for a plurality of modules may be configured to be displayed in a list.
[0067] [Example of list: FIG. 8] An example of the list (a list of tested equipment to be maintained) will be described with reference to FIG. 8. FIG. 8 is an explanatory diagram showing an example of the list. The list displays a list of stored analysis data files for the specified module. As shown in FIG. 8, in the list (a list of tested equipment to be maintained), the test type, serial number, and display button are displayed corresponding to the equipment name to be maintained (module name).
[0068] The example of FIG. 8 shows a display example when the module name folders 8 of "Module A" and "Module B" are selected as the search folders, and each row corresponds to one analysis data file 82.
[0069] Specifically, in order from the top, it shows the results of the function test for the equipment with serial number 001 of Module A, the results of the function test for the equipment with serial number 002 of Module A, and the results of the function test for the equipment with serial number 001 of Module B. The analysis data displayed in the list may also be particularly referred to as reference data.
[0070] When the display button for each row is clicked, the test controller 20 reads out the corresponding analysis data file 82 and displays the detailed time-series analysis data as a list of test results for each module. The process of displaying the list of test results for each module is referred to as the test result display process for each module.
[0071] [Example of List of Test Results for Each Module: Figure 9] An example of the list of test results for each module will be described with reference to Figure 9. Figure 9 is an explanatory diagram showing an example of the list of test results for each module. As shown in Figure 9, in the list of test results for each module (described as the list of test results in the figure), the analysis data within the selected analysis data file is displayed in time series. Specifically, in the list of test results for each module, multiple pieces of data for test items, standard values, and test results are displayed.
[0072] In the example of Figure 9, for the relevant module, the test results of test item 0-1, test item 1-1, and test item 1-2 are displayed for two times, the previous time (June 8, 2020) and the current time (May 6, 2023). Here, it is shown for two times, but if there is analysis data stored for three or more times, more can be displayed.
[0073] Furthermore, the background color of the cell displaying the test result is changed according to whether the test result is normal (good), abnormal (bad), or at the boundary value which is the boundary between normal and abnormal. For example, when it is normal, the background color of the cell is white, when it is abnormal, it is red (dark gray in Figure 9), and when it is at the boundary value, it is orange (light gray in Figure 9).
[0074] This enables the maintenance staff to easily visually grasp which test items were defective, and by comparing with past test results, it becomes easier to estimate the cause of the defect, recognize the trend of performance degradation, and plan the maintenance of the module. In particular, by displaying the results in chronological order, it becomes easier to determine whether the cause of the defect is aging deterioration or other factors.
[0075] [Test Result Display Processing by Module: Figure 10] Next, the module-by-module test result display processing in the test controller 20 will be described with reference to FIG. 10. FIG. 10 is a flowchart showing the module-by-module test result display processing. As shown in FIG. 10, when any display button in the list of FIG. 9 is clicked, the test controller 20 acquires the path of the analysis data file 82 designated (S51).
[0076] Then, the test controller 20 reads out the individual analysis data from the analysis data file 82 (S52), generates the data of the module-by-module test result list (S53), and displays the module-by-module test result list (S54).
[0077] In addition, when generating the data of the module-by-module test result list in process S53, the test controller 20 compares the standard value and the test result for each test item, determines whether the background color of the cell is white, red, or orange, for example, and specifies the display color of each cell. In this way, the module-by-module test result display processing is performed.
[0078] [Effects of the Embodiment] According to this test apparatus, the test controller 20 attaches the measurement date to the measurement result data, stores it as a log file in the log folder, extracts the data for analyzing defects from the specified log folder as analysis data to generate analysis data, and distributes and accumulates the analysis data in the analysis data file 82 corresponding to the module name, test type, and serial number. When analyzing the defects of an individual module, if the module name, test type, and serial number are specified, the analysis data can be read from the corresponding analysis data file 82 and displayed in a list, enabling quick selection and display of the data available for defect analysis and efficient performance of defect analysis and maintenance work.
[0079] Also, according to this test apparatus, in the test result list by module for displaying the analysis data selected from the list screen, the test results of multiple test items for the same module are displayed multiple times in chronological order. Therefore, it is easier to grasp the deterioration trend of the apparatus by comparing with past test results and it can be used for planned maintenance work.
[0080] [Application Example] In the above example, only the data extracted by the maintenance staff from the log data is stored as analysis data. However, if there is room in the processing capacity and storage capacity, all test results may be sorted and stored in the corresponding analysis data file 82 in the corresponding folder in the analysis data storage unit 7. In this case, at the end of the test, the sorting process of the log data is performed. As a result, in the test result list by module, more detailed test results can be displayed, which is useful for inferring the cause of defects and planned maintenance work.
Industrial Applicability
[0081] The present invention is suitable for a test apparatus that can easily extract and display past test results and the like of defective maintenance target equipment from a huge log file, and can efficiently perform defect cause analysis and maintenance work.
Description of Symbols
[0082] 1…Test apparatus, 2…Device under test, 5…Memory unit, 6…Log data storage unit, 7…Analysis data storage unit, 8…Module name folder, 10…Measuring instrument, 20…Test controller, 21…Module, 30…Switching unit, 50…Execution history analysis screen, 51…Search folder selection unit, 52…Search folder reference button, 53…Output file selection unit, 54…Output file reference button, 55, 56…Execution button, 57…End button, 61…Log folder, 81…Test type folder, 82…Analysis data file
Claims
1. A test apparatus for measuring the performance of replaceable maintenance equipment of the equipment under test and conducting tests, Multiple measuring instruments that output test signals and measure the output from the equipment to be maintained, A switching unit that connects one of the aforementioned measuring instruments to the device under test, The system includes a test control unit that inputs and analyzes measurement result data from the aforementioned multiple measuring instruments, The test control unit stores the measurement result data as a log file in a log folder, adding the date of measurement to the measurement data; extracts data for analyzing defects from the log file as analysis data; generates analysis data files corresponding to the equipment to be maintained and the type of test; and distributes and stores the analysis data in the analysis data files according to the equipment to be maintained and the type of test.
2. The test control unit generates a folder in advance with the name of the equipment to be maintained, generates a folder with the name of the test type within that folder, generates an analysis data file within the folder with the name of the test type, and uses the serial number corresponding to the manufacturing number as the name of the analysis data file, as described in claim 1.
3. The test control unit displays a list of analysis data files corresponding to the name of the equipment to be maintained, the test type name, and the serial number of the equipment that has been tested, and displays the analysis data selected from the list as the test result on the display unit, as described in claim 2.
4. The test apparatus according to claim 3, characterized in that the test control unit displays the test results in a manner that allows comparison with past test results stored in the selected analysis data file when displaying the test results.
5. The test control unit, when displaying the test results, displays the test results in cells corresponding to the test items for each date, and changes the color of the cells depending on whether the test results are normal, abnormal, or fall within a boundary value between normal and abnormal, as described in claim 4.