A self-diagnosis network system for fuel dispenser and intelligent fuel dispenser
Through CAN bus architecture and gateway technology, self-diagnosis and data collection of tanker faults are realized, solving the problem that existing tanker cannot self-diagnose, and improving management efficiency and cost-effectiveness.
Patent Information
- Application Number
- CN202211009646.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-08-22
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2042-08-22
AI Technical Summary
The existing tanker lacks the self-diagnosis function of faults, cannot realize the summary statistics and analysis of its own data, lacks monitoring and adjustment functions, and only has simple advertising delivery functions, and fails to realize human-computer interaction.
The CAN bus architecture protocol is adopted to realize fault detection and diagnosis through data bus communication between the multi-function display module, the gas machine motherboard module and the pulse data acquisition module, and combine gateway and sensor data acquisition to realize the display and processing of fault information.
It realizes the self-diagnosis ability of the tanker fault, improves the emergency response capacity of the gas station, simplifies the management of multiple gas stations, saves costs and increases profits.
Smart Images

Figure CN115448244B_ABST
Abstract
Description
Technical Field
[0001] The invention belongs to the technical field of fuel dispensers, and in particular relates to a fuel dispenser self-diagnosis network system and an intelligent fuel dispenser. Background Art
[0002] At present, most gas pumps are traditional and only have the function of refueling. Some of them can only realize simple functions, which can be called simplified versions of "smart gas pumps". They fail to realize the self-diagnosis function of gas pump faults. This is because the electrical architecture and technical conditions of the current gas pumps are limited, and they cannot realize the data aggregation, statistics and analysis of the gas pumps themselves to find abnormalities. There is a lack of background services and cloud support, and the gas pumps themselves lack the necessary monitoring and adjustment functions. They are equipped with a 32-inch touch screen, but only have the function of advertising. They do not have the function of calling the data interface to display the fault information, and fail to realize the real exchange between man and machine. Summary of the invention
[0003] In view of the above-mentioned deficiencies, an object of the present invention is to provide a fuel dispenser self-diagnosis network system and an intelligent fuel dispenser.
[0004] The present invention provides the following technical solutions:
[0005] A self-diagnosis network system for a fuel dispenser and an intelligent fuel dispenser, comprising a CAN0 bus, a CAN1 bus, and a gateway; a multifunctional display screen module, a fuel dispenser mainboard module, and a pulse data acquisition module are connected through data bus communication and through CAN0 bus communication; the fuel dispenser mainboard module is connected to a keyboard control board, a solenoid valve controller, and a tax control screen through CAN0 bus communication; the pulse data acquisition module, the fuel dispenser mainboard module, an oil and gas concentration sensor, a temperature sensor, a pressure sensor, a liquid level meter, a breakaway valve, a POS machine, an oil and gas recovery control module, and a plurality of oil gun switches are connected through CAN1 bus communication.
[0006] The information synchronization steps between the multi-function display screen module, the fuel dispenser main board module, and the CPU of the pulse data acquisition module are as follows:
[0007] S101, the gateway receives a flag setting signal sent by the CPU of the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module;
[0008] S102, determine whether the network system cycle timing is ≥500ms; if so, proceed to the next step, if not, the multi-function display module CPU reads the contents of the gateway data buffer register;
[0009] S103, the network system periodic timing reset; the gateway receives the module dial code sent by the CPU of the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module to the gateway; the register calculates the matching count;
[0010] S104, the gateway determines whether the CPU dial codes of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module are consistent and whether the dial code data is received; if so, proceed to the next step; if not, clear the register match count, and determine whether the match count is ≥7 and whether the dial code data is received. If so, the gateway receives the fault information and flag setting signal sent by the CPU of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module, and then feeds the system to let the multi-function display screen module CPU read the contents of the gateway data buffer register. If not, determine whether the match count is ≥7 and whether the dial code data is not received. If so, let the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module send the flag setting signal for the uplink and downlink data, and then initialize the receiving area of the CAN0 bus. The gateway checks the working mode. If not, let the system feed the dog and let the multi-function display screen module CPU read the contents of the gateway data buffer register.
[0011] S105, make the dial code compare and count correctly;
[0012] S106, determine whether the dial code comparison is correct and the count is ≥5; if so, proceed to the next step, if not, feed the system and let the multi-function display module CPU read the contents of the gateway data buffer register;
[0013] S107, reset the DIP fault light;
[0014] S108, the gateway determines whether the CPU dial code sending timing of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module is consistent; if so, proceed to the next step, if not, after the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module send uplink and downlink data flags are set, the receiving area of the CAN0 bus is initialized, and the gateway checks the working mode;
[0015] S109. The gateway determines whether it is a pulse data acquisition module. If so, the gateway confirms that the acquisition module is successfully synchronized, and then initializes the receiving area of the CAN0 bus, and the gateway checks the working mode; if not, the pulse data acquisition module sends the uplink and downlink data flag setting signal, and then initializes the receiving area of the CAN0 bus, and the gateway determines whether it is a fuel dispenser mainboard module; if so, the gateway confirms that the fuel dispenser mainboard module is successfully synchronized, and then initializes the receiving area of the CAN0 bus, and the gateway checks the working mode; if not, the fuel dispenser mainboard module sends the uplink and downlink data flag setting signal, and then initializes the receiving area of the CAN0 bus, and the gateway determines whether it is a multi-function display module; if so, the gateway confirms that the multi-function display module is successfully synchronized, and then initializes the receiving area of the CAN0 bus, and the gateway checks the working mode; if not, the multi-function display module sends the uplink and downlink data flag setting signal, and then initializes the receiving area of the CAN0 bus, and the gateway determines whether it is a multi-function display module.
[0016] The steps for gateway data collection are:
[0017] S201, the gateway periodically obtains data on the channel;
[0018] S202, compare the data saved in the previous cycle with the newly collected data to see if they are consistent; if not, proceed to the next step; if yes, determine whether data is sampled for 10 consecutive sampling cycles, if not, terminate, if yes, determine whether new data is sampled, if yes, set the register state, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light, if not, light up the corresponding fault light, send fault information and set the fault, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light;
[0019] S203, check whether the near-end line of the circuit is normal, if so, proceed to the next step, if not, determine whether data is sampled for 10 consecutive cycles, if not, terminate, if so, clear the corresponding collection count, clear the uplink and downlink line faults, and turn off the fault light when there is no collection fault;
[0020] S204, determine whether data is sampled for 10 consecutive cycles, if not, terminate, if yes, determine whether it is an uplink, if not, proceed to the next step, if it is an uplink, set the uplink fault, and then determine whether the uplink communication is normal, if not, terminate, if normal, send fault information, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light;
[0021] S205, determine whether it is a downlink line, if not, terminate; if it is a downlink line, set the downlink line fault, and then determine whether the downlink line communication is normal, if not, terminate; if normal, send fault information, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light.
[0022] The troubleshooting steps are:
[0023] S401, the gateway obtains the current working mode;
[0024] S402, the gateway performs fault detection on the uplink and downlink lines of the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module;
[0025] S403, set loop variable 1 J=0;
[0026] S404, determine whether J is less than 5; if not, proceed to the next step, if yes, determine whether the RS485 channel status is not 0x77; if the RS485 channel status is not 0x77, then when the cable transmission channel count is <255, the channel count is +1; when the cable transmission channel count is ≥255, the channel count is cleared, and then the channel count is set to 4 and a channel fault is sent, and then the loop variable J is incremented and then it is determined whether J is less than 5; if the RS485 channel status is 0x77, the pulse data acquisition module status information count is cleared, and then the loop variable J is incremented and then it is determined whether J is less than 5;
[0027] S405, clearing the pulse data acquisition module status information count;
[0028] S406, set loop variable one J=0;
[0029] S407, determine whether J is less than 3, if J ≥ 3, terminate, if J < 3, determine whether the pulse data acquisition module is normal and whether the sensor network has no faults; if so, increase J and then determine whether J is less than 3, if not, send an error code, and then increase J and then determine whether J is less than 3.
[0030] The steps for CAN0 bus and CAN1 bus to receive data are:
[0031] S501, determine whether it is CAN0 bus, if it is CAN0 bus, read CAN0 buffer data and proceed to the next step, if it is not CAN0 bus, determine whether it is CAN1 bus; if it is not CAN1 bus, proceed to the next step, if it is CAN1 bus, read CAN1 buffer data and proceed to the next step;
[0032] S502, read the IDs of other devices connected to the CAN0 bus or CAN1 bus except the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module;
[0033] S503, read device data;
[0034] S504, read the device number;
[0035] S505, determine whether the number is greater than 0 and less than 10; if not, terminate; if yes, proceed to the next step;
[0036] S506, reading the data of the device connected to the CAN0 bus and the data of the device connected to the CAN1 bus, reading the original data of the device, and performing corresponding processing;
[0037] S507: Compare fault information and send fault code and warning information.
[0038] The steps to send fault information to CAN0 bus and CAN1 bus are:
[0039] S601, determine whether the number of cache fault packets of the CPU registers of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module is ≤ 0, if so, the cache fault pointer assigns the write pointer to the read pointer and then terminates, if not, proceed to the next step;
[0040] S602, setting the ID number of the module connected to the CAN0 bus;
[0041] S603, reading data in the fault buffer area;
[0042] S604, sending fault information to the CAN1 bus according to the ID number;
[0043] S605, when the transmission to the CAN1 bus fails, the fault information is sent to the CAN0 bus according to the ID number;
[0044] S606, determine whether the transmission is successful, if not, terminate, if yes, set the fault buffer read pointer +6, when the fault data buffer read pointer ≥ 0x60, clear the read pointer, and the total number of packets -1, and then terminate.
[0045] The program flow between the multi-function display screen module, the fuel dispenser main board module, and the pulse data acquisition module is as follows:
[0046] S701, system initialization;
[0047] S702, variable initialization;
[0048] S703, loop variable (1) starts;
[0049] S704, the data received by UART is sent to the SPI buffer area;
[0050] S705, SPI data processing;
[0051] S706, SPI data is sent to the CAN0 bus buffer;
[0052] S707, the data packet received by the gateway is sent to the SPI;
[0053] S708, SPI loads data;
[0054] S709, gateway fault detection;
[0055] S710, UART fault detection;
[0056] S711, fuel dispenser host module and pulse data acquisition module periodic update;
[0057] S712: After feeding the dog, the system returns to S703.
[0058] The system process is:
[0059] S801, power on and start;
[0060] S802, initialization of each module;
[0061] S803, start the fuel dispenser program;
[0062] S804, start the fuel dispenser self-checking program;
[0063] S805, start the fuel dispenser fault code library;
[0064] S806, check whether the networking beacon is normal, if not, the APP window will prompt an error list, if normal, proceed to the next step;
[0065] S807, transmit threshold data and determine whether the test threshold is normal. If it is not normal, the APP window prompts an error list. If it is normal, perform information fusion processing; collect time data and determine whether the time is normal. If it is not normal, the APP window prompts an error list. If it is normal, perform information fusion processing;
[0066] S808, determine whether it is urgent, if it is urgent, make a voice announcement, if it is not urgent, proceed to the next step;
[0067] S809, self-test and service life data are stored locally in the fuel dispenser;
[0068] S810, self-inspection and service life data upload to APP and cloud analysis.
[0069] An intelligent fuel dispenser comprises the above-mentioned fuel dispenser self-diagnosis network system.
[0070] The beneficial effects of the present invention are as follows: the present invention adopts the CAN bus architecture protocol, which can realize the scalability of the tanker itself, facilitate the circulation of data, and solve the current inability to realize the self-diagnosis capability of the tanker fault; after the tanker realizes the self-diagnosis capability of the fault, it is convenient for the emergency handling capability of the gas station, and it is more convenient for the gas station management company to manage multiple gas stations and multiple oil machines, saving costs and increasing profits. The tanker pulse data acquisition module is a microprocessor that integrates the five basic components of the arithmetic unit, controller, memory, input and output interface and bus. Its memory is divided into two parts, one of which is the firmware memory, and the control programs of various functions of the network tanker are installed here. Even if the power is completely cut off, these programs will not be changed or lost; the working process of the tanker pulse data acquisition module includes signal filtering and amplification, analog-to-digital conversion, signal operation and output control, etc. BRIEF DESCRIPTION OF THE DRAWINGS
[0071] Figure 1 It is a network framework diagram of the present invention;
[0072] Figure 2 It is a flow chart of information synchronization between CPUs;
[0073] Figure 3 It is the flow chart of gateway data collection;
[0074] Figure 4 It is a fault diagnosis flow chart;
[0075] Figure 5 This is the CAN receiving data flow chart;
[0076] Figure 6 It is a flow chart of sending fault information;
[0077] Figure 7 It is a flow chart of the program between modules;
[0078] Figure 8 It is a system flow chart.
[0079] Marked in the figure are: CAN0 bus 101, CAN1 bus 102, gateway 103, tax control screen 201, solenoid valve controller 202, keyboard control board 203, multi-function display screen module 204, fuel dispenser main board module 205, pulse data acquisition module 206, oil and gas concentration sensor 207, temperature sensor 208, pressure sensor 209, liquid level meter 210, break valve 211, POS machine 212, oil and gas recovery control module 213, oil gun switch 214. DETAILED DESCRIPTION
[0080] like Figure 1-8As shown, a fuel dispenser self-diagnosis network system and an intelligent fuel dispenser include a CAN0 bus 101, a CAN1 bus 102, and a gateway 103; a multi-function display screen module 204, a fuel dispenser mainboard module 205, and a pulse data acquisition module 206 are connected through data bus communication, and are connected through CAN0 bus communication; the fuel dispenser mainboard module 205 is connected to the keyboard control board 203, the solenoid valve controller 202, and the tax control screen 201 through the CAN0 bus communication; the pulse data acquisition module 206, the fuel dispenser mainboard module 205, the oil and gas concentration sensor 207, the temperature sensor 208, the pressure sensor 209, the liquid level meter 210, the break valve 211, the POS machine 212, the oil and gas recovery control module 213, and a plurality of oil gun switches 214 are connected through the CAN1 bus communication.
[0081] The information synchronization steps between the CPUs of the multifunctional display screen module 204, the fuel dispenser mainboard module 205, and the pulse data acquisition module 206 are as follows:
[0082] S101, the gateway receives a flag setting signal sent by the CPU of the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module;
[0083] S102, determine whether the network system cycle timing is ≥500ms; if so, proceed to the next step, if not, the multi-function display module CPU reads the contents of the gateway data buffer register;
[0084] S103, the network system periodic timing reset; the gateway receives the module dial code sent by the CPU of the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module to the gateway; the register calculates the matching count;
[0085] S104, the gateway determines whether the CPU dial codes of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module are consistent and whether the dial code data is received; if so, proceed to the next step; if not, clear the register match count, and determine whether the match count is ≥7 and whether the dial code data is received. If so, the gateway receives the fault information and flag setting signal sent by the CPU of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module, and then feeds the system to let the multi-function display screen module CPU read the contents of the gateway data buffer register. If not, determine whether the match count is ≥7 and whether the dial code data is not received. If so, let the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module send the flag setting signal for the uplink and downlink data, and then initialize the receiving area of the CAN0 bus. The gateway checks the working mode. If not, let the system feed the dog and let the multi-function display screen module CPU read the contents of the gateway data buffer register.
[0086] S105, make the dial code compare and count correctly;
[0087] S106, determine whether the dial code comparison is correct and the count is ≥5; if so, proceed to the next step, if not, feed the system and let the multi-function display module CPU read the contents of the gateway data buffer register;
[0088] S107, reset the DIP fault light;
[0089] S108, the gateway determines whether the CPU dial code sending timing of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module is consistent; if so, proceed to the next step, if not, after the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module send uplink and downlink data flags are set, the receiving area of the CAN0 bus is initialized, and the gateway checks the working mode;
[0090] S109. The gateway determines whether it is a pulse data acquisition module. If so, the gateway confirms that the acquisition module is successfully synchronized, and then initializes the receiving area of the CAN0 bus, and the gateway checks the working mode; if not, the pulse data acquisition module sends the uplink and downlink data flag setting signal, and then initializes the receiving area of the CAN0 bus, and the gateway determines whether it is a fuel dispenser mainboard module; if so, the gateway confirms that the fuel dispenser mainboard module is successfully synchronized, and then initializes the receiving area of the CAN0 bus, and the gateway checks the working mode; if not, the fuel dispenser mainboard module sends the uplink and downlink data flag setting signal, and then initializes the receiving area of the CAN0 bus, and the gateway determines whether it is a multi-function display module; if so, the gateway confirms that the multi-function display module is successfully synchronized, and then initializes the receiving area of the CAN0 bus, and the gateway checks the working mode; if not, the multi-function display module sends the uplink and downlink data flag setting signal, and then initializes the receiving area of the CAN0 bus, and the gateway determines whether it is a multi-function display module.
[0091] The steps for gateway data collection are:
[0092] S201, the gateway periodically obtains data on the channel;
[0093] S202, compare the data saved in the previous cycle with the newly collected data to see if they are consistent; if not, proceed to the next step; if yes, determine whether data is sampled for 10 consecutive sampling cycles, if not, terminate, if yes, determine whether new data is sampled, if yes, set the register state, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light, if not, light up the corresponding fault light, send fault information and set the fault, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light;
[0094] S203, check whether the near-end line of the circuit is normal, if so, proceed to the next step, if not, determine whether data is sampled for 10 consecutive cycles, if not, terminate, if so, clear the corresponding collection count, clear the uplink and downlink line faults, and turn off the fault light when there is no collection fault;
[0095] S204, determine whether data is sampled for 10 consecutive cycles, if not, terminate, if yes, determine whether it is an uplink, if not, proceed to the next step, if it is an uplink, set the uplink fault, and then determine whether the uplink communication is normal, if not, terminate, if normal, send fault information, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light;
[0096] S205, determine whether it is a downlink line, if not, terminate; if it is a downlink line, set the downlink line fault, and then determine whether the downlink line communication is normal, if not, terminate; if normal, send fault information, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light.
[0097] The troubleshooting steps are:
[0098] S401, the gateway obtains the current working mode;
[0099] S402, the gateway performs fault detection on the uplink and downlink lines of the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module;
[0100] S403, set loop variable one J=0;
[0101] S404, determine whether J is less than 5; if not, proceed to the next step, if yes, determine whether the RS485 channel status is not 0x77; if the RS485 channel status is not 0x77, then when the cable transmission channel count is <255, the channel count is +1; when the cable transmission channel count is ≥255, the channel count is cleared, and then the channel count is set to 4 and a channel fault is sent, and then the loop variable J is incremented and then it is determined whether J is less than 5; if the RS485 channel status is 0x77, the pulse data acquisition module status information count is cleared, and then the loop variable J is incremented and then it is determined whether J is less than 5;
[0102] S405, clearing the pulse data acquisition module status information count;
[0103] S406, set loop variable one J=0;
[0104] S407, determine whether J is less than 3, if J ≥ 3, terminate, if J < 3, determine whether the pulse data acquisition module is normal and whether the sensor network has no faults; if so, increase J and then determine whether J is less than 3, if not, send an error code, and then increase J and then determine whether J is less than 3.
[0105] The steps for CAN0 bus and CAN1 bus to receive data are:
[0106] S501, determine whether it is CAN0 bus, if it is CAN0 bus, read CAN0 buffer data and proceed to the next step, if it is not CAN0 bus, determine whether it is CAN1 bus; if it is not CAN1 bus, proceed to the next step, if it is CAN1 bus, read CAN1 buffer data and proceed to the next step;
[0107] S502, read the IDs of other devices connected to the CAN0 bus or CAN1 bus except the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module;
[0108] S503, read device data;
[0109] S504, read the device number;
[0110] S505, determine whether the number is greater than 0 and less than 10; if not, terminate; if yes, proceed to the next step;
[0111] S506, reading the data of the device connected to the CAN0 bus and the data of the device connected to the CAN1 bus, reading the original data of the device, and performing corresponding processing;
[0112] S507: Compare fault information and send fault code and warning information.
[0113] The steps to send fault information to CAN0 bus and CAN1 bus are:
[0114] S601, determine whether the number of cache fault packets of the CPU registers of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module is ≤ 0, if so, the cache fault pointer assigns the write pointer to the read pointer and then terminates, if not, proceed to the next step;
[0115] S602, setting the ID number of the module connected to the CAN0 bus;
[0116] S603, reading data in the fault buffer area;
[0117] S604, sending fault information to the CAN1 bus according to the ID number;
[0118] S605, when the transmission to the CAN1 bus fails, the fault information is sent to the CAN0 bus according to the ID number;
[0119] S606, determine whether the transmission is successful, if not, terminate, if yes, set the fault buffer read pointer +6, when the fault data buffer read pointer ≥ 0x60, clear the read pointer, and the total number of packets -1, and then terminate.
[0120] The program flow between the multifunctional display screen module 204, the fuel dispenser main board module 205, and the pulse data acquisition module 206 is as follows:
[0121] S701, system initialization;
[0122] S702, variable initialization;
[0123] S703, loop variable (1) starts;
[0124] S704, the data received by UART is sent to the SPI buffer area;
[0125] S705, SPI data processing;
[0126] S706, SPI data is sent to the CAN0 bus buffer;
[0127] S707, the data packet received by the gateway is sent to the SPI;
[0128] S708, SPI loads data;
[0129] S709, gateway fault detection;
[0130] S710, UART fault detection;
[0131] S711, fuel dispenser host module and pulse data acquisition module periodic update;
[0132] S712: After feeding the dog, the system returns to S703.
[0133] The system process is:
[0134] S801, power on and start;
[0135] S802, initialization of each module;
[0136] S803, start the fuel dispenser program;
[0137] S804, start the fuel dispenser self-checking program;
[0138] S805, start the fuel dispenser fault code library;
[0139] S806, check whether the networking beacon is normal, if not, the APP window will prompt an error list, if normal, proceed to the next step;
[0140] S807, transmit threshold data and determine whether the test threshold is normal. If it is not normal, the APP window prompts an error list. If it is normal, perform information fusion processing; collect time data and determine whether the time is normal. If it is not normal, the APP window prompts an error list. If it is normal, perform information fusion processing;
[0141] S808, determine whether it is urgent, if it is urgent, make a voice announcement, if it is not urgent, proceed to the next step;
[0142] S809, self-test and service life data are stored locally in the fuel dispenser;
[0143] S810, self-inspection and service life data upload to APP and cloud analysis.
[0144] An intelligent fuel dispenser comprises the above-mentioned fuel dispenser self-diagnosis network system.
[0145] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention is described in detail with reference to the aforementioned embodiments, those skilled in the art can still modify the technical solutions described in the aforementioned embodiments or replace some of the technical features therein by equivalents. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.
Claims
1. A self-diagnosis network system for fuel dispensers, Features: Including CAN0 bus, CAN1 bus, gateway; The multifunctional display screen module, the fuel dispenser main board module, and the pulse data acquisition module are connected through data bus communication and CAN0 bus communication; the fuel dispenser main board module is connected to the keyboard control board, the solenoid valve controller, and the tax control screen through CAN0 bus communication; the pulse data acquisition module, the fuel dispenser main board module, the oil and gas concentration sensor, the temperature sensor, the pressure sensor, the liquid level meter, the breakaway valve, the POS machine, the oil and gas recovery control module, and several oil gun switches are connected through CAN1 bus communication; The information synchronization steps between the multi-function display screen module, the fuel dispenser main board module, and the CPU of the pulse data acquisition module are as follows: S101, the gateway receives a flag setting signal sent by the CPU of the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module; S102, determine whether the network system cycle timing is ≥500ms; if so, proceed to the next step, if not, the multi-function display module CPU reads the contents of the gateway data buffer register; S103, the network system periodic timing reset; the gateway receives the module dial code sent by the CPU of the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module to the gateway; the register calculates the matching count; S104, the gateway determines whether the CPU dial codes of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module are consistent and whether the dial code data is received; if so, proceed to the next step; if not, clear the register match count, and determine whether the match count is ≥7 and whether the dial code data is received. If so, the gateway receives the fault information and flag setting signal sent by the CPU of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module, and then feeds the system to let the multi-function display screen module CPU read the contents of the gateway data buffer register. If not, determine whether the match count is ≥7 and whether the dial code data is not received. If so, let the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module send the flag setting signal for the uplink and downlink data, and then initialize the receiving area of the CAN0 bus. The gateway checks the working mode. If not, let the system feed the dog and let the multi-function display screen module CPU read the contents of the gateway data buffer register. S105, make the dial code compare and count correctly; S106, determine whether the dial code comparison is correct and the count is ≥5; if so, proceed to the next step, if not, feed the system and let the multi-function display module CPU read the contents of the gateway data buffer register; S107, reset the DIP fault light; S108, the gateway determines whether the CPU dial code sending timing of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module is consistent; if so, proceed to the next step, if not, after the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module send uplink and downlink data flags are set, the receiving area of the CAN0 bus is initialized, and the gateway checks the working mode; S109, the gateway determines whether it is a pulse data acquisition module. If so, the gateway confirms that the acquisition module is synchronized successfully, and then initializes the receiving area of the CAN0 bus, and the gateway checks the working mode; if not, the pulse data acquisition module sends the uplink and downlink data flag setting signal, and then initializes the receiving area of the CAN0 bus, and the gateway determines whether it is a tanker mainboard module; if so, the gateway confirms that the tanker mainboard module is synchronized successfully, and then initializes the receiving area of the CAN0 bus, and the gateway checks the working mode; if not, the tanker mainboard module sends the uplink and downlink data flag setting signal, and then initializes the receiving area of the CAN0 bus, and the gateway determines whether it is a multi-function display screen module; If yes, the gateway confirms that the multi-function display screen module is synchronized successfully, and then initializes the receiving area of the CAN0 bus, and the gateway checks the working mode; if not, the multi-function display screen module sends uplink and downlink data flags, and then initializes the receiving area of the CAN0 bus, and the gateway determines whether it is a multi-function display screen module.
2. The fuel dispenser self-diagnosis network system according to claim 1, It is characterized in that The steps for gateway data collection are: S201, the gateway periodically obtains data on the channel; S202, compare the data saved in the previous cycle with the newly collected data to see if they are consistent; if not, proceed to the next step; if yes, determine whether data is sampled for 10 consecutive sampling cycles, if not, terminate, if yes, determine whether new data is sampled, if yes, set the register state, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light, if not, light up the corresponding fault light, send fault information and set the fault, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light; S203, check whether the near-end line of the circuit is normal, if so, proceed to the next step, if not, determine whether data is sampled for 10 consecutive cycles, if not, terminate, if so, clear the corresponding collection count, clear the uplink and downlink line faults, and turn off the fault light when there is no collection fault; S204, determine whether data is sampled for 10 consecutive cycles, if not, terminate, if yes, determine whether it is an uplink, if not, proceed to the next step, if it is an uplink, set the uplink fault, and then determine whether the uplink communication is normal, if not, terminate, if normal, send fault information, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light; S205, determine whether it is a downlink line, if not, terminate; if it is a downlink line, set the downlink line fault, and then determine whether the downlink line communication is normal, if not, terminate; if normal, send fault information, then clear the corresponding collection count, clear the uplink and downlink line faults, and when there is no collection fault, turn off the fault light.
3. The fuel dispenser self-diagnosis network system according to claim 1, It is characterized in that The troubleshooting steps are: S401, the gateway obtains the current working mode; S402, the gateway performs fault detection on the uplink and downlink lines of the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module; S403, set loop variable 1 J=0; S404, determine whether J is less than 5; if not, proceed to the next step, if yes, determine whether the RS485 channel status is not 0x77; If the RS485 channel status is not 0x77, when the cable transmission channel count is less than 255, the channel count is +1; when the cable transmission channel count is ≥255, the channel count is cleared, and then the channel count is set to 4 and a channel fault is sent, and then the loop variable J is incremented and then it is determined whether J is less than 5; if the RS485 channel status is 0x77, the pulse data acquisition module status information count is cleared, and then the loop variable J is incremented and then it is determined whether J is less than 5; S405, clearing the pulse data acquisition module status information count; S406, set loop variable one J=0; S407, determine whether J is less than 3, if J ≥ 3, terminate, if J < 3, determine whether the pulse data acquisition module is normal and whether the sensor network has no faults; if so, increase J and then determine whether J is less than 3, if not, send an error code, and then increase J and then determine whether J is less than 3.
4. The fuel dispenser self-diagnosis network system according to claim 1, It is characterized in that The steps for CAN0 bus and CAN1 bus to receive data are: S501, determine whether it is CAN0 bus, if it is CAN0 bus, read CAN0 buffer data and proceed to the next step, if it is not CAN0 bus, determine whether it is CAN1 bus; if it is not CAN1 bus, proceed to the next step, if it is CAN1 bus, read CAN1 buffer data and proceed to the next step; S502, read the IDs of other devices connected to the CAN0 bus or CAN1 bus except the multi-function display screen module, the fuel dispenser mainboard module, and the pulse data acquisition module; S503, read device data; S504, read the device number; S505, determine whether the number is greater than 0 and less than 10; if not, terminate; if yes, proceed to the next step; S506, reading the data of the device connected to the CAN0 bus and the data of the device connected to the CAN1 bus, reading the original data of the device, and performing corresponding processing; S507: Compare fault information and send fault code and warning information.
5. The fuel dispenser self-diagnosis network system according to claim 1, It is characterized in that The steps to send fault information to CAN0 bus and CAN1 bus are: S601, determine whether the number of cache fault packets of the CPU registers of the multi-function display screen module, the tanker mainboard module, and the pulse data acquisition module is ≤ 0, if so, the cache fault pointer assigns the write pointer to the read pointer and then terminates, if not, proceed to the next step; S602, setting the ID number of the module connected to the CAN0 bus; S603, reading data in the fault buffer area; S604, sending fault information to the CAN1 bus according to the ID number; S605, when the transmission to the CAN1 bus fails, the fault information is sent to the CAN0 bus according to the ID number; S606, determine whether the transmission is successful, if not, terminate, if yes, set the fault buffer read pointer +6, when the fault data buffer read pointer ≥ 0x60, clear the read pointer, and the total number of packets -1, and then terminate.
6. The fuel dispenser self-diagnosis network system according to claim 1, It is characterized in that The program flow between the multi-function display screen module, the fuel dispenser main board module, and the pulse data acquisition module is as follows: S701, system initialization; S702, variable initialization; S703, loop variable (1) starts; S704, the data received by UART is sent to the SPI buffer area; S705, SPI data processing; S706, SPI data is sent to the CAN0 bus buffer; S707, the data packet received by the gateway is sent to the SPI; S708, SPI loads data; S709, gateway fault detection; S710, UART fault detection; S711, fuel dispenser host module and pulse data acquisition module periodic update; S712: After feeding the dog, the system returns to S703.
7. The fuel dispenser self-diagnosis network system according to any one of claims 1 to 6, It is characterized in that The system process is: S801, power on and start; S802, initialization of each module; S803, start the fuel dispenser program; S804, start the fuel dispenser self-checking program; S805, start the fuel dispenser fault code library; S806, check whether the networking beacon is normal, if not, the APP window will prompt an error list, if normal, proceed to the next step; S807, transmit threshold data and determine whether the test threshold is normal. If it is not normal, the APP window prompts an error list. If it is normal, perform information fusion processing; collect time data and determine whether the time is normal. If it is not normal, the APP window prompts an error list. If it is normal, perform information fusion processing; S808, determine whether it is urgent, if it is urgent, make a voice announcement, if it is not urgent, proceed to the next step; S809, self-test and service life data are stored locally in the fuel dispenser; S810, self-inspection and service life data upload to APP and cloud analysis.
8. An intelligent fuel dispenser, It is characterized in that It includes the fuel dispenser self-diagnosis network system as described in claim 7.
