WO2023116752A1 - Test method and test apparatus for code scanner head - Google Patents

Abstract

Provided in the present application are a test method and test apparatus for a code scanner head. The test method comprises: according to a complete test status flag bit of a code scanner head, determining whether to perform a PCBA test and/or a module test. The PCBA test comprises the following steps: acquiring a serial number and a firmware version number of the code scanner head; if the serial number is successfully acquired, and the firmware version number is correct, determining whether to enable an automatic test; and if an automatic test is enabled, automatically executing a PCBA test item in the test. The module test comprises the following steps: acquiring the serial number, the firmware version number, and a PCBA test result of the code scanner head; if the serial number is successfully acquired, the firmware version number is correct, and the PCBA test result is a pass, determining whether to enable the automatic test; and if the automatic test is enabled, automatically executing a module test item in the test. The test method and the test apparatus improve the test efficiency of a code scanner head.

Description

Detection method and detection device for sweeping dock technical field

The present application mainly relates to an automatic detection method and device, in particular to a detection method and a detection device for scanning docks.

Background technique

With the increasing popularity of barcode scanning applications, more and more devices such as POS machines, cash registers, counter cards, and self-service cash register systems support barcode scanning, and the tests related to scanning docks have also increased, including a number of test items. At present, when testing the sweeping dock, it is necessary to enter a separate interface for each test, and return to the previous level after the test is completed to start the next test. There are too many interactions in this way, and the operation process is cumbersome. For the dock scanner that has been tested, you need to enter the corresponding test item to check the test status of the dock scanner, and the test steps have been added. In addition, in the production test, the current test and the code scanning test are directly judged by humans. The existing equipment test items are single, there is a lot of repetitive labor in the test process, the degree of automation is low, and the test efficiency is low. The error is large. The above-mentioned problems lead to low detection efficiency and lax quality control of the wharf to be scanned.

Contents of the invention

The application proposes a detection method for scanning docks to solve the above-mentioned technical problems, including: judging whether to perform PCBA test and/or module test according to the complete test status flag of the sweep dock to be tested, the complete test status flag is used To represent the test status of the dock to be tested, the test status includes a PCBA test status and a module test status, wherein the PCBA test includes the following steps: Step S11: Obtain the serial number and the serial number of the dock to be tested Firmware version number; Step S12: If the serial number is obtained successfully, and the firmware version number is correct, then judge whether to open the PCBA automatic test; Step S13: If the PCBA automatic test is opened, then automatically execute the PCBA test The PCBA test item; Step S14: record PCBA test result; The module test includes the following steps: Step S21: Obtain the serial number, firmware version number and the PCBA test result of the scanning dock to be tested; Step S22: If Successfully obtain the serial number, the firmware version number is correct, and the PCBA test result is passed, then judge whether to open the automatic test of the module; Step S23: if open the automatic test of the module, then automatically execute the automatic test of the module The module test item in the group test; Step S24: record the module test result.

In one embodiment of the present application, before the step of judging whether to carry out the PCBA test and/or module test according to the complete test status flag bit of the scanning dock to be tested, it also includes: from the micro control unit of the scanning dock to be tested Obtain the complete test status flag bit in .

In an embodiment of the present application, the complete test status flag includes multi-bit binary characters, including a first group of binary characters and a second group of binary characters, and the first group of binary characters is used to indicate that the PCBA test state, the second group of binary characters is used to represent the test state of the module.

In an embodiment of the present application, before the step S11 and before the step S21, it also includes: writing the serial number and firmware version number of the scanning dock to be tested into the micro control unit; the steps Both S11 and the step S21 include: reading the serial number and the firmware version number from the micro control unit.

In an embodiment of the present application, the step S21 further includes: reading the PCBA test result from the microcontroller unit.

In an embodiment of the present application, the PCBA test item and/or the module test item at least includes a current test.

In an embodiment of the present application, the PCBA test item also includes one or a combination of supplementary light grid lamp test and code scanning test.

In an embodiment of the present application, the module test item further includes one or any combination of supplementary light grid light test, code scanning test, close-range test and distant view test.

In an embodiment of the present application, in the PCBA test, when all PCBA test items pass the test, the PCBA test result is passed.

In an embodiment of the present application, in the module test, when all the module test items pass the test, the module test result is passed.

In an embodiment of the present application, after the PCBA test and/or the module test, a module verification is also included, and the module verification is used to judge the grating lamp to be tested. Whether the boundary aperture is within the FOV of the camera of the dock to be tested, and if so, the dock to be tested passes the module verification.

In an embodiment of the present application, the step of module verification includes: enabling the scanning terminal to be tested to perform a code scanning operation; when performing the code scanning operation, obtaining the grating light of the scanning terminal to be tested Calculate the offset of the quasi-center, and judge whether the boundary aperture of the grating light of the wharf to be tested is located within the FOV of the camera of the wharf to be tested according to the offset.

In an embodiment of the present application, the dock to be tested includes one or any combination of a camera, a laser light and a supplementary light.

The present application also provides a detection device for scanning docks, including: a memory for storing instructions executable by a processor; and a processor for executing the instructions to implement the detection method for scanning docks as described above.

The present application also provides a computer-readable medium storing computer program codes, the computer program codes implement the above-mentioned scanning code detection method when executed by a processor.

The detection method of sweeping the dock of the present application knows the test state of the sweeping dock in advance before the test, avoids interface switching, and simplifies the operation process; at the same time, by setting two test modes of automatic test and manual test, automatic judgment and manual judgment by software The combined method reduces manual intervention in the testing process, improves testing efficiency, and is conducive to improving the production efficiency and testing quality of dock sweeping.

In order to solve the above problems, the present application provides a detection device for scanning docks, including: a test terminal for carrying the scanning dock to be tested; a display terminal for generating and displaying barcodes; a driving mechanism for placing the display terminal or The mold of the test terminal; and a controller for controlling the test terminal, the display terminal and the driving mechanism, wherein the controller controls the test parameters of the scan terminal to be tested through the test terminal , the controller controls the movement of the driving mechanism and the barcode to be generated and displayed by the display terminal according to the test content.

In an embodiment of the present application, the display terminal includes a display screen.

In an embodiment of the present application, the driving mechanism includes a mechanical arm.

In an embodiment of the present application, one or any of the controller, the testing terminal, the display terminal and the driving mechanism are connected to the same wireless network.

In an embodiment of the present application, the controller is further configured to send a first instruction to the driving mechanism, where the first instruction includes an instruction to control the moving track and/or moving speed of the driving mechanism.

In an embodiment of the present application, the controller is further configured to send a second instruction to the display terminal, the second instruction includes one or any of the size, type, color and grayscale of the barcode combination.

In an embodiment of the present application, the controller is further configured to record the state of the barcode, and the state includes one or any combination of barcode generation success, barcode generation failure, and barcode generation timeout.

In an embodiment of the present application, the controller is further configured to send a third instruction to the test terminal, the third instruction includes the parameters of the dock scan test and the test result parameters, wherein the scan dock test The parameters include the switch command and code scanning frequency of the scanning dock to be tested, and the test result parameters include a timeout period.

In an embodiment of the present application, the controller is further configured to judge the test result of the current scan code test according to the test result parameter, and the test result includes one or any of test success, test failure and timeout failure combination.

In an embodiment of the present application, the test content includes one or any combination of depth of field test, grayscale test, motion tolerance, fixed speed, color barcode, and stained barcode.

The testing device for scanning docks of the present application can automatically complete the testing of code scanners or scanning docks by combining the controller, testing terminal, display terminal and driving mechanism into a unified automatic testing device, thereby improving the testing efficiency.

Figure overview

Features and performances of the present invention are further described by the following examples and accompanying drawings.

Fig. 1 is the structural block diagram of the dock to be tested in the detection method of scanning dock according to an embodiment of the present application;

FIG. 2 is an exemplary flow chart of a detection method for scanning docks according to an embodiment of the present application;

Fig. 3 is an exemplary flow chart of PCBA testing in the detection method of scanning dock according to an embodiment of the present application;

Fig. 4 is an exemplary flow chart of PCBA testing in the detection method of scanning dock according to an embodiment of the present application;

Fig. 5 is an exemplary flow chart of module testing in the detection method of dock scanning according to an embodiment of the present application;

FIG. 6A and FIG. 6B are exemplary flowcharts of module testing in the detection method of dock scanning according to an embodiment of the present application;

7A and 7B are schematic diagrams of the principle of module verification in the detection method of dock scanning according to an embodiment of the present application;

Fig. 8 is a schematic diagram of the connection relationship of the detection device for scanning the dock according to an embodiment of the present application;

FIG. 9 is a schematic structural frame diagram of a detection device for scanning docks according to an embodiment of the present application;

Fig. 10 is an exemplary timing diagram of the detection device for scanning the dock of the embodiment shown in Fig. 9 when testing;

Fig. 11 is a schematic structural frame diagram of a detection device for scanning docks according to another embodiment of the present application;

FIG. 12 is a system block diagram of a detection device for scanning docks according to an embodiment of the present application.

Preferred Embodiments of the Invention

The flow chart is used in this application to illustrate the operations performed by the system according to the embodiment of this application. It should be understood that the preceding or following operations are not necessarily performed in an exact order. Instead, various steps may be processed in reverse order or concurrently. At the same time, other operations are either added to these procedures, or a certain step or steps are removed from these procedures.

In some embodiments of the present application, the dock to be tested includes one or any combination of a camera, a grating light and a supplementary light.

FIG. 1 is a structural block diagram of a dock to be tested in a dock scanning detection method according to an embodiment of the present application. Referring to FIG. 1 , the dock scanner to be tested mainly includes a grating light 12 , a camera 13 , a supplementary light 14 , and a dock scanner motherboard 11 for placing these hardware. The dock mainboard 11 includes an MCU chip. It can be understood that what is shown in FIG. 1 is only an example, and is not intended to limit the specific hardware included in the dock scanning to be tested.

According to different production stages, the test of scanning dock can be divided into two stages: PCBA (Printed Circuit Board Assembly) test and module test. Among them, PCBA refers to the whole process of PCB empty board passing through SMT upper part or DIP plug-in. The main hardware to be tested for scanning the dock includes the grating light 12 shown in FIG. 1 , the camera 13 and the supplementary light 14 . In order to perform PCBA testing, hardware such as camera 13, grating light 12 and fill light 14 can be fastened to the scanner main board 11, as shown in FIG. 1 . The module test is usually after the PCBA test is completed, the dock scanning main board 11, the grating light 12, the camera 13 and the fill light 14 shown in Figure 1 are packaged as a whole into a complete dock scanning hardware 10, and the complete dock scanning The overall test of the hardware 10 is performed to investigate the complete performance of the scanning dock to be tested in use.

The detection method of the sweeping dock of the present application includes: judging whether to carry out PCBA test and/or module test according to the complete test state flag of the sweeping dock to be tested, the complete test state flag is used to represent the test state of the sweeping dock to be tested, and the test Status includes PCBA testing status and module testing status. In this embodiment, there is no limitation on how to obtain the complete test status flag of the dock to be tested. You can check whether the test item has passed the test by entering the test item of the dock scan to be tested.

In some embodiments, before the step of judging whether to perform PCBA test and/or module test according to the complete test status flag bit of the dock to be tested, it also includes: obtaining the complete test status from the microcontroller unit of the dock to be tested Flag bit. Wherein, a micro control unit (MCU) can be included in the main board 11 of the scanning dock as shown in FIG. 1 .

FIG. 2 is an exemplary flow chart of a detection method for scanning docks according to an embodiment of the present application. As shown in Figure 2, the detection method of this embodiment comprises the following steps:

Step S01: Insert the scanning dock to be tested. Specifically, a dock-sweeping test fixture is used in the dock-sweeping test process, and the fixture includes a tester and various test environments. The accompanying test machine is externally connected to the FPC cable, and the terminal to be tested is connected to the accompanying test machine through the FPC line. Inserting the scanning dock to be tested in this step refers to buckling the scanning dock to be tested to the FPC and connecting it with the accompanying test machine.

Step S02: Obtain the complete test status flag. That is, the test results of the PCBA test and the module test are obtained. This application does not limit how to obtain the complete test status flag.

Step S03: Determine whether the dock scanning to be tested has been tested. If yes, go to step S05; if not, go to step S04.

In some embodiments of the present application, when the dock to be tested is connected to the tester, the complete test status flag can be obtained from the micro control unit (MCU) through program settings, and the complete test status flag includes multiple Bit binary characters, which include the first group of binary characters used to represent the PCBA test status and the second group of binary characters used to represent the module test status.

For further illustrating the complete test state flag of the present application, a specific example is given here: the complete test state flag can be the following 16 binary characters: 1111000011110000; wherein the first eight characters are the first group of binary characters, representing the PCBA Test result, the last eight characters are the second group of binary characters, indicating the result of the module test. The binary character "1" can indicate that the test result of a specific item is successful, and "0" indicates failure or not tested. The test status of PCBA test and module test can be checked through the flag bit, so as to determine the next step according to the test result. Exemplarily, it is assumed that the PCBA test includes a current test, a code scanning test and a supplementary light test. In the first group of binary characters, the first digit from the left represents the current test result, and the second digit represents the code scanning In the test result, the third digit indicates the supplementary light test. If the current test of the scanning terminal to be tested is successful, the code scanning test fails, and the supplementary light test is successful, the first group of binary characters is: 10100000. According to the agreement, the status of each test item in the scanning dock to be tested can be known by reading the complete test status flag.

Step S03 can know the status of all PCBA tests and module tests of the scanning terminal to be tested according to the complete test status flag. Exemplarily, a specific flag bit may be set in the complete test status flag bit to indicate whether a certain test item has been tested. It can also be judged whether one of the multiple test items has been tested. Continuing the above example, for example, judge whether there is "1" in the first group of binary characters tested by PCBA, and whether there is "1" in the second group of binary characters tested by the module. Tested if there is at least one "1".

Step S04: Display a green background. If it is determined in step S03 that the dock to be tested has not been tested, a green background is displayed, indicating that the dock to be tested needs to be tested.

Step S05: Determine whether the test is successful. If it is judged in step S03 that the dock to be tested has been tested, then further judge the result of the test. If yes, go to step S07; if not, go to step S06. Step S05 can be used to determine whether all test items are successfully tested, or determine whether a specific test item is successfully tested.

Step S06: Display a red background. If it is determined in step S05 that the terminal to be tested has not passed the test, a red background is displayed. Indicates that the dock to be tested needs to be tested.

Step S07: Display a turquoise background. If it is determined in step S05 that the dock to be tested has passed the test, a turquoise background will be displayed. Indicates that the terminal of the meter to be tested has passed the test, and no follow-up test is required.

Through the above steps, you can know the test status of the wharf to be tested before the test, and you can know the test status without entering the complete test program. In the subsequent steps, you can only test for the test items that have not been tested and failed the test. Improve the production efficiency of sweeping dock.

In other embodiments, steps S03 and S05 can be combined into one step, and according to these embodiments, three different background colors can be given based on the result of one judgment.

Through the above steps, it is judged that the scanning docks to be tested need to be tested, and then these scanning docks to be tested will be tested.

FIG. 3 is an exemplary flow chart of PCBA testing in the detection method for scanning docks according to an embodiment of the present application. As shown in Figure 3, the PCBA test in this embodiment comprises the following steps:

Step S11: Obtain the serial number (SN number) and firmware version number of the dock to be tested. Among them, the SN number is the unique identification of each scanner, which is written into the MCU according to the established rules before the test. The firmware version number is the firmware version information imported by the current batch production, and the firmware version is written into the MCU before testing.

Step S12: If the serial number is obtained successfully and the firmware version number is correct, then determine whether to enable the PCBA automatic test.

In some embodiments of the present application, when performing the PCBA test, it is necessary to ensure that the correct SN number has been written into the MCU chip of the scanning terminal and the firmware version that has passed the test is flashed. The SN number and firmware version number can be read from the MCU. The successful acquisition of the serial number in step S12 means that the SN number has been read, and the SN number is legal. If the SN number cannot be read from the MCU, or the SN number is illegal, the serial number has not been obtained successfully.

In some embodiments, the SN to be read is written according to a specific rule. If the SN cannot be read out according to the specific rule, it means that the SN is not written in the MCU or the SN is wrong. If no SN is written, the read SN will be empty or a default specific character.

After step S12, if the serial number is not obtained successfully, or the firmware version number is incorrect, a prompt box will pop up in the software interface for testing, and the testing is not allowed.

Step S13: If the PCBA automatic test is enabled, the PCBA test items in the PCBA test are automatically executed.

In one embodiment of the present application, the automatic test is started through the software interface, and then each test item is tested according to the set order, and the test results of each test item are judged. If a certain test is passed, the next test will be automatically executed. item, if a test is not passed, the test is stopped and the test item is recorded. Correspondingly, if the automatic test is not enabled, manual testing is used to manually control the test items to be performed by clicking the corresponding test items on the software interface.

Step S14: Record the PCBA test results.

In some embodiments, the PCBA test result is recorded in a flag bit corresponding to the PCBA test among the complete test status flag bits.

In some embodiments, the PCBA test item and/or the module test item at least includes a current test.

In some embodiments, the PCBA test item also includes one or a combination of supplementary light grid light test and code scanning test.

In order to further illustrate the PCBA test of the present application, a specific example is given here. Fig. 4 is the exemplary flow chart of PCBA test in the detection method of sweeping dock of an embodiment of the present application, and this embodiment comprises the following steps:

Step S110: Obtain SN number and firmware version number. According to the obtained SN number and the firmware version number, the next step to be executed is judged. If the obtained SN number and the firmware version number are correct, step S112 is executed, otherwise, step S111 is executed, and the test is ended.

Step S112: Determine whether to test automatically. In this embodiment, automatic PCBA testing or manual PCBA testing can be selected through the software interface. If the automatic test is enabled, go to step S113; otherwise, go to step S120.

Step S113: Perform a current test. When the automatic test is selected, the PCBA test items in the PCBA test are automatically executed. The order of the test items can be set. In the embodiment shown in FIG. 4 , the test items include: current test, supplementary light grid lamp test and code scanning test. The order of the test items can be adjusted according to requirements. Preferably, the test order is: current test, supplementary light grid light test, and code scanning test. In this way, if the current test fails, it means that the hardware itself is not connected, and there is no need to carry out the next test; after the current test is passed, it is necessary to judge whether there is any solder joint between the hardware through the supplementary light grid lamp test. The code scanning test is performed only after the test is passed.

Step S114: Determine whether the current test is successful. If the current test fails, go to step S128: stop the test, then go to step S129: record the test failure; if the test is successful, go to step S115.

Step S115 : Carry out a grid light test for supplementary light.

Step S116: Judging whether the test of the supplementary light grid light is successful. If the supplementary light grid light test fails, proceed to step S128: stop the test, and then proceed to step S129: record the test failure; if the test succeeds, proceed to step S117.

Step S117: Perform code scanning test.

Step S118: Determine whether the code scanning test is successful. If the code scanning test fails, proceed to step S128: stop the test, and then perform step S129: record the test failure. If the code scanning test is successful, step S119 is executed.

Step S119: record that the test is successful. If the scanning dock to be tested passes the current test, fill light grid light test and code scanning test, the record test is successful, that is, the scanning dock to be tested has passed all PCBA tests.

Step 120: Manual testing. If it is judged in step S112 that the automatic test is not enabled, a manual test is performed by default. Specifically, in step S120, the test item can be selected manually by manually clicking on the software interface. The test items listed in the embodiment shown in FIG. 4 include: current test, supplementary light grid light test and code scanning test. If the current test is selected, step S121 is performed; if the supplementary light grid light test is selected, step S122 is performed; if the code scanning test is selected, step S123 is performed.

Step S121: Conduct a current test.

Step S122 : Carry out a grid light test for supplementary light.

Step S123: Perform code scanning test.

Step S124: After the current test is performed, it is judged in this step whether it is successful or not, and the test result is recorded.

Step S125: After the supplementary light grid lamp test, judge whether it is successful or not in this step, and record the test result.

Step S126: After the code scanning test is performed, it is judged in this step whether it is successful or not, and the test result is recorded.

Step S127: Judging whether all test items of the manual test are all successful. If all test items are successful, it is determined that the test is passed, and step 119 is performed to record that the test is successful; otherwise, it is determined that the test is not passed, and step S129 is performed.

In some embodiments, the judgment results of steps S124, S125 and S126 are directly sent to step S127, as long as one of the results is failure, the judgment result of step S127 is no. In the case of manual testing, it is judged in step S127 whether all PCBA test items have been executed according to the number of judgment results received. For example, if the number of PCBA test items is set to 3, then in step S127, if 3 test results are received, it means that all test items have been manually clicked, and it can be determined whether all test items are successful.

Step S128: Stop testing.

Step S129: Record test failure.

In some embodiments, both the record test success in step S119 and the test failure record in step S129 are recorded in the flag bits corresponding to the PCBA test item in the complete test status flag bits of the scanning terminal to be tested.

According to the embodiment shown in FIG. 4 , no matter how many test items the PCBA test includes, as long as the test result of one of them is a failure, the PCBA test is considered to be a failure. When all PCBA test items pass the test, the PCBA test result is passed.

According to the embodiment shown in Figure 4, by setting the automatic test mode, the manual intervention in the test process is reduced; by setting the test mode of the manual test, more convenient options are provided for the sweeping dock test, which can be selectively carried out manually The test of several test items; the combination of automatic test and manual test improves the test efficiency of sweeping the dock.

FIG. 5 is an exemplary flow chart of module testing in the detection method of dock scanning according to an embodiment of the present application. As shown in Figure 5, the module test in this embodiment comprises the following steps:

Step S21: Obtain the serial number and firmware version number of the dock to be tested and obtain the PCBA test result. Wherein, the specific content of obtaining the serial number and the firmware version number of the dock to be scanned is the same as step S11, and will not be repeated here.

Step S22: If the serial number is obtained successfully, the firmware version number is correct, and the PCBA test result is passed, it is judged whether to enable the module automatic test. The difference between step S22 and step S12 is that this step requires that the scanning terminal to be tested has passed the PCBA test, and if it fails, the module test will not be performed; what is more, the judgment of this step is: enable the automatic module test. The same part as step S12 will not be repeated here.

Step S23: If the automatic module test is enabled, the module test item in the module test is automatically executed.

In some embodiments, the module test items include at least a current test.

In some embodiments, the module test item also includes one or any combination of supplementary light grid light test, code scanning test, close-range test and distant view test.

Similar to step S13, step S23 can be controlled through the same software interface as in step S13.

Step S24: Record the module test result.

In order to further illustrate the module test of the present application, a specific embodiment is given here. FIG. 6A and FIG. 6B are exemplary flowcharts of module testing in the detection method for scanning docks according to an embodiment of the present application. It should be noted that in the process of module testing, in addition to obtaining the SN number and firmware version before step S210 shown in Figure 6A, it is also necessary to determine whether the scanning terminal to be tested has passed the PCBA test, and if it has not passed the PCBA test, then no Mod testing process, but end testing.

FIG. 6A and FIG. 6B are used together to illustrate the overall process of the module test in this embodiment, wherein the test items of the module test include current test, supplementary light grid lamp test, code scanning test, close-up test and long-term test. Referring to Fig. 6A, the module test of this embodiment includes the following steps:

Step S210: Obtain the SN number, firmware version number and PCBA test flag, when the SN number and the firmware version number are correct, and judge the scanning dock to be tested according to the PCBA test flag in the complete test status flag of the scanning dock to be tested If the PCBA test has been passed, turn to step S212; otherwise, turn to step S211.

It should be noted that among the three judging items whether the SN number is correct, whether the firmware version number is correct, and whether the PCBA test flag is successful, one of the judging results is no, and the judging result of step S210 is no.

Step S211: End the module test.

Step S212: Determine whether to enable automatic testing. This step is similar to step S112, except that the test to be performed is a module test instead of a PCBA test. The specific steps will not be described further. If yes, execute step S214; if no, execute step S213.

Step S213: When the automatic test is not enabled, perform a manual test on the software interface, and manually click each test item in the module test. The specific flow of manual testing is illustrated in Figure 6B.

Step S214: Conduct a current test.

Step S215: Determine whether the current test is successful. If yes, execute step S216; if not, execute step S230.

Step S216 : Carry out a grid light test for supplementary light.

Step S217: Judging whether the supplementary light grid light test is successful. If yes, execute step S218; if not, execute step S230.

Step S218: Perform code scanning test.

Step S219: Determine whether the code scanning test is successful. If yes, execute step S220; if not, execute step S230.

Step S220: Perform a close-range test.

Step S221: Determine whether the close-range test is successful. If yes, execute step S222; if not, execute step S230.

Step S222: Perform a prospect test.

Step S223: Determine whether the prospect test is successful. If yes, execute step S224; if not, execute step S230.

Step S224: Perform module verification.

Step S225: Automatically determine whether the module verification is successful. If yes, execute step S226; if no, execute step S230.

Step S226: Manually judge whether the module verification is successful. If yes, execute step S227; if no, execute step S230.

Step S230: Stop testing.

Step S231: Record test failure.

It should be noted that the sequence of test items defined in the automatic test process shown in FIG. 6A is: current test, supplementary light grid light test, code scanning test, close-up test, long-range test and module verification.

Referring to FIG. 6B, after step S213 in FIG. 6A, the following steps are also included:

Step S240: Conduct a current test.

Step S241: Perform a prospect test.

In Fig. 6A, other tests included in the module test of this embodiment are omitted between the modules of step S240 and step S241, which are the supplementary light grid light test, the code scanning test, and the close-up test.

Step S242: Determine whether the current test is successful.

Step S243: Determine whether the prospect test is successful.

In FIG. 6A , between the modules of step S242 and step S243 , the judging box for judging whether the supplementary light grid light test, code scanning test, and close-up test is successful is omitted.

After the judgment of steps S242-S243 is completed, the judgment result is recorded and used for the judgment of step S244.

Step S244: Determine whether all processes are successful. When all the module test items are successful, turn to step S227. This step S227 is the same step as that in FIG. 6A , so the same reference numerals are used.

If one of the module test items fails or fails, the result of step S244 is no, and the process turns to step S230.

Step S230 and step S231 in FIG. 6B are the same step as step S230 and step S231 in FIG. 6A respectively, so the same reference numerals are used.

Step S251: Perform module verification.

To carry out this step, the corresponding option to select the module calibration is provided on the software interface. Module verification can be performed by selecting this option. The module verification is the same as the module verification in step S224 in FIG. 6A , and will be described in a unified manner later.

Step S252: Automatically judge whether the module verification is successful. If yes, execute step S253; if not, execute step S230.

Step S253: Manually judge whether the module verification is successful. If yes, execute step S227; if not, execute step S230.

It can be understood that, in the process of the manual test shown in FIG. 6B , there is no limitation on the sequence of each test item.

Figure 6A and Figure 6B together show an embodiment of a complete detection method. In some embodiments, the steps related to module verification, namely steps S224, 225, 226, 251, 252, and 253, may not be included. In some embodiments, the step S226 and step S253 of manually judging whether it is successful may not be included in the step of module verification.

According to the embodiment of Fig. 6A and Fig. 6B, the scanning dock to be tested has passed the complete test of PCBA test and module test, and the test result obtained can be used as the test result of the scanning dock to be tested, and recorded in the scanning dock to be tested. Complete test status flags.

The steps related to the module verification in FIG. 6A and FIG. 6B are described below.

In some embodiments of the present application, after the PCBA test and/or the module test, module verification is also included. The module verification is used to judge whether the boundary aperture of the grating light of the wharf to be tested is within the FOV of the camera of the wharf to be tested, and if so, the wharf to be tested has passed the module verification. Specifically, the module verification includes the following steps: first, make the scanning dock to be tested perform a code scanning operation; specifically, make the scanning dock to be tested face the white background to perform the code scanning operation, and there is a gap between the scanning dock to be tested and the white background. A certain preset distance; then, when performing the code scanning operation, obtain the boundary aperture and crosshair of the grating light of the dock to be tested, calculate the offset of the crosshair, and judge the grating of the dock to be tested according to the offset Whether the boundary aperture of the light is within the FOV of the camera of the dock to be tested.

7A and 7B are schematic diagrams of the principle of module verification in the detection method according to an embodiment of the present application. Referring to FIG. 7A , when performing module verification, the scanning terminal to be tested is located about 15 cm away from the scanning plane 70 . The scan plane 70 may be a white background. Perform scan operations even with cameras and light barriers working simultaneously. Referring to Fig. 7B, the camera forms a FOV (Field of View) field of view 71 as shown in the outer frame on the scanning plane 70, and the grating light forms a boundary aperture 72 and a quasicenter 73 as shown in the inner frame on the scanning plane 70 . In this embodiment, the crosshair 73 is a crosshair. In other embodiments, the collimator 73 may have other shapes.

At a fixed position, the FOV angle of view 71 of the camera is fixed, and the boundary aperture 72 of the grating light is fixed. After the dock to be tested is imaged, the FOV angle of view 71 can be directly used as the size of the imaged picture, and calculated according to the algorithm Based on the position of the collimator 73 in the imaging picture, it can be calculated whether the boundary aperture 72 of the grating lamp is located outside the imaging picture. For example, parameters such as the top margin, bottom margin, left margin, and right margin from the boundary aperture 72 to the FOV viewing angle 71 can be calculated.

In some embodiments, the camera to be tested to scan the dock is a camera module. When the installation of the camera module and the grating light of the wharf to be tested is qualified, the boundary aperture 72 is located in the FOV field of view angle 71; when the installation of the camera module and the grating light of the wharf to be tested is unqualified, the boundary aperture 72 may be Located outside the 71° angle of view of the FOV. Through module verification, abnormal problems in the assembly of the scanning dock to be tested can be detected.

With reference to Fig. 7A and Fig. 7B, steps S226 and S253 of manual judgment in Fig. 6A and Fig. 6B include: after the automatic judgment is completed, the FOV map and the photo of the grating light are displayed together for the tester to re-judgment.

In the embodiment shown in Fig. 6A and Fig. 6B, after the verification of the module, it is firstly judged automatically according to the algorithm whether the verification of the module is successful, and then the manual judgment is performed based on the result of the automatic judgment, which ensures that the verification of the module is successful. Accuracy of group verification results.

The present application also provides a detection device for scanning docks, including a test terminal, a display terminal, a driving mechanism and a controller. The detection device can be used to implement the detection method described above. In particular, the detection device can be used in the PCBA test stage and the module test stage in the above detection method. Furthermore, the detection device is used for scanning code testing in the PCBA testing phase, scanning code testing in module testing, close-range testing and long-term testing, etc. By adopting the detection device, the test of the code scanner or the scanning dock can be completed automatically, and the test efficiency is improved.

FIG. 8 is a schematic diagram of a connection relationship of a detection device for scanning docks according to an embodiment of the present application. Referring to FIG. 8 , the detection device 800 of this embodiment includes a testing terminal 810 , a display terminal 820 , a driving mechanism 830 and a controller 840 . Among them, the test terminal 810 is used to carry the scanning terminal to be tested; the display terminal 820 is used to generate and display barcodes; the drive mechanism 830 has a mold (not shown) for placing the display terminal 820 or the test terminal 810; the controller 840 is used for Control the test terminal 810, the display terminal 820 and the drive mechanism 830, wherein the controller 840 controls the test parameters of the terminal to be tested through the test terminal 810, and the controller 840 controls the movement of the drive mechanism 830 and the display terminal 820 according to the test content. The barcode to be generated and displayed.

In some embodiments, the controller 840 is also used to perform the following steps in the detection method: obtain the complete test status flag bit from the micro control unit of the dock to be tested; judge whether to Conduct PCBA testing and/or module testing.

In the embodiment shown in Fig. 8, if the display terminal 820 is placed on the mold of the drive mechanism 830, the drive mechanism 830 can drive the display terminal 820 to move under the control of the controller 840. At this time, the position of the test terminal 810 Fixed; if the test end 810 is placed on the mold of the drive mechanism 830, the drive mechanism 830 can drive the test end 810 to move under the control of the controller 840. At this time, the position of the display end 820 is fixed.

Referring to FIG. 8 , the connecting lines are used in the figure to indicate the connection relationship of the various components, but the connecting lines are not used to limit the connection between the various components in a wired manner. Wherein, the controller 840 is respectively connected with the display terminal 820 , the testing terminal 810 and the driving mechanism 830 .

In some embodiments, one or any of the controller 840, the testing terminal 810, the display terminal 820 and the driving mechanism 830 are connected to the same wireless network. In the embodiment shown in FIG. 8, the controller 840, the test terminal 810, the display terminal 820 and the driving mechanism 830 are all connected to the same router 850, that is, the controller 840, the test terminal 810, the display terminal 820 and the The drive mechanism 830 is in the same wireless network. The driving mechanism 830 can receive instructions from the controller 840 through the wireless network, so as to control the movement of the mold according to the instructions, and then drive the movement of the display terminal 820 or the testing terminal 810 .

In some embodiments, the test content includes any one of PCBA test items and module test items. The controller 840 controls the movement of the driving mechanism 830 and the barcode to be generated and displayed by the display terminal 820 according to the test content. It can be understood that the cooperation of the driving mechanism 830 and the display terminal 820 may not be required for the test of some test items, such as the current test, the controller 840 directly controls the scanning terminal to perform the current test.

In some embodiments, the test content includes one or any combination of depth of field test, grayscale test, motion tolerance, fixed speed, color barcode, and stained barcode, and the required tests can be customized according to actual needs. These test contents all involve the control of the drive mechanism 830 and the display terminal 820 by the controller 840 . For different test contents, the barcodes to be generated by the display terminal 820 are different, for example, the content of the barcodes and the size of the barcodes (such as: 15mil QR codes) can be different.

Exemplarily, when the test content is a color barcode, the controller 840 controls the display terminal 820 to generate a color barcode. This application does not limit the method of how the display terminal 820 generates the color barcode. A plurality of color barcodes used for the color barcode test may be stored in the controller 840 in advance. When performing a color barcode test, you can also select a certain number of color barcodes to test in sequence according to the preset program. When the test content is a defaced barcode, the display terminal 820 generates a defaced barcode. Due to the actual situation, there can be many kinds of defaced barcodes, such as the location, size, and shape of the defaced part, etc. Displays the desired defaced barcode.

Similarly, for different test contents, the moving modes of the driving mechanism 830 are also different. For example, when the test content is a depth of field test, the controller 840 controls the driving mechanism 830 to move according to the requirements of the depth of field test. Exemplarily, when the display terminal 820 is placed on the mold of the driving mechanism 830, the distance between the display terminal 820 and the test terminal 810 is firstly made relatively close, and a close-up test is carried out, and the distance is gradually increased from an initial position, and one is changed each time. position, the controller 840 controls the scanning dock to be tested on the testing terminal 810 to perform a code scanning and record the scanning result. During the movement of the display terminal 820, the distance when the code scanning of the terminal under test is successful for the first time is the short-range distance. The content of the depth of field test is only an example, and is not intended to limit the specific content of the actual depth of field test.

In some embodiments, the controller 840 is further configured to send a first instruction to the driving mechanism 830 , where the first instruction includes an instruction to control the moving track and/or moving speed of the driving mechanism 830 . It can be understood that the first instruction is related to the test content. The movement trajectory is an arbitrary route in three-dimensional space.

In some embodiments, the controller 840 is further configured to send a second instruction to the display terminal 820 . The second instruction includes displaying one or any combination of the size, type, color and grayscale of the barcode. It can be understood that the second instruction is related to the test content.

According to these embodiments, when the wharf to be tested is tested, the controller 840 sends the first instruction to the driving mechanism 830 so that the driving mechanism 830 moves according to the test content, so that the test process is well controllable; The terminal 820 sends a second instruction containing different content to change the content of the barcode displayed on the display terminal 820, so that manual replacement of the barcode is not required, and the efficiency of the test is improved.

In some embodiments, the controller 840 is also used to record the state of the barcode generated and displayed by the display terminal 820, the state including one or any combination of successful barcode generation, barcode generation failure, and barcode generation timeout. When testing, the display terminal 820 needs to generate and display a specific barcode according to the test content. However, in some cases, the barcode finally generated and displayed by the display terminal 820 may be different from the predetermined barcode to be displayed. Thus, these embodiments provide a verification function for displayed barcodes. According to the status of the recorded barcode, it can be clearly defined whether the barcode was generated successfully, failed or timed out. In this way, when the barcode fails to be generated, the fault can be eliminated in time to avoid the long-term suspension of the barcode scan test due to the failure to generate the barcode.

In some embodiments, the display terminal 820 returns the result of generating the barcode according to the first instruction to the controller 840, so that the controller 840 obtains the result of generating the barcode, and calculates the state of the barcode.

The application does not limit the types of barcodes displayed on the display terminal 820, and the barcodes may include one-dimensional barcodes, two-dimensional barcodes, and multi-dimensional barcodes. Specifically, for example the following types of barcodes: CODE25_INTERLEAVED, CODE39, CODE25_INDUSTRY, CODE39_EXTENDED, CODE93, CODE_128, EAN, UPC_A, UPC_E, QR, PDF417, DATAMATRIX, AZTEC, CHANNEL_CODE, CODABAR, CODE25_INDUSTRY, CODE25_INTER LEAVED, CODE_11, CODE25_MATRIX, CODE25_IATA, CODE25_DATALOGIC , ITF14, CODE39, CODE39_EXTENDED, CODE93, DOD_LOGMARS, CODE_128, NVE18, EAN, MSI_PLESSEY, TELEPEN, TELEPEN_NUMERIC, UPC_A, UPC_E, CODABLOCK_F, CODE16K, CODE49, PDF417, PDF417_TRUNCATED, PDF417 _MICRO, AZTEC, AZTEC_RUNE, DATAMATRIX, CODE_ONE, GRIDMATRIX, MAXICODE ,QR,QR_MICRO,DB14,DB14_STACKED,DB14_STACKED_OMNIDIRECT,DB_LIMITED,DB_EXPANDED,DB_EXPANDED_STACKED,AUSPOST,AUSPOST_REPLY,AUSPOST_REROUTE,AUSPOST_REDIRECT,BRAZIL_CEPNET,DP_LEITCODE,DP_IDENTCODE,K IX_CODE, JAPAN_POST, KOREA_POST, RM4SCC, USPS_IMAIL, CODE39_HIBC, USPS_POSTNET, USPS_PLANET, CODE_32, AZTEC_HIBC , CODABLOCK_HIBC, CODE_128_HIBC, DATAMATRIX_HIBC, PDF417_HIBC, PDF417_MICRO_HIBC, QR_HIBC, PHARMA, PHARMA_TWOTRACK, PZN, USPS_IMPB.

In some embodiments, the controller 840 includes terminals such as a computer (PC), a tablet computer, and the like.

In some embodiments, the controller 840 is further configured to send a third instruction to the testing terminal 810, where the third instruction includes a terminal scanning test parameter and a test result parameter. Among them, the test parameters of the scanning terminal include the switch command and the scanning frequency of the scanning terminal to be tested, and the test result parameters include the timeout time. The opening and closing of the scanning dock can be controlled by sending the third instruction through the controller 840 without manual participation. The code scanning frequency and timeout time can also be changed through the controller 840 . For example, the code scanning frequency can be set to 20 milliseconds through the controller 840, that is, the code is scanned every 20 ms; Code timed out.

In some embodiments, the controller 840 is further configured to judge the test result of the current code scanning test according to the test result parameter, and the test result includes one or any combination of test success, test failure and timeout failure. For example, if the timeout period is set to 2 seconds by the controller 840, when the code scanning result of the test terminal 810 exceeds 2 seconds, the code scanning result cannot be obtained, and the controller 840 judges the code scanning test result as a code scanning timeout; If the code scanning result is correct, the controller 840 determines the test result of the code scanning test as successful code scanning, and then moves the driving mechanism 830 to perform the next test. If the scan code fails, re-scan the code until the number of failures reaches the predetermined number or the scan code times out. For the above test results, the controller 840 can store them in digital format, such as xls, txt format, so as to facilitate the sharing, backup and delivery of subsequent test results. At the same time, the step of manually recording the test results is also omitted, which improves the test efficiency.

FIG. 9 is a schematic diagram of a structural frame of a detection device according to an embodiment of the present application. 8 and FIG. 9, in the embodiment shown in FIG. 9, the test terminal 810 of the detection device 800 is embodied as a code scanning test terminal 910, the display terminal 810 is embodied as a barcode display terminal 920, and the driving mechanism 830 is embodied as The robotic arm 930 and the controller 840 correspond to the controller 940 in FIG. 9 . Since FIG. 9 is a specific implementation of the embodiment shown in FIG. 8, the same components may use different labels, such as controller 840 and controller 940, which respectively refer to the controller 840 in the framework detection device 800 , the specific implementation of the controller 940 in the detection device 900, both of which belong to different representations of the same element.

Referring to FIG. 9 , in the detection device 900 , a code scanning terminal 910 is equipped with a code scanning terminal to be tested. The code scanning test terminal 910 can be equipped with various types of scanning docks, and has wide versatility. A barcode is generated and displayed at the barcode display terminal 920 .

In some embodiments, the display end includes a display screen. In the embodiment shown in FIG. 9 , the barcode display terminal 920 can be various types of display screens, such as liquid crystal display screens, ink display screens, LED display screens, and the like.

There is a mold for placing the barcode display end 920 on the mechanical arm 930 . During the test, the barcode display terminal 920 is placed on the mold of the mechanical arm 930 , so that the mechanical arm 930 can drive the barcode display terminal 920 to move.

As shown in FIG. 9 , in this embodiment, the code scanning test terminal 910 , the barcode display terminal 920 , the mechanical arm 930 and the controller 940 are all placed on a workbench 950 . The workbench 950 can be a table at a certain height from the ground, or it can be the ground. In some other embodiments of the present application, the above devices may be placed according to actual testing requirements, and are not limited to the situation in this embodiment.

FIG. 10 is an exemplary timing diagram of the detection device of the embodiment shown in FIG. 9 when testing. The testing process will be further described below with reference to FIG. 9 and FIG. 10 .

Referring to FIG. 10 , the sequence diagram includes four execution subjects in the embodiment shown in FIG. 9 : barcode display terminal 920 , controller 940 , code scanning test terminal 910 and mechanical arm 930 . Among them, the long bars below each execution body represent the time progress bar from top to bottom, and the endpoints of the aligned progress bars indicate that the task nodes execute actions at the same time.

Referring to FIG. 103 , for example, when the controller 940 is a PC, the PC directly connects to the robotic arm 930 through the development manual of the robotic arm 930 using an IP address, and sends the first Instructions, the PC end uses Socket communication to connect the code scanning test terminal 910 and the barcode display terminal 920 to send the second instruction and the third instruction to the barcode display terminal 920 and the code scanning test terminal 9210 respectively through the Socket communication method, and the barcode display terminal 920 sends all The state of the generated barcode is returned to the controller 940 , and the code scanning test terminal 910 returns the test result parameters to the controller 940 . The controller 940 judges the test result of the current code scanning test according to the test result parameters. If the test is successful, the robot arm 930 is moved to perform the next code scanning test; if the test fails, the code is scanned again until the result is a successful test. or timeout.

For example, in the close-range test, starting from the closest point, you will always get the result of code scanning failure, and then continue the test until the code scanning is successful. In the vision test, the scan code test result is always successful at the beginning, and the scan code fails when it reaches the farthest point, so it needs to be judged again.

In some embodiments, each instruction may include a corresponding command serial number, and each returned result, such as the status of the barcode and the test result, may also include a corresponding serial number, so as to facilitate the execution of the program.

In some embodiments, the maximum transmission value of the Socket communication data may be related to the length of the displayed barcode character string and the length of the returned test result. For example, in this embodiment, the maximum transmission value of Socket communication data is set to 4Kb.

In some other embodiments of the present application, the controller 940 may also be connected to the mechanical arm 930 by means of a serial port and Bluetooth, so as to send the first instruction to the mechanical arm 930 .

The above description is not intended to limit the connection modes among the test terminal, the display terminal, the driving mechanism, and the controller, and the specific connection modes may be varied.

The detection device of the present application forms a unified automatic detection device with the controller, test terminal, display terminal and driving mechanism, and sends instructions to the test terminal, display terminal and driving mechanism through the controller to perform various tests, which can be completed automatically The test of sweeping the dock improves the test efficiency. It also supports the export of test results in digital format, which facilitates the sharing, backup and transfer of test results.

In the embodiment shown in FIG. 9 , the position of the code scanning test terminal 910 can be fixed, and the mechanical arm 930 only drives the barcode display terminal 920 to move to test the terminal to be scanned. In some other embodiments of the present application, the display end is fixed, and the test end is driven by a driving mechanism for testing.

Fig. 11 is a schematic structural frame diagram of a detection device according to another embodiment of the present application. Different from the embodiment shown in FIG. 9 , in the detection device 1100 of this embodiment, the barcode display end 1120 is fixed on the workbench 1150 , and the code scanning test end 1110 is placed on the mold of the mechanical arm 1130 . In this way, the robot arm 1130 will drive the code scanning test end 1120 to move according to the first instruction sent by the controller 1140, and the way of its movement is related to the test content. It can be understood that for the same test content, in the embodiments shown in FIG. 9 and FIG. 11 , the first instructions sent by the controller may be the same or different, depending on the specific test content. For example, in the depth of field test, in the embodiment shown in Figure 9, the mechanical arm 930 drives the barcode display terminal 940 to approach the code scanning test terminal 910 first, and then gradually move away; in the embodiment shown in Figure 11, the mechanical arm 1130 Drive the code scanning test end 1110 to approach the code scanning test end 1110 first, and then gradually move away from it. In this example, the moving modes of the mechanical arms may be the same, so the first instruction is also the same.

Other contents in the embodiment shown in FIG. 11 are the same as those in the embodiment shown in FIG. 9 , and reference may be made to related explanations, and details are not repeated here.

The present application also provides a detection device for scanning docks, including: a memory for storing instructions executable by a processor; and a processor for executing the instructions to implement the detection method for scanning docks described above.

FIG. 12 is a system block diagram of a detection device for scanning docks according to an embodiment of the present application. Referring to FIG. 12 , the detection device 1200 may include an internal communication bus 1201 , a processor 1202 , a read only memory (ROM) 1203 , a random access memory (RAM) 1204 and a communication port 1205 . When applied to a personal computer, the detection device 1200 may also include a hard disk 1206 . The internal communication bus 1201 can realize data communication between components of the detection device 1200 . The processor 1202 can make a judgment and issue a prompt. In some embodiments, processor 1202 may consist of one or more processors. The communication port 1205 can realize data communication between the detection device 1200 and the outside. In some embodiments, the detection device 1200 can send and receive information and data from the network through the communication port 1205 . The detection device 1200 may also include different forms of program storage units and data storage units, such as a hard disk 1206, a read-only memory (ROM) 1203 and a random access memory (RAM) 1204, which can store various data for computer processing and/or communication. data files, and possibly program instructions executed by processor 1202. The processor executes these instructions to implement the main parts of the method. The result processed by the processor is transmitted to the user equipment through the communication port, and displayed on the user interface.

The above detection method can be implemented as a computer program, stored in the hard disk 1206, and can be loaded into the processor 1202 for execution, so as to implement the detection method of the present application.

The present invention also includes a computer-readable medium storing computer program codes. When the computer program codes are executed by a processor, the above-mentioned detection method for scanning docks is realized.

When the detection method of scanning docks is implemented as a computer program, it can also be stored in a computer-readable storage medium as a product. For example, computer-readable storage media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic stripe), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and flash memory devices ( For example, Electrically Erasable Programmable Read Only Memory (EPROM), card, stick, key drive). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" may include, but is not limited to, wireless channels and various other media (and/or storage media) capable of storing, containing and/or carrying code and/or instructions and/or data.

It should be understood that the embodiments described above are illustrative only. Embodiments described herein may be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For hardware implementation, the processor can be implemented on one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays ( FPGA), processors, controllers, microcontrollers, microprocessors, and/or other electronic units designed to perform the functions described herein, or combinations thereof.

Some aspects of the present application may be entirely implemented by hardware, may be entirely implemented by software (including firmware, resident software, microcode, etc.), or may be implemented by a combination of hardware and software. The above hardware or software may be referred to as "block", "module", "engine", "unit", "component" or "system". The processor can be one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DAPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors , a controller, a microcontroller, a microprocessor, or a combination thereof. Additionally, aspects of the present application may be embodied as a computer product comprising computer readable program code on one or more computer readable media. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic tape...), optical disks (e.g., compact disk CD, digital versatile disk DVD...), smart cards, and flash memory devices ( For example, cards, sticks, key drives...).

A computer readable medium may contain a propagated data signal embodying a computer program code, for example, in baseband or as part of a carrier wave. The propagated signal may take many forms, including electromagnetic, optical, etc., or a suitable combination. The computer-readable medium can be any computer-readable medium, except computer-readable storage media, that can communicate, propagate, or transfer the program for use by being coupled to an instruction execution system, apparatus, or device. Program code on a computer readable medium may be transmitted over any suitable medium, including radio, electrical cables, fiber optic cables, radio frequency signals, or the like, or combinations of any of the foregoing.

The basic concept has been described above, obviously, for those skilled in the art, the above disclosure of the invention is only an example, and does not constitute a limitation to the present application. Although not expressly stated here, various modifications, improvements and amendments to this application may be made by those skilled in the art. Such modifications, improvements, and amendments are suggested in this application, so such modifications, improvements, and amendments still belong to the spirit and scope of the exemplary embodiments of this application.

Claims (15)

1. A detection method for scanning docks, comprising:

   Judging whether to carry out PCBA test and/or module test according to the complete test state flag bit of scanning dock to be tested, described complete test state flag bit is used for representing the test state of described sweep dock to be tested, and described test state comprises PCBA test State and module test state, wherein, described PCBA test comprises the following steps:

   Step S11: Obtain the serial number and firmware version number of the dock to be tested;

   Step S12: If the serial number is successfully obtained, and the firmware version number is correct, then determine whether to enable the PCBA automatic test;

   Step S13: If the PCBA automatic test is enabled, automatically execute the PCBA test items in the PCBA test;

   Step S14: record the PCBA test result;

   The module test includes the following steps:

   Step S21: Obtain the serial number, firmware version number and the PCBA test result of the scanning dock to be tested;

   Step S22: If the serial number is successfully obtained, the firmware version number is correct, and the PCBA test result is passed, then it is judged whether to enable the automatic module test;

   Step S23: If the module automatic test is enabled, automatically execute the module test items in the module test;

   Step S24: record the module test result.
2. The detection method according to claim 1, further comprising: The complete test status flag bit is obtained in the micro control unit of the terminal.
3. The detection method according to claim 2, wherein the complete test state flag comprises multi-bit binary characters, including a first group of binary characters and a second group of binary characters, and the first group of binary characters is used for Indicates the PCBA test status, and the second group of binary characters is used to indicate the module test status.
4. The detection method according to claim 1, characterized in that, before the step S11 and before the step S21, it also includes: writing the serial number and firmware version number of the scanning dock to be tested into the micro control unit In; the step S11 and the step S21 all include: reading the serial number and the firmware version number from the micro control unit; the step S21 also includes: reading from the micro control unit The PCBA test results.
5. The detection method according to claim 1, wherein the PCBA test item and/or the module test item at least includes a current test, and the PCBA test item also includes a supplementary light grid lamp test and a code scanning test One or any combination of items, the module test item also includes one or any combination of supplementary light grid lamp test, code scanning test, close-range test and vision test.
6. The detection method according to claim 1, characterized in that, after the PCBA test and/or the module test, it also includes a module verification, and the module verification is used to judge the tested Whether the boundary aperture of the grating light of the scanning dock is within the FOV of the camera of the scanning dock to be tested, and if so, the scanning dock to be tested passes the module verification.
7. The detection method according to claim 6, wherein said step of module verification comprises:

   Make the scanning dock to be tested perform a code scanning operation;

   When performing the code scanning operation, obtain the boundary aperture and the center of gravity of the grating light of the scanning dock to be tested, calculate the offset of the alignment, and judge the position of the scanning dock to be tested according to the offset Whether the boundary aperture of the grating light is within the FOV of the camera of the dock to be tested.
8. The detection method according to claim 1, wherein the dock to be tested includes one or any combination of a camera, a grating light and a supplementary light.
9. A detection device for scanning docks, comprising:

   The test terminal is used to carry the scanning dock to be tested;

   The display terminal is used to generate and display barcodes;

   a drive mechanism having a mold for seating the display end or the test end; and

   A controller for controlling the test terminal, the display terminal and the driving mechanism, wherein the controller controls the test parameters of the scan terminal to be tested through the test terminal, and the controller according to the test The content controls the movement of the driving mechanism and the barcode to be generated and displayed by the display terminal.
10. The detection device according to claim 9, wherein the test content includes one or any combination of depth of field test, grayscale test, motion tolerance, fixed speed, color barcode, and stained barcode.
11. The detection device according to claim 9, wherein the display terminal includes a display screen, the driving mechanism includes a mechanical arm, and the controller, the testing terminal, the display terminal and the driving mechanism One or any of them are connected to the same wireless network.
12. The detection device according to claim 9, wherein the controller is further configured to send a first instruction to the driving mechanism, and the first instruction includes controlling the moving track and/or moving speed of the driving mechanism instructions.
13. The detection device according to claim 9, wherein the controller is further configured to send a second instruction to the display terminal, the second instruction includes the size, type, color and grayscale of the barcode one or any combination of them.
14. The detection device according to claim 9, wherein the controller is further configured to send a third instruction to the test terminal, the third instruction includes the scanning terminal test parameters and test result parameters, wherein, The test parameters of the scanning dock include the switch command and scanning frequency of the scanning dock to be tested, and the test result parameters include a timeout period.
15. The detection device according to claim 9, wherein the controller is further configured to execute the detection method according to any one of claims 1-8.

Images