
Originally Posted by
lockner13
Got it running! Let me explain this for the others in this post!
SO everyone read the following quote from Evan.s@hptuners
"It's definitely not trying to use the SD tables, it's still in MAF mode. I believe the flex fuel tables are what is messing with it somehow, the OEM tables get overriden to the "Flex Fuel -> Low Ethanol Content" Tables. I.e. making a change to your cranking fuel tables, injector scalar, boost, or lambda/AFR tables will do nothing, you have to make the change in the low ethanol content tables. Try using those to fix your issue, if you don't want flex and it's still bothering you I can remove the feature and investigate further what's going on. This hasn't been an issue on the test vehicle, which like i said runs the exact same file as yours"
Now, with that being said about scalar and cranking ipw being overwritten, IN ORDER TO GET THE CAR TO START AND RUN DO THE FOLLOWING!
REGARDLESS of flex sensor and accompanying parts being installed, YOU MUST ENABLE FLEX FUEL in the map to get the car to start because as stated above, the oem maps have been overwritten and if flex is disabled, the car has NO injector scalar, cranking ipw, boost, or lambda/afr tables to reference and doesnt know how to go about things properly.
I do not currently have flex fuel parts installed on my car so I didnt see why I would need to enable the flex maps, but after reading the reply, I rrealized that it will have to be enabled for the ecu to even know how to run the car. Now, will this completely fix the issue for tuning the car while not actually using flex? That im not sure yet, but will report back.
Evan, Please let me know your thoughts here!
Thanks,
Ben