@phmagic Yes, I'm running version_3.0, but not the latest. I ran into an unknown difficulty with one of the shots in my app when I ran with the latest, so I dropped back to an older version.
@phmagic Thanks for the info on the fence. I arrived at basically that conclusion after poking around in GeofenceManager.py. On my first test I didn't know what subCoord might be, so I just made it the same as coord. After observing how the copter would stop but sort of "stick" to a fence wall, I realized subCoord must be an inset. And sure enough, there it was in GeofenceManager.py :-)
@phmagic I assume there's a plan or a desire to implement the Solo's Geofence in terms of ArduCopter's new POLY_FENCE when it's available?
Sounds good. I've seen videos of that in action, and it appears to work well. It has an advantage in that it can control position directly and actually slow the copter down on the way to the fence edge and stop it. You can "push" against the fence edge at an angle, and it just flies along it without any bounce. I did a low-altitude fence some time ago for a company in NZ (lets them fly over the ocean without going under), and the ability to control position on the fly makes a huge difference. :-)