pgmfi.org

After some issues which I thought may have been my fuel pump, I decided to re-tune my car. The car would go super lean while cruising on the freeway...so lean that the car would surge and become unstable. (i cruise around 3k rpm at about 65 or 70mph) I've been on the same tune for a really long time, so I figured it was something mechanical. So, I replaced the stock fuel pump with a walbro 255lph one, but that didn't fix my issues...it actually made them worse (obviously)

So, it was time to upgrade TE and re-tune...Im running all the new turboEdit software, using the new ng_63 rom, and the new ecuControl plugin with a ostrich chip emulator, and HULOG data cable. I've been out tuning for 3 nights in a row (about an hour each night)...and each time I start the next day, its like my changes/time did nothing. I don't get it! As I'm dataloggging, I allow ecuControl to adjust the fuel tables after some 3rd gear pulls to get the fuel levels in the ball park. I later finesse them myself a bit, seeing what the recommended adjustment ecuControl says, and kinda figure what to add/subtract, and try again. This is mainly to overcome the errors that the ecuControl plug in cant do (like record in the -3hg col...it still does not map trace that column!)

When I'm satisfied with the AFRs, and the car is running fairly well, I'll save the map, then turn the o2 sensor back on in the rom options (off in boost of curse) to let the ecu handle the rest, then save THAT map. (so there's 2 copies, one with the o2 off, and one with it on) Then, to make sure that the ostrich syncs up my latest changes, I'll re-sync the rom with ostrich via RTP. (older version of TE made me feel this was a nesc step to make sure all the changes were saved in the ostrich) turn the car off, then restart to make sure it worked.

However, no matter what, the car does not run right...no matter if the o2 sensor is on or off...no changes stick! The car that was behaving nicely, and pulling hard the night before is now stumbling and struggling to stay on! I've used turboEdit for years now, but I've never had an issue like this. I go super rich to the point where i stall the car when trying to start in first gear under a decent load (like going up a small hill), or the car fluctuates from running lean to rich when cursing. (this is with the o2 sensor on)

I'm pretty frustrated, so I'm looking for advice. Has anyone had any issues with the o2 sensor adjustments with the new NG_63 rom? Any other issues? Maybe you guys can give some pointers with my tuning technique?

tl;dr
TE is acting up, and pissing me off, my 3 nights worth of tuning didn't help...maybe its user error, but I need some kind of guidance.

hmmm... when your finished tuning try reconnecting to the emulator then get the rom off the ostrich...compare it to the base (beginning) rom and the tuned (final) rom and make sure that it jives with the tuned rom.

i havent had my o2 sensor enabled in years...last time i tried it i was getting some swings in the afr and thought the sensor might just be going bad.

the -3hg col not logging isn't an ecucontrol error, its actually because of the way the remap tables on the rom were written. we can fix this, i just chose not to for now because it would cause everyone to have to retune.

what i would do for now:

1. upload your base map to the emulator and save the file as xxxx-(base).
2. start tuning until the car runs better.
3. disconnect from emulator.
4. save that rom as xxxx-(tuned).
5. reconnect and get the rom off the emulator, then save the file as xxxx-(from emulator).

compare and/or post the maps so we can make sure that the tuned and from emulator roms are exactly the same.

which version of TE are you using? 3.2.1 or an alpha test version of 3.2.2? i know for 3.2.2 i changed the way you connect to emulator so you didn't have to upload the rom on connection...this was basically for people who need to connect while the car was running. but the old code should still be there under the drop down menu...it wasn't deleted.

the important thing is to keep all these roms organized...if your tuned sessions from each day are dramatically different then something else may be wrong.

Make sure there is no vacuum leak especially from your map sensor. I had a similar problem that almost made me lose my mind...

Apart from that, I did experience some strange problems with NG63. My tune was going to the right direction to a point... and then all hell breaks loose. It was like the fuel values were all over the place. For me O2 sensor settings didn't do the trick... but manual fuel multiplier changes. I ended up using NG62 code because I had no time to find what was going wrong with NG63.

I think you should try NG62 or even earlier roms in order to see if this is code specific or just a general strange problem that can be caused by mechanical failure. (e.g a vacuum leak or a faulty fuel pressure regulator)

What is the temp change between tuning sessions and when you run it the next day? Have you logged your AFRs and the IAT? Set your ELD offsets? Changed anything with the IAT and ECT fuel correction?