1.) Printed material I expect to pay for. Downloadable material is mostly free to distribute (hence so many free software packages and servers). I wouldn't mind paying $10 to download a shop manual to pay for the Internet server maintenance fee and such.I agree in general but would like to make a couple points.
Dan
- Software and documentation is not free. Every owner needs an operations manual but not every owner needs a service manual. I would expect to pay a reasonable fee for service manuals and software distribution. Additional fees for periodic updates and maintenance.
- OEMs compete and ECUs are key to performance and competitive edge. Thats not going to get standardized anymore than you would standardize an engine.
- Interfaces are what gets standardized and right now outside of OBD2 there are no "open source" diagnostic or maintenance standards. Thats another competitive area but there are enough generic functions (e.g. coding an injector or battery) that some baseline standard COULD be developed. I dont see any industry interest in that and I dont see that happening without OEM support. From a historical perspective OBD2 was a CARB regulatory mandate that they were forced to adopt.
Related: A whole business can be run off Free and Open Source Software (FOSS) for $0 (web server, applications, code authoring software, word processing, e-mail, spreadsheets, database, etc) so free or reasonably priced access to ECUs and auto-specific documentation is at least "reasonably possible."
2.) ECUs are very reliable computers, some do more, some do less. There's no reason making 4 tiers of units per application wouldn't fit most applications. Coding how those work can be proprietary but the diagnostic & service interface could be standardized.
Related: Computers to run FOSS, and the R/C electronics to fly planes/helis/etc. is not free, but very affordably priced. People buy the hardware from reliable manufacturers, the software and documentation is free.
3.) I've seen basic race application ECUs, but nothing approaching the major OEM complexity. There is a project or two (speeduino, rusEFI) that's open-source, so there's hope.
Related: Arduino and Raspberry Pi platforms are open-source platforms with many add-on controllers from third-parties. The third-party documentation and interface is "free" as in covered by the price of buying the hardware module. I've read up on modules in advance, the full docs are readily available without purchase as an incentive to see if the module is a good fit, and if so how to use it once you buy it.
----
Of course, there has to be a will to make it happen if it's going to happen. In the R/C (hobby) industry it happened, which is impressive given the small number of people involved in R/C compared to the general population, but it is a hobby. Coding and hardware for a highly regulated industry is certainly different, which I think is the core of what you're saying, and that I completely agree with.