Has anybody seen this issue and or know of a resolve with BLheli32?




Matek F405 FC flashed to current betaflight ver 3.2
Wraith 32+ esc's

It looks like it's connecting correctly through passthrough however it's showing me there's nothing on the esc's so I can't change any settings or flash them.  Just got the esc's the other day and finally got them installed but they've never beeped beyond what would be normal programming mode.  Am I missing a step that I need to flash them initially as it's the new closed source setup?

I don't have any experience with BLHeli32 ESCs or the BLHeli32 Suite yet but I just have to ask, is your battery plugged in?

(09-Jul-2017, 02:31 AM)RENOV8R Wrote: I don't have any experience with BLHeli32 ESCs or the BLHeli32 Suite yet but I just have to ask, is your battery plugged in?

Yes usb connected, open blheli32 suite, connect in configurator, plugged in battery, then attempted to read esc's and those are the messages I got.

(09-Jul-2017, 03:11 AM)Rhymin Wrote: Yes usb connected, open blheli32 suite, connect in configurator, plugged in battery, then attempted to read esc's and those are the messages I got.

Have you tried flashing them yet?  If so, did you get error messages then?  If not, I think that's what I would try.

(09-Jul-2017, 09:07 AM)sloscotty Wrote: Have you tried flashing them yet?  If so, did you get error messages then?  If not, I think that's what I would try.

Hence the reason I'm here, I have no way to flash them beyond passthrough nor not sure why I would even have to they're all of a week old.

(09-Jul-2017, 03:53 PM)Rhymin Wrote: Hence the reason I'm here, I have no way to flash them beyond passthrough nor not sure why I would even have to they're all of a week old.

Your "Flash BLHeli" button is active (in your screen shots).  That's why I would try it.  Who knows what they shipped those with?

Did you select the com port? I know I always forgot.

Have you chosen an analog ESC protocol in betaflight? I'm not familiar with blheli 32, but I know that with blheli_s you could not use dshot when using blheli passthrough

As you can see in the SS it shows they are connected (and it's on com port 3 as in the SS).  The second of the two SS is the message you get when you click the flash BLheli button.  I'm almost starting to think I have an issue with my flight controller and the passthrough more so than the esc's themselves.  I have another FC ordered and on the way.

Doesn't matter what protocol you choose in betaflight it still shows the ESC's as blank within blheli32 config. And actually you can choose Dshot through betaflight I have another multi running 600 just fine however that copter has BLheli_s esc's. With the newest beta version of betaflight Dshot 1200, and powershot 1000 is actually in the drop down menu you don't have to go change motor pwm in CLI.

Just because pass through doesn't work, it doesn't mean your FC is bad. I couldn't update my ESCs with pass through with the firmware on the shipped ESCs. I had to flash all ESCs using C2 port. Once I flashed, I was able to use pass through for future firmware updates. Go figure.

I don't think the protocol really matters when you are trying to flash ESCs.

It looks like you have to flash the ESCs the hard way.

(09-Jul-2017, 11:43 PM)voodoo614 Wrote: Just because pass through doesn't work, it doesn't mean your FC is bad. I couldn't update my ESCs with pass through with the firmware on the shipped ESCs. I had to flash all ESCs using C2 port. Once I flashed, I was able to use pass through for future firmware updates. Go figure.

I don't think the protocol really matters when you are trying to flash ESCs.

It looks like you have to flash the ESCs the hard way.

I officially have a fc issue now as the processor chip released it's magic smoke on me yesterday but beside the point. I went and picked up an arduino board so while I'm waiting for my new fc to come via snail mail I'm gonna have to learn how to do it the hard way looks like.

(10-Jul-2017, 01:42 PM)Rhymin Wrote: I officially have a fc issue now as the processor chip released it's magic smoke on me yesterday but beside the point. I went and picked up an arduino board so while I'm waiting for my new fc to come via snail mail I'm gonna have to learn how to do it the hard way looks like.

Too bad about your FC. Depending on where you buy it, likely they will send you a replacement.

Always good to learn how to do things differently. An arduino is so useful, especially in this hobby. You might be able to update using the one wire technique and don't have to deal with C2 port. Oscar has a tutorial on his blog.

(10-Jul-2017, 07:40 PM)voodoo614 Wrote: Too bad about your FC. Depending on where you buy it, likely they will send you a replacement.

Always good to learn how to do things differently. An arduino is  so useful, especially in this hobby. You might be able to update using the one wire technique and don't have to deal with C2 port.  Oscar has a tutorial on his blog.

I sent RDQ a message regarding the FC so will have to see if there's anything that can be done with it, if not I'll chalk it up to being a noob and eat it sadly.  Although knowing why it smoked would be helpful in my learning processes, that Matek FC and PDB are pretty straight forward with the ribbon cable.  Who knows...

I'll have to go and see if I can't find that blog, I have found a ton of good information from his others as well.

(10-Jul-2017, 11:17 PM)Rhymin Wrote: I sent RDQ a message regarding the FC so will have to see if there's anything that can be done with it, if not I'll chalk it up to being a noob and eat it sadly.  Although knowing why it smoked would be helpful in my learning processes, that Matek FC and PDB are pretty straight forward with the ribbon cable.  Who knows...

I'll have to go and see if I can't find that blog, I have found a ton of good information from his others as well.

Matek just released they new FC AIO with built-in PDB.

Just wanted to say thanks to everyone for their input and suggestions for troubleshooting this.  Got my new FC in the mail today and it looks like that's fixed my issues with the passthrough.  Didn't really ever mess with the Arduino board but it looks like I didn't need to.