Low map kpa vs baro - 9093 miata base tune
 

Hey everyone, new to this forum (not miatas or cars) and megasquirt. Was wondering if someone could point me in the right direction. I recently installed MSPNP2, Aem wideband, and a Gm Iat sensor in place of my Afm into my 92.
Do not have an IACV, deleted it over a year ago without problems. I double checked my connections (power, ground, iat wires, vac line from fpr, etc). I loaded tunerstudio, downloaded base map for 90-93, matched firmware, calibrated therm table for iat, synced wideband and set timing to 10 advance. Have been reading on and off over last few days about anything else I could have done wrong or skipped. Car will only run a couple seconds then dies, sometimes a little longer if accelerator is played with. Afr gauge goes up while shutting off, smells like gas, and pops/gurgles through intake when it dies. Pulled plugs and are wet also. Attempted to lower crank pulse and ve table just in hopes to react, but nothing.
Is there anything else I am missing or could be causing an overly rich mix and shutting off engine? Anyone with 90-93 settings? Thanks in advnace...

you need to tune the car.
and no, I'm not joking or trolling.

Ya, I understand that. And that each car, even with same parts can react different. But shouldn't the base map get it close, or able to idle somewhat. Don't get how it can be that far off

Vacuum leak...

/\ that's what it sounds like

Alright, will check over vacuum lines when i home. Thanks

Checked vacuum lines from fpr tee and going to ms. Didn't find a leak. I did however found that if I unplugged ms vac line, that the car is responding the same way. Maybe it's not reading speed density correctly?

If you pull the vac line and have no change to the engine then you just have a hella big leak.

What at does your data log show for vacuum at idle?

Check if you have the right MAP Sensor calibration, also.

Im now thinking it is map related. Spent the night with a friend trying to adjust tables, and also timing is spot on. Car will idle ok, really rich when the vac line to ms is disconnected from the tee and just have an open port. But as soon as I connect that hose, barely runs and super lean.

Attach a data log and your tune... Otherwise we would be guessing..

Is difficult to keep it running long enough for a log.
My map is reading around 55kpa, while baro is at 105kpa while engine off. Reading that they should be close to the same. Am just above sea level. What map sensor would be used for a mspnp2 90-93 miata? Ive tried all sensor options, none of them match kpa to baro. Also read that it can need a firmware file to give me correct option?

Mspnp2 should have the 4 bar sensor right? I dont have the option in calibration. Running 3.4.2, with 3.3.1 9093 base tune

Alright guys, I Really need some insight. I know you want a log, but cant keep it idling for more than a few seconds unless map hose is disconnected. I am convinced it is MAP related. I have confirmed it is MPXH6400 sensor. When I calibrate, my map kpa reads 70, while baro read around 100. What else could cause low MAP kpa reading? Have tried both 3.3.3 and 3.4.2 flash. Any possibility non matching file signatures could cause this when loading the 9093 base miata tune? Have tps disconnected and baro correction to 0. Please, I can try and advice right now. Have some time off. Thanks

Tried blowing/sucking into the MAP line with tunerstudio open and watching the MAP gauge in MS? That's the simplest way to verify your map line doesn't have a hole/kink in it.

Another thought - the MSPNP case, iirc, has a short piece of tubing that goes to the outside of the case/fitting. Might want to verify that's intact.

I have tired pushing/sucking are through hose and confirmed that reading changes. Also just today open up ecu to check hose is intact, not cut, and to see what map sensor is in it.

Here is my MSQ by the way

Under calibrate map/baro use same sensors under MAP and Baro.

I have tried that. Why would that affect what my map kpa is reading?
I have read that altering inc files, or having incorrect files, could have effect? Is it possible mismatch signatures cause this?

This'll sound totally random - what does megasquirt say your voltage is at?