Has anyone tried pin 77 on an evo 7 ecu? I can't seem to get it to work using that pin. There seems to be no voltage and when I opened up the ecu it appears to be a broken circuit with missing resistors? Is this because jdm e7s didn't have the fuel temp. Wiring up the iat sensor to the Afm pin and changing the rom to run off that works fine however. Also need scaling for apexi 3 bar map sensor if possible. Any advice? I've gotten it running but would prefer if I could get those issues sorted.

 

hello look at my logs question

i have been trying to get sd working... have a few logs for u guys to look at and attaching my current VE tables. the evoscan log is of mainly cruise and some 0-5psi stuff, the other log is a 3rd gear run.

whats strange is that in the evoscan log at 130-140kph i am running a fair bit rich.. approx 1whole afr.

my idle trims look quite good, cruise are currently bad.

 

At the end of your cruise/idle log, your STFT goes pretty negative. It looks like you need a lot less VE at idle. I'm assuming that your 'Boost_PSI' column is kpa? You didn't include your LTFTs, so I can't tell the ultimate adjustment, but based solely on STFT you need to take out some VE at idle (unless your LTFT Lo was very postive at that time).

Cruise looked ok for the most part, with STFT bouncing around 0, but again, without LTFT mid, I can't tell if it's dialed in well or just adjusted and pushed everything into LTFT mid.

OK, just opened your other log and see that LTFTs are there. Your LTFT mid is almost maxed out negative...so you need to remove VE there as well. At idle, your LTFT Lo is about +2, and your STFT is about +2, so that looks good. Maybe in your other log at the end, the LTFT Lo was postive?

It's a bit tough looking at two logs with different data. This is what I would suggest to log to be able to tune the VE tables well:

After fully warmed up:
1. Log of idle with boost (kpa), load, LTFT Lo, STFT
2. Log of cruise with boost (kpa), load, LTFT mid, STFT at various, but steady RPM:
2000 RPM
2500 RPM
3000 RPM
3500 RPM

If possible, if there are slight uphill or downhill roads, see if you can do the cruise logs both ways so that you can get different map/load levels at each RPM.

That's the only way you can get a good representation of your 3D VE map without before charts from your MAF based logs.

 

Just to give you an idea of maybe where the problem areas are, here is what your 3D VE map looks like, multiplied from your 2D tables:

Simple interpolation is done between the cells. If you want, you can show more map columns and interpolate yourself.

In comparison, here was my 3D VE table from my maf logs, when I was tuning SD a while back:

I have a greater increase in VE with change in map than you do. For example, at idle (30-40kpa or so), I go from about 70% VE to about 85% at 100 kpa. Your table shows a bit flatter with map, showing 90% at idle, all the way until 100kpa, where you have 95%.

I think if you get some good logs that I mentioned above, then we can iron out the best settings for you. In general, though, I would probably say shape your map VE a bit more downwards at idle and then use your RPM VE to tune different cruising RPM as the same map. Then continue to adjust back and forth. (This is where a 3D map would help rather than 2D maps...but we should be able to get tuned pretty well).

 

Well, kind of lol. The one's I posted are the main one's I constantly adjusted. The 2 1D tables are just the setup for the "stumbling" fix, the 2 tables labeled "Asynch" are for throttle tip-in, and the other 2 are self explanatory. I did however retune pretty much most of my fuel maps as well as well as the throttle crossover point from closed to open loop. For the fuel map I adjusted the 0-100 kPa/Load% range to adjust for the new way the map is being read due to the MAP sensor, and I had to take out a bit of fuel in my peak boost area of my maps as it was a little on the rich side, but that also could be due to the difference in how the sensor compares to the map. Timing I pretty much left alone as it stayed consistent the whole way through, and if anything I added a degree here and there.

 

eric.. i will put maf back on and log again.... actually had a good run but for some reason the logs came out wrong

 

You don't need to waste your time, since you are already now on SD. Just do the logs I mentioned above and we should be able to dial in your VE tables from that.

 

I didnt see any portions labeled asynch anything or anything close, thats why i asked. I want to make sure i have all of the patch input into my rom

 

Did you use logworks to chart that?

I NEVER got that kind of data down low and my data at low MAP values has always had a HUGE standard deviation to it, even after removing data like accel/decel and fuel cut conditions. I always get good tight data above about 2500 RPM and 50 kPa though.

 

Yep, I used LogWorks, from what I remember. To multiply out the SD tables, just Excel, with interpolation for the extra columns so I could compare the two maps.

What equation did you use for your VE? I think I have a link somewhere in here with tephra's data that I charted for John when he was helping Tephra with the VE tables. I think in there I have what I used...baro+temp comp load with MAT.

Here's the link I was talking about.

For my data, I used VE=100* Load/(MAP*(298/(273+MAT))). At least that's what I remember and mentioned in this thread.

 

Yeah, I was actually thinking something related but different. My mistake. I get crap data when charting AFR. I seem to remember getting decent data for VE back on my old setup.

 

What you can do if you are already on SD, is to make 3D charts of map vs RPM with total fuel correction as the data. By total fuel correction, I mean:

STFT+LTFT Lo for idle
STFT+LTFT Mid for cruise

That's leads to a question I have...isn't there a mut request or variable that hold the currently selected LTFT? I know DSMLink had this as an option to log. It would help in making these type of charts.

This can give you a clear picture of where your 2D VE tables need adjusting. Again, it gets a little tricky with just the 2D tables and trying to match a 3D chart, but it can be done, just not as easily as a full 3D chart.

I just took a look at ziad's logs and did this in LogWorks. As long as you have good log data, such as a nice long idle and nice, steady cruise at different map and RPM, then the 3D chart will be very helpful in tuning the SD tables. The rest, after that, is just the async/sync throttle and accel enrichment.

If anyone wants to see any screenshots of what I am talking about, let me know.


Eric

 

is there a formula to convert the formula used in ecuflash for one appropriate for evoscan to match up kpa in ecuflash to kpa logged in evoscan? it would help me greatly to see what corresponds to the ecuflash kpa values as I don't have the proper scaling for my avcr map sensor. That way even if the kpa values aren't correct I can match up the values at least.

 

the last post sits where im stuch at as well...

What exactly are guys logging to know where in your fuel/timing tables you are at and how does that correspond to the SD tables to adjust them ?

 

1psi=6.895kPa

The kPa you want is absolute pressure, and the psi you are logging is probably gauge pressure.

So, whatever your formula in evoscan is, just add atmospheric pressure (14.7 at sea level), then multiply by 6.895 to get kPa.