JAMIE - Can you share with us the base binaries and XML files you are using successfully for 96534706 and 94172715? (Tables cleaned up because we have no interest in your personal intellectual property). I will compare (filediff) them with the binaries we are all downloading and trying to use unsuccessfully from post #1.

This will hopefully help us to pinpoint the root cause of our multiple failures.

 

Thanks for posting this. Now that your experience correlates with my own I feel better because it now makes sense. We still don't have the answer though......

BTW - 3D SD (96534706) should not inherit any XML from 2D SD (96531706), only from the base ROM (96530706). This explains why you have a 2D table (SD MAP Sensor VE and Calibration) appearing in your 3D ROM in one of your earlier screen shots.

 

+1 I'm pretty positive it's something in the 9417 2D and/or 2.0 3D bin. My 9417 Maf works great and there's not much to the XML in 2.0. I may have said this before, but the 2D 9417 has the exact same problem as the 2.0.

 

Ah, great! I think I'm too smart for my own good. I know I was changing XML's around, but I think I forgot what all I did. I may try it the right way tomorrow.

I'm just having so much fun with the 9653 2D ROM.

 

Sorry, that's something I have spent years custom tailoring and building myself and I am keeping my XML's for myself. Any other pro tuner will say the same. its a LOT of research and work to build up your personal settings. As much as I like to contribute to the community, that's throwing all of my hard work to stay ahead of the competition away. Everything you need is in the downloadable versions in the V7 thread.

I'm the one who actually revised the XML file layouts you see in post 2 in the V7 thread and removed the dependance of the evo7base file. I also added the small descriptions in parenthesis to a lot of parameters too so people didnt need to ask what that setting controlled.



I worked with whoever posted up the prepatched roms back then. I have since revised them again for my own tuning tastes, as any of you can do as well.

-Jamie

 

And you are a horrible person for it.

I'm starting to get into the XML editing and I would recommend everyone doing this kind of tuning should familiarize themselves. Even if it's just renaming some of the table titles and how things are organized, you could get your key editing elements doubled up to and displaying at a single table in the top,.

 

I tried the 96534706. I got it idling and cruising. It was pretty lean though. I scaled my FIC 1100 Hz injectors all the way down to 609 after being at 713 on the 2D. I was still lean at 609. I raised VE and it helped a little, but not enough. It seems that there is something else wrong, but I think I'm done with this one.

I tried 94172715 and it does the same as the 9417 2D, starts right up, but no matter what I do it goes extremely lean when giving any throttle and misfires/dies.

I'm a little sad because I feel like I'm giving up on something that others had success with. I am having a lot of success with the 9653 2D ROM as well as all the MAF ROMs.

 

Just finished trying donner's 96536706 3D SD Livemap ROM. It ran badly after scaling my injectors down 20% from 770 to 626 (on E85). Like the other 3D SD ROMS i've tried (96534706 and 94172715), I couldn't figure out how to make it add fuel fast enough during tip in and transition into boost. I double checked and kPa, Load and Airflow Hz seemed closer to where I expected on this ROM when compared to the MAF tune used to compile my 3D VE table.

After trying and failing to get any of the 3D SD ROM's to run past tip in and into boost, I suspect there is either a fundamental setup mistake that we are all making, or a common bug in the SD ROM XMLs or IPW calculation subroutine.

I'm sorry to say that I'm giving up on 3D VE at this time.

Carl

 

Come on, guys. I dont want to mess everything in that rom and than guess why it dindt work for me too...

 

What map sensor are you running? I had the same issue where the car would go really lean at tip in and then was fine once into full boost. I had to right click on a few tables in ECUflash and change the scalings to the proper sensor since I was used to using a certain sensor.

 

Yep, this is my experience too so it's looking more like there's an issue with this ROM's airflow/load calculation. What MAP sensors are you guys using? Maybe it's time for SD 3.0... I'm very familiar with true VE based SD systems and how they should work, but unfortunately I'm not nearly versed enough in ROM disassembly to attempt to build one myself. However, if this was to be redone, here's my list of what I consider requirements:

-MAP voltage vs kPa for fool-proof MAP sensor setup
-engine displacement input (rescales load for displacement change)
-kPa to load table
-3D VE in actual kPa vs RPM
-charge temp blend based on airflow (sets IAT vs. CLT dependency for temperature portion of airflow calculation)


Beau

 

I have done countless 9417 and 8859 3D SD tunes with no issue. I'm leaning towards setup error and tuning technique. If this was so common, hundreds of people would be having these issues.

-Jamie

 

The posts above (including mine) are 9653. Also, I was able to get the car to run normally after significant (and incorrect) alteration of values such as injector scaling, abnormally high VE values, etc. This is not how a VE system should be tuned. Injector scaling should be realistic, actual AFR should match target AFR dead on at all loads/RPM, and VE values very rarely hit over 100 on our vehicles. I was able to accomplish all of these things on the 2D SD ROM, hence why I'll be sticking with that. Typical idle VE will be 45-60 depending on cams etc, and peak torque VE will range from 95-105. Anything out of that range would be considered incorrect and just a bandaid for an improperly designed SD implementation.

Beau

 

My bad, I misread it as problems switching to 9417 from 9653.

 

I'm using Omni 4 Bar.

I've never used another SD system, but I'm looking forward to trying one. Is AEM's a true SD?