Thats gotta be it. Thanks man/heh I've been logging 2byte and just moved over .

Other than the jitter issues that all SD roms face sub 3K RPM, it looks good. I can't wait until we can start identifying and deleting unused/unwanted code, It's just a time issue for me.

 

Hi all,

I've been testing the 8859 variant for my usdm evo ix, and I've got it running almost perfectly. Idle, cruise, and even boost are great. The AFR's are right where they should be, however for some weird reason my ignition timing is way off during boost from about 4-7k. Some areas are off as much as 3-4 degrees compared to the map. Has anyone else been experiencing this?

 

If anyone wants to see what exactly i'm talking about. Here's a copy of my evoscan log...i tryed posting my map also, but it exceeds the file size limit. I'll post up pics of my timing map in a bit.

 

I noticed that the Timing Retard Limit #1 under the "Global Ignition Settings" has changed from 203 to 255 with the 3d SD map. Would that affect my ignition timing or is that value required? Any ideas are greatly appreciated.

Thanks!

 

How does your VE and kPa to Load map look like? Post pic of those too. Is your boost about correct in logs (120-130kPa=17.4-18.8psi)?

 

^yes your right, I posted all the pics including the log just to make it easier. There aren't that many data items because it was only a 2nd gear pull. I was also logging all sorts of stuff to check my trims at the same time which wasn't good as far as resolution. Thanks

 

Did you datalog your intake temp? There is also reduction table for ign advance as function of intake temp.

IIRC baro&temp compensated load is used for table look up's in tephra roms. Is it now so that by SD calculations we get raw load and that is still modified with value of baro (locked in sd) and intake temp? If it is like I suspect, you would need to datalog baro&temp compensated load to get know what load value is exactly used for table look up as 1 byte load is based to raw load value.

 

Unfortunately I did not, however it was fairly cool about 50-60 deg F and my temp sensor is placed in the lower section of the upper intercooler pipe.

Where is this table you speak of? I can't find any tables in EcuFlash referencing ignition retard vs. air temp. I've only seen wgdc comp vs. temp.

 

Ok. That table is not necessarily defined in your rom, I'm using 8858 myself.

Check this thread for IAT comp xml mods:

https://www.evolutionm.net/forums/ec...ing-trims.html

Just to be sure, did you check your Octane Level, was it still 100% (= your car was using only High Oct maps, not interpolating between high/low)?

 

^Yes I made sure it wasn't interpolating as well, and to be extra sure I made both Hi and Lo octane ign maps exactly the same during the run because it happened a few days ago. I've only recently started to add my timing back.

BTW thanks for your help. I'll try and get those definitions and log again later today.

-Jon

 

If you are experiencing high intake temps I think it would be best if you got a handle on whats causing that before diving into the table to correct it.

 

Exactly. My purpose was not to zero that table out in any case but to point that if intake temps are very high, timing is reduced few degrees. It is good to check intake temp by datalogging anyway even outside temps are low, just to make sure that measurement works correctly.

 

what about this rom makes it so I cant use my front 02 to control closed loop while having mrfred's wb logging patch with wideband control turned off? Is that the case on all SD roms?

 

now neither setting is giving me o2 feedback.

 

Started over from scratch. Everything seems to be good. Im currently using the fuel temp sensor to mimic iat. And its the most driveable my car has ever been. I wont deny that some of my issues with my MAF tune (stalling, bucking, etc) could have been fixed with proper tuning. But I couldnt do it.

I do have a hiccup that seems to be between 2500-3500 rpm and if I had to guess was around 80-90 load. Im willing to bet its load dependent.

But the hiccup really is about 1/10th of a hassle that my maf tune was.

I set the MAF Comp table to 100s, with Percent(128) scaling. I went through and set my Fuel map up to be real target afr numbers. Than have just been adjusting the VE map by comparing logged WB to AFRMAP. Its my first venture into SD.
I figured since my logged MAP kPA was pretty much inline with the load Im logging now and used to seeing, there was no reason to modify the kpa-load table. Im still not 100% sure why I would need to adjust the KPA-LOAD table. But Im just taking it slowly and havent been into boost yet, just adjusting my closed loop areas, while forcing open loop.

Thanks. I am really really happy with it so far. Im going to try the different jitter fixes and see if I can alleviate the hiccup Im seeing. But as long as it doesnt happen at WOT, I'll live with it. Ive been living with alot worse for the last 3 years.

Id still like to know if this rom will be, or should be right now, compatible with mrfred's WB closed loop patch. I dont NEED to use it now, but will later on.