A method for early warning and identification of abnormal jump number of a fuel dispenser gun

Abstract

This invention discloses a method for early warning and identification of abnormal fuel dispenser nozzle count jumps, comprising: after the fuel dispenser solenoid valve is opened, acquiring first pulse information generated by the fuel dispenser within a first brief judgment period, second pulse information generated by the fuel dispenser within a second continuous judgment period, and the flow rate of the fuel dispenser per second via the Internet of Things; the second continuous judgment period is longer than the first brief judgment period; determining whether the fuel dispenser has a count jump fault based on the first pulse information, the second pulse information, and the flow rate, and determining the fault type of the count jump fault; generating early warning information based on the fault type after the fuel dispenser count jump fault occurs; generating alarm information when the early warning information meets specified conditions, and reporting the alarm information to the operation and maintenance platform for processing. This method achieves automated detection and early warning of fuel dispenser count jump faults through logical judgment, improving equipment stability and reliability from a technical prevention perspective and reducing risks.

Description

Technical Field

[0001] This invention relates to the field of fuel dispenser technology, and in particular to a method for early warning and identification of abnormal fuel dispenser nozzle lifting counts. Background Technology

[0002] Malfunctions in the fuel dispenser itself or related equipment can cause abnormal fuel nozzle readings. These can occur during the dispensing process (when lifting the nozzle) or after non-quota dispensing has ended but before the nozzle is reattached. Abnormal fuel nozzle readings refer to situations where, during the dispensing operation, the display immediately shows the quantity and amount of fuel dispensed, even before the main valve is turned on, or the dispenser continues to read the fuel number after refueling and the nozzle is reattached. In most cases, if abnormal readings occur shortly after dispensing, observing the sight glass will reveal either an insufficient or no fuel level.

[0003] Although the main reason for gas pumps displaying incorrect readings is inadequate routine maintenance of equipment and facilities, this phenomenon can easily cause customers to suspect and be dissatisfied with the readings even before the pump is started, leading to complaints. If not handled promptly, the issue can spread rapidly through WeChat, the internet, newspapers, and other media, generating public opinion and severely impacting the image and reputation of gas station companies, even causing significant economic losses. Therefore, gas station managers and operators need to pay close attention to this problem.

[0004] Existing methods for detecting whether fuel dispenser equipment is experiencing a faulty flow rate require manual inspection of the display screen or oil sight glass. This method cannot directly and quickly determine the specific fault type and requires further testing over time. There is also no systematic fault detection method available. Summary of the Invention

[0005] To overcome the problems existing in related technologies, the present invention provides a method for early warning and identification of abnormal nozzle lifting counts in refueling machines, thereby solving the defects in related technologies.

[0006] According to a first aspect of the present invention, a method for identifying abnormal nozzle jump counts on a refueling machine is provided, the method comprising:

[0007] After the fuel nozzle solenoid valve is opened, the first pulse information generated by the fuel nozzle in the first short judgment period, the second pulse information generated by the fuel nozzle in the second continuous judgment period, and the flow rate of the fuel nozzle per second are obtained through the Internet of Things; the second continuous judgment period is longer than the first short judgment period.

[0008] Based on the first pulse information, the second pulse information, and the flow rate, it is determined whether the refueling nozzle has a jump count fault, and the fault type to which the jump count fault belongs is determined; the jump count fault is a nozzle lift jump count fault or a nozzle jump count fault.

[0009] After the fuel nozzle experiences the aforementioned fault in the number of clicks, a warning message is generated based on the fault type.

[0010] When the warning information meets the specified conditions, an alarm information is generated and reported to the operation and maintenance platform for processing.

[0011] Preferably, the first short-term judgment period is from the 0th second to the 1.5th second after the fuel nozzle opens the solenoid valve, and the second continuous judgment period is from the 0th second to the 9.5th second after the fuel nozzle opens the solenoid valve.

[0012] Preferably, the step of determining whether the refueling nozzle has a countdown fault based on the first pulse information, the second pulse information, and the flow rate, and determining the fault type to which the countdown fault belongs, includes:

[0013] When the first pulse information indicates that the fuel nozzle generates a pulse within the first short judgment period, and the second pulse information indicates that the fuel nozzle does not generate a continuous pulse within the second continuous judgment period, it is determined that the fuel nozzle has a fault of skipping the nozzle.

[0014] The fault type of the nozzle jump failure is determined based on the number of pulses generated by the refueling nozzle in the second pulse information.

[0015] Preferably, determining the fault type of the nozzle jump count fault based on the number of pulses generated by the refueling nozzle in the second pulse information includes:

[0016] If the number of pulses generated by the refueling nozzle in the second pulse information does not exceed 9, then the fault type of the nozzle jump count fault is determined to be the first type of jump count fault.

[0017] If the number of pulses generated by the refueling nozzle in the second pulse information exceeds 9, then the fault type of the nozzle jump count fault is determined to be the second type of jump count fault.

[0018] Preferably, the step of determining whether the refueling nozzle has a countdown fault based on the first pulse information, the second pulse information, and the flow rate, and determining the fault type to which the countdown fault belongs, includes:

[0019] When the first pulse information indicates that the fuel nozzle generates a pulse during the first short judgment period, and the second pulse information indicates that the fuel nozzle generates a continuous pulse during the second continuous judgment period, then the number of pulses generated by the fuel nozzle in the second pulse information is used to determine whether the fuel nozzle has a jump count fault, and the fault type to which the jump count fault belongs is determined.

[0020] Preferably, the step of determining whether the fuel nozzle has a pulse count failure based on the number of pulses generated by the fuel nozzle in the second pulse information, and determining the fault type to which the pulse count failure belongs, includes:

[0021] If the number of pulses generated by the refueling nozzle in the second pulse information is less than 200, it is determined that the refueling nozzle has a nozzle lift-off fault, and the fault type of the nozzle lift-off fault is determined to be a third type of fault.

[0022] Preferably, the step of determining whether the refueling nozzle has a countdown fault based on the first pulse information, the second pulse information, and the flow rate, and determining the fault type to which the countdown fault belongs, includes:

[0023] When the flow rate of the refueling nozzle drops below 5L / min, the flow rate of the refueling nozzle for the next 9 consecutive seconds is obtained;

[0024] If the flow rate of the refueling nozzle is greater than 0 L / min and less than 5 L / min for the next 9 consecutive seconds, it is determined that the refueling nozzle has a nozzle skipping fault, and the fault type of the nozzle skipping fault is determined to be the fourth type of skipping fault.

[0025] Preferably, the step of generating alarm information after the early warning information reaches a specified condition and reporting the alarm information to the operation and maintenance platform for processing includes:

[0026] When a single refueling nozzle simultaneously collects warning information for both nozzle lifting failure and nozzle disconnection failure, a first alarm is generated and reported to the maintenance platform for emergency repair.

[0027] When a single refueling nozzle collects warning information for three consecutive shifts, a second alarm is generated and reported to the maintenance platform for a second emergency repair.

[0028] Preferably, the step of generating alarm information after the warning information reaches a specified condition and reporting the alarm information to the operation and maintenance platform for processing further includes:

[0029] Simultaneously with generating the alarm information, a lock command for the refueling nozzle is sent to the refueling equipment, so that upon receiving the lock command, the refueling equipment locks the refueling nozzle without entering a specified unlock password.

[0030] According to a second aspect of the present invention, a pre-warning and identification device for abnormal nozzle counts on a fuel dispenser is provided. The device is connected to the fuel dispenser nozzle via an Internet of Things (IoT) and comprises:

[0031] The data acquisition module is used to acquire, via the Internet of Things, the first pulse information generated by the fuel nozzle within a first short judgment period, the second pulse information generated by the fuel nozzle within a second continuous judgment period, and the flow rate of the fuel nozzle per second after the fuel nozzle solenoid valve is opened; the second continuous judgment period is longer than the first short judgment period.

[0032] The detection module is used to determine whether the refueling nozzle has a jump count fault based on the first pulse information, the second pulse information, and the flow rate, and to determine the fault type to which the jump count fault belongs; the jump count fault is a nozzle lift jump count fault or a nozzle jump count fault.

[0033] The early warning module is used to generate early warning information based on the fault type after the fuel nozzle experiences the fault in the number of clicks.

[0034] The alarm module is used to generate alarm information when the warning information reaches the specified conditions, and to report the alarm information to the operation and maintenance platform for processing.

[0035] This invention discloses a method for early warning and identification of abnormal fuel dispenser nozzle lifting. Through reasonable logical judgment, it realizes the automated detection of fuel dispenser nozzle lifting faults. Based on the operating status of the fuel dispenser, including the collected first pulse information, second pulse information, and the flow rate per second of the fuel nozzle, it can systematically determine whether a nozzle lifting fault exists and the specific type of the fault, and issue corresponding early warnings. This significantly improves the stability and reliability of the equipment from a technical prevention perspective, and through system early warning and proactive prevention, minimizes the risks caused by nozzle lifting faults.

[0036] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the invention. Attached Figure Description

[0037] Figure 1 This is a flowchart illustrating a method for early warning and identification of abnormal nozzle lifting counts on a fuel dispenser, according to an embodiment of the present invention.

[0038] Figure 2 This is a flowchart illustrating the judgment logic for a first type and a second type of hop count fault according to an embodiment of the present invention.

[0039] Figure 3 This is a flowchart illustrating the judgment logic of a third type of hop count fault according to an embodiment of the present invention.

[0040] Figure 4 This is a flowchart illustrating the judgment logic for a gun-raising jump count fault according to an embodiment of the present invention.

[0041] Figure 5 This is a flowchart illustrating the judgment logic of a fourth type of hop count fault according to an embodiment of the present invention.

[0042] Figure 6 This is a flowchart illustrating the logic for determining the number of clicks during a click fault according to an embodiment of the present invention.

[0043] Figure 7 This is a schematic diagram of the structure of a fuel dispenser nozzle abnormal jump count warning and identification device according to an embodiment of the present invention.

[0044] Figure 8 This is a schematic diagram of the hardware structure of a computing device according to an embodiment of the present invention. Detailed Implementation

[0045] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

[0046] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. The singular forms “a,” “the,” and “the” used in this invention and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items.

[0047] It should be understood that although the terms first, second, third, etc., may be used in this invention to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of this invention, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

[0048] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments.

[0049] like Figure 1 As shown, Figure 1 This is a flowchart illustrating a method for identifying abnormal nozzle lift-off counts on a fuel dispenser according to an embodiment of the present invention, comprising the following steps:

[0050] Step S101: After the fuel nozzle solenoid valve is opened, the first pulse information generated by the fuel nozzle in the first short judgment period, the second pulse information generated by the fuel nozzle in the second continuous judgment period, and the flow rate of the fuel nozzle per second are obtained through the Internet of Things; the second continuous judgment period is longer than the first short judgment period.

[0051] Step S102: Based on the first pulse information, the second pulse information, and the flow rate, determine whether the refueling nozzle has a jump count fault, and determine the fault type to which the jump count fault belongs; wherein, the jump count fault is a nozzle lift jump count fault or a nozzle jump count fault.

[0052] Step S103: After the fuel nozzle experiences a fault in its number of ticks, generate a warning message based on the fault type.

[0053] Step S104: When the warning information meets the specified conditions, an alarm information is generated and reported to the operation and maintenance platform for processing.

[0054] In step S101, the device can be connected to the refueling equipment and refueling nozzle via the Internet of Things to obtain real-time data such as pulse generation and flow rate of the refueling nozzle during the refueling process, and then perform automated fault detection and analysis based on this data.

[0055] Specifically, once the operator picks up the nozzle and completes the IC card (Integrated Circuit Card) authorization, the fuel dispenser display screen will indicate that refueling is in progress, thus starting the refueling process.

[0056] Specifically, the display screen of a refueling device usually starts counting from 0.1L. Therefore, when refueling, the first 9 pulses (0.09L) of a transaction will not be displayed on the display screen. That is, even if oil is dispensed before 0.09L, the display screen will not show it. This part of the oil that is not displayed is called the pulse hidden amount.

[0057] Specifically, in order to reduce the water hammer effect during refueling and lower the incidence of nozzle jumps, when refueling, it is generally set that only the small valve of the solenoid valve is opened for the first 0.15L of the transaction, at which time the flow rate is about 3 pulses / second. After refueling to 0.15L (about 5 seconds), the large valve of the solenoid valve is opened to restore the flow rate to normal (30L-40L / Min).

[0058] Since abnormal data flow and other data jump faults often occur during the nozzle lifting stage, the pulse information generated by the fuel nozzle during nozzle lifting can be collected to determine whether a data jump fault occurs during the nozzle lifting stage.

[0059] Specifically, the count failure during the gun-raising phase can generally be divided into short-term gun-raising count failure and continuous gun-raising count failure.

[0060] Specifically, if the solenoid valve generates a pulse after opening, but it ends after a few seconds and the number of pulses is inconsistent, this situation is called a transient nozzle lift-up pulse count failure. Before the fuel nozzle is inserted into the fuel tank and refueling begins, there are two possibilities: First, if the number of pulses does not exceed the hidden pulse value, this situation, although it can be identified by IoT software, is meaningless and can be ignored, but can also be used as a warning reference; Second, if the number of pulses exceeds the hidden pulse value, the display screen will show the fuel level, which can be observed visually and identified by IoT software. The causes of transient nozzle lift-up pulse count failures are mostly due to the submersible pump not maintaining pressure due to prolonged periods without refueling (or a malfunctioning check valve), expansion of the hose (the amount of expansion is related to the hose length, hardness, etc.), and air in the pipeline due to temperature differences.

[0061] Specifically, if there is a continuous pulse count when the nozzle is lifted, the solenoid valve will open and continuously generate pulses. Once this pulse count exceeds the hidden pulse threshold (0.09L), the display will show a slow, continuous ticking of numbers. This is called a continuous nozzle lifting pulse count fault. Two scenarios can occur: First, if the nozzle is already in the tank and refueling has begun before the pulse count reaches the hidden pulse threshold, this is not visible to the naked eye but can be detected by IoT software. Second, if the pulse count exceeds the hidden pulse threshold before refueling begins, this is detectable by both IoT software and the naked eye. The main cause of continuous nozzle lifting pulse count faults is equipment malfunction, such as cross-contamination between the vapor recovery oil and gas lines, or leakage from the flow meter outlet to the nozzle tip.

[0062] Specifically, when the refueling nozzle shuts off normally, theoretically no pulses should continue to be generated and the flow rate should be 0. However, if there is a fault in the equipment and a pulse count occurs, although the refueling nozzle is closed after shutting off, there is still oil flowing inside. This is manifested as the refueling equipment display screen continuing to display numbers. This situation is called a shut-off pulse count fault.

[0063] Both the firing pin jump count fault (including brief and continuous firing pin jump count faults) and the firing pin jump count fault can cause abnormal data display, leading to problems. Therefore, it is necessary to monitor and detect both the firing pin jump count fault (including brief and continuous firing pin jump count faults) and the firing pin jump count fault, so as to provide timely warnings and proactive prevention and control, thereby improving the stability and reliability of the equipment and reducing the risks that jump count faults may cause.

[0064] Specifically, to detect and distinguish between transient and continuous nozzle-flickering faults in nozzle-flickering failures, in step S101, the first pulse information generated by the fuel nozzle during a first transient judgment period and the second pulse information generated by the fuel nozzle during a second continuous judgment period can be collected respectively. Based on the first and second pulse information, it can be determined whether the fuel nozzle has a transient or continuous nozzle-flickering fault. Specifically, the first transient judgment period is the first cycle for determining whether a pulse appears immediately after the solenoid valve opens. By collecting the first pulse information of the fuel nozzle during the first transient judgment period, it can be determined whether the fuel nozzle may have a nozzle-flickering fault. The second continuous judgment period is a judgment period for determining whether a pulse appears continuously within several seconds after the solenoid valve opens. By collecting the second pulse information of the fuel nozzle during the second continuous judgment period, it can be determined whether the fuel nozzle may have a transient or continuous nozzle-flickering fault. Specifically, the second continuous judgment period is greater than and includes the first transient judgment period. Specifically, the first pulse information collected during the first brief judgment period can be whether the refueling nozzle generates a pulse during the first brief judgment period, and the number of pulses generated; while the second pulse information collected during the second continuous judgment period can be whether the refueling nozzle continuously generates a pulse during the second continuous judgment period, and the number of pulses generated.

[0065] Specifically, although the valve opens immediately after the nozzle is lifted and IC card authorization is completed, it still requires 0.5 seconds to convert into the mechanical action of opening the solenoid valve. Therefore, the aforementioned first brief judgment period can be set from 0 to 1.5 seconds after the fuel nozzle opens the solenoid valve, completing the acquisition of the first pulse information within 1.5 seconds. After the aforementioned first brief judgment period, a pulse detection can be performed every 1 second, and this process can continue for 8 seconds. After 9.5 seconds, the judgment process exits, and the acquisition of the second pulse information is completed. That is, the aforementioned second continuous judgment period can be set from 0 to 9.5 seconds after the fuel nozzle opens the solenoid valve. Specifically, the aforementioned first brief judgment period and second continuous judgment period can also be set to other time periods according to the actual effect, and the present invention does not limit this.

[0066] Specifically, in order to detect whether a nozzle skipping or count skipping fault may occur, the flow rate of the refueling nozzle per second can be collected in step S01, so as to determine whether a nozzle skipping or count skipping fault has occurred based on the change in flow rate.

[0067] In step S102, after acquiring the first pulse information, second pulse information, and flow rate per second from the refueling nozzle, logical judgments can be made based on this data to determine whether the refueling nozzle has a jump count fault and to identify the fault type. The jump count fault of the refueling nozzle can be either a nozzle lifting jump count fault or a nozzle shut-off jump count fault.

[0068] Specifically, since transient nozzle-lifting jump count faults manifest in two different ways depending on the number of jumps—either displayed on the display or not—and these two manifestations lead to different consequences, with the displayed jump count being more likely to cause disputes and conflicts, transient nozzle-lifting jump count faults can be divided into two different types. The first type of jump count fault is characterized by jump counts occurring before refueling, but the jump count does not exceed the pulse hidden threshold, and the display shows no jump count. This type of fault occurs during the nozzle-lifting stage and may be caused by thermal expansion and contraction, hose expansion, etc., and has lower warning importance. The second type of jump count fault is characterized by jump counts occurring before refueling, and the jump count exceeds the pulse hidden threshold, with the nozzle displayed on the display. This type of fault occurs during the nozzle-lifting stage and may be caused by issues such as submersible pump check valve leaks, pipeline leaks, etc., and has higher warning importance.

[0069] Specifically, continuous nozzle lifting and meter reading failures can be classified as the third type of failure. That is, the third type of failure is characterized by continuous meter readings even when the nozzle is lifted without adding fuel. This type of failure occurs during the nozzle lifting stage, is generally caused by equipment failure, and has high early warning importance.

[0070] Specifically, the skipping count fault can also be classified into a fourth type of skipping count fault. That is, the fourth type of skipping count fault can be a skipping count fault in which the count continues to run after the skipping has stopped. This fourth type of skipping count fault occurs during the skipping stage and is generally caused by equipment failure. It also has high early warning importance.

[0071] Specifically, in step S102, based on the first pulse information, the second pulse information, and the flow rate, it is determined whether the refueling nozzle has a faulty pulse count, and the fault type to which the faulty pulse count belongs can be determined, which may include:

[0072] When the first pulse information indicates that the fuel nozzle generates a pulse within the first short judgment period, and the second pulse information indicates that the fuel nozzle does not generate a continuous pulse within the second continuous judgment period, it is determined that the fuel nozzle has a fault of skipping the nozzle; then, the fault type to which the fault of skipping the nozzle belongs is determined according to the number of pulses generated by the fuel nozzle in the second pulse information.

[0073] like Figure 2 As shown, Figure 2This is a flowchart illustrating the judgment logic for a first type and a second type of nozzle count fault according to an embodiment of the present invention. After the nozzle is lifted, a pulse is generated within the first brief judgment period (second 0-second 1.5-second) but does not continue to occur within the second continuous judgment period (9.5 seconds). This may be a brief nozzle lift-up count fault caused by various problems such as pipeline issues or weather conditions. That is, the pulse has an end within the 9.5-second period, which can be judged as a nozzle lift-up count fault occurring before the refueling process begins. Specifically, this nozzle lift-up count fault is a brief nozzle lift-up count fault. Next, the fault type of this brief nozzle lift-up count fault can be further determined by judging the number of pulses generated by the refueling nozzle in the second pulse information. It can be determined whether the fault type is a first type or a second type of nozzle lift-up count fault.

[0074] Specifically, the method of determining the fault type of the nozzle jump failure based on the number of pulses generated by the refueling nozzle in the second pulse information can include:

[0075] If the number of pulses generated by the refueling nozzle in the second pulse information does not exceed 9, the fault type of the nozzle lifting jump count fault is determined to be the first type of jump count fault; if the number of pulses generated by the refueling nozzle in the second pulse information exceeds 9, the fault type of the nozzle lifting jump count fault is determined to be the second type of jump count fault.

[0076] Specifically, if the number of pulses obtained in the second pulse information does not exceed 9, the fuel dispenser will not exhibit any characteristics because the number of pulses does not exceed the pulse hiding amount. The display screen will not show the amount of fuel dispensed, and it will be invisible to the naked eye. Furthermore, if pulse generation stops at a certain point within the second continuous judgment cycle (9.5 seconds), the system can determine that the fuel dispenser has experienced a nozzle lift-up pulse count failure, and that this failure belongs to the first type of pulse count failure. Based on this first type of failure, a warning message is generated and uploaded for processing. Conversely, if the number of pulses obtained in the second pulse information exceeds 9, meaning the fuel dispenser display screen already shows the amount of fuel dispensed, and pulse generation stops at a certain point within the second continuous judgment cycle (9.5 seconds), the system can determine that the fuel dispenser has experienced a nozzle lift-up pulse count failure, and that this failure belongs to the second type of failure. Based on this second type of failure, a warning message is generated and uploaded for processing.

[0077] Specifically, in step S102, based on the first pulse information, the second pulse information, and the flow rate, it is determined whether the refueling nozzle has a faulty flow rate, and the fault type to which the faulty flow rate belongs may be determined. This may also include:

[0078] When the first pulse information indicates that the fuel nozzle generates a pulse within the first short judgment period, and the second pulse information indicates that the fuel nozzle generates a continuous pulse within the second continuous judgment period, then the number of pulses generated by the fuel nozzle in the second pulse information is used to determine whether the fuel nozzle has a jump count fault, and the fault type to which the jump count fault belongs is determined.

[0079] Specifically, such as Figure 3 As shown, Figure 3 This is a flowchart illustrating the judgment logic for a third type of nozzle jump fault according to an embodiment of the present invention. After the nozzle is lifted, if a pulse is generated within the first short judgment period (second 0-1.5) and continues to occur within the second continuous judgment period (9.5 seconds), there are two possible scenarios. The first scenario is that the gas station is performing self-calibration or is quickly lifting the nozzle for refueling. In this case, the nozzle is initially in the open state, so a pulse can be detected immediately after lifting the nozzle. However, in this situation, based on the actual refueling flow rate, due to the faster flow rate, the amount of fuel dispensed by the nozzle after the second continuous judgment period (9.5 seconds) will exceed a certain fuel quantity standard. The second scenario is that there is a problem with the gas station equipment, causing a jump fault to occur in the first second even when the gas station attendant follows the normal operating procedure, i.e., waiting more than 3 seconds after lifting the nozzle before starting refueling, instead of self-calibration or quick nozzle lifting. The pulse continues to occur within the second continuous judgment period (9.5 seconds), meaning a pulse is generated even before the nozzle is squeezed (within 3 seconds of lifting the nozzle), indicating a continuous nozzle lift jump fault. In this situation, the actual flow rate of the fuel dispenser is relatively slow, so the amount of fuel dispensed within the second continuous judgment period (9.5 seconds) will not exceed the aforementioned fuel volume standard. Therefore, when the fuel dispenser generates pulses during the first short judgment period and continuous pulses during the second continuous judgment period, it can be further determined whether the fuel dispenser has a faulty pump count based on whether the number of pulses generated by the fuel dispenser in the second pulse information exceeds the preset fuel volume standard, and the fault type to which the pump count fault belongs can be determined. Specifically, in some embodiments, the aforementioned preset fuel volume standard can be set to 200 pulses, which is approximately 2L of fuel volume, that is, whether a continuous pump count fault occurs can be determined based on whether the number of pulses generated by the fuel dispenser in the second pulse information exceeds 200.

[0080] Specifically, when determining whether the fuel nozzle has a fault in the number of pulses generated by the fuel nozzle in the second pulse information, it can be determined whether the cumulative number of pulses at a certain moment during the second continuous judgment period exceeds the fuel quantity standard, or it can be determined whether the total cumulative number of pulses after the end of the second continuous judgment period exceeds the fuel quantity standard. This invention does not limit this.

[0081] Specifically, the above-mentioned determination of whether the fuel nozzle has a pulse count failure based on the number of pulses generated by the fuel nozzle in the second pulse information, and the determination of the fault type to which the pulse count failure belongs, may include:

[0082] If the number of pulses generated by the refueling nozzle in the second pulse information is less than 200, it is determined that the refueling nozzle has a nozzle count failure, and the failure type is determined to be a third type of count failure.

[0083] Specifically, in some embodiments, the preset oil quantity standard can also be set to other values ​​according to the actual situation to better distinguish between the two different situations. The present invention does not limit this.

[0084] Specifically, if the refueling volume exceeds 2L (i.e., the number of pulses exceeds 200) after the second continuous judgment period (9.5 seconds), it can be determined that the refueling is normal. Therefore, the system can filter out transactions that generate pulses in the first second and have pulses continuously for 9.5 seconds, but whose refueling volume exceeds 2L after the judgment period ends, without generating a warning message. However, if the refueling volume does not exceed 2L (i.e., the number of pulses exceeds 200) after the second continuous judgment period (9.5 seconds), the system can determine that the refueling nozzle has experienced a nozzle lift-off fault, and the fault type of this nozzle lift-off fault is a type 3 fault. Therefore, a warning message is generated according to the type 3 fault and uploaded for processing.

[0085] Specifically, such as Figure 4 As shown, Figure 4 This is a flowchart illustrating the judgment logic for a nozzle-lifting jump count fault according to an embodiment of the present invention. The nozzle-lifting jump count fault can include a first type of jump count fault, a second type of jump count fault, and a third type of jump count fault. The judgment is based on whether a pulse is generated from 0 seconds to 9.5 seconds after the start of refueling. The software process is executed step-by-step to accurately determine the jump count.

[0086] Since the valve opens immediately after the gun is picked up and the IC card authorization is completed, but it takes 0.5 seconds to convert into the mechanical action of opening the solenoid valve, the first judgment cycle is from 0 seconds to 1.5 seconds. Then, a pulse judgment is performed every 1 second for 8 consecutive seconds, and the judgment is exited after 9.5 seconds.

[0087] The process begins by checking for continuous pulses every second from second 0 to 9.5. If no continuous pulses are generated, then within the check period, if a pulse occurs in the first second, it is checked whether the number of pulses exceeds 9 and then stops generating. If the number of pulses does not exceed 9, then it is checked whether the number of pulses after the first second is less than 9 and then stops generating; if so, the fuel dispenser is considered to have experienced a first-type pulse count failure. If the number of pulses after the first second exceeds 9, the fuel dispenser is considered to have experienced a second-type pulse count failure. When continuous pulses are generated, it is further checked whether the amount of fuel dispensed within 9.5 seconds exceeds 2L (i.e., 200 pulses). If not, the fuel dispenser is considered to have experienced a third-type pulse count failure. If the amount of fuel dispensed within 9.5 seconds exceeds 2L, the fuel dispenser is considered to be functioning normally. Due to occasional normal errors that trigger the pump count mechanism during daily refueling, such transactions usually occur within a very short time between the employee picking up the pump and refueling, which is equivalent to simulating the pump count process. This would be a transaction under unconventional operation, with the transaction volume exceeding 2L in 9.5 seconds. Therefore, no judgment is made regardless of whether there is actually a count. In other words, the judgment process only takes effect under normal operation.

[0088] Specifically, in step S102, based on the first pulse information, the second pulse information, and the flow rate, it is determined whether the refueling nozzle has a faulty flow rate, and the fault type to which the faulty flow rate belongs may be determined. This may also include:

[0089] When the flow rate of the fuel nozzle drops below 5L / min, the flow rate of the fuel nozzle is obtained for the next 9 consecutive seconds. If the flow rate of the fuel nozzle for the next 9 consecutive seconds is greater than 0L / min and less than 5L / min, it is determined that the fuel nozzle has a fault of skipping the number of times, and the fault type of the fault of skipping the number of times is determined to be the fourth type of fault.

[0090] When the equipment is functioning normally, the flow rate typically drops from the normal 30L / Min to 0 after the fuel dispenser shuts off. However, in the event of a malfunction causing the fuel dispenser to skip numbers, the reduced flow rate will be greater than 0L / Min, but will not exceed 5L / Min. Therefore, if the flow rate remains in this state for 9 consecutive seconds, the system can determine that a fault has occurred. Because the refueling process after the dispenser shuts off is very complex, the computer logic cannot accurately distinguish between manual refueling and a faulty flow rate. Therefore, only a more extreme judgment can be made here. The specific judgment scenario is that when there is a faulty flow rate after the dispenser shuts off, the fuel dispenser display keeps showing a number, and it is immediately visible to the naked eye when holding the fuel nozzle. After 9 consecutive seconds, the computer can also make a judgment.

[0091] Specifically, such as Figure 5 As shown, Figure 5This is a flowchart illustrating the judgment logic of a fourth type of nozzle skipping fault according to an embodiment of the present invention. First, the fuel dispenser checks the flow rate once per second, using 5L / min as the judgment threshold. If pulses are generated continuously for 9 seconds, and the flow rate is continuously within the range of less than 5L / min and greater than 0L / min, the system can determine that the fuel dispenser has a nozzle skipping fault, and that this nozzle skipping fault belongs to the fourth type of skipping fault. Therefore, a warning message is generated according to the fourth type of skipping fault and uploaded for processing.

[0092] Specifically, depending on the actual test conditions, the above-mentioned flow rate judgment threshold can be set to other values ​​in other embodiments to more accurately determine whether there is a skipping gun skipping fault. This invention does not limit this.

[0093] Specifically, depending on the actual test conditions, in other embodiments, the duration for determining whether the test flow rate falls within the above-mentioned determination interval can be set to other time lengths to more accurately determine whether there is a fault in the number of skipped shots. This invention does not limit this.

[0094] Specifically, such as Figure 6 As shown, Figure 6 This is a flowchart illustrating the judgment logic for a nozzle skipping / counting fault according to an embodiment of the present invention. In actual refueling, except for manual control, it is practically impossible to achieve a flow rate below 5L / min, let alone maintain such a low flow rate for an extended period. Therefore, when the refueling nozzle flow rate (S) is 0L / min < S < 5L / min for 9 consecutive seconds, a fourth type of skipping / counting fault can be identified. Specifically, the refueling pump can check the flow rate data once per second. When the flow rate drops from above 10L / min in the previous second to below 5L / min (approximately 8 pulses per second), it can be further determined whether pulses are generated for 9 consecutive seconds, and whether the flow rate remains continuously within the range of less than 5L / min and greater than 0L / min. If so, it is determined that the refueling nozzle has experienced a fourth type of skipping / counting fault; otherwise, it is determined that the refueling is being manually controlled, and no action is taken.

[0095] Specifically, considering that gas stations may refuel motorcycles, and given the complexity of the motorcycle refueling process, which can easily trigger incorrect nozzle lift-up and nozzle count checks, transactions with a refueling volume of 10L or less can be filtered out as motorcycle refueling. These transactions are considered non-standard refueling and therefore do not require nozzle lift-up or nozzle count checks. A check is only performed when the pump completes a standard refueling transaction.

[0096] In step S103, when a fuel nozzle experiences a fault in the number of clicks, a warning message can be generated and statistically analyzed based on the fault type to provide real-time information on the equipment status of the fuel nozzle.

[0097] In step S104, when the warning information of the fuel nozzle reaches certain conditions, it indicates that the fuel nozzle has a major malfunction and is likely to cause disputes. Therefore, an alarm can be generated after the warning information reaches the specified conditions and the alarm can be reported to the operation and maintenance platform for processing, so as to remind the gas station maintenance personnel to repair the fuel nozzle.

[0098] Specifically, each time an abnormal number of fuel nozzle clicks occurs, the Internet of Things (IoT) collects data and generates a warning message. When the warning message meets certain conditions, an alarm is triggered, and the operation and maintenance platform automatically generates a fault handling plan and sends an SMS. The fault handling plan can be divided into different levels according to its urgency. For example, in some embodiments, the fault handling plan can be divided into a first emergency repair procedure with higher urgency and a second emergency repair procedure with lower urgency.

[0099] Specifically, in step S104, in some embodiments, the process of generating alarm information after the warning information reaches a specified condition and reporting the alarm information to the operation and maintenance platform for processing may include:

[0100] When a single refueling nozzle simultaneously collects warning information for both nozzle lifting and nozzle disconnection faults, a first alarm is generated and reported to the maintenance platform for the first emergency repair. When a single refueling nozzle collects warning information for three consecutive shifts, a second alarm is generated and reported to the maintenance platform for the second emergency repair.

[0101] Specifically, when the Internet of Things (IoT) detects that a single fuel nozzle is simultaneously exhibiting both "nozzle lift-up" and "nozzle stop-up" occurrences, it can be determined that the nozzle has a very high probability of malfunction. In this case, the IoT can generate and display an alarm message and automatically push the fault information to the maintenance platform, triggering an SMS notification to relevant personnel for immediate emergency repair. Specifically, this immediate emergency repair could involve the gas station shutting down the corresponding fuel nozzle, with the maintenance unit dispatching personnel to the station for repair within 8 hours.

[0102] Specifically, when the IoT detects that a single fuel nozzle experiences a number of clicks or disconnections, but these occur at different times, it can be determined that the nozzle is suspected of being faulty. The IoT will only generate and display a warning message. In this case, the gas station should pay close attention to the corresponding fuel nozzle. However, if a single fuel nozzle receives warning messages for three consecutive shifts, it can be determined that the probability of the nozzle being faulty is high. In this case, the IoT can generate and display an alarm message and automatically push the fault information to the maintenance platform to trigger an SMS notification for relevant personnel to conduct a second emergency repair. Specifically, this second emergency repair could involve the gas station shutting down the corresponding fuel nozzle, with the maintenance unit dispatching personnel to the station for repair within 22 hours.

[0103] In addition, under normal circumstances, after each shift change, the gas pump will activate the forced emptying function. This can only be deactivated by inserting an employee card and lifting the nozzle. A fixed amount of 3 yuan is typically set. Any skipped charges caused by pipeline problems can be detected during this stage, and since the skipped amount is limited to 3 yuan, it prevents further losses to the gas station. Therefore, the skipped charge transactions generated by the forced emptying operation can be directly uploaded to the Internet of Things (IoT) for early warning information. The IoT can also collect data on whether a transaction (i.e., a nozzle skipping) occurs during the forced emptying of a single gas pump. If nozzle skipping occurs for three consecutive shifts, it can be determined that the probability of the gas pump being faulty is extremely high. In this case, the IoT can generate and display an alarm message and automatically push fault information to the maintenance platform to trigger an SMS reminder for relevant personnel to carry out the first emergency repair. Specifically, the first emergency repair plan can be that the gas station shuts down the corresponding gas pump, and the maintenance unit arranges personnel to the station for repair within 8 hours.

[0104] Specifically, in step S104, in some embodiments, the process of generating alarm information after the warning information reaches a specified condition and reporting the alarm information to the operation and maintenance platform for processing may further include:

[0105] At the same time as generating the alarm information, a lock command for the refueling nozzle is sent to the refueling equipment so that the refueling equipment locks the refueling nozzle after receiving the lock command and without entering a specified unlock password.

[0106] Specifically, when a fuel nozzle in a refueling station exhibits abnormal flow rate and generates alarm information (including a first alarm and a second alarm), it can be assumed that the nozzle is likely faulty. Its use should be restricted until repairs are completed to avoid significant losses. In this case, the Internet of Things (IoT) can send a nozzle-locking command to the refueling station. Upon receiving this command, the refueling station locks the faulty nozzle, restricting its use at the device level. Specifically, the timing and triggering conditions for sending the nozzle-locking command can be simultaneous with the generation of the alarm information or simultaneously with the push notification of the abnormal flow rate fault via SMS. The invention does not impose any restrictions on this, as long as the use of the faulty nozzle is promptly restricted. Specifically, after receiving the nozzle-locking command and locking the nozzle, the refueling station can also display the message "Fluctuation Rate Fault, Nozzle Locked" on the LCD screen as a reminder. Specifically, once the nozzle is locked, it can only be put back into use after the maintenance unit arrives at the gas station to repair it, and then the designated unlocking password is entered on the refueling station's keypad to unlock it.

[0107] The fuel dispenser nozzle abnormal count alarm identification method described in this invention can automatically detect fuel dispenser count alarm faults through reasonable logical judgment. Based on the operating status of the fuel dispenser, including the collected first pulse information, second pulse information, and the flow rate per second of the fuel nozzle, it can systematically determine whether a count alarm fault exists and its specific type, and issue corresponding warnings. This significantly improves the stability and reliability of the equipment from a technical prevention perspective, and through system warnings and proactive prevention, minimizes the risks caused by count alarm faults.

[0108] Furthermore, based on the practical application of this software upgrade, and in conjunction with the hardware aspects of the equipment, we can also collaborate with equipment manufacturers to research and improve the overall sealing performance, reliability, and control sensitivity of the equipment; optimize the internal processes of the fuel dispenser, such as assembling the solenoid valve at the front end of the flow meter to reduce internal air leakage; and improve the thickness, material, and toughness of the air pipe in the oil and gas recovery coaxial hose to increase its pressure / bending resistance and prevent the risk of nozzle tripping or skipping due to hardware damage.

[0109] Corresponding to the livestock weight measurement method embodiments described above, the present invention also provides a livestock weight measurement device.

[0110] like Figure 7 As shown, Figure 7 This is a schematic diagram of a fuel dispenser nozzle abnormal jump count warning and identification device according to an embodiment of the present invention. The device is connected to the fuel dispenser nozzle on the fuel dispenser via the Internet of Things and includes the following modules:

[0111] The data acquisition module 710 is used to acquire, via the Internet of Things, the first pulse information generated by the fuel nozzle in the first short judgment period, the second pulse information generated by the fuel nozzle in the second continuous judgment period, and the flow rate of the fuel nozzle per second after the fuel nozzle solenoid valve is opened; the second continuous judgment period is longer than the first short judgment period.

[0112] The detection module 720 is used to determine whether the refueling nozzle has a jump count fault based on the first pulse information, the second pulse information, and the flow rate, and to determine the fault type to which the jump count fault belongs; the jump count fault is either a nozzle lift jump count fault or a nozzle stop jump count fault;

[0113] The early warning module 730 is used to generate early warning information based on the fault type after the fuel nozzle experiences a fault in the number of clicks.

[0114] The alarm module 740 is used to generate alarm information when the warning information reaches the specified conditions, and to report the alarm information to the operation and maintenance platform for processing.

[0115] Preferably, the first short-term judgment period can be from the 0th second to the 1.5th second after the fuel nozzle opens the solenoid valve, and the second continuous judgment period can be from the 0th second to the 9.5th second after the fuel nozzle opens the solenoid valve.

[0116] Preferably, the detection module 720 described above can be used for:

[0117] When the first pulse information is that the fuel nozzle generates a pulse within the first short judgment period, and the second pulse information is that the fuel nozzle does not generate a continuous pulse within the second continuous judgment period, it is judged that the fuel nozzle has a fault of skipping the number of times it lifts the nozzle.

[0118] The type of fault to which the nozzle jump fault belongs is determined by the number of pulses generated by the refueling nozzle in the second pulse information.

[0119] Preferably, the determination of the fault type of the nozzle jump failure based on the number of pulses generated by the refueling nozzle in the second pulse information may include:

[0120] If the number of pulses generated by the refueling nozzle in the second pulse information does not exceed 9, then the fault type of the nozzle jump count fault is determined to be the first type of jump count fault.

[0121] If the number of pulses generated by the refueling nozzle in the second pulse information exceeds 9, then the fault type to which the nozzle jump count fault belongs is determined to be the second type of jump count fault.

[0122] Preferably, the detection module 720 described above can also be used for:

[0123] When the first pulse information indicates that the fuel nozzle generates a pulse within the first short judgment period, and the second pulse information indicates that the fuel nozzle generates a continuous pulse within the second continuous judgment period, the number of pulses generated by the fuel nozzle in the second pulse information is used to determine whether the fuel nozzle has a jump count fault, and the fault type to which the jump count fault belongs is determined.

[0124] Preferably, the above-mentioned determination of whether the fuel nozzle has a pulse count failure based on the number of pulses generated by the fuel nozzle in the second pulse information, and determination of the fault type to which the pulse count failure belongs, may include:

[0125] If the number of pulses generated by the refueling nozzle in the second pulse information is less than 200, it is determined that the refueling nozzle has a nozzle lift count failure, and the failure type of the nozzle lift count failure is determined to be a third type of count failure.

[0126] Preferably, the detection module 720 described above can also be used for:

[0127] When the flow rate of the fuel nozzle drops below 5L / min, obtain the flow rate of the fuel nozzle for the next 9 consecutive seconds;

[0128] If the flow rate of the fuel nozzle is greater than 0 L / min and less than 5 L / min for the next 9 consecutive seconds, it is determined that the fuel nozzle has a shut-off fault, and the fault type of the shut-off fault is determined to be the fourth type of shut-off fault.

[0129] Preferably, the alarm module 740 described above can be used for:

[0130] When a single fuel nozzle simultaneously collects warning information for both nozzle lifting failure and nozzle tripping failure, a first alarm is generated and reported to the maintenance platform for emergency repair.

[0131] When a single refueling nozzle collects warning information for three consecutive shifts, a second alarm is generated and reported to the operation and maintenance platform for a second emergency repair.

[0132] Preferably, the alarm module 740 can also be used for:

[0133] At the same time as generating the alarm information, a lock command for the refueling nozzle is sent to the refueling equipment so that the refueling equipment locks the refueling nozzle after receiving the lock command and without entering a specified unlock password.

[0134] The specific implementation process of the functions and roles of each module in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0135] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of the present invention according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0136] The present invention also provides a computer device, which includes at least a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described in any of the foregoing embodiments.

[0137] Figure 8The diagram illustrates a more specific hardware structure of a computing device provided by the present invention. This device may include: a processor 801, a memory 802, an input / output interface 803, a communication interface 804, and a bus 805. The processor 801, memory 802, input / output interface 803, and communication interface 804 are interconnected internally via the bus 805.

[0138] The processor 801 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solution provided by this invention. The processor 801 may also include a graphics card, such as an Nvidia Titan X graphics card or a 1080Ti graphics card.

[0139] The memory 802 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 802 can store the operating system and other application programs. When the technical solution provided by this invention is implemented through software or firmware, the relevant program code is stored in the memory 802 and is called and executed by the processor 801.

[0140] The input / output interface 803 is used to connect input / output modules to enable information input and output. Input / output modules can be configured as components within the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., while output devices may include displays, speakers, vibrators, indicator lights, etc.

[0141] The communication interface 804 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (e.g., USB, Ethernet cable) or wireless means (e.g., mobile network, Wi-Fi, Bluetooth).

[0142] Bus 805 includes a pathway for transmitting information between various components of the device, such as processor 801, memory 802, input / output interface 803, and communication interface 804.

[0143] It should be noted that although the above-described device only shows the processor 801, memory 802, input / output interface 803, communication interface 804, and bus 805, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the present invention, and not necessarily all the components shown in the figures.

[0144] The present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the methods described in any of the foregoing embodiments.

[0145] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0146] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of the present invention.

[0147] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0148] The various embodiments in this invention are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments. The device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate. In implementing the present invention, the functions of each module can be implemented in one or more software and / or hardware. Alternatively, some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0149] Obviously, the above embodiments of the present invention are merely examples for clearly illustrating the present invention, and are not intended to limit the implementation of the present invention. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention should be included within the protection scope of the claims of the present invention.

Claims

1. A method for identifying abnormal jump count of a forecourt dispenser, characterized in that, The method includes: After the fuel nozzle solenoid valve is opened, the first pulse information generated by the fuel nozzle in the first short judgment period, the second pulse information generated by the fuel nozzle in the second continuous judgment period, and the flow rate of the fuel nozzle per second are obtained through the Internet of Things; the second continuous judgment period is longer than the first short judgment period. Based on the first pulse information, the second pulse information, and the flow rate, determine whether the refueling nozzle has a faulty flow rate, and determine the fault type to which the faulty flow rate belongs; including: When the first pulse information indicates that the fuel nozzle generates a pulse within the first short judgment period, and the second pulse information indicates that the fuel nozzle does not generate a continuous pulse within the second continuous judgment period, it is determined that the fuel nozzle has a fault of skipping the nozzle. The fault type of the nozzle jump count fault is determined based on the number of pulses generated by the refueling nozzle in the second pulse information, including: if the number of pulses generated by the refueling nozzle in the second pulse information does not exceed 9, then the fault type of the nozzle jump count fault is determined to be the first type of jump count fault. If the number of pulses generated by the refueling nozzle in the second pulse information exceeds 9, then the fault type of the nozzle lift-off jump count fault is determined to be the second type of jump count fault; the jump count fault is either a nozzle lift-off jump count fault or a nozzle jump count fault. After the fuel nozzle experiences the aforementioned fault in the number of clicks, a warning message is generated based on the fault type. When the warning information meets the specified conditions, an alarm information is generated and reported to the operation and maintenance platform for processing; The step of determining whether the refueling nozzle has a faulty flow rate based on the first pulse information, the second pulse information, and the flow rate, and determining the fault type to which the faulty flow rate belongs, includes: When the first pulse information indicates that the refueling nozzle generates a pulse within the first short judgment period, and the second pulse information indicates that the refueling nozzle generates a continuous pulse within the second continuous judgment period, then the number of pulses generated by the refueling nozzle in the second pulse information is used to determine whether the refueling nozzle has a count-skipping fault, and the fault type to which the count-skipping fault belongs is determined; specifically including: If the number of pulses generated by the refueling nozzle in the second pulse information is less than 200, it is determined that the refueling nozzle has a nozzle lift count failure, and the failure type of the nozzle lift count failure is determined to be a third type of count failure. The step of determining whether the refueling nozzle has a faulty flow rate based on the first pulse information, the second pulse information, and the flow rate, and determining the fault type to which the faulty flow rate belongs, includes: When the flow rate of the refueling nozzle drops below 5L / min, the flow rate of the refueling nozzle for the next 9 consecutive seconds is obtained; If the flow rate of the refueling nozzle is greater than 0 L / min and less than 5 L / min for the next 9 consecutive seconds, it is determined that the refueling nozzle has a nozzle skipping fault, and the fault type of the nozzle skipping fault is determined to be the fourth type of skipping fault.

2. The method of claim 1, wherein, The first short-term judgment period is from the 0th second to the 1.5th second after the fuel nozzle opens the solenoid valve, and the second continuous judgment period is from the 0th second to the 9.5th second after the fuel nozzle opens the solenoid valve.

3. The method of claim 1, wherein, The process of generating alarm information after the early warning information meets specified conditions and reporting the alarm information to the operation and maintenance platform for processing includes: When a single refueling nozzle simultaneously collects warning information for both nozzle lifting failure and nozzle disconnection failure, a first alarm is generated and reported to the maintenance platform for emergency repair. When a single refueling nozzle collects warning information for three consecutive shifts, a second alarm is generated and reported to the maintenance platform for a second emergency repair.

4. The method of claim 1, wherein, The step of generating alarm information after the early warning information reaches the specified conditions and reporting the alarm information to the operation and maintenance platform for processing also includes: Simultaneously with generating the alarm information, a lock command for the refueling nozzle is sent to the refueling equipment, so that upon receiving the lock command, the refueling equipment locks the refueling nozzle without entering a specified unlock password.

5. A device for early warning and identification of abnormal nozzle lifting counts on a fuel dispenser, characterized in that, The device is based on the method according to any one of claims 1-4, the device is connected to the fuel nozzle on the refueling equipment via the Internet of Things, and the device comprises: The data acquisition module is used to acquire, via the Internet of Things, the first pulse information generated by the fuel nozzle within a first short judgment period, the second pulse information generated by the fuel nozzle within a second continuous judgment period, and the flow rate of the fuel nozzle per second after the fuel nozzle solenoid valve is opened; the second continuous judgment period is longer than the first short judgment period. The detection module is used to determine whether the refueling nozzle has a jump count fault based on the first pulse information, the second pulse information, and the flow rate, and to determine the fault type to which the jump count fault belongs; the jump count fault is a nozzle lift jump count fault or a nozzle jump count fault. The early warning module is used to generate early warning information based on the fault type after the fuel nozzle experiences the fault in the number of clicks. The alarm module is used to generate alarm information when the warning information reaches the specified conditions, and to report the alarm information to the operation and maintenance platform for processing.

Images