aseer

Hello,
I have a MSPNP9093 (with the cap upgrade) and 550 injectors. I loaded the HiRes 10g code last week and everything seemed fine (idles well). I loaded my prior base maps and settings and did some short street tuning runs and everything felt good and looked fine on the MLV, at least to me (and I ran the VE analyzer to do some minor tweeks). I drove the car about 60 miles and then did another logged run and noticed what felt like hiccups at boost. The log shows that I am now going lean at higher boost where last week everything seemed fine. I did multiple runs today and yesterday and see the same thing (say around 155kpa and above).
I am new to the MS platform and cannot figure out what might have changed between last week and today (I hope it is something simple).
I truncated two sample logs that show the difference, if anyone cares to take a look I would be curious to hear what you think?
(the car has the base spark map for the MSPNP9093 except around idle and the VE tables are only street tuned using the MLV; dyno tuning is supposed to be this week but I would like to know if something is wrong before I head to the dyno).
The first log is what I call the "normal" one and the second is the "lean" one (the "lean" one is a little long but if you jump to the end you will see what I mean). I truncated the logs for ease of viewing but if a longer log helps, just let me know.

Thanks.

Braineack

iTrader: (62)

the highres code normally leans out a previous good map on 029v.

aseer

Thanks for responding.

In this case both logs are taken with the hi res code. (I assume there is not a settling period or anything along those lines)

Braineack

iTrader: (62)

clueless. way lean now. fuel pump failing?

cjernigan

iTrader: (13)

There is no settling period. If you're running leaner then something must be difference. I can't look at your logs now but are your IATs substantially higher? Could a weak fuel pump cause this as well, I don't see why it wouldn't cause issues if it can't keep up with your fueling needs due to age/wear.
Something is different for it to go lean and unless you're trying to tune while the engine temp is changing then there shouldn't be problems. It's possible that you're getting into cells that have not been tuned yet. Look at your fuel table and do some hand smoothing to fix any large jumps that might be present. If you don't hit a cell in a datalog then MLV can't tune for it.

aseer

The cells that are now going lean were sampled in the prior runs and looked good (using hires code). I will take a look at other variables that may be different but nothing jumped out at me (the temperatures were similar for the bulk of each run). The logs look like night and day to me.
I have records on this car going back to 1993 when I bought it (it is a a 91) I'll check to see when/if the fuel pump was changed (I think when the turbo went in the pump was swapped).

Thanks again and if there is anything else I should check or information I can provide that will help narrow the possibilities of what might be causing the latest logs, please let me know.

If more details about the car's set up might help, here are a few more line items:
• MSPNP9093 (DIYAutotune) (MapDaddy MAP sensor, IAT kit, HiRes code)
• FM1 turbo package
• FM updated turbo housing outlet.
• FM hybrid downpipe w/ 1.8 hiflow cat
• Custom exhaust (dual, magnaflow muffler, custom install).
• Racing Beat aluminum flywheel
• FM dual Spal fan kit.
• Mobile 1 & Redline
• RC Eng 550 injectors
• Knocksense
• FM fuel rail
• Innovate LC-1 wideband O2 sensor and blue gauge kit.
• AutoMeter SportComp boost gauge.
• FM Aluminum Race Radiator. (Samco silicon radiator hoses)
• Hose Techniques silicon vacuum hose kit

Braineack

iTrader: (62)

here chad:

aseer

Thanks for posting that (I just noted the Compare feature). I was going to note that at the end of the "lean" log I am seeing AFR's of around 17 where on the "normal" run it was about 12 (this at about 170kpa). Increasing monotonically with MAT and RPM's (where on the "normal" log the AFR seems to stay relatively flat.
You guys have a much better feel than I do for how the logs should look, I appreciate you taking a look.

I will have the car checked out tomorrow hopefully if I can get squeezed in (as I was about to drive 500 miles to get it dyno tuned and if there is an issue, I need to get it resolved).

Dave

FoundSoul

iTrader: (5)

As the HiRes code was never released with the MM9093 MSPNP (though it can work just fine, we just didn't release it that way so you'll need to make sure you set it up right) -- do you have it easythermed properly for use with the IAT sensor we provided and the stock CLT sensor? The values we used can be found in the .inc files that are a part of the MM9093 MegaTune package.

Also-- where is your IAT sensor located?

This isn't normal behavior, something is either installed or configured out of whack here... let's figure it out before something bad happens!

aseer

Hi Jerry,


I started with the files/installation provided with your 02/12/08 installation .exe.
I then just used the process listed here:
http://ozmx5.com/viewtopic.php?f=4&t=19 (I did not easytherm it since those settings seemed to be included). Using the 9093 (No AFM 10G files). The sensor is at the TB input (same as in the manual).

I then loaded the stock MSPNP9093 .msq and adjusted the settings by hand for my configuration (my prior VE maps, my MAP sensor, my idle settings).
I then took some logs and did some adjustments using the VE analyzer. (the adjustments were not large)
The car ran GREAT at first (the "normal" log was taken on that same code, >10psi boost with no issue, the car hauled a$$).
Is it possible that something got corrupted, is there a way to tell?
Dave
(I am going to give the car a going over as well and check to see that nothing is now hanging loose) I have longer logs as well if that might be useful.

Ben

iTrader: (33)

Max MAT 215°F?

aseer

There seem to be communication glitches in the log. I assumed the odd max values were due to that. (I also assumed that was a separate issue but you guys are the experts)

Ben

iTrader: (33)

I'd be pretty concerned about what happens at 310 seconds. Don't know if you have a wiring issue, or if it's internal, or what.

Matt Cramer

This is a communications error and not an ECU issue. I've gone over the "spikes" with aseer before, it seems like a minor computer hiccup.

FoundSoul

iTrader: (5)

I haven't taken a look at those files just yet though I can. But even if they're right it's difficult to say if they are all in place right (both the firmware flashed properly and the .inc files placed properly). If the IAT sensor calibration is off at all then you can get wildly different AFR's in the same load cells with different intake temps. It's easy to simulate on the dyno if you've got this going on... do some steady state loading in a particular cell with the hood open and a big fan on and datalog it, that's your low IAT reading. Then close the hood and repeat the same exact test. That's your high IAT reading. If you're seeing wild AFR variation in the same cell (RPM and MAP) with IAT being the only difference then the IAT calibration is likely the issue.

Here are the readings we used:

IAT Sensor:
; Input Data: Temp, degF Resistance
; 48 7000
; 87 1930
; 146 560


CLT Sensor:
; Input Data: Temp, degF Resistance
; -4 16150
; 104 1150
; 176 330


You can compare the values to what your easythermed values currently are in your projects \mtcfg\ folder in the matfactor.inc and thermfactor.inc right at the top of the files. That is 'assuming' the .inc files you're using match the calibration in the firmware you loaded.

Braineack

iTrader: (62)

Smart thinking, I was going to suggest a change in the AIT corrections, but that wouldn't make sense; an improper resistance curve does.

aseer

Ok, I have some work to do. (I thought my runs were at similar temperatures, or close to each other but I can check the values you suggested). I did pull the CLT sensor at the back of the engine block and put it in very hot water and then did a side by side with a calibrated temperature probe. Those numbers were very closely matched (what the MSPNP read and the probe).
I'll switch over and start checking the IAT and CLT settings you suggested.

(The process for loading the 10G HiRes code that used the 9093 settings seemed very simple but I could have missed something)

And again, thank you to all who took a look.

(btw, the idle with the HiRes code is great on my car, I really like the improvement)

Braineack

iTrader: (62)

there's a chance you could have flashed one file and didn't overwrite the file your CPU reads off. so you'd see the same exact scale on your laptop but the MS would be reading a way different value.

aseer

I am definitely new enough to this platform to miss something. I just followed these steps line by line (except for not using Easytherm since the values were supposedly correct for my 9093 with the GMIAT), it seemed very easy and at first everything seemed to work great.
http://ozmx5.com/viewtopic.php?f=4&t=13

I will go through the temperature settings and learn EasyTherm (once it finishes installing).

Braineack

iTrader: (62)

it's possible you flashed the "with afm" file, which would be the only cause of this. or if sabotuer created the images incorrectly.