BLHeli_32 Server Down For Maintenance - Safety Critical Firmware #743
Comments
|
They must provide at least a way for all to update to the latest firmware. |
|
time to get things solved before the former members and employees of the business will be tracked cause no one wants to see them in the hobby again killing products they have developed and then left behind. |
|
It's now time to give access to the community or they need to understand that someone will eventually file a lawsuit and force their hand. I had a feeling the servers would shut down. Dirty low down and underhanded. They took our money and now deny access to the product we paid for. All this needs is one greedy lawyer and a class action. |
|
they need to give support , they dont have a contract with the manufacturers ? |
|
@sskaug can you please at least update the BLHeliSuite32xm software to skip checking for server connection and allow browsing local HEX files to flash? |
|
A full hex file dump for all previous versions need to be public. Ive spent thousands over the years and my business is dependant on the ability to manipulate firmware for clients. I have found very few hex files and honestly they are all outdated such as 32.6/32.7 !! please release a hex dump for the previous versions. |
|
TBH BL-Heli 32 has been feature stagnant and bug-filled for a long time. The community needs to go back to open source and learn the lesson about paid license-ware garbage. Even if we can get BL-Heli to comply and give us hex files or boot loaders, the answer is still in AM32. I just went and joined the Alka Motors Patreon. $5 a month is nothing. Lets get some smart guys working on this. If I could code this stuff I'd be all over it. I say we pause development of BeF, put those smart guys on AM32 for a while until we get back to a place where we can safely update our ESC again. BeF is pretty darn mature at this point. I'd happily wait a year for 4.6 if it means we can get our ESC back and get past this betrayal. Lets keep FPV open source and free. And a footnote to this thought, this would be a good time for the big retailers like GetFPV, RDQ,Pyro and others to step up and put some serious money behind AM32. They all are sitting on inventory right now that can't be updated and it's going to start to hurt their bottom line. |
|
Just my 2 cents, I will start returning the few ESC's I have ordered for my new builds. I really don't care about BlHeli32 anymore, I just hope they open their bootloader so its possible to flash other software easily. |
|
please release all the previous versions of firmware. |
|
Please BLHeli_32 Devs let us be able to change firmwares! We already paid for the licenses! This is so wrong! What is happening in the world with war has nothing to do with you! Please let us change FW that we paid for! Thank you! |
|
Publish the bootloader. Allow us to proceed with AM32. You owe it to the community that depended on you... |
|
|
|
Plus 1 to allow existing escs to be updated to later firmware versions mainly with aim of installing firmware where bugs/issues have been resolved. |
|
I don't know what political pressure Blheli 32 Company is under, but I think they reacted too quickly. What would have been to make a DJI-like system, when you buy an esc, you activate it like an air unit. They could have monitored the activations and checked that they were in the right hands. |
|
My updated beta flight will now not work because the firmware I had on my quads ESC is too old… I’m now also stuck with older beta flight firmware …. Not to mention the spooling up problem mentioned by the OP please let us just update our firmware for a few days and get our setups sorted |
|
that sucks. i payed for it what they doing????? |
|
[mindrev] dont beg them.. they owe us.... |
|
I have to ask, with known documented incidents of people having serious injury, why didn’t BLHeli do more to get notifications out of this patch to begin with? I don't recall a single email from any vendor I've ever purchased a BNF or ESC with BHeli over the years sending a heads up that this was fixed. And yes, I do have multiple ESCs on 32.9... WHERE was any effort to get the word out about this ~6 months ago? You gave it a one-liner in the release notes, that's it. So now that BLHeli has ceased operations, many are now learning that 32.9 and below have this safety issue. A motor can spool up to 100% on plug-in, and slice your hand open to the point of needing surgery AND we are stuck to either continue with that risk or throw what we paid for in the trash. 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, or the conditions for it to be most likely to occur) that’s still an unnecessary risk just because BLHeli are choosing to do the wrong thing. Post the hex binaries today, and allow us to update, at bare minimum. -- John C. |
|
This is not acceptable, hope this issue will be resolved!!! |
|
Make the firmware open source please we Will maintain what you Will not be able to |
|
|
this is really a bottomless impudence. This company should be taken to court with a class action suit. I'm lost for words... how brazen can they be. This behavior won't solve a single problem. The war will then just take place with blheli-s or something else. but blheli-as is now also accepting civilian casualties because of their behavior. I hope the company founders go bankrupt and/or get sued. |
|
Please provide support...... thank you |
|
I ordered an esc on wednesday, it was delivered monday. In that time, everything shut down and I can no longer get updates. If you had provided any kind of alert or warning I would simply have not bought a BLHeli32 product. Are you going to refund the money spent on licenses that can't be used? How comically naive this whole thing is. |
|
I have ordered 3 stacks, they probably contain the older firmware, how can I upgrade to the latest version now? Are you kids or something ? |
|
We are very sorry for this current server operation interruption, we are working very hard to get the required clarifications to put it back in operation. |
Thanks, that's a relief that you are still here and that there's hope for the update server to come back. Also - it would have been a good idea to post this somewhere if that was the case, all of the panicked responses with pitchforks would have been avoided. |
@sskaug Thanks for hopping on the thread. Happy that there is some hope the update servers will return, however this doesn't solve the problem. What is the current thinking around unlocking the bootloader / releasing firmware for customers who have licenses? Fine you don't want to sell more licenses or continue FW development, that's your choice. Nothing the community can do there, but giving us the freedom to update/ change FW without being tied to your licensing server is the short term solution we need while we develop AM32. Even if the licensing servers return there's no guarantee they will stay up. We could be right back here any time. |
|
I am a victim of 32.9. The defect of 32.9 caused my index finger to lose its original function！ |
Thank you. I think it's owed to the community that supported this project was so long. The last thing I want to see is people getting hurt because of a bug. Can't just be left behind as a community. Every single person in here basically supported this project no matter how you look at it the least you can do is show us the respect deserve. Honestly I think you was just a rash and quick decision without actually thinking of the consequences behind it. It is what it is hopefully this server goes back up and everybody can actually do what they need to do. |
|
How dare you post such a thoughtful, well reasoned, helpful, and polite reply?!!! This GitHub issue is for vitriol, ridiculous demands and accusations, and conspiratorial tinfoil hat ramblings only!!! Take a few moments to think before you respond next time! |
|
How to say you’re an idiot without saying you’re an idiot. I’ve looked at
the various blheli suites and they all highly depend on info from the
server. There are also numerous interesting b64 strings that do not decode
to plain text that are most likely public keys being used for signature
verification. But I just glanced at it with Ghidra and IDA….
It’s easy to bypass the first check, but the rest seem problematic and
requiring a private key.
…On Thu, Jul 25, 2024 at 1:35 PM Paul ***@***.***> wrote:
Blheli suite send data over uart to the esc, the protocol looks clear do
not know is "key" is needed for unlock bootloader, also do not know if
"validate" is mandatatory to send the firmware to the esc, so while there
are not solid proofs about the "imposibilitie" of flashing tescodes is all
bullshit
—
Reply to this email directly, view it on GitHub
<#743 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AALTXFK6VM32Y5IHEZFEVTDZOEZMPAVCNFSM6AAAAABIYKZAIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJRGA2DOOBQGU>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
There we go! This guy gets it! That's how you do that correctly! |
@sskaug so? |
So... Not hard enough apparently! |
|
Opening this thread every few days not even for BLHeli_32 updates anymore, just for the quality replies |
|
@VitroidFPV i reported the last guy and he’s gone now 😂 |
|
I think there are people who should calm things down I'm not sure who's done what or why but some of the things I've read I hate to say I am saddened to be part of it. Isn't the fpv community meant to be about helping like minded people? Things suck for all involved we can hope for it to get better but let's not make things worse |
|
Can people please stop being such fing bellends. Threats, begging and toys of of the pram helps no one. No one likes how this has played out however the hard cold truth is blheli owe you me or anyone else nothing. Blheli did not sell their products directly to consumers. Their software was provided by licences to esc manufacturers directly as you the customer was never entitled to anything from blheli them selves. The business has closed, stoped trading, they are no more. It’s a non business. It’s polly. Their software was closed source and remains so today and as such they not required to publish anything. You existing products remain fully functional as they did before and there are alternatives on the market you can choose. No one has been left ripped off or with anything that won’t work. |
|
Sorry but I disagree with your comment. |
Dam right |
Assumptions. You bought into a closed, proprietary system. Nobody guaranteed you support nor long-term updates. Ultimately you bought a product with a firmware at a specific version. Stopping software updates does not change anything to the fact that you still have the product with the specific firmware. Your ESC does not suddenly stop working. If you did not upgrade, you would still have what you initially bought. Any update should be seen as a bonus. I agree that the situation could have been handled better, but there is a lot of entitlement going on here. How is it that you don't complain to the actual manufacturers who sold you the hardware without a potential migration path to a different firmware?
Right. One "bad actor" is now representative for a whole country. |
|
…………Ultimately you bought a product with a firmware at a specific version. Stopping software updates does not change anything to the fact that you still have the product with the specific firmware. Your ESC does not suddenly stop working. If you did not upgrade, you would still have what you initially bought. Any update should be seen as a bonus.
This is not right : last year I had the opportunity to buy several BLHeli32 ESC at a good price and I didn’t care about the software version because I knew that it was anyway possible to update them at any time. When I received them I didn’t check software version because I had no time for this. But now I understand that it will never be possible to update and for instance there is no sport telemetry on the ESC I received , so these ESC are now unusable for me.
That is why I am not at all happy of this situation. There are still many BLHeli32 ESC on the market, but software version is never mentioned meaning you don’t know what you will get, it is a big mess…
I only needed one information a few weeks (days) before the shutdown.
De : Chris L. ***@***.***
Envoyé : dimanche 11 août 2024 19:25
À : bitdump/BLHeli
Cc : sybu0; Comment
Objet : Re: [bitdump/BLHeli] BLHeli_32 Server Down For Maintenance - Safety Critical Firmware (Issue #743)
... having in mind that these products would have appropriate and long-term follow up
Assumptions. You bought into a closed, proprietary system. Nobody guaranteed you support nor long-term updates.
Ultimately you bought a product with a firmware at a specific version. Stopping software updates does not change anything to the fact that you still have the product with the specific firmware. Your ESC does not suddenly stop working. If you did not upgrade, you would still have what you initially bought. Any update should be seen as a bonus.
I agree that the situation could have been handled better, but there is a lot of entitlement going on here. How is it that you don't complain to the actual manufacturers who sold you the hardware without a potential migration path to a different firmware?
... and will remember that Norway companies are not better than others and are able to let people down as any company from banana republic
Right. One "bad actor" is now representative for a whole country.
—
Reply to this email directly, view it on GitHub <#743 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM3PSTUFYRT2G7M76OSN65TZQ6M45AVCNFSM6AAAAABIYKZAIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBSHAZTCMBTGE> .
You are receiving this because you commented.Description : https://github.com/notifications/beacon/AM3PSTUVA7TBIZ7XKU6VPLTZQ6M45A5CNFSM6AAAAABIYKZAIOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUICE6LO.gifMessage ID: ***@***.***>
|
That's what I am saying: you assumed something. Your assumption was - obviously - wrong. The ESC is still as usable as it was the moment you bought it. Nothing changed. If you can't use it the way it is, you have multiple options:
I would cut my losses and stop crying over spilled milk. |
|
I will echo @stylesuxx. You should accept the situation right now and move forwards. Flashing AM32 is not that hard, and if a target for your ESC does not exist, Alka will help you to get it working. Or sell it, or use it as is. Posting on this issue is not going to get you anywhere. |
|
Well, when an assumption is right every day during several years, it is not an assumption, it’s a fact, and when you have a minimum respect for people, you make sure that the shutdown of your activity will make as little damage as possible.
De : Chris L. ***@***.***
Envoyé : lundi 12 août 2024 18:34
À : bitdump/BLHeli
Cc : sybu0; Comment
Objet : Re: [bitdump/BLHeli] BLHeli_32 Server Down For Maintenance - Safety Critical Firmware (Issue #743)
... and I didn’t care about the software version because I knew that it was anyway possible to update them at any time.
That's what I am saying: you assumed something. Your assumption was - obviously - wrong.
The ESC is still as usable as it was the moment you bought it. Nothing changed.
If you can't use it the way it is, you have multiple options:
1. See if you can flash AM32
2. Sell/Give it to someone who can use it as is - plenty people won't care if it has sPort telemetry or not
3. Sit it out and hope that by some miracle the devs will provide a migration path
I would cut my losses and stop crying over spilled milk.
—
Reply to this email directly, view it on GitHub <#743 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AM3PSTWNPFA6IPDTOH2Q343ZRDPVVAVCNFSM6AAAAABIYKZAIOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOBUGQ2TSNRSGU> .
You are receiving this because you commented.Description : https://github.com/notifications/beacon/AM3PSTXAJK3K5DTFJ5MC4HDZRDPVVA5CNFSM6AAAAABIYKZAIOWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUIFILGS.gifMessage ID: ***@***.***>
|
I was just asking for a status update since it's been two months since they last replied, but it seems like they don't even give a shit anymore. ¯_(ツ)_/¯ Nothing to see here. 👀 |
|
As amusing as this thread is.. it shows just how childish and self absorbed some members of this hobby are.. sad and a bit embarrassing actually as 99% of the users in this hobby are legally adults 🤦♂️ |
Oi! I resemble that remark! 🤣 But, at the end of the day, I 100% agree with This is simply another justification for my preference of open source software over closed source/proprietary... even if the original devs close up shop... someone can pick it up and carry on. So I will be looking to AM32 for any of my future needs in that space, in addition to Bluejay. That's it... I'm outta here... thanks for all the good (and bad!) times BLHeli_32! |
Not just suck it up. Learn from it. Closed source should never be considered part of any open source project. If an integral part of an open source project is closed source, for whatever reason ("it just works so well", "the dev has promised to keep it going indefinitely", "it would be unnecessary work to develop it again as OSS"...), then there's something wrong with the project and an open source alternative for the closed source component should be a priority. I'm not hating against closed source, but it should never be considered part of any OSS. |
Lols NO open source project makes ANY kind of promises.. that is total nonsense…. There are a LOT of misnomers about what an open source project is/isn’t and what can/can’t do… fact is no one reads the license agreements or actually understands them |
|
It’s also fair to consider the evolution of the situation here. If I recall correctly BLHeli was open for a very long time, and then the decision was made to close it and sell licenses. The community didn’t object because the process was transparent to the end user and the manufacturers paid the BLH devs and no one “felt” the tax. Basically the cancer of greed took over. Now I may be mistaken about how genuinely “open-source” it was early on. I’m fuzzy on this but I want to say it went closed shortly after going 32 bit. I recall a post by sskaug saying he had invested a lot of his time into the project and he felt like he deserved to be compensated for his efforts. I also agree we need to learn from this. This problem of open/closed source isn't going away. Small, tightly knit groups of developers are always positioned to do something like this and when large amounts of effort are left unrewarded, greed is left opportunity. The time for anger has long since past. Now is a time for action. Expletive filled rants get us no where and just annoy good folk. Donate, code or test. If you can't do any of those simple asks then please, respectfully stfu and wait. |
AFAIK ever since BLHeli_32 started development, it was always closed source. But BLHeli_S was open source from the start and still is to this day, but it has since been surpassed by better alternative firmwares |
Like I said, I'm a little fuzzy. Plain old BLHeli predated BLHeli_S or BLHeli_32, and that's the one I seem to recall being open. |
Where did I write that any open source project makes any kind of promise? The main point of open source is that ANYONE can participate in development. And if the main dev chooses to shut everything down (exactly what happened with BLHeli32), then again ANYBODY can fork the project and keep it alive. A lot of misnomers about what an open source project is, indeed. The fact that apparently many people don't understand the implications of this disaster is exactly what got us into this predicament in the first place. |
|
This is unacceptable, I just bought a new ECS and it turns out that it's on the unstable version. I am left with no recourse. This is especially frustrating because I didn't hear about all this stuff happening, but I was still able to buy the ECS with no warning whatsoever. |
return it. |
Can you send me the 32.7? :D So i can use Bi-Directional DShot... |
Finally some one with half a brain in this conversation.. your issue is the company who’s esc you brought. Not the developer who licensed his software to that company… |
|
Alors finalement il n y a pas de solution, su je comprends bien, ont la tous dans le LUC |
and others
Hi, first of all we are shocked and sad to see BLHeli stop trading and stop development on BLHeli_32.
There are customers who have purchased ESCs already with older firmware flashed from the factory with known potentially critical bugs that could cause harm and injury to themselves and others that are now no longer able to update via BLheli Suit as the servers are now offline.
We understand there will be no new updates however will you be providing users ongoing access to the last update V31.10 for BLHeli32 for all ESCs supported ?
Further more as you will no longer be providing updates there may be yet unknown bugs in BLHeli_32 32.10 that you will be no longer addressing.
As such will you be providing a bootloader unlock for users to allow them to install alternative software on their hardware.
I am sure you can appreciate the inherent risks around multirotors and the importance of safety in all aspects and being able to update or replace firmware is not only a basic user requirement but also will be required by many regulators around the globe where uas are used for commercial and industrial use.
We would appreciate some clarity on the future for current BLHeli_32 users who have supported the project and business.
Regards
Mads Tech.
The text was updated successfully, but these errors were encountered: