From 3ddaa5e49b3ee4929aa728a392e1575ef01c638d Mon Sep 17 00:00:00 2001 From: blubbi321 Date: Thu, 13 Sep 2018 19:13:24 +0200 Subject: [PATCH] Update README.md Fixed typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 0ba1248..0ade5fd 100644 --- a/README.md +++ b/README.md @@ -56,7 +56,7 @@ If the motors do something, but don't rotate smooth and quietly, try to use an a Nunchuck not working: Use the right one of the 2 types of nunchucks. Use i2c pullups. -Nunchuck or PPM working bad: The i2c bus and PPM signal are very sensitive to emv distortions of the motor controller. They get stronger the faster you are. Keep cables short, use shielded cable, use ferrits, stabalize voltage in nunchuck or reviever, add i2c pullups. To many errors leads to very high accelerations which triggers the protection board within the battery to shut everything down. +Nunchuck or PPM working bad: The i2c bus and PPM signal are very sensitive to emv distortions of the motor controller. They get stronger the faster you are. Keep cables short, use shielded cable, use ferrits, stabilize voltage in nunchuck or reviever, add i2c pullups. To many errors leads to very high accelerations which triggers the protection board within the battery to shut everything down. Most robust way for input is to use the ADC and potis. It works well even on 1m unshielded cable. Solder ~100k Ohm resistors between ADC-inputs and gnd directly on the mainboard. Use potis as pullups to 3.3V.