rusefi.com

Hello,
I finished building my rusefi and I installed the 4 EGT modules.
And it works, it's beautiful. It's accurate and fast.

I don't know if this is a subject already mentioned.
I'm mounting my rusefi ecu on a car.
I tried to do tests on logs, and I noticed that some information on the gauges are not available when making logs with Tunerstudio.
For example, the 4 thermocouples, and other stuff are not visible in the log.
Would there be another solution?

Having the knock module is very very useful, but a development idea that would be needed and present on ecu OEMs is to have the knock level voltages for each cylinder.
With the 4 thermocouples and the visualization of knock levels could highlight the option "Cylinder Extra Tuming" but also see if cylinders are defective (sparkplug, injector, sealing, or other).
What do you think?

Just added EGT info into TS logs - https://github.com/rusefi/rusefi/commit/f2aa684aec4f8d7c8bfacfc5ae3e594915799238
Please let me know what other gauges are not getting into the log and I will add

Knock was never tested. In order to test knock we need someone to volunteer and have their engine knocking, only once we prove this works it would make sense to develop features based on knock.

russian wrote: ↑

Sun May 27, 2018 3:23 pm

Just added EGT info into TS logs - https://github.com/rusefi/rusefi/commit/f2aa684aec4f8d7c8bfacfc5ae3e594915799238
Please let me know what other gauges are not getting into the log and I will add

Thank you for these quick changes.
I'll test tomorrow if it works and I'll tell you.
I will also try to list if it lacks other gauges.

For the knock, I want to do some tests I have something to do, but my knock module (Frankenso board) doesn't work at the moment. I made the settings well, but nothing. I hit the knock sensor with a screwdriver but the knock voltage level doesn't move
I don't understand why yet?

let's move into some knock-related topic or start a new one?

What does hipinfo command say in rusefi console?

let's spin off a new topic!
so what do we expect to see in that hipinfo command?
basically, we need some sort of explainer, containing thorough and complete information about the knock phenomenon itself, about setting up knock detection part of rusefi (both, software- and hardware-wise).

1. On a four-cylinder four-stroke enine, knock events occur four times over a camshaft revolution, right?
2. Knock window in rusefi is a sector of a camshaft revolution (relative to initial CPS offset) , where we can expect to see knock in the first cylinder (btw, if knocking occurs just at some certain part of the certain stroke, then what is the need in this setting?)
3. During the knock window, the ADC circuit in rusefi board samples the values from the HIP chip and calculates the average value (can't understand that integration-related graphs and slopes). If that value is higher than those in the predefined table, it triggers a knocking event (which can be observed in tunerstudio).
This is why just knocking with a hammer on the sensor won't necesarily be seen in console, you need to knock at the write moment.
4. So far, Rusefi doesn't have anything in terms of knocking avoidance, does it? No special ignition logic, nothing - just capturing the knock events.
5. predefining the table of baseline 'noise' level requires quite some effort. probably we need some recommendations, where to start from.
6. setting gain - same question

russian wrote: ↑

Sun May 27, 2018 3:23 pm

Just added EGT info into TS logs - https://github.com/rusefi/rusefi/commit/f2aa684aec4f8d7c8bfacfc5ae3e594915799238
Please let me know what other gauges are not getting into the log and I will add

As you ask me
I also noticed that it's also missing
Ignition advance
IAT correction
Knock count
Knock level

Lyonz wrote: ↑

Wed May 30, 2018 6:10 pm

I also noticed that it's also missing
Ignition advance
IAT correction
Knock count
Knock level

Just added knock count https://github.com/rusefi/rusefi/commit/8881bef3cdcf9eb950b2bf1bc25464908b695871

Looks like the other ones should be there already?

entry = ignitionAdvance, @@GAUGE_NAME_TIMING_ADVANCE@@, float, "%.2f"
entry = knockLevel, @@GAUGE_NAME_KNOCK_LEVEL@@, float, "%.2f"
entry = iatCorrection, @@GAUGE_NAME_FUEL_IAT_CORR@@, float, "%.3f"

Is it possible to add the injector phase angle to logging? I didn’t see it in there.

junk3r wrote: ↑

Tue Jun 12, 2018 12:22 am

Is it possible to add the injector phase angle to logging? I didn’t see it in there.

Sure. I've made some first steps - can you finish the part about rusefi.input file changes? Or I can finish that a bit later https://github.com/rusefi/rusefi/commit/9158dc22f2f0db2435a9dbbc52fc73f982f865b4

i did a pull request. I didn't add it to the gauges as it's probably not needed there.

rusefi.ini generated & commited