Configurable universal modular test system

Abstract

The invention relates to a configurable general modular test system, which comprises a master module connected with a user side and a slave module connected with the master module, the master module and the slave module are general test modules, the master module is provided with a timer and can control external equipment of the master module and the slave module, so that the control logic is clear, and the test efficiency is improved. And the synchronization among the modules can be realized through the unified control of the main module, hardware resources are fully utilized to efficiently work, the same type of actions can be managed consistently, problems can be conveniently searched, and repeated problems are reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of product testing, and in particular to the technical field of a configurable universal modular testing system. Background Art

[0002] With the advancement of production technology, the testing requirements for factory products are also increasing. Taking the testing of electronic products as an example, it is usually necessary to conduct multiple tests such as electrical performance testing, functional testing, environmental adaptability testing, durability testing, safety performance testing, etc.

[0003] These tests are completed by external devices other than the product, and the test items and standards vary due to differences in customer needs. Considering rigor, the current test technology is to design a special fixture for each product according to the needs, and complete multiple tests as described above on the fixture, which can achieve high-standard testing with efficiency, rigor and consistency. To this end, each special fixture will be customized with a different control motherboard, which is responsible for communicating and controlling various external devices used for testing (such as sensors, power supplies, signal generators, etc.).

[0004] However, the current testing technology has at least the following problems.

[0005] First, the control motherboard and control program are inefficient: each fixture has to be customized, and this repetitive work leads to low work efficiency, uneven technical levels, complex management, and high maintenance costs.

[0006] Secondly, it is difficult to avoid new problems in the early stage of fixture debugging. If the main board has been installed on a fixture with complex wiring, it is very difficult to update the firmware of the main and auxiliary modules at this time.

[0007] In summary, existing test fixtures and control systems have obvious limitations when facing diverse and changing test requirements. Therefore, a more flexible, efficient, and easy-to-maintain test solution is needed to improve test efficiency and maintenance convenience and meet the needs of different customers and test projects. Summary of the invention

[0008] The present invention provides a configurable universal modular test system, which aims to improve test efficiency and maintenance convenience through universal modular design and coordination of master and slave modules, and meet the needs of different customers and test projects.

[0009] To achieve the above object, the present invention adopts the following technical solutions:

[0010] A configurable universal modular test system, comprising a main module connected to a user end and a slave module connected to the main module, wherein the main module and the slave module are universal test modules;

[0011] The main module includes a main serial port 1 connected to the user end, a main serial port 2 connected to the slave module, and a device port connected to an external device;

[0012] The slave module includes a slave serial port 1 connected to the master module and a device port connected to an external device;

[0013] The master module is provided with a timer and can control external devices of the master module and the slave modules.

[0014] Compared with the prior art, the universal modular test system of this case makes the control logic clear through universal modularization, and the master module can achieve synchronization between modules through unified control, fully utilize hardware resources to work efficiently, and can also achieve consistent management of actions of the same type, making it easier to find problems and reduce duplication of problems. The modular design can also retain control independence, that is, the unitization of actions, which not only facilitates independent testing of actions, but also allows the unitized actions to be arbitrarily arranged into combination tests of combined actions.

[0015] In some embodiments, the master module and / or slave module can be used independently or online, and the software programming of the master module and the slave module control is integrated to selectively compile and download codes to different modules through macro definitions.

[0016] In this way, the required functions can be expanded or reduced, which greatly shortens the product development cycle, ensures the stability of the product, and realizes the rapid replacement of test fixtures and convenient firmware updates. When the communication control logic changes, only the main module firmware needs to be updated, and only the main module firmware needs to be updated to meet customer needs, and no changes are required in the slave module. At the same time, when updating, only the main serial port 1 of the main module needs to be used to complete the convenient source program modification.

[0017] It also includes the main process of slave module workflow, slave module status confirmation process, main module and slave module work allocation process, inspection process, startup induction inspection process, slave module induction inspection process, and action execution process. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 It is a schematic diagram of a configurable universal modular test system in this case;

[0019] Figure 2 It is from the module workflow diagram;

[0020] Figure 3 It is the flow chart of module status confirmation;

[0021] Figure 4 It is a flow chart of work distribution between master module and slave module;

[0022] Figure 5 is to check the flow chart;

[0023] Figure 6 It is the start-up induction check flow chart;

[0024] Figure 7 It is the flow chart of the induction check from the module;

[0025] Figure 8 It is an action execution flow chart. DETAILED DESCRIPTION

[0026] The features of the present invention and other related features are further described in detail below through embodiments to facilitate understanding by those skilled in the art:

[0027] Please refer to Figure 1 The present invention provides a configurable universal modular test system, including a main module connected to a user terminal, wherein the main module and the slave module are universal test modules. The user terminal is an interface for users to interact with the main module, responsible for sending commands and receiving feedback information, and can be a PC.

[0028] The master module is responsible for overall control and coordination, managing the tasks of multiple slave modules, receiving commands from the user end and sending control instructions. The master module and slave modules use PCB boards as carriers to match fixtures and external devices. Both the master module and slave modules are modularly designed to make the control logic clear and the interference between them small. The master module can achieve synchronization between modules under unified control, making full use of hardware resources and working efficiently.

[0029] Specifically, the master module includes a master serial port 1 connected to the user end, a master serial port 2 connected to the slave module, and a device port connected to an external device. The slave module includes a slave serial port 1 connected to the master module and a device port connected to an external device. The device port is generally an IC universal port and an I2C interface. The master module is provided with a timer that can be used as a system clock, which is used when the master module and the slave module control the external device. The IC universal port is divided into two types: input port and output port. The input port can correspond to sensors, touch buttons, etc., and the output port can correspond to motors, relays and other commonly used test equipment in the industry, which will not be described in detail.

[0030] In addition, I2C communication is used in both master and slave modules to control external devices through two lines of clock signal (SCL) and data signal (SDA), such as reading and writing EEPROM (electrically erasable programmable read-only memory).

[0031] That is, the same type of actions can be managed consistently, making it easier to find problems and reduce duplication. The modular design can also retain control independence, that is, action unitization, which not only facilitates independent testing of actions, but also allows unitized actions to be arbitrarily arranged into combination tests.

[0032] In some embodiments, the master module and / or slave module can be used independently or online, and the software programming of the master module and the slave module control is integrated, and the code is selectively compiled and downloaded to different modules through macro definition. That is, the timer can also be designed in the slave module, and it can be exchanged with each other according to the requirements of the actual test conditions. It is also possible to test only the master module and the slave module separately for projects with simple test requirements or repeated tests.

[0033] At the same time, the required functions can be expanded or reduced, which greatly shortens the product development cycle, ensures the stability of the product, and realizes the rapid replacement of test fixtures and convenient firmware updates. When the communication control logic changes, only the main module firmware needs to be updated, and only the main module firmware needs to be updated to meet customer needs, and no changes are required from the module. At the same time, when updating, only the main serial port 1 of the main module needs to be used to complete the convenient source program modification.

[0034] The following is a detailed description of the system in this case through its workflow. Figures 2 to 8 The main work process includes the slave module workflow S100, the slave module status confirmation process S200, the main module and slave module work allocation process S300, the inspection process S400, the start-up induction inspection process S500, the slave module induction inspection process S600, and the action execution process S700.

[0035] Specifically, please refer to Figure 2 The slave module workflow S100 mainly receives the instruction of the master module and then reads or sets the port. The port here refers to the chip universal port, which is divided into input port and output port. The concept of universal port will be used in the subsequent description.

[0036] First, the port is initialized, and step S110 determines whether data is received successfully from serial port 1;

[0037] If yes, then execute step S120 to determine whether it is a control instruction of the output port, otherwise return to execute step S110;

[0038] If step S120 determines that it is an output port control instruction, step S121 is executed to read the port status, and then the instruction returns. If step S120 determines that it is not an output port control instruction, step S130 is executed to determine whether it is an input port control instruction.

[0039] If step S130 determines that it is an input port control instruction, step S131 is executed to set the port status, and then the instruction returns. If step S130 determines that it is not an input port control instruction, step S140 is executed to determine whether it is other instructions, where other instructions can be reset instructions, interrupt instructions, etc.

[0040] If it is determined to be other instructions in step S140, the instruction returns to execute step S300, otherwise it returns to continue executing step S110. As described above, the slave module makes judgment information according to the received instruction, and then sends the judgment information to the master serial port 2 of the master module through the slave serial port 1 of the slave module.

[0041] Please refer to Figure 3 ,The module status confirmation process S200 is completed in the main module, port initialization, and receiving user end data. For example, when the user end is a PC device, a command is sent to the main serial port 1 of the main module through the PC serial port. If the main module is triggered by a key, it represents that a certain command is generated.

[0042] Then, step S210 is executed to determine whether the main serial port 2 receives data successfully. If yes, step S220 is executed; otherwise, step S300 is executed.

[0043] Step S220 determines whether the module input port check is completed, if so, execute step S221 to set the input port flag and record the output status, then execute step S300, otherwise execute step S230;

[0044] Step S230 determines whether the module output port check is completed, if so, execute step S231 to set the output port flag and record the output status, then execute step S300, otherwise execute step S240;

[0045] Step S240 determines whether the slave module is idle, if so, execute step S241 to forward the master serial port 1 to the user end, otherwise execute step S300.

[0046] Please continue to refer to Figure 4 , the work allocation process S300 of the master module and the slave module is completed in the master module, and its process is as follows, connecting step S200;

[0047] Step S310 determines whether the primary serial port 1 receives data successfully, if yes, executes step S320, otherwise executes step S400;

[0048] Step S320 determines whether it is a command from the master serial port 2. If so, step S321 is executed, the master serial port 2 is forwarded to the slave module, and the slave module executes step S100. If not, step S330 is executed;

[0049] Step S330 determines whether it is a command from the main serial port 1. If so, step S331 is executed to set an action flag and record an action status, and then step S400 is executed. Otherwise, step S400 is executed.

[0050] For example, in a specific application example, the user, that is, the PC, needs to query the status of the current port of the slave module, and sends a slave module status query instruction to the main module, which then forwards it to the slave module. The slave module will determine and process whether there are other instructions in S140 in the S100 process, and then return the processing result to the main module, which then returns it to the user, that is, the PC.

[0051] Please refer to Figure 5 ,The inspection process S400 is mainly to check safety and induction, and its steps are as follows;

[0052] Step S410 determines whether the security port is triggered, if so, executes step S411 to start the action protection, then returns to execute step S200, otherwise, executes step S420;

[0053] Step S420 determines whether the action is idle, which includes the master module and the slave module. If it is determined to be idle, step S421 is executed to start the operation according to the action flag and register the sensing inspection record, otherwise step S500 is executed;

[0054] After step S421 starts the operation according to the action flag, if step S422 starts the sensing check class and S423 ignores the sensing check class, then step S500 is entered after execution. If step S424 is executed as the slave module sensing check class, step S425 is continued to be forwarded from the master serial port 2 to the slave module, and then step S500 is entered. The specific process can be to send the start action instruction to the slave module through the master serial port 2 and register the sensing check record.

[0055] Please refer to Figure 6 , starting the induction inspection process S500 includes:

[0056] Step S510 determines whether the output port mark is == completed. If so, step S511 is executed to start the induction check, which includes step S512 master module induction check, step S513 slave module induction check, and step S514 induction check ignore. Here, steps S512, S513, and S514 respectively represent the instructions for checking direct start, and do not represent the whole process. If step S510 determines that it is not, step S520 is executed. As described above, at step S400, the start action instruction is sent to the slave module, and the induction check record is registered. Then, at step S500, if it is determined that the output port mark is == completed, the slave module induction check process S600 will be executed at step S500;

[0057] Step S520 determines whether the output port flag == error, if so, then execute step S521 to determine whether the error count is ≥ 3, if so, then execute step S560 to set the state and record the action determination result, at this time, the error count is completed by the error counter. If step S521 is executed to determine whether the error count is ≥ 3, if it is determined to be otherwise, execute step S522 to set the action restart.

[0058] If step S520 determines whether the output port flag == error, if it is determined otherwise, step S530 is executed.

[0059] Step S530 determines whether the output port flag is == waiting, if so, step S531 is executed to determine whether it is timed out, if so, step S521 is executed, otherwise step S522 is executed. If step S530 determines whether the output port flag is == waiting, if not, step S540 is executed.

[0060] Step S540 determines whether the output port flag == jump, if so, executes step S560, otherwise, executes step S550;

[0061] Step S550, determine whether the output port flag == jump failure, if it is determined to be yes, execute step S560, otherwise execute step S522. That is, after the step S500 process is completed, a state will be set to record whether the action is error, completion, etc.

[0062] Please refer to Figure 7 , the slave module sensing check process S600 is completed in the slave module, including starting the sensing check from step S511 of the main process, and then executing step S513 of the slave module sensing check;

[0063] Step S610 determines whether the idle state has timed out, if so, executes step S620, otherwise returns to the main process;

[0064] Step S620 determines whether the input port flag is == error, if so, execute step S621 to set the input port flag == idle, continue to execute step S622 master serial port 2 to send instructions to the slave module, then return to the main process, otherwise execute step S630;

[0065] Step S630 determines whether the input port flag == completed, if so, the check ends and the state is set in step S560, otherwise, step S640 is executed;

[0066] Step S640 determines whether the input port flag == waiting, if so, executes step S650, otherwise executes step S660;

[0067] Step S650 determines whether the waiting count is greater than 10, if so, executes step S621, otherwise executes step S660;

[0068] Step S660 determines whether the debounce count is greater than 50. If so, the check ends and step S560 is executed to set the status. Otherwise, the main process is returned.

[0069] Please refer to Figure 8 , the action execution process S700 includes:

[0070] Step S710 determines whether a combined action is performed, if so, executes step S720, otherwise, executes step S730;

[0071] Step S720 determines whether the independent action is completed, if so, executes step S740, otherwise returns to step S200;

[0072] Step S740 determines whether the combined action is completed, if so, the operation ends, otherwise, step S741 is executed to prepare for the next action, and then returns to step S200;

[0073] Step S730 determines whether it is an independent action, if so, executes step S750, otherwise, executes back to step S200;

[0074] Step S750 determines whether the action is completed, if so, the operation ends, otherwise returns to step S200.

[0075] As mentioned above, this case protects a configurable universal modular testing system, and all technical solutions that are the same or similar to this case should be deemed to fall within the scope of protection of this case.

Claims

1. A configurable universal modular test system, characterized in that: It includes a main module connected to a user end and a slave module connected to the main module, wherein the main module and the slave module are universal test modules; The main module includes a main serial port 1 connected to the user end, a main serial port 2 connected to the slave module, and a device port connected to an external device; The slave module includes a slave serial port 1 connected to the master module and a device port connected to an external device; The master module is provided with a timer and can control external devices of the master module and the slave modules.

2. A configurable universal modular test system as claimed in claim 1, characterized in that: The master module and / or slave module can be used independently or online, and the software programming of the master module and the slave module control is integrated, and the code is selectively compiled and downloaded to different modules through macro definition.

3. A configurable universal modular test system as claimed in claim 1, characterized in that: It also includes a main process of executing a slave module workflow S100, a slave module status confirmation process S200, a master module and slave module work allocation process S300, an inspection process S400, a start-up induction inspection process S500, a slave module induction inspection process S600, and an action execution process S700.

4. A configurable universal modular test system as claimed in claim 3, characterized in that: The slave module workflow S100 includes: The port is initialized, and then step S110 is executed; Step S110 determines whether data is received successfully from the serial port, if yes, executes step S120, otherwise returns to execute step S110; Step S120 determines whether to output the port control instruction. If so, step S121 is executed to read the port status, and then the instruction is executed and returned. Otherwise, step S130 is executed. Step S130 determines whether a port control instruction is input, if so, execute step S131 to set the port status, then execute the instruction and return to execute step S200, otherwise, execute step S140; Step S140 determines whether it is another instruction. If so, the instruction is executed and the execution returns. Otherwise, the execution returns to step S110.

5. A configurable universal modular test system as claimed in claim 4, characterized in that: The slave module status confirmation process S200 includes: The port is initialized, and then the user terminal data is received and step S210 is executed; Step S210 determines whether the primary serial port 2 receives data successfully, if yes, executes step S220, otherwise executes step S300; Step S220 determines whether the module input port check is completed, if so, execute step S221 to set the input port flag, and then execute step S300, otherwise execute step S230; Step S230 determines whether the module output port check is completed, if so, execute step S231 to set the output port flag, and then execute step S300, otherwise execute step S240; Step S240 determines whether the action is idle, if so, execute step S241 to forward the main serial port 1 to the user end, and then execute step S300, otherwise execute step S300.

6. A configurable universal modular test system as claimed in claim 5, characterized in that: The master module and slave module work allocation process S300 includes: Step S310 determines whether the primary serial port 1 receives data successfully, if yes, executes step S320, otherwise executes step S400; Step S320 determines whether it is a command from the master serial port 2. If so, step S321 is executed, the master serial port 2 is forwarded to the slave module, and the slave module executes step S100. If not, step S330 is executed; Step S330 determines whether it is a command from the main serial port 1. If so, step S331 is executed to set an action flag, and then step S400 is executed. Otherwise, step S400 is executed.

7. A configurable universal modular test system as claimed in claim 3, characterized in that: The inspection process S400 includes: Step S410 determines whether the security port is triggered, if so, executes step S411 to start the action protection, then returns to execute step S200, otherwise, executes step S420; Step S420 determines whether the action is idle, which includes the master module and the slave module. If it is determined to be idle, step S421 is executed to start the operation according to the action flag and register the sensing inspection record, otherwise step S500 is executed; After step S421 starts the operation according to the action flag, if step S422 is executed for the main module sensing check class and S423 is executed for the sensing check ignoring class, then step S500 is entered after execution; if step S424 is executed for the slave module sensing check class, then step S425 is continued to be executed where the main serial port 2 is forwarded to the slave module, and then step S500 is executed.

8. A configurable universal modular test system as claimed in claim 7, characterized in that: The main module sensing inspection process S500 includes: Step S510 determines whether the output port flag == completed, if so, execute step S511 to start the sensing check, otherwise execute step S520; Step S520 determines whether the output port flag == error, if so, execute step S521 to determine whether the error count is ≥ 3, if so, execute step S560 to set the state and record the action determination result; If step S521 is executed to determine whether the error count is ≥ 3, if it is determined that otherwise, step S522 is executed to set the action to restart; If step S520 determines whether the output port flag == error, if it is determined otherwise, step S530 is executed; Step S530 determines whether the output port flag == waiting, if so, then executes step S531 to determine whether it is timed out, if so, then executes step S521, otherwise, executes step S522; If step S530 determines whether the output port flag == waiting, if it is determined otherwise, step S540 is executed; Step S540 determines whether the output port flag == jump, if so, executes step S560, otherwise, executes step S550; Step S550, determine whether the output port flag == jump failure, if it is determined to be yes, execute step S560, otherwise execute step S522.

9. A configurable universal modular test system as claimed in claim 8, characterized in that: The slave module sensing check process S600 is completed in the slave module, including starting the sensing check from step S511 of the master process, and then executing step S513 of the slave module sensing check; Step S610 determines whether the idle state has timed out, if so, executes step S620, otherwise returns to the main process; Step S620 determines whether the input port flag is == error, if so, execute step S621 to set the input port flag == idle, continue to execute step S622 master serial port 2 to send instructions to the slave module, then return to the main process, otherwise execute step S630; Step S630 determines whether the input port flag == completed, if so, the check ends and the state is set in step S560, otherwise, step S640 is executed; Step S640 determines whether the input port flag == waiting, if so, executes step S650, otherwise executes step S660; Step S650 determines whether the waiting count is greater than 10, if so, executes step S621, otherwise executes step S660; Step S660 determines whether the debounce count is greater than 50. If so, the check ends and step S560 is executed to set the status. Otherwise, the main process is returned.

10. A configurable universal modular test system as claimed in claim 9, characterized in that: The action execution process S700 includes: Step S710 determines whether a combined action is performed, if so, executes step S720, otherwise, executes step S730; Step S720 determines whether the independent action is completed, if so, executes step S740, otherwise returns to step S200; Step S740 determines whether the combined action is completed, if so, the operation ends, otherwise, step S741 is executed to prepare for the next action, and then returns to step S200; Step S730 determines whether it is an independent action, if so, executes step S750, otherwise, executes back to step S200; Step S750 determines whether the action is completed, if so, the operation ends, otherwise returns to step S200.

Images