fuel pump low/high voltage transition table
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
I've figured that the load location is 420E, but I'm still a bit noob with IDA, so haven't figured out how to find the RPM axis location. I could guess, or assume that the RPM axis locations already defined in my xml for other things are correct, but that's just not right!
So I have an Evo 8 here and I always wondered why the car gets stuck in open loop after starting sometimes. Well, I have the rear seat out so I could hear that the fuel pump was at full battery voltage and the AFR was VERY lean in open loop (18-19 AFR).
After a few minutes, the car switched back to low battery voltage at the pump and closed loop operation returned and AFR was back to 14.7 and fuel trims are close to zero.
So I guess the ECT and IAT conditions have something to do with it but it seemed odd that the AFR would be leaner with higher battery voltage but would have perfect fuel trims when closed loop and low battery voltage occured.
Thoughts?
-Jamie
After a few minutes, the car switched back to low battery voltage at the pump and closed loop operation returned and AFR was back to 14.7 and fuel trims are close to zero.
So I guess the ECT and IAT conditions have something to do with it but it seemed odd that the AFR would be leaner with higher battery voltage but would have perfect fuel trims when closed loop and low battery voltage occured.
Thoughts?
-Jamie
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Coolant temp and IAT both have to be pretty high to trip the longer delay to going to low voltage. Those timers could be tied to other algorithms in the ECU. I can look some time.
What else forces the ecu to stay in closed loop after startup besides the TPS and engine load openloop tables? If I cracked the TPS by less than 1%, it immediately goes into closed loop.
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
There are a bunch of factors that go into deciding whether the ECU puts the engine in closed loop. Its way more than the the throttle and load tables.
I've figured that the load location is 420E, but I'm still a bit noob with IDA, so haven't figured out how to find the RPM axis location. I could guess, or assume that the RPM axis locations already defined in my xml for other things are correct, but that's just not right!
Well that's something! Most guys in Oz with 8's run 9626 which is why I was after it.
Maybe mrfred or someone can help sort it for us.
-Acree
So, is there a way to make the ECU ignore the IAT and ECT inputs so that the hi switch isn't thrown upon startup? Only have it thrown when above say 80% throttle and whatever load.
Would be nice to make a dual pump control with this...
Would be nice to make a dual pump control with this...
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
Yes, it can be done, but the low/full voltage switch on the primary pump is needed in order to avoid overrun at idle. Even a Walbro 255 running at full voltage can overrun the fpr at idle.
Yea....I noticed haha. Had my trims within 3%, hardwired the pump, now they are like -10-12 lol. Little tweaking here and there getting it back to normal.
How can we get TPS % incorporated into this, or is that possible? Sorry, I know nothing about disassembly or programming
How can we get TPS % incorporated into this, or is that possible? Sorry, I know nothing about disassembly or programming
bringing this back from the grave, what about for rom ID 88590715 and all the tephra V7 maps?
how come this isn't on there already? do you guys know of a thread compiling all tables not found in V7?
how come this isn't on there already? do you guys know of a thread compiling all tables not found in V7?
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
The 88590015 table also works for 88590715. Its up to you to add it to your definitions.






