rusEfi presentation
- AndreyB
- Site Admin
- Posts: 14334
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
rusEfi presentation
Subj attached
- Attachments
-
- rusEFI presentation 2019 Q4.pptx
- (2.8 MiB) Downloaded 364 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
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
- Dron_Gus
- contributor
- Posts: 456
- Joined: Wed Nov 13, 2013 1:11 pm
- Location: S-Pb
- Github Username: dron0gus
Re: rusEfi presentation
Few words about tests/test coverage?
-
- contributor
- Posts: 413
- Joined: Tue Jul 24, 2018 8:55 pm
- Github Username: Orchardperformance
- Slack: Orchardperformance
Re: rusEfi presentation
Tests?
What would you be looking for? I can always add something.
It was really intended to be a quick intro presentation.
What would you be looking for? I can always add something.
It was really intended to be a quick intro presentation.
Now keeping MRE in stock in the UK - https://www.FutureProofPerformance.com
Re: rusEfi presentation
@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
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 ...