5 ms·
I like the basic idea, but unless Porsche moves away from manufacturer lock-in for all of the software on board of the vehicles, including the inability to insp
by jacquesm 3y ago
I like the basic idea, but unless Porsche moves away from manufacturer lock-in for all of the software on board of the vehicles, including the inability to inspect and/or repair the underlying hardware not much of use will come of efforts like this. It's like so many other brands that claim to love Open Source Software for marketing purposes but that continue to refuse to open up the key components of the software that they ship.
Porsche could make some real headlines by opening up their ECU code and the code that drives their infotainment systems, would be nice if it was accompanied by schematics and the tools required to read-out and re-program the hardware.
Fat chance that will ever happen because 'safety', 'environment' and a bunch of other fig-leaf excuses.
- bri3d 3y agoThe biggest excuse is much more reasonable (albeit annoying, the same reason why most board support firmware isn't open source): ECUs are built using code generation from models (ASCET, LabView/Simulink, etc.) on top of 10 layers of proprietary middleware and compilers, using components supplied by hundreds of consulting firms, so an open-source effort would have to be a paradigm shift in the industry from the ground up. It's not something Porsche could decide to do on their own.
- jacquesm 3y agoWell, they could dedicate a team to it if they were serious about it and work with open source advocates to make it all work. I'd rather have a tarball with hard to parse code and weird tooling than nothing at all. But - as I said - I have no illusions about this and see it as a marketing effort.
- AlotOfReading 3y agoIn my experience it's fairly common even for the manufacturer to not have full access to the code, let alone permission to open source it. I don't think it makes it merely a "marketing effort" if they avoid that.
- jacquesm 3y agoYes, I'm aware of that. Which is why my assumption that this would be a red herring was born out. As long as Freescale and Bosch are in control I don't see any of this changing.
- thot_experiment 3y agoHonestly just documenting the APIs the different components use to talk to one another would be incredibly helpful. There are so many things that could be done in the pursuit of openness that absolutely won't be.
- archi42 3y agoI did some work on a toolchain used in automotive (and other industries) to proof^W prove certain software properties related to safety. This is already a massive effort, expensive to build & maintain - but after all a small cog in the whole machine. (Using Rust over subset-of-C would deprecate maybe half of that work; at most I'd guess). The hypothetical team would take a decade or two to replicate just that cog. Yes, having the whole machinery available as FOSS would be awesome and I'd like to live & work in a world in which this is the norm (Hello, Star Trek?). But all this requires very talented people, many of whom studied and racked up student debt, want something to eat and a place to stay. We first need another paradigm shift to make this kind niche open work sustainable. Oh, and if you ever find yourself in a car with critical components not checked with that kind of toolchain: I strongly recommended getting out of there asap ;-) For all the excellent people building that software, there will always be some who'd be better writing mobile apps instead (or anything else that cannot kill people). (btw: You asked me about the setpoints of the 12k 3P Deye inverters a while ago: Seems to work nice for me with my basic "just the inverter + PV + battery" setup. Though some people report trouble when using AC coupling with another inverter; in that case the Deye seems to swing more around the setpoint).
- jacquesm 3y agoThe main thing I think manufacturers would try to avoid is to be embarrassed by the kind of shenanigans that helped VW to pass emissions inspections when in fact they shouldn't have. And that's proof enough to me that manufacturers don't give a rats ass about safety or the environment if it means more money for them. I realize how complex those toolchains are (and how many parties would have to sign off on a release) but what amazes me more is that we are willing to trust these manufacturers on their say-so. Because chances are their interests and our interests are not aligned, as the diesel scandal has clearly proven. And I would not be at all surprised if there were more such scandals but we just haven't uncovered them. Given what the Asahilinux people and some other very talented individuals have done in the FOSS movement, combined with the fact that half the world is powered by open source including for many mission critical and safety critical applications I'm pretty sure we could handle vehicles as well. Nice to see your setup works well!
- posguy 3y agoVolkswagen (Porsche's parent company) certainly has the scale to make this happen. Seems like its entirely a corporate culture issue, same as what plagues Volkswagen's EVs and newer cars with terrible infotainment systems.
- FirmwareBurner 3y ago>Volkswagen (Porsche's parent company) certainly has the scale to make this happen. Yeah, but VW and Porsche are into selling cars not OSS so their priorities are aligned with that. Think of it from the bean-counter's perspective, which run these companies: why would they invest resources into sharing your SW as OSS if that's not gonna sell more cars?
- AaronM 3y agoI think you can make that same argument for many large companies that contribute to OSS though.
- FirmwareBurner 3y agoContributing to OSS is one thing. Open sourcing your existing closed source internal SW is another and is hugely risky legally as that could have many faults and bugs that could get them sued if discovered. Toyota had the unintended acceleration lawsuit during which an external audit discovered several bugs and deficiencies with their SW, testing, and dev process. Knowing this, why would any car manufacturer air their dirty laundry in public for the sake of OSS? Their lawyers would definitely advise them to never OSS anything internal out of the kindness of their hearts as that could backfire spectacularly.
- Kim_Bruning 3y agoHiding safety flaws? That doesn't sound like a very healthy safety culture. This sounds like a good reason to have a little government regulation to align incentives with safety interests.
- thistoowontpass 3y agoCurious, who are the main consulting firms active here?
- dongping 3y agoBertrandt, IAV, EDAG, to name a few (link in German): https://de.wikipedia.org/wiki/Entwicklungsdienstleister#Top_10_(nach_L%C3%BCnendonk) https://de.wikipedia.org/wiki/Entwicklungsdienstleister#Top_...
- ryeights 3y agoPIWIS for the people! I got briefly excited that Porsche was going to make this happen.
- PaulWaldman 3y ago>It's like so many other brands that claim to love Open Source Software for marketing purposes but that continue to refuse to open up the key components of the software that they ship. Nobody is buying a car based on the manufacturer's love of open source software above other factors. "I really liked the size of the X3, but went with a Macan because Porsche loves open source software." Said no one ever.
- layer8 3y agoRMS might. ;) https://www.reddit.com/r/linuxmemes/comments/jx6fz1/stallmans_car/ https://www.reddit.com/r/linuxmemes/comments/jx6fz1/stallman...
- svorakang 3y agoNeither safety now environment is something you can easily wave at like that. Also, you're completely missing security concerns and legislative. I have worked in the automotive embedded software industry since 2009 and I have got caught in the safety track in my career. It's a strange place to be, because the basics are extremely simple, yet it takes hundreds if not thousands of man-years to get a modern vehicle reasonable safe just in terms of the electrical system (this includes the software in automotive terms). There are so many ways to make a mistake that could easily result in an accident. Even the window regulators have non-trivial implementation concerns for anti-pinch. Allowing a random hacker to override this is a terrible idea. Now imagine what kind of mess you could do with brakes and steering... Designing a vehicle to be hackable will very likely lead to an unsafe vehicle. I believe what I just wrote applies similarly for security too. Furthermore releasing software for the market, extensive testing is carried out by an independent body to ensure that legislation is followed. Even conceivably simple things such as lighting or headbeam alignment is a pretty large problem domain by itself. Also, so is just the communication standards for diagnostics. I would say that large changes would be required to transform this industry. In some, protected domains there is use of open source, such as Qt/Linux for HMI, but opening the HMI to be fully hackable is unlikely to happen. There is quite some liability to make the HMI non-distracting.
- frenchie4111 3y agoI think their point / the general FOSS argument is that those 1000 of man-years would be turned into 10000 man-years if these things were open sourced. A similar security concern could be waived at things like openssl, but it seems pretty inarguable that openssl is a net-positive for security.
- svorakang 3y agoI'm all for open access to the code for the sake of safety. On the other hand, I'm completely against hobbyists accidently bypassing a safety mechanism. Open access, but secure access to software download could make sense, at least for commodity parts. When it comes to features with competitive advantage, though, I don't see that OEMs or its suppliers have anything to gain.
- deleted 3y ago[deleted]