Silverware Wiki

User Tools

Site Tools

Trace:
more_brushless_setup_info

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
more_brushless_setup_info [2018/02/09 03:52]
ian446 		more_brushless_setup_info [2018/03/09 10:11] (current)
ian446 minor change
Line 7: Line 7:
 <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 Dshot:**</font> <font 16px/inherit>**How to set up Dshot:**</font>
Line 21: 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> <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 DSHOT150
 //#define DSHOT300 //#define DSHOT300
Line 27: Line 28:
 // IDLE_OFFSET is added to the throttle. Adjust its value so that the motors // IDLE_OFFSET is added to the throttle. Adjust its value so that the motors
 // still spin at minimum throttle. // 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>
Line 37: Line 38:
  
 <font 13px/inherit>In **hardware.h** - the esc PPM driver is selected instead of the default PWM driver</font> <font 13px/inherit>In **hardware.h** - the esc PPM driver is selected instead of the default PWM driver</font>
- 
 <code> <code>
 //#define USE_PWM_DRIVER //#define USE_PWM_DRIVER
Line 61: Line 61:
 <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>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>
  
-<code>// invert = signal after fets (may need 1k pullup resistor)+<code> 
 +// invert = signal after fets (may need 1k pullup resistor)
 // commented = signal straight from CPU pins // commented = signal straight from CPU pins
-#define ESC_INVERT_SIGNAL</code>+#define ESC_INVERT_SIGNAL 
 +</code>
  
 <font 13px/inherit>Or for H101, H8 mini green:</font> <font 13px/inherit>Or for H101, H8 mini green:</font>
  
-<code>// output polarity ( low - motor output with pullup resistor (500 ohms or near) ) +<code> 
-// enable for motor output after fets  +// output polarity ( low - motor output with pullup resistor (500 ohms or near) ) 
-#define INVERTED_PWM</code>+// enable for motor output after fets 
 +#define INVERTED_PWM 
 +</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 either of these two boxes:</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>
  
-<code>// invert = signal after fets (may need 1k pullup resistor)+<code> 
 +// invert = signal after fets (may need 1k pullup resistor)
 // commented = signal straight from CPU pins // commented = signal straight from CPU pins
-//#define ESC_INVERT_SIGNAL</code>+//#define ESC_INVERT_SIGNAL 
 +</code>
  
 <font 13px/inherit>Or for H101, H8 mini green:</font> <font 13px/inherit>Or for H101, H8 mini green:</font>
  
-<code>// output polarity ( low - motor output with pullup resistor (500 ohms or near) )+<code> 
 +// output polarity ( low - motor output with pullup resistor (500 ohms or near) )
 // enable for motor output after fets // enable for motor output after fets
-//#define INVERTED_PWM</code>+//#define INVERTED_PWM 
 +</code> 
 + 
 +<font 13px/inherit>Happy flying!!</font> 
 + 
 +{{:lob9610000kv.jpg?nolink&|{{::lob9610000kv.jpg?nolink&400|}}}} 
 + 
more_brushless_setup_info.1518144774.txt.gz · Last modified: 2018/02/09 03:52 by ian446

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki