Num cylinders 8 do not change to 2 when restart device.
Yes, but now we get this false trigger setup warning (24tooth 2missing).
“The declared number of primary trigger teeth is incorrect. Their number multiplied by 2 should be divisible without remainder by the number of cylinders, and 360 should be divisible by the number of teeth without remainder. Typical numbers of teeth are 60, 36, 24, 12, (number of cylinders), (number of cylinders divided by 2).”
alright so i first installed the v3 on a test Ecu.
update went fine from 2.155.
DBW - it is connected to normal VW throttle body 06a133062C
the two signals are opose to each other, it cannot be defined correctly. i tried to set it up and the relation (shouldn’t it be set up already in dbw calibration?)
when i disabled check signal throttle works no issues.
You need to define the characteristic in TPS check tolerance table:
So check the check sensor voltage at 0% of dbw, and 100% of dbw opening, enter those 2 values in this table and interpolate.
You have very simple system, but this approach allows to define any type of plausibility check
I have done it as you said. it does work, but, strange throttle interference occur.
attached log, throttle dc changes, no pedal movement, bench with stable power supply
Can this table table generated from the auto calibration?
Did Old V2 Black disregard those checks previously?
Do you mean the spikes on the DBW DC ? It is ok until the throttle is stable at position.
According to the plausibility check autotune it is planned.
In V2 you selected from drop-down list the plausibility check type.
But if there was not supported plausibility check function it had to be hardcoded.
Now it is not an issue as you can define any function.
And trust me some types of plausibility checks are very very strange.
weird issue i have encountered with, every time I reconnect to the ecu, it says that the data ecu data is different from the laptop data, even if the data is saved in ecu folder.
when i checked , the backup in the backup folder is saved correctly. when it press “Get Data From EMU” it is the latest. if I press Use Client DATA it reverts to first calibration or something like that.
