1.8 KiB

Raw Blame History

We are interested to create a fundamentally better ECU DIY experience.

Desired User Outcomes

We are looking to reduce manual data processing and to expand self-tuning capabilities. We are looking to increase the success rate for ECU amateurs.

Software usability
mass storage device
drivers
firmware update
tuning software
bench test/diagnostics
Community toolset - remote tuning, tune and log community involvement
Hardware breakage diagnostics: misfire detection
Hardware breakage diagnostics: broken wire detection for many wires
Long term fuel table autotune
Long term timing table tune
WUE Warm-Up Enrichment auto tune
Limp mode
Hardware self-detection: Injector lag?
Hardware self-detection: Trigger shape detection / diagnostics
“As good as OEM in terms of XXX” or “As good as OEM in any term”

Mileage
Cold start
Cranking duration
Trigger Decoding Quality

SDLC efforts

Data workflow tools: human feedback and objective data from real users (REO)
HW in the loop: rusEFI hardware quality assurance
HW in the loop: rusEFI CI
HW in the loop: Competitor analysis toolset - both OEM and aftermarket
Universal code vs custom vehicle code

Implementation Strategy

Gather more data about rusEFI operation. We are looking to gather more data about engine operation and process that data programmatically.

We are looking to gather:

VSS as rotation sensor or GPS
Direct accelerometer measurement maybe 3D
Crankshaft acceleration data based on trigger input, on the scale of individual engine cycle
Acoustic knock data
Cylinder Pressure Pike data via Ion sense, maybe knock data via ion sense

Engineering toolset development

Faster data acquisition (at least full time composite logger/engine sniffer)