Differences

This shows you the differences between two versions of the page.

--- more_brushless_setup_info [2018/02/09 03:11]
ian446
+++ more_brushless_setup_info [2018/03/09 10:11] (current)
ian446 minor change
@@ Line 1: / Line 1: @@
 <font 16px/inherit>**Brushless setup - driving esc's - firmware settings. Revised Feb, 2018.**</font>
-<font 13px/inherit>This page follows on from the first brushless page with a little more detail about setting up a silverwared FC to control a quad with brushless motors.</font>
+<font 13px/inherit>It is highly recommended to use BLHeli_S esc's to make things easy and effective. The reason is that they can use Dshot or the older PPM protocols (both protocols give great results), and are easy to set up with BLHelisuite. A BLHeli_S esc will auto-detect either Dshot or various PPM and oneshot protocols. For Dshot, the esc drive signal must come from the FET gate and you would select dshot_driver_beta in hardware.h. If you do not plan to use the signal from the FET gate (i.e. you will use pull-up resistors after the FET's) then you must use PPM protocol (e.g. oneshot) and select esc_driver in hardware.h.</font>
-<font 13px/inherit>It is highly recommended to use BLHeli_S esc's to make things easy and effective. The reason is that they can use Dshot or the older PPM protocols (both protocols give great results), and are easy to set up with BLHelisuite. For Dshot, the esc drive signal must come from the FET gate and you would select dshot_driver_beta in hardware.h. If you do not plan to use the signal from the FET gate (i.e. you will use pull-up resistors after the FET's) then you must use PPM protocol (e.g. oneshot) and select esc_driver in hardware.h.</font>
 <font 13px/inherit>If you are familiar with Betaflight or Cleanflight, you might wonder what "PPM" is. In silverware, a PPM signal is a conventional signal that drives an esc using (for example) oneshot protocol, and a PWM signal is one that drives an FET for a brushed motor.</font>
-<font 13px/inherit>If you have a BLHeli flashable esc and want to connect to it to check or change the settings, you will need an interface between BLHeliSuite and the esc. Many people use an Arduino Nano, which is only a few dollars, and the Nano can be flashed by BLHeliSuite to become the interface to an individual esc, or to a 4 in 1 esc either individually or as a group).</font>
+<font 13px/inherit>If you have a BLHeli flashable esc and want to connect to it to check or change the settings, you will need an interface between BLHeliSuite and the esc. Many people use an Arduino Nano, which is only a few dollars, and the Nano can be flashed by BLHeliSuite to become the interface to an individual esc, or to a 4 in 1 esc (either individually or as a group).</font>
-<font 13px/inherit>It is **strongly recommended** to connect to your esc's with BLHelisuite to untick the "Programming by TX" check box, and while you are there, check that all four esc's have the same firmware revision and same default settings. The esc's will almost always misbehave if the "Programming by TX" check box is left in the default (ticked) setting. They can enter the programming mode when all you want to do is fly the quad...and if that happens, you will have to connect to BLHelisuite to correct the settings.</font>
+<font 13px/inherit>It is **strongly recommended** to connect to your esc's with BLHelisuite to untick the "Programming by TX" check box, and while you are there, check that all four esc's have the same firmware revision and same default settings. The esc's can misbehave if the "Programming by TX" check box is left in the default (ticked) setting. They can unintentionally enter the programming mode when all you want to do is fly the quad, and if that happens, you will have to connect to BLHelisuite to correct the settings.</font>
-<font 16px/inherit>**How to set up the Dshot esc driver:**</font>
+<font 16px/inherit>**How to set up Dshot:**</font>
 <font 13px/inherit>The Dshot esc driver is selected in hardware.h.</font>
@@ Line 23: / Line 21: @@
 <font 13px/inherit>Then, in drv_dshot.c, select either DSHOT600, DSHOT300 or DSHOT150, and adjust the IDLE_OFFSET number if you need to, in order to set the desired “idle” speed. Default is 40 and I often use 32 for high-Kv 100mm and 120mm quads.</font>
-<code>#define DSHOT600
+<code>
+#define DSHOT600
 //#define DSHOT150
 //#define DSHOT300
@@ Line 29: / Line 28: @@
 // IDLE_OFFSET is added to the throttle. Adjust its value so that the motors
 // still spin at minimum throttle.
-#define IDLE_OFFSET 32</code>
+#define IDLE_OFFSET 32
+</code>
+<font 13px/inherit>**Note for Dshot:** The signal can only be taken from before the FET (FET gate) for it to work.</font>
-<font 13px/inherit>**Note** for Dshot: The signal can only be taken from before the FET (FET gate) for it to work.</font>
+<font 13px/inherit>If you are using Dshot, you do not need to read any further, the following instructions are for PPM.</font>
-<font 16px/inherit>**How to set up the PPM esc driver:**</font>
+<font 16px/inherit>**How to set up PPM/Oneshot:**</font>
 <font 13px/inherit>In **hardware.h** - the esc PPM driver is selected instead of the default PWM driver</font>
 <code>
 //#define USE_PWM_DRIVER
@@ Line 59: / Line 59: @@
 </code>
-<font 13px/inherit>Finally, the PPM signal polarity needs to be set in drv_esc.c. If you are taking the signal from after the FET, from the motor output - (neg) pad, the signal must be inverted in the firmware because the FET also inverts it, (by inverting twice, the signal ends up having the correct polarity).</font>
+<font 13px/inherit>Finally, the PPM signal polarity needs to be set in drv_esc.c. If you are taking the signal from after the FET with pullup resistors to drive the esc, i.e. from the motor output - (neg) pad, the signal must be inverted in the firmware because the FET also inverts it, (by inverting twice, the signal ends up having the correct polarity).</font>
-<font 13px/inherit>**Setting the esc signal polarity for H8 mini blue and CG023:**</font>
-<font 13px/inherit>If you are taking the signal from after the FET with pullup resistors to drive the esc, the polarity would be set inverted:</font>
 <code>
@@ Line 71: / Line 67: @@
 </code>
-<font 13px/inherit>If you are taking the signal from the gate of the FET (straight from the CPU pins) to drive the esc, the polarity would be set non-inverted, like this:</font>
+<font 13px/inherit>Or for H101, H8 mini green:</font>
 <code>
-// invert = signal after fets (may need 1k pullup resistor)
+// output polarity ( low - motor output with pullup resistor (500 ohms or near) )
-// commented = signal straight from CPU pins
+// enable for motor output after fets
-//#define ESC_INVERT_SIGNAL
+#define INVERTED_PWM
 </code>
-<font 13px/inherit>**Setting the esc signal polarity for H8 mini green and H101:**</font>
+<font 13px/inherit>If you are taking the signal from the gate of the FET (straight from the CPU pins) to drive the esc, the polarity would be set non-inverted, like either of these two boxes:</font>
-<font 13px/inherit>If you are taking the signal from after the FET with pullup resistors to drive the esc, the polarity would be set inverted:</font>
 <code>
-// output polarity ( low - motor output with pullup resistor (500 ohms or near) )
+// invert = signal after fets (may need 1k pullup resistor)
-// enable for motor output after fets
+// commented = signal straight from CPU pins
-#define INVERTED_PWM
+//#define ESC_INVERT_SIGNAL
 </code>
-<font 13px/inherit>If you are taking the signal from the gate of the FET (straight from the CPU pins) to drive the esc, the polarity would be set non-inverted, like this:</font>
+<font 13px/inherit>Or for H101, H8 mini green:</font>
 <code>
@@ Line 97: / Line 91: @@
 </code>
-<font 18px/inherit>**PWM**</font>
+<font 13px/inherit>Happy flying!!</font>
-<font 13px/inherit>For PWM (brushed motor ouput), a BLHeli flashable esc has to be used to enable the pwm input of the esc. To flash an esc, or just connect to it to check or change the settings, you will need an interface between BLHeliSuite and the esc. Many people use an Arduino Nano, which is only a few dollars, and it can be flashed by BLHeliSuite to become the interface to connect to many different esc's. An alternative is to buy an esc programmer for your particular esc's, and this will serve as the BLHeli/esc interface instead of the Arduino Nano.</font>
+{{:lob9610000kv.jpg?nolink&|{{::lob9610000kv.jpg?nolink&400|}}}}
-<font 13px/inherit>When you connect an esc to BLHeliSuite, there is a box labelled "Enable PWM Input". In this box, the slider must be set to ON and the setting written to the esc by clicking on the Write Setup button. Then confirm the settings have been written by clicking on the Read Setup button. Note: BLHeli_S esc's do not support PWM Input. For BLHeli_S you must use the PPM method to drive the esc.</font>
-<font 13px/inherit>If you are using resistors (and therefore taking the signal for the esc's after the FET), the Input Polarity in BLHeliSuite must be set to Negative. If you are taking the signal from the gate of the FET, Input Polarity would be set to the default setting Positive.</font>
-**<font 14px/inherit>PWM FIRMWARE SETTINGS</font>**
-<font 13px/inherit>For PWM there are only a couple of things to change in the firmware in **config.h**. The motor PWM has to be set to 1kHz, 2kHz, 4kHz, 8kHz or 12kHz. These are the values that BLHeli firmware will accept. I have used mostly 8kHz. With PWM, you have to manually arm the esc by raising and then lowering the throttle.</font>
-<code>
-For the H8 mini green and H101 board set (in config.h):
-#define MOTOR_CURVE_NONE
-#define PWM_8KHZ
-For H8 mini blue board and CG023 set (in config.h):
-#define PWMFREQ 8000
-#define MOTOR_CURVE_NONE
-</code>
-<font 13px/inherit>For the H8 mini green, H8 mini blue, H101 and CG023 code, the min motor speed is also changed in config.h. The line MOTOR_MIN_ENABLE has to be uncommented, and the MOTOR_MIN_VALUE has to be set, usually to a value between 0.06 and 0.12 (lower for 3S and higher for 2S battery). This sets the minimum motor speed that the motors will spin at, and if it is too low, the motors will not start together cleanly. If it is too high, the quad may lift off at minimum motor speed, so start with a low value and work up. Silverxxx recommends testing it with the "motors_to_throttle" option, as that way you can clearly see if they start and run properly.</font>
-<code>
-// limit minimum motor output to a value (0.0 - 1.0)
-#define MOTOR_MIN_ENABLE
-#define MOTOR_MIN_VALUE 0.07
-</code>

Silverware Wiki

User Tools

Site Tools

Differences

Page Tools