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/01/19 08:01]
ian446 		more_brushless_setup_info [2018/03/09 10:11] (current)
ian446 minor change
Line 1: Line 1:
-<font 14px/inherit>**Brushless setup - driving esc's - firmware settings. Revised Jan 01, 2017.**</font>+<font 16px/inherit>**Brushless setup - driving esc's - firmware settings. Revised Feb, 2018.**</font>
  
-<font 14px/inherit>**Unfortunately much of this information is 12 months old, and no longer correct. I will rewrite it soon. Ian. 19th Jan 2017.**</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>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. There are instructions for H8 mini green, H8 mini blue, H101 and CG023 boards, for setting up either PPM, PWM or Dshot. These instructions assume the dual version firmware of the H8 mini green and H101 firmwares are used, as opposed to the acro only versions that are also available. It does not cover setting up 3D flying with the H101 board, refer to SirDomsen's H101 Brushless Mod page for 3D info and setup.</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 16px/inherit>**PPM, PWM and DSHOT**</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>Most brushless quads use a PPM signal to drive their esc's. Also, PPM is used by model aircraft receivers to control the servo's and an esc for the motor, so it is basically the conventional way to drive an esc.</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 13px/inherit>Dshot is a digital throttle signal sent to the esc in the form of a binary number, as opposed to a pulsewidth or pulse position signal. The esc’s do not need to be calibrated when using Dshot. Dshot can be run on BLHeli_S esc's with BLHeli firmware revision 16.5 or later.</font>+<font 16px/inherit>**How to set up Dshot:**</font>
  
-<font 13px/inherit>However, the default signal from a silverwared FC is a PWM signal that drives the brushed motors with an FET. This PWM signal can be used to drive an esc if you can connect to the esc with BLHeliSuite and set the “Enable PWM Input” to on. When enable pwm input is set to on, the esc will accept either PWM or PPM signals, it is auto-detected by the esc. If the enable pwm input is set to off, (this is the default BLHeli setting), the esc will only work with PPM signals. In later BLHeli firmware revisions from around 16.4 onwards, PWM input enable is no longer an option, and Dshot was introduced. From Revision 16.5 onwards, the esc’s can auto-detect PPM or Dshot signals, but cannot use brushed PWM signals.</font>+<font 13px/inherit>The Dshot esc driver is selected in hardware.h.</font>
  
-<font 18px/inherit>**PPM and Dshot**</font>+<code> 
 +//#define USE_PWM_DRIVER 
 +//#define USE_ESC_DRIVER 
 +#define USE_DSHOT_DRIVER 
 +</code>
  
-<font 13px/inherit>With PPM output you can technically run any standard esc regardless of the esc firmware, even if it does not support BLHeli firmware, however, if you are going to buy some esc’s for a build it is recommended to purchase esc’s that have, or can use, BLHeli firmware</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>
  
-<font 13px/inherit>If you have BLHeli flashable esc's 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 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 BLHeliSuite/esc interface instead of the Arduino Nano.</font>+<code> 
 +#define DSHOT600 
 +//#define DSHOT150 
 +//#define DSHOT300
  
-<font 14px/inherit>**PPM and DSHOT FIRMWARE SETTINGS FOR H8 MINI BLUE, CG023, H8 MINI GREEN and H101.**</font>+// IDLE_OFFSET is added to the throttle. Adjust its value so that the motors 
 +// still spin at minimum throttle. 
 +#define IDLE_OFFSET 32 
 +</code>
  
-<font 13px/inherit>**In a nutshell, these are the esc drive options for the following firmwares:**</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>**H8 mini blue:** PPM or oneshot, both with adjustable freq option. Select "USE_ESC_DRIVER" in hardware.h Esc settings are in drv_esc.c. A Dshot 150/300/600 beta version is being tested right now (May 2017).</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 13px/inherit>**CG023:** PPM, oneshot or oneshot42 all with adjustable freq option. Select "USE_ESC_DRIVER" in hardware.h Esc settings are in drv_esc.c. A Dshot 150/300/600 beta version is being tested right now and is included in the current CG023 firmware (May 2017). The settings are found in the drv_dshot.c file.</font> +<font 16px/inherit>**How to set up PPM/Oneshot:**</font>
- +
-<font 13px/inherit>**H8 mini green:** PPM with adjustable freq, oneshot125 option, Dshot150 and Dshot300. Select "USE_ESC_DRIVER" or "USE_DSHOT_DRIVER" in hardware.h Esc settings are in drv_esc.c or drv_dshot.c</font> +
- +
-<font 13px/inherit>**H101:** PPM with adjustable freq, oneshot125 option, Dshot150, Dshot300, and bi-directional (3D) control. Select "USE_ESC_DRIVER" or "USE_DSHOT_DRIVER" in hardware.h Esc settings are in drv_esc.c or drv_dshot.c</font> +
- +
-<font 14px/inherit>**How to set up the Dshot esc driver:**</font> +
- +
-<font 13px/inherit>The H8 mini green and H101 have a Dshot option that can be selected if you want to use it with Dshot compatible BLHeli_S esc’s. The Dshot esc driver is selected in hardware.h. Then, in drv_dshot.c, select either DSHOT150 or DSHOT300, and adjust the IDLE_OFFSET number if you need to, in order to set the desired “idle” speed.</font> +
- +
-<font 13px/inherit>**Note** for Dshot: The signal can only be taken from before the FET (FET gate) for it to work. The Dshot driver (drv_dshot.c) has no provision to set the polarity.</font> +
- +
-<font 14px/inherit>**How to set up the PPM esc driver:**</font>+
  
 <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>
- 
-<font 13px/inherit>In **drv_esc.c** - the esc min throttle, esc max throttle and throttle_off values are set</font> 
- 
-<font 13px/inherit>Change the code in the **hardware.h** file to look like this to enable the esc PPM driver:</font> 
 <code> <code>
 //#define USE_PWM_DRIVER //#define USE_PWM_DRIVER
Line 50: Line 44:
 </code> </code>
  
-<font 13px/inherit>For the **drv_esc.c** file changes, have a look at the BLHeli [[http://static.rcgroups.net/forums/attachments/6/5/8/6/0/5/a9287300-73-blheli-default-xm20a-setup.png|screenshot]] of this esc. Notice the values in the bottom right corner in BLHeli, PPM Min Throttle 1148 and PPM Max Throttle 1832. These are BLHeli default values, and they need to be entered into the drv_esc.c file as shown below.</font> +<font 13px/inherit>In **drv_esc.c** - the esc min throttle, esc max throttle and throttle_off values are set</font>
- +
-<font 13px/inherit>A note from the first brushless page (written by the firmware author):</font>+
  
-<font 13px/inherit>"The PPM limits are usually found in the esc driver file, and should be set correctly. They do not necessarily correspond with the esc set limits, they may be slightly different. Especially important is the “minimum” limit, as the brushless motors should never stop in flight. The minimum limit should be set slightly higher in the code for this reason. A throttle check should be used to make sure the motors never stop above zero throttle."</font>+<font 13px/inherit>The default values for BLHeli_S are Min Throttle 1148 and Max Throttle 1832. The values in drv_esc.c need to be set so that the FC values match what the esc is expecting, so ESC_MAX can be set to 1832 and ESC_MIN is set a bit higher than what the esc is expecting, to raise the idle speed a little, and usually a value of 1152 to 1160 works well. It can be changed/tuned to suit your particular quad and preferences.</font>
  
 <code> <code>
-#define ESC_MIN 1160+#define ESC_MIN 1154
 #define ESC_MAX 1832 #define ESC_MAX 1832
 </code> </code>
  
-<font 13px/inherit>You can see I have added 12 to 1148 to get the 1160 ESC_MIN value, that is just a guess and will have to be fine-tuned for the quad. The final number might be 1170 for example, depending on the hardware in the quad. Another reason for adjusting the ESC_MIN value is to get a clean motor start, it can be adjusted to give a good “idle” speed where the motors will start and run reliably. If it is too high, the quad may lift off at minimum motor speed, so set it as low as possible, but high enough to still get consistent motor starts, and not stall during flight at low (but not “off”) throttle position.</font>+<font 13px/inherit>ESC_THROTTLEOFF is the value sent to the esc by the FC to to indicate the motors off condition. Anything under 1148 should work but I often use 960 to be sure.</font>
  
 <code> <code>
Line 67: Line 59:
 </code> </code>
  
-<font 13px/inherit>This tells the FC processor what signal to send to the esc to indicate throttle off condition. (It has nothing to do with BLHeli). 960 works for me, possibly any value from 900 to 1000 will work.</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>Finally, the PPM signal polarity needs to be set in drv_esc.c.</font> <font 13px/inherit>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>**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> <code>
Line 81: Line 67:
 </code> </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> <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> </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> <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> </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> <code>
Line 107: Line 91:
 </code> </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>+
  
  
more_brushless_setup_info.1516345314.txt.gz · Last modified: 2018/01/19 08:01 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