Ok guys, upgraded my MSPNP 2 to Version 3.3 and now it runs like total ****. was running great battery died. had to change the battery. Then AC idle up wouldn't work any more on the variable resister on the board. Talked to Phil and he stated possible corruption with the firmware. SOOOO long story short updated firmware. checked settings in tunerstudio, reconnected the ignitor, fired it up and bam runs like ****. AFR will not change no matter what I do. I'm sure its something I'm missing. but I can't figure out what it could be.

 

First thing to check: Are the CLT, MAT, and MAP readings correct?

 

looks to be. Vac reading seems to be different than the gauge.

my main concern is that the O2 AFR reading doesn't deviate at all. Should I have also unplugged my O2 before updating firmware? is it possible it got burned up? something I'm missing that needs to be reset up?

 

Did it work before?

Did you got to tools > calibrate AFR table and set up your wideband?

 

Yes sir worked before. Was running smooth minus the AC idle up. Before the battery died it has been running smooth.

Phil sent me a message told me to start a new project with the new firmware and load in the msq. I'll try that this after noon and see if that helps or solves it.

 

what firmware did you have before 3.3.3? a lot of settings need to be changed between newer and older firmwares.

 

it was the original firmware from 2012 when I got it. Version 2 something I think. I followed the readme's setting changes. I didnt start a new project. here's to hoping that part helps

BUT if you have some things I need to make sure to check settings wise or anything else please let me know. going to work on it some more this evening.

 

yeah, you need to go through the map section by section to make sure all settings still make sense. i notice a lot of times idle code will get turned off completely, or switch to warmup only or something odd.

 

ok I'll start a new project and double check that section.

should I have unplugged my O2 as well when I did the firmware update? didn't see anything say that. I'm just hoping that it isn't fried and its just an issue with the codes. old project and all.

 

here is the tune settings with a new project as Phil asked for and the data log. you can see that my O2 is getting a reading finally But its still sounds like it isn't hitting right and running like ****.