Unmanned aerial vehicle equipment identifier management system and method

Abstract

The invention discloses an unmanned aerial vehicle equipment identifier management system and method, and relates to the technical field of management systems. The system specifically comprises a configuration module which is used for sending a unique control signal to a plurality of different peripheral devices according to configuration information input by a user so as to distribute IDs when the devices are started; the monitoring module is used for receiving the ID information reported by the peripheral equipment, comparing the ID information with configuration information input by a user, and triggering a reconfiguration process or giving an alarm to prompt the user when configuration abnormity is found; and the storage module is used for storing the configured ID information and the associated state of the peripheral equipment so as to ensure that the peripheral equipment can operate normally in subsequent work. The invention aims to realize efficient, accurate and easy-to-implement identification and management of the same type of equipment of the unmanned aerial vehicle, simplify the production and installation process, and guarantee the stability and reliability of multi-equipment collaborative operation.

Description

Technical Field

[0001] The present invention relates to the technical field of management systems, and in particular to an identification and management system and method for unmanned aerial vehicle equipment. Background Art

[0002] With the rapid development of agricultural modernization, plant protection drones are increasingly used in agricultural production, especially in liquid operations such as pesticide spraying and irrigation and water replenishment. With their advantages of high efficiency, high precision and flexible operation, plant protection drones have greatly improved the level of intelligent agricultural operations. However, with the expansion of agricultural production scale and the increase in diversified demands, plant protection drones are also facing increasingly stringent technical challenges in terms of operating range and workload.

[0003] Traditional plant protection drones usually use a single spraying device to complete operations. For example, a water pump and a nozzle can meet basic needs. However, with the diversification of agricultural needs and the widespread use of drones in complex operating environments, this single-device operation mode has gradually exposed problems such as low efficiency and lack of adaptability. For example, in large-scale farmland operations, higher spraying efficiency, wider coverage, and more precise spraying effects are required. Therefore, more and more drones use a combination of multiple water pumps and multiple nozzles, such as a dual-pump four-nozzle or even a three-pump six-nozzle configuration, to cope with complex and diverse operational needs.

[0004] However, this way of multi-device collaborative operation also brings complexity to equipment management and configuration. In order to meet the needs of digital and intelligent development, each water pump and nozzle is usually designed as an independent intelligent device with independent identification information. For example, each nozzle has a unique device number (ID number) so that it can be distinguished and managed in the system. This design can achieve precise control and monitoring, improve spraying effect and work efficiency. However, in actual applications, in order to achieve the identification management of nozzle equipment, two methods are currently used: one is to distinguish the materials of each nozzle at the production end, such as numbering and identifying 6 nozzles with the same appearance, and distinguishing them by printing labels; the other is to automatically assign a unique ID to each nozzle after the equipment is installed through software. These two methods can solve the problem of nozzle identification to a certain extent, but there are still many problems in their implementation process. For example, the method of material distinction has a high degree of manual participation in the production and assembly process, which is easy to cause confusion in nozzle identification due to label printing errors, improper material management, etc.; and in the installation stage, the wrong installation position of the nozzle or inconsistent installation direction may also affect the normal operation of the nozzle. In addition, although the use of automatic software configuration reduces the need for material differentiation on the production side, in actual operation, it may still cause abnormal allocation of nozzle IDs due to equipment burning errors or other improper operations. The above problems may cause the system spraying effect to fail to meet the standards, or even cause serious operational accidents, seriously affecting the reliability and market promotion of agricultural drones.

[0005] Therefore, how to achieve efficient, accurate and easy-to-implement identification and management of similar drone equipment, simplify the production and installation process, and ensure the stability and reliability of collaborative operations of multiple devices has become a technical problem that needs to be urgently solved in the current development of plant protection drone spraying systems. Summary of the invention

[0006] The main purpose of the present invention is to provide a drone equipment identification management system and method, which aims to achieve efficient, accurate and easy-to-implement identification and management of drone equipment of the same type, simplify the production and installation process, and ensure the stability and reliability of collaborative operation of multiple devices.

[0007] In order to achieve the above object, the present invention proposes a drone equipment identification management system, comprising: A configuration module, used to send a unique control signal to a plurality of different peripheral devices to assign an ID according to the configuration information input by the user when the device is started; A monitoring module is used to receive the ID information reported by the peripheral device and compare it with the configuration information input by the user. When a configuration abnormality is found, a reconfiguration process is triggered or an alarm is issued to prompt the user; and The storage module is used to save the ID information of the peripheral device and its associated status after the configuration is completed to ensure that the peripheral device can operate normally in subsequent work.

[0008] In an embodiment of the present application, the plurality of different peripheral devices all have a default ID, and the default ID can be configured.

[0009] In one embodiment of the present application, the control signal is a signal with different pulse widths, and each peripheral device automatically updates its own ID according to the received pulse width signal.

[0010] In one embodiment of the present application, when the number of configuration failures of the monitoring module exceeds a preset number, an alarm message is triggered to remind the user to check.

[0011] The present application also discloses a method for managing drone equipment identification, comprising the following steps: S1: After starting the drone, read the user configuration information and the current status information of the peripheral devices; S2: Determine whether the number and status of the peripheral devices conform to the user configuration information; S3: If not, the control system sends different control signals to the peripheral device according to the user configuration information to assign a unique ID and count the number of configurations; S4: After receiving the control signal, the peripheral device updates its own ID and reports it, and repeats step S2.

[0012] In one embodiment of the present application, after the number of configurations is counted, the method further includes: Determine whether the current configuration times have reached the preset times. If so, trigger an alarm to prompt the user to check until the configuration is successful or the user corrects the configuration information.

[0013] In one embodiment of the present application, it is determined whether the number and status of the peripheral devices conform to the user configuration information. If so, no configuration is required.

[0014] By adopting the above technical solution, through the control signal distribution mechanism of the configuration module, there is no need to manually configure and identify the peripheral devices one by one, which reduces the complexity of manual operation. The unified initial setting of the default ID, combined with the automatic allocation function, realizes the rapid configuration of peripheral devices. The monitoring module can compare the configuration information with the reported information in real time and automatically determine whether the configuration is successful. When a configuration anomaly is detected, the system will actively trigger the reconfiguration process to avoid operation interruption or equipment failure caused by configuration errors. The design of the storage module enables the configuration information of the peripheral devices to be persisted. Even if the drone is started multiple times or the external environment changes, the system can quickly restore the configured device status, avoid repeated operations and improve the continuity and reliability of drone mission execution. When the device configuration fails, the system will prompt the user to check the source of the error through the alarm function, helping the user to quickly locate the problem, reducing maintenance time and resource consumption. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The present invention is described in detail below with reference to specific embodiments and accompanying drawings, wherein: Figure 1 is a structural diagram of the system of the present invention; Figure 2 It is a schematic diagram of the process structure of the method of the present invention. DETAILED DESCRIPTION

[0016] In order to make the purpose, technical solution and advantages of the present invention clearer, the present invention is described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the following specific embodiments are only used to explain the present invention and do not constitute a limitation to the present invention.

[0017] like Figure 1 As shown, in order to achieve the above purpose, the present invention proposes a drone equipment identification management system, comprising: A configuration module, used to send a unique control signal to a plurality of different peripheral devices to assign an ID according to the configuration information input by the user when the device is started; A monitoring module is used to receive the ID information reported by the peripheral device and compare it with the configuration information input by the user. When a configuration abnormality is found, a reconfiguration process is triggered or an alarm is issued to prompt the user; and The storage module is used to save the ID information of the peripheral device and its associated status after the configuration is completed to ensure that the peripheral device can operate normally in subsequent work.

[0018] Specifically, the configuration module is set in the drone control system, and its function is to assign a unique ID to the peripheral device by sending a unique control signal to the peripheral device. When the device starts, the configuration module reads the configuration information entered by the user, such as the number of specified peripheral devices and the desired ID configuration rules. Based on the information entered by the user, the configuration module sends a specific control signal to the control pin of each peripheral device, such as a PWM signal with different pulse widths (such as 100 microseconds, 200 microseconds, 300 microseconds, etc.) to distinguish the identity of the peripheral device. The peripheral device that receives the control signal will parse the signal, automatically set its own ID according to the signal content, and then report the assigned ID to the monitoring module.

[0019] The monitoring module receives the ID information reported by the peripheral devices in real time, and compares it with the configuration information entered by the user one by one. If the monitoring module detects that the number of IDs or the ID content of the peripheral devices does not match the configuration information entered by the user (for example, the user specifies 4 peripheral devices, but only 3 devices report ID information), the monitoring module will trigger the reconfiguration process. During the reconfiguration process, the configuration module will send a control signal again to reallocate the ID of the peripheral device. If the configuration process fails after multiple attempts (for example, three times), the monitoring module triggers an alarm, prompting the user to check the connection status of the peripheral device or the input configuration information, and displays an error message on the system interface.

[0020] The storage module is set in the storage hardware of the drone system. Its function is to save the ID information of the peripheral device and its associated operating status after the configuration is completed. After the configuration is completed, the storage module stores the ID of the peripheral device, the operating status of the device (such as normal or abnormal), and the connection information between the device and other parts of the drone as persistent data to ensure that each peripheral device can be correctly identified and operate normally during the subsequent operation of the drone. For example, when restarting the drone, the storage module directly provides the previously saved ID information to avoid repeating the configuration process.

[0021] By adopting the above technical solution, through the control signal distribution mechanism of the configuration module, there is no need to manually configure and identify the peripheral devices one by one, which reduces the complexity of manual operation. The unified initial setting of the default ID, combined with the automatic allocation function, realizes the rapid configuration of peripheral devices. The monitoring module can compare the configuration information with the reported information in real time and automatically determine whether the configuration is successful. When a configuration anomaly is detected, the system will actively trigger the reconfiguration process to avoid operation interruption or equipment failure caused by configuration errors. The design of the storage module enables the configuration information of the peripheral devices to be persisted. Even if the drone is started multiple times or the external environment changes, the system can quickly restore the configured device status, avoid repeated operations and improve the continuity and reliability of drone mission execution. When the device configuration fails, the system will prompt the user to check the source of the error through the alarm function, helping the user to quickly locate the problem, reducing maintenance time and resource consumption.

[0022] In an embodiment of the present application, the plurality of different peripheral devices all have a default ID, and the default ID can be configured.

[0023] Specifically, each peripheral device has the same default ID (for example, "ID No. 1") to facilitate initial identification and batch management of the system. The uniformity of the default ID eliminates the need to distinguish peripheral devices individually during procurement and storage, and all peripheral devices can be treated uniformly as standardized components. The configuration module modifies the default ID of the peripheral device by sending different control signals (for example, PWM signals with different pulse widths). When the device starts, the configuration module reads the configuration information entered by the user, and sends a unique control signal to the control pin of each peripheral device based on the number of peripheral devices actually required by the drone and the allocation rules. After receiving the control signal, the peripheral device will parse the signal content and modify its own default ID based on the analysis result, thereby completing the allocation of a unique ID.

[0024] When the system starts, the configuration module will first detect all connected peripheral devices and send control signals to all peripheral devices. If the default ID of the peripheral device has not been modified (that is, all devices are the default ID "No. 1"), the configuration module will send different signals in sequence, such as 100 microsecond pulse width corresponding to ID No. 2, 200 microsecond pulse width corresponding to ID No. 3, etc. The peripheral device modifies its own ID according to the received signal and reports the new ID information to the monitoring module. After the configuration is completed, the monitoring module will compare the reported ID information with the configuration information entered by the user to verify the correctness of the allocation result.

[0025] The monitoring module is responsible for real-time monitoring of the ID reporting information of peripheral devices during the entire configuration process to ensure that all peripheral devices can successfully complete the ID modification. If the monitoring module finds that there are still peripheral devices that have not completed the ID modification, it will notify the configuration module to resend the control signal until the configuration is successful or the number of configuration attempts is exceeded. The successfully assigned ID information and peripheral device status are persistently stored by the storage module so that they can be directly called in subsequent work to avoid repeated configuration.

[0026] In some cases (such as abnormal peripheral device connection or configuration signal not received correctly), the monitoring module detects that the number of reported IDs does not match the configuration requirements entered by the user, and an alarm will be triggered to prompt the user to check the device connection or re-enter the configuration requirements.

[0027] By adopting the above technical solution and the unified design of the default ID, peripheral devices do not need to be distinguished by model or number during procurement, transportation and storage, which simplifies the management process. The monitoring module compares the configuration information entered by the user with the ID information reported by the peripheral device in real time to ensure that the configuration of the peripheral device is accurate. When an abnormality occurs, the system can trigger reconfiguration or alarm prompts in time to reduce the possibility of operation failure.

[0028] In one embodiment of the present application, the control signal is a signal with different pulse widths, and each peripheral device automatically updates its own ID according to the received pulse width signal.

[0029] Specifically, when the device is started, the configuration module generates multiple control signals with different pulse widths according to the configuration information input by the user. For example, if the user specifies that 4 peripheral devices need to be managed, the configuration module generates pulse width signals of 100 microseconds, 200 microseconds, 300 microseconds and 400 microseconds respectively, and sends the control signals to the control pins of the peripheral devices through their respective output channels. The pulse width of the signal corresponds to the target ID assigned to the peripheral device one by one, for example, 100 microseconds corresponds to ID 1, 200 microseconds corresponds to ID 2, and so on.

[0030] By adopting the above technical solution, by using control signals with different pulse widths, each peripheral device can accurately parse the corresponding target ID according to the received signal, realize automatic ID allocation, and avoid configuration errors that may be caused by manual intervention.

[0031] In one embodiment of the present application, when the number of configuration failures of the monitoring module exceeds a preset number, an alarm message is triggered to remind the user to check.

[0032] Specifically, during the configuration process, the monitoring module receives the ID information reported by the peripheral device and compares it with the configuration information entered by the user one by one to verify the correctness of the configuration result. If the peripheral device does not report new ID information as expected, or the reported ID information does not match the target ID, the monitoring module will determine that the current configuration has failed, and immediately notify the configuration module to resend the control signal to trigger the next round of configuration process.

[0033] The monitoring module sets a failure counter inside to record the number of consecutive configuration failures. Each time the configuration module completes a round of control signal transmission, the monitoring module compares the results and updates the counter. If the configuration is successful, the counter is cleared; if the configuration fails, the counter is incremented. The counter is compared with the preset maximum number of failures (for example, 3 times). When the counter value exceeds the preset number, the monitoring module determines that the configuration has failed and terminates the automatic retry.

[0034] After the preset number of configuration failures is exceeded, the monitoring module generates an alarm message and issues a prompt to the user through the user interface. The alarm message includes the specific cause of the failure (such as abnormal connection, peripheral device response timeout, etc.) and the recommended solution (such as checking device connection, re-entering configuration information). The alarm message can notify the user in a variety of ways, such as graphical interface prompts, sound alarms, or sending messages through the remote monitoring system.

[0035] By adopting the above technical solution, through the configuration failure detection and retry mechanism of the monitoring module, the system can try to complete the ID configuration multiple times, minimize the configuration failure caused by accidental factors (such as signal interference or device response delay), and improve the reliability of the configuration process.

[0036] like Figure 2 As shown, the present application also discloses a method for managing drone equipment identification, comprising the following steps: S1: After starting the drone, read the user configuration information and the current status information of the peripheral devices; S2: Determine whether the number and status of the peripheral devices conform to the user configuration information; S3: If not, the control system sends different control signals to the peripheral device according to the user configuration information to assign a unique ID and count the number of configurations; S4: After receiving the control signal, the peripheral device updates its own ID and reports it, and repeats step S2.

[0037] Specifically, after starting the drone, the flight control system of the drone is powered on and starts running. The flight control system first reads the pre-stored user configuration information. The user configuration information includes the target number of peripheral devices, function allocation and corresponding configuration requirements. At the same time, the flight control system obtains the current status information of the peripheral devices through the communication interface, including the current number of peripheral devices and their unique identifiers. For example, the default identifier of the peripheral device in the initial state is No. 1, such as No. 1 nozzle and No. 1 water pump.

[0038] After obtaining the user configuration information and the current status information of the peripheral devices, the flight control system determines whether the number and status of the peripheral devices are consistent with the user configuration information. If the number and status of the peripheral devices are consistent with the user configuration information, no configuration is required, and the system enters the standby state and prepares to perform subsequent operations.

[0039] If the number or status of the peripheral device is inconsistent with the user configuration information, the configuration process will be entered. The flight control system sends control signals to the peripheral devices one by one according to the user configuration information to assign unique identifiers. Specifically, the flight control system sends control signals according to the following rules based on the target number of peripheral devices and their configuration requirements: Send a 100 microsecond PWM pulse width signal to the pin that controls peripheral device No. 1; Send a 200 microsecond PWM pulse width signal to the pin that controls peripheral device No. 2; Send a 300 microsecond PWM pulse width signal to the pin that controls peripheral device No. 3; Send a 400 microsecond PWM pulse width signal to the pin that controls peripheral device No. 4, and so on.

[0040] After receiving the corresponding PWM pulse width signal, the peripheral device automatically updates its own unique identifier to the number corresponding to the control signal, and reports the updated unique identifier and status information to the flight control system through the communication interface.

[0041] After receiving the reported information from all peripheral devices, the flight control system will determine again whether the number and status of the peripheral devices are consistent with the user configuration information. If they are consistent, the configuration is successful, the system exits the configuration process and enters the standby state. If they are still inconsistent, the flight control system will re-enter the configuration process and resend the control signal to try to complete the configuration again.

[0042] This configuration process is attempted multiple times. For the sake of convenience, this application takes three attempts as an example. This configuration process is attempted up to three times. If all three attempts fail, the flight control system will determine that the configuration has failed, and issue a warning to the user through a display device or an alarm device, prompting the user to check whether the number and status of the peripheral devices are correct, and reminding the user to reconfirm or modify the user configuration information. If the user powers on again after the modification, the drone will enter the configuration process again until the configuration is successful.

[0043] By adopting the above technical solution, the method avoids the problem of confusion and repeated configuration of peripheral devices by allocating unique identifiers, simplifies the installation and management process of peripheral devices, and improves the accuracy and automation level of configuration. By setting a predetermined attempt limit, it not only improves the configuration efficiency, but also provides users with clear fault prompts.

[0044] In one embodiment of the present application, after the number of configurations is counted, the method further includes: Determine whether the current configuration times have reached the preset times. If so, trigger an alarm to prompt the user to check until the configuration is successful or the user corrects the configuration information.

[0045] Specifically, during the configuration process, the flight control system will also count the number of attempts for the current configuration. If it is found during the configuration process that the number or status of the peripheral devices does not conform to the user configuration information, and the number of configuration attempts has not reached the preset maximum number (for example, 3 times), the flight control system will continue with the next round of configuration attempts. If the number of configuration attempts reaches the preset maximum number, the flight control system triggers an alarm and prompts the user to check. At this time, the flight control system will display a warning message to the user, informing the user that the configuration of the peripheral device failed, and the user needs to check whether the peripheral device is correctly connected or confirm whether the user configuration information is accurate. If the user does not correct the configuration information, the flight control system will re-execute the configuration process each time it is started, and an alarm will pop up to remind you.

[0046] If the user corrects the configuration information and restarts the drone, the flight control system will re-enter the configuration process until the configuration is successful.

[0047] By adopting the above technical solution, the method ensures the accurate matching of peripheral devices and user configuration information by allocating unique identifiers, avoids the confusion of peripheral devices, simplifies the configuration process of drone devices, and improves the automation and accuracy of device management. Setting the configuration attempt limit and alarm mechanism not only improves the configuration efficiency, but also enhances the operability of troubleshooting, ensuring that the configuration of drone peripheral devices can be completed quickly and accurately.

[0048] In one embodiment of the present application, it is determined whether the number and status of the peripheral devices conform to the user configuration information. If so, no configuration is required.

[0049] By adopting the above technical solution, the process is simple and easy to implement.

[0050] The above description is only a preferred embodiment of the present invention, and does not limit the patent scope of the present invention. All equivalent structural changes made by using the contents of the present invention specification and drawings under the inventive concept of the present invention, or directly / indirectly applied in other related technical fields are included in the patent protection scope of the present invention.

Claims

1. A drone equipment identification management system, characterized in that: include: A configuration module, used to send a unique control signal to a plurality of different peripheral devices to assign an ID according to the configuration information input by the user when the device is started; The monitoring module is used to receive the ID information reported by the peripheral device and compare it with the configuration information input by the user. When a configuration abnormality is found, the reconfiguration process is triggered or an alarm is issued to prompt the user; as well as The storage module is used to save the ID information of the peripheral device and its associated status after the configuration is completed to ensure that the peripheral device can operate normally in subsequent work.

2. The unmanned aerial vehicle equipment identification management system according to claim 1, characterized in that: The plurality of different peripheral devices all have a default ID, and the default ID can be configured.

3. The unmanned aerial vehicle equipment identification management system according to claim 1, characterized in that: The control signal is a signal with different pulse widths, and each peripheral device automatically updates its own ID according to the received pulse width signal.

4. The unmanned aerial vehicle equipment identification management system according to claim 1, characterized in that: When the number of configuration failures of the monitoring module exceeds a preset number, an alarm message is triggered to remind the user to check.

5. A method for managing drone equipment identification, characterized in that: The following steps are involved: S1: After starting the drone, read the user configuration information and the current status information of the peripheral devices; S2: Determine whether the number and status of the peripheral devices conform to the user configuration information; S3: If not, the control system sends different control signals to the peripheral device according to the user configuration information to assign a unique ID and count the number of configurations; S4: After receiving the control signal, the peripheral device updates its own ID and reports it, and repeats step S2.

6. The method for managing the identification of unmanned aerial vehicle equipment according to claim 5, characterized in that: After the configuration times are counted, it also includes: Determine whether the current configuration times have reached the preset times. If so, trigger an alarm to prompt the user to check until the configuration is successful or the user corrects the configuration information.

7. The method for managing the identification of unmanned aerial vehicle equipment according to claim 5, characterized in that: Determine whether the number and status of the peripheral devices conform to the user configuration information. If so, no configuration is required.

Images