when it turns on
wasted spark ignition after sequezial
why is there no vw r32 4 teeth tick in the secondary trigger?
Can u plz fix the bug, that when u increase rpm by anything else than pedal press (e.g. downshift) and cross max idle rpm, idle stays active and fuelcut doesn’t get active?
I was crossing the alps last week and this bug was very annoying in longer downhill sessions where u want to have effective engine braking and actually don’t press the pedal for a longer time.
Are you sure your settings in Armed state airflow are correct ?
If the TPS opening there is too high the engine RPM will do not drop.
Do you have log with such behaviour ? I would like to see the strategies states.
There could be also some conflicts between active strategies.
@Jadzwin_ECUMASTER If I understand correctly I have experienced something similar to @derUltraTT (if his armed state airflow is set correctly?)
Idle control will kick in while coasting at 0% PPS in gear and rpm drops below the idle ramp down rpm. Since it is in gear and the rpm doesn’t drop as quickly as the idle strategy would like, it retards the timing to minimum to try bring the rpm down and will stay that way until you touch the PPS. I wonder if the idle strategy could only kick in when the ECU detects the car is no longer in a calculated gear (ie. the engine spins freely when in neutral or the clutch is pressed.), or would this be too slow to repsond? Or is there another way around this?
Additionally I’ve found that when using cruise control below the idle ramp down rpm it will kick into idle control and do the same thing, retarding the timing since the PPS is at 0% - even though the TPS is doing it’s thing to maintain the target speed.
PS - Any chance we could have a deadband option added back into the VVT settings? I had it set at 1deg in V2 to prevent it dragging down the VVT DC when the cam is at it’s resting position (my cam sensor can randomly sit at 1deg when it is really at 0deg)
- We will try to find the solution for this.
- There is a bug in PID control of airflow that it cannot lower the airflow (it can only increase) so when ignition timing is retarding by idle controller, the airflow will not be decreased by airflow PID. The fix will be present in next build
- Cruise control - I will check and fix if the idle starts to be active when CC is active
- No problem with the VVTI PID deadband
One more idea. Did you try the VSS target increase ?So when the vehicle is moving the target is higher so there is no need to retard timing
I have noticed the idle PID not reducing airflow! Will be handy to have that working 
I have my VSS target increase set to 200rpm, but I don’t think that makes a difference since the idle target is irrelevant when coasting in gear.
I found a random old log of the idle kicking in while coasting. You can see I am coasting in 3rd gear, and as the rpm drops below the ramp down idle threshold (in this case 1700rpm), idle control takes over in and tries to manage the rpm - even though I am coasting in gear, and it wont have any effect. Thus is drags the ignition PID down to minimum to try lower the rpm quicker.
That’s why I suggested maybe only having the idle strategy activate when the vehicle is not in a specified gear? I recall having this in V2 as well - but it’s not the end of the world! Just a little annoying.
I am not sure what exact issues derUltraTT is having after re-reading, it sounds different to this?
My issue is this:
I am coasting with around 2800rpm and acc pedal not pressed; overrun is active and idle not active.
→ press clutch → engine drops in idle → release clutch → rpm increases again to 2800rpm but engine stays in idle (no overrun is active) until i press pedal again
AudiTT_AJQ_rev55.emub3 (61.6 KB)
20240708_0738_rev55_idleleaveproblem.emublog3 (160.0 KB)
Expected bahaviour would be, that after releasing clutch and crossing idle max threshold, idle gets inactive and overrun gets active.
I will try to get a log tomorrow and upload, but I wanted to bring this up first to see if there was in input first to help pin point the issue. When I start the car it doesn’t seem to be getting enough air flow to start. I have the crank IAC duty set to 85%. If I give it throttle it will start, but once started, IAC continues to appear to do nothing. I have it set for IAC to take over .1S after start. I can rev it a few times and the IAC starts working like it should, sometimes it does not. The times that is does not, I can enable the manual override DC and it idles perfect. I then turn off the override and then 99% of the time it will start using the target DC from the table. This seems to have been more of an issue from 3.28 onwards.
I’m not sure whether this is a bug or if I have done something wrong with the WBO circuit calibration, however, I have completed the procedure by unplugging the O2 sensor from the ECU, and then checking in the logbook the stored value of 4070.
In the logs however, “WBO Circuit Calibration” = NO.
Have I done something incorrectly?
Could we at for the DSG Upshift Fuel Cut?
Would be nice instead of retard ignition because this can raise up the boost
Here are the logs for my erratic IAC behavior. My wideband cal is also showing NO aswell.
beta map edit 2.emub3 (57.3 KB)
20240709_0659.emublog3 (2.3 MB)
From yesterday there have been many new issues reported. Please be patient I will take care of each post, but some of them are challenging and I need time to analyze the data and propose solutions.
It is ok.
The log channel Wbo circuit calibration is not Wbo circuit calibrated.
It is only Yes during the WBO calibration process.
Value 4070 sounds very reasonable for me.
There is an option for spark cut for upshifts.
From our experience, any cut makes the shift slower and less smooth.
The ignition retard works the best. The boost should be stable as the boost control strategy should control it.
The solution seems to be simple:
There will be another parameter that will block idle over defined VSS (eg. 5-7 km/h to allow creeping). When you press the clutch pedal, then the idle control will be allowed to work. I think it solves the problem.
That is a solution!
Only issue I see is it would mean entering neutral and releasing the clutch at any speed above that value would result in the car stalling (since idle wouldn’t keep it alive)
Maybe, you could trial a VSS value above which it that doesn’t block idle, but disables the idle ramp down feature.
Then if it detects the clutch is pressed it will behave normally (as you said) but if the clutch is released while above that speed into neutral, the car can idle as normal, although without the ramp down.
This should fix it, as it is unlikely that the car will be coasting in gear below the idle target rpm! Where it is currently entering idle control above the target idle rpm when the ramp down rpm is crossed.
What do you think?
I didnt consider Neutral during driving.
The idea with the ramp down feature disabled over defined speed seems to be ok.
I have different idea. When the VSS is over defined speed the idle works in open loop only. It is simple and I cannot find the case it will work wrong