Pipette management method and system

Abstract

The application provides a pipette management method and system. By setting an identification code on the outer surface of the pipette, the equipment information of the pipette can be obtained by scanning the identification code, and the verification information of the pipette can be obtained by scanning the identification code of the pipette. After obtaining the state of the pipette, a verification prompt instruction is sent according to the verification state of the pipette to prompt the related prompt device on the pipette stand to send a related prompt signal to prompt the staff about the state of each pipette, that is, the user can intuitively know the state of each pipette through the prompt signal, and there is no need to find a table to understand the state of each pipette, thereby omitting the step of finding the state and improving the user experience.

Description

Technical Field

[0001] This application relates to the field of pipette technology, and in particular to a pipette management method and system. Background Technology

[0002] In medical laboratories, pipettes are used extensively. As one of the key pieces of equipment affecting the accuracy of sample results, pipettes need to be checked or calibrated regularly to ensure the accuracy of the sample volume dispensed.

[0003] Currently, after checking or calibrating pipettes, users record the pipette's status information in a table. Therefore, when a user wants to determine the status of a particular pipette, they need to consult the table, which is cumbersome. Furthermore, when there are many pipettes, using a table to record information is prone to errors or omissions, leading to inaccurate pipette status information and potential quality risks. Summary of the Invention

[0004] To address the problems of existing technologies that require consulting tables to check pipette status, which is cumbersome and prone to errors or omissions when recording information in tables when there are many pipettes, leading to inaccurate pipette status information and quality risks, this invention provides a pipette management method and system that can automatically input and directly display the status information of pipettes.

[0005] To achieve the above-mentioned objectives, the present invention provides the following technical solution:

[0006] Firstly, a pipette management method is provided, applied to a pipette management system, the pipette management system comprising: a server, pipettes, and pipette racks, the method comprising:

[0007] Obtain the device information of the pipette based on the identification code on the pipette's exterior;

[0008] Obtain verification information, which includes verification items for equipment information;

[0009] The verification results are obtained based on the verification items and equipment information;

[0010] The verification status of the pipette is determined based on the verification results;

[0011] Based on the verification status, a verification prompt command is sent to the pipette, and the pipette is controlled to issue a verification prompt message.

[0012] Secondly, a pipette management system is provided, characterized in that the pipette management system includes: a server, pipettes, and a pipette rack, wherein the server is used for:

[0013] Obtain the device information of the pipette based on the identification code on the pipette's exterior;

[0014] Obtain verification information, which includes verification items for equipment information;

[0015] The verification results are obtained based on the verification items and equipment information;

[0016] The verification status of the pipette is determined based on the verification results;

[0017] Based on the verification status, a verification prompt command is sent to the pipette, and the pipette is controlled to issue a verification prompt message.

[0018] The aforementioned pipette management method and system uses an identification code on the pipette's exterior, recording the pipette's device information. Scanning the code retrieves this device information. After pipette verification or calibration, the verification information for each pipette is linked to its device information. Scanning the identification code again retrieves this verification information. Based on the verification and device information, the verification result is obtained, determining the pipette's verification status (e.g., normal, pending verification, or unverified). Once the pipette's status is known, a verification prompt is issued, triggering relevant indicators on the pipette holder to signal the status of each pipette. This allows users to intuitively understand the status of each pipette through these signals, eliminating the need to consult tables and improving the user experience. Meanwhile, by uploading the calibration data and parameters of the pipettes to the server, they can be accessed at any time when needed, which can reduce the risk of data loss and avoid quality problems caused by errors in manual statistics. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] in:

[0021] Figure 1 This is a flowchart illustrating a pipette management method in one embodiment;

[0022] Figure 2 This is a partial structural diagram of a pipette in one embodiment;

[0023] Figure 3 This is a flowchart illustrating a pipette management method in one embodiment;

[0024] Figure 4 This is a flowchart illustrating a pipette management method in one embodiment;

[0025] Figure 5 This is a partial structural diagram of a pipette in one embodiment;

[0026] Figure 6 This is a schematic diagram of a pipette management system in one embodiment.

[0027] in:

[0028] 1. Pipette; 2. Pipette holder; 21. Holder; 211. Sampling position; 22. Pipette holder; 23. Image acquisition device; 24. Status indicator light; 25. Inductive charging transmitter; 26. Gravity sensor; 3. Server. Detailed Implementation

[0029] The specific embodiments described herein are merely illustrative of this application and are not intended to limit this application.

[0030] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0031] It should be noted that the terms "comprising," "including," and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application, are intended to cover non-exclusive inclusion. For example, a process, method, terminal, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices. Terms such as "first" and "second" in the claims, specification, and accompanying drawings of this application, as well as relational terms, are used merely to distinguish one entity / operation / object from another entity / operation / object, and do not necessarily require or imply any such immediate relationship or order between these entities / operations / objects.

[0032] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0033] In medical laboratories, pipettes are used extensively. As one of the key pieces of equipment affecting the accuracy of sample results, pipettes need to be checked or calibrated regularly to ensure the accuracy of sample dispensing volume.

[0034] Currently, after checking or calibrating pipette 1, users record its status information in a table. Therefore, when a user wants to determine the status of a specific pipette 1, they need to consult the table, which is cumbersome. Furthermore, when there are many pipettes 1, using a table to record information is prone to errors or omissions, leading to inaccurate status information and potential quality risks.

[0035] Example 1

[0036] To address the cumbersome process of consulting tables to check the status of pipette 1 in existing technologies, and the potential for errors or omissions when using tables to record information, especially when dealing with a large number of pipettes 1, leading to inaccurate pipette 1 status information and quality risks, the following solutions are needed. Figure 1 As shown, the present invention provides a pipette management method, applied to a pipette management system, the pipette management system comprising: a server 3, a pipette 1, and a pipette rack 2, the method comprising:

[0037] Step 101: Server 3 obtains the device information of pipette 1 based on the identification code on the surface of pipette 1.

[0038] It is worth noting that an identification code is set on the outer shell of pipette 1, which can be a QR code or a barcode. Scanning the identification code can obtain the device information of pipette 1, such as model, bound laboratory number, pipette type, nominal value, etc. This information is pre-bound by scanning the identification code, and after binding, the above information can be obtained by scanning the identification code. Server 3 can scan the identification code on pipette 1 through an image acquisition device 23 set on the frame 21 of pipette 1. The image acquisition device 23 can be a camera. In a preferred embodiment, the image acquisition device 23 is set on the frame 21 after the pipette holder 22 that fixes pipette 1. When pipette 1 is fixed on the pipette holder 22, the image acquisition device 23 faces pipette 1 and reads the identification code on the outer shell of pipette 1, so that server 3 can obtain the device information of pipette 1.

[0039] Step 102: Server 3 obtains verification information, which includes verification items for device information.

[0040] It is worth noting that during the use of pipette 1, it needs to be checked or calibrated periodically, generally every 6 months and every 12 months. The check information includes information from both the check and calibration processes, such as the check items, calibration items, check time, check results, calibration time, and calibration results. After checking or calibrating pipette 1, staff will input the check information into server 3 and bind it to the corresponding identification code on pipette 1. After binding, the check information for that pipette 1 can be retrieved by scanning the identification code. Both the device information and check information for pipette 1 are stored in server 3, and a corresponding electronic information file is created for each pipette 1.

[0041] Step 103: Server 3 obtains the verification results based on the verification items and equipment information.

[0042] It is worth noting that after server 3 obtains the verification items, the corresponding verification time, and the verification results, it needs to determine which pipette 1 these written information belong to. At this time, server 3 obtains the device information of pipette 1 and combines the verification information and the device information to obtain the final verification result of pipette 1.

[0043] Step 104: Server 3 determines the verification status of pipette 1 based on the verification results.

[0044] It is worth noting that the verification results include the verification or calibration time, for example, the verification time is January 1, 2022. The verification results also include the condition of pipette 1 after verification. The verification status of pipette 1 is determined based on the verification or calibration time and the most recent time. The verification status includes normal status, pending verification status, and unverified status. For example, if the verification time of a pipette 1 is January 1, 2022, and the last time the identification code was scanned is May 1, 2022, five months have passed since the last verification, which is less than the six-month verification period. Therefore, the verification status of this pipette 1 is normal, meaning that this pipette 1 does not currently need verification and can be used directly. For example, if the verification date of pipette 1 is January 1, 2022, and the last time the identification code was scanned was May 28, 2022, 178 days have passed since the last verification. It is about to reach the 6-month (180-day) verification period. A preset time (e.g., 5 days) can be set. When the time remaining before the verification time is within the preset time, pipette 1 is in the pending verification state. Therefore, in this example, the verification status of pipette 1 is pending verification, which means that this pipette 1 needs to be verified in time. For example, if the verification date of pipette 1 is January 1, 2022, and the last scan of the identification code is June 25, 2022, 185 days have passed since the last verification. The verification period has exceeded 6 months (180 days). Therefore, pipette 1 is in an unverified state. Thus, in this example, the verification status of pipette 1 is unverified, which means that pipette 1 must be verified before it can continue to be used.

[0045] Step 105: Server 3 sends a verification prompt command to pipette 2 according to the verification status, and controls pipette 2 to send verification prompt information.

[0046] It is worth noting that after server 3 obtains the verification status of pipette 1, it will send a verification prompt command to pipette rack 2 based on the verification status of pipette 1. Specifically, it sends a verification prompt command to the status indicator light 24 on pipette rack 2. Upon receiving the verification prompt command, status indicator light 24 will emit light of the corresponding color and verification prompt information. For example, if pipette 1 is in a normal state, server 3 sends a normal state prompt command to status indicator light 24, controlling status indicator light 24 to emit light. The color of the light can represent the status of pipette 1; for example, green light for normal state, yellow light for pending verification state, and red light for unverified state. Therefore, the status of each pipette 1 can be intuitively seen based on the light emitted by status indicator light 24.

[0047] The aforementioned pipette management method involves affixing an identification code to the exterior of each pipette 1, recording its device information within the code. This device information can be obtained by scanning the code. After pipette 1 undergoes verification or calibration, the verification information for each pipette 1 is linked to its device information. Scanning the identification code again retrieves this verification information. Based on the verification and device information, the verification result for each pipette 1 is obtained, determining its verification status (e.g., normal, pending verification, or unverified). Once the status of each pipette 1 is determined, a verification prompt command is issued, triggering the relevant prompting device on the pipette rack 2 to issue a notification signal. This allows users to intuitively understand the status of each pipette 1 through the prompt signals, eliminating the need to consult a table and improving the user experience. Meanwhile, by uploading the calibration data and calibration parameters of pipette 1 to server 3, it can be accessed at any time when needed, which can reduce the risk of data loss and avoid quality problems caused by errors during manual statistics.

[0048] Example 2

[0049] Based on Example 1, such as Figure 2 As shown, this embodiment provides a pipette management method. The pipette 11 is also equipped with an inductive charging receiver. The pipette rack 22 includes a rack body 21, a pipette slot 22, an image acquisition device 23, a status indicator light 24, an inductive charging transmitter 25, and a gravity sensor 26.

[0050] The pipette slot 22, image acquisition device 23, status indicator light 24, and inductive charging transmitter 25 are all mounted on the frame 21, and the image acquisition device 23, status indicator light 24, inductive charging transmitter 25, and gravity sensor 26 are all electrically connected to the server 3.

[0051] One of the pipette slots 22 includes two parallel slots for fixing the pipette 1;

[0052] When the pipette 1 is fixed on the pipette slot 22, the pipette 1 will squeeze the gravity sensing device 26;

[0053] The image acquisition device 23 is disposed between the two slots. When the pipette 1 is fixed on the pipette slot 22, the image acquisition device 23 can acquire an image including the identification code on the pipette 1.

[0054] The status indicator light 24 is located on one side of the pipette slot 22;

[0055] The inductive charging transmitter 25 is disposed between the two slots. When the pipette 1 is fixed on the pipette slot 22, the pipette holder 2 charges the pipette 1 through the inductive charging transmitter 25 and the inductive charging receiver.

[0056] It is worth noting that the frame 21 is equipped with pipette slots 22, an image acquisition device 23, a status indicator light 24, an inductive charging transmitter 25, and a gravity sensor 26. The pipette slots 22 secure the pipette 1 and include two parallel slots that hold the pipette 1 in place. Each pipette slot 22 also has a gravity sensor 26, which can be a gravity button located in the middle of the slot or elsewhere. The gravity sensor 26 protrudes from the surface of the frame 21. When the pipette 1 is fixed in the slot, the pipette 1's shell will press against the gravity sensor 26, triggering it. The image acquisition device 23 is located on the frame 21 behind the pipette slots 22 where the pipette 1 is fixed. When the pipette 1 is fixed in the slot, the image acquisition device 23 faces the pipette 1 and reads the identification code on the pipette 1's shell, allowing the server 3 to obtain the device information of the pipette 1. A status indicator light 24 is located on one side of the pipette slot 22. The status indicator light 24 emits different colored lights according to the received instructions to indicate the status of the pipette 1. The pipette 1 includes a single-channel manual pipette 1, a multi-channel manual pipette 1, and an electronic continuous dispensing pipette. The electronic continuous dispensing pipette is a great tool in manual science, with continuous dispensing function, which can greatly improve the efficiency of laboratory work. However, a major drawback of the electronic continuous dispensing pipette is that it requires a long charging time, and the charging interface of the pipette 1 is easily damaged due to high usage frequency. Therefore, this embodiment uses an inductive charging device to charge the electronic continuous dispensing pipette. Specifically, the electronic continuous dispensing pipette, i.e., the pipette 1, is equipped with an inductive charging receiver, and an inductive charging transmitter 25 is located between the two slots. When the pipette 1 is fixed on the pipette slot 22, the pipette holder 2 charges the pipette 1 through the inductive charging transmitter 25 and the inductive charging receiver.

[0057] Example 3

[0058] like Figure 3 and Figure 4 As shown, based on Embodiments 1 and 2, in order to better charge the electronic continuous dispensing pipette, this embodiment provides a pipette management method, which further includes the following steps before obtaining the device information of the pipette 1 based on the identification code on the surface of the pipette 1:

[0059] Step 201: When the pipette 1 squeezes the gravity sensor 26, the gravity sensor 26 sends a pipette 1 return signal to the server 3.

[0060] Step 202: The server 3 receives the return signal of the pipette 1 and sends an image acquisition signal to the image acquisition device 23;

[0061] Step 203: The image acquisition device 23 acquires an image with the identification code based on the image acquisition signal, and sends the image to the server 3;

[0062] The method further includes:

[0063] Step 301: When the pipette 1 squeezes the gravity sensor 26, the gravity sensor 26 sends a pipette 1 return signal to the server 3.

[0064] Step 302: The server 3 receives the return signal of the pipette 1 and sends a first query command to the pipette 1;

[0065] Step 303: The pipette 1 receives the first query instruction, obtains the device information of the pipette 1, and sends the device information to the server 3;

[0066] Step 304: The server 3 determines whether the pipette 1 has an inductive charging receiver based on the device information;

[0067] Step 305: If so, the server 3 sends a charging signal to the inductive charging transmitter 25;

[0068] Step 306: The inductive charging transmitter 25 receives the charging signal to charge the pipette 1;

[0069] Step 307: The pipette 1 acquires the power information and sends the power information to the server 3;

[0070] Step 308: The server 3 determines whether the pipette 1 is fully charged based on the power information;

[0071] Step 309: If so, the server 3 sends a stop charging signal to the inductive charging transmitter 25;

[0072] Step 310: The inductive charging transmitter 25 receives the stop charging signal and stops charging the pipette 1.

[0073] It is worth noting that the specific steps by which server 3 obtains the device information of pipette 1 based on the identification code on the surface of pipette 1 are as follows: After the user finishes using pipette 1, he fixes pipette 1 on pipette holder 2. At this time, pipette 1 squeezes gravity sensor 26, and gravity sensor 26 sends a pipette 1 return signal to server 3; server 3 receives pipette 1 return signal and sends image acquisition signal to image acquisition device 23; image acquisition device 23 acquires image with identification code based on image acquisition signal and sends image to server 3; server 3 receives image with identification code and identifies identification code to obtain the corresponding device information of pipette 1.

[0074] Simultaneously, when pipette 1 squeezes the gravity sensor 26, server 3 needs to charge pipette 1 to ensure sufficient power for the next use. The specific steps are as follows: When pipette 1 squeezes the gravity sensor 26, the gravity sensor 26 sends a return signal to server 3; server 3 receives the return signal and sends a first query command to pipette 1; pipette 1 receives the first query command, obtains its device information, and sends the device information to server 3; server 3 determines whether pipette 1 has an inductive charging receiver based on the device information; if so, server 3 sends a charging signal to inductive charging transmitter 25; inductive charging transmitter 25 receives the charging signal and charges pipette 1; pipette 1 obtains its power information and sends it to server 3; server 3 determines whether pipette 1 is fully charged based on the power information; if so, server 3 sends a stop charging signal to inductive charging transmitter 25; inductive charging transmitter 25 receives the stop charging signal and stops charging pipette 1. When server 3 determines that pipette 1 does not have an inductive charging receiver based on the device information, it will not activate inductive charging transmitter 25.

[0075] In this embodiment, it is first determined whether the fixed pipette 1 is an electronic continuous dispensing device. If so, the inductive charging transmitter 25 is activated to charge the pipette 1. At the same time, it is also determined whether the pipette 1 is fully charged. Once fully charged, the charging is stopped, which saves energy and prevents damage to the pipette 1.

[0076] Example 4

[0077] Based on Embodiments 1 and 2, to more intuitively display the status of pipette 1, this embodiment provides a pipette management method. The server 3 sends a verification prompt command to the pipette rack 2 according to the verification status, controlling the pipette rack 2 to issue verification prompt information, including:

[0078] Server 3 obtains the verification status of pipette 1, which includes: normal status, pending verification status, and unverified status. The verification prompt instructions include prompting normal status, prompting pending verification status, and prompting unverified status.

[0079] When the verification status is normal, the server 3 sends a normal status prompt command to the status indicator 24, and controls the pipette 2 to send a normal status prompt signal.

[0080] When the verification status is pending verification, the server 3 sends a pending verification status prompt command to the status indicator 24, and controls the pipette 2 to send a pending verification status prompt signal;

[0081] When the verification status is unverified, the server 3 sends a prompt command to the status indicator 24 to indicate the unverified status, and controls the pipette 2 to issue an unverified status prompt signal;

[0082] Status indicator 24 receives the verification prompt command and emits light of the color corresponding to the verification prompt command.

[0083] It is worth noting that after obtaining the verification status of pipette 1, server 3 will send a verification prompt command to pipette rack 2 based on the verification status of pipette 1. Specifically, this is done by sending a verification prompt command to the status indicator light 24 on pipette rack 2. Upon receiving the verification prompt command, status indicator light 24 will emit light of the corresponding color and verification prompt information. For example, if pipette 1 is in a normal state, server 3 will send a normal state prompt command to status indicator light 24, controlling status indicator light 24 to emit light. The color of the light can represent the status of pipette 1; for example, green light for a normal state, yellow light for a state awaiting verification, and red light for a state not yet verified. Therefore, the status of each pipette 1 can be intuitively seen based on the light emitted by status indicator light 24. For example, if status indicator light 24 emits green light, it can be directly determined that the corresponding pipette 1 is in a normal state and can be used directly.

[0084] Example 5

[0085] The laboratory faces difficulties in tracing information about pipette 1, and some pipette 1s have even been lost because their whereabouts cannot be traced after being borrowed.

[0086] Based on Embodiments 1 and 2, in order to solve the problem of pipette 1 being difficult to retrieve after being borrowed, this embodiment provides a pipette management method. The pipette management system also includes a display panel, and the device information of the pipette 1 includes the laboratory number.

[0087] The method further includes:

[0088] When the pipette 1 squeezes the gravity sensor 26, the gravity sensor 26 sends a pipette 1 return signal to the server 3.

[0089] The server 3 receives the return signal of the pipette 1 and sends a second query command to the pipette 1;

[0090] The pipette 1 receives the second query instruction, obtains the laboratory number of the pipette 1, and sends the laboratory number of the pipette 1 to the server 3;

[0091] The server 3 receives the return signal of the pipette 1 and sends a third query command to the pipette rack 2;

[0092] The pipette 2 receives the third query command and obtains the laboratory number corresponding to the pipette 2;

[0093] Server 3 compares the laboratory number of pipette 1 with the laboratory number of pipette rack 2;

[0094] If there is a discrepancy, the server 3 sends a first abnormality alert command to the display panel that matches the laboratory number of the pipette 2;

[0095] The display panel with the same laboratory number as the pipette 2 receives the first abnormality prompt instruction and issues the first abnormality prompt information;

[0096] Furthermore, the server 3 sends a second abnormality alert command to the display panel that matches the laboratory number of the pipette 1;

[0097] The display panel, which corresponds to the laboratory number of the pipette 2, receives the second abnormality alert command and issues the second abnormality alert message.

[0098] It is worth noting that when pipette 1 is borrowed to other laboratories, for example, pipette 1 from laboratory A is borrowed to laboratory B for use, after use, staff can easily place pipette 1 directly onto pipette slot 22 in laboratory B. At this point, server 3 will identify which laboratory pipette 1 belongs to. If it finds that pipette 1 does not belong to that laboratory, it will issue a prompt message. The specific steps are as follows: pipette 1 squeezes the gravity sensor 26, and the gravity sensor 26 sends a return signal to server 3; server 3 receives the return signal and sends a second query command to pipette 1; pipette 1 receives the second query command, obtains the laboratory number of pipette 1 (the laboratory number of pipette 1 can be obtained through a query identification code), and sends the laboratory number of pipette 1 to server 3; server 3 receives the return signal of pipette 1 and sends a third query command to pipette rack 2; pipette rack 2 receives the third query command and obtains the laboratory number corresponding to pipette rack 2 (the laboratory number of pipette rack 2 is recorded in server 3, and server 3 can query it directly); server 3 compares the laboratory number of pipette 1 with the laboratory number of pipette rack 2; if they do not match, server 3 sends a message to the display surface that matches the laboratory number of pipette rack 2. The server sends a first abnormality alert command; the display panel with the same laboratory number as the pipette rack receives the first abnormality alert command and issues a first abnormality alert message (for example, after pipette 1 a from laboratory A is borrowed to laboratory B, when pipette 1 a is placed on pipette rack 2 in laboratory B, the server sends a first abnormality alert command to the display panel of laboratory B, and the display panel of laboratory B displays that pipette 1 a does not belong to laboratory B and needs to be returned to laboratory A); and the server sends a second abnormality alert command to the display panel with the same laboratory number as pipette 1; the display panel with the same laboratory number as pipette rack 2 receives the second abnormality alert command and issues a second abnormality alert message (for example, after pipette 1 a from laboratory A is borrowed to laboratory B, when pipette 1 a is placed on pipette rack 2 in laboratory B, the server sends a second abnormality alert command to the display panel of laboratory A, and the display panel of laboratory A displays that pipette 1 a is placed in laboratory B and needs to be retrieved from laboratory B).

[0099] This embodiment obtains the laboratory number of the pipette 1 on the pipette rack 2 and compares it with the laboratory number of the pipette rack 2 to determine whether the pipette 1 belongs to that laboratory. If not, a prompt message is issued to inform that the pipette 1 does not belong to that laboratory and needs to be returned as soon as possible. At the same time, the location of the borrowed pipette 1 in the laboratory with the same number as pipette 1 is also informed, which helps to solve the problem of pipette 1 being difficult to find after it has been borrowed.

[0100] Example 6

[0101] When there are many pipettes 1, there will be a large inconsistency in the usage rate of different pipettes 1. For example, some pipettes 1 may be used a lot, while others may be used very little.

[0102] Based on Examples 1 and 2, in order to balance the usage rate of each pipette 1, this example provides a pipette management method, which further includes:

[0103] The pipette 1 records and saves its own usage information, including the number of times it has been used.

[0104] The server 3 sends a fourth query command to all pipettes 1 in a laboratory;

[0105] The pipette 1 acquires its own usage information within a preset time period and sends the usage information to the server 3; the server 3 receives the usage information, sorts all pipettes 1 according to the number of uses, and generates a usage report for all pipettes 1.

[0106] The server 3 compares the number of times each pipette 1 is used with the preset number of times;

[0107] If the number of times the pipette 1 is used is greater than or equal to the preset number, the server 3 sends an overuse warning instruction to the status indicator 24 corresponding to the pipette holder 2 that fixes the pipette 1.

[0108] The status indicator 24 receives the excessive usage prompt instruction and issues an excessive usage prompt signal;

[0109] If the number of times the pipette 1 is used is less than the preset number, the server 3 sends a suggested usage prompt instruction to the status indicator 24 corresponding to the pipette holder 2 that fixes the pipette 1.

[0110] The status indicator 24 receives the suggested use prompt instruction and issues a suggested use prompt signal.

[0111] It is worth noting that pipette 1 or server 3 can record the usage information of pipette 1. Specifically, each time pipette 1 is removed, the gravity sensor button is released. At this time, server 3 sends usage information to pipette 1, indicating that pipette 1 has been used once. A preset time can also be added to more accurately determine the usage status of pipette 1. For example, if pipette 1 releases the gravity sensor button and is not returned to pipette holder 2 after a preset time (i.e., the gravity sensor button is not pressed), it is considered that pipette 1 has been used once. In this embodiment, server 3 collects the usage information of each pipette 1 at regular intervals, sorts all pipette 1 according to the number of times each pipette 1 has been used, and generates a usage report for all pipette 1. Staff can adjust the placement order of pipette 1 according to the usage report, for example, placing pipette 1 with low usage rate in an easily accessible position. At the same time, the server 3 will compare the number of times each pipette 1 has been used with the preset number of times. Based on the comparison result, the server will control the status indicator 24 to send a usage count reminder signal, which will intuitively remind the staff of the number of times each pipette 1 has been used and remind the staff to prioritize the use of pipettes 1 with low usage rates, thereby balancing the usage rates of each pipette 1.

[0112] Example 7

[0113] In existing laboratories, pipette racks 2 are usually arranged in a row to hold pipettes 1. When staff need to use a pipette 1, they take it from the slot with the pipette 1; when they don't need it, they put the pipette 1 back into an empty slot. The management is not standardized.

[0114] Based on Examples 1 and 2, in order to more intelligently assist staff in removing or placing pipette 1 and to make management more standardized, such as... Figure 5 As shown, this embodiment provides a pipette management method. The frame 21 is circular, and a rotating device is provided below the frame 21. The frame 21 is rotatably connected to the rotating device. A distance sensor and an RFID antenna are also provided on the frame 21. The distance sensor and the RFID antenna are both electrically connected to the server 3. An RFID tag is provided inside the pipette 1.

[0115] When the distance sensor detects that a user is approaching, it sends a first proximity signal to the server 3.

[0116] The server 3 receives the first proximity signal and sends a detection command to the RFID antenna;

[0117] The RFID antenna receives the detection command and detects whether an RFID tag is approaching. When an RFID tag is detected, it sends a second proximity signal to the server 3. When no RFID tag is detected, it sends a third proximity signal to the server 3.

[0118] When the server 3 receives the first proximity signal and the second proximity signal at the same time, the server 3 obtains the idle status of the pipette slot 22 and obtains a set of idle pipette slots 22 in an idle state;

[0119] The server 3 obtains the coordinates of each pipette slot 22 in the set of idle pipette slots 22 and calculates the rotation distance of each pipette slot 22 to the sampling position 211.

[0120] The server 3 selects the idle card position with the shortest rotation distance as the collection card position, and sends a first rotation command to the rotation device according to the rotation distance of the collection card position.

[0121] The rotating device receives the first rotating command and rotates by the corresponding angle, causing the collection card to rotate to the sampling position 211.

[0122] When the server 3 receives the first proximity signal and the third proximity signal, the server 3 obtains the idle status of the pipette slot 22 and obtains a set of pipette slots 22 that are in use and fixed and in normal use.

[0123] The server 3 obtains the coordinates of each pipette slot 22 in the set of pipette slots 22 and calculates the rotation distance of each pipette slot 22 to the sampling position 211.

[0124] The server 3 selects the card position with the smallest rotation distance as the card position for retrieval, and sends a second rotation command to the rotation device according to the rotation distance of the card position for retrieval.

[0125] The rotating device receives the second rotating command and rotates by the corresponding angle, causing the card slot to rotate to the sampling position 211.

[0126] It is worth noting that in this embodiment, the frame 21 of the pipette holder 2 is circular, and a rotating device is provided below the frame 21. The frame 21 is rotatably connected to the rotating device, which can drive the circular frame 21 to rotate. A distance sensor on the frame 21 can detect whether someone is approaching. An RFID antenna is also provided on the frame 21, and an RFID tag is installed inside the pipette 1. Therefore, the frame 21 can detect whether the pipette 1 is approaching via the RFID antenna and the RFID tag. When the server 3 detects a user approaching via the distance sensor, it will detect whether an RFID tag is approaching via the RFID antenna. If so, it means a user is approaching with the pipette 1 to put it back; if not, it means only the user is approaching to retrieve the pipette 1. After determining the user's purpose, it is necessary to meet the user's needs (placing or retrieving the pipette 1). Server 3 determines the user's needs based on the received proximity signal, then obtains the coordinates of the corresponding card position according to the user's needs, determines the card position with the smallest rotation distance that meets the user's needs, and then controls the rotating device to rotate so that the card position that meets the user's needs and has the smallest rotation distance rotates to the sampling position 211. The user can then remove the pipette 1 from the sampling position 211 or put the pipette 1 back into the sampling position 211 according to their own needs.

[0127] This embodiment uses a distance sensor, RFID antenna, and RFID tag to determine the user's needs (placing or retrieving pipette 1), and determines the position with the shortest rotation distance based on the user's needs. It then controls the rotation device to ensure that the position with the shortest rotation distance, satisfying the user's needs, rotates to the sample storage / retrieval position 211. This satisfies the user's requirements while minimizing the rotation distance of the pipette holder 2, reducing energy consumption. This more intelligently assists staff in retrieving or returning pipette 1, making management more standardized.

[0128] Example 8

[0129] To address the cumbersome process of consulting tables to check the status of pipette 1 in existing technologies, and the potential for errors or omissions when using tables to record information, especially when dealing with a large number of pipettes 1, leading to inaccurate pipette 1 status information and quality risks, the following solutions are needed. Figure 6 As shown, the present invention provides a pipette management system, which includes: a server 3, a pipette 1, and a pipette rack 2. The server 3 is used for:

[0130] Obtain device information of pipette 1 based on the identification code on the surface of pipette 1;

[0131] Obtain verification information, which includes verification items for equipment information;

[0132] The verification results are obtained based on the verification items and equipment information;

[0133] Determine the verification status of pipette 1 based on the verification results;

[0134] Based on the verification status, a verification prompt command is sent to the pipette 2, controlling the pipette 2 to issue verification prompt information.

[0135] The aforementioned pipette management system uses an identification code on the exterior of each pipette 1, which records the device information of each pipette 1. This device information can be obtained by scanning the identification code. After each pipette 1 is checked or calibrated, the check information is linked to the device information. Scanning the identification code of each pipette 1 retrieves this check information. Based on the check information and device information, the check result of each pipette 1 is obtained, determining its check status, such as normal, pending check, or unchecked. Once the status of each pipette 1 is known, a check prompt command is issued, prompting the relevant prompting device on the pipette rack 2 to issue a corresponding signal. This allows users to intuitively know the status of each pipette 1 through the prompt signals, eliminating the need to look up the status in a table and improving the user experience. Meanwhile, by uploading the calibration data and calibration parameters of pipette 1 to server 3, it can be accessed at any time when needed, which can reduce the risk of data loss and avoid quality problems caused by errors during manual statistics.

[0136] Example 9

[0137] Based on Embodiment 8, this embodiment provides a pipette management system, wherein the pipette 1 is further provided with an inductive charging receiver; the pipette rack 2 includes a frame 21, a pipette slot 22, an image acquisition device 23, a status indicator light 24, an inductive charging transmitter 25, and a gravity sensor 26.

[0138] The pipette slot 22, image acquisition device 23, status indicator light 24, and inductive charging transmitter 25 are all mounted on the frame 21, and the image acquisition device 23, status indicator light 24, inductive charging transmitter 25, and gravity sensor 26 are all electrically connected to the server 3.

[0139] One of the pipette slots 22 includes two parallel slots for fixing the pipette 1;

[0140] When the pipette 1 is fixed on the pipette slot 22, the pipette 1 will squeeze the gravity sensing device 26;

[0141] The image acquisition device 23 is disposed between the two slots. When the pipette 1 is fixed on the pipette slot 22, the image acquisition device 23 can acquire an image including the identification code on the pipette 1.

[0142] The status indicator light 24 is located on one side of the pipette slot 22;

[0143] The inductive charging transmitter 25 is disposed between the two slots. When the pipette 1 is fixed on the pipette slot 22, the pipette holder 2 charges the pipette 1 through the inductive charging transmitter 25 and the inductive charging receiver.

[0144] Example 10

[0145] Based on embodiments 8 and 9, this embodiment provides a pipette management system in which the gravity sensor 26 is used to send a pipette 1 return signal to the server 3 when the pipette 1 squeezes the gravity sensor 26.

[0146] The server 3 is used to receive the return signal of the pipette 1 and send the image acquisition signal to the image acquisition device 23;

[0147] The image acquisition device 23 is used to acquire an image with the identification code based on the image acquisition signal, and send the image to the server 3;

[0148] When the pipette 1 squeezes the gravity sensor 26, the gravity sensor 26 is used to send a return signal of the pipette 1 to the server 3.

[0149] The server 3 is used to receive the return signal of the pipette 1 and send a first query command to the pipette 1;

[0150] The pipette 1 is used to receive the first query instruction, obtain the device information of the pipette 1, and send the device information to the server 3;

[0151] The server 3 is used to determine whether the pipette 1 has an inductive charging receiver based on the device information.

[0152] If so, the server 3 is used to send a charging signal to the inductive charging transmitter 25;

[0153] The inductive charging transmitter 25 is used to receive the charging signal to charge the pipette 1;

[0154] The pipette 1 is used to acquire power information and send the power information to the server 3;

[0155] The server 3 is used to determine whether the pipette 1 is fully charged based on the power information.

[0156] If so, the server 3 is used to send a stop charging signal to the inductive charging transmitter 25;

[0157] The inductive charging transmitter 25 is used to receive the stop charging signal and stop charging the pipette 1.

[0158] Example 11

[0159] Based on Examples 8 and 9, this example provides a pipette management system.

[0160] Server 3 is used for:

[0161] The verification status of the pipette 1 is obtained, including: normal status, pending verification status, and unverified status. The verification prompt instructions include prompting normal status, prompting pending verification status, and prompting unverified status.

[0162] When the verification status is normal, the server 3 sends a normal status prompt command to the status indicator 24, and controls the pipette 2 to send a normal status prompt signal.

[0163] When the verification status is pending verification, the server 3 sends a pending verification status prompt command to the status indicator 24, and controls the pipette 2 to send a pending verification status prompt signal;

[0164] When the verification status is unverified, the server 3 sends a prompt command to the status indicator 24 to indicate the unverified status, and controls the pipette 2 to issue an unverified status prompt signal;

[0165] Status indicator light 24 is used for:

[0166] Upon receiving the verification prompt instruction, emit light of the color corresponding to the verification prompt instruction.

[0167] Example 12

[0168] Based on embodiments 8 and 9, this embodiment provides a pipette management system, which further includes a display panel, and the device information of the pipette 1 includes a laboratory number;

[0169] When the pipette 1 squeezes the gravity sensor 26, the gravity sensor 26 is used to send a return signal of the pipette 1 to the server 3.

[0170] The server 3 is used to receive the return signal of the pipette 1 and send a second query command to the pipette 1;

[0171] The pipette 1 is used to receive the second query instruction, obtain the laboratory number of the pipette 1, and send the laboratory number of the pipette 1 to the server 3;

[0172] The server 3 is used to receive the return signal of the pipette 1 and send a third query command to the pipette rack 2;

[0173] The pipette 2 is used to receive the third query command and obtain the laboratory number corresponding to the pipette 2;

[0174] Server 3 is used to compare the laboratory number of pipette 1 and the laboratory number of pipette rack 2;

[0175] If there is a discrepancy, the server 3 is used to send a first abnormality alert instruction to the display panel that matches the laboratory number of the pipette 2;

[0176] The display panel, which corresponds to the laboratory number of the pipette 2, is used to receive the first abnormality alert instruction and issue the first abnormality alert information;

[0177] Furthermore, the server 3 is used to send a second abnormality alert command to the display panel that matches the laboratory number of the pipette 1;

[0178] The display panel, which corresponds to the laboratory number of the pipette 2, is used to receive the second abnormality alert instruction and issue the second abnormality alert information.

[0179] Example 13

[0180] Based on embodiments 8 and 9, this embodiment provides a pipette management system, wherein the pipette 1 records and saves its own usage information, including the number of times it has been used;

[0181] The server 3 is used to send a fourth query command to all pipettes 1 in a laboratory;

[0182] The pipette 1 is used to obtain its own usage information within a preset time and send the usage information to the server 3;

[0183] The server 3 is used to receive the usage information, sort all pipettes 1 according to the number of times they are used, and generate a usage report for all pipettes 1.

[0184] The server 3 is used to compare the number of times each pipette 1 is used with the preset number of times;

[0185] If the number of times the pipette 1 is used is greater than or equal to the preset number of times, the server 3 sends an overuse prompt instruction to the status indicator 24 corresponding to the pipette holder 2 that fixes the pipette 1;

[0186] The status indicator light 24 is used to receive the excessive usage prompt instruction and issue an excessive usage prompt signal;

[0187] If the number of times the pipette 1 is used is less than the preset number, the server 3 sends a suggested usage prompt instruction to the status indicator 24 corresponding to the pipette holder 2 that fixes the pipette 1.

[0188] The status indicator light 24 is used to receive the suggested usage prompt instruction and issue a suggested usage prompt signal.

[0189] Example 14

[0190] Based on embodiments 8 and 9, this embodiment provides a pipette management system. The frame 21 is circular, and a rotating device is provided below the frame 21. The frame 21 is rotatably connected to the rotating device. A distance sensor and an RFID antenna are also provided on the frame 21. The distance sensor and the RFID antenna are both electrically connected to the server 3. An RFID tag is provided inside the pipette 1.

[0191] When the distance sensor detects that a user is approaching, the distance sensor is used to send a first proximity signal to the server 3;

[0192] The server 3 is used to receive the first proximity signal and send a detection command to the RFID antenna;

[0193] The RFID antenna is used to receive the detection command and detect whether an RFID tag is approaching. When an RFID tag is detected approaching, a second proximity signal is sent to the server 3. When no RFID tag is detected approaching, a third proximity signal is sent to the server 3.

[0194] When the server 3 receives the first proximity signal and the second proximity signal at the same time, the server 3 is used to obtain the idle status of the pipette slot 22 and obtain a set of idle pipette slots 22 in an idle state;

[0195] The server 3 is used to obtain the coordinates of each pipette slot 22 in the set of idle pipette slots 22, and calculate the rotation distance of each pipette slot 22 to the sampling position 211.

[0196] The server 3 is used to select the idle card position with the shortest rotation distance as the collection card position, and sends a first rotation command to the rotation device according to the rotation distance of the collection card position.

[0197] The rotating device is used to receive the first rotating command and rotate the corresponding angle so that the collection card position is rotated to the sampling position 211.

[0198] When the server 3 receives the first proximity signal and the third proximity signal, the server 3 is used to obtain the idle status of the pipette slot 22 and obtain a set of pipette slots 22 that are in use and fixed and in normal use.

[0199] The server 3 is used to obtain the coordinates of each pipette slot 22 in the set of pipette slots 22 and calculate the rotation distance of each pipette slot 22 to the sampling position 211.

[0200] The server 3 is used to select the card position with the smallest rotation distance as the card position for taking out, and sends a second rotation command to the rotating device according to the rotation distance of the card position for taking out.

[0201] The rotating device is used to receive the second rotating command and rotate the corresponding angle so that the card slot is rotated to the sampling position 211.

[0202] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments described above. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), RAMbus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and RAMbus dynamic RAM (RDRAM), etc.

[0203] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0204] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A pipette management method, characterized in that, The method is applied to a pipette management system, which includes a server, pipettes, and pipette racks. Obtain the device information of the pipette based on the identification code on the pipette's exterior; Obtain verification information, which includes verification items for equipment information; The verification results are obtained based on the verification items and equipment information; The verification status of the pipette is determined based on the verification results; Based on the verification status, a verification prompt command is sent to the pipette, and the pipette is controlled to issue a verification prompt message. The pipette is also equipped with an inductive charging receiver; the pipette rack includes a frame, a pipette holder, an image acquisition device, a status indicator light, an inductive charging transmitter, and a gravity sensor. The pipette holder, image acquisition device, status indicator light, and inductive charging transmitter are all mounted on the frame, and the image acquisition device, status indicator light, inductive charging transmitter, and gravity sensor are all electrically connected to the server. One of the pipette holders includes two parallel slots for securing the pipette; When the pipette is fixed in the pipette holder, the pipette will squeeze the gravity sensing device; The image acquisition device is located between two slots. When the pipette is fixed in the pipette slot, the image acquisition device can acquire an image including the identification code on the pipette. The status indicator light is located on one side of the pipette slot; The inductive charging transmitter is located between the two slots. When the pipette is fixed in the pipette slot, the pipette holder charges the pipette through the inductive charging transmitter and the inductive charging receiver.

2. The pipette management method as described in claim 1, characterized in that, Before obtaining the device information of the pipette based on the identification code on the pipette's exterior, the method further includes: When the pipette squeezes the gravity sensor, the gravity sensor sends a pipette return signal to the server. The server receives the pipette return signal and sends an image acquisition signal to the image acquisition device; The image acquisition device acquires an image with the identification code based on the image acquisition signal, and sends the image to the server; The method further includes: When the pipette squeezes the gravity sensor, the gravity sensor sends a pipette return signal to the server. The server receives the pipette return signal and sends a first query command to the pipette; The pipette receives the first query instruction, obtains the device information of the pipette, and sends the device information to the server; The server determines whether the pipette has an inductive charging receiver based on the device information. If so, the server sends a charging signal to the inductive charging transmitter; The inductive charging transmitter receives the charging signal to charge the pipette; The pipette acquires power information and sends the power information to the server; The server determines whether the pipette is fully charged based on the power information. If so, the server sends a stop charging signal to the inductive charging transmitter; The inductive charging transmitter receives the stop charging signal and stops charging the pipette.

3. The pipette management method as described in claim 1, characterized in that, The server sends a verification prompt command to the pipette based on the verification status, and controls the pipette to send verification prompt information, including: The server obtains the verification status of the pipette, which includes: normal status, pending verification status, and unverified status. The verification prompt instructions include prompts for normal status, prompts for pending verification status, and prompts for unverified status. When the verification status is normal, the server sends a normal status prompt command to the status indicator light and controls the pipette to send a normal status prompt signal; When the verification status is pending verification, the server sends a pending verification status prompt command to the status indicator light, and controls the pipette to send a pending verification status prompt signal; When the verification status is unverified, the server sends a prompt command to the status indicator light to indicate the unverified status, and controls the pipette to issue an unverified status prompt signal; The status indicator light receives the verification prompt command and emits light of the color corresponding to the verification prompt command.

4. The pipette management method as described in claim 1, characterized in that, The pipette management system also includes a display panel, and the device information of the pipette includes the laboratory number; The method further includes: When the pipette squeezes the gravity sensor, the gravity sensor sends a pipette return signal to the server. The server receives the pipette return signal and sends a second query command to the pipette; The pipette receives the second query command, obtains the pipette's laboratory number, and sends the pipette's laboratory number to the server; The server receives the pipette return signal and sends a third query command to the pipette holder; The pipette receives the third query command and obtains the laboratory number corresponding to the pipette; The server compares the laboratory number of the pipette with the laboratory number of the pipette rack; If there is a discrepancy, the server sends a first anomaly alert command to the display panel that matches the laboratory number of the pipette; The display panel, which corresponds to the laboratory number of the pipette, receives the first abnormality alert instruction and issues the first abnormality alert message; Furthermore, the server sends a second abnormality alert command to the display panel that matches the laboratory number of the pipette; The display panel, which corresponds to the laboratory number of the pipette, receives the second abnormality alert command and issues the second abnormality alert message.

5. The pipette management method as described in claim 1, characterized in that, The method further includes: The pipette records and saves its own usage information, including the number of times it has been used. The server sends a fourth query command to all pipettes in a laboratory. The pipette acquires its own usage information within a preset time and sends the usage information to the server. The server receives the usage information, sorts all pipettes by usage count according to the number of uses, and generates a usage report for all pipettes. The server compares the number of times each pipette has been used with a preset number of uses. If the number of times the pipette is used is greater than or equal to the preset number, the server sends an overuse warning instruction to the status indicator light corresponding to the pipette holder that holds the pipette. The status indicator light receives the excessive usage prompt instruction and issues an excessive usage prompt signal; If the number of times the pipette is used is less than the preset number, the server sends a usage suggestion instruction to the status indicator light corresponding to the pipette holder that holds the pipette. The status indicator light receives the suggested usage prompt instruction and issues a suggested usage prompt signal.

6. The pipette management method as described in claim 1, characterized in that, The frame is circular, and a rotating device is provided below the frame. The frame is rotatably connected to the rotating device. A distance sensor and an RFID antenna are also provided on the frame. Both the distance sensor and the RFID antenna are electrically connected to the server. An RFID tag is provided inside the pipette. When the distance sensor detects that a user is approaching, it sends a first proximity signal to the server; The server receives the first proximity signal and sends a detection command to the RFID antenna; The RFID antenna receives the detection command and detects whether an RFID tag is approaching. When an RFID tag is detected, it sends a second proximity signal to the server. When no RFID tag is detected, it sends a third proximity signal to the server. When the server receives both the first proximity signal and the second proximity signal simultaneously, the server obtains the idle status of the pipette slots and obtains a set of idle pipette slots in an idle state. The server obtains the coordinates of each pipette slot in the set of idle pipette slots and calculates the rotation distance of each pipette slot to the sampling position. The server selects the idle card slot with the shortest rotation distance as the collection card slot, and sends a first rotation command to the rotation device according to the rotation distance of the collection card slot. The rotating device receives the first rotating command and rotates by the corresponding angle, so that the collection card position rotates to the sampling position; When the server receives the first proximity signal and the third proximity signal, the server obtains the idle status of the pipette slots and obtains a set of pipette slots that are in use and fixed and in normal use. The server obtains the coordinates of each pipette slot in the set of pipette slots and calculates the rotation distance of each pipette slot to the sampling position. The server selects the card position with the smallest rotation distance as the card position for retrieval, and sends a second rotation command to the rotation device according to the rotation distance of the card position for retrieval. The rotating device receives the second rotating command and rotates by the corresponding angle, causing the card slot to rotate to the sampling position.

7. A pipette management system, characterized in that, For use in applying the pipette management method according to any one of claims 1 to 6, the pipette management system comprises: a server, pipettes, and pipette racks, wherein the server is used for: Obtain the device information of the pipette based on the identification code on the pipette's exterior; Obtain verification information, which includes verification items for equipment information; The verification results are obtained based on the verification items and equipment information; The verification status of the pipette is determined based on the verification results; Based on the verification status, a verification prompt command is sent to the pipette, and the pipette is controlled to issue a verification prompt message.

8. The pipette management system as described in claim 7, characterized in that, The pipette is also equipped with an inductive charging receiver; the pipette rack includes a frame, a pipette holder, an image acquisition device, a status indicator light, an inductive charging transmitter, and a gravity sensor. The pipette holder, image acquisition device, status indicator light, and inductive charging transmitter are all mounted on the frame, and the image acquisition device, status indicator light, inductive charging transmitter, and gravity sensor are all electrically connected to the server. One of the pipette holders includes two parallel slots for securing the pipette; When the pipette is fixed in the pipette holder, the pipette will squeeze the gravity sensing device; The image acquisition device is located between two slots. When the pipette is fixed in the pipette slot, the image acquisition device can acquire an image including the identification code on the pipette. The status indicator light is located on one side of the pipette slot; The inductive charging transmitter is located between the two slots. When the pipette is fixed in the pipette slot, the pipette holder charges the pipette through the inductive charging transmitter and the inductive charging receiver.

9. The pipette management system as described in claim 8, characterized in that, The server is used for: The verification status of the pipette is obtained, including: normal status, pending verification status, and unverified status. The verification prompt instructions include prompts for normal status, pending verification status, and unverified status. When the verification status is normal, the server sends a normal status prompt command to the status indicator light and controls the pipette to send a normal status prompt signal; When the verification status is pending verification, the server sends a pending verification status prompt command to the status indicator light, and controls the pipette to send a pending verification status prompt signal; When the verification status is unverified, the server sends a prompt command to the status indicator light to indicate the unverified status, and controls the pipette to issue an unverified status prompt signal; Status indicator lights are used for: Upon receiving the verification prompt instruction, emit light of the color corresponding to the verification prompt instruction.

Images