Miata Turbo Forum - Boost cars, acquire cats.

Miata Turbo Forum - Boost cars, acquire cats. (https://www.miataturbo.net/)
-   MEGAsquirt (https://www.miataturbo.net/megasquirt-18/)
-   -   So I got my car running on the PNP firmware and it runs like crap! (https://www.miataturbo.net/megasquirt-18/so-i-got-my-car-running-pnp-firmware-runs-like-crap-30191/)

scottv 01-11-2009 10:18 PM

So I got my car running on the PNP firmware and it runs like crap!
 
2 Attachment(s)
I'm thinking there might be an issue with my wideband but the gauge works although it reads lower than what I have in the AFR table at x rpm...and the needle just goes all over the place in Megatune. I drove it and it did ok but I got to a hill and the car would barely make it up-it wouldn't go over about 15mph up the hill-I thought it was going to die. I have searched all over and can't figure this out...do my .msq and logfile look totally jacked?

I have an AEM wideband-grounded at the Megasquirt harness, setup as Linear.

???????????:bang::bang:

patsmx5 01-11-2009 10:32 PM

I looked through the datalog and it looks like shit. Everything it records is in a square wave. You have major noise issues.

Post everything you know about your setup. What you have done, what you have tried. What you have changed/fixed/fucked up/etc.
Does it run on the stock ECU? Did it run fine before MSPNP?
Did you wire everything exactly like you should have?

scottv 01-11-2009 10:57 PM

It ran fine on stock ecu and narrowband. Took out the stock ECU and narrowband and added the Megasquirt-built by Braineak so I figure it's good. Added the AEM wideband, it's running P00, power and ground wired to the same as Megasquirt, signal wire to the o2 wire on the MS harness. AEM gauge reads 10 at idle, will jump around when I press the gas, but the readings don't sync up with what's in my AFR maps. In Megatune, the A/F gauge is all over the place-doesn't stay on any one reading just jumps all over. I loaded the PNP firmware 9495 with MAF. Then put in the PNP msq. Changed the o2 setting in Megatune to wideband. switchpoint to 2.375 Car stock at -10 timing, synced up with Megasquirt.

That's all I've done. drove it and got the results posted. :eek5:

wayne_curr 01-11-2009 11:02 PM


Originally Posted by scottv (Post 352080)
It ran fine on stock ecu and narrowband. Took out the stock ECU and narrowband and added the Megasquirt-built by Braineak so I figure it's good. Added the AEM wideband, it's running P00, power and ground wired to the same as Megasquirt, signal wire to the o2 wire on the MS harness. AEM gauge reads 10 at idle, will jump around when I press the gas, but the readings don't sync up with what's in my AFR maps. In Megatune, the A/F gauge is all over the place-doesn't stay on any one reading just jumps all over. I loaded the PNP firmware 9495 with MAF. Then put in the PNP msq. Changed the o2 setting in Megatune to wideband. switchpoint to 2.375 Car stock at -10 timing, synced up with Megasquirt.

That's all I've done. drove it and got the results posted. :eek5:

By this do you mean that you've also gone into the config file and set MT to use the AEM WB02?

scottv 01-11-2009 11:24 PM


Originally Posted by wayne_curr (Post 352084)
By this do you mean that you've also gone into the config file and set MT to use the AEM WB02?

yes, I changed it in MegaTune configurator, under MSPNP MM9495 with MAF under settings-LAMBDA SENSOR and set it to AEM_LINEAR

scottv 02-01-2009 05:05 PM

damn I still can't get this thing working! Since last posting (when power and ground were wired into the MS harness) - I changed the ground and wired it directly to the battery. After doing this, now the AEM gauge reads 14.7, then "counts down" to 10.0 then flashes between 10.0 and --
So, I then tried grounding to where the ECU is ground in the engine bay-same result.

Then I wired both power and ground of the AEM to the battery and same thing. When I datalogged the wideband reading is all over the place like before and the needle in MT jumps while it's running.

Is it possible the sensor itself is dead? Any guesses on why the gauge would count down like this with the car running? :vash:

The car runs fine on the stock O2 sensor and stock ECU and it ran and passed inspection fine (registration ended in Jan)...so the car is ok otherwise. Appreciate any input!

scottv 02-01-2009 08:39 PM

ok, so I figured out what was wrong-for some reason MS wasn't getting the correct signal from the wideband. Something was wrong with the wire I ran behind the dash from the white wire to MS. When I ran another wire straight from the white wire coming out of the back of the AEM gauge to MS it showed as a constant figure in MT. :bowrofl: ok, now maybe I can get this turbo install going somewhere.

ThePass 02-02-2009 02:48 AM

Can't exactly understand what you mean by the white wire behind the dash and whatnot but I was going to recommend making sure you unplugged the wire going to the stock o2 sensor because if you didn't, the MS would be getting signal from both your stock one and the wideband and although you can select which one to use in MS, you should not have them both connected. Sounds like when you ran the direct wire you may have bypassed the stock wideband and solved the issue. fwiw, there is a little electrical connector by the CAS that is the wire for the stock o2 sensor - you can see one end of it go down behind the motor to the sensor. I unplugged it at this connector.
-Ryan

scottv 02-02-2009 08:00 AM

The white wire is the one going from the AEM gauge/controller to the MS WBO2 input...basically the wire MS gets the WB sensor from. My extension wire was the problem with the signal being all over the place-I'm thinking the wire either got snagged to ground somewhere behind the dash or was just bad. As far as having the stock O2 sensor connected-that might have been what caused the AEM gauge to do the countdown thing I posted about earlier. Initially (in my Jan posts I had it unplugged and the gauge didn't do the countdown)...then after having to run it stock again for inspection I didn't unplug it-didn't think it would be an issue because I'm standalone but guess I was wrong.

Thanks, I think everything is good now! FINALLY! :)


All times are GMT -4. The time now is 03:39 PM.


© 2024 MH Sub I, LLC dba Internet Brands