Yes thats true as the air flow PID controls based on ignition target error.
It would be very unusual to use airflow PID control without ignition PID control,
as ignition gives faster and finer RPM control.
Okay interessting…didnt expect the SW work like that. But that is smart and actually an effective way to prevent ignition pid run and stay in its limits. This was i think a Problem in V2. Because of such smart details i like ur products.
U are right in general…i just wanted to deactivate ignition pid for air pid base tuning and finding idle airflow basemap.
Do you think it would be possible to add the option to change the idle strategy to a button? Seems like a big advantage for using ignition cut idle to reduce EGT after the pull. Or to be able to add things like this to the programming function as well and therefore create this strategy based on for example CLT, EGT , VSS etc…
The good:
-Ability to calibrate O2 is nice. I always had a small offset near lambda 1 previously.
-Has the internal MAP sensor calibration been improved?
-Transition off idle is improved
-Generally the PID tuning seems to be easier to get a good result with, and I’m glad there’s actually units displayed now
-I think the strategy for idle air control has improved and is less prone to swinging the valve/throttle excessively
Bad:
-haven’t had any dramas yet asides from the issue I caused
It is already there. It is called Cycling idle. Just assign button or function and it will override the base idle.
1 Like
To topic EMU CAN stream.
I use SW 3.025 and the EMU CAN stream seems not to be the same as with V2.
- Lambda target value is somehow corrupted
- TPS and DBW pos is showing the same. From my point of view old TPS should now be PPS (i think most people used DBW, so TPS is PPS in V2); since dbw pos is gone now it should be TPS
2 Likes
This update is amazing, especially the seperate Y Axis for the VVTI tables, would this be possible with the Fuel and Ignition tables as well? For example on my K24, Low cam would be up to 6500rpm and high cam would be from 3500 to 8000 so I could have a bit more resolution between the two tables.
2 Likes
How this can be activated ?
You cant. This table is created automatically as you change anything with the fuel model and fuel pressure.
Will be fixed for next build of v3 firmware
Another bug?
In dsg engine torque table you can add 635 as maximum torque. Typing more will add only 635
Yes. It is a bug.
For DQ250 it doesn’t matter as you cannot send more torque than 620Nm over CAN.
Will be fixed for the next firmware version.
But dq500 can do more 
Thx for your fast response
yes for sure As I wrote will be fixed in next build
Thanks for the info. We take care about it
I do not see the knock sensor value (V) on channel list
Can it be restored?
Left double-click on the graph log channel enter to its configuration, but when i change the channel in this window, the new settings are not applied
Sorry, ecu.errorFlags shows oil pressure sensor error because I had it disconnected 
In V2 this error did not exists
There are 8 channels knock voltage peak cyl, for knock voltage of each cylinder. It is a raw value from the knock sensor.