Replies

  • This reply was deleted.
    • I'm having problems with Geo Fence.

      When I'm in a mission the hex will often fence breach at the first waypoint and then RTL. Sometimes it will make it past the first waypoint to fence breach later in the mission.

      I set the breach limit to 800m distance and 140m altitude, to make sure I don't go past the fence and I still get the message and the systems still RTLs.

      I've added the graphs from the Telemetry Logs (Altitude in GLOBAL POS & GPS_RAW_INT) and the .kmz file of the flight.

      Altitude log files show a spike in altitude right before Fence Breach, but I didn't see any spikes in altitude and the .kmz file confirms this.

      What's going on and how can I keep this from happening? It's very important that stop this from happening. Any help would be greatly appreciated.

      GLOBAL_POSTIONING relative_alt.PNG

      2015-07-08 19-14-17.tlog.kmz

      GPS_RAW_INT alt.PNG

  • Updated mine to 1.3.8.1 beta, no more message.

    Edit: 1.3.9 just released!

  • This reply was deleted.
  • This reply was deleted.
    • Developer

      Bug already reported on GitHub, wait the fix.

    • Hi Marco,

      I have a project where I need to use my quad in a couple hours.  Am I okay to fly even thought the Geofence Breach comes up on Mission Planner?  

      Note:  The Geofence is disabled

      Thanks.

    • Great!

    • I was wondering as well, searching for the Geofence :-)

      Btw. it seems, that the Compass calibration is working for both MAG (PIXHAWK),and shows the offset for both MAG but it doesn´t store them.  Anybody noticed sth. similiar ?.

    • I saw that too. They are stored though. If you refresh the parameters, they both show up.

    • Thanks 

    • Thank's Marco

This reply was deleted.