VEMS 3.6 AAN PNP with firmware 1.2.32, VemsTune 1.5.30, LSU 4.2
When starting engine, wideband in VemsTune shows 1.83.
After sensor is heated up, wideband in VemsTune shows 0.65.
Zeitronix shows 0.91.
Changing sensor = same result :-\
before firmware update everything was fine...
Hello Black,
After downgrading firmware to 1.2.30 (from 1.2.32), does wideband work again ?
In that case i would be very interested to see your 1.2.32 config, please make a bugreport/sharing report; Reports without any additional data are very hard for me to review.
Best regards, Dave
Quote from: VEMS on May 15, 2015, 01:21:43 PM
Hello Black,
After downgrading firmware to 1.2.30 (from 1.2.32), does wideband work again ?
In that case i would be very interested to see your 1.2.32 config, please make a bugreport/sharing report; Reports without any additional data are very hard for me to review.
Best regards, Dave
Report is coming soon.. But when I downgrade do 1.2.30 what will happen with my tables axis because I am using the 700kPa setup (factor 4 in map calibration)...
Quote from: black on May 15, 2015, 02:08:10 PM
Report is coming soon.. But when I downgrade do 1.2.30 what will happen with my tables axis because I am using the 700kPa setup (factor 4 in map calibration)...
In 1.2.30 factor = 4 was not supported so it would make sense to load some 1.2.30 (i hope you saved one) from before for this small test.
Best regards, Dave
Quote from: VEMS on May 15, 2015, 02:38:31 PM
Quote from: black on May 15, 2015, 02:08:10 PM
Report is coming soon.. But when I downgrade do 1.2.30 what will happen with my tables axis because I am using the 700kPa setup (factor 4 in map calibration)...
In 1.2.30 factor = 4 was not supported so it would make sense to load some 1.2.30 (i hope you saved one) from before for this small test.
Best regards, Dave
ok, I will have a look at this...
PS logfile sent via PN
Tried to do a new config file from the .32 log I sent you. (ECU disconnected)
LSU in Wideband settings is 4.2 / 4.2 in logfile like it should be
- Saving config file from logfile
- Closing VEMSTune
- Starting VEMSTune again
- Loading previous saved config file
- LSU is now 4.9 / 4.9 ... should be still 4.2 / 4.2 :'(
- changing to 4.2
- saving
- Closing VEMSTune
- Starting VEMSTune again
- loading saved config file
- and again - 4.9 :-\
Config safe from ECU:
fix_retard[0]=80
fix_retard[1]=80
fix_retard[2]=80
fix_retard[3]=80
fix_retard[4]=80
wbo2_pump_pw_zero2=65
wbo2_nernstdc_target2=85
wbo2_calibration2=00
ibutton_code2[0]=64
ibutton_code2[1]=A8
fuelcut_delay=01
iac2etctarget=00
wbo2_ri_target2=AF
wbo2_config=C0
h[0]=01 02 04 08 10 20 40 80
h[1]=00 60 48 30 18 FF FF FF
h[2]=68 40 38 48 58 50 50 50
h[3]=00 00 00 00 00 00 00 00
h[4]=80 80 80 80 80 80 80 80
h[5]=00 00 00 00 00 00 00 00
ECU offline, config safe from log or from previous config:
fix_retard[0]=80
fix_retard[1]=80
fix_retard[2]=80
fix_retard[3]=80
fix_retard[4]=80
wbo2_pump_pw_zero2=65
wbo2_nernstdc_target2=85
wbo2_calibration2=00
h[0]=01 02 04 08 10 20 40 80
h[1]=00 60 48 30 18 FF FF FF
h[2]=68 40 38 48 58 50 50 50
h[3]=00 00 00 00 00 00 00 00
h[4]=80 80 80 80 80 80 80 80
h[5]=00 00 00 00 00 00 00 00
No WBO2 config anymore ?
Hello Black,
That are some good hints you provided there, it seems you have a earlier compile of 1.2.32 in your VT directory (remember 1.2.32 is still experimental and had multiple iterations) . Please follow these steps:
1) browse into VT_install_dir/vemsprojects and remove firmware_1.2.32 dir
2) browse into VT_install_dir/webcache/fw and remove v3_firmware_1.2.32.zip
3) re-download 1.2.32 from DEV server: http://svn.x-dsl.hu/f/v3_firmware_1.2.32.zip and copy to VT_install_dir/webcache/fw dir
4) start VT, update ini's from web
5) in VT firmware webtool, reinstall 1.2.32
6) upload load this new 1.2.32 firmware to your ecu and upload config.
I suspect there was a mismatch between the firmware in your ecu (some older 1.2.32 version) and the latest ini's from web, which are always for the last (to be released) version. We have many cars running 1.2.32 out there (both LSU 4.2 and 4.9), so rest assured there is no actual wideband problem in firmware.
Best regards, Dave
Quote from: VEMS on May 17, 2015, 03:00:16 PM
Hello Black,
That are some good hints you provided there, it seems you have a earlier compile of 1.2.32 in your VT directory (remember 1.2.32 is still experimental and had multiple iterations) . Please follow these steps:
1) browse into VT_install_dir/vemsprojects and remove firmware_1.2.32 dir
2) browse into VT_install_dir/webcache/fw and remove v3_firmware_1.2.32.zip
3) re-download 1.2.32 from DEV server: http://svn.x-dsl.hu/f/v3_firmware_1.2.32.zip and copy to VT_install_dir/webcache/fw dir
4) start VT, update ini's from web
5) in VT firmware webtool, reinstall 1.2.32
6) upload load this new 1.2.32 firmware to your ecu and upload config.
I suspect there was a mismatch between the firmware in your ecu (some older 1.2.32 version) and the latest ini's from web, which are always for the last (to be released) version. We have many cars running 1.2.32 out there (both LSU 4.2 and 4.9), so rest assured there is no actual wideband problem in firmware.
Best regards, Dave
Thanks we will test this.
by the way, 1.2.30 LSU works...
regards
Ok,
now wideband is running with 1.2.32... thanks a lot 8)
regards...
Hello Black,
Glad to hear its sorted now, sorry for the mixup.
Best regards, Dave
Quote from: VEMS on May 18, 2015, 08:57:00 AM
Hello Black,
Glad to hear its sorted now, sorry for the mixup.
Best regards, Dave
Still issues - did you notice my last logfile (PN)?
regards
black
After days of testing we have still issues...
...wideband sometimes takes 10 Minutes before showing values with the last .32 :'(
Hello Black,
Quote from: black on May 30, 2015, 07:47:32 AM
After days of testing we have still issues...
...wideband sometimes takes 10 Minutes before showing values with the last .32 :'(
I missed your latest comment, i'll locate your sharing report and take a look. note: sharing reports are not automatically reviewed unless explicitly linked from wiki/forum thread or email with a description of problem/data on what needs to be reviewed.
Best regards, Dave
Quote from: VEMS on May 30, 2015, 11:03:30 AM
Hello Black,
Quote from: black on May 30, 2015, 07:47:32 AM
After days of testing we have still issues...
...wideband sometimes takes 10 Minutes before showing values with the last .32 :'(
.... note: sharing reports are not automatically reviewed unless explicitly linked from wiki/forum thread or email with a description of problem/data on what needs to be reviewed.
Best regards, Dave
I know, I know but I sent you a PN here with a link to my newest sharing report - maybe it was lost somehow... regards :-)
i have almost same problem with wideband, always when make first startup after car has stopped over night then wb dont show nothing , then i let it idle for 10 minutes and restart car and after that it shows lambda normally. also when its heated up and only iginition is on then its also showing lambda 1.00 or something .
problem began after installing 1.2.32
Quote from: s38turbo on June 21, 2015, 08:20:45 AM
i have almost same problem with wideband, ...
good the see I am not the only one...
I could test a second 3.6 ECU with firmware update and wideband 4.2.
VEMS AAN ECU plug & play M55 3.6 board with firmware 1.1.96
I did all the voltage tests with the 1.1.96 firmware.
All voltages are correct.
And here is the interesting result. I did the bench test with no wideband connected but DVM and 12V lamp connected.
The voltage is rising slowly up to 11,7V and the lamp is shining brighter. At 11,7V it stays shining and showing 11,7V.
After that I updated to firmware 1.2.30 and did the same tests, after that to 1.2.32 and the same tests.
With 1.2.30 and 1.2.32 voltage is rising slowly up to 11,5V and the lamp is shining brighter. At 11,5V voltage drops to 0V and lamp is off... stays off
Driving with 1.2.32 - needs up to 10 minutes left before wideband is working.
After that, downgrade back to 1.1.96 and the same tests again. Everything works fine like at the first test - lamp stays on.
So it has to be something with the firmware...
AND we did another test with a third car and VEMS M55 plug and Play with 3.7 board in Audi - firmware update from 1.1.96 to 1.2.30 results in no wideband issues. Just fine like1.1.96.
Maybe something with older 3.6 boards??
regards
Hi Guys,
Im running some elaborate tests to confirm this case, will post some more info once i pinpointed (or at least replicated) it in a controlled situation.
Best regards, Dave