Software opinions

Yes you can, but you need to make it manually (in file selector enter . and then open EMUB3 file)

Hey Jadzwin,

I have noticed that some cars I set up with V3 are running lean.

Under Fueling - General there is an option to select what fuel is in the car.

What should I select here to get the same result for injection as in V2, or does this not affect the injection PW?

For DSG Mode, can I get some Information what Number stands for P, N, D, R, S and manual?

thanks

setup your graph correct. max 5v etc. you will see the fine spikes again. had the same prob

I tryed it offline(ecu not connected). Did not work for me.
Correct if i am wrong please.
What i did:
1.Open V3 sw
2. open Ve table
3. Press “Open 3d table” button
4. Then i guess opens file selector window where on the right side is file type “Table files(*.emubt)” where you can not change or type nothing, on the left side is “File name”. I try to enter “.” hit enter nothing happens then i typed in manually project name with .emub3 on the end and it accept it but do not import nothing.

MAP Referenced.

If your fuel dose differs please send me both calibrations I will test.

DSG Mode:

AT_MODE_LIST_P 2
AT_MODE_LIST_R 3
AT_MODE_LIST_N 4
AT_MODE_LIST_D 5
AT_MODE_LIST_S 6
AT_MODE_LIST_M 7

1 Like

Save project as XML first.
Then you will be able to load tables directly form project (but only cell values are imported not axes).

Remember posting about rev match issues a while back. Looking back at some of the logs from weekend and seems to be working much better. However I can still feel and see another short blip of throttle after the initial rev matching has happened. I have shortened down the rev match duration down to 0.5s. This improved it slightly down from 0.7 seconds I used to run on V2. I wish I had tried 0.3 seconds to see what it did but at the moment I can’t see why closes then open the throttle again. Drive wire target source is always from rev matching during this duration


Doing some logging/tuning today and noticed a couple of things. I might be me, but:

  1. When Knock is active, I could feel it pulling timing, but it doesn’t show in the log. I shows as a Knock Ignition Correction, but the Ignition Angle doesn’t change and I can’t seem to find where it actually pulled the timing anywhere in the data streams.

  2. I can’t find a way to export a CSV file with accurate parameters. The log will export, but it doesn’t have my parameters that are active in the window like it did with V2.

  3. I see the “M” mark is now working. Thank you for this.

Are you using knock ignition cotrol per cylinder?

For csv export issue it will be fixed for next build.

Foe knock sensor:

could you plublish this log ?

1 Like

Attached is the log in question. Like i said, I can feel it when the ignition is pulled, but I can’t find it in the log.

This was not set on per cylinder at the time of this log, but I do plan to run it this way.

EMU Black Porsche V3 111624.emub3 (60.2 KB)

20241117_1528 Knock Active not sure.emublog3 (1.3 MB)

Is there training somewhere on how to use these functions?

In ur log there is no ignition retard by knock. Also in general the ignition angle is stable. I would say that what u feel is something else. Probably misfire related to other stuff.

Is there a description of what these options do? Is one, possibly, real time?

Did not work for me, and also this is not the best way if you need to double check for axles anyway you can copy data then too.
Could be nice if in the future you can make map import from project simple if it is possible of course. That will save a lot of time to tuners and will help to make new project fast. I used that function on other standalone ecus very useful.

I’ve checked your log and everything works as expected.

Knock count increases, knock ignition correction is applied and also the I. knock correction flag is on.

I can the knock show up in the Knock Ignition Correction, but it doesn’t show up in the overall Ignition Angle like it does in V2. I can work with this now that I know it’s true, but ideally, it would be reflected in the overall Ignition Angle.

Also, I haven’t tried this but I am assuming that a per cylinder retard will show up in the Knock Ignition Retard for the respect cylinder? In this case, cylinder 5.

Is there a way to change the Tune Display to add both Lambda 1 and Lambda 2?

It is made like that to be consistent.
If you select per cylinder trim it is an issue how to show it on ignition angle.

There is another option that, always the ign. angle log channel will be corrected by the angle of most retarded cylinder.

To have per cylinder knock correction you need to select proper value for Ignition control type.