From dd1d3ad362d8ba73f1237b8bbe6a417c6d4f0269 Mon Sep 17 00:00:00 2001 From: Jacob Alexander Date: Sun, 1 Dec 2013 17:13:42 -0500 Subject: [PATCH] Increasing MAX_PRESS_DELTA_MV to measured min kishsaver value - Enabling the test point strobe on the kishsaver really kills the sensing (many keys don't work, even at 400) --- Scan/avr-capsense/scan_loop.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Scan/avr-capsense/scan_loop.c b/Scan/avr-capsense/scan_loop.c index bec9d9d..b85a814 100644 --- a/Scan/avr-capsense/scan_loop.c +++ b/Scan/avr-capsense/scan_loop.c @@ -32,7 +32,7 @@ // ----- Defines ----- // TODO dfj defines...needs commenting and maybe some cleaning... -#define MAX_PRESS_DELTA_MV 380 +#define MAX_PRESS_DELTA_MV 450 // As measured from the Teensy ADC pin #define THRESHOLD_MV (MAX_PRESS_DELTA_MV >> 1) //(2560 / (0x3ff/2)) ~= 5 #define MV_PER_ADC 5 @@ -232,7 +232,7 @@ inline void scan_setup() strobe_map[6] = 8; strobe_map[7] = 9; // XXX - Disabling for now, not sure how to deal with test points yet (without spamming the debug) - //strobe_map[9] = 15; // Test point strobe (3 test points, sense 1, 4, 5) + //strobe_map[8] = 15; // Test point strobe (3 test points, sense 1, 4, 5) #elif defined(TERMINAL_6110668_STROBE) total_strobes = 16;