No beer please i prefer hard liquor

 

depends vodka? scotch? etc... lmao

new question time

ok the tip in crap is driving me insane, whats the drawbacks to going open loop all the time? at this point i am considering it. It's messing up my attempts to rein in the small screwed up parts in vacuum that i have mostly sorted out finally, and it makes driving all screwed up.(going lean then rapidly rich or on target afr = choppy accel)

 

I hate to jump into someone elses thread, but I dont want to start another one when I have similar issues. Ive done my searching and reading and can't find answers so I just need to ask and hope I dont get "use the search button". Plus maybe it will help answer some questions for the Skylineracer as well.

I recently downloaded the 96533706 recommended from Sheides SD thread. Im using this on my evo 8 with an AEM 3.5 map sensor and GM IAT sensor. I transfered all the files into my rommetadata and opened up the file. The first box I get what was shown below. Two table that say RAM and two that dont. The RAM SD RPM tables are identical but the SD VE Kpa is different. One table was almost 1:1 but the other is not even close. Im sure there's a reason that one isn't 1:1 but I dont know why.

So I go through all the psi tables and adjust the sensor to Klavico 3.5. I hit apply and everything seams to be okay (I didnt notice the SD VE table didnt change). So I load the tables, fire the car up and it runs super rich. I shut the car off, turn off my Zeitronix log and reopen ecuflash. I happen to open up a psi table to make sure the scaling still said 3.5 and every table says omni 4 bar. So I opened up the original file and the kpa scalings are identical. They never changed to the 3.5 bar.

So I go ahead and adjust the SD RPM tables down to what you see and got the car to idle at 12.5:1 so I know im heading in the right direction.

Here's what Im looking at after I made my adjustments to the SD RPM table


Here are my questions.
- What is the purpose of the RAM tables and should I adjust both SD RPM tables like I did?
- Did I not load the proper MAP scaling definitions properly so its not changing in the ROM or did I miss a table that needs to be changed?
- Since I can adjust the SD RPM table to make the car richer or leaner and fix the fuel trims, is there no reason to go back into the scaling and latency tables to make adjustments once I know they are within reason?

I hope these arent newby questions that are in every thread I just read through for the past week. A step in the right direction will be helpful! Thank you!

 

The RAM tables are if you are using a DMA/LiveMAP version of the ROM. If you are and have those tables in RAM, then you can use the LiveMAP client to adjust them on the fly. (I don't know if the ROM you have is the DMA/LiveMap ROM or not, so to be safe, just adjust both RAM and SD tables to be the same, and you'll be fine.)

Sounds like you did something wrong. You must use the correct scaling for the map sensor that you are using. Otherwise, the kpa column of your tables won't make any sense...they will be way off from what the kPa really is. If you are using a 3.5 bar sensor, then make sure you set the scaling accordingly and it keeps.

If you are referring to the injector scaling and injector latency, no, there is no reason to adjust those if your trims are good. There are numerous ways to tune your fueling with the SD patch and the VE tables.

 

Black:

Looks like you changed the scaling but neglected to fix the numbers for Map(KPA)

Copy the right hand side (Load%) into the left hand side (kpa) and it shouldn't run as rich. Keep adjusting until its right. There is my recommendations for the vacuum side only 1 or 2 pages back in this thread.

 

roadspike what do u think about just going open loop?

 

Ran that way for a year it works really well especially when your just starting lets you see what you really need to adjust.

 

thats what i am going to work on now cause this stupid async problem is making me go insane lmao.

 

What async tables are you modifying?

 

wtf open loop still = lean in areas where rpm load and map are rich at other times??

 

async vs tps

 

Just tune it out like normal with mapping the AFR and making adjustments in the VE table until its smooth .

Whats happened is you made adjustments but they were being corrected by the o2 sensor and now that its not you can see what your adjustments really did.

 

i am confused though cause when i look at the excel sheet from evoscan kPa rpm and load are roughly the same yet it decides to go from 14 to 19 then to 12 afr?

 

That sounds like tip in am i right is TPS changing at that time?

There is an async rpm adder which has some points completely disabled i think between 1500-2500 rpm increase the values there so async does something.

 

well i found the correct table, u are right like usual there is a async vs rpm table where it was 0 for many cells so i bumped them up to the next highest number in that table which was six, and tada the tip in problem seems gone! VR should verify on their customer cars. also reined in more of the crazy rich boost condition to where it didn't stutter and accelerated under some knocksum cause of the richness?