6.09.2010
While wainting for the EGT chips i was wondering if i should chenge the resistor to use instead of the stock IAT the 1.8T IAT sensor.
- you get 1C resolution, but with new (1.1.7x or 1.1.8x) firmwares the resolution is 2C even with the PTC type MAT sensor. So no big gain by upgrading.
- What values must they have and were is this resistor placed?
- for PTC type audi-AAN/3B factory MAT (also called "strong MAT pullup"), there is a piggyback resistor, 530 Ohm on top of 2k7 above the CPU (between CPU and the closer edge at the endplate). No need to unclamp, it's enough to remove the endplate only !
- Remove the 530 Ohm so only the 2k7 stays on board (that's why it's piggybacked, for easy removal). That small HW change converts it to more standard "weak pullup" that perfectly suits the MAT of most engines. But of course, on the software side, chosing the right (eg. 2252/256 NTC) curve during firmware upload or configuring proper 17-point curve is still needed.
Thanks
24.08.2010
EGT problems 0 to 1125 Celsius and again 0 changing every second on VEMS. The sensor is brand new and came in yesterday. Where is the problem? Can it be the controller inside VEMS?
- yes, possibly. Try to short the EGT inputs, white and green wires.
- also, try to disconnect EGT sensor, and short the EGT inputs, white and green wires. See what happens
- you can also try with EGT sensor connected, but removed from the exhaust. Maybe some ground-loop causes this problem
- make sure the EGT inputs don't touch +12V, not even for a split second
Answer
- Removed sensor-no change
- Short wires-no change
- opened VEMS today and seen no wiring issues
-If i wanna change the AD597 do i need something special or i simply replace it like every SMD chip?
- it can be replaced easily
- it does not need extra calibration
- however, test some mcp3208 analog input (EGT also connects via mcp3208). If the problem is from mcp3208, than changing AD597 won't fix the issue.
- make sure to stay in 0-5V range (12V on mcp3208 input damages the board immediately)
09.10.2009
Do we have any MSQ file for the AAN or ADU with Plug n Play VEMS for the 1.1.44alpha firmware. I used the 16x14.
I upgraded to it and now the car doesnt start and i think it has to do with ignition, or other settings, since the files i had where from the 1.1.27beta version.
1.1.44 is not released. If you need some recent feature, 1.1.50 (also not released yet) is a better choice.
- MSQ will not help you if the megatune vemsv3.ini file you use is old, and lacks sections.
- the most likely problem is injector staging in config_ext , but without your config and tables dump noone can tell. 1.1.50 is GenBoard/UnderDevelopment/FirmwareChanges ( but recent VemsTune can download it directly from internet). MembersPage/MarcellGal/PowerAndTraction now running on 1.1.50 .
17.01.2009
Did someone managed to listen and use the stock Knock sensors with VEMS? If yes pleeeeaaaaase help!
Hallo, i was amazed as i saw today that there is a PNP Motronic VEMS.
The question is now how PNP is it and what must i change.
- be warned that there are many different motronic pinouts. You have to identify and verify yours
- if you correctly identified and verified, it should be rather simple to get the car running if it's a tested setup
- As far as i know it is the same as the Audi ABY engine and the later AAN engine with the Hallsensor at the Camshaft pulley. I suppose that this setup is known (please confirm). If it is so, then this means what with the VEMS i can control and setup right away Ignition,injection and boost control?
- if the setup is yet untested, one has to be even more very careful with the pinout verification and documenting it. This is not recommended to someone who would not dare to make a native econoseal install
- if you correctly identified and verified, it should be rather simple to get the car running if it's a tested setup
- using a factory harness can help a bit, if it's in good condition. But any problem can cause a lot of headache, and if there are problem, finding and fixing it is often more difficult than with a self-made harness (or a new documented harness)
- Factory harness is OK right now. The car is original and running every day.
- getting the car running is the start of the fun and risks.
- One has to be very careful with tuning, and be prepared to stop and go back to the measurements and debugging, should the slightest suspicion arise. Tuning requires knowledge and experience. It is highly recommended to get someone experienced help, at least for the first few times.
- one has to plan any modification very carefully. It is very important not to ruin something important (in harness, ground, flyback, fuses, or ... config).
- Of couerse. My main consern is the instalation and Set-Up of the VEMS on my car. If the sensors are recognized and work right after the VEMS is plugged (and with the initial - Basic maps) with Megatune. After that i can get someone to tune on megatune.
I am not very electronically inclined so my questions are dumb:
I plug the VEMS PNP-Motronic to the harness, istall and connect and verify and calibrate the Wide band and the EGT. Is the car now ready for the Tune?
The VEMS comes out of the box with support for the Ignition, injection and Boost control without further mod to the Sensors or the cables of the Car?
Is it possible to find for starters a full runing program for the ADU engine, and from that point modify it further?
- we have full running dumps for ADU engine (and 3B, which seems to need slightly higher pulsewidths) but even from a conservative one, one has to be very careful (add more fuel, take away some ignadv, verify lambda, EGT and sound, etc...) and tune almost like it was an unknown engine. Such configs help to get the car started though
Hi, i am thinking of Using the VEMS v3.x on my currently Stock Audi RS2. It has from the Factory an I5 2.2. liter Turbocharged engine (Engine Code-ADU). The stock ECU system is a Bosch Motronic. For the future i am preparing a strong bottom end and big turbo.
The car is an everyday car and want it to have a cultivated ride (when i am cruising with it or in the City). I want the Climate Control (Air Condition), Auto Check (it has also Trip Computer but i think it will not work with the VEMS).
I would like to make the convertion this way so i must only change the less possible stuff to run on Vems (and also easy to go back to the Motronic system if the car will be sold).
I connected VEMS and tried to connect it to the PC.
The connection is Succesful but i become a Message that the tabes between controller and MT doesnt match.
I Choose 16X14 and it says the Controller has 12x12. I made a FirmwareUpdate to 16x14 but i still become the same message.
- follow VemsAudiAan
- You will use v3gui to upgrade firmware to 1.1.27 firmware and use
- 12x12 is recommended, you don't need 16x14 at all
- [starting config] and tables
- MT Version 1.1.23rc will read real injector pulsewidth / 10, so you need 1.1.27 or similar. Choose 12x12 high-boost at startup
If you have pinout for ADU, we can check if the cyl1 <=> 3 ignition is swapped, so we can hint h[2]= ... change if necessary.
MAT sensor
- measure MAT sensor resistance at know temperature.
- if you use the factory PTC type sensor (appr 500 Ohm at 25C), than ptc_260_425 or similar is good (425 is for the internal pullup resistor, which is actually 430 Ohm in your controller).
With bad table chosen at firmware upgrade, the MAT reading will be almost constant, and if it changes at all, it decrease with rising MAT.
2..3.2008
It started with Marcels file. Very nice. Still no EGT and WB installed. Very happy!!!
4.3.2008
I installed the cables for the Lambda and EGT. The 12V connection for the WB comes not through VEMS but separate doesnt it?
I would also like to know about the WBO2 Calibration Constant. Should i measure it or is it mesured from the factory?
- To calibrate wbo2 you have to open the bay terminal in Megatune then type Man mde02 mlp07.
More info here: http://vems.sourceforge.net/manualhtml2/ch07s02.html
Thanks
Done some more today. I am seeing the target
AFR at idle but not everywhere else. I also made a Log.
Here is some throttle while standing and the other one my first log while driving. Also the MT File i done it
- v3.x EGT Calibration 0x4B or 0x4C (75 or 76 in MT) See AfreshTiny/EgtCalibration if you want to verify with an input signal.
http://www.vems.hu/files/Standing%20Throttle.xls
http://www.vems.hu/files/drive.xls
http://www.vems.hu/files/changes.msq
OK, done some more and i am very pleased with the Results. Car runs fine with this basic tune. I have tryed to controll boost with VEMS but i somehow cant get it, till now!
So i start:
1. It is set to MAP Target but i am going to run it at Boost Target (page was down so i couldnt read about boost settings).
2. Boost is set to 200 kpa but it somehow goes till 240. Right at 240 kpa it takes fuel off - must search why i cant see any that can cause this but maybe i am blind.
3. Must see that somehow i get the knock to work. Dont even know if my channels are correct.
http://www.vems.hu/files/Boostlog1.xls
http://www.vems.hu/files/mallon%20kalo.msq
13.3.2008
So after running with VEMS and daily use some other issues that i dint solve yet are:
1. After crank up the RPM stay for several seconds high and then it starts going from 1000-1500 RPM so as if i the throttle kick and let and then again. After ca. 30 seconds is it away and idles very nice.
-Do you think i should do the diode install?
http://www.vems.hu/wiki/index.php?page=MembersPage%2FPeterJensen%2FAudiSidle
Here is the start-up
http://www.vems.hu/files/Idle.xls
Boost-control
2. I cant set the boost control up correct. I tryed and set the boost control so now i dont get Fuel cut because on the Inj PW and noticed that i get the Boost i want (almost) but it is not stable. I set it to 1 bar and i get 1.1 then goes down to 0.85-0.9 then again to 1.1 then again down ect.
This is the RPM vs Boost vs TPS log:
3490 167.0 99
3550 173.8 99
3605 181.0 99
3669 188.5 99
3733 197.8 99
3797 206.5 99
3870 214.5 99
3926 201.0 99
3939 188.0 99
4092 192.0 99
4115 202.8 99
4146 212.5 99
4297 212.8 99
4249 196.5 99
4338 184.5 99
4421 185.0 99
4447 197.8 99
4587 211.3 99
4622 204.0 99
4618 189.8 85
4559 162.0 5
i have logs for everything. But mcd-mct for nowthing ? ;-)
The boostcontrol is usually almost a PD-controller.
P=255
D=... hard to tell (start with decimal 20)
The I value can be close to 0. Usually there is no time for the I to act in gear 1 and gear2.
As a result, there might be a systematic error (eg. you set 190 kPa but get 210 kPa, this also depends on the boost valve reference position: 1/5, (start with this: 2/5), 3/5, 4/5 (you will get highest actual boost with 4/5, likely significantly above target).
Still have the boost fluctuation problems with the N75 control and i am not so pleased with it yet.
I just realized what crap i writed about the overrun Fuelcut and resume. I was not thinking.
Today i installed the Diode and set the boost settings as mentioned above. Warm car startup is very nice and the boost very smooth. Thank you very much for your help. I am very happy with the Results.
The next step would be to set the knock sensing better than i have now.
Thanks again
Anybody knows why now and then i have this problem during idle. It seems that the Idle valve doesnt respond so fast. It gets worse with AC.
Can it be that my Idle valve is faulty? It happens occasionaly.
http://www.vems.hu/files/Bad%20idle.xls
This is my file at the moment:
http://www.vems.hu/files/After%20Diode%20and%20Boost.msq
Please comment or suggest changes for EGO, VE-Autotune, Idle ect. Whatever you think is wrong please comment. I also need to tune the Spark table further and a bit the lambda.
Thanks
Today i did a 200 km Trip and have noticed that when crousing and going at about 100 KPA then the EGT goes till 750 Celcious. The EGT sensor is right after the turbo. Is it ok or should i change something?
http://www.vems.hu/files/High%20EGT.xls
Knock sensing
Can someone help with the Knock control? Does it read both sensors? What settings should i have? Should do it with the Terminal or with MT?
See knock_chan (for channel 0 and channel1) on GenBoard/UnderDevelopment/FirmwareChanges
- Shoudn't both sensors work at the same time (one is near the 1 and 2 cylinders the other near 4 and 5. What other settings for the Audi I5 engine?
You can also check KnockListener during tuning.
What are you use for the MAT sensor? I used ptc_260_425 but it doesnt move so fast with temperature changes and it doesnt seem so "sensitive". Must it be like this or is the file not soooo good?
Should i go with a newer Firmware or is the 1.1.27b the best for Auditrigger?
26.06.2008
I have been running closed loop under all conditions, also under wot, but it seems to not being able to maintain lambda 1 at idle, were it will swing from 0.97-1.07 or so,
is i turn ego off it will be stable.
I made the VE-Table as accurate as i can but when on idle and the fan kicks in it takes 20 seconds or so for the idle to be somehow stable. When the fan stops i get the same. When the AC is on the same ect.
It is stable only at the conditions where i tuned it (i.e. warm engine and AC off, and big fan off) when something changes it starts to jump here and there.
- What settings do you use?
- With FW 1.1.27 i cant use 16x14 Maps (what do i do wrong). Should i use the FW files found on the My 16x14 Setup or something else?
- seen (not released) 1.1.33 FW version and i would like to try Switch-activated config Swap features out but i can't understand how should i load 2 different configs
- 1.1.33 is not released, so don't use unless for testing on the bench or mt development
- for sure, you will need to prepare 2 sets of config/tables first (eg tune with MT, a primary and a secondary) and dump in mcd/mct format. When publishing these for forther help, you can add some description about your goals.
- MT can only adjust the one in the primary position. The secondary config must be uploaded manually (mcs in the mtt file changed to mcS1, also different confswitch=.. value)
- 1.1.33 is not released as stable for any setup. (no MT released)
- Do you need 16x14 for Audi 5 Cyl turbo?
30.06.2008
Managed to run the 16x14 FW and map i made. Problem: idle RPM stays very low when AC is ON.
Is there anything to do with this on the 1.1.27 FW Version?
Yes:
- use low iac_integral_limit_inc (maybe 2..3)
- Increase iac_ref_pos[] so it can handle AC.
- increase iac_integral_limit_dec; so RPM can go down without AC
Or must i wait for the newer ones with the map switching ect?
map switching should not be needed for AC, although 2 different sets of iac_ref_pos[] make it easier. The same effect as a 100..510 Ohm resistor from iac pin switched to GND when AC is active (AC relay input, if active low): to add some current to iac to open it more when needed.
The VBatt compensation in 1.1.3x will help for sure. The vbatt tends to drop with RPM around 900 RPM (mostly because of the Bosch alternator), which cries for this vbatt compensation, true
Do you have logs with AC and without AC ? Just make sure to number logs the same way as the mcd / mct dumps if you change the config in the meantime (as is likely)
MembersPage/Billman/VEMSOptions
MembersPage/Billman/BuyingList
Thanks a lot
Vasilis