Q: Why start an open-source project about automotive electronics?

A: Automakers have toyed with the idea of open-source electronics initiatives in the past, but these efforts have for the most part only been partial or narrow in focus, and success seems tough to quantify. The Initiative seeks to change this by nurturing the development of a complete electrical system for, well, almost anything that has an engine.

Previous efforts at this specific idea have also been manufacturer-only, with only a few known non-industry efforts efforts known to exist and those focused on building a few specific systems for a few specific vehicle makes and models. The Initiative seeks to alter this by bringing a full-scale effort to bear that involves both manufacturers and non-industry talent working toward building a standardized and parts-interchangeable whole-car electrical system.

 

Q: What makes OSAEI any different from the other open-source auto projects out there?

A: Our goal is to develop a common platform to manage anything with an internal-combustion engine - this includes not just gasoline powered autos and light trucks, but also encompasses diesel engine vehicles, watercraft, and even non-vehicle devices powered by engines such as lawnmowers. The only engine-powered devices we're excluding from development efforts are aircraft, and this is simply a function of the increased risk to health and safety attendant with aircraft systems development and with it the corresponding increase in regulations, requirements, and legal liabilities.

Part of our goal is also to eventually provide a project for every major device in a typical vehicle's electrical system, from simpler devices like relays to primary powertrain controllers.

 

Q: What about those other open-source auto projects? What if they want to join OSAEI?

A: We welcome other open-source projects that wish to merge with the Initiative, and extend the same offers to participants in those projects. We do, however, require that submissions not be encumbered by any agreements with other parties and that the submitter own all rights to their submissions, so if participants have signed any sort of contractual agreements with other projects that would impact commercial licensing and/or free-for-noncommercial-use redistribution we cannot accept their submissions. As always, we believe strongly in giving credit where it's due so merged projects will include references to their originators.

That having been said, if you are part of or operate an existing open-source auto electronics project and would like to bring your work over to or merge your entire project into the Initiative, please contact OSAEI.

 

Q: Can an open-source auto electrical system be "safe?"

A: Our insistence upon sound development practices, careful component selection, and rigorous testing - and compliance with existing laws and standards - means that any project developed to completion will by definition be comparable to superior in safety and quality to anything currently in production that performs the same functions. Plus, safety can be designed in to a level not seen before by incorporating things like graceful failure, automatic fallbacks, self-state monitoring, and manual overrides - for example, an engine controller could be designed to recognize a brake pedal depression as a signal to override any acceleration signal no matter what sends it.

 

Q: Isn't this illegal? (See also, "the government will never allow it.")

A: Part of the design requirements are that a project comply with all relevant laws and standards, which by definition will satisfy legalities regarding using an open-source electrical system in a vehicle. The biggest legal concern in the United States is compliance with the EPA's various mandates regarding auto emissions - engine controllers in particular will need to meet or exceed emissions standards and this is already a design requirement.

If anything, the government is likely to encourage efforts like the Initiative, in that what we seek to accomplish will have the collateral effect of making vehicles more efficient. To further this aim we welcome representation from relevant government agencies as part of the Initiative's steering committees.

 

Q: Won't automakers try to stop this? (See also, "the automakers will never allow it.")

A: We not only seek to produce designs that automakers would be inclined to embrace, we encourage automakers (and other manufacturers) to actively participate in the development process through the Initiative's steering committees. Any manufacturer of a product that can utilize an Initiative project can designate a representative to represent their interests in relevant steering committees, and through these committees help create projects that would provide real benefits for that manufacturer's customers . Manufacturers gain access to technologies that are built and bulletproofed without the R&D costs, customers get improved products, and Initiative participants earn both recognition for their contributions and royalties from commercial sales in accordance with the Initiative's commercial licensing terms.

 

Q: What incentives would an automaker have to participate, especially given that OSAEI would basically make electrical parts interchangeable across product lines from different manufacturers?

A: While the circuitry would be standardized, more than one level of hardware implementation will exist for complex projects and the software can and will vary. - manufacturers can tailor their implementations of Initiative projects to suit their needs, provided that the base-model projects provide minimal functionality. For example, one vehicle may include cruise control while another may not, simply by using a different hardware implementation level that excludes the hardware and firmware needed to support that feature. While a full-hardware engine controller should be usable with any engine it supports once it has received proper program code, manufacturers will be able to provide different features and special capabilities for their products simply by using customized program code in their controllers. By standardizing a set of hardware with enough power to do anything they're likely to want or need, manufacturers can develop new and compelling features for their products without having to spend time reengineering the hardware.

 

Q: What operating systems will the Initiative's project computers run?

A: For most projects that involve microprocessors and microcontrollers, the answer is none - one of the hallmarks of reliability is simplicity, and for crucial systems in particular using an OS instead of straight assembly code would entail adding layers of complexity, and with them extra points of failure, that are more critical to avoid than the benefits and features of an OS would provide. Simpler really is better, especially if the project in question could damage something or lead to injury or death if it malfunctions, such as an airbag controller or antilock braking system controller.

Basically, the only systems that an OS would be called for in a typical automobile would be used for navigation, information display, and entertainment.Everything else would be better suited to a OS-less software methodology.

Of course, none of this is ironclad...