I had been toying with the idea of using the IAT voltage to add fuel when on boost.
It's a +5vdc line that increases the fuel compensation as the voltage increases. I found this by loading a gen 1 map into RomRaider and comparing the 2 tables in the IAT section.
You have to look at the voltage increase as the temperature drops, then compare this to the second table that shows fuel compensation increases as the temperature drops. The second table doesn't specifically say "fuel compensation", but I've seen reference to this table in (at least) one other post by RidgeRacer (I believe) that referred to this as a fuel comp table.
It occurred to me that if one were to remove the IAT sensor and replace it with a map sensor by connecting the +5vcd output of the map sensor to the +5vdc of the IAT (dark green, I think), you could end up with a cheap fuel enrichment.
As much as I like EE2, it lacks a way to view or modify these tables.
You can modify the fuel compensation table in RR, save it, then load it into EE2 without error, so that should work.
Thats a good idea, in stock configuration as the intake air temp increase it leans out the fuel..not by a significant amount...but you concept sounds good.
Thanks for the input, busa2001.
I was curious if EE2 modifies the fuel comp table in any way.
I know from using EE2 a little bit that you can set the IAT to dyno mode, which sets all the cells in the voltage/temp table to 24C.
After visiting BitBucket, and updating my VS, I was able to determine that EE2 version 126.96.36.1991 does not write to the fuel comp table.
I went a step further and modified the Advanced form in EE2, providing a easy link to a new form for the fuel comp table. (see attached images)
I substituted the temperature column headings for voltage (by comparing the 2 IAT tables) to simplify the tuning process.
You can't access the IAT map if the "IAT disable for dyno" is checked.
Please note that I had to take 2 screen shots of the IAT fuel comp table because it's a fairly wide table.
Any feed back/suggestions/critiques are welcome.
btw I'm not a VS programmer: I did this by copying/pasting pieces of the existing code until I could build the project successfully.
This next bit says it all (from the EE2 About-> Program info box). These guys really know how to code
I would like to thank particularly the following persons and companies for making this possible. If you wish to work with professionals, I suggest contacting any of them.
bikeland.info Marlin Bially (who first unrevealed the inside of the denso ecus) New Limits Dave Owen (R.I.P. words fastest NA driver for his support and testing) Kansiset.net Jarmo Saastamoinen (gen1 enginebuilding and advice) Samin Autopaja Sami Vittaniemi (dyno- and engine advice) JariM Jari Määttä for very valuable testing and feedback JaSa Jaakko Saarela for implementing the shifter code Smithabusa Greg Smith with providing support for countless users Bryan Bryan Snyder for building the gen2 engine to be tuned Justin BKing mate from Australia for his contribution to code
Hoping to try it out in a couple days.
I'm waiting for some parts for my flasher interface cable.
If my data logger shows that applying voltage to that wire richens the afr, then I will test it on the dyno.
I don't think it'll be a replacement for my vortech super fmu, but I am hoping it's as good as the Powercommander hub and 3bar GM map sensor.
btw: I've created an account on BitBucket under 2k4-busa (search ecueditor) and you'll see a zip file in the download area.
I couldn't get my workspace to push up to bb using Mercurial, but I did zip the entire folder and upload that file on to bb.
I used Visual Studio 2013 Express.
Let me know if you can't download the file.
2k4-busa wrote:Hoping to try it out in a couple days.I'm waiting for some parts for my flasher interface cable.If my data logger shows that applying voltage to that wire richens the afr, then I will test it on the dyno.I don't think it'll be a replacement for my vortech super fmu, but I am hoping it's as good as the Powercommander hub and 3bar GM map sensor.btw: I've created an account on BitBucket under 2k4-busa (search ecueditor) and you'll see a zip file in the download area.I couldn't get my workspace to push up to bb using Mercurial, but I did zip the entire folder and upload that file on to bb.I used Visual Studio 2013 Express.Let me know if you can't download the file. Jon -- Edited by 2k4-busa on Friday 28th of August 2015 08:18:58 PM
-- Edited by 2k4-busa on Friday 28th of August 2015 08:18:58 PM
I saw three files in the download area but they appear to be older zip file..can you post the link, whats the name of the zip file?
I mistakenly left the account set to private.
You can search for ecueditor with iat fuel compensation or here's a link
I've never set up bb before so hopefully this will work
I updated the IAT form with some notes, and cleaned up some unused code.
Once you have extracted the files from the zip file, you will find the Publish folder contains a setup.exe. Clicking it will install the app from the folder where you have extracted all the files.
I'm also going to have my hand at enabling the data logging, so you'll find the Data Logging button is live, but I've done no work to any of the functionality, so basically nothing in there will work on a Gen 1 (yet).
I've not flashed my ecu yet because my interface cable parts aren't going to show up today as I was promised, so I don't know if the FTDV installed correctly. There were some posts that if it doesn't install into the correct folder that it won't flash.
-- Edited by 2k4-busa on Saturday 29th of August 2015 04:15:52 PM
I finished my cable and flashed the ecu.
To verify the map did indeed upload to the ecu, I input a crazy number in the shifter kill (120ms) and from the sounds of the kill time, it confirmed the fdt messages that the map installed successfully.
I then went back to my bin file and played around with the IAT values, and found that the bin file allows a maximum of 255 in each cell.
I've not put any limits on the input of the cells so be aware that if you try a greater number, the table will not update, but will error.
I've not yet wired in a map sensor, but hope to by this weekend.
I can also say that when you unplug the IAT, the FI light comes on. I hope that wiring in a map sensor eliminates this.
A few things to note: This version, like the last production version of ee2, requires .net 4.5 to run. All my hacking and pasting was done on Windows 8.1. with Visual Studio 2013 Express. I tried to run this on an HP Mini 110 with XP sp3 and .net 3.5 and if failed miserably.
-Edit- I reviewed an original download I had saved from bitbucket and the .net was 4.0. The ee2 version is 188.8.131.52 (not .1111 as stated in the title)
Some of you are probably wondering why RomRaider displays different numbers than I do in the IAT table. RR shows all decimal numbers like ".84", ".9", ".94".
Before RR displays the fuel compensation values, the formula ((x+384)/256)-1 is applied to each cell.
When I load the table, I am displaying the actual value (raw number) read from the bin file.
btw...... my credentials as a programmer center around a 4th generation rapid development and deployment IDE. I have 30+ years with the same company programming, installing, training, and supporting our product which we provide to several local police and fire departments.
I finally got a chance to play around with the IAT today.
I did see changes to the AFR while applying pressure or vacuum, but I can't (yet) swear it would make a big difference under boost at/near red line.
I removed the dark green wire from the smaller ecu connector (pin #50).
I then inserted a wire with a factory style pin into #50, and connected it to the +5vdc from a GM 2 bar map sensor.
There was no FI light showing on the dash (what a relief !!)
I connected a volt meter to the +5vdc too.
All tests were at or near idle (approximately 1100 - 1250 rpm) with the engine was fully warmed.
My data logger is Zeitronix ZT-2 logging AFR, TPS, RPM, a Zeitronix MAP sensor (not used in this test) and fuel pressure (41 - 42psi at idle).
After flashing a stock map, my (unscientific) tests consisted of applying air pressure or vacuum to the GM MAP sensor. I only recorded voltage on pin #50, but did not have a means to measure applied air pressure.
Stock map13.8 - 14.2 afr at idlemap 2.38 v at idlevacuum (map voltage going down to 1.12 v) - minimal change in AFR, going up to 14.9pressure (map voltage going up to 4.80v) showed minimal change in AFR, going down to 13.0
24C set IAT disable for Dyno12.5 AFR at 1100RPMMap 2.38 - 2.39 v at idleLittle to no effect by MAP sensor vacuum or air pressure (vacuum to 1.12 v, pressure to 4.80 v)
Set all cells in IAT to zero.16.5 - 18.0 AFR at 1100RPM (mostly in the 17's)Map 2.38 - 2.39 v at idleno effect by MAP sensor applying vacuum or pressure (vacuum to 1.12 v, pressure to 4.80 v)
Set the lower voltage cells to 0.00, and cells from 3.06v - 4.78v to 250.0015.5 - 16.2 AFR at 1100RPM (mostly in the 17's)Map 2.38 - 2.39 v at idleEven the slightest pressure into MAP and the AFR would begin to show a rich AFR, Applying up to 4.80v would give an AFR as low as 11.9 - 12.0The slightest vacuum into MAP (1.12v) and AFR would go up (lean out) to 17 - 18.50
If I applied too much pressure where the IAT voltage was 5.00 on meter, then FI light came on.
It would seem that every cell needs to have a value, or the ecu is interpolating the values in the empty cells. I will test this tomorrow. I've run out of time for today.
Tonight I will reevaluate my code, and perhaps I'll find my scale of voltage to fuel compensation needs some work.
Life and it's challenges have side tracked the project.
Been painting the kids bedrooms, ordering beds, etc, etc....
And then there's work.
I've barely had time to verify my code (which seems in order.... I'm not doing to much in there except reading a table, allowing changes to the table, and writing the data back).
What I really need is dyno time.
anything new? any updates?