Inspection system, program, and the like
The inspection system efficiently executes multiple inspection items by arranging devices and using predefined files to guide the process, reducing development time and cost while enhancing user interface flexibility.
Patent Information
- Application Number
- JP2023093957
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-06-07
- Publication Date
- 2024-12-19
AI Technical Summary
Conventional inspection systems require significant time and effort to build individual systems for each inspection item, making it inefficient to perform multiple inspection items sequentially on an object.
An inspection system that arranges multiple devices for different inspection items and moves the object to face each device sequentially, allowing for easy execution of inspection items without the need for complex switching mechanisms, using predefined inspection definition files to guide the inspection process and generate user interfaces for various inspection targets.
This approach reduces the time and cost required to develop and manage inspection systems, enabling flexible and efficient execution of multiple inspection items on different targets with reduced device complexity and improved user interface efficiency.
Smart Images

Figure 2024175878000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to, for example, an inspection system, a program, and the like. [Background technology]
[0002] Conventionally, various types of inspections have been performed at production sites of products, etc. For example, a detector that detects and reports wireless signals emitted from measuring equipment, etc. is known (for example, Patent Document 1). For example, after such equipment is manufactured, adjustments are made to optimize characteristics during operation and inspections such as checking the detection of wireless signals are performed. For example, inspections are performed by executing multiple inspection items in sequence, but since individual systems are constructed for each equipment, this takes a lot of time, and improvements have been desired. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Japanese Patent Application Publication No. 05-275934 Summary of the Invention [Problem to be solved by the invention]
[0004] An object of the present invention is to provide a system that is superior to conventional systems, for example, by easily executing a plurality of inspection items in sequence on an object to be inspected.
[0005] The purpose of the present invention is not limited to this, and the applicant intends to obtain rights for configurations that aim to obtain effects from parts of the configurations disclosed in this specification and drawings, etc., by filing a divisional application, amendment, etc. For example, this specification discloses a problem in which the part described as "can be" in this specification is read as "the problem is to be". The problems are described as being independent, and the applicant intends to obtain rights for the configurations for solving each problem separately by filing a divisional application, amendment, etc. Even if the problems are implicitly understood from the description in the specification, the applicant intends to include part of the configurations described in this specification in the scope of the patent claim by amendment or divisional application. In addition, the applicant has disclosed a configuration that solves a problem that combines these independent problems, and intends to obtain rights for it. [Means for solving the problem]
[0006] (1) One aspect of the system of the present invention is 1. An inspection system for inspecting at least one inspection object, comprising: It is preferable to sequentially perform a plurality of inspection items on the object to be inspected. In this way, it is easy to carry out a plurality of inspection items in sequence on the object to be inspected. In particular, it is preferable to have a function for carrying out a plurality of inspection items in sequence on the object to be inspected that is the inspection target. In this way, it is easy to carry out a plurality of inspection items in sequence on the object to be inspected.
[0007] The "inspection subject" may be specified by, for example, at least one of the "item to be inspected" and "multiple inspection items." The inspection target is set as a different inspection target when, for example, at least one of the object to be inspected and the multiple inspection items is different. As an example, when the object to be inspected is a wireless signal board that receives a wireless signal, the multiple inspection items are different in the case of an adjustment inspection for adjusting the received wireless signal and in the case of a confirmation inspection for confirming reception of a wireless signal, even if the object to be inspected is the same, so that the inspection targets are different. Also, when the object to be inspected is, for example, a wireless signal board, those with different versions or different product names may be set (handled) as different objects to be inspected and provided as different inspection targets. The inspection target can be arbitrarily defined by the user. The inspection may be configured to check whether the signal is in a preset normal state.
[0008] (2) It is preferable that a plurality of devices used for the plurality of inspection items are arranged, and each of the devices starts operating by moving the object to be inspected to a position opposite the device. In this way, multiple test items can be executed sequentially using simple means. For example, tests can be executed in one device without constructing a mechanism for switching between multiple functions. This reduces the time required to develop an inspection system.
[0009] The arrangement may be, for example, along the direction of movement. The arrangement may be, for example, on a disk and the movement may be performed by rotating the disk. The arrangement may be, in particular, on a straight line and the movement may be performed on the straight line. The movement to the opposing position may be, for example, automatically performed, or may be manually performed.Movement to the opposing position may be, for example, by placing the object to be inspected at a fixed position and moving the device, or may be, for example, by placing the device at a fixed position and moving the object to be inspected.Movement to the opposing position may be, in particular, by placing some of the multiple devices at a fixed position, or may be, for example, by placing all of the devices at fixed positions and moving the object to be inspected to each position of all of the devices. As a configuration in which each device starts operating by moving the object to be inspected to a position opposite each device, a configuration in which the other device starts operating in response to detecting that the object to be inspected has been moved from a position opposite a certain device to a position opposite the other device may be used, but a configuration in which each device starts operating in response to detecting that the object to be inspected is in a position opposite a specific device among multiple devices is preferable.
[0010] (3) the object to be inspected is a member having a substrate for receiving a wireless signal, Each device may output a different radio signal. In this way, a plurality of test items can be performed using one device without implementing a switching function that is required when switching wireless signals.
[0011] The "member comprising a board" may be a member comprising a board and a plurality of components mounted on the board, and may particularly be an integrated member. A signal take-off section may be provided from the board to obtain the test results when the test items are performed in sequence. The signal take-off section may comprise a component such as a connector soldered to the board, but the signal take-off section may not have a component such as a connector soldered to it, and may instead have a board pattern that is conductive when contacted with a conductive member from the outside to take out a signal. A plurality of components may be soldered to the board, but the signal take-off section may not be soldered. Also, the object to be inspected may be a member that constitutes a circuit by a board and components attached to the board.
[0012] Each device may be configured to output a different wireless signal, and a member having a board for receiving the wireless signal may output a signal when each of the different wireless signals is received, and inspection results may be obtained by combining inspection results based on all the different wireless signals.
[0013] (4) the at least one test object is a plurality of test objects; It is preferable that the system be provided with a function for generating and displaying an inspection screen showing the object to be inspected and the multiple inspection items based on an inspection definition file corresponding to one of multiple inspection definition files corresponding to each inspection object that have been created in advance and which identify the object to be inspected and the multiple inspection items, and a function for sequentially executing the multiple inspection items displayed on the inspection screen. In this way, by creating test definition files corresponding to multiple test targets, it is possible to provide a test system that displays a user interface for executing multiple test procedures. This makes it possible to execute multiple tests for different test targets in a single test system, thereby reducing the time required for developing and managing the test system.
[0014] It is preferable that multiple "test definition files" corresponding to multiple test objects are created in advance. For example, the test definition file may specify at least the object to be tested and multiple test items for each test object, and may be stored in a storage device or the like that can be referenced by the test system. The referable storage means may be, for example, one provided within the inspection system, one that is detachable from the inspection system, or one that can be read by the inspection system via communication (whether wired or wireless). It is preferable to have a function of storing the test definition files in a storage means, displaying a list of at least some of the test definition files, and allowing the user to select at least one of them as the test to be executed. The test definition file may be created by a human, but may also be created (eg, generated) by the system.
[0015] (5) The plurality of test definition files include, for each of the test objects, information for specifying the plurality of test items and an order in which the plurality of test items are to be executed; The function of generating and displaying the inspection screen may display information on the inspection screen in which the plurality of inspection items contained in the one inspection definition file are arranged in the order. In this way, the user can arbitrarily define the objects to be inspected or multiple inspection items for the inspection target. This allows the user to set the order of multiple inspection items for the inspection system they want to realize by creating an inspection definition file.
[0016] The "information specifying the order in which the multiple test items are to be performed" may be, for example, information listing the multiple test items in the order in which they are to be performed, or information (numeric values) specifying the order in which the multiple test items are to be performed. The "information in which the multiple test items are arranged in the order" may be, for example, a display in which the names of multiple test items are arranged in the order in which they are to be performed, or a display in which buttons indicating the names of multiple test items are arranged in order.
[0017] (6) the function of generating and displaying the inspection screen includes displaying a plurality of operation buttons on the inspection screen for receiving instructions regarding the execution of the plurality of inspection items; The function of sequentially executing the plurality of test items may be such that the plurality of test items are executed based on pressing of the plurality of operation buttons. In this way, the user can press the operation button to proceed with the execution of the test item at any timing. The pressing of an operation button may be detected by a click at the position of a pointer of an input device such as a mouse, but it is particularly preferable to detect the user pressing a touch panel.
[0018] The "operation buttons" may be provided, for example, with buttons for starting, stopping, canceling, etc. the execution of an examination item as instructions related to the execution.
[0019] (7) The plurality of operation buttons include an operation button for executing all of the plurality of test items and an operation button for executing each of the plurality of test items individually, The function of sequentially executing the plurality of test items may execute at least one of the plurality of test items based on a pressed operation button. In this way, any one of the multiple test items can be executed, so that it is possible to flexibly respond to cases where a specific test item among the multiple test items needs to be executed, thereby making it possible to reduce the cost required for testing and to avoid building a system that executes any one of the multiple test items.
[0020] The "operation button for executing all of the plurality of test items" may be, for example, a button used when executing a plurality of test items in sequence. In particular, it is preferable to provide one "operation button for executing all of the plurality of test items" on the screen. The "operation button for individually executing each of the plurality of test items" may be, for example, a button corresponding to each of the plurality of test items, and may be a button used when individually executing each of the test items, and the name of the test item may be indicated on the operation button. In particular, it is preferable to provide a plurality of "operation buttons for individually executing each of the plurality of test items" on the screen. "Executing at least one test item" may include, for example, a function of executing either all of a plurality of test items or executing the test item of the pressed operation button based on the pressed operation button.
[0021] (8) the plurality of operation buttons includes a progress button for proceeding to the next execution of the plurality of test items, The plurality of test definition files each include, for the plurality of test items, a test type indicating either an adjustment test requiring adjustment to the test result or a confirmation test for confirming the test result and proceeding to the next test, and a specified value to be compared with the test result in the confirmation test; The function of executing the multiple inspection items sequentially may, in the adjustment inspection, display the inspection results on the inspection screen and wait until the proceed button is pressed, and in the confirmation inspection, judge the inspection results of the confirmation inspection using the specified values, proceed to the next inspection item if the result is within the specified values, and display an error if the result is outside the specified values. In this way, it is possible to incorporate into multiple test items test items that require user processing such as adjustments depending on the test results. Also, in a test to confirm that the test results are within a specified range, it is possible to proceed with the test items in order without waiting for user confirmation. This makes it possible to provide a test system that can handle a variety of test items and to improve the efficiency of the execution of confirmation tests.
[0022] An "adjustment inspection" may be, for example, an inspection in which the user adjusts the object to be inspected using an adjustment means or the like based on the inspection results, and after completing the adjustment, the user presses a proceed button to proceed to the next inspection item.
[0023] (9) The function of generating and displaying the inspection screen may display the inspection item being executed on the inspection screen. In this way, the user can be notified of the inspection status.
[0024] "Displaying the test item currently being executed on the test screen" may, for example, mean displaying only the test item currently being executed, or when multiple test items are all being executed, displaying multiple test items and making it possible to identify the test item currently being executed by display processing such as changing the color of the test item currently being executed or making it blink.
[0025] (10) The inspection screen may display the results of executing at least one inspection item. In this way, the user can check the test results on the test display screen and can easily refer to the test results without performing any special operations. For example, this is useful when the user wishes to continue, stop, or cancel the test based on the test results during the confirmation test.
[0026] The "result of executing at least one test item" may be, for example, the test result of executing at least one test item among a plurality of test items, and may be displayed temporarily during the test, or may be displayed so that the results of executing each test item can be displayed at a glance, etc. As an example, it may be possible to display the measured value of each test item, and the judgment result of the measured value, such as OK or NG, etc.
[0027] (11) The function of sequentially executing a plurality of test items may include storing the test results of at least one of the test items. This makes it easier for the user to collect the test results after the test, perform processing using the test results, and so on.
[0028] The "results of executing at least one test item" may refer to the test results to be saved, for example, when the results of executing one test item are saved, when multiple test items are executed and all results are saved, or when the results of a test item selected in advance from among multiple test items are saved. In addition, the inspection system may be configured to store the inspection results of executing at least one inspection item using a function other than the function of sequentially executing the multiple inspection items, such as a function of generating and displaying the inspection screen, or may be configured to store the inspection results using a separate function such as a function of saving the inspection results or a function of using the inspection results.
[0029] (12) The test definition file corresponding to one of the test subjects may be selected by a user. In this way, the user can start a desired inspection system by selecting a desired inspection definition file for executing an inspection before starting the inspection. This allows inspection of different inspection targets to be executed by changing the inspection definition file in one inspection system (device).
[0030] The inspection system may be configured, for example, so that after the user selects an inspection definition file and confirms the inspection target, the user is prompted to press an operation button to start the inspection, thereby starting the execution of the inspection item.
[0031] (13) The inspection screen may have an area showing the inspection item being performed, an area showing the inspection status of the inspection item being performed while the inspection items are being performed, and an area showing the inspection results of the inspection items in sequence. In this way, the inspection status of the inspection item being performed can be displayed in real time along with the inspection results of the search items that have been executed.
[0032] The "area showing the test item being performed" may show the test item in the area showing the test status. The "area showing the test status" may display, for example, data showing the test status for the test item being performed. The "area that sequentially displays the test results" may display the test results (OK, NG, etc.) in the order in which a number of test items are performed, for example.
[0033] The "data indicating the test status" may, for example, display the measured values detected for the test item being performed. In this way, it is possible to check the measurement values of the inspection items being carried out at any time, and to grasp the inspection status of the objects being inspected in real time.
[0034] The measurement values may be displayed, for example, as numerical values, or may be displayed as a graph or the like.
[0035] It is also advisable to display the measurement values of the test items after they have been performed, in addition to the measurement values of the test items being performed. This makes it easier to check the measurement values of multiple test items at any time.
[0036] Furthermore, the test definition file has information for displaying the measurement values detected for the test item being performed in the area indicating the test status, and the area indicating the test status displays the measurement values for the test item being performed based on the information to be displayed. In this way, the load of displaying the measurement values according to the test object can be reduced when the function for sequentially executing a plurality of test items is used. The method of displaying the measurement values according to the test object can be selected according to the user's wishes.
[0037] The "information to be displayed" may be, for example, an application (software) that displays measurement values in an area showing the test status and that can activate a function to execute multiple test items in sequence. The "information to be displayed" may be, for example, information that displays a graph or the like in an area showing the test status. The area showing the test status may display, for example, the measured values of the test items being executed by a function for sequentially executing a plurality of test items (or a function for generating and displaying a test screen, etc.) by starting an application as the information to be displayed. Alternatively, the area showing the test status may display, for example, the measured values, etc. by a function for sequentially executing a plurality of test items (or a function for generating and displaying a test screen, etc.) by using the information to be displayed.
[0038] (14) The test definition file has information for forming a display area for displaying the test status of each test item in the area showing the test status, The function of generating and displaying the inspection screen may generate an area showing the inspection status using information that forms the display area. In this way, the function for generating and displaying an inspection screen can reduce the load of generating an individual display screen according to the inspection object. Also, the individual screen according to the inspection object can be generated in accordance with the user's intention.
[0039] The "information forming the display area" may be, for example, an application (software) capable of generating and displaying an inspection screen. The "information forming the display area" may be, for example, information specifying an image to be placed in the area showing the inspection status.
[0040] (15) For each inspection target, when inspecting a plurality of objects to be inspected, it is preferable to further provide a function of calculating a defect rate using the inspection results stored up to a predetermined timing, detecting a change in the defect rate, and notifying the detected change in the defect rate. In this way, it is possible to detect changes in the defect rate and to notify the user of the detected change in the defect rate, so that the user can take measures such as implementing measures to suppress the defect rate.
[0041] The "predetermined timing" may be, for example, when the number of produced units exceeds a preset number, or when the inspection result is NG. The "function of notifying the user of a change in the defect rate" may, for example, be a means of notifying the user of a change in the defect rate by combining one or more of a warning message, a change in the color of the display screen, a notification sound, etc., so as to draw the user's attention. The term "based on a change in the defect rate" may refer to, for example, when a change in the defect rate occurs, when the change in the defect rate exceeds a predetermined value, or the like.
[0042] The change in the defect rate may be detected by expanding the variation, for example, using the standard deviation, the absolute value of the deviation, the sum of squares of the deviation, the sum of cubes, or the sum of fourth powers of the deviation.
[0043] (16) For each inspection target, when inspecting a plurality of objects to be inspected, when the inspection results are acquired, a function of calculating a control index using the inspection results may be further provided. In this way, the production process capability and the like can be visualized based on the control index while the inspection is being carried out, which allows upstream management of the production process.
[0044] The control index may be, for example, a value indicating the proportion of test results that are NG for each test item.
[0045] (17) It is preferable that at least two types of inspection definition files are created for one inspection target, one for a mass production mode and one for a pre-production mode. In this way, it becomes easy to change the inspection items etc. according to the production system, and therefore it is possible to improve the production efficiency according to the production system.
[0046] (18) It is preferable that the device further has a function of expressing a value calculated using the test results using Bollinger bands. This makes it easier to analyze values calculated using the test results, and makes it easier to focus on problems that can be identified from the test results.
[0047] (19) The inspection results may be recorded in a memory means possessed by the object being inspected. In this way, it becomes possible to refer to the inspection results from the object being inspected.
[0048] The storage means may be, for example, an RFID (Radio Frequency Identification) that the object to be inspected has, or a non-volatile memory such as a flash memory, or a medium (such as an SD card) that is attached to the object to be inspected.
[0049] (20) The inspection results recorded in the memory means may be configured to be displayable on a device equipped with the object to be inspected. In this way, the inspection results can be viewed at the location where the device containing the object to be inspected is placed, making it possible to easily obtain information that is useful during maintenance, etc.
[0050] Furthermore, it is preferable that the display function be configured so that it can be displayed by a person who knows a secret code or operation, such as a serviceman, but cannot be displayed by the user.
[0051] (21) The test definition file includes a test item for instructing setting of test conditions and storing the test results in association with the test conditions for at least one of the plurality of test items, The function of sequentially executing the plurality of test items may store the test results executed in accordance with the instructions and the conditions at the time of the test in association with the conditions. In this way, it becomes possible to obtain the desired inspection results in association with the conditions at the time of the inspection, etc., and to store the results as data useful for predicting variations in component performance and tendencies for failure.
[0052] The "inspection conditions" may be, for example, outputting radio waves of a specific frequency within the radar's designed receiving frequency range from the jig, and identifying the position within the sweep range where the radar receives radio waves of that frequency.
[0053] (22) It is preferable that the area showing the inspection status can be selected to be displayed or not displayed. In this way, an appropriate display method can be selected depending on the examiner. For example, when an examiner who is inexperienced in testing performs an examination, it is possible to prevent the measurement values from being displayed in the area showing the examination status. This makes it possible to encourage the examiner to focus on the examination results shown in the area showing the examination results in sequence. In addition, when there is someone who does not want to see the examination status data, it is possible to select not to display the data.
[0054] The display and non-display can be realized, for example, by making it selectable by an operation button, or by creating, for each test subject, an test definition file for display and an test definition file for non-display.
[0055] (23) The inspection screen has an area for selecting an inspection item to be performed from among the plurality of inspection items, the region for selecting the test item to be performed is configured to prompt the user to select a test item to be performed from among the plurality of test items; The function of sequentially executing the multiple test items may sequentially execute the test items selected in an area for selecting the test items to be executed when an operation button for executing all of the multiple test items is pressed. In this way, when a desired test among a plurality of test items is to be executed, it is possible to flexibly respond without creating a new test definition file.
[0056] The "area for selecting the test items to be performed" may be displayed, for example, on the test screen before the test is started, or may be displayed when an operation button for executing all of a plurality of test items is pressed, and may be displayed as a screen prompting the selection of the test items to be performed. The "operation button for executing all of a plurality of test items" may be provided as a different button for prompting selection in the area for selecting the test items to be executed and for executing all of the test items.
[0057] (24) It is preferable to cause a computer to execute a program that realizes the functions of any one of the inspection systems described above in (4) to (23). This makes it easier to implement the functions of the inspection system in a computer, and also makes it easier to realize the functions of the inspection system using a plurality of devices, for example.
[0058] The inventions shown in (1) to (24) above can be arbitrarily combined. For example, at least a part of the configuration of at least one of the inventions after (2) may be added to all or a part of the configuration of the invention shown in (1). In particular, it is preferable to add at least a part of the configuration of at least one of the inventions after (2) to the invention shown in (1). In addition, any configuration may be extracted from the inventions shown in (1) to (24) and the extracted configurations may be combined. The applicant of this application intends to obtain rights to the inventions including these configurations. In addition, even if there is a description such as "in the case of" or "when", it is not intended to describe the configuration as being limited to that case or time. These are examples of better configurations, and the applicant intends to obtain rights to configurations other than these cases or times. In addition, the parts described in order are not limited to this order. Configurations in which some parts have been deleted or the order has been changed are also disclosed, and the applicant intends to obtain rights.
[0059] However, the following configuration provides particularly excellent results. For the above (2), it is particularly preferable to have the configuration of (1). For the above (3), it is particularly preferable to have the configuration of (2). For the above (4), it is particularly preferable to have the configuration of (1). For the above (5), it is particularly preferable to have the configuration of (4). For the above (6), it is particularly preferable to have the configuration of (4) or (5). For the above (7), it is particularly preferable to have the configuration of (6). For the above (8), it is particularly preferable to have the configuration of (6) or (7). For the above (9), it is particularly preferable to have any one of the configurations of (4) to (8). For the above (10), it is particularly preferable to have any one of the configurations of (4) to (9). For the above (11), it is particularly preferable to have any one of the configurations of (4) to (10). For the above (12), it is particularly preferable to have any one of the configurations of (4) to (11). For the above (13), it is particularly preferable to have any one of the configurations of (4) to (12). For the above (14), it is particularly preferable to have the configuration of (13). For the above (15) and (16), it is particularly preferable to have the configuration of (11). For the above (18), it is particularly preferable to have the configuration of (15) or (16). For the above (19), it is particularly preferable to have the configuration of (11). For the above (20), it is particularly preferable to have the configuration of (19). For the above (21), it is particularly preferable to have the configuration of (11). For the above (22), it is particularly preferable to have the configuration of (13) or (14). For the above (23), it is particularly preferable to have the configuration of (7). Effect of the Invention
[0060] According to the present invention, it is possible to provide an inspection system that can easily perform a plurality of inspection items in sequence on an object to be inspected.
[0061] The effects of the invention of this application are not limited to this, and effects obtained from the configuration disclosed in the specification and drawings, etc. are also disclosed, and the intention is to obtain rights to the configuration that achieves the effects by divisional applications, amendments, etc. For example, in this specification, the phrase "can" is a description that clearly indicates the effect that is achieved, and there are also parts that show the effect even without the phrase "can." Also, there are effects that can be understood from the configuration even without such a description. [Brief description of the drawings]
[0062] [Figure 1] FIG. 1 is a block diagram illustrating an example of the configuration of an inspection system according to a first embodiment. [Diagram 2] 4 is a flowchart illustrating the flow of inspection by the inspection system of the first embodiment. [Diagram 3] FIG. 2 is a diagram for explaining an example of an operation screen of the inspection system of the first embodiment. [Figure 4] 13 is a diagram illustrating an example of an RD board provided with screws and coils. FIG. [Diagram 5] FIG. 11 is a block diagram illustrating an overview of an inspection device to which the inspection system of the second embodiment is applied. [Figure 6] FIG. 11 is a block diagram illustrating an inspection system according to a second embodiment. [Figure 7] FIG. 11 is a block diagram illustrating a configuration example of an RD inspection device to which the inspection system of the second embodiment is applied. [Figure 8] 10 is a flowchart illustrating an example of an operation performed when the inspection system is started. [Figure 9] 13 is a diagram illustrating an example of a screen prompting selection of an examination definition file. FIG. [Figure 10] FIG. 13 is a diagram illustrating an example of a screen for prompting confirmation of the contents of an examination and acceptance of the start of the examination. [Figure 11] 13 is a diagram illustrating an example of an inspection screen at the start of inspection of RD adjustment. FIG. [Figure 12] FIG. 13 is a diagram illustrating an example of an inspection screen when a first inspection item of the RD adjustment is executed. [Figure 13]FIG. 13 is a diagram illustrating an example of an inspection screen when a third inspection item of the RD adjustment is executed. [Figure 14] FIG. 13 is a diagram illustrating an example of an inspection screen when a seventh inspection item of the RD adjustment is executed. [Figure 15] 13 is a diagram illustrating an example of an inspection screen when inspection of RD adjustment is completed. FIG. [Figure 16] FIG. 11 is a block diagram illustrating an example of the configuration of an SC inspection device to which the inspection system of the second embodiment is applied. [Figure 17] 13 is a diagram illustrating an example of an inspection screen at the start of an SC adjustment inspection. FIG. [Figure 18] FIG. 13 is a diagram illustrating an example of an inspection screen when a fourth inspection item of the SC adjustment is executed. [Figure 19] FIG. 13 is a diagram illustrating an example of an inspection screen when a ninth inspection item of the SC adjustment is executed. [Figure 20] 13 is a diagram illustrating an example of an inspection screen when an SC adjustment inspection is completed. FIG. [Figure 21] FIG. 2 is a diagram illustrating an example of an external interface connected to the control device. [Figure 22] FIG. 11 is a block diagram illustrating another example of an inspection device to which the inspection system of the second embodiment is applied. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0063] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In order to clarify the description, the following description and drawings have been omitted or simplified as appropriate. In each drawing, components and corresponding parts having the same configuration or function are given the same reference numerals, and the description thereof will be omitted.
[0064] An example of an inspection system that sequentially executes a plurality of inspection items for inspecting an inspection target will be described below. In each embodiment, the test is, for example, performed sequentially by executing a plurality of test items, and it is assumed that there is no process for determining, based on the test results or the like, in the middle of the multiple test items, which test item to select and execute next from the multiple test items, but rather that the test items are simply executed sequentially.
[0065] Embodiment 1. In this embodiment, an embodiment will be described in which an inspection system has a configuration in which a plurality of devices used for a plurality of inspection items are arranged, and each device starts operating by moving an object to be inspected to a position opposite each device. As an example of the inspection system, the configuration of a wireless signal inspection device will be used. In the following, for example, a case will be described in which the inspection subject is the "manufacturing adjustment of a radar detecting board" (also referred to as "manufacturing adjustment of an RD board"), the "object to be inspected" is the "radar detecting board" (also referred to as an "RD board") that detects radar, and the "multiple inspection items" are the "manufacturing adjustment" of manufacturing the RD board and adjusting its reception by the radar. The RD board is an example of a member that has a board.
[0066] FIG. 1 is a block diagram illustrating an example of the configuration of an inspection system according to the first embodiment. The first inspection system 10 (hereinafter referred to as the "inspection system 10") includes a personal computer (hereinafter referred to as the "PC") 11 as a control means, a serial communication adapter 12, a pin board fixing base 13, a spectrum analyzer 14, an adjustment base 15, a stabilized power supply 16, and an oscilloscope 17. In addition, a USB (Universal Serial Bus) board 18 is disposed between the PC 11 and the serial communication adapter 12, and an emulator 19 is disposed between the PC 11 and the pin board fixing base 13.
[0067] Adjustment base 15 has a plurality of horns 151 to 157, a substrate installation board 158, and a rail 159. Here, the plurality of horns 151 to 157 are an example of a plurality of devices used for a plurality of inspection items. The substrate installation board 158 is fixed to the pin board fixing base 13 .
[0068] When an inspection item is instructed by an inspector (user) pressing an inspection button or the like, the PC 11 transmits the instruction to the RD board mounted on the adjustment base 15 via the USB board 18 and the serial communication adapter 12. When the adjustment base 15 is mounted on the RD board, the contact probe on the adjustment base 15 comes into contact with the TP provided on the RD board, thereby achieving electrical continuity. In detail, the contact probe pin of the jig board mounted on the adjustment base 15 comes into contact with the TP (test point) provided on the back side of FIG. 4, thereby connecting the power supply / data line to the board. The TP is provided on the opposite side of the RD board from the side on which the screws and coil are mounted (see FIG. 4). The TP is a pad to which the contact pin for inspection is applied. When a flash write command is issued from the PC 11, the command is transmitted via the emulator 19 to the RD board installed on the adjustment base 15.
[0069] FIG. 2 is a flowchart illustrating the flow of inspection by the inspection system of the first embodiment. As a preparation step, an inspector sets the RD board on the board installation board 158 (S11). As a flash writing step, an inspector issues an instruction to start flash writing from the PC 11 (S12). When the flash writing to the RD board is completed, the inspector performs the reset process by turning the power OFF and ON.
[0070] After the power is turned on, the PC 11 displays an operation screen such as that shown in FIG. 3, and prompts the examiner to press a button to proceed with the examination. In the operation screen in Fig. 3, area A11 shows an X-band level meter, and area A12 shows a manufacturing tab. When the manufacturing tab is selected, areas A13 and A14 are displayed. Area A13 shows a button for an inspector to give instructions such as writing the production of a product, and area A14 shows the measured values. In addition, the operation screen is configured so that in addition to the manufacturing tab, each of the setting 1, setting 2, relay, writing, and manufacturing SC tabs can be selected.
[0071] The Settings 1 tab displays a screen used, for example, to send commands to the radar microcontroller requesting basic status or to configure the application itself (ROM version, etc.). The Settings 2 tab displays a screen used, for example, when sending or setting a command requesting the positioning status to the radar microcontroller (GPS status request, etc.). The Relay tab displays a screen used for making settings (such as baud rate settings) related to communications (between the PC and the board), for example. The Write tab displays a screen used to make detailed settings when writing in the Manufacturing RD tab (such as setting the Write Level to a fixed value). The Manufacturing SC tab, for example, displays a screen for performing manufacturing adjustment of an SC board. The Manufacturing SC tab may be configured to display, for example, at least a part of the items shown in an area A24 in FIG.
[0072] Next, as a local adjustment step, the inspector issues an instruction to initialize the frequency from the PC 11 (for example, by pressing the "Initial Setting (F1)" button provided in the area A13 in FIG. 3), and adjusts the local oscillation frequency to a predetermined value (for example, 11.543 GHz) by turning a screw (S14). The screw is an adjustment tool provided on the RD board, and the inspector adjusts the local frequency by turning the screw.
[0073] After adjusting the local frequency, the inspector turns the coil to adjust the noise waveform voltage so that it falls within a specified range (e.g., 0.8±0.1V) as a noise level adjustment process (S15). The voltage of the noise waveform is displayed, for example, on the oscilloscope 17 (Fig. 1). This can also be displayed within the app only if the oscilloscope is a model that can be connected to a GP-IB. The coil is an adjustment jig attached to the RD board, and the inspector adjusts the voltage of the noise waveform by rotating the coil. FIG. 4 shows an example of an RD board provided with screws and coils.
[0074] Next, the inspector performs the inspection items from steps S16 to S22 using multiple horns as a level adjustment process for adjusting the level of the received radar. In steps S16 to S22, the inspector slides board installation board 158, on which the RD board is installed, along rails 159 to move it so as to face any one of the plurality of horns 151 to 157, thereby carrying out the inspection.
[0075] The inspection system 10 is configured such that when the substrate mounting board 158 faces any of the multiple horns 151 to 157, the switch of the opposing horn is turned ON, a wireless signal based on the inspection item is output, and the results received by the RD substrate are displayed on the PC 11. Each horn (horns 151 to 157) serves as a housing that outputs a radio signal of a particular strength (RD Lv1 to 5, etc.). When board installation board 158 moves to the front of the horn, it steps on a switch installed on the pulley surface of board installation board 158, turning on the output of the horn in front (one of horns 151-157). Here, the oscillation side is each horn (horns 151-157), and the receiving side is the product board on board installation board 158. The examiner refers to the test results (e.g., the measurement values in area A14) displayed on the operation screen of PC 11 and moves on to the next test item if the result is normal, and if an error occurs, performs a specified process or ends the test.
[0076] The Level 1 verification process is a process for verifying the inherent Level 1 sensitivity of the RD board (product body). The level 3 adjustment process (level 3 writing process) is a process for writing a level 3 signal. The level 3 adjustment confirmation process involves outputting level 2 radar waves from the horn to confirm that level 3 writing has been done correctly. The level 5 write process is a process for writing a level 5 signal. The level 5 adjustment confirmation process involves outputting level 4 radar waves from the horn to confirm that level 5 has been written correctly.
[0077] The sensitivity of each level is as follows: Level 1 is the inherent sensitivity of the RD board (product body). Level 2 is a sensitivity between levels 1 and 3. Level 3 is the boundary value of the center sensitivity at the receiving strength guaranteed by the radar module. Level 4 is a sensitivity between levels 3 and 5. Level 5 is the boundary value of maximum sensitivity at reception strength guaranteed by the radar module. The bandwidth Lo is the boundary value of the minimum frequency band that can be received by the radar module, and limits the lower limit of the receiving frequency band of the radar module (it will not receive signals below a certain frequency band). The bandwidth Hi is the boundary value of the maximum frequency band that can be received by the radar module, and limits the upper limit band of the receiving frequency of the radar module (waves above a certain band will not be received).
[0078] The frequency relationship of horns 151 to 157 increases in the order from level 1 to level 5 (Lv1 < lv2 < lv3 < lv4 < lv5). X-band is the same frequency band but with different oscillation strength. Band LO and Band Hi are masks for the surrounding bands. The procedure from steps S16 to S22 will be described in detail below.
[0079] In the level 1 (Lv1) confirmation process, the inspector moves the board installation board 158 so that it faces the horn 153, and confirms that the level meter shown in area A11 on the screen of the PC 11 lights up to the level 1 value (e.g., "1") (S16). This confirms the inherent level 1 sensitivity of the RD board (product body). In the level 3 (Lv3) adjustment process, the inspector moves the substrate installation board 158 so that it faces the horn 155, confirms that the level meter lights up to the level 3 value (e.g., “3”), and presses the “S meter level 3 (F3)” button to write the level 3 signal (S17). Through these steps, the inspector stores in the RD board the state in which the RD board is receiving the radar wave output from the horn. In this way, the sensitivity (response value) corresponding to each level is stored.
[0080] In the level 3 adjustment confirmation process, the inspector moves the substrate installation board 158 so that it faces the horn 154, and confirms that the level meter lights up to the level 2 (Lv2) value (e.g., "2") (S18). The level 2 range of the RD module is determined by writing the level 3 threshold value. Therefore, by moving in front of the level 2 output horn (horn 154) after writing level 3, it is possible to simultaneously confirm that the level 3 writing was successful and to confirm that level 2 was received. If the writing has failed, reception is not possible. By writing the level 3 sensitivity in step S17, the level 2 sensitivity between levels 1 and 3 is determined, so in step S18, it is confirmed whether the RD board can determine the level 2 radar wave.
[0081] In the level 5 (Lv5) writing process, the inspector moves the board installation board 158 to face the horn 157, confirms that the level meter lights up to the level 5 value (e.g., "5"), and then presses the "S-meter level 5 (F4)" button to write the level 5 signal (S19). In this way, the level 5 sensitivity is stored in the RD board. By writing the level 5 threshold, the level 4 range of the RD module is determined. Therefore, by moving in front of the level 4 output horn (horn 156) after writing level 5, it is possible to simultaneously confirm that the level 5 has been written successfully and that the level 4 has been received. If the writing has failed, reception is not possible.
[0082] In the level 5 writing confirmation step, the inspector moves the substrate installation board 158 so as to face the horn 156, and confirms that the level meter lights up to the level 4 (Lv4) value (for example, "4") (S20). By writing a sensitivity of level 5 in step S19, it is confirmed in step S20 whether the RD board can determine level 4 radar waves.
[0083] The bandwidth Lo writing process is a process of limiting the band of the receiving frequency of the radar module (no reception below a certain band will be possible). In the bandwidth Lo writing process, the inspector moves the board installation board 158 so that it faces the horn 151, confirms that the level meter lights up to one of the values from level 1 to level 5, presses the "Bandwidth - Droop Voltage Lo (F7)" button, writes the bandwidth Lo, and then confirms that the value on the level meter goes out (S21). In the bandwidth Hi writing process, the inspector moves the board installation board 158 so that it faces the horn 152, confirms that the level meter lights up to one of the values from level 1 to level 5, presses the "Bandwidth-Dropout Voltage Hi (F8)" button, writes the bandwidth Hi, and then confirms that the value on the level meter goes out (S22). As an inspection end process step for ending the inspection after each inspection item has been performed, the inspector turns off the power of serial communications adapter 12, removes the RD board from board installation board 158, and ends the inspection (S23).
[0084] As explained in the level adjustment process above, the inspection system 10 has a configuration in which each device starts operating by moving the object to be inspected (the board installation board 158 with the RD board mounted thereon) to a position opposite each device, so that multiple inspection items can be executed in a simple manner. This configuration does not require the construction of a mechanism for switching between multiple devices when the number of inspection items to be inspected is within a predetermined range, and therefore has the effect of reducing the time required for the development of the inspection system and reducing the number of devices required for the mechanism for switching between multiple devices.
[0085] Embodiment 2. This embodiment describes an aspect in which an inspection system provides a user interface corresponding to a plurality of inspection targets.
[0086] The radio signal inspection device as the inspection system 10 described in the first embodiment has been described as an inspection target for manufacturing adjustment of an RD board. However, there are various combinations of the objects to be inspected and the inspection items. For example, for an inspection target of a board that detects a radio signal different from that of a radar, there is an inspection such as adjustment of a signal detection board (also called an "SC board") that detects a radio signal with a lower frequency than that of a radar. In the conventional technology, an individual system is constructed using an inspection device corresponding to each inspection target. When constructing each system, a user interface (also called a "UI") is generated that prompts the user to perform operations such as starting and stopping the inspection, and displays the inspection progress or the inspection results. Developing such a UI for each system requires time and the like for each system, which is a burden on the developer of the inspection system.
[0087] In this embodiment, an inspection system will be described that creates and displays UIs corresponding to a plurality of inspection targets based on information created in advance, and executes inspection of each inspection target.
[0088] The inspection system of this embodiment has a function of generating and displaying an inspection screen indicating the object to be inspected and the multiple inspection items based on an inspection definition file corresponding to one of multiple inspection definition files corresponding to each inspection target that have been created in advance, and a function of sequentially executing the multiple inspection items displayed on the inspection screen.
[0089] In this way, it is possible to provide a UI that can be used for a plurality of different test targets, and the cost (time, etc.) required to develop an application for each test target can be reduced. In addition, by using a definition file that describes multiple test items, a UI can be provided in a single application. In addition, the application has a function for executing multiple test items sequentially, which reduces the manpower required for testing, thereby further reducing costs.
[0090] The inspection system of the second embodiment may be applied to, for example, an inspection device that includes a control device that controls the entire inspection, and a group of devices that execute the inspection based on instructions from the control device. In the following, an embodiment will be described in which a PC is used as the control device.
[0091] With reference to FIG. 5, a case will be described in which the inspection system of this embodiment is applied to an inspection device that inspects a plurality of inspection targets using a plurality of different device groups. FIG. 5 is a block diagram illustrating an outline of an inspection device to which the inspection system of the second embodiment is applied. The inspection device 200 includes a first PC 210 and a second PC 270 as control devices, a first device group 230 that performs inspections based on instructions from the first PC 210, and a second device group 250 that performs inspections based on instructions from the second PC 270. The first PC 210 and the second PC 270 each include a memory and a control unit. The memory is, for example, a main storage device having a RAM (Random Access Memory) and a ROM (Read Only Memory). The memory has at least an area for temporarily storing an examination definition file that the control unit can refer to and that is read from the memory etc. The memory may have an area for storing, for example, a plurality of examination definition files. The control unit outputs a command to cause the group of devices to execute the test items. The control unit has, for example, a CPU (Central Processing Unit) etc. The control unit may have, for example, in addition to the CPU, an MPU (Micro Processing Unit), a GPU (Graphics Processing Unit), an ASIC (Application-Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), etc. The control unit temporarily stores the program read from the ROM of the memory in the RAM. The RAM of the memory provides a working area for the control unit. The control unit performs various controls by temporarily storing data generated during the execution of the program in the RAM and performing arithmetic processing.
[0092] The inspection device 200, for example, as the inspection system of embodiment 2, may use a program that causes the first PC 210 and the second PC 270 to execute the function of generating and displaying the above-mentioned inspection screen and the function of sequentially executing multiple inspection items. In the first PC 210 and the second PC 270, applications (programs) of the inspection system and related drivers (drivers for relay devices, communication, audio, etc.) are pre-installed.
[0093] Fig. 6 is a block diagram for explaining the inspection system of embodiment 2. Fig. 6 shows an example in which a second inspection system 20 (hereinafter referred to as "inspection system 20") is introduced into the first PC 210, but the second PC 270 can also be similarly introduced. The inspection system 20 has at least a function 21 for generating and displaying an inspection screen, and a function 23 for sequentially executing a plurality of inspection items. These functions are configured to provide information to a user and receive instructions from the user via a display unit 211 and an operation unit 213 provided in the first PC 210. An outline of the functions of the inspection system 20 will be described.
[0094] The function 21 for generating and displaying an inspection screen displays a screen showing the names of multiple inspection definition files (or information for identifying multiple inspection targets, etc.) on the display unit 211 and prompts the user to make a selection. The function 21 for generating and displaying an inspection screen reads out one inspection definition file selected by the user via the operation unit 213 from a referable storage means, etc., and holds it in memory. Next, the function 21 for generating and displaying an inspection screen creates an inspection screen corresponding to the inspection target of the inspection definition file selected by the user based on the inspection definition file, and displays it on the display unit 211. The inspection screen displays operation buttons that prompt the user to perform operations such as starting, stopping, and canceling the inspection. After displaying the inspection screen, the inspection system 20 waits for instructions from the user.
[0095] When the user presses an operation button to instruct the start, stop, or abort of an examination, a function 23 for sequentially executing multiple examination items causes the group of devices to execute the examination based on the user's instructions and obtains the examination results.
[0096] By applying the inspection system of this embodiment to a control device (such as a PC), it is possible to generate and display an inspection screen corresponding to each of multiple inspection objects based on an inspection definition file corresponding to each of the multiple inspection objects, and to sequentially execute multiple inspection items for the inspection objects on the corresponding equipment groups, etc. As an example, a case will be described in which a first inspection target to be inspected using the first device group 230 and a second inspection target to be inspected using the second device group 250 are provided as the multiple inspection targets. The first PC 210 generates and displays an inspection screen based on an inspection definition file of the first inspection target, and can cause the first device group 230 to sequentially execute multiple inspection items of the first inspection target. The second PC 270 generates and displays an inspection screen based on an inspection definition file of the second inspection target, and can cause the second device group 250 to sequentially execute multiple inspection items of the second inspection target. This eliminates the need to build a function for generating an inspection screen corresponding to each inspection object, thereby reducing the time and cost required for designing and building an inspection system corresponding to each inspection object.
[0097] Here, the examination definition file will be described. The test definition file includes at least information specifying a plurality of test items and the order in which each test item is to be performed. One test definition file is created in advance for each of a plurality of test objects. The plurality of test definition files created for each test object are stored in a storage means or the like that can be referenced by the control device.
[0098] The test definition file is created, for example, by a plurality of commands, and describes character strings of commands and parameters. The information specifying the order in which each test item is executed may be, for example, the order in which the commands specifying the test items are written.
[0099] Next, an example of multiple commands will be described. The multiple commands include, for example, commands related to initial settings, test items, and end settings. The initial setting command sets, for example, the model name of the object to be inspected, the address of the device group, external input, the output destination when a NG judgment is made, and the like. The command for the test item sets, for example, the designation of the test item, a default value, an instruction to send to the group of devices, a waiting time during the test, and the like. The end setting command may, for example, set the saving of the test results.
[0100] For a plurality of commands, for example, combinations of the contents to be set by each command and parameters corresponding to each command are prepared in advance and provided to the user. For example, the user creates an examination definition file using a plurality of prepared commands.
[0101] Here, an example of a command related to an examination item will be described. To specify an examination item, for example, the examination type and examination item name are specified as parameters, and written as "command, examination type, examination item name". The test type is specified as, for example, either "adjustment test" or "confirmation test." An "adjustment test" is a test that requires adjustments to the test results, and the test cannot proceed to the next test item unless the inspector checks the test results and presses the next button; this is also called a "single test." A "confirmation test" is a test that checks the test results (for example, checks that no errors have occurred) and proceeds to the next test, whereas a "continuous test" is a test that proceeds to the next test item without the inspector checking it, and ends if the test results are NG.
[0102] In this embodiment, for example, a command "HE○" is prepared as a command for specifying an examination item. "O" is a number ranging from 1 to the maximum number of test items that can be registered in the test definition file (for example, 50). For example, "HE1, T, FW write" means the following: HE1: First test item T: Unit inspection (adjustment inspection) FW Write: Name of individual button inspection 1 A command for executing an examination item is written after the specification of the examination item (eg, command "HE1") and before the specification of the next examination item (eg, command "HE2"). The function 21 for generating and displaying an inspection screen acquires the number, order, etc. of a plurality of inspection items based on a command ("HE○") specifying an inspection item, and generates an inspection screen.
[0103] Next, an example of a command for executing a test item will be described. The transmission modulation adjustment (command KE), which sets the default value for the test, specifies the test name, upper limit of the default value, lower limit of the default value, and unit as parameters, and is written as "KE, test name string, upper limit of the default value (decimal), lower limit of the default value (decimal), unit string." To set the waiting time (command "WT"), for example, the waiting time (in milliseconds) is specified as a parameter, and is written as "WT, waiting time (decimal)".
[0104] Receiving a measurement value (command IR) specifies an acquired data index, a coefficient, and a unit as parameters, and is written as "IR, a numerical value specifying the index, a coefficient (decimal), a unit." The acquired index data is shown as an example of a unit for selecting received measurement data, and data may be selected by other methods.
[0105] When sending a message (for example, commands SO1 and SO2), the message string is specified as a parameter, and written as "SO1, string" or "SO2, string." Command SO1 is used as the operation procedure displayed during automatic inspection, and command SO2 is used as the operation procedure displayed during manual inspection. The message is displayed, for example, in area A25, which will be described later with reference to FIG. 11, etc.
[0106] To execute an inspection (for example, commands RD and SC), the inspection button number is specified as a parameter, and written as "RD, number" or "SC, number". Command RD is a command to execute an inspection of RD adjustment, and SC is a command to execute an inspection of SC adjustment. Here, executing an inspection is the same process as, for example, pressing a button for an inspection to be executed when manually inspecting an inspection device. The inspection definition file, for example, writes commands to set the equipment to be used in the inspection to be executed, commands to instruct the equipment to be used in the inspection to be executed, etc., before writing command RD or command SC. The test button numbers are numbers that are associated with search items in advance. The test definition file may have, for example, a table that associates test button numbers with test items. The test button numbers may correspond to test contents in area A24 (or individual buttons in area A23), which will be described later with reference to FIG. 11 etc. In this embodiment, it is assumed that a test is performed by pressing a button for the test contents (or test items).
[0107] Table identification (e.g., commands T1 and T2) is written as "T1, ON" or "T2, ON". Command T1 identifies the currently used table (table in use) as table 1, and command T2 identifies the currently used table as table 2. When commands T1 and T2 are used, it is assumed that the test uses multiple tables, and when identifying one table, the other tables are not identified.
[0108] In addition, inspection items are executed by commands sent to each device group. Detailed explanations are omitted here. Note that the above-mentioned commands and command parameters are merely examples and are not limited to these, and the names of commands, types of parameters, etc. are appropriately set so that the inspection system can interpret them. The inspection system 20 inspects the inspection target by executing a plurality of commands in the inspection definition file in sequence using a function 23 for sequentially executing a plurality of inspection items.
[0109] By using such an inspection definition file, when inspection system 20 inspects inspection objects having different objects to be inspected, types of inspection items, numbers of inspection items, etc., it is possible to provide a UI corresponding to the inspection object and execute the inspection items by reading the inspection definition file corresponding to the inspection object. In addition, when there are two or more similar inspection targets among multiple inspection targets, a part of one similar inspection target file can be rewritten to easily create an inspection target file corresponding to the other similar inspection targets.
[0110] For example, there may be cases where the objects to be inspected are different but multiple similar inspection items are inspected, or the objects to be inspected are the same but some of the inspection items are different, etc. In such cases, it is possible to create an inspection definition file that corresponds to any inspection object by rewriting parts (name, specified value, parameters, inspection items, etc.) of the inspection definition file for the similar inspection object. As a specific example, when executing the same multiple inspection items even though the models of the multiple inspected objects are different, since the antenna shapes and characteristics are different, sensitivity adjustments, horn output levels during confirmation, etc. can be accommodated by using an inspection definition file created by changing command parameters.
[0111] The inspection system 20 will be described below using a specific example of an inspection device 200 to which the inspection system 20 of this embodiment is applied. As an example of the inspection device 200, a configuration example having an RD inspection device and an SC inspection device is used. The RD inspection device has a configuration corresponding to the first PC 210 and the first equipment group 230 in Figure 5, with the inspection target being the "manufacturing adjustment of the RD board", the object to be inspected being the "RD board", and multiple inspection items being the "manufacturing adjustment" of manufacturing the RD board and adjusting its reception by the radar. The SC inspection device is configured to correspond to the second PC 270 and second equipment group 250 in Figure 5, with the inspection target being "reception confirmation of SC board", the object to be inspected being the "SC board", and multiple inspection items being "reception confirmation" to confirm the reception of a wireless signal by the SC board. The inspection definition files corresponding to the manufacturing adjustment of the RD board and the reception confirmation of the SC board are created by the user and are stored in advance in a storage means that the inspection system 20 can refer to.
[0112] FIG. 7 is a block diagram illustrating a configuration example of an RD inspection device to which the inspection system of the second embodiment is applied. The RD inspection device 201 includes a PC 31 as a first PC 210 (control device), and a first equipment group 230 including a serial conversion jig 32, a pinboard fixing stand 33, a spectrum analyzer 34, an adjustment base 35, a stabilized power supply 36, an oscilloscope 37, a GPIB (General Purpose Interface Bus) converter 38, an emulator 39, a controller unit 40, a signal generation unit (hereinafter referred to as "SG") 41, and a coaxial switching jig 42. The adjustment base 35 has a horn 351 and a substrate mounting board 353 . These parts are connected as shown by lines in FIG.
[0113] The PC 31 sends instructions to the spectrum analyzer 34, the oscilloscope 37, and the SG 41 via the GPIB converter 38. The PC 31 also sends instructions to the serial conversion jig 32 and the coaxial switching jig 42 via the controller unit 40.
[0114] The RD inspection device 201 includes an inspection system 20 of this embodiment in a PC 31. When the inspection system 20 is activated by a user via an operation unit 213 of the PC 31, the inspection system 20 starts processing. FIG. 8 is a flowchart illustrating an example of the operation of the inspection system when it is started up. When the inspection system 20 is started, it executes the following processes in order: selection of an inspection definition file (FIG. 9), confirmation of the inspection contents and acceptance of the start of the inspection (FIG. 10), display of an inspection screen (FIG. 11, etc.), and execution of the inspection. The details are described below.
[0115] When the inspection system 20 is started (S31), the inspection system 20 displays the example screen shown in FIG. 9 on the display unit 211, and prompts the user to select an inspection definition file (S32). FIG. 9 is a diagram for explaining an example of a screen in which the inspection system 20 prompts the user to select an inspection definition file. For example, when an inspection application is started, an arbitrary folder that stores an inspection definition file is opened. In the inspection system 20, a specific folder is predefined as an inspection definition folder. For example, a plurality of inspection definition files are saved in a folder C:\teigi. The inspection system 20 displays the file name of each inspection definition file on the screen of FIG. 9. FIG. 9 shows an example of a state when "RD adjustment_separate model" is selected. When the user presses the select button, the inspection system 20 reads the selected inspection definition file and displays the example screen shown in FIG. 10 on the display unit 211 based on the inspection definition file (S33). Fig. 10 is a diagram for explaining an example of a screen on which the inspection system 20 prompts the user to confirm the contents and accept the start of the inspection. Fig. 10 shows the model name and the like described in the inspection definition file, prompting the user to confirm the selected inspection definition file and input manufacturing information and the like, and indicates that the inspection will start when the user presses the start button.
[0116] When the user presses the start button, in the inspection system 20, the function 21 for generating and displaying an inspection screen generates an inspection screen based on the inspection definition file read in step S33, and displays it on the display unit 211 (S34). FIG. 11 is a diagram for explaining an example of an inspection screen at the start of an RD adjustment inspection. The function 21 for generating and displaying an inspection screen generates and displays an inspection screen having, for example, an area A21 for the display screen, an area A22 for the inspection, an area A23 for operation buttons, an area A24 for the object to be inspected and the inspection items, an area A25 for prompting operation, an area A26 for performing the inspection, and an area A27 for the inspection results.
[0117] The area A21 relating to the display screen has, for example, items such as file, display, and setting, and allows the following selection for each item. File: "Switch model", "Save inspection log", "Exit" Display: "Reset production volume", "Display debug mode" Settings: "Model Settings"
[0118] The inspection-related area A22 displays, for example, the model name, inspection item name, inspection type, inspection name, inspection standard (Min / Max), inspection number, and production quantity. Model name: The name of the model being inspected Inspection Item Name: Inspection Item Being Executed Inspection type: Unit inspection (adjustment inspection), continuous inspection (confirmation inspection), etc. Test Name: The name of the test being performed Inspection standard (Min / Max): Displays the specification range for the inspection name, and is also used to check whether the measured value is within the specification range during confirmation inspection. Test Number: The number of the test being performed Production volume: Current production volume inspected By selecting "Reset production volume" in the display of area A21, the production volume can be reset (to zero).
[0119] The operation button area A23 has buttons for each of a plurality of examination items and buttons for predetermined basic operations. The function 21 for generating and displaying an inspection screen provides buttons for each of a plurality of inspection items on the inspection screen based on the designation of the inspection item determined by the command "HE○" in the inspection definition file. Since the buttons for the inspection items are specific to the inspection subject, it is advisable to provide the maximum number of registrable inspection items (for example, 50) in the inspection definition file. The name of the test item button may be the "test item name" parameter of the command "HE○".
[0120] In addition, the function 21 for generating and displaying the inspection screen is provided with predetermined basic operation buttons, such as an inspection stop button, a mute button, an automatic operation button, and a next button. The predetermined basic operation buttons may be set as buttons that are permanently displayed on the inspection screen, for example. The test stop button will stop the test immediately. The mute button stops the output of sounds when an examination is completed, etc. The automatic operation button executes the inspection items registered in the inspection definition file sequentially, starting from the top, such as item 1, item 2, item 3, etc. The Next button will end the test item currently being performed and move on to the next test item.
[0121] A function 23 for sequentially executing a plurality of test items by pressing (clicking) a desired test item button on the test screen executes only the corresponding test item. The function 21 for generating and displaying an inspection screen generates the inspection screen so that input other than an inspection stop button and a next button is not accepted during the inspection.
[0122] The area A24 relating to the object to be inspected and the inspection items has a main body information area A241, a real-time display area A242, and an inspection item display area A243. The main body information area A241 displays main body information acquired from the object to be inspected (inspection board). The real-time display area A242 displays the current status in real time based on the information acquired from the test board.
[0123] The test item display area A243 sequentially displays test contents corresponding to a plurality of test items. During execution of a test item, the test item display area A243 may be displayed, for example, in a different color or brightness so that the test contents being executed can be identified. The test contents displayed in the test item display area A243 are test contents to be executed, for example, by command RD, and the number on the left is the test button number. The command RD plays the role of pressing (or clicking) the button indicating the test content displayed in the test item display area A243. Of the test contents displayed in the test item display area A243, "status request" and "initialization" are preferably set in advance and assigned unique test button plates.
[0124] Since the real-time display area A242 and the test item display area A243 contain information specific to the test subject, the function 21 for generating and displaying the test screen generates the test display screen based on the information described in the test definition file. For example, the user may define in the test definition file the collection method (collection destination) of information specific to the test subject to be displayed on the test display screen, the display method of the collected information on the screen, etc., according to the test contents. Alternatively, the user may use another application or the like that functions to collect information and display the collected information. In such a case, by describing the application in the test definition file, the test system 20 may use (launch) the specified application and cause the application to collect information and / or display the collected information.
[0125] The area A25 for prompting an operation displays a message prompting the user to perform an operation, and when no operation by the user is required, the examination status such as "Automatic examination in progress" or "Examination completed" is displayed.
[0126] The area A26 relating to the execution of the test displays the status of transmission / reception between the first PC 210 and the first device group 230 (or between the second PC 270 and the second device group 250). For example, it displays status such as "sending command", "individual device test in progress", "continuous test in progress", transmitted data, received data, etc.
[0127] The test result area A27 displays the test results for each test item. For example, the test results may be displayed in order after each test item is performed.
[0128] Furthermore, the inspection system 20 proceeds with the inspection as follows, based on the type of inspection, for example, confirmation inspection or adjustment inspection. The function 23 for sequentially executing a plurality of inspection items collates the values of the measuring device with the specifications during confirmation inspection to determine pass / fail. If the result is a pass (OK), the inspection result area A27 is temporarily turned green (for example, until moving on to the next inspection item), and then the process moves on to the next inspection item. In the case of failure (NG), the inspection result area A27 is turned red and the inspection execution is stopped at the current failed inspection. During the adjustment inspection, the values of the measuring device are displayed in real time on the inspection screen (for example, the real-time display area A242). Pressing the Next button moves to the next inspection item.
[0129] Furthermore, the inspection system 20 may be configured such that, for example, when "record inspection log" is selected in the file in the area A21 related to the display screen, the results of the confirmation inspection are constantly recorded. This concludes the description of the example of the test screen at the start of the test. In the following description, for example, "area A21 related to the display screen" will be abbreviated as necessary to "area A21".
[0130] When the example screen of Figure 11 is displayed, if the user presses a button for automatic operation or an individual test item, function 23 for executing multiple test items sequentially starts automatic operation or execution of an individual test item (S35). The function 23 for sequentially executing a plurality of test items causes the devices to execute each test item according to commands written in the test definition file. An example of carrying out an inspection similar to the operational example of FIG. 2 will be described below.
[0131] 12 shows an example of an inspection screen when flash writing (S12 in FIG. 2) is executed as the first inspection item of RD adjustment after the automatic operation button is pressed. The inspection item name in area A22 is displayed as "FW Write", and area A25 displays a message prompting the user to operate, and to press the next button after operating. In area A23, the automatic operation button is hidden, and in area A24, of the multiple inspection items, inspection button number 1 "Initialization and Initialization" is displayed in a different color from the other inspection items.
[0132] 13 shows an example of an inspection screen when performing local adjustment (S14 in FIG. 2) and noise level adjustment (S15 in FIG. 2) as the third inspection item of RD adjustment. The inspection item name in area A22 is displayed as "Transmission frequency / noise adjustment," and area A25 displays a message encouraging the user to perform an operation and to press the next button after the operation. 14 shows an example of the inspection screen when executing level 5 writing (S19 in FIG. 2) as the seventh inspection item. The inspection item name in area A22 is displayed as "S-meter Level 5 writing", the message "Automatic inspection in progress" is displayed in area A25, and the inspection results during the automatic inspection are displayed in area A27.
[0133] 15 shows an example of the inspection screen when the RD adjustment inspection is completed. The inspection item name in area A22 is displayed as "Inspection completed", the message "Inspection completed" is displayed in area A25, and the inspection results of the inspection items performed in the automatic inspection are displayed in area A27. When the test is completed, the function 23 for sequentially executing a plurality of test items stores the test results in a predetermined storage area (S36). The storage area for storing the test results is set in advance. For example, it is preferable to be able to specify the storage area for storing the test results in the test definition file.
[0134] Thereafter, function 21 for generating and displaying an inspection screen displays the screen at the start of inspection in Fig. 11 (S37). At this time, function 21 for generating and displaying an inspection screen increments the numerical value of the number of produced vehicles in area A22 by one and displays it. Function 23 for sequentially executing a plurality of inspection items waits for an instruction to start the next inspection, etc., and when the user presses the button for automatic operation or an individual inspection item (continue inspection in S38), starts the process from step S35, and ends the inspection when there is no instruction from the user within a predetermined time period or when the user closes the inspection screen (end inspection in S38). Furthermore, if an error occurs during testing, function 23 for sequentially executing a plurality of test items displays a message in area A25 notifying the user of the occurrence of the error, saves the test results in a specified storage area, and ends the test.
[0135] Next, the SC inspection device will be described. FIG. 16 is a block diagram illustrating a configuration example of an SC inspection device to which the inspection system of the second embodiment is applied. The SC inspection device 203 includes a PC 51 as a second PC 270 (control means), and a serial conversion tool 52, an adjustment tool 53, a spectrum analyzer 54, an audio analyzer 55, a stabilized power supply 56, an oscilloscope 57, a GPIB converter 58, and a controller unit 59 as a second device group 250. These units are connected as shown by lines in FIG.
[0136] The PC 51 sends instructions to the spectrum analyzer 54, the audio analyzer 55, and the oscilloscope 57 via the GPIB converter 58. The PC 51 also sends instructions to the serial conversion jig 52 via the controller unit 59.
[0137] The SC inspection device 203 includes the inspection system 20 of this embodiment in the PC 51. The inspection system 20 starts processing when activated by a user via the operation unit 213 of the PC 51 at the start of inspection. An example of the operation of the inspection system 20 in the SC inspection device 203 will be described with reference to FIG. When the inspection system 20 is started (S31), it selects an inspection definition file (S32), confirms the inspection contents, and accepts the start of the inspection (S33) in the same manner as the RD inspection device 201. Here, an example will be described in which "SC adjustment_separate model" is selected from the multiple inspection definition files shown in FIG.
[0138] In the example screen of Figure 10, when the user presses the start button, the inspection system 20 causes the function 21 for generating and displaying an inspection screen to generate an inspection screen based on the selected inspection definition file and display it on the display unit 211 (S34). FIG. 17 is a diagram for explaining an example of an inspection screen at the start of an SC adjustment inspection.
[0139] Areas A21 to A27 are divided in the same manner as in FIG. 11, but are different in that areas A23, A24, A26, etc. are generated to correspond to a plurality of examination items. For example, the operation button area A23 has individual buttons for each of the multiple test items defined in the test definition file, so the names and number of test items vary. Also, the area A24 related to the object to be tested and the test items will be displayed differently depending on the test subject.
[0140] For example, in the structure of an in-app user interface (UI), if an inspection definition file is not loaded, the inspection button will not be generated (it will not even exist). By selecting an inspection definition file, the UI within the app is automatically generated according to the selected inspection content. For example, if there is one inspection process, there will be one inspection button within the app. If there are ten inspection processes, there will be ten inspection buttons within the app. In this way, the app (screens generated by the app, etc.) is structured to change shape based on the information in the inspection definition file.
[0141] The test contents displayed in the test item display area A243 are test contents to be executed by, for example, command SC, and the number on the left side is the test button number. Command SC plays the role of pressing (or clicking) the button showing the test contents displayed in the test item display area A243. This is the same as command RD described in FIG. 11.
[0142] When the example screen of Figure 17 is displayed, if the user presses a button for automatic operation or an individual test item, function 23 for executing multiple test items sequentially starts automatic operation or execution of an individual test item (S35). The function 23 for sequentially executing a plurality of test items causes the devices to execute each test item according to commands written in the test definition file.
[0143] Fig. 18 shows an example of the inspection screen when performing a band edge reception check as the fourth inspection item of the SC adjustment after the automatic operation button is pressed. The inspection item name in area A22 is displayed as "Band Edge Reception Check", the message "Automatic inspection in progress" is displayed in area A25, and the inspection results during the automatic inspection are displayed in area A27. Also, the automatic operation button is not displayed in area A23. The test item display area A243 of the area A24 indicates that the test for "Table Selection" of test button number 4 is currently being performed. In Fig. 18, the item for "Table Selection" of test button number 4 is displayed in a different way (such as a different color) from the others.
[0144] Test button number 4 "Table Selection" selects table 1 or table 2 depending on the test results. Then, test button numbers 10 and 11, which are executed after that, inspect the reception confirmation at the frequency according to the selected table. Fig. 18 shows an example of the display when table 1 is selected in "Table selection". If table 2 is selected in "Table selection", test button numbers 10 and 11 inspect at the frequency according to table 2, so the "347.7125MHz (Table1)" frequency displayed in test button number 10 in area A243 and the "340.8MHz (Table1)" frequency displayed in test button number 11 will be the frequency of table 2 (Fig. 17, button UI for 10 and 11 in area A243).
[0145] Fig. 19 shows an example of an inspection screen when SINAD sensitivity check is executed as the ninth inspection item of SC adjustment. The inspection item name in area A22 displays an outline of the frequency for which sensitivity is to be checked (if the exact frequency is to be displayed, it will be "350.100MHz"), such as "SINAD sensitivity check (350)". Area A25 displays the message "Automatic inspection in progress", and area A27 displays the inspection results during the automatic inspection.
[0146] 20 shows an example of the inspection screen when the inspection is completed. The name of the inspection item in area A22 is displayed as "Inspection completed", the message "Inspection completed" is displayed in area A25, and the inspection results of the inspection items performed in the automatic inspection are displayed in area A27. When the test is completed, the function 23 for sequentially executing a plurality of test items stores the test results in a predetermined storage area (S36).
[0147] Thereafter, the function 21 for generating and displaying an inspection screen displays the screen at the start of inspection in Fig. 16 (S37). At this time, the function 21 for generating and displaying an inspection screen adds one to the number of production units in the area A22 and displays it. The process of step S38, the process when an error occurs, and the like are similar to the processes explained in the RD inspection device 201, and therefore the explanation will be omitted.
[0148] Here, the storage destination of the inspection results in step S36 in FIG. 8 will be described. The function 23 for sequentially executing a plurality of test items may store the test results of at least one executed test item in a preset storage means. The test system 20 may be configured to allow the storage means to be specified, for example, by setting the storage means in a test definition file, or by specifying the storage means using a screen that allows the user to input information when starting the test (such as changing FIG. 10 or displaying a screen for specifying the storage means after FIG. 10). Furthermore, the test system 20 may be configured to display a screen that prompts the user to specify the storage means at the timing of saving the test results when the storage means to be stored has not been specified.
[0149] In addition, the inspection system 20 may have a function that allows the user to select the inspection results to be saved. In this way, the user can select and save the inspection results to be used after the inspection, thereby reducing the amount of data to be saved. In addition, it is possible to save useful inspection results based on the user's intentions and the subject of the inspection, making it easier to refer to them efficiently after the inspection.
[0150] Variation 1 of embodiment 2 The functional configuration example in FIG. 6 is an example, and the functions of the inspection system 20 may be configured as one function, or the functions may be further divided, such as by separating the function of saving the inspection results. Also, in the above embodiment, the functions described as being executed by the function 21 for generating and displaying an inspection screen or the function 23 for sequentially executing a plurality of inspection items may be executed by the other.
[0151] In addition, the inspection system 20 can be configured to have other functions described in each embodiment below, in addition to the function 21 of generating and displaying an inspection screen and the function 23 of sequentially executing multiple inspection items.
[0152] When starting the inspection system 20, the inspection system 20 may be configured so that the user selects (clicks) an inspection definition file from a folder in the control device (PC) in which the inspection definition file is saved.
[0153] Variation 2 of embodiment 2 In the above embodiment, the inspection system 20 has been described as receiving instructions from a user via the operation buttons displayed on the inspection screen, but may be configured to receive instructions from a user using an external operation device. For example, an operation device may be connected to the control device (first PC 210, second PC 270, etc.) via an external interface as shown in Fig. 21 to receive instructions from a user. For example, buttons such as Examination 1, Examination 2, . . . shown in area A23 of FIG. 11 correspond to buttons such as Examination 1, Examination 2, . . . in FIG. The operation device in Fig. 21 is arranged in a position separated from the top row and the bottom five rows. In the top row of the operation device, the instruction buttons for proceeding are arranged in the same order as on the screen, from left to right, and among the bottom five rows, Examination 1, Examination 2, ... are assigned in that order from left to right in the top row. In this way, the operation device assigns the examination buttons shown in area A23 in Fig. 11 to the numeric keypad, realizing a configuration in which the user can instruct examinations.
[0154] 5, the inspection device 200 has been described as having two combinations of control devices and device groups, namely, the first PC 210 and the first device group 230, and the second PC 270 and the second device group 250, but the inspection device may have three or more combinations, or may have only one combination. As an example, the inspection device may have the configuration examples of the inspection devices 200A to 200C shown in FIG. 22. The inspection device 200A including a set of a control device and a device group can achieve the effects of the inspection system 20 when inspecting a plurality of different inspection targets using the first device group 230.
[0155] Moreover, the inspection devices 200B and 200C, each having a plurality of device groups in one control device, are configuration examples in which the first PC 210 is connected to a plurality of different device groups. The inspection devices 200B and 200C can be configured to send commands to each device via an interface using a relay device (e.g., GP-IB). As in the configuration examples of FIG. 7 or FIG. 16, the inspection system 20 and the device group are designed to target the control device via an interface using GP-IB. The inspection devices 200B and 200C can set unique GP-IB addresses on the device side, and can send commands from the inspection system 20 by configuring the set addresses so that they do not overlap on the GP-IB interface.
[0156] Modification 3 of embodiment 2 On the examination screen, the area A242 may be configured to allow the results of different examinations to be referred to, for example, by tabs. A plurality of tabs may be associated with different examination results, and a function of switching the display of examination results may be provided, in which different examination results are displayed on the screen by selecting (clicking) a tab.
[0157] Variation 4 of embodiment 2 In the test system 20 of the second embodiment, the area A24 indicates non-generic device-specific information, for example, the status of a software module for performing a device-specific test. Displaying device-specific information requires complex processing and control, so it is preferable to modularize software (application) separate from the inspection system 20 for such complex processing and control, and to provide the inspection system 20 with a function for incorporating the UI of the modularized software. It is preferable for the inspection system 20 to incorporate the incorporated function into the processing (inspection sequence) of the general-purpose part, call it, and return it when it is completed. In this way, it is possible to avoid complicating the general-purpose parts of the inspection system 20, while making it possible to execute complex inspection procedures and visualize complex states of jigs and inspection objects.
[0158] For example, by modularizing the process of generating the screen of area A242, the process of generating individual screens can be separated. Also, the process of displaying real-time information in area A242 may be modularized. Inspection system 20 (for example, function 23 for sequentially executing a plurality of inspection items) may be configured to pass information acquired from the inspection board to modularized software, and the modularized software may display the real-time information.
[0159] In addition, the inspection system 20 may be configured to display the execution status of multiple inspection items in real-time information in the area A242 so that the execution status can be checked. Furthermore, the inspection system 20 may be configured to simultaneously display, for example, a number of measurement states of the machine (object to be inspected) within the area A242, allowing the states to be checked in real time at any time.
[0160] In each of the following embodiments, a form in which further functions are added to the inspection system 20 of the above-described second embodiment will be described.
[0161] Embodiment 3. The inspection system 20 may have a function to detect, for example, subtle changes in the defect rate during production and output a warning. The function for detecting subtle changes in the defect rate and outputting a warning may, for example, perform the above-mentioned detection by expanding the variation. For the expansion of the variation, for example, the standard deviation, the absolute value of the deviation, or the sum of squares, cubes, or fourth powers of the deviation may be used.
[0162] Embodiment 4. The inspection system 20 may have a function to visualize management indicators (e.g., management indicators such as production process capacity) based on individual aircraft data (data on the item to be inspected, e.g., data on inspection boards such as SD boards, SC boards, etc.) of adjustment inspection items (one example of multiple inspection items). The function for visualizing control indicators based on individual aircraft data for adjustment and inspection items should be equipped with a function for calculating on demand each time individual aircraft data for the aforementioned adjustment and inspection items is obtained, in order to perform source management in real time. The inspection system 20 may record the data of the adjustment inspection items output from the inspection jig as the machine data, and may also record the data of the machine to be inspected (for example, the main body information in the area A241).
[0163] Moreover, the inspection system 20 of this embodiment preferably has the following functions. 1-1. The inspection system 20, for example, records data on adjustment inspection items required for an OK / NG judgment output from the inspection jig as aircraft data in association with the OK / NG judgment result, but it is preferable not to measure the characteristics of the aircraft over its entire area and not to record data over the entire area as aircraft data. In this way, it is possible to calculate the control index while significantly shortening the inspection time. For example, the output value from an external measuring device may be varied to measure and record the inherent value of the machine, but this would take a very long time to inspect and would not be worth the productivity. It is better to configure it so that the output value required for the OK / NG judgment is output. For example, the receiving system can output specification values from an external device and record them as data on adjustment inspection items required to determine whether the aircraft can accept them as OK or NG.
[0164] 1-1-1. The inspection system 20 may, for example, be configured as described in 1-1 above in principle, and may vary the local frequency and record multiple measurement results within a variable range as aircraft data.
[0165] 1-2. It is preferable that the inspection system 20 has a means for switching between mass production mode and pre-mass production mode on the screen, for example. Inspection system 20 may have different inspection definition files corresponding to the mass production mode and the pre-production mode on the screen, for example, and the read-in file may be changed. For example, the inspection definition files in different folders may be referenced for the mass production mode and the pre-production mode. For example, when displaying the file list of Fig. 9, the files for the mass production mode and the files for the pre-production mode may be displayed together in different screen areas. For example, the different screen areas may be switched using tabs. Alternatively, a screen for selecting the mass production mode or the pre-production mode may be displayed before displaying the screen of Fig. 9, and the files for the mode selected by the user may be read from the folder for that mode, and the list of files for the selected mode may be displayed in Fig. 9. For example, in mass production mode, the inspection system 20 performs the operations described above in 1-1. or 1-1-1., but in pre-production mode, it is preferable to perform operations such as measuring the characteristics of the aircraft over the entire area and recording the data over the entire area as aircraft data.
[0166] Embodiment 5. The inspection system 20 may have the following functions with regard to the control index. It is generally assumed that quality control activities use the Seven QC Tools or the New Seven QC Tools. In particular, for transitional (during production) management, the control chart (JIS Z 9020-2:2016<https: / / jis.eomec.com / jisz902022016#gsc.tab=0> Control Charts - Part 2: Shewhart Control Chart - JIS standard (eomec.com) is used. The following two articles can be found on the Internet as reference material: <https: / / backlog.com / ja / blog / what-is-a-control-chart / > What is a control chart? A comprehensive explanation of its relationship with the seven QC tools, its structure and types | Backlog Blog <https: / / backlog.com / ja / blog / what-is-a-control-chart / #8%E3%81%A4%E3%81%AE%E7%95%B0%E5%B8%B8%E5%88%A4%E5%AE%9A%E3%83%AB%E3%83%BC%E3%83%AB> 8 rules for determining abnormalities Since the Xs control chart uses the standard deviation, the idea of expanding the variation in the third embodiment, for example, by using the standard deviation, the absolute value of the deviation, the sum of squares of the deviation, the sum of cubes of the deviation, or the sum of fourth powers of the deviation, can also be applied to this chart.
[0167] However, in the Xr Control Chart, the center line of the X graph is the overall average value, but I am not sure whether the overall average value is suitable as a standard. Furthermore, it is not suitable for visually capturing long-term changes. The graph of X and the graph of r are separate, which makes it difficult to understand intuitively.
[0168] So, I propose the following idea: Applying Bollinger Bands, which are used for investment decision-making, to quality control. The following articles can be found on the Internet as reference material: <https: / / www.oanda.jp / lab-education / beginners / technical_analysis / bolinger-band / > What are Bollinger Bands? How to read them, use them, and set them up | OANDAFX / CFD Lab-education In Bollinger Bands, the vertical axis is price and the horizontal axis is time (which can be switched to hourly, daily, weekly, monthly, etc.), with the vertical axis being the numerical value of the item under quality control (for example, reception sensitivity). The horizontal axis can be time, but it is better to use lot charts. Alternatively, if the factory does not sell lots on a daily basis, you can keep the chart on a daily basis and separate the lot for that day into multiple candlesticks.
[0169] It is a good idea to add horizontal lines of a different color to the candlesticks to indicate the average or median value. It is good to represent the candlesticks themselves as horizontal bars divided by frequency distribution (frequency distribution graph, histogram), as this allows you to see the distribution within the candlestick. It is recommended that the center line be a simple moving average line, but in order to detect subtle changes in the defect rate during production faster than humans can, it is recommended to display a weighted moving average line, exponentially smoothed moving average line, etc. instead of or in addition to the simple moving average line. The following articles can be found on the Internet as reference material: <https: / / www.sevendata.co.jp / shihyou / technical / heikatsuidou.html> How to read and use exponential moving averages | Technical analysis indicators | How to read and use indicators | Investment know-how | Stock expert (sevendata.co.jp)
[0170] As with Bollinger Bands, it is a good idea to draw lines of ±σ, ±2σ, and ±3σ. At this time, it is preferable to switch to the fourth root, for example, by using the sum of the fourth powers of the deviations in order to expand the variation in the third embodiment. In this way, for example, the following points become easier to understand: When lines such as ±3σ are squeezing (contracting), it is visually clear that the variation is converging and moving in a positive direction. When the lines are expanded, such as ±3σ, it is visually clear that there is a high possibility that some kind of abnormality is occurring. When the price band walks against a line such as ±3σ, it is visually clear that there is a high possibility that some abnormal trend is expanding. If the candlestick is large, it is visually obvious that something unusual may have occurred during the day.
[0171] Furthermore, to see the overall distribution within the displayed graph range, it is a good idea to plot the number of transactions per day along the X-axis as a bar graph. It is also a good idea to plot a histogram of each sensitivity range along the Y-axis, similar to the volume by price range on the investment graph. The following articles can be found on the Internet as reference material: <https: / / aibashiro.jp / contents / yg00045 / > What is price range volume? Easy to understand explanation for stock beginners (aibashiro.jp)
[0172] Embodiment 6. The inspection system 20 may be provided with the functions described below when recording the inspection results on a predetermined recording medium. 1. The inspection system 20 may have a function of recording the inspection results (e.g., the sensitivity characteristics for each measured frequency) in an RFID in the machine, or in a non-volatile memory such as a flash memory, or in a medium (e.g., an SD card) attached to the machine. Here, in this embodiment, the machine is, for example, an object to be inspected (RD board, SC board, etc.), or a device equipped with an object to be inspected. The aircraft or a device capable of communicating with the aircraft should have a function to display the contents of the communication. The communication device may be a PC or a portable communication device, and the communication method may be either wired or wireless. The display may be configured so that only a serviceman or other person who knows the secret code or operation can display it, but the user cannot.
[0173] This allows customer service personnel to check the inspection results at the customer service site without having to trace the system records at the factory using serial numbers, etc. This is useful for identifying the causes of breakdowns, etc. Because the RFID tag is located inside the aircraft, unlike a situation where an RFID tag is simply attached to the packaging, it will not be lost together with the aircraft that is believed to have failed, and the inspection data can be reliably obtained at the service site.
[0174] 1-1. The storage unit in 1 above may be mounted on each board in the aircraft, and the inspection data for each board may be stored on each board. The inspection system 20 may have a function of writing the inspection results to the storage unit of each board. 1-2. The above item 1 should be the packaging material and the unit itself that places the unit in a position within the packaging that is readable from the outside when the unit is in its packaged state (packaged state at the time of shipment from the factory). 1-3. In the above item 1, it is advisable to make it possible to read inventory management information from outside. In particular, by implementing 1-1, inventory management at factories and service sites can be made easier. In addition, by following the method described in 1-2, inventory management at the product distribution and sales sites can be facilitated. 1-4. It would be a good idea to provide the aircraft with a post-shipment operating mode function that records, in a readable manner, operation logs such as supply voltage, current, and temperature in addition to the above 1.
[0175] 2. Information regarding the inspection may be displayed on a display unit such as an LCD (Liquid Crystal Display) or LED (Light Emitting Diode) on the aircraft itself, and the information may be read by the inspection system using a camera or the like and reflected in the inspection results. It is not productive to collect all the received data from each individual aircraft and calculate process capacity. However, if any output level from the measuring device (SG) and the receiving RSSI level of each machine can be output to the fixture system from each machine, it can be instantly reflected in the process capability, and production can be brought closer to ideal (it can also be displayed on the machine's LCD and read by a camera).
[0176] For example, if the current RD adjustment inspection tact time is 60 seconds, it would be better if it could be made faster than that. It is also a good idea to do the following: The TEST mode should be able to output the RSSI level during reception from the aircraft in real time. Currently, people check by listening to the sound and looking at the display, so this will be much faster. It may take time to sweep and check all levels, so if you obtain the RSSI levels of each aircraft for the SG output levels of design specifications Lev1, 3, and 5 (current levels are also checked manually), the remaining levels can be calculated (for example, just Lev1 and 5 will suffice). In fact, currently, except for Lev1, Lev3 is written and the remaining Levs are determined by the aircraft software (for example, the "arbitrary output level" may be a stepped point rather than a continuous one). Even if the measurements are continuous, it is best to measure so that each unit responds quickly. For example, if the "output level" is swept, and the RD (RD board) has poor tracking ability, waiting times will occur. Also, even if the RD responds instantly, if the sweep takes a long time, productivity will decrease. Similarly, if the "frequency" is swept, productivity will decrease even more.
[0177] If the inspection time is long enough that it does not deteriorate productivity, the measurement should be performed continuously, but if the measurement takes so long that it deteriorates productivity, the signal should be applied in stages. In particular, for inspection items that are discovered after the board is completed and that cannot be obtained from the TP using a contact probe in the first place, the inspection software on the aircraft may be updated to display the results of that inspection item on the LCD.
[0178] 2-1. The display can be an LCD. It can simply be green for OK and red for NG. 2-2. It is advisable that the display unit should show both machine-readable information and human-readable information showing the test results. As easily machine-readable information showing the test results, a QR code (registered trademark) containing the test results within the device may be displayed.
[0179] 3. Alternatively, it would be a good idea to provide a function for the aircraft being inspected to perform self-inspection in addition to the inspection on the inspection system side (PC side). 4. In particular, it would be good to have a function that allows the inspection software to be uploaded from the inspection system to the aircraft before inspection.
[0180] 5. If there are multiple test items, it is a good idea to display the combined results of multiple tests on the aircraft's display. It is advisable to photograph this with a camera or other device in this inspection system and obtain the data electrically and without contact. 6. When the power supply to the machine is configured to be interrupted between inspection items, it is advisable to have a function to display the inspection results on an LCD or the like in the process before the power supply is interrupted and to read them with the inspection system (for example, because power is supplied to the machine from a jig equipped with a contact probe and the jig is replaced between inspection items). When the power supply to the machine is interrupted between inspection items, the inspection results in the machine are stored in a memory that does not disappear even when the power is turned off, and when the power is turned on, the final inspection results are displayed based on the contents of this memory and the subsequent inspection results.
[0181] 7. When a process is divided, for example, it is a good idea to have a function in the second process that allows the inspection results of the previous process system to be read and displayed (on the initial read file selection screen, etc.). By doing this, for example, it is easy to reject any accidentally mixed-in items that fail inspection at the start of the second process. Alternatively, it would be a good idea to have a function in the second process that displays the need for adjustments based on the results of the previous process.
[0182] Embodiment 7. The inspection system 20 may have the following functions for recording, displaying, etc., of the inspection results. 1. The equipment group may, for example, output radio waves of a specific frequency within the designed receiving frequency range of the radar from a fixture, and output the inspection results to this system (inspection system 20) so as to enable identification of the position within the sweep range where the radar received the radio waves of that frequency. For example, when a frequency in the middle of the designed frequency sweep range is emitted from the jig, the position where the radar receives it (in this embodiment, the position where the sweep is stopped) may be on the higher frequency side. In this way, the degree of variation can be verified through multiple inspections. It can also be used to predict variations in part performance and tendencies toward defects.
[0183] 1-1. The inspection system 20 may have a function for displaying the inspection results recorded in 1 above for a plurality of inspection targets in a comparable manner, for example.
[0184] 2. The inspection system 20 should have a function to acquire the overall output results for each module, for example, and also acquire the output results for each circuit block within the module, such as the output of the first stage amplifier and the output of the second stage amplifier, and record them in association with each other.
[0185] 3. The actual device (for example, a radar detector equipped with an RD board or SC board) should have a function to record the contents output after installation in the vehicle (at the customer's site) (after the power is first turned on after leaving the factory), and it is recommended that this recording area be left empty (with nothing recorded) when the device is shipped from the factory.
[0186] 3-1. The function of recording the content output after installation may include, for example, a function of recording information capable of identifying the content of the audio output in association with information capable of identifying the date and time of the output. This helps to identify situations where a customer may assume that an audio output not present in the radar detector (for example, an "error" sound) is coming from another device (for example, an ETC).
[0187] Embodiment 8. In this embodiment, a configuration or function that is effective when the examiner is an unskilled person will be described. 1. The inspection system 20 may have a function to not display area A24 on the inspection screen, for example. 2. The inspection system 20 may have a function to display the inspection result, for example, "OK" or "NG" in large letters on the inspection screen. 3. The inspection system 20 may be configured so that it is possible to specify, for example, in the inspection definition file, whether or not to display the area A24. 3-1. It would be good to be able to specify whether or not each button should display a specific area (eg, area A24) such as the right area in the test definition file.
[0188] EMBODIMENT 9. The inspection system 20 may have the following functions regarding display of the inspection results. 1. The inspection system 20 may, for example, display different colors of buttons depending on whether they require human operation or are executed automatically without human operation (e.g., orange for those operated by a human and blue for those executed automatically). 2. The inspection system 20 may, for example, provide a display between buttons indicating the flow between inspection processes (for example, displaying an arrow "⇒" between "Inspection 1" and "Inspection 2" shown in area A23 of FIG. 11).
[0189] 3. The inspection system 20 may, for example, be able to manually skip a specific inspection step without executing any inspection. For example, if the buttons indicating each inspection shown in area A23 of FIG. 11 are displayed in light blue, pressing and holding the light blue button for "Inspection 5" may turn the button gray, and "Inspection 5" may be skipped and executed. Also, for example, the arrow "⇒" in 2 above may be displayed as Inspection 4 ⇒ Inspection 6, bypassing Inspection 5. 4. The inspection system 20 may have a function for storing, for example, the steps skipped in 3 above in association with each other. 5. The inspection system 20 may have a function for recording, for example, items that exceed a specified value for a specified period of time in area A24 of the inspection screen. 6. It is recommended that the default values for each of the items listed above in 5 be written in the button generation file (inspection definition file).
[0190] The above-mentioned embodiments 1 to 9 may be arbitrarily combined. For example, a first substrate may be inspected in embodiment 1, and a second substrate may be inspected in embodiment 2 to manufacture a device having the first substrate and the second substrate. Alternatively, a selection screen for selecting which embodiment to execute may be displayed, the user may select, and the selected embodiment may be executed.
[0191] The scope of the present invention is not limited to the configurations expressly described in the specification, but includes combinations of various aspects of the present invention disclosed herein. The configurations of the present invention for which a patent is sought are specified in the appended claims, but it is the intention of the present inventors to include in the claims any configurations disclosed in this specification that are not currently specified in the claims.
[0192] The present invention is not limited to the configuration described in the above-mentioned embodiment. The components of each of the above-mentioned embodiments and modifications may be arbitrarily selected and combined. Any components of each of the embodiments and modifications may be arbitrarily combined with any components described in the means for solving the invention or any components that embody any components described in the means for solving the invention. We intend to acquire rights to these as well through amendments to this application or divisional applications, etc. Even if there is a description such as "in the case of..." or "when...", this is not intended to describe a configuration that is limited to that case or time. We also disclose configurations that are not in these cases or times, and we intend to acquire rights to them. Furthermore, the parts described in order are not limited to this order. We also disclose configurations in which some parts are deleted or the order is changed, and we intend to acquire rights to them.
[0193] In addition, we intend to obtain rights to the overall design or partial design by filing a conversion application to a design application. The drawings depict the entire device in solid lines, but they include not only the overall design but also partial designs claimed for some parts of the device. For example, it is a drawing that includes some parts of the device as partial designs, regardless of the parts, as well as a drawing that includes some parts of the device as partial designs. A part of the device may be a part of the device, or it may be a part of that part. We intend to obtain rights to not only the overall design, but also partial designs in which any part of the solid line parts of the drawings is drawn as a dashed line part.
[0194] The present inspection system allows the inspection process to be defined in a file, making it easy to change the process and contributing to the SDGs (Sustainable Development Goals) as follows: Goal 9: Build industry, innovation and infrastructure Defining processes in a file makes it easier to incorporate innovations, promoting sustainability and innovation in the industry. Goal 8: Decent work and economic growth Making it easier to change processes leads to increased productivity and the creation of new employment opportunities. It also makes it easier for workers to understand processes, creating a more comfortable working environment. Goal 12: Responsible Consumption and Production Using definition files helps to reduce resource consumption and waste, which contributes to sustainable consumption and production patterns. Goal 13: Climate action Easier process changes can lead to greater efficiency and environmental friendliness, potentially resulting in reduced greenhouse gas emissions, which contributes to tackling climate change. Goal 17: Partnerships for the goals Sharing process definition files and promoting international collaboration and cooperation will facilitate technology transfer and knowledge sharing, building stronger partnerships to achieve the Sustainable Development Goals. Defining the inspection process on file not only contributes to the SDGs, but also contributes to the efficiency and sustainability of the entire organization. Adopting such an approach will accelerate efforts toward sustainable development. [Explanation of symbols]
[0195] 10, 20 Inspection system 11. Personal computer (PC) 15, 35 Adjustment base 21 Function to generate and display inspection screens 23 Function to execute multiple test items sequentially 151-157, 353 Horn 158, 353 PCB installation board 200, 200A~200C Inspection equipment 210 First PC 211 Display section 213 Operation section 230 First equipment group 250 Second equipment group 270 Second PC
Claims
1. 1. An inspection system for inspecting at least one inspection object, comprising: An inspection system that sequentially performs a plurality of inspection items on the object to be inspected.
2. A configuration is provided in which a plurality of devices used for the plurality of inspection items are arranged, and each device starts operating by moving the object to be inspected to a position opposite each device.
2. The inspection system according to claim 1 .
3. the object to be inspected is a member having a substrate for receiving a wireless signal, Each device outputs a different radio signal.
3. The inspection system according to claim 2.
4. The at least one test object is a plurality of objects, The device includes a function for identifying the object to be inspected and the plurality of inspection items, a function for generating and displaying an inspection screen showing the object to be inspected and the plurality of inspection items based on an inspection definition file corresponding to one of a plurality of inspection definition files corresponding to each inspection object that have been created in advance, and a function for sequentially executing the plurality of inspection items displayed on the inspection screen.
2. The inspection system according to claim 1 .
5. The plurality of test definition files include, for each of the test objects, the plurality of test items and information specifying an order in which the plurality of test items are to be executed; The function of generating and displaying the inspection screen displays information in which the plurality of inspection items contained in the one inspection definition file are arranged in the order on the inspection screen.
5. The inspection system according to claim 4.
6. The function of generating and displaying the inspection screen includes displaying a plurality of operation buttons on the inspection screen for receiving instructions regarding the execution of the plurality of inspection items; The function of sequentially executing the plurality of test items executes the plurality of test items based on pressing of the plurality of operation buttons.
6. The inspection system according to claim 4 or 5.
7. the plurality of operation buttons include an operation button for executing all of the plurality of test items and an operation button for executing each of the plurality of test items individually, The function of sequentially executing the plurality of test items executes at least one of the plurality of test items based on a pressed operation button.
7. The inspection system according to claim 6.
8. the plurality of operation buttons includes a progress button for proceeding to the next execution of the plurality of test items, The plurality of test definition files each include, for the plurality of test items, a test type indicating either an adjustment test that requires adjustment to the test result or a confirmation test that confirms the test result and proceeds to the next test, and a specified value to be compared with the test result of the confirmation test; The function of sequentially executing the plurality of inspection items, in the adjustment inspection, displays the inspection result on the inspection screen and waits until the proceed button is pressed, and in the confirmation inspection, judges the inspection result of the confirmation inspection using the specified value, proceeds to the next inspection item if the result is within the specified value, and displays an error if the result is outside the specified value.
7. The inspection system according to claim 6.
9. The function of generating and displaying the inspection screen displays the inspection item being executed on the inspection screen.
6. The inspection system according to claim 4 or 5.
10. The inspection screen displays an inspection result obtained by executing at least one inspection item.
6. The inspection system according to claim 4 or 5.
11. The function of sequentially executing a plurality of test items includes storing test results of at least one of the test items.
6. The inspection system according to claim 4 or 5.
12. The test definition file corresponding to one test object is selected by the user.
6. The inspection system according to claim 4 or 5.
13. The inspection screen has an area showing an inspection item being performed, an area showing the inspection status of the inspection item being performed while the inspection items are being performed, and an area showing the inspection results of the inspection items in sequence.
6. The inspection system according to claim 4 or 5.
14. the test definition file has information for forming a display area for displaying the test status of each test item in the area showing the test status; The function of generating and displaying the inspection screen generates an area showing the inspection status using information forming the display area.
14. The inspection system of claim 13.
15. Further, the apparatus further includes a function of calculating a defect rate using the inspection results stored up to a predetermined timing when inspecting a plurality of objects to be inspected for each inspection target, detecting a change in the defect rate, and notifying the detected change in the defect rate. The inspection system of claim 11 .
16. Further, when the inspection results are acquired when inspecting a plurality of objects to be inspected in each inspection target, a function of calculating a management index using the inspection results is provided. The inspection system of claim 11 .
17. The inspection definition file is created for one inspection object in at least two types of files, one for mass production mode and one for pre-production mode.
6. The inspection system according to claim 4 or 5.
18. Further having a function of expressing the value calculated using the test result using Bollinger bands.
16. The inspection system of claim 15.
19. The inspection results are recorded in a memory means of the object to be inspected.
12. The inspection system of claim 11.
20. The inspection result recorded in the storage means is configured to be displayable in a device equipped with the object to be inspected.
20. The inspection system of claim 19.
21. the test definition file has a test item for instructing setting of test conditions and storing the test results in association with the test conditions for at least one of the plurality of test items, The function of sequentially executing the plurality of test items is to store the test results executed according to the instructions and the conditions at the time of the test in association with the conditions. The inspection system of claim 11 .
22. The area showing the inspection status can be selected to be displayed or not displayed.
14. The inspection system of claim 13.
23. the inspection screen has an area for selecting an inspection item to be performed from among the plurality of inspection items, the region for selecting the test item to be performed is configured to prompt the user to select a test item to be performed from among the plurality of test items; The function of sequentially executing the plurality of test items is to sequentially execute the test items selected in the area for selecting the test items to be executed when an operation button for executing all of the plurality of test items is pressed.
8. The inspection system according to claim 7.
24. A program for causing a computer to execute the functions of the inspection system according to claim 4 or 5.
Citation Information
Patent Citations
JP05‐275934A
