QUOTE (pugfan @ Feb 10 2011, 09:32)

I'll make a judgement and say you're not a software engineer.
Why would basic logging necessarily be trivial? Sure, an OEM can bring a lot of man-power to bear but their ECU software architecture may be completely unsuited for global logging and could require a complete re-write, somewhat unlikely I'd agree but I've seen it before on software projects larger than what goes into an engine ECU. Their ECU hardware may already be stretched in processing capacity or memory with no immediate plans to address this. Their software process may be quite immature and unable to cope with a change that impacts on a broad level and production logging is one of those aspects that is all pervasive throughout code.
(No. Not a software engineer.)
- I say trivial because the % increase in ECU functionality required is miniscule.
- All OEM ECU's already incorporate logging at various levels.
- Many (including Toyota) are already logging at the level that would be required to provide a basic data snapshot of the period prior to engine stop (or some other defined event such as airbag deployment).
- ECU development falls to a specialised division within the company (Denso, Delco etc) or often an outside supplier (Bosch, Siemens, Delphi etc). Corporations like Bosch have traditionally driven HW/FW/SW development and innovation. I guarantee for example, that basic "flight recorder" logging would be available as an upgrade, at very short notice to OEMs using Bosch engine management.
- At the OEM level, amortisation over a large number of vehicles means that the cost of pure development (no hardware or tooling) have little impact on unit costing.