paparazzi-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[paparazzi-commits] [paparazzi/paparazzi] 8ba2c0: [rotorcraft] heading i


From: GitHub
Subject: [paparazzi-commits] [paparazzi/paparazzi] 8ba2c0: [rotorcraft] heading integration protection in RC-...
Date: Thu, 11 Jun 2015 09:49:16 -0700

  Branch: refs/heads/master
  Home:   https://github.com/paparazzi/paparazzi
  Commit: 8ba2c0848fbc7976da127581c7bd8959eb1f4ebe
      
https://github.com/paparazzi/paparazzi/commit/8ba2c0848fbc7976da127581c7bd8959eb1f4ebe
  Author: Felix Ruess <address@hidden>
  Date:   2015-05-04 (Mon, 04 May 2015)

  Changed paths:
    M 
sw/airborne/firmwares/rotorcraft/stabilization/stabilization_attitude_rc_setpoint.c

  Log Message:
  -----------
  [rotorcraft] heading integration protection in RC-event

The PSI += .... was highly depending on the RC-frame rate.
With most RC this is not a problem but with variable message rates (e.g. 
rc_datalink dropping messages or joysticks sending too many frames) this line 
becomes dangerous.

So measure the time between to calls to read_rc_setpoint function instead of 
using a fixed RC_UPDATE_FREQ.
To prevent really weird things from happening, bound dt to 0.5s.

Don't partuculariliy like that this pulls in the sys_time dependency here,
but couldn't think of something better...

should close #452


  Commit: fe4b1f8066af9f8b1d79b6c2881dfc58fcb229cd
      
https://github.com/paparazzi/paparazzi/commit/fe4b1f8066af9f8b1d79b6c2881dfc58fcb229cd
  Author: Felix Ruess <address@hidden>
  Date:   2015-06-11 (Thu, 11 Jun 2015)

  Changed paths:
    M 
sw/airborne/firmwares/rotorcraft/stabilization/stabilization_attitude_rc_setpoint.c

  Log Message:
  -----------
  Merge pull request #1174 from paparazzi/rc_heading_integration_protection

[rotorcraft] heading integration protection in RC-event

The PSI += .... was highly depending on the RC-frame rate.
With most RC this is not a problem but with variable message rates (e.g. 
rc_datalink dropping messages or joysticks sending too many frames) this line 
becomes dangerous.

So measure the time between to calls to read_rc_setpoint function instead of 
using a fixed RC_UPDATE_FREQ.
To prevent really weird things from happening, bound dt to 0.5s.

fixes #452


Compare: 
https://github.com/paparazzi/paparazzi/compare/ecdc6faac171...fe4b1f8066af

reply via email to

[Prev in Thread] Current Thread [Next in Thread]