rusEfi presentation

Post Reply
User avatar
AndreyB
Site Admin
Posts: 12794
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

rusEfi presentation

Post by AndreyB »

Subj attached
Attachments
rusEFI presentation 2019 Q4.pptx
(2.8 MiB) Downloaded 257 times
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions

Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
User avatar
Dron_Gus
contributor
contributor
Posts: 327
Joined: Wed Nov 13, 2013 1:11 pm
Location: S-Pb
Github Username: dron0gus

Re: rusEfi presentation

Post by Dron_Gus »

Few words about tests/test coverage?
Simon@FutureProof
contributor
contributor
Posts: 381
Joined: Tue Jul 24, 2018 8:55 pm
Github Username: Orchardperformance
Slack: Orchardperformance

Re: rusEfi presentation

Post by Simon@FutureProof »

Tests?

What would you be looking for? I can always add something.

It was really intended to be a quick intro presentation.
Now keeping MRE and Proteus in stock in the UK - https://www.FutureProofPerformance.com
User avatar
sepp2gl
Posts: 32
Joined: Sat Jan 01, 2022 3:47 pm
Location: Germany
Github Username: sepp2gl

Re: rusEfi presentation

Post by sepp2gl »

@AndreyB:
I think, some statements from "About rusEFI" should be part of this presentation.
Especially the scoping
"...a GPL open-source engine control unit for gasoline port-injected internal combustion engines. This project involves embedded hardware, software, and engines. ...
...This project is NOT for emissions regulated or safety regulated applications. This project is for race cars, snow blowers, fixed engine applications, and science experiments."

From my perspective the last statement is extremely important.
By this presentation new visitors of the rusEFI-Forum can get to know, what your project is about ...and what is NOT covered.

In addition I propose to add two further main-chapters to the forum:
1. Engines
This chapter should analyse and discuss features of all engines, that are of special interest for the community.
It should result in an engine-specific datasheet.
among others: Compression-Ratio, Displacement, MPFI/GDI, ETC, EGR, Turbocharger System (if any), VVT, Miller/Atkinson-Cycle, Cylinder Deactivation,...

2. Engine Management System
This should focus on three sub-chapters "Sensors", "Actuators" and "Engine functionalities" (above specific algos and software) and should discuss competing technologies and concepts. E.g. Knock-Detection based on vibration sensor or ion-sensing or in-cylinder pressure sensors with pros and cons.

These two chapters are currently discussed in the Chapters "Software" and "Hardware", where they IMHO do not belong.
As a result a lot of conceptual decision-making is hidden in "Software/Hardware" and thus not very transparent.

T2US, sepp2gl
Everything keeps being better ... ;)
Post Reply