You know as crazy as this may sound following the desired engine load table as a percentage function of throttle may be "safe".

Another question though Mr. Banks. I have a 5 bar kavlico sensor in my setup if i understand this correctly your SD mod will work as long as the correct settings are put in as per MrFred's log via JDM map thread?

I want to ensure when i give this a shot this coming weekend I have everything in order. I've also seen some results for VE calculations is that just an Evoscan logging variable you guys are adding?

 

I am currently running SD through the ECU with the kavlico 5-bar sensor. Works fine.

 

You can't sensibly use throttle position as a failsafe here since there is not enough correlation between throttle position and airflow during transients on a turbocharged engine to make the failsafe sensitive or specific.

Whatever method you want to use to collect data to calculate VE is fine, the idea is load/MAP(kPa).

 

I know it wouldn't be precise, in fact that why i was comtemplating this as a failsafe/ limp home method. Hopefully the car would run rich enough not to misfire and possibly not make the engine go kaboom.

The idea was something like a very crude alpha-n setup to prevent total catastrophe.

 

Is anyone else having definition problems with 94170015? Ive checked it several times now and everything seems correct but when I open my map in ecuflash the values are all crazy like they would be if the definitions are wrong.

 

It is a nice idea, but try writing down the algorithm of how you would choose the TPS or MAP load source... a simple comparison won't work because to prevent running lean you'd have to use the highest load, then it would choke the engine with fuel during spool up when you have high TPS low MAP. The only way to do it sensibly I can think of or have seen, is to use complex MAF and MAP airflow learning systems, we need more sensors.

 

Sounds like the Big/Little Endian issue. What version of ECUFlash are you using?

 

I am using 1.41 so it should be a big endian right?

 

That's correct. Which values are showing up strange? The ones in the "patch" ROM?

 

All of the tables for sd when I open my map in ecuflash show up as random numbers


they all look like this

2815.....
2815.....
2815....


ect....

 

That doesn't really help me diagnose the issue. I need to know if the SD tables in the SD "patch" ROM that you download from my website are showing random numbers.

 

The stock rom that I downloaded with the patch look correct.

 

ok, you're doing good because that tells me that ECUFlash is reading the tables correctly.

 

Yes the rom That comes with the patch looks good but when I open my rom I get random numbers.

 

Post up a pic of the tables in the "patch" ROM.