D-shot and Bl-heli Passthrough should make setting up esc's (that you can actually buy) a lot easier. Great Job! (also on chibios!) Now some hardware supplier should make a good (can-)esc so we can finally get all the information that is lost (trapped) in the esc (errors, temp, current, etc...)
Forgot to mention that for BLHELI_32 ESC's to actually run on arduplane, you must set SERVO_BLH_MASK to 4, assuming that ch 3 is your throttle channel, as it normally would be on a plane. BLHELI_S ESC's will work on both settings of this parameter. you do not need to reboot, just write params and it will work. Some of the duckumentation on the WIKI says that plane only supports "PWM" for non lift motors on quad plane, and ch 3 throttle for plane, but it's not true. You are welcome internet people.
Silly question, is this classed as esc calibration or does this need to be done still? we just moved to Dshot esc and are having a hard time with getting them set
@Nando, I agree that good CAN ESCs would be really nice, but I have implemented the ESC telemetry protocol for BLHeli_32 as well. We get RPM, current, voltage, total-current and temperature if you connect up the telemetry pin of the ESCs and you use DShot.
How is the telemetry from multiple ESC's connected to an ArduPilot FC? Usually on BetaFlight and the like, they're all wired to a single UART Rx pin. Is it possible to log things like RPM, current, voltage, etc? Could a smart throttle to amperage correlation spin-up test be initiated at the beginning of each arming, like DJI's do to check for propeller presence / damage? I've thought about building a board with a lot of amperage sensors to log data to correlate for motor-health monitoring over time. MTBF for brushless multirotor motors (specifically the bearings) can be less than 160 hours (even on premium u-series tmotors); hardware maintenance could be prompted for a motor that is consuming more amperage than normal once a baseline is measured and set.
Fan of BLHeli32 here and im really excited about this feature. I use blheli 32 so I can not worry about using a higher voltage battery or higher kv motor or higher pitch prop than the esc can handle because it can protect itself by limiting the current to not more than it or the windings of the motor could handle. I'm getting really good luck with them except those stupid programmable leds that break off the pcb..
IcemanFPV add some epoxy around the LED's. You could try coating them with an elastic glue like "fiber fix" as well. Hot glue won't hold up to the heat if you're driving the motors hard.
Have followed this video exactly. Thanks for taking the time to do it. Do the AUX ports need to be powered? And if so, through a BEC, or does connect the red wire to one of the ESC leads suffice. Once again, thanks for taking the time to do the video and sharing. Cheers
Good day, soon i will mount hobbywing e f35a esc with bheli firmware, for make it work properly i must follow the same procedure described on the video or its not necessary?
Hi,I was able to connect to the AUX/FMU side of the Pixhawk-4 after I loaded Ardupilot and Was able to see the Tekko32 ESCs with the BLHeli32.However, the ESC numbering is not matching with the X-Frame Quad that I have for some reason, ESC-1 shows up as ECS-5 and ESC-2 shows up as ESC-6 etc. The other information on the motors and their ESC setting is OK. How can I correct the numbering of these ESCs? Thank you again.
I have a genuine pixhawk mini. Tried this but no success. Does the pixhawk mini servo output not support the passthrough? I'm tired of taking the whole damn thing apart
I am still confused has anyone know of information of how this can be done with QGroundControl. I use a Pixhawk 2.4.8 flashed with the latest version. It would be nice to use this feature if only for the ability to change the motor direction. My BLHeli configurator is the Google Chrome app. Thanks
hi. I have a question. i got pixhawk 2.4.8 with 4.04 on fmuv3 connected to 4in1esc qbrain , flashed to blheli 14.9. I connected motors to aux 9-12 and set parameters for servo 9, 10, 11 and 12 to motor1, motor2, motor3, motor4, or 33, 34, 35 and 36. I have also disabled servo ouput 1, 2, 3 and 4. I set blheli passtrough to enabled and am using oneshot125 for esc protocol. But even if i set protocol to dshot150 , when i try to connect it connects, but than i hit read setup and it sais "Found multiple esc configuration in silabs mode" ESC1: no info ESC2: no info ESC3: no info ESC4:no info than i click ok, and than i get Serial interface Ardu connected succesfully. Connection to ESC1 failed! Please check data -und power-connections to the ESC. And i got my battery connected and full Any advice please? i'm really lost.
Hi, I connected my Pixhawk-4 and installed the Ardupilot. I then disconnected it and executed the BLHeliSuite32 as you showed, but it couldn't find or read any of my Tekko32 ESCs. I have set all the parameters for BLH and Servo as you showed, and configured a Pass-through Mask/Channel, but nothing. Below is what I see in the messages log. We need to know how the "TX" pins on the ESCs are connected to the Pixhawk-4 and which port and how that port is configured. Many Thanks. 12/22/2020 3:55:12 PM : Frame: QUAD 12/22/2020 3:55:12 PM : RCOut: PWM:1-8 DS1200:9-12 PWM:13-16 12/22/2020 3:55:12 PM : fmuv5 001D0039 34385119 39313933 12/22/2020 3:55:12 PM : ChibiOS: d4fce84e 12/22/2020 3:55:12 PM : ArduCopter V4.0.5 (3f6b43e3) 12/22/2020 3:55:12 PM : Frame: QUAD 12/22/2020 3:55:12 PM : RCOut: PWM:1-8 DS1200:9-12 PWM:13-16 12/22/2020 3:55:12 PM : fmuv5 001D0039 34385119 39313933 12/22/2020 3:55:12 PM : ChibiOS: d4fce84e 12/22/2020 3:55:12 PM : ArduCopter V4.0.5 (3f6b43e3)
Hello, please help. I have an orange cube. And several iflight 45A Slick ESC's. I have bought three sets of these, burned a few, but i keep running into issues with brand new ones, where they wont flash. Blheli says they are erased, or not activated. I have had this happen on several of them. Right now i have three in my quad that work fine, but i am getting ready to swap out that 4th one a 4th time. (Motor one in my case.) Nothing i do changes anything on these blown up esc's. I only have one flight controller so unable to test esc's on a different platform.
****SOLVED**** note that BLHeli 32.6.1.2 DOES NOT WORK with passthrough. I got a copy of 32.6.1.0 and its fine. ________________________________________________________ Help please. Ive followed the instructions on here and in the documentation. Getting -'found no valid ESC configuration' from the BLHeli suite. I think its getting to the cube but not 'passing through'. The esc is powered. Set all parameters exactly as explained. Posted the issue on 3.6 forum. Esc is a tmotor 4 in 1 F55A pro. The ESC is working for a motor test on AUX 1-4 in DShot150 mode. Dont know what else to try.
Hello, thanks for this amazing tutorial. I am getting this error while trying to connect to the blheli_suite "Initialization of serial 1wire passthrough or 4way interface failed"
Is there documentation anywhere on how to get this same process to work with a Pixhawk 4? I have BLHELI_S ESCs and cannot get this process to work with my Pixhawk 4 on Arducopter V3.6.4.
Excuse me. Why i don't have "SERVO_BHL_AUTO" and other "SERVO_BHL_" in my full parametrs list? Because of what I can have such a problem. I have version Mission_Planner 1.3.58
I can connect BL Heli 32 Suite to the Pixhawk via USB (while at the same time Mision Planner is connected via radio telemetry), but when I click "read setup", all I get a small box that shows 4 ESC's (I am using a 4-in-1), but there is no information there...just 3 short dashed next to each esc. Then when I click OK, I get another box that says "Serial interface "ARDU" connected successfully", and "Connection to ESC #1 failed, please check data und power connections to the ESC". So...what am I doing wrong? Do I have to move my ESC connector to one of the Pixhawk RC-9 thru RC-14 ports? (Right now it's connected to prop 1, 2 3, and 4. Thanks...
It would have been quite helpful to see a picture of a wiring diagram...it wasn't clear that the esc wires have to be moved from 1, 2, 3, and 4, to 9, 10, 11, and 12...the author said it was neccessary for a CUBE, but not for anything else (I have a Pixhawk, non-cube)...SO OK...I figured a couple things out (I think)...number 1 is the esc's have to be on battery power...this is not obvious as a person (me...ok...maybe dumb) could assume that the ESC is getting power thru the 5v connection from the pixhawk. So I set Servo 1, 2, 3, 4 to ZERO (which means DISABLED), then set servos 9, 10, 11, 12, to 33, 34, 35, 36. I actually don't know if 1 thru 4 had to be disabled, as that was before I had connected battery power. Now that I have ESC data...the BLHeli Suite thinks I have FIVE esc's...the first one is blank....then 2, 3, 4, 5 have data...weird.
Hello Bill, I have follow this video and the ardupilot wiki, but I'm having the same problem that you had in the beguining with the "Serial interface "ARDU" connected successfully", and "Connection to ESC #1 failed, please check data und power connections to the ESC" issue. I have four BLheli S ESC's that are connected to the first four auxiliary channels on the Pixhawk, and all the main channels are disabled. how do you solve your problem? Thanks
Well the first thing I realized is I did have to move my esc connectors to RC-9, 10, 11, and 12...sounds like you already did that (plus of course RC1, 2, 3, and 4 set to ZERO). That worked for me. Hmmmm...I'm not sure what else to say except that sometimes I had to reboot this or that to get it to work. Remember your esc's need battery power of course (just connecting USB power to Pixhawk won't do it).
Yes, I have all the ESCs connected to the auxiliary channels, also the main channels are all disabled, and ESCs are connected with the power battery. All the Mission Planner configurations seams to be correct, so I don´t know what could cause this issue. I have BLHeli_S ESCs so I need the BLHeli Suite 16, that is a little bit diferrente from the 32 version.
Paulo você conseguiu? Estou com uma pixhawk 2.1 e esc Littlebee em um frame tarot 680, mas os escs não estão calibrados (estão com rotacao de 10%) e preciso ajustar direção de giro. Escs estão soldados na placa, não utilizei conector banana pra economizar espaço...
Valeu pela sugestão, acho que vai ser o jeito...fazer um por um com Arduino nano..tô encucado com a rotação que não tá nem em 10%...tvz fazendo isso resolva
deu certo com arduino nano...tive que desabilitar o parametro "Low RPM Power Protect", ele tava limitando a rotação do motor...to usando em um tarot 680 hexa, motores rctimer 360kv
