From 9cf671b81725521644b8c91d741fdb36bd37ca25 Mon Sep 17 00:00:00 2001 From: Bruce Luckcuck Date: Mon, 10 Sep 2018 08:07:27 -0400 Subject: [PATCH] Change dterm_notch_cutoff default to 0 The dterm notch is disabled and dterm_notch_hz is already 0 by default. When the Configurator saves changes from the PID Tuning tab and the notch is disabled it sets both dterm_notch_hz and dterm_notch_cutoff to 0. Since the default was left at 160, this makes dterm_notch_cutoff appear in diff outputs. Ultimately it's just cosmetic since the dterm notch is disabled if either value is zero. But there's no reason for the dterm_notch_cutoff to remain set to the legacy 160 value. --- src/main/flight/pid.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/flight/pid.c b/src/main/flight/pid.c index baf0591c9..67d398fee 100644 --- a/src/main/flight/pid.c +++ b/src/main/flight/pid.c @@ -130,7 +130,7 @@ void resetPidProfile(pidProfile_t *pidProfile) .dterm_lowpass_hz = 100, // dual PT1 filtering ON by default .dterm_lowpass2_hz = 200, // second Dterm LPF ON by default .dterm_notch_hz = 0, - .dterm_notch_cutoff = 160, + .dterm_notch_cutoff = 0, .dterm_filter_type = FILTER_PT1, .itermWindupPointPercent = 40, .vbatPidCompensation = 0,