My SES light came on last night so I decided to hook my laptop to the car using autoenginuity software. It came up with the following codes.

p0300 which I know is random misfire.
p0152 bank 2 sensor 1 heater voltage high

p168e manufacturer specific
B0282 manufacturer specific
U2b0d manufacturer specific.

So I have 2 questions... First one is whether or not these codes really exist or is autoenginuity just a waste of money.

Second question is regarding the p0300 code. I recently had my engine swapped due to oil burning issues (under warranty) A few weeks after the swap I had my battery and e-brake lights flash at me at high RPM's. a few days after that the flashing batter/ebrake light got to the point where they were flashing so fast it was like they were on full time. I took it back to the dealer and they said the plastic alternator connector had come loose so they just pushed the 2 halves back together. I thought everything was fine. Now I am getting the misfire code. Obviously the alternator connection was intermittent after the swap. Is it possible that this could have caused damage to the coils and therefore the p0300 code pops up? Or just a coincidence? I have to see the dealer about this so I don't want to look like a fool if I blame the impending bad coil on their mistake of not connecting the alternator properly

 

Are you actually getting a misfire though? If you are getting one with any regularity or for any length of time you should be able to hear it and feel it. If your O2 sensor is gone and the AFR went wonky as a result, even temporarily, it could have tripped that code. Did you do a power balance test on the coils?

As for the bottom 3 codes, they aren't reading properly because you don't have the enhanced Nissan add-on. (they might be unconverted from hexidecimal)

 

actually I DO have the enhanced nissan addon as well. I even updated the software a few weeks ago. I don't know if I am getting misfire or not. I don't feel anything different. Maybe at low idle it feels a bit rough sometimes. The first time I got the code the alternator connector wasn't plugged in right so I didn't think much of it. My SES light came on wednesday night, it was on Thursday morning on the way to work, then it was off on the way home thursday night. The o2 sensor that is throwing the code is simulated.

 

Ohh... well that's a little different then, didn't know the o2 was simulated or you had the enhanced interface. Maybe there's still something they didn't program in, even on the enhanced... Contact AE maybe and see what they say?

If it's not misfiring (I think you'd know if it was) and the light went off I'd just see what happens in the next few days...

 

I'm going to upgrade the software again. Looks like they put out a new edition in the last 2 or 3 days. I'll re-read the codes and see what happens.

 

ok, I did the upgrade, it was a PITA but I finally got it. the strange codes are no longer there. Just the p0300 and p0152. Hope I have this correct because the secondaries are simulated because of the headers. I wonder if I have a loose connection there because that one seems to come and go.