These are for VEMS ECU Wideband Users only
Please review your wideband controller settings in MegaTune, the following settings are the factory recommended settings.
In MegaTune:
Settings->Wideband Settings
(http://www.vems.co.uk/VEMSConfigs/MTWidebandSettings.png)
Note: Pump zero pw (5V/256) is specific to your VEMS unit, and does not need to be changed.
WBO2 calibration constant is specific to your sensor this will have been calibrated and does not need to be changed.
Settings->Wideband Controller PID
(http://www.vems.co.uk/VEMSConfigs/MTWidebandControllerPID.png)
Note: Pump PID nernst target is specfic to your VEMS unit, and does not need to be changed.
If you have a VEMS v3.3 or later both Pump zero pw and Pump PID nernst target values will have been defined from the factory, and will have been supplied with your unit. If you have any queries just shout.
Rob I assume these apply to us on ver 3.2.
Havn't checked to see how diferent mine are to the ones you have given.
regards
Agriv8
Yep all v3.x, these settings are more about the way that the sensor is driven than the hardware doing the driving.
Hi Rob,
i think i have done something wrong with my WB settings. The data i have with the unit is:
pump-= 4.14V
wbo2_pump_pw_zero=0x67
wbo2_nernstdc_target=0x85
pump+= -3.3mV/200 Ohm
AREF=4.9V
(C103=1nF, no D100)
What settings should i use?
Thanks
can the settings, that comes with the unit,be recalled,
As i dont know the setting for my board .VEMS number 1484.
Thanks,
Skassa
Go to the webshop and select My Account, the order history will have the details.
I cant remember what info they give you with a PCB on its own though.
Quote from: billman on April 11, 2008, 11:16:20 PM
Hi Rob,
i think i have done something wrong with my WB settings. The data i have with the unit is:
pump-= 4.14V
wbo2_pump_pw_zero=0x67
wbo2_nernstdc_target=0x85
pump+= -3.3mV/200 Ohm
AREF=4.9V
(C103=1nF, no D100)
What settings should i use?
Thanks
?
Should i give in MT Pump zero 103 and nerst target 133? Is my conversion correct? I also need to know the Calibration constant.
Those conversions are correct. The calibration has to be done for the sensor, the details of which are in the UserGuide:
http://www.vems.hu/wiki/index.php?page=MembersPage%2FPhatBob%2FUserGuide
Cheers
Rob
just did the configuration. I was way off.
Was Pump Zero-67 and Nerst 85, Constant 125
i had to have: 103, 133 and 206
Nice huh? Hope that it will be better now.
Where did the original pump zero and nerst values come from?
As i said i dont have a clue and i put in the file the hex values! ;D
I dint have black smoke or sothething like this, i noticed it because it smelled funny...
Is it possible, wbo2 calibration constant need 231 to 20.9 O2, much higher than usual?
v3.3 1.1.27 all wbo setup values set as above.
Yes 231 (E7) is perfectly acceptable - the calibration values tend to be at the higher end of the scale, I'd be concerned if it were calibrating with a low number, I cant think of seeing much below 150 (96)
My wideband Isn't reading correctly(Reading from full rich to full lean) It's not a problem with the sensor.
Any ideas?
(http://i516.photobucket.com/albums/u330/AjRoselli/wberror.jpg)
edit: In case anyone was wondering it was a problem with the sensor connector. It's always the thing that's out of site.. :(
I can't seem to get my o2 gauge to read anything at my calibration screen...
VEMStune .10.14 (2010.01.08)
1.1.7, running Mattias' config, modified for my own use:
Wideband Controller
---------------------
Warmup ABS 228
Max time at ABS 41.9
Fallback V 176
Retry after 24
Heater PID Ri Target 150
Heater KP 70
Heater KI 16
KD 26
PID Int. Limit 128
Pump KP 21
KI 78
KD 0
PID Int Limit 132
----------------------------
Base Setup\Engine Calibration:
----------------------
Pump Zero PW 100
Pump PID Nernst Target 134
WBO2 Sensor Calibration 100
----------------------------
WBo2 Calibration:
----------------------------
WBo2 Sensor Calibration 100
Running sanity check:
---------------------
X Table Header order "launch rpm curve x values must be in strictly monotonous ascending...
X warmup_clt[9] "Please check warmup_clt[9]!
! Tooth_wheel_twidth
- "please check tooth wheel twidth [0,1]
! Shifcut and Launch "please check shiftcut input!"
----------------------
Soo, I don't want to change anything about my tooth wheel width, since the motor runs great, but that's a different thread.
Just trying to get you guys as much data as I can about this.
the O2 sensor IS heating up.
Initially upon wiring this up, I wired up pins 2 and 4 crossed (read: pin 2 should be disconnected, pin 4 goes to pin 18 on EC18... I had pin 4 disconnected and pin 2 going to pin EC18). This has been fixed.
I thought maybe this had fried my sensor, so I'm now running it with my friend's sensor installed, but i'm having the same issue.
Thanks for any advice you guys may have.
Also... There isn't by chance some output or input I have to enable in order to get my wideband to be recognised?
I got it to recognize an 02 value once in a while... It'll come on after about 45 seconds of VEMS being on, is this just the delay from power on until when the heater is up to temp?
It doesn't show me the o2 value every time, either.
After calibrating it (value of 174 = 20.9), I started the motor, and didn't get a lambda value, or an AFR value. After about 8 seconds I shut the ignition off, and vems showed me a high value of about 1.75 Lambda and 17.0 for AFR... Is there some delay between starting and when it'll show me the values, and I just shut it off right as it gave a value? I'm having some strange issues w all this, lol
When the shadowed peak needles hit 1.75 and 17.0, I had already had vems running for a bit, and I was getting 20.9% on the wbo2 calibration screen, then I closed the calib screen, started the motor, and got nothing on the gauges until after I had shut the motor off in about 5-7 seconds.
Update:
If I run the motor, it'll eventually show me my AFR and Lambda. However, it cuts in and out, seemingly at random.
I'm checking my wiring (again), but aside from that, what could be causing it to cut out like this?
Hi!
Is the same wide band controller settings Mega Tune than Vems Tune?????
:-\
Has anybody actually tried to change the pump PID settings? I know that it's factory recommended. However, i have 2 LSU4's where one is connected to a round display. So I'm able to compare them against each other.
With experience from the idle PID tuning, I expected that the use of Integral is slightly 'different' than other PID controllers, also here. In fact it looks to me like the I is acting like an extra P with filter. And to let the I value overplay the P value as much as the standard settings suggest, well its a bit unusual, but i don't have the experience with WBo2's to do anything but an educated guess.
So what i did - disable the KI value completely, set to 0, and move the KD value up to 5.
Result - More consistent readings, not jumping around so much and better convergence with the other sensor.
I don't need the lambda readings to be jumping up and down 5 times per second anyway, there is not enough time to correct for this at the injectors.
But the question remains.. how will this affect the sensor? What about life expectancy?
Rob, I put your setting still I have unstable reading in VT, it goes rich then lean continuously.
What else can be done?
Are these values valid for 1.2.11? I upgraded to help with the infamous audi phantom trigger errors (seems to have helped!) and I love the new boost PID options but in upgrading my wideband (and MAT) sensor is not functioning ???
Just heater Ri target is changed.
Quote from: GintsK on April 11, 2013, 10:11:30 AM
Just heater Ri target is changed.
To what? Everyone uses 150...........................
180 is for firmware 1.2.0+
Quote from: MWfire on April 11, 2013, 01:57:35 PM
180 is for firmware 1.2.0+
I'll give it a shot, thanks!
I got following answer from support:
Quotet depends on the firmware version:
Fw 1.2.2 and above: Ri(wbo2_ri_target) should be greater then 159 and less then 181.
in older firmware: Ri should be greater then 139 and less then 156.
Quote from: GintsK on April 12, 2013, 05:48:40 AM
I got following answer from support:
Quotet depends on the firmware version:
Fw 1.2.2 and above: Ri(wbo2_ri_target) should be greater then 159 and less then 181.
in older firmware: Ri should be greater then 139 and less then 156.
Nice, so it is not actually published anywhere? (except here now)
Quote from: Sprocket on April 13, 2013, 08:11:24 PMNice, so it is not actually published anywhere? (except here now)
Since this was changed VemsTune warns you if you are not using a wbo2_ri_target value in the correct range that matches your firmware.
Everyone not familiar with the "validate config" button should look it up.
Quote from: Sprocket on April 13, 2013, 08:11:24 PM
Quote from: GintsK on April 12, 2013, 05:48:40 AM
I got following answer from support:
Quotet depends on the firmware version:
Fw 1.2.2 and above: Ri(wbo2_ri_target) should be greater then 159 and less then 181.
in older firmware: Ri should be greater then 139 and less then 156.
Nice, so it is not actually published anywhere? (except here now)
This has been discussed before on this forum why vemstune keeps throwing up this error with what is seen to be a default value ??? it appears that Vemstune is questioning a valid default value?.................. this is not obviously the case, but there is no support documantation on either wiki or this forum that suggests "wbo2_ri_target=A0 to B4" only "wbo2_ri_target=96"
I'll change it to 160 just to stop the error, since I don't know what real effect it has in the range of 160 to 180.
There is no dialog in Vemstune to say it should be set between 160 and 180, only when the the config is validated.
imho vemstune change that automatically when new firmware is uploaded.
Quote from: MWfire on April 14, 2013, 03:03:56 PM
imho vemstune change that automatically when new firmware is uploaded.
Not on mine it didn't, I wouldn't be talking about it if it did :D