-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Geofence option #62
Comments
Also, in case of "fly away" add a condition: if geofence triggered RTH but UAV is still going away, trigger emergency landing |
or turn to home after XXXX meters. |
@AnandNL turn to home after XXXX meters is not geofence! I have found some C# code for geofence. Still need a gui or export or import functions from google map as user interface. public bool Contains(GeoLocation location)
} |
By definition geofencing is using GPS to create a virtual geographic boundary. In that scope defining a barrier as a max distance from home seems legit to me and if properly implemented quite extendable as well. |
Hi! Could be freakin' nice to get a "lite" geofence mode, like a alternative mode of althold, where you can set a max altitude, and a max home distance, cause since the french law about professional drone change in last July, it's the only point where Inav can't be legal to use... And I'd love to be able to use my Inav setup instead of a DJI! |
A "hard" geofence distance (and height) would be nice to keep legal. As long as it's turned off by default. I live in a very flat area, so I would probably turn on the height fence to say 450 feet. We already know distance to home, so it's just a matter of how to deal when exceeding the max altitude or distance. |
I saw in the Pawel spychalski's YouTube channel that he is working on a kind of bracking, for the next firmware, could be the option that the distance max would be triggering, cause for the max height, althold is already able to maintain the quad at a specific altitude. |
Maybe "hard" and "soft" geofence options? "hard" would trigger RTH, while "soft" would trigger position hold and throttle max speed until you're back inside the geofence? Maybe even a combination, for example, "soft" geofence at 0.8km and "hard" at 1.0km. Obviously, there would be OSD to notify of both. This would be like a warning before a RTH or possibly "land" was triggered. |
I'd really like something like that, so I could work with my own Inav setup, would be amazing... |
Hi! Now this request seem to be open about 3 years ago, any news about a geofence option in INAV? Does any of the Devs could answer about it? Would be nice to know if we are waiting for something or if I should build an ardupilot setup even if I rather use INAV. |
This quad claims Geofencing using the YupiF7 FC: https://www.studiosport.fr/racer-corsair-s1-s3-studiosport-a17684.html also see Fincky video here: https://www.youtube.com/watch?v=8OJxaEc2Sbg YupiF7: https://www.yupifc.com/ Anyone know if it's using an iNav fork and if so, where to find the source? |
betaflight fork not inav one |
OK understood - can't seem to find it though... Is the source published? |
as i know ,not published and it is not planed . |
Is that OK ref. GPL? If there was published source I would try and port to iNav... |
No, it's not ok. It's a violation of GPL. |
in fact i don't think this violating the GPL , |
A derivative work based on a GPL licensed project (in this case Betaflight) that's being distributed without publishing the source code... That's the very definition of a GPL license violation. |
Possibly what's happening here is that YupiFC distribute their binary (in the flight controller) and then offer the source only to those who a) have the binary and b) request it. |
Nope, doesn't work that way. You can't withhold the source or otherwise charge for it (by only providing it to customers) and it must be freely available to anyone who wants it. Applying additional license terms to the GPL licensed software (such as requiring purchase or other terms of use) is expressly prohibited. By not providing the source of the derivative work they are not authorized to use the original licensed source. Period. The entire point of the GPL license is that it requires the propagation of the open source aspect. In a nutshell, by taking advantage of others' work for your benefit you're agreeing to contribute your improvements to further the project. You probably should read the GPL license terms for a better understanding. |
This feature should also include support for exclusion zones within a geofenced area. For example, I fly at a field which has communication towers on the perimeter. If the tower interferes and triggers a failsafe return-to-home, I wouldn't want the it to fly the vehicle directly into or through the RF beams of the tower. |
Hi ! |
This can be done using the inav programming tab now. Using the "home distance" and override rc channel to enable rth. You can also add a sticky in there to only enable rth between 50m and 49m from home. |
@Tdogb You have a good suggestion. I think the key feature of this request is the user defined polygon. There may be very specific areas boarding a flight area which which are closer than other parts of the flight area, and should trigger an RTH. Eg: Trees, buildings, terrain, etc.. |
any developments?! |
The text was updated successfully, but these errors were encountered: