I remember back to when Helio tried to convince the community that Open Source could not be trusted to support the community or be sustainable. 😂 OPEN SOURCE FTW on this one.
I have a customer build with 32.9 that needs the update to 32.10 that will not work with 3D mode till it is. This is extremely frustrating, and this is unacceptable. This sets back the 3D community... Hai AM32 devs... need some testers for 3D?
opening the blheli32 bootloader is the only way to properly support users going forward. It wouldn't need more than that and would be a good final gesture from the blheli32 team.
While posting on a closed source video platform, probably posting from a closed source phone, via some closed source WiFi access point, across some closed source Internet provider, while wearing some closed source shoes, inside your closed source house. See where this is going
@@paulrobinson270 OP's post is about a lack of trust in closed source products (which I agree with), not whether people use them. Using closed source products doesn't negate concerns about their trustworthiness.
99% of people who complain about closed source this and open source that wouldnt know what a pull request or a git push was. And I bet not one of them has looked at the source code for betaflight. Blheli32 was not a community project, it was a commercial one.
@@paulrobinson270 nor (apparently) do most people understand the RFC process which ensures that the internet is essentially open source, (IIRC the internet is actually free as the RFC process requires a protocol have 2 free reference implmentations before it can be RFCd) or that most ISPs - at least where I live - run massive amounts of open source software. Despite not knowing that the Internet is free, many people benefit from the Intertet and understand it's benefits. You don't need to know about pull requests and pushes to benefit from open source, and you don't need to know how to write or read code to understand the risks of closed source. Not sure if you've noticed but "opensource" has moved on from a time where it only pertains to software.
I bet someone saw that announcement and immediately went "oh no you don't. Challenge accepted". Remember how DJI didn't allow OSD on the older goggles and the Wtf.FPV team did their thing? In the long run the community will go Open Source anyways - this doesn't worry me at all.
8 years I've been in fpv, built 217 quads....and I can count the number of times I needed to flash esc one hand. I kinda laughed when they closed, because I've never seen an improvement in 32 that made any difference to me (variable pwm, meh 🤷♂️) this really doesn't seem to be a big deal, so long as manufacturers can crossover without interrupting supply chain. I've talked to 2 esc manufacturers, who both said they had plenty of licenses for the immediate future, and both already have AM32 implementations. Be curious if the update servers going offline impacts manufacturing, more than individuals.
Someone had pointed out that variable PWM just causes issues with the gyro and makes quads harder to tune than for example running a constant 48khz. Agreed there isn't any real benefits to blheli_32 over am32 or bluejay.
32.10 fixed the esc not working after bumping into the ground... I only have 1 of my 20+ quads "fixed" I have a few on broken 32.8 that I never got around to fixing...
I think that even though it is rare, the motor spool up bug that has been fixed is serious. Even if it’s a 1 in 100,000 times chance for it to happen upon plug-in (I’m making this up-I don’t know what it is) that’s still an unnecessary risk just because BLHeli have chosen to do the wrong thing here.
I'd like to know how these "licences" work... Do manufacturers need to use this licence in order for their software to download and flash the firmware to the ESCs? Or (more likely) do they have the offline file for the firmware and the licences just say how many ESCs they can legally flash it to? If it's the latter, what's to stop ESC manufacturers from just continuing to flash that file to their ESCs and selling them like that (even when they run out of licenses) - since Blheli doesn't exist anymore & this can't come after them for flashing it without a licence? That would be a bad outcome for users, however, as we'd be stuck with whatever firmware they shipped it with and not be able to update...
Really appreciate you for making a video on putting am32 on bheli32 esc. It looks crazy complicated but I know a video from you will be amazing to follow along with. Thanks for all you do!
I've got a box full of single 32-ESCs that are still unused, how the hell.... Edit: Just checked, the AM32 has Servo PWM, Dshot(300, 600) motor protocol support and Bi-directional Dshot .. So that's good for a new start. :)
I've never seen a whole operation just vanish like that, its all very strange. Hopefully someone on the team is able to keep blheli_32 alive one way or another
Yeah, after watching your last video yesterday evening i tried to get my BLHeli32 AIO's to the latest version and was bummer'd when the server did not work anymore ... let's hope somebody has already mirrored the hex files ;)
Still have the bootloader issue, which prevents an update without looking to the server for a valid license comparison. Once a bootloader is solved, then a mirrored hex would work, until then, nope.
One idea would be that they open a window for 2 weeks for everyone who wants to update their BL32 ESC in the hobby. With enough advance notice, of course. And all the influencers should be informed about it so they can spread it further...
An update to unlock the bootloaders wouldn't cost them anything and it might save them getting sued. But this is the problem with closed source solutions. I guess in time someone will work out how to hack the bootloader and wipe out the problem. There are lots of super intelligent people in this community.
One problem for us is we don't have a relationship with BLHeli AS. We as buyers of BL32 ESCs have relationships with retailers or at best ESC manufacturers. BLHeli AS's realtionship is with the various ESC manufacturers.
I was nearly nipped by one of my quads on older firmware, luckily I was uninjured and got to update to 32.10 before this debacle. A poor situation to be sure.
I am a 65 year old simpleton in the 5 years of fpv 1 time I tried to update an esc after watching JB's video and I burned it so after that never again and I have never had any reason to update any esc so I have been able to spend more time flying less time on the bench how many times do you really need to update your esc's
This has to be hard on resellers of BLHeli AS ESCs. This worse than if a company goes bankrupt. They're now have inventory that needs refreshing, and has decreased in value, as there is no manufacture support. Hopefully any BLHeli ESC in inventory can be flashed, or converted to other firmware. Technically resellers can not even re-flash BLHeli AS firmware to latest version, as their licenses to do so has be invalidated. If there are know safety issues, that would mean BLHeli AS would be breaking consumer protection laws (at least in U.S., not sure about Norway, or other parts of the world)
Its actually pretty simple for manufacturers - they build a bed of nails, write a simple script and flash all their ESCs with AM32 or any other open source firmware.
The fact that they are legally protecting themselves against sanctions does not mean that it will somehow be possible to do firmware updates offline unofficially, made possible by some hackers, spread on some website.... (so BLHeli AS is not to blame for this)... I hope that this will be the case and also will be safe. However, the manufacturers will probably still be prevented from selling BL32 ESCs...I want tzhe update because I have 3x BL32 ESCs in the box that may need the update from 32.9 to 32.10 due to 3D mode.
Few yrs ago i was thinking that they would dump down users like dji when they dump hundreds of thousands of naza users .. as you said the future is for open source products.. and open source products only . I am sad to watch it happening and the worse still coming from those start dumping users w/o naming the big elephant!
I use a bench-power supply when I don't want to plug a battery in. The one I have, I got for like $40~$50. 30volts (adjustable down to 0.01volts @10Amps. It's helpful for small testing, as I build, or troubleshoot. Just be really careful, not to let the contacts slip and arc where they shouldn't be arcing, if you go that way.
Has the source code hex been available or temporarily stored somewhere? I mean, we could flash the hex (either found somewhere or compiled for source that might be around somewhere) via stlink without the blheli32 suite that's now dead without the servers.
The 32.95 firmware which fixes the spoolup issue is in the source code. Problem is you still can't update even with a local hex file. We need someone to get around the software trying to check the servers before an update.
@@MadRC yeah definitely not the best outcome, but a possible work around. In regards to bootloader, would the manufacturers have this? Being that the company is closed maybe they could share it without ramifications.
32.9 is not safe ? Because I bought 3x ESCs at September 2023 that I wanted to install for this summer (this month). And if 32.10 doesn't come out until November 2023. So I probably have the bad 32.9 on them ?
No it’s not quite as simple as that. There have been reported issues with un commanded spin ups on many drones and esc and there seemed to be something with 32.9. However no bug was ever found however the dev added some additional safeguards to mitigate potential but it’s never 100%. There is no absolute facts that the esc firmware was bad or that it was fixed. They just make some changes.
@@MadRC Great answer TY. This and since I fly 3D and have a centered gimbal, I still run the risk of something happening despite double or triple arming. That's why I'm thinking about getting thick leather gloves that I only put on when I connect or disconnect the battery. I've also had experience with a spin up that really shouldn't have happened and I've reported on that (title "don't make tjis mistake i destroyed motors during 3d config"). Luckily I didn't have any props on it. I've also increased safety measures since then.
Thanks as always for the informative video! Just to be clear, it is still generally okay to make changes for ESC on 32.9? Or should we leave the default settings as-is?
One year of development, by one person with less than 50 commits in git history, no pull requests, no discussions in the repo. All sings of not for production usage.
And of course one of my esc aren't being recognized and I have to reflash my 4-1 and i cant. I hope they come up with a solution because as of now I have a brand new esc that I can't use!!! Bullshit!!!
@@MadRC The 32.9 is perfectly fine for me. I have 2 pcs of sealed Velox V50A and I hope its on 32.9. I also just ordered that new Velox F7 stack with Velox V50A SE in it.
@@raphaelpirker3406 any updates for that 500Hz Tracer firmware? Sent an email a while back about the bugs I ran into on v131.37 but never got an update.
@@raphaelpirker3406sooo, just the FC has 20x20 mounting then? And, it requires a bracket to actually make this work correctly? Well, sure you can say it's compatible with 30.5x30.5 or 20x20. But, it requires a bracket to even mount the ESC in the first place. Making the stack even taller and requiring more room to fit the ESC in the first place. Got it.
Its not just our hobby it's more or less our lives. This is why right to repair is important. The same think can happen with more or less any other product with a microporcessor and firmware. Of just think what happens if their corporate network gets cracked by a bad actor and they lose acccess to their source - e.g. ransom ware, cyberwarfare. Think your car, your voting machine, your government's guided missile (defense contractors charge a premium for IP so gov's don't always buy it.) . your microwave oven.
Yes and ... on the other hand this is a small business deciding to fold and lose their income to prevent their product from being used to hurt people. It is just as likely that a small business would fail for other reasons. It's not "just manufacturers getting away with it" as much as us, the consumer, being unaware of accepting the risks. Remember CDs with offline driver installers?
@@SeanPoulter your correct. I edited my comment but I was actually referring more towards other parts of the hobby.The blheli-32 guy is actually loosing from what I understand to be a significant amount of money for what most of us believe to be a noble cause regardless he can do what he wants.
Uh...you mean going out of business? Sometimes people go out of business. I don't know why you have this attitude of "letting" them do anything...creating the stuff we use is extremely difficult and time consuming. If anything, you owe all the people who do that. You've been given the gift of technology you could never create on your own. And yet somehow you feel entitled in that position. So strange to me. In what way would you not "let" them get away with this exactly? Force them to keep working? Not allow them to change jobs? Slave labor? Or maybe you feel it should've all been open source? Well, no one was stopping anyone...make an open source version. You can't blame these folks for supplying you with a product.
@@geometerfpv2804 I was speaking of hardware NEVER free open source firmware which I contribute to every month with the acception of INAV I don't fly beta flight and still contribute. Hardware companies. Speedybee, skyzone, matek, holybro, fat shark, betafpv probably more. All have had issues in the past know amongst the community, have revised the product to actually work but don't replace parts they know are bad. Either you've been in the hobby for a week or you've been really lucky. I give two shits what a person does or where they work with your slave labor bullshit remark. 32 wants to close shop fine especially for the reasons they chose.
Can someone please explain what were the major advantages of BL32 over bluejay? Because to me it seems like Bluejay just does more with less and it’s open source.
@@MadRC I get that. But is there like functional difference between the two? I've seen Chris Rosser's testing and there doesn't appear to be a definitive BL32 superiority.
Yes I know, but no one has ever proved that a BL32 ESC flies better than a Bluejay ESC. Even though BL32 ESCs are more expensive. I'd like to see someone do laptimes on a BL32 based ESC quad and then a Bluejay based ESC quad to see which is fastest.
@@putrid.p ofc its relevant. People who put their faith into 32 bit hardware and the closed nature of BL32 have now been burned. What benifits did they get for their trouble over people who stuck with 8 bit hardware and open source? Cause no one has ever proven 32 bit flies better. Seems like the smart choice was sticking with 8 bit ESC.
@@ChinaExpatsRC The advantage of 32bit is purely they can natively support dshot with hardware dma. What this means is that when running very fast dshot at high rates the mcu wont get overloaded. But like you honestly I think my spedix 32bit escs performed no better than my dys xs30 in actual real usage.
@@MadRC Would the process be anything like setting fuses in an Arduino? Or something else, entirely? I think there are a lot of us, who are excited for the notion of learning the process.
Their proprietary blheli_32 can rot in hell. They did not contribute to the opensource project, they commercialized it for profit with minimal work, and if you were effected than let it be a lesson to you about this hobby!
What are you talking about... Telemetry, 32 bit, bidirectional dshot support. There's a reason every high end ESC has blheli32. If it was so easy to do, the manufacturers would have thrown a few bucks to make their own instead of licensing
@@chezfpv9139 whoosh, right over your head I see. Keep running blheli_32 and tell me how that works out for you. Point is stick to open source or your equipment is subject to end of life due to some bozo company's situation. 😉
Yeah this is confirmation bias...they made lots of industry first improvements. Closed source often does (DJI anyone?...let me guess, you hate them too...we had been stuck with analog for a decade plus, and no one was working on anything new...).
@@geometerfpv2804 DJI is a company in it to make money, if you want a stable, reliable commercial drone go with DJI, I did. When I tinker in the drone making hobby I want open source because its hobby friendly. Think if IBM kept computer architecture proprietary, we would not be having this conversation right now.
You must be a very active person in the open source community, creating tons of code for free with deep understanding of the community ... or just a moaning westerner that assumes software, and others people time is for free?
how many of you will now switch and start using linux instead of microsoft windows? Somewhere around 0.0001% I suppose because you don't learn. And then you'll cry again when something similar happens with your computers
The whole Ukraine thing is a copout... that's like gun companies not making guns because of misuse.....or phone companies not making phones because of drug dealeds😂😂
It certainly has me scratching my head. If every single, secret sauce digital camera, transceiver video-tech, shut their door tonight, and took every proprietary, motion sensor, and motor controller software provider with them, and they all took every untold secret, and went home, to have one great-big "Non-Disclosure Party" to never be heard from again... Well, cameras would continue to fly. That genie's out of the bottle.
BLHeli_S is not affected, BLHeli32 is, as it's operated under a licensing situation. Requires servers do a "check" upon update, which are currently offline so NO updates are possible, but BLHeli_S is still able to be update and you can run firmware like BlueJay or JESC etc to still get RPM filtering and what not.
Seems like they're givin' us, the tall finger. 😐 What good is advanced hardware when it leads to dependent broken coding/software? It becomes fully useless. Someone needs to crack it, it's not that difficult. Just don't try to produce anything with it, for revenue. That's stealing intellectual material for profit. Cracking it and sharing the files is not a problem. The problem is reproducing it for-profit. Sounds to me like they've sold a bunch of products that you cannot control; meaning modify and repair. I'm certain that wasn't part of their business plan. My intuition is telling me that it's something regulatory[governmental] ; where they are attempting to stifle any type of growth [saturation]. We can already see that drones are used in warfare, and I believe that's a valid consideration in this particular instance. My personal opinion is that sux and it's bullshit. They're copping out on their responsibility to thier consumers. [Of course I know nothing of their business structure, practices or economic health. I'm making my own educated assumptions, just like all of you. Appreciate it, Ian and thanks. @Mads Tech
On the bright side... every single person who lives for this hobby is a problem solver. And I'd wager that a majority of those problem solvers, are also a little smarter than the average bear.🤪 *even if we are a bunch of sh1t pilots*
safety is the priority number 1 cause it can kill the hobby especially in bigger quads And this one is well known , I mean the issue is well known and not something mysterious that has not happened.
Not acceptable. Sure, leave the business. But, never leave users without the option to upgrade to the latest firmware. This would be your last commitment, almost. Have you ever heard of post-market surveillance? Not that this legally applies to BlHeli but ......This is not the way to begin or end a withdrawal.
It is fascinating to hear the demands for a duty of care and responsibility to have a safe product, but also not want government over-regulation or to pay the prices for well engineered software or a certification process.
is there at least 1 person which thinks of Putin shutting down the drone threat from ukraine with this move? its not a permanent solution, but having some time is signifikant in this case. we cant blame Steffen for shutting down his baby and business, we do not know at all what did lead to this. i think there is much more behind.... we just dont know. who would shut down such a good business? i would not at all
pilots should stop using the github issue tracker for ranting. the O.P. was good and a few comments were good, but now everyone adding their 2 cents going to make the devs annoyed. they will do what they are capable of as time permits. if they dont, then oh well.
Why not bluejay as well though? Don't get me wrong, I've been running AM32 and it's always been absolutely fantastic. But I can say the same for bluejay. It supports all the important features for our quads. I understand theoretically AM32 has the 32 bit advantage but in practice, honestly, it's difficult to really pin down that advantage. Plus the bluejay ESCs tend to also be cheaper and they are a lot easier to flash. I think it's also a very good alternative. Especially now where it is much much simpler to just flash it.
@@Quick-Flash I understand that you can't flash your current BL32 ESCs. I just meant that I think bluejay is also a very good option to use moving forward as an alternative. As in, as a consumer, when purchasing a new ESC :) It's also a good project to support imho
Leave everyone high and dry, blame Russia, call it a day. Yeah, I think I'll learn about those involved to avoid doing business with them in the future.
I remember back to when Helio tried to convince the community that Open Source could not be trusted to support the community or be sustainable. 😂
OPEN SOURCE FTW on this one.
I have a customer build with 32.9 that needs the update to 32.10 that will not work with 3D mode till it is. This is extremely frustrating, and this is unacceptable. This sets back the 3D community...
Hai AM32 devs... need some testers for 3D?
Reach out to them Zoe I’m sure they would love to have your feedback. I’m a massive fan of your work 😊
💯 straight up ass holes for not just letting it go open source. They were just like we don't wanna do it anymore & nobody else gets to use it ...
32.9 is borked always has been
@@Sugar_K Been sitting here having an existential crisis all day lol
@@ZoeFPV poor thing! You taking to the am guys yet if not I can point you in the right direction…
opening the blheli32 bootloader is the only way to properly support users going forward. It wouldn't need more than that and would be a good final gesture from the blheli32 team.
As you see you should never trust closed-source solutions.
While posting on a closed source video platform, probably posting from a closed source phone, via some closed source WiFi access point, across some closed source Internet provider, while wearing some closed source shoes, inside your closed source house. See where this is going
@@paulrobinson270 Yet you participate in society, curious!
@@paulrobinson270 OP's post is about a lack of trust in closed source products (which I agree with), not whether people use them. Using closed source products doesn't negate concerns about their trustworthiness.
99% of people who complain about closed source this and open source that wouldnt know what a pull request or a git push was. And I bet not one of them has looked at the source code for betaflight. Blheli32 was not a community project, it was a commercial one.
@@paulrobinson270 nor (apparently) do most people understand the RFC process which ensures that the internet is essentially open source, (IIRC the internet is actually free as the RFC process requires a protocol have 2 free reference implmentations before it can be RFCd) or that most ISPs - at least where I live - run massive amounts of open source software.
Despite not knowing that the Internet is free, many people benefit from the Intertet and understand it's benefits.
You don't need to know about pull requests and pushes to benefit from open source, and you don't need to know how to write or read code to understand the risks of closed source.
Not sure if you've noticed but "opensource" has moved on from a time where it only pertains to software.
I guess this leaves the door wide open for reverse-engineering and hacking/cracking attempts then… Getting the popcorn ready. 😅
I bet someone saw that announcement and immediately went "oh no you don't. Challenge accepted". Remember how DJI didn't allow OSD on the older goggles and the Wtf.FPV team did their thing? In the long run the community will go Open Source anyways - this doesn't worry me at all.
8 years I've been in fpv, built 217 quads....and I can count the number of times I needed to flash esc one hand. I kinda laughed when they closed, because I've never seen an improvement in 32 that made any difference to me (variable pwm, meh 🤷♂️) this really doesn't seem to be a big deal, so long as manufacturers can crossover without interrupting supply chain. I've talked to 2 esc manufacturers, who both said they had plenty of licenses for the immediate future, and both already have AM32 implementations. Be curious if the update servers going offline impacts manufacturing, more than individuals.
Someone had pointed out that variable PWM just causes issues with the gyro and makes quads harder to tune than for example running a constant 48khz. Agreed there isn't any real benefits to blheli_32 over am32 or bluejay.
32.10 fixed the esc not working after bumping into the ground...
I only have 1 of my 20+ quads "fixed"
I have a few on broken 32.8 that I never got around to fixing...
@@RCRitterFPV if I "bump" into the ground and the esc stops working, I can guarantee that FW isn't going to fix it 🤣
I think that even though it is rare, the motor spool up bug that has been fixed is serious.
Even if it’s a 1 in 100,000 times chance for it to happen upon plug-in (I’m making this up-I don’t know what it is) that’s still an unnecessary risk just because BLHeli have chosen to do the wrong thing here.
I'd like to know how these "licences" work... Do manufacturers need to use this licence in order for their software to download and flash the firmware to the ESCs? Or (more likely) do they have the offline file for the firmware and the licences just say how many ESCs they can legally flash it to? If it's the latter, what's to stop ESC manufacturers from just continuing to flash that file to their ESCs and selling them like that (even when they run out of licenses) - since Blheli doesn't exist anymore & this can't come after them for flashing it without a licence? That would be a bad outcome for users, however, as we'd be stuck with whatever firmware they shipped it with and not be able to update...
Really appreciate you for making a video on putting am32 on bheli32 esc. It looks crazy complicated but I know a video from you will be amazing to follow along with. Thanks for all you do!
I've got a box full of single 32-ESCs that are still unused, how the hell....
Edit: Just checked, the AM32 has Servo PWM, Dshot(300, 600) motor protocol support and
Bi-directional Dshot .. So that's good for a new start. :)
I've never seen a whole operation just vanish like that, its all very strange. Hopefully someone on the team is able to keep blheli_32 alive one way or another
Yeah, after watching your last video yesterday evening i tried to get my BLHeli32 AIO's to the latest version and was bummer'd when the server did not work anymore ... let's hope somebody has already mirrored the hex files ;)
Still have the bootloader issue, which prevents an update without looking to the server for a valid license comparison. Once a bootloader is solved, then a mirrored hex would work, until then, nope.
I bought skystars stacks about a month ago and swapped over and LOVE it along with the AM32 its all lovely!
One idea would be that they open a window for 2 weeks for everyone who wants to update their BL32 ESC in the hobby. With enough advance notice, of course. And all the influencers should be informed about it so they can spread it further...
that is an incredibly stupid idea. not everyone lives online or followers "influencers". no
An update to unlock the bootloaders wouldn't cost them anything and it might save them getting sued. But this is the problem with closed source solutions. I guess in time someone will work out how to hack the bootloader and wipe out the problem. There are lots of super intelligent people in this community.
Ian, as always, great video. Thank you for pressing BLHeli for answers!
One problem for us is we don't have a relationship with BLHeli AS. We as buyers of BL32 ESCs have relationships with retailers or at best ESC manufacturers. BLHeli AS's realtionship is with the various ESC manufacturers.
Great my two skystars escs are now locked on older firmware
I would very much like to see a tutorial on installing AM32 on an AIKON AK32 55A V3, or a 4-in-1 like this.
I was nearly nipped by one of my quads on older firmware, luckily I was uninjured and got to update to 32.10 before this debacle. A poor situation to be sure.
I am a 65 year old simpleton in the 5 years of fpv 1 time I tried to update an esc after watching JB's video and I burned it so after that never again and I have never had any reason to update any esc so I have been able to spend more time flying less time on the bench how many times do you really need to update your esc's
To fix bugs or to get new features. If the quad flies good, there's really no reason to update
Great...
Waiting for someone to publish the software
Because blheli 32 is closed source I never did like to use them. I just got lucky I stayed away from them.😊
This has to be hard on resellers of BLHeli AS ESCs. This worse than if a company goes bankrupt. They're now have inventory that needs refreshing, and has decreased in value, as there is no manufacture support. Hopefully any BLHeli ESC in inventory can be flashed, or converted to other firmware. Technically resellers can not even re-flash BLHeli AS firmware to latest version, as their licenses to do so has be invalidated. If there are know safety issues, that would mean BLHeli AS would be breaking consumer protection laws (at least in U.S., not sure about Norway, or other parts of the world)
Its actually pretty simple for manufacturers - they build a bed of nails, write a simple script and flash all their ESCs with AM32 or any other open source firmware.
Escape32 looks to have some promising features
The fact that they are legally protecting themselves against sanctions does not mean that it will somehow be possible to do firmware updates offline unofficially, made possible by some hackers, spread on some website.... (so BLHeli AS is not to blame for this)... I hope that this will be the case and also will be safe. However, the manufacturers will probably still be prevented from selling BL32 ESCs...I want tzhe update because I have 3x BL32 ESCs in the box that may need the update from 32.9 to 32.10 due to 3D mode.
Few yrs ago i was thinking that they would dump down users like dji when they dump hundreds of thousands of naza users .. as you said the future is for open source products.. and open source products only . I am sad to watch it happening and the worse still coming from those start dumping users w/o naming the big elephant!
Bluejay for the win! Cheaper, opensource, and works fantastic!
8bit bluejay is not even close to blheli32
@@grampafpvBlheli32 is no even close to Blheli32
@@grampafpv Why not? It lacks some resolution, but has equal power. Check Chris Rosser's lab tests.
@@grampafpvone exists and is supported, the other is not
Thank you for this Ian.
How can I check the FW on my escs without soldering them to xt60 plug?
I use a bench-power supply when I don't want to plug a battery in. The one I have, I got for like $40~$50. 30volts (adjustable down to 0.01volts @10Amps. It's helpful for small testing, as I build, or troubleshoot. Just be really careful, not to let the contacts slip and arc where they shouldn't be arcing, if you go that way.
Has the source code hex been available or temporarily stored somewhere? I mean, we could flash the hex (either found somewhere or compiled for source that might be around somewhere) via stlink without the blheli32 suite that's now dead without the servers.
I have a few old blheli32 escs that are literally running firmware from 4 years ago... Will they still work? Lol
Yep will be fine.
The 32.95 firmware which fixes the spoolup issue is in the source code. Problem is you still can't update even with a local hex file. We need someone to get around the software trying to check the servers before an update.
Yes I did see it. But it’s a beta so not 100% clear
@@MadRC yeah definitely not the best outcome, but a possible work around. In regards to bootloader, would the manufacturers have this? Being that the company is closed maybe they could share it without ramifications.
32.9 is not safe ? Because I bought 3x ESCs at September 2023 that I wanted to install for this summer (this month). And if 32.10 doesn't come out until November 2023. So I probably have the bad 32.9 on them ?
No it’s not quite as simple as that.
There have been reported issues with un commanded spin ups on many drones and esc and there seemed to be something with 32.9. However no bug was ever found however the dev added some additional safeguards to mitigate potential but it’s never 100%.
There is no absolute facts that the esc firmware was bad or that it was fixed. They just make some changes.
@@MadRC Great answer TY. This and since I fly 3D and have a centered gimbal, I still run the risk of something happening despite double or triple arming. That's why I'm thinking about getting thick leather gloves that I only put on when I connect or disconnect the battery. I've also had experience with a spin up that really shouldn't have happened and I've reported on that (title "don't make tjis mistake i destroyed motors during 3d config"). Luckily I didn't have any props on it. I've also increased safety measures since then.
Just had a question.
Does this affect any Bl-heli S esc's?
Iirc, s was opensource. But don't quote me on that! 😊 Also, if it ain't broke, why fix it?!.......
Nope, blheli-S already has bluejay as its successor
No S is fine but It’s been abandoned for years now anyways. You shoud flash bluejay as it’s simple and better.
just sad and frustrating. I really hope the 32.10 files get published somewhere.
Thanks as always for the informative video! Just to be clear, it is still generally okay to make changes for ESC on 32.9? Or should we leave the default settings as-is?
There is no issues making changes to settings.
I am very impressed by how silent the topic of Escape32 is.
One year of development, by one person with less than 50 commits in git history, no pull requests, no discussions in the repo. All sings of not for production usage.
@@wKich and Russians… lots and lots of Russians
@@wKich and Russians... lots of Russians..
@@wKich So you've seen some nonsense somewhere and decided to copy-and-paste? Smart move.
@@senyx0 wow, take a look who is here. An author who can't accept facts. If you don't understand what bus factor means, I have bad news for you
Missing the git link to issue in description
Just added
github.com/bitdump/BLHeli/issues/743
Yeah this is crazy can’t do that
Update my esc firmware? Is that a thing?
Can we flash different (AM32) firmware onto our existing ESCs with blheli32?
Real talk. Do you think Betaflight and other wares might go this direction?
No Betaflight is fine. As is ELRS. We can’t comment for other systems though that are closed source.
And you said you were not good at doing thumbnails….😂😂😂
And of course one of my esc aren't being recognized and I have to reflash my 4-1 and i cant. I hope they come up with a solution because as of now I have
a brand new esc that I can't use!!! Bullshit!!!
How long ago were the bug fixes corrected with new releases? Are manufacturers still selling buggy ones?
It’s about 7 months and yes ESCs are still shipping with the 32.9
@@MadRC The 32.9 is perfectly fine for me. I have 2 pcs of sealed Velox V50A and I hope its on 32.9. I also just ordered that new Velox F7 stack with Velox V50A SE in it.
Kinda wondering if someone bought the firmware. Would explain why they ceased and firmware unavailable.
Most likely
I just bought some bheli32.. my quad will be stuck in multishot I'll guess 😓
why? Shouldn't support most protocols already?
I really hope no one will ever do business with these individuals, especially in the DIY and RC community.
They trying to hurt FPV...thats not good
I think to Update my ESC so i cant can flight because my motors didnt work. So i need to wait, or what?
The update will have no impact on your motors or esc working.
@@MadRC The Motors Work when i start them in Beta flight. But Beta flights disable arm the Motors because MOTOR_PROTOCOL and DSHOT_TELEM
We might see lawsuits in the aftermath of this.
I noticed TBS released some AM32 esc's yesterday. TBS lucid 6s 4 in 1.
Only one problem with it, it's neither 20x20 or 30x30 mounting...
So, no go for me and probably the majority of us.
@@BikeGuyFPVit actually supports both. 30.5 x 30.5 as well as 20x20 mounting.
@@raphaelpirker3406 any updates for that 500Hz Tracer firmware? Sent an email a while back about the bugs I ran into on v131.37 but never got an update.
@@raphaelpirker3406
Any updates for Tracer 500Hz? Sent a email a while back giving you a report for v131.37 and never heard back from ya.
@@raphaelpirker3406sooo, just the FC has 20x20 mounting then? And, it requires a bracket to actually make this work correctly?
Well, sure you can say it's compatible with 30.5x30.5 or 20x20. But, it requires a bracket to even mount the ESC in the first place. Making the stack even taller and requiring more room to fit the ESC in the first place. Got it.
The shit that we let manufacturers get away with in our hobby is ridiculous.
Its not just our hobby it's more or less our lives. This is why right to repair is important. The same think can happen with more or less any other product with a microporcessor and firmware.
Of just think what happens if their corporate network gets cracked by a bad actor and they lose acccess to their source - e.g. ransom ware, cyberwarfare.
Think your car, your voting machine, your government's guided missile (defense contractors charge a premium for IP so gov's don't always buy it.) . your microwave oven.
Yes and ... on the other hand this is a small business deciding to fold and lose their income to prevent their product from being used to hurt people. It is just as likely that a small business would fail for other reasons. It's not "just manufacturers getting away with it" as much as us, the consumer, being unaware of accepting the risks. Remember CDs with offline driver installers?
@@SeanPoulter your correct. I edited my comment but I was actually referring more towards other parts of the hobby.The blheli-32 guy is actually loosing from what I understand to be a significant amount of money for what most of us believe to be a noble cause regardless he can do what he wants.
Uh...you mean going out of business? Sometimes people go out of business. I don't know why you have this attitude of "letting" them do anything...creating the stuff we use is extremely difficult and time consuming. If anything, you owe all the people who do that. You've been given the gift of technology you could never create on your own. And yet somehow you feel entitled in that position. So strange to me.
In what way would you not "let" them get away with this exactly? Force them to keep working? Not allow them to change jobs? Slave labor? Or maybe you feel it should've all been open source? Well, no one was stopping anyone...make an open source version. You can't blame these folks for supplying you with a product.
@@geometerfpv2804 I was speaking of hardware NEVER free open source firmware which I contribute to every month with the acception of INAV I don't fly beta flight and still contribute. Hardware companies. Speedybee, skyzone, matek, holybro, fat shark, betafpv probably more. All have had issues in the past know amongst the community, have revised the product to actually work but don't replace parts they know are bad. Either you've been in the hobby for a week or you've been really lucky. I give two shits what a person does or where they work with your slave labor bullshit remark. 32 wants to close shop fine especially for the reasons they chose.
They're probably going to come back, rebranded, it's just an office reshuffle.
The biggest issue now is the stock in shops or manufacturers that are on older firmware! Will you buy blheli32 today?
Yea this is an issue. I would hope new esc came with 32.10. But it’s not always the case.
Just reflash with AM32 or is there any problem?
@@GK-dd5ci Can you run us through the refresh process?
@@GK-dd5ci Not a simple procedure for everyone and if the pads are inside the esc (tekko32 f4 65a with 32.8) is even worse.
Most of the time they come with older firmware....it'll be hard ti find one with 32.10 on it already
i just want to know how to reflash all my old Bl_Heli escs to AM32
if they work just leave em for now
Can someone please explain what were the major advantages of BL32 over bluejay? Because to me it seems like Bluejay just does more with less and it’s open source.
Bluejay is for 8 bit esc on older hardware. BLHeli 32 and AM32 for the new 32 bit arm hardware. They are not interchangeable
@@MadRC I get that. But is there like functional difference between the two? I've seen Chris Rosser's testing and there doesn't appear to be a definitive BL32 superiority.
For typical FPV quads it doesn’t buy you much. For larger quads and fixed-wing there are some extra features that can be useful.
This is a sad story 😢
Open source is always the right answer. Closed source will always stab you in the back.
I've never seen a side by side comparison that proves BL32 flies better than Bluejay.
Bluejay and BLHeli_32 run on different hardware.
Yes I know, but no one has ever proved that a BL32 ESC flies better than a Bluejay ESC. Even though BL32 ESCs are more expensive. I'd like to see someone do laptimes on a BL32 based ESC quad and then a Bluejay based ESC quad to see which is fastest.
@@ChinaExpatsRC irrelevant to the topic. This is about 32 bit escs
@@putrid.p ofc its relevant. People who put their faith into 32 bit hardware and the closed nature of BL32 have now been burned. What benifits did they get for their trouble over people who stuck with 8 bit hardware and open source? Cause no one has ever proven 32 bit flies better. Seems like the smart choice was sticking with 8 bit ESC.
@@ChinaExpatsRC The advantage of 32bit is purely they can natively support dshot with hardware dma. What this means is that when running very fast dshot at high rates the mcu wont get overloaded.
But like you honestly I think my spedix 32bit escs performed no better than my dys xs30 in actual real usage.
Am i correct in thinking that anything that runs BLHeli_32 can run AM32?
Technically yes but there is complications as BLHeli locks the bootloader. It’s doable though.
@@MadRC Would the process be anything like setting fuses in an Arduino? Or something else, entirely? I think there are a lot of us, who are excited for the notion of learning the process.
And they had the bawls to blame it on Muh Russia - two plus years into the war. 😐
No, they blamed it on restrictions from the Norwegian government.
Is better stay at bluejay
What a headache
Madness!
I’m so glad I never updated my fc’s lolol let it all hash out for now I guess
Update please
Their proprietary blheli_32 can rot in hell. They did not contribute to the opensource project, they commercialized it for profit with minimal work, and if you were effected than let it be a lesson to you about this hobby!
What are you talking about... Telemetry, 32 bit, bidirectional dshot support. There's a reason every high end ESC has blheli32. If it was so easy to do, the manufacturers would have thrown a few bucks to make their own instead of licensing
@@chezfpv9139 whoosh, right over your head I see. Keep running blheli_32 and tell me how that works out for you. Point is stick to open source or your equipment is subject to end of life due to some bozo company's situation. 😉
Yeah this is confirmation bias...they made lots of industry first improvements. Closed source often does (DJI anyone?...let me guess, you hate them too...we had been stuck with analog for a decade plus, and no one was working on anything new...).
@@geometerfpv2804 DJI is a company in it to make money, if you want a stable, reliable commercial drone go with DJI, I did. When I tinker in the drone making hobby I want open source because its hobby friendly. Think if IBM kept computer architecture proprietary, we would not be having this conversation right now.
You must be a very active person in the open source community, creating tons of code for free with deep understanding of the community ... or just a moaning westerner that assumes software, and others people time is for free?
How does Github allow this?
class action?
how many of you will now switch and start using linux instead of microsoft windows? Somewhere around 0.0001% I suppose because you don't learn. And then you'll cry again when something similar happens with your computers
Since Brian released PID Toolbox for Linux I haven’t booted W11. Next boot will probably have 3 hours of updates :p
The whole Ukraine thing is a copout... that's like gun companies not making guns because of misuse.....or phone companies not making phones because of drug dealeds😂😂
It certainly has me scratching my head. If every single, secret sauce digital camera, transceiver video-tech, shut their door tonight, and took every proprietary, motion sensor, and motor controller software provider with them, and they all took every untold secret, and went home, to have one great-big "Non-Disclosure Party" to never be heard from again... Well, cameras would continue to fly. That genie's out of the bottle.
Wow!! What a bunch of BS. at least I always updated my escs to 32.10 a while ago.
well that is annoying
Wow
Is this the same for Blheli_S or is that different I know a little but I'm no expert? Anyone have an opinion. Thanks
It is just for business sanktions. BLS is open source. They can not put sanctions on open source.
BLHeli_S is not affected, BLHeli32 is, as it's operated under a licensing situation. Requires servers do a "check" upon update, which are currently offline so NO updates are possible, but BLHeli_S is still able to be update and you can run firmware like BlueJay or JESC etc to still get RPM filtering and what not.
Can a blheli_32 esc be flashed over to blheli_S or to bluejay? (I have at least 4 4-in-1 blheli_32 escs I have not yet used!)
32 is 32bit. S and Bluejay are 16bit. Different chips.
@breakflight might be able to use am32 but who knows
Just put em something and fly em there will work fine
Will require at the moment to re-flash the bootloader after soldering wires from an ftdi adapter.
@@breakflight S and Bluejay are 8 bit. But yeah, still not compatible as you say.
I hope no one will hire Steffen Skaug after this. It's clear how he will behave.
3:20 I think their "solution" is probably "well if you're not happy with the lack of firmware updates then stop using our hardware"...
Sadly that seems so
I liked 32.9
I think they've been threatened...
Their overpriced trash gets even worse! LOL!
So... Basically, BLHELI rage quited in fact... 🙄
Thanks, Ian!
Stay safe there with your family! 🖖😊
Waiting for the lawsuits ! Guy should have just released it open source instead of screwing everyone who supported him
Fu*k they business models, we are pay for they license and now they just gone
Seems like they're givin' us, the tall finger. 😐 What good is advanced hardware when it leads to dependent broken coding/software?
It becomes fully useless.
Someone needs to crack it, it's not that difficult. Just don't try to produce anything with it, for revenue.
That's stealing intellectual material for profit. Cracking it and sharing the files is not a problem. The problem is reproducing it for-profit.
Sounds to me like they've sold a bunch of products that you cannot control; meaning modify and repair. I'm certain that wasn't part of their business plan.
My intuition is telling me that it's something regulatory[governmental] ; where they are attempting to stifle any type of growth [saturation]. We can already see that drones are used in warfare, and I believe that's a valid consideration in this particular instance.
My personal opinion is that sux and it's bullshit. They're copping out on their responsibility to thier consumers.
[Of course I know nothing of their business structure, practices or economic health. I'm making my own educated assumptions, just like all of you.
Appreciate it, Ian and thanks. @Mads Tech
Man, 1st this DJi ban bullshit and now this? Damn, the future of our beautiful hobby isn't looking good
On the bright side... every single person who lives for this hobby is a problem solver. And I'd wager that a majority of those problem solvers, are also a little smarter than the average bear.🤪 *even if we are a bunch of sh1t pilots*
Open source is definitely the answer to this 💩🤣
safety is the priority number 1 cause it can kill the hobby especially in bigger quads
And this one is well known , I mean the issue is well known and not something mysterious that has not happened.
Not acceptable. Sure, leave the business. But, never leave users without the option to upgrade to the latest firmware. This would be your last commitment, almost. Have you ever heard of post-market surveillance? Not that this legally applies to BlHeli but ......This is not the way to begin or end a withdrawal.
It is fascinating to hear the demands for a duty of care and responsibility to have a safe product, but also not want government over-regulation or to pay the prices for well engineered software or a certification process.
😢
is there at least 1 person which thinks of Putin shutting down the drone threat from ukraine with this move? its not a permanent solution, but having some time is signifikant in this case. we cant blame Steffen for shutting down his baby and business, we do not know at all what did lead to this. i think there is much more behind.... we just dont know. who would shut down such a good business? i would not at all
pilots should stop using the github issue tracker for ranting. the O.P. was good and a few comments were good, but now everyone adding their 2 cents going to make the devs annoyed. they will do what they are capable of as time permits. if they dont, then oh well.
I cant believe there's only like 3 or 4 videos on this shit show!!!
Trashy move by whoever these jerks are running this.
Why not bluejay as well though? Don't get me wrong, I've been running AM32 and it's always been absolutely fantastic. But I can say the same for bluejay. It supports all the important features for our quads. I understand theoretically AM32 has the 32 bit advantage but in practice, honestly, it's difficult to really pin down that advantage. Plus the bluejay ESCs tend to also be cheaper and they are a lot easier to flash. I think it's also a very good alternative. Especially now where it is much much simpler to just flash it.
AM32 and ESCape32 are the only 2 software's you can flash on a BL32 ESC. So if any future 32 bit ESC will be made it will be AM32 or ESCape32.
@@Quick-Flash I understand that you can't flash your current BL32 ESCs. I just meant that I think bluejay is also a very good option to use moving forward as an alternative. As in, as a consumer, when purchasing a new ESC :) It's also a good project to support imho
Leave everyone high and dry, blame Russia, call it a day. Yeah, I think I'll learn about those involved to avoid doing business with them in the future.
Cant we just run bluejay
Not on a 32 bit esc. Bluejay is for 8 bit
See?.. Keep supporting arrogant USA politics and scaring of them europeans.. 🤣
have many nib for future builds hmmm