DShot Pass through not working on Holybro H7/Tekko32 stack

Hi all!

First time drone builder, struggling to get Arducopter setup with my ESC. Build:

  • Holybro Kakute H7 Flight controller, successfully flashed with latest stable Arducopter
  • Holybro Tekko32 F4 4in1 50A ESC (website says comes with BLHeli_32)
  • Spektrum SRXL2 receiver
  • Banner on mission planner is Mission Planner 1.3.82, Arducopter V4.5.6

I followed the instructions for setting up DShot ESCS (DShot ESCs — Copter documentation) and setting up BLHeli_32 passthrough (BLHeli32 and BLHeli_S ESCs — Copter documentation). I know I have telemetry from the ESC since I can see my battery voltage on mission planner. After plugging in my FC with USB, connecting with mission planner, then plugging in battery, I can arm with my transmitter. But Throttle inputs (which do show up on the RC calibration page) don’t spin the motors. I know I have DShot configured since I see this message in mission planner: “9/14/2024 10:09:42 AM : RCOut: DS1200:1-4 PWM:5-8 NeoP:9”. I’ve also tried with DShot600.

Similarly, I can successfully connect to my FC with BLHeliSuite 32.10.0.0, but trying to “read setup” gives me an 'ESC Configuration not found" for all four ESC’s.

Does anyone have troubleshooting steps? Like I said, I’m a first-timer and could be missing a simple step somewhere. Any ideas?

Thanks everyone!

Use DS600, although I’m not sure that will help. Please post your parameters.

I tried Dshot600 first; 1200 was just trying something else since I saw that helped another poster. Here’s my parameter list.

params.param (20.6 KB)

It all looks correct. Unfortunately you appear to be a victim of passthrough not working with certain board/ECS combinations. Your only option currently is to flash betaflight in order to configure the ESCs.

Sad, thanks for the reply though. Are you saying you would flash betaflight to the H7, configure the ESC through that, confirm ESC works, then reflash ardupilot to the H7? What would that change/help? Holybro’s page on the ESC says it comes with BLHeli32 installed, so what needs to be ‘configured’ through Betaflight to make it work that isn’t currently setup? Just trying to understand what I need to achieve here.

Thanks for the help!
Joey

You shouldn’t need to change anything - the configuration should be correct, so I would just leave it alone

There was likely something else going on.

I had asimilar issue, I swapped between these 3 settings and it started working on mine…
Screenshot 2024-09-14 144407

Same flight controller but I swapped ESC’s and they stopped communicating with pass thru. changed these settings and boom started working.

Was my summary of what you mean by “your only option is flashing beta flight” correct though? Are you recommending I try flashing betaflight, re flashing blheli32 through my now-beta flight FC (can I even re flash it since it’s dead now?), not changing any configuration, and hoping a clean install fixes something? I just want to use ardupilot and get the motors spinning, and I’m very confused on what paths I have available to me that might work. What would you recommend I do to get this working?

Thanks for help by the way, I appreciate it a lot!

I could only get this to connect to my flight controller on the USB/COM option. Then with the FC connection working I get “no ESC configuration found”. Were you able to connect to your FC with all three options, then only one gave you good pass through to your ESC?

It seems odd the motors don’t spin. Did you try motor test in mission planner? The config looks correct apart from using dshot 1200. Do you get any arming sounds from the motors?

One other thing I remembered is when I plugged up the esc’s. I had to usb power the flight controller first and wait until it connected then plug in the battery then click connect.

I do have a set of both of these. If I get a chance I will try wiring them up…

1 Like

None at all. No arming sounds, no beeps, no movement. I don’t know if this FC/ESC even has a beeper to use though. I only know I’m armed from the HUD in mission planner when I’m connected over USB. I also confirmed my throttle commands are going through the FC; if I arm then go to the serial output tab I can see my throttle commands change with stick input.

I tried motor test in Mission Planner but also got nothing.

Just for sanity sake, is it possible I messed up the ESC soldering it together? The joints all look pretty good to me, and I assumed the board is good since I’m getting good battery telemetry off it (?). I tried double checking for shorts with a multimeter and quickly realized any two wires on a brushless motor will read a short so that was useless.

Post a few photo of your build.

Then the 8 pin goes to another 8 pin on the Kakute H7 FC that’s labeled as M1-M4 on Holybro’s documentation. If there’s anything else I can give you that might help, let me know. Thanks!

That is some fairly awful soldering on that ESC. Looks like you need a higher watt iron and ample use of flux.

In order to create better solder joints, the PADs and the cable ends should first be individually tinned and only then connected with a little additional solder.
When tinning, first leave the cable ends longer and twist them a little, then shorten them with the side cutters and tin the tip again very briefly.

However, that is not the cause of the difficulties

All true statements lol. I did the best I could with the skills and equipment I had. Current goal is just to get the thing in the air in any capacity, then I’ll worry about my solder joint quality. Thanks for the tips for when I get to it though!

Any luck getting this combo working? Any tips on what I can try?

Thanks!