DESC:

FORM 2

THE PATENTS ACT, 1970 (39 of 1970)
&

THE PATENT RULES, 2003

COMPLETE SPECIFICATION

(See Section 10 and Rule 13)

Title of Invention:

A SYSTEM AND METHOD FOR PREFLIGHT SANITY CHECK IN UAV

APPLICANT:

AARAV UNMANNED SYSTEMS PRIVATE LIMITED

An Indian entity having address as:
#3, 80 Feet Main Road, MCHS Layout, Jakkur,
Bangalore - 560064

The following specification particularly describes the invention and the manner in which it is to be performed.

CROSS-REFERENCE TO RELATED APPLICATIONS AND PRIORITY
The present application claims priority from the Indian patent application, having application number 202241059954, filled on 20th October 2022, incorporated herein by a reference.
TECHNICAL FIELD
The present disclosure relates to the system and method for preflight check in unmanned aerial vehicles (UAV). More specifically, the present disclosure relates to the preflight sanity check for certain components in UAV before mission.
BACKGROUND
The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also correspond to implementations of the claimed technology.
The UAV is an aerial vehicle with no pilot-to-man controls. They can be remotely controlled by personnel on the ground or by pre-programmed flight plans. Of late, the UAVs have become increasingly more sophisticated, and the term UAV has been changed to UAS, an acronym for Unmanned Aircraft System. The change amplifies the fact that apart from being an aerial vehicle, this complex system includes ground stations, satellite connectivity, sometimes onboard weapons, and other components. Militarily these systems are gaining tremendous importance, as they can conduct precision strikes on faraway targets without collateral damage.
The initial generation of UAVs were primarily used for surveillance. With increased operational requirements they were armed, and they became known as Unmanned Combat Aerial Vehicles (UCAVs). Broadly military UAVs are used for surveillance, farming, artillery firing, gathering Electronic Intelligence (ELINT) information, lasing targets for fighter aircraft and Post strike Damage Assessment (PSDA).
UAV technology has advanced rapidly over the years and are now being used for various purposes, including photography, videography, surveying, mapping, and more. As UAV technology advances, the number of applications will continue to grow. It’s quite evident that UAVs have helped different sectors improve research, productivity, and risk mitigation in their respective operations. Because UAVs are operating in airspace alongside other manned aircraft, often with passengers, and in and around other objects and humans, they can pose a threat to life and property if they are operated with uncertified or incompatible or untested software or hardware, and they can pose a further threat if the UAV is hacked or taken over by an unauthorized person with nefarious purposes. Since unmanned and beyond-line-of- sight UAVs may be operated in a fully autonomous mode with no direct human interaction, a system is needed to assure that the UAV's working components, software and hardware are working properly and ready for mission, so that the UAV can be trusted to operate in airspace.
Therefore, there exists a long-standing need to provide a system and method for preflight sanity check of an unmanned aerial vehicle (UAV) components to overcome the above-mentioned problems.

SUMMARY
The present disclosure overcomes one or more shortcomings of the prior art and provides additional advantages discussed throughout the present disclosure. Additional features and advantages are realized through the techniques of the present disclosure. Other embodiments and aspects of the disclosure are described in detail herein and are considered a part of the claimed disclosure.
The present disclosure has been made in order to solve the problems, and it is an object of the present disclosure to provide a system and method for preflight sanity check an unmanned aerial vehicle (UAV) component before mission.
In one implementation of the present disclosure, a system for prefight sanity check of an unmanned aerial vehicle (UAV) components is disclosed. The system may comprise an unmanned aerial vehicle (UAV) and a ground control station (GCS). The ground control station (GCS) is communicatively coupled with the plurality of UAV components via a wired or a wireless communication channel. The UAV may comprise a plurality of UAV components including a battery, a camera, a global positioning system (GPS), a radio controller (RC), a magnetometer or a compass. Further, a plurality of sensors may be associated with the plurality of UAV components. The GCS may be configured for receiving preflight data of UAV comprising battery data, camera data, GPS data, RC data, Magnetic Field data, logger data and home location and distance data captured via the plurality of sensors associated with the plurality of UAV components to store a corresponding predetermined data in the absence of errors. Further, the GCS may be configured for transmitting a first mission command to the UAV to start planning a mission. The GCS may be configured to transmit a signal to the UAV for performing a pre-flight sanity check after the completion of planning of the mission. The GCS may be configured for receiving the pre-flight data of UAV captured via the plurality of sensors associated with the plurality of UAV components. The GCS may be comparing the received preflight data with the corresponding predetermined data stored in the GCS to perform a preflight sanity check. The GCS may be configured for detecting errors present in the plurality of UAV components based on preflight sanity check. The GCS may be configured for transmitting a second mission command to the UAV based on detected errors.
In one implementation of the present disclosure, a method for prefight sanity check of an unmanned aerial vehicle (UAV) components is disclosed. The method may comprise a step of receiving, via a ground control station (GCS), a preflight data of UAV comprising battery data, camera data, GPS data, RC data, Magnetic Field data, logger data and home location and distance data captured via the plurality of sensors associated with the plurality of UAV components to store a corresponding predetermined data in the absence of errors. The method may comprise a step of transmitting, via the GCS, a first mission command to the UAV to start planning of the mission. The method may comprise step of transmitting, via the GCS, a signal to the UAV for performing a preflight sanity check after the completion of planning of the mission. The method may comprise step of receiving, via the GCS, the preflight data of UAV captured via the plurality of sensors associated with the plurality of UAV components. The method may comprise step of comparing, via the GCS, the received preflight data with the corresponding predetermined data stored in the GCS to perform a preflight sanity check. The method may comprise step of detecting, via the GCS, errors present in the plurality of UAV components based on preflight sanity checks. The method may comprise step of transmitting, via the GCS, a second mission command to the UAV based on the detected errors.
The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description.
BRIEF DESCRIPTION OF DRAWINGS
The detailed description is described with reference to the accompanying Figures. In the Figures, the left-most digit(s) of a reference number identifies the Figure in which the reference number first appears. The same numbers are used throughout the drawings to refer like features and components.
Figure 1 illustrates a network implementation of a system (100) for a preflight sanity check of an unmanned aerial vehicle (UAV) components, in accordance with an embodiment of the present disclosure.
Figure 2 illustrates components of a ground control station (GCS) (103), in accordance with the embodiment of the present disclosure.
Figure 3 illustrates a method (300) for a preflight sanity check of UAV components, in accordance with the embodiment of the present disclosure.
Figure 4a-4b illustrates a method flow chart (400) of a step-wise working of the preflight sanity check of the UAV components (104) using the GCS application, in accordance with the exemplary embodiment of the present disclosure.
DETAILED DESCRIPTION
The terms “comprise”, “comprising”, “include(s)”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, system or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or system or method. In other words, one or more elements in a system or apparatus preceded by “comprises” does not, without more constraints, preclude the existence of other elements or additional elements in the system or apparatus.
Reference throughout the specification to “various embodiments,” “some embodiments,” “one embodiment,” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in various embodiments,” “in some embodiments,” “in one embodiment,” or “in an embodiment” in places throughout the specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
Now referring to Figure. 1, a network implementation of the system (100) for a preflight sanity check of UAV components, is illustrated. The system (100) may comprise an Unmanned Aerial Vehicle (UAV) (101) and a ground control station (GCS) (103). The UAV (101) may comprise a plurality of UAV components (104).
In one embodiment, the plurality of UAV components may include but is not limited to, a battery, a camera, a global positioning system (GPS), a radio controller (RC), a memory/SD card and a magnetometer or compass. Further, a plurality of sensors may be associated with the plurality of UAV components. The UAV (101) and the GCS (103) may be communicatively coupled with a wireless communication channel.
The plurality of UAV components (104) may play an important role in maintaining the UAV mission smooth and problem-free. In one embodiment, the battery may be configured to maintain the efficient voltage and current required for operating a UAV (101). In one embodiment, the camera may be configured for collecting pictorial data of the field during the mission of the UAV (101). In one embodiment, the GPS may be configured for locating the UAV (101) by maintaining proper longitude and latitude with the help of proper satellite count. In one embodiment, the compass or magnetometer may be configured for navigation of the UAV (101) by maintaining a magnetic field data. The magnetic field data may comprise roll, pitch, and yaw and heading of compass related to the UAV. In one embodiment, the logger may be used for integrating various types of payloads. The home location and distance data may be used for bringing the UAV (101) back to the launch location. The RC may be configured for proper launch and control of the UAV (101) during the mission.
The plurality of sensors associated with the plurality of UAV components may be configured for capturing a preflight data of UAV comprising battery data, camera data, GPS data, RC data, Magnetic Field data, logger data and home location and distance data. The GCS (103) may be configured for storing the preflight data as corresponding predetermined data in the absence of errors.
In yet another embodiment, the UAV (101) and the GCS (103) may communicate with each other via the network (102). In one implementation, the network (102) may be a wireless network, a wired network, or a combination thereof. The network (102) can be implemented as one of the different types of networks, such as intranet, local area network (LAN), wide area network (WAN), the internet, and the like. The network (102) may either be a dedicated network or a shared network. The shared network represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), and the like, to communicate with one another. Further, the network (102) may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, and the like.
In another embodiment, the network (102) may include any one of the following: a cable/wired network, a wireless network, a telephone network (e.g., Analog, Digital, POTS, PSTN, ISDN, xDSL), a cellular communication network, a mobile telephone network (e.g., CDMA, GSM, NDAC, TDMA, E-TDMA, NAMPS, WCDMA, CDMA-2000, UMTS, 3G, 4G, 5G, 6G), a radio network, a television network, the Internet, the intranet, the local area network (LAN), the wide area network (WAN), an electronic positioning network, an X.25 network, an optical network (e.g., PON), a satellite network (e.g., VSAT), a packet-switched network, a circuit-switched network, a public network, a private network, and/or other wired or wireless communications network configured to carry data.
Referring to Figure 2, components of the GCS (103) are illustrated, in accordance with an embodiment of the present subject matter. The GCS (103) may be computer or user device associated with an operator. Examples of the GCS (103) may include, but are not limited to, a touch device, a smart device, a portable device, a portable computer, a personal digital assistant, a handheld device, mobile phone, tablet, laptop and a workstation.
In one embodiment, the GCS (103) may include at least one processor (201), an input/output (I/O) interface (202), and a memory (203). The at least one processor (201) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions or the like. Among other capabilities, at least one processor (201) is configured to fetch and execute computer-readable instructions stored in the memory (203).
The I/O interface (202) may include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like. The I/O interface (202) may allow the UAV (101) to interact with a user directly or through the GCS (103). Further, the I/O interface (202) may enable the network (102) to communicate with other computing devices, such as web servers and external data servers (not shown), cloud. The I/O interface (202) can facilitate multiple communications within a wide variety of networks and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite. The I/O interface (202) may include one or more ports for connecting a number of devices to one another or to another server. In one embodiment, the I/O interface (202) allows the UAV (101) to be logically coupled to GCS (103), some of which may be built in. Illustrative components include tablets, mobile phones, scanners, printers, wireless devices, etc.
The memory (203) may include any computer-readable medium known in the art including, for example, volatile memory, such as static random-access memory (SRAM) and dynamic random-access memory (DRAM), and/or non-volatile memory, such as read-only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, magnetic tapes, and the like. The memory (203) may be removable, non-removable, or a combination thereof. The memory (203) may include routines, programs, objects, components, data structures, etc., which perform particular tasks or implement particular abstract data types. The memory (203) may include modules (204) and data (207). In one embodiment, the modules (204) include routines, programs, objects, components, data structures, etc., which performs particular task, functions or implement particular abstract data types. In one implementation, the modules (204) may include a comparison module (205) and an error detection module (206).
In one embodiment, the GCS (103) may be configured for receiving a preflight data of UAV. In an exemplary embodiment, the preflight data of (UAV) may comprise battery data, camera data, GPS data, RC data, Magnetic Field data, logger data and home location and distance data captured via the plurality of sensors associated with the plurality of UAV components. The GCS (103) may be configured to store a predetermined data including battery data, camera data, GPS data, RC data, Magnetic Field data, logger data and home location and distance data in the absence of errors.
In one embodiment, the battery data may comprise battery current and battery voltage. The camera data may comprise pulse and triggers emitted by the camera. The GPS data may comprise a satellite count. The Magnetic field data may comprise roll, pitch, yaw, and heading of the compass related to the UAV. The logger data may comprise payloads, GPS data, and camera log files. The home location and distance data may comprise latitude and longitude data for the UAV. The RC data may comprise minimum, maximum, and trim control values for UAV flight control.
In one embodiment, the GCS (103) may be configured to transmit a first mission command to the UAV to start planning of the mission. Further, the GCS (103) may be configured to transmit a signal to UAV for performing preflight sanity check after completion of planning of mission.
After completion of planning of the mission, the GCS (103) may be configured for receiving the preflight data of UAV captured via the plurality of sensors associated with the plurality of UAV components (104).
In one embodiment, the GCS (103) may comprise the comparison module (205) to compare the received preflight data with the corresponding predetermined data stored in the GCS (103) to perform preflight sanity check.
In one embodiment, the comparison module (205) may compare real-time data received from the plurality of sensors associated with the plurality of UAV components with the predetermined data stored within the GCS (103). Further, the error detection module (206) may be configured to detect errors present in the plurality of UAV components based on preflight sanity check.
In one embodiment, the comparison module (205) may be configured to compare the current battery voltage and current with a predetermined battery voltage and current stored in the GCS (103). The error detection module (206) may be configured to detect a low battery error, if the received battery data is below the predetermined battery current and battery voltage. The GCS may be configured for indicating a low battery error to a user associated with the GCS.
In one embodiment, the comparison module (205) may be configured to compare the current camera pulse and triggers may be compared with the predetermined camera pulse and triggers stored in the GCS (103). The error detection module (206) may be configured to detect camera error if the received camera data differs from the predetermined camera pulse and triggers. The GCS (103) may be configured for indicating a camera error to the user associated with the GCS (103).
In one embodiment, the comparison module (205) may be configured to compare received satellite counts with a predetermined satellite counts stored in the GCS (103). The error detection module (206) may be configured to detect a GPS signal weakness error if the received satellite count is lower than the predetermined satellite count. The GCS (103) may be configured for indicating the GPS signal weakness error to the user associated with the GCS (103).
In one embodiment, the comparison module (205) may be configured to compare received Magnetic field data with a predetermined Magnetic field data stored in the GCS (103). The error detection module (206) may be configured to detect a calibration error of the compass or magnetometer if the received Magnetic field data differs from the predetermined Magnetic field data. The GCS (103) may be configured for indicating the calibration error of the compass or magnetometer to the user associated with the GCS (103).
In one embodiment, the comparison module (205) may be configured to compare the received logger data with a predetermined logger data stored in the GCS (103). The error detection module (206) may be configured to detect an inconsistency error in the logger data if the received logger data differs from the predetermined logger data. The GCS (103) may be configured for indicating the inconsistency error in the logger data to the user associated with the GCS (103).
In one embodiment, the comparison module (205) may be configured to compare the received home location and distance data with a predetermined home location and distance data stored in the GCS (103). The error detection module (206) may be configured to detect a home location and distance error if the received home location and distance data differs from the predetermined home location and distance data. The GCS (103) may be configured for indicating the home location and distance error to the user associated with the GCS (103).
In one embodiment, the comparison module (205) may be configured to compare the received the RC data with a predetermined RC data stored in the GCS (103). The error detection module (206) may be configured detect a control error, if the received control values differ from the predetermined RC data. The GCS (103) may be configured for indicating the control error to the user associated with the GCS (103).
In one embodiment, the GCS (103) may be configured for transmitting a second mission command to the UAV based on a plurality of checks corresponding to the plurality of the UAV components (104) checked. In one embodiment, the plurality of checks may be displayed on a user interface (UI) of the GCS (103) and checked based on the detected errors.
In one embodiment, the second mission command may be selected from a take-off mission command in case of zero errors present in the plurality of UAV components, and stop mission and fix error command in case of error present in the at least one UAV component of the plurality of UAV component.
In one embodiment, GCS (103) may be configured for providing step-by-step instructions or suggestions to the user associated with the GCS to resolve or fix the detected errors based on a type of error detected in each UAV component of the plurality of UAV components.
Referring to Figure. 3, a method (300) for prefight sanity checks of an unmanned aerial vehicle (UAV) components (104) is disclosed.
At step (301), the GCS (103) may receive preflight data of the UAV, including battery data, camera data, GPS data, RC data, Magnetic Field data, logger data, and home location and distance data. This data may be captured via the plurality of sensors associated with the UAV components (104) and may be stored as corresponding predetermined data in the absence of errors.
At step (302), the GCS (103) may transmit a first mission command to the UAV to initiate mission planning.
At step (303), after the completion of mission planning, the GCS (103) may send a signal to the UAV (101) to perform a preflight sanity check.
At step (304), the GCS (103) may receive the preflight data of the UAV (101), captured via the plurality of sensors associated with the UAV components (104).
At step (305), the GCS (103) may compare the received preflight data with the corresponding predetermined data stored in the GCS (103) to perform a preflight sanity check.
At step (306), the GCS (103) may detect errors present in the plurality of UAV components (104) based on the preflight sanity check.
At step (307), the GCS (103) may transmit a second mission command to the UAV based on a plurality of checks corresponding to the plurality of the UAV components (104) checked the detected errors. The plurality of checkboxes may be displayed on the user interface (UI) of the GCS (103) and checked based on the detected errors.
Now referring to Figure 4(a) and 4(b), a method flow chart of a step-wise working of the preflight sanity check of the UAV components (104) using GCS application before a mission, is illustrated, in accordance with an exemplary embodiment of the present subject matter. The method may include the following steps:
Step (401): Starting of the GCS application installed on a user device.
Step (402): connecting the UAV and GCS application through a wired or a wireless communication.
Step (403): The GCS receives Messages through the wired or the wireless communication channel from UAV based on data captured via the plurality of sensors associated with the plurality of UAV components. The GCS shows no error for the values need to fetch parameters of the plurality of UAV components again.
Step (404): Storing of fetched data in GCS
The GCS (103) may store the fetched data from the plurality UAV components (104). The stored data may comprise the preflight data of UAV comprising battery data, camera data, GPS data, RC data, Magnetic Field data, logger data and home location and distance data captured via the plurality of sensors associated with the plurality of UAV components to store a corresponding predetermined data in the absence of errors utilized for later use.
Step (405): Sending mission to the UAV
After storing the preflight data in the data storage unit the GCS (103) may send a mission command to the UAV (101).
Step (406): Starting of mission
After receiving mission command from the GCS (103), the UAV (101) starts planning of mission.
Step (407): Preflight sanity check
After completion of mission planning and before the start of the mission, the GCS (103) may signal the UAV (101) to undergo a preflight sanity check. During preflight sanity check the UAV component (104) may send data to GCS (103) for comparison. The comparison may be as follows:
Battery: comparing current battery data with the stored battery data in GCS;
GPS: comparing current GPS data with the stored GPS data in GCS;
RC: comparing current RC data with the stored RC data in GCS;
Camera: comparing current camera data with the stored camera data in GCS;
HOME: comparing current home data with the stored home data in GCS;
Magnetic field: comparing current Magnetic field data with the stored Magnetic field data in the GCS;
Logger: comparing current Logger data with the stored Logger data in GCS;
Step (408): checks against preflight checks for the plurality of UAV components of the UAV
The GCS checks a pre-flight check corresponding to the plurality of the UAV components (104). During checking, if there are any difference or unsafe output displayed on the user interface, GCS (103) may stop the mission and may ask the operator to fix the problem. In one embodiment, the GCS a pre-flight check list or checkboxes may be displayed on the user interface of the GCS.
Step (409): Aim and take off
If there are no difference or safe output displayed on the user interface, then GCS (103) may send take off command to the UAV(101). The output displayed on the user interface of the GCS (103) is the comparison between current and stored data of the UAV components (104). The GCS transmit the second mission command aim and take-off mission command in case of zero errors present in the plurality of UAV components.
The presently disclosed system and method for preflight sanity check of UAV components (104) before mission may have the following advantageous functionalities on the conventional art:
? To maintain smooth UAV mission.
? To avoid crash or accident of the UAV.
? To prevent any failure of UAV component during mission.
? To avoid unexpected comeback of UAV in the middle of mission.
? To avoid failure of mission due to shortage of pictorial data.
? To avoid dislocation or crash of the UAV during mission due to lost satellite network or compass issue.
? To integrate optimum payload during mission.
? To avoid hard landing of UAV in an unexpected location.
? To avoid sudden jerk during takeoff and loss of control during landing due to low RC value.
Various modifications to the embodiment will be readily apparent to those skilled in the art and the generic principles herein may be applied to other embodiments. However, one of ordinary skill in the art will readily recognize that the present disclosure is not intended to be limited to the embodiments illustrated but is to be accorded the widest scope consistent with the principles and features described herein.
The foregoing description shall be interpreted as illustrative and not in any limiting sense. A person of ordinary skill in the art would understand that certain modifications could come within the scope of this disclosure.
The embodiments, examples and alternatives of the preceding paragraphs or the description and drawings, including any of their various aspects or respective individual features, may be taken independently or in any combination. Features described in connection with one embodiment are applicable to all embodiments unless such features are incompatible.

,CLAIMS:WE CLAIM:
1. A system (100) for prefight sanity check of an unmanned aerial vehicle (UAV) components (104), wherein the system (100) comprising:
An unmanned aerial vehicle (UAV)(101) comprises a plurality of UAV components including a battery, a camera, a global positioning system (GPS), a radio controller (RC), a magnetometer or compass, wherein a plurality of sensor is associated with the plurality of UAV components (104);
a ground control station (GCS)(103) communicatively coupled with the plurality of UAV components (104) via a wired or a wireless communication channel, wherein the GCS (104) is configured for:
receiving a preflight data of UAV (101) comprising battery data, camera data, GPS data, RC data, Magnetic Field data, logger data and home location and distance data captured via the plurality of sensors associated with the plurality of UAV components (104) to store a corresponding predetermined data in the absence of errors;
transmitting a first mission command to the UAV (101) to start planning of the mission;
transmitting a signal to UAV (101) for performing preflight sanity check after completion of planning of mission, wherein:
receiving the preflight data of UAV(101) captured via the plurality of sensors associated with the plurality of UAV components (104);
comparing the received preflight data with the corresponding predetermined data stored in the GCS (103) to perform preflight sanity check;
detecting errors present in the plurality of UAV (104) components based on preflight sanity check; and
transmitting a second mission command to the UAV (101) based on the detected errors.
2. The system as claimed in claim 1, wherein the battery data comprises battery current and battery voltage.
3. The system as claimed in claim 1, wherein the camera data comprises pulse and triggers emitted by the camera.
4. The system as claimed in claim 1, wherein the GPS data comprises satellite count.
5. The system as claimed in claim 1, wherein the Magnetic field data comprises roll, pitch, yaw, and heading of the compass related to the UAV.
6. The system as claimed in claim 1, wherein the logger data comprises payloads, GPS data, and camera log files.
7. The system as claimed in claim 1, wherein the home location and distance data comprise latitude and longitude data for the UAV.
8. The system as claimed in claim 1, wherein the RC data comprises minimum, maximum, and trim control values for UAV flight control.
9. The system as claimed in claim 2, wherein the GCS (103) is configured for comparing the battery current and battery voltage with a predetermined battery current and battery voltage stored in the GCS (103), wherein if the received battery data is below the predetermined battery current and battery voltage, then the GCS (103) is configured for indicating a low battery error to a user associated with the GCS (103).
10. The system as claimed in claim 3, wherein the GCS (103) is configured for comparing the current camera pulse and triggers with a predetermined camera pulse and triggers stored in the GCS (103), wherein if the received camera data differs from the predetermined camera pulse and triggers, then the GCS (103) is configured for indicating a camera error to the user associated with the GCS (103).
11. The system (100) as claimed in claim 4, wherein the GCS (103) is configured for comparing received satellite counts with a predetermined satellite counts stored in the GCS (103), wherein if the received satellite count is lower than the predetermined satellite count, then the GCS (103) is configured for indicating a GPS signal weakness error to the user associated with the GCS (103).
12. The system (100) as claimed in claim 5, wherein the GCS (103) is configured for comparing received Magnetic field data with a predetermined Magnetic field data stored in the GCS, wherein if the received Magnetic field data differs from the predetermined Magnetic field data, then the GCS (103) is configured for indicating calibration error of the compass or magnetometer to the user associated with the GCS (103).
13. The system (100) as claimed in claim 6, wherein and the GCS (103) is configured for comparing the received logger data with a predetermined logger data stored in the GCS (103), wherein if the received logger data differs from the predetermined logger data, then the GCS (103) is configured for indicating an inconsistency error in the logger data to the user associated with the GCS (103).
14. The system (100) as claimed in claim 7, wherein the GCS (103) is configured for comparing the received home location and distance data with a predetermined home location and distance data stored in the GCS (103), wherein if the received home location and distance data differs from the predetermined home location and distance data, then the GCS (103) is configured for indicating a home location and distance error to the user associated with the GCS (103).
15. The system (100) as claimed in claim 8, wherein and the GCS (103) is configured for comparing the RC data with a predetermined RC data stored in the GCS, wherein if the received control values differ from the predetermined RC data, then the GCS (103) is configured for indicating a control error to the user associated with the GCS (103).
16. The system (100) as claimed in claim 1, wherein the second mission command is selected from a take-off mission command in case of zero errors present in the plurality of UAV components (104), and stop mission and fix error command in case of error present in the at least one UAV component of the plurality of UAV component (104).
17. The system (100) as claimed in claim 1, wherein the GCS (103) is configured for providing step-by-step instructions or suggestions to the user associated with the GCS (103) to resolve the detected errors based on a type of error detected in each UAV component of the plurality of UAV components (104).
18. A method (300) for prefight sanity check of an unmanned aerial vehicle (UAV) components (104), wherein the method comprising:
receiving, via a ground control station (GCS) (103), a preflight data of UAV comprising battery data, camera data, GPS data, RC data, Magnetic Field data, logger data and home location and distance data captured via the plurality of sensors associated with the plurality of UAV components (104) to store a corresponding predetermined data in the absence of errors;
transmitting, via the GCS (103), a first mission command to the UAV (101) to start planning of the mission;
transmitting, via the GCS (103), a signal to UAV (101) for performing preflight sanity check after completion of planning of mission;
receiving, via the GCS (103), the preflight data of UAV (101) captured via the plurality of sensors associated with the plurality of UAV components (104);
comparing, via the GCS (103), the received preflight data with the corresponding predetermined data stored in the GCS (103) to perform preflight sanity check;
detecting, via the GCS (103), errors present in the plurality of UAV components based on preflight sanity check; and
transmitting, via the GCS (103), a second mission command to the UAV based on the detected errors.
19. The method (300) as claimed in claim 18, wherein the battery data comprises battery current and battery voltage.
20. The method (300) as claimed in claim 18, wherein the camera data comprises pulse and triggers emitted by the camera.
21. The method (300) as claimed in claim 18, wherein the GPS data comprises satellite count.
22. The method (300) as claimed in claim 18, wherein the Magnetic field data comprises roll, pitch, yaw, and heading of the compass related to the UAV.
23. The method (300) as claimed in claim 18, wherein the logger data comprises payloads, GPS data, and camera log files.
24. The method (300) as claimed in claim 18, wherein the home location and distance data comprise latitude and longitude data for the UAV.
25. The method (300) as claimed in claim 18, wherein the RC data comprises minimum, maximum, and trim control values for UAV flight control.
26. The method (300) as claimed in claim 19, further comprising comparing, via the GCS (103), the battery current and battery voltage with a predetermined battery current and battery voltage stored in the GCS (103), wherein if the received battery data is below the predetermined battery current and battery voltage, then the GCS (103) is configured for indicating a low battery error to the user associated with the GCS (103).
27. The method (300) as claimed in claim 20, further comprising comparing, via the GCS (103), the current camera pulse and triggers with a predetermined camera pulse and triggers stored in the GCS (103), wherein if the received camera data differs from the predetermined camera pulse and triggers, then the GCS (103) is configured for indicating a camera error to the user associated with the GCS (103).
28. The method (300) as claimed in claim 21, further comprising comparing, via the GCS (103), received satellite counts with a predetermined satellite counts stored in the GCS (103), wherein if the received satellite count is lower than the predetermined satellite counts, then the GCS (103) is configured for indicating a GPS signal weakness error to the user associated with the GCS (103).
29. The method (300) as claimed in claim 22, further comprising comparing, via the GCS (103), received Magnetic field data with a predetermined Magnetic field data stored in the GCS (103), wherein if the received Magnetic field data differs from the predetermined Magnetic field data, then the GCS (103) is configured for indicating a calibration issue of the compass or magnetometer to the user associated with the GCS (103).
30. The method (300) as claimed in claim 23, further comprising comparing, via the GCS (103), the received logger data with a predetermined logger data stored in the GCS (103), wherein if the received data differs from the predetermined logger data, then the GCS (103) is configured for indicating an inconsistency in the logger data to the user associated with the GCS (103) .
31. The method (300) as claimed in claim 24, further comparing, via the GCS (103), the received home location and distance data with a predetermined home location and distance data stored in the GCS (103), wherein if the received data differs from the predetermined home location and distance data, then the GCS (103) is configured for indicating a home location and distance error to the user associated with the GCS (103).
32. The method as claimed in claim 25, further comprising comparing, via the GCS (103), the received RC data with a predetermined RC data stored in the GCS (103), wherein if the received control values differ from the predetermined RC data, then the GCS (103) is configured for indicating a control issue to the user associated with the GCS (103).
33. The method (300) as claimed in claim 18, wherein the second mission command is selected from a take-off mission command in case of zero errors present in the plurality of UAV components, and stop mission and fix error command in case of error present in the at least one UAV component of the plurality of UAV components.
34. The method (300) as claimed in claim 18, further comprising providing, via the GCS, step-by-step instructions or suggestions to the user associated with the GCS to resolve the detected errors based on a type of error detected in each UAV component of the plurality of UAV components.
Dated this 19th Day of October 2023
Priyank Gupta
Agent for the Applicant
IN/PA-1454