hi, please check dbw wizard tune as it still dont work with the saab DBW
20240921_1215 dbw.emublog3 (303.1 KB)
manually i got it to work with settings made wiht pro8 wizard. and manual tweaks but during blip it overshoots and undershoots still not good enough
Can you please check knock ignition reduction.
for what i can tell its doing nothing on the semi sequential cars. wasted spark cars.
20240921_1612 knock.emublog3 (1.9 MB)
its says knock. i can see knock. but no where i can see its pulling ignition.
there should be a difference between end ign angle and ign angle from table like in the old verson of softwre. and in the table of ign reduction cyl 1 2 3 4 there should be something.
cant see anything.
settings for actions are from 2000 till 7000 above 30percent TPS in this file (rather have map sensor there but ok)
20240921_1359_42.emub3 (62.6 KB)
knock ignition correction shows response for knock and is working on your log i can see that
not seeing it. please show me ?
in V2 its easy to see. the ignition angle changed vs ign angle from table.
as there is 1 ignition angle channel, there is 8 knock per cylinder trim channels that shows trim for each cylinder when knock occurs.
Please take a look for knock sensor help there is description for all knock related channels
for what i can see its calculationg needed reduction angle. but not implementing it.
should be visual at least in Cyl 2 and Cyl 3 as its wasted spark and ecu can not know what cyl is actual ignition
still not convinced. please convince me. that its working on wasted spark.
remember i had to send 6 emails before my “stall” problems whas acknowledged that there was a bug in the software.
Till monday I’m not able to take a look on logs.
I do it on Monday
i sometimes have the same readings. knock on 3 cylinders but only 1 is showing knock in the graph.
can i hang on a question. what knock window duration and knock window start do you guys use? i am running around 15deg ignition at 2,2bar of boost at the moment. maybe this needs for calculation.
Hi @Jadzwin_ECUMASTER do you have any updates on my issue?
Thanks
I will check it today.
I think the problem with asyn acc enrich is that the tps rate (map rate) can be different depending the time you press the pedal within the integrator window.
If the whole change starts of the begining of for example 20ms window the value will be much higher than if it starts in the middle of the window.
The async injection is performed immediately.
For the acc enrin the value will be increased after next integration, but not for asyn enrichment.
I need to disccuss it with the team, to find neat solution.
For the transients on low rpm there is one trick that helps a lot.
You can build DBW characteristic table like that:
Then on low RPM, the transient will be much lower, but still it will not influence the maximum RPM increase. In general it makes a engine response much better.
I’ve tested everything and it works correctly as it was described in help.
I will add some more explanation that it isnt visible in ignition angle channel.
From help:
Knock control strategy ignition timing correction, since it works per cylinder, is not visible on the Ignition angle log channel! You should observe the knock strategy ignition correction channels or/and the I.KS correction channel.
And further:
Knock ign retard cyl #1-#8 - when the option Per cylinder is selected for Knock sensor action / Ignition control type, these channels show the current ignition correction for each specific cylinder.
Knock ign correction - when the option All cylinders is selected for Knock sensor action / Ignition control type, this channel shows the current ignition correction for all cylinders.
Thx a lot…will try that for my very low rpm problem.
I was always thinking about limiting the TPS speed at very low rpm.
For this it would be great to have this…
…as a 2D MAP with rpm as axis. Maybe 3-4 coulumns are enough.
But i never really tried it. Low values here for the whole rpm range make the vehicle more or less undrivable.
Will defenitly try this on my current project with EMUpro.
Any ideas? The cars been sat for over a week now waiting to try and sort this issue.
Did u try my settings?..how is ur engine behaving with them?
Try to limit the the throttle opening for the low rpm.
Also increase the async acc enrich.
In enxt version here will be improvemnt for dbw that the throttle speed can be cobtrolled as a funcrion of rpm (also separate control for opening and closing).
Also the async enrichment will be more repetable.
Another tip for now is to lower tps rate time base even to 10ms.
Hello Iam here to point to the bug I found in v3.036.
When I open the saved log from the run (measured via PC), there is an issue with timestamp view (visible on attached picture).
Also its impossible to work after click to “Zoom full out” button. Then program is stuck with no responce , when something starts to happen - its incredably slow.
When I transfered my maps from v2 to v3 i notticed increasment of VE map.
Iam attaching the comparation from EXCEL:
I saw that also in log when i shift+s for thicker lines(they look great) and zoom out client freeze and i get “not responding” message. Pc cpu was low.
The VE differs after loading v2 tables or after tuning ?
