If you experience communication issues with the device, please restart your computer. We have noticed that these problems are caused by the Windows USB driver. We are working on reproducing and resolving this issue.
Change log:
DBW TUNER: Autcalibration bug fixed, added new channel DBW cal. tool state to allow easier data analysis
TIMERS: Boost target correction is working now
CAN: FIAT 500 immo code resent if ignition turns on during delayed turn off, EMS fail status send when EMU status > Cranking
CAN: FIAT Grande Punto CAN Hand brake bug fixed, EMS fail status send when EMU status > Cranking
ACCENRICH: When the ACC enrich was low (less than 15%), the acceleration enrichment calculations were wrong (the enrichment was higher than it should)
GENERAL: When Load ECU desktop option in general option is unmarked, the configuration of the desktop will always be saved to the Default directory
GEARSHIFT: Upshift torque reduction table changed to 3D (gear vs MAP)
TC: Fixed bug with Indicator light
TREEVIEW: Bug fixed with the log group list
HELP: Ignition outputs help added
HELP: Timers help added
Yes everything is setup ok. Just spent 2 hours trying to eliminate this issue with 3.036 but it’s still just as bad. I will get the log and upload on here later.
please also publish your ve table and scope from idle. Bad engine response is often caused by wrong injectiors angle and lean spots in ve in area the ecu interpolate during fast throttle movement.
Also sometimes dbw characteristic adjustment helps a lot.
Asynvhronus enrichment works immediately and adds the fuel instantly for all cylinders.
And do not look at lambda but at engine response.
Are the effects of the changed Acceleration enrichment big?
Any more expiriences?
I sadly atm don’t have time to tune and having a closer look at this myselfe.
20240918_1827_40.emub3 (60.7 KB) 20240918_2251.emublog3 (4.8 MB)
This is the last log before we gave up. We had 2 hours of changing settings in the ACC but we couldn’t get a smooth transition on and off light load. Engine judders a lot.
Ignition angle is the final ignition angle. But it is a single value.
For the knock sensor there are 8 channels Knock ing reteard cyl X, that shows you additional per cylinder trims.
According Saab DBW it should work with 3.036. I will check.
Could you give me information in such situation there is a problem with the ACC enrichment ? Eg light acceleration , strong tip in, when you try accelerate after overrun, on low rpm, etc ?
Also could you please send a scope file ? I would like to see the injection sequence on the scope
The issue is from when engine is on overrun and I give it a small amount pedal it starts to enrich but then I get a judder from the engine for a split second and then it runs fine until I go into overrun again. It does this all the time even when just free revving the engine from idle.
I saw it on the log. After overrun there is no residual fuel in the manifold. You can try to increase enrichment during overrun exit as well as for low rpm do not cut all the fuel during overrun.
I did all of the above with no improvement, the exit fuel enrichment was at 30% and went all the way to 65% and all that I noticed was more popping out the exhaust. I then turned the overrun off and the issue is still there.
Also when I try to upload my log data from the EDL-1 it says 'Sorry, the file you are trying to upload is not authorized (authorized extensions: jpg, jpeg, png, gif, heic, heif, webp, avif, emub, dbc, adu, pmu, txt, pdf, doc, docx, csv, emublog3, emub3, emupro, emuprolog, emuproscp, zip, emubscp3).
I have the same engine as u and i could achieve very good results. Engine response is really good. Maybe try mine: AudiTT_AJQ_rev74_ACC.emub3 (64.4 KB)
I also use MAP based enrichment. I could get better results with less tuning effort. Probably some adjustments to 3.036 needed.
I just have a small issue since ever (not related to current SW).
At very low engine speed (1000rpm) in one out of 10 tries i get a jerking when going from 0 to 100% pedal:
20240919_2152_rev74_lowrpmACC.emublog3 (226.5 KB)
I actually can’t spot differences in the situation when it works and when not. Enrichment times are nearly identical.
ACC enrichment tuning helped to minimize it, but i can’t make it completly gone. Overrun isn’t a factor here since it comes from idle - I think this is probably related to something else than fueling. Anyone an idea?
This value range is much higher than usable. It is the range where launch control applies PIDs. What would be the reason to have the bigger range as the typical values are in hundreds not thousands ? What is your case?
Than I didnt understand it correctly. Thanks for the explanation.
How do I define when the LC start to retard timing? Based on the values in the tables for LC?
