I experience the same thing, my ethanol percentage undershoots by around 10% or so. If we could have the ability to customize the HZ to ethanol output that would be fantastic
So I upgraded to 3.037 and swapped the throttle body for my spare. They are both identical, clean and known working on this set up. The PID debug is set to DBW.
Again cold start, two dips this time, albeit not as much of a drop as other times (some times is can go nearly down to 700rpm when target 1000rpm+).
As @derUltraTT mentioned regarding the deadband, it does appear to happen every time the TPS and target fall outside this set value. I have not touched that value since I started on this engine, maybe I need to increase it slightly ? However, relative small throttle changes on this engine have a large impact, as its quite large diameter (82mm) for the engine size (2.7L).
@kimbaku I did not set 4000hz in there, maybe it is the default value? No idea if its too high, my throttle is Bosch 0280750474. Throttle operation is great otherwise, throughout all engine use. @Jadzwin_ECUMASTER does the DBW calibration routine have any bearing on the frequency, or does this need to be set by the user first?
20241009_1752_10.emublog3 (2.3 MB)
987_09102024.emub3 (64.6 KB)
I would increase the deadband to 0,3 and watch the behaviour of the system. Do u also have this issue with engine warm?
It’s hard to say, it may have done in the past, but because this car is circuit use only I rarely have it sat on idle after starting once it is up to temperature. I only notice it as I run it to initially warm it up. In the log I shut it off and start it again (approx 50C CLT), but no dips occour that time.
In reality its not a huge problem, it was more so if there was an underlying issue (or configuration problem etc). Thought it may be more of an issue as we also had it happen on numerous occasions on another car with a different engine and different throttle body (also on V3). That could also be deadband related, so will check.
I will increase mine when I get chance and test it
I can see something strange in your DBW calibration:
- The limp position voltage is below TPS min voltage. Thats is very strange, as the new DBW Tuner do not allow such settings.
- Is your throttle regular one ? (with the limp position in between and movement down and up)?
- In PID below limp position the friction factor is 0%. This friction factor is responsible for additional force required to move the throttle.
However the first question is the most important.
Throttle body is of normal type, yes. I initially used the calibration tool (probably back in early <3.02x), and have not changed any of those values since, they are as they were upon calibration.
Does the tool change the limp position voltage and friction factor, or are they user defined values?
TPS and limp position is set by the cal too.
The friction factor is not, and I’ve just realised that by default for PID below pos the friction factor is 0%.
So please run the Cal tool again (3.037) and manually set the friction factor for PID below to 15%.
The friction factor is also set up by the DBW cal tool. I’ve just check
No problem, I will run the tool again in the next few days and see what settings change 
I will add non custom characteristic table for FF sensor.
2 Likes
Calibration worked fine, and values now seem correct.
1. Calibrating throttle position sensor Main signal and motor direction
TPS voltages: default 0.71 V, max 0.49 V, min 4.69 V
Motor direction inverted!
Max open throttle voltage 4.59 V
Closed throttle voltage 0.53 V
Limp mode voltage 0.71V
2. Calibrating DC ref and friction
DC for 10% (1.08V) = 29.5%
DC for 90% (4.20V) = 36.0%
DC for 85% (4.00V) = 9.0%
DC for -30% (0.65V) = -25.0%
DC for -80% (0.55V) = -28.5%
DC for -70% (0.57V) = -2.5%
3. PID Tuning
Final Tu = 88 ms, Ampl = 21.91
kP= 3.49, kI= 53.03, kD= 0.057
Calibration time 58.3 s
FINISHED!
However something has changed (assume TPS) as I’ve had to knock around 3-4% out of my active airflow table to get the same result and stop the airflow PID running with lots of correction. RPM drop did not happen this time
1 Like
as your previous tps ranges were strange ( the limp voltage), now the position to opening % changed.
Have some very slight idle fluctuations and can’t tell if this is from a problem with DBW or not. I see DBW delta error kinda spiking/jumping around during idle. Yet TPS and DBW target are very stable. What causes DBW delta error exactly? Log of idle attached
dbw-delta-error.emublog3 (66.4 KB)
Your throttle is very stable, the delta erro is different between current and previous error of the throttle, but in the log it is not scaled properly.
However your idle issue is connected to the ignition pid (much too aggressive) and your lambda (often higher than 1.0)
1 Like
DSG:
Can we get the up/down shift table back?
Really useful when looking for the perfect shift RPM.
Maybe you can also add a feature where you can select up or down separately.
Also it would be nice to get in the sensor pressure configuration the pressurecurve for the VW Aircondition Pressure Sensor. It is a really cheap sensor and I want to put some in the car.
Kind regards
XSD
@Jadzwin_ECUMASTER
Can u say something to priority of dbw target source?
Pedel vs. CC vs. CAN control…what is the logic which wins when different sources rqst at the same time?
And is there a DBW speed limitation during CC? I think i can see a limitation to 50%/s but i i am actually not sure atm cause i play alot around with the limitations atm and see a lot of strange stuff regarding the limitations (but i also have some logics by myselfe implemeted).
Here you are. I also put it into the help
DBW Targets priority
Override (used by DBW overriden options)
Rev limiters
Gear cut (Cut and blip)
CAN control
Rev matching
DSG Blip
Overrun (disable when the cruise control is active)
Launch control
ALS
Cruise control
Rolling launch control
Flat shift
Idle
Idle blend
Target table
1 Like
Thx a lot. This priority is followed strictly? Or is there some logic which says a higher value of a lower priority source wins…e.g. CC says DBW target 50% but target table says 70%? I think i observed that if CC is active and i press pedal, the higher pedal value wins. Or when CC is active and i send a lower target via CAN. Didn’t try it but i would prefere here that CC value wins.
You are right. For the cruise control if the target from table is higher than target from CC the cruise control is suspended and the user can accelerate.
When te user close the throttle (the target under CC control TPS pos) the CC is resumed.
It works like in OEM cars when you can for example pass another car without disabling cruise control.
Makes sense…and is CC interaction with CAN DBW control similar? Does CAN control always win or does CC win if CAN control value is lower than CC value?