I am using Evoscan 2.6 and Ecuflash 1.42 with an Openport 2.0
The load factor is 1.2 in both. I am logging Load 1Byte with request ID 41 (but is says gauge max 270 in Evoscan). Are those right?
Thx

 

ok I think I have found the problem. I should log temp+baro compensated load or baro compensated load to look up the timing. I have tried temp+baro and it "goes the other way" so I think I will try baro compensated load and see if it is spot on. The temp here is between 20-25 degrees Celsius so I think that should do it.
Thx I will post my results

 

I have a question about the ISCV tables. For the "AC off" there are two tables (neutral and drive). How does the ECU switch from one to the other - is it based on the clutch switch (clutch in = neutral, clutch out = drive) or the speed sensor (speed zero = neutral, speed > zero = drive) or some combination of both?

 

can anyone help me with the launch timing map?
i lowered the timing in the launch area (launch map) at -15º, go wot, boost raises up to 1.3 bar but when i release the clutch, the engine stalls, like if it's missing a lot of power. Someone told me it was a tuning issue, so, can anyone help me with a map example??

thanks a lot.

 

Car starts and then instantly dies when using 94170715 (v7 + Mods Omni 4 Bar MAP)

Starts and runs fine on my old 94170015 Rom.

Need ideas Please Help?

 

I just did the switch over today on my car and on my second drive (8895017) today was getting a lot of knock flashing. Got home to open up my logs to see afr values that don't exist in my main fuel table. I did some more reserch to find that it looks like the car was pulling off my alt fuel map. This doesn't make any sense, I don't have it even setup or toggled on the tephra mod options to use that feature. Almost my whole log was showing a 14.7afr map value for the whole duration and that would correspond perfectly to the alt map table but not even close to any values in my main fuel table.
Any ideas to why the ecu is pulling from this table instead. I was checking for the same thing in my ign table but that one looks to be pulling from the right table. I've since adjusted alt fuel table to be the same as my main fuel map to avoid lean conditions and to be able to safely drive it.

-rob

 

If you really want to see it reference your main fuel map all the time, you need to make sure you have lean spool disabled, as well as having closed loop disabled.

I believe they can both be disabled in the periphery bits.

 

I'm currently running 94170715 with a 4-bar MAP. email me both ROMs and I'll take a look when I get home this evening.

robbie
(dot)
nelson
a t
gmail
[dot]
com

 

didid u change the scalings for the omni 4 bar map? the scalings in the v7 when I pulled it up were for the jdm map sensor. that was on my rom anyways, might check your scalings. did u copy over your fuel injector batt volt and inj size (if ur not running stock). run through all the map scalings and the other ticks in that section and check them to the omni setup link.

 

Lean spool shows its toggled as disabled already. Is this really wise to follow my map the whole time or are there ways toa djust when it follows and when it doesn't? It doesn't seem like its tunable like it is right now cause its following some other set of tables even under boost. It seems like my previous settings prior to v7 followed my fuel map entirely. I will check settings and keep playing with it to become more familiar with the new settings and options. I'm sure there's a way to adjust when it goes open loop vs closed loop.

Any other ideas I'm looking over?

edit*

compared my open loop throttle response percentages from my old settings to the new V7 and will change accordingly, it takes a lot more for it to kick over in the new v7 map. I can understand for more fuel economy, but not for how I drive!

 

That is why I suggest to everyone to copy all the open loop tables from their old rom over to the V7 rom so it will not change the closed to open loop transition so much...

 

sounds like you figured it out then?

 

yeah thanks for all your help! now I just gotta keep tuning then switch to sd!

 

I'm working on logging AFR thru the rear O2. Instructions say if I'm running tephra V5 or higher Nothing needs to be added to the rom definition. But I can't find the MUT12 address in anywhere. So do I need to add it or am I just not looking in the right place?

 

:0