Yes and for diesels there are options too, but fewer and as far as I'm aware none are open source or open hardware. If I'm going to bet on the longevity and maintainability of a computer control system all 3 of these things need to be open software and open hardware or highly standardized in a very stable way:
1. Controllers. Absolutely must be open software and hardware, no compromises.
2. Actuators. If not open hardware, they must be documented sufficiently to facilitate adapting a suitable replacement in the future.
3. Sensors. Same constraints as actuators.
Unfortunately even mega/microsquirt systems don't quite get us there yet.
[edit] One example that informs my hardline stance here is reading ECU codes. On the Toyota's ECU there's an open interface for reading fault codes documented in the factory shop manual. You jump a couple pins on a connector in the engine compartment with a test light and read the number of flashes. The Benz, by contrast, is completely proprietary and "secret". It does have an OBD2 port, but almost none of the modules are accessible. To read and clear codes you need to use a round 38pin connector and software that knows how to speak their protocols. There are aftermarket systems which are somewhat unreliable but function almost "good enough". The most reliable option for an end user is to buy a counterfeit Star Diagnostics System multiplexer and a sketchy pirated version of Mercedes-Benz's diagnostics software and run it on an air gapped laptop. Or you can purchase the official Star Diagnostics System for like $20k.
So even routine maintenance is borderline impossible, let alone replacing components. Without the proprietary software, variant coding is impossible for example.
Comments
Yes and for diesels there are options too, but fewer and as far as I'm aware none are open source or open hardware. If I'm going to bet on the longevity and maintainability of a computer control system all 3 of these things need to be open software and open hardware or highly standardized in a very stable way:
1. Controllers. Absolutely must be open software and hardware, no compromises.
2. Actuators. If not open hardware, they must be documented sufficiently to facilitate adapting a suitable replacement in the future.
3. Sensors. Same constraints as actuators.
Unfortunately even mega/microsquirt systems don't quite get us there yet.
[edit] One example that informs my hardline stance here is reading ECU codes. On the Toyota's ECU there's an open interface for reading fault codes documented in the factory shop manual. You jump a couple pins on a connector in the engine compartment with a test light and read the number of flashes. The Benz, by contrast, is completely proprietary and "secret". It does have an OBD2 port, but almost none of the modules are accessible. To read and clear codes you need to use a round 38pin connector and software that knows how to speak their protocols. There are aftermarket systems which are somewhat unreliable but function almost "good enough". The most reliable option for an end user is to buy a counterfeit Star Diagnostics System multiplexer and a sketchy pirated version of Mercedes-Benz's diagnostics software and run it on an air gapped laptop. Or you can purchase the official Star Diagnostics System for like $20k.
So even routine maintenance is borderline impossible, let alone replacing components. Without the proprietary software, variant coding is impossible for example.