Comment by zoobab
13 hours ago
We need to free up Bosch systems. They use lots of open source libs, but they close the whole chain (like spare batteries) so that you cannot plug external batteries from other suppliers.
13 hours ago
We need to free up Bosch systems. They use lots of open source libs, but they close the whole chain (like spare batteries) so that you cannot plug external batteries from other suppliers.
Having been on the flip side of this divide in the past, there really are a lot of potential safety and reliability problems when using random third party versions of components. While I'm sure there are strong financial incentives to constrain supply, there are also some other strong reasons as well.
Also it's very expensive to actually make an ecosystem compared to a close one. The best way to incentivize manufacturers to do it is by creating a competing product that is open and having that differentiating feature drive sales away. That's generally the approach that works best.
That's kinda been the experience I've found in the open source diabetes space; several manufacturers have floated making things harder to hack, and we've found that actually showing them how many people use the reverse engineered API and would definitely go to their competitor is a really useful way of disincentivising that sort of anti-consumer behaviour.
> there really are a lot of potential safety and reliability problems when using random third party versions of components.
What are you talking about?
If a seller sells you random junk that causes safety issue, they are liable of the damage like the OEM would if their product was bad.
Then, if the seller is in a jurisdiction where you can't hope to sue, then it's either your problem for picking this random seller on their website, or we should make it Amazon's problem to feature this kind of sellers in the first place. Surely the biggest retailer on the planet could afford vetting businesses selling on its platform to protect consumers' safety.
In any case, the fact that Bosch's ecosystem is closed offers no additional protection whatsoever, as shady sellers already sell counterfeit components (that may or may not work at all).
> What are you talking about?
> If a seller sells you random junk that causes safety issue, they are liable of the damage like the OEM would if their product was bad.
No, the GP comment is right. I’ve worked on products where a lot of users did mods and used third party accessories.
Customers don’t care who, how, or why their product broke. They want to make noise and try to get a warranty fix for it. Customers would try to mod their devices, break it in the process, and then spend weeks trying to drag us on social media until we relented and shipped them a new one for free.
They’re not going to be pursuing damages against the Aliexpress vendor who sold them a flawed battery pack, nor the Amazon seller called WOBALUBAFY that has already disappeared, nor the YouTuber who hastily showed them how to solder some things together.
They always try to hide the evidence and claim the product failed by itself because the big American company has the deep pockets and the ability to send them free stuff to avoid bad PR.
1 reply →
The closed system doesn’t (only) prevent counterfeit systems, it also prevents someone from maliciously releasing a mod that could make the motor accelerate instead of break at some random time.
It’d be negligent for anyone to release a product like this without locking down the FW.
Many years ago, we did exactly that: our product had FW update support and our biggest concern was a rogue hacker creating a package that would brick the product.
Safety is just an excuse for control, let's be real.
Also your "best way" doesn't always work - often there are monopolies or oligopolies (e.g. in smartphones).
Though I think for e-bikes that isn't the case, so yeah I would just say don't buy a Bosch ebike - there are plenty of better alternatives out there.
When it comes to ebike batteries I think the alarmism is actually valid considering how often we see explosive fireballs on trains and in apartment buildings coming from cheap no brand ebike batteries.
High capacity batteries are incredibly dangerous devices kept safe only by very careful engineering and manufacturing.
Pretty much anything hardware based is like this. Everything is 100% closed source and bolted down such that inspecting it is outright impossible without extensive reverse engineering.
I believe one of the feasibilities we have with electric locomotion is the standardization of components: electric motors, motor controllers, batteries and battery chargers. These being interchangeable will lead to lower costs through competition and more innovation.
It's disappointing that manufacturers are moving the other way to enable vendor lock-in. But only one manufacturer has to jump the fence and the others will be left behind.
I’m suspicious of this vision because for example, with battery packs, cells with compatible voltage and size have vastly different characteristics.
Those characteristics, like safe discharge rate, capacity, projected cycle count, are all things that manufactures exaggerate or get wrong.
I don’t think there’s any way that consumers can ever be informed enough to have an efficient market in products such as those
2 replies →
I definitely think AI is going to change this. Astra is shockingly good at reverse engineering. I was working with a proprietary software library and I just asked it how some (poorly documented) function worked and it just went off and disassembled it without me even prompting. I asked it if there was a way of disabling some error checks and it went and found some undocumented functions (not in the header), disassembled them and figured out how to use them for me.
I didn't actually even give it the ability to run this code and it could still reverse engineer everything.
I've been surprised how much Astra prefers to go off script to "find the answer" than Sol was unprompted.
I've been doing some PCB design lately, and I was working up the firmware with Codex and asked about how to handle a specific part of my SPI setup. The firmware and KiCad hardware are in different folders/repos so none of it was in-context, but Astra just decided to `find` the folder nearby, then read the KiCad net lists by directly invoking the KiCad CLI on the .kicad_sch/.kicad_pcb files it found. Topped it off by reading the Espressif code vendored in my PlatformIO install to make sure everything would work.
For now, but I think eventually the hardware companies will catch on and build everything much more locked down with signed firmwares, keys burned in to the chip, encrypted communications with accessories, etc.
2 replies →
I took a look into the batteries for the ebike systems, they have some sort of AES based pairing and the chips are read protected. You probably can dump the firmware from the update packages for the things. (maybe some hw exploitation stuff as well?) I did a thing where I put their battery controller on an after market battery with a divisor and it started and paired, but for some reason blew up afterwards.
I now realize it would be easier to write the whole thing wholesale, but.. uhh, it's no small feat, and I have a job soooo...
Bosch should open their shit, it might save them, because it seems the chinese with Avinox will eat their dinner in a couple of years. They seem to be pretty litigious, they went after a forum that documented initiatives to reverse (well, they also hosted pirated diagnostics sw but.. yeah)
Like Apple who used BSD but then closed the whole chain?
At https://infinite-battery.com (disclaimer: I'm a co-founder) our battery is compatible with Bosch systems