mspnp2 failure from diyautotune?
11-25-2013, 10:07 AM
#1
Newb
Thread Starter
Join Date: Jul 2013
Posts: 36
Total Cats: 0
mspnp2 failure from diyautotune?
Hey guys finally broke down and got a megasquirt and wow I was blown away how well my car ran even on the base tune. However after 300 miles something went terribly wrong. I set out on a road trip and about 80 miles in, injectors 1 and 3 were stuck wide open. I reloaded the base tune and nothing. A buddy at the shop i hang out at said it might be a injector driver. Diyautotune has been helpful, but has anyone else had a bad pnp? Were they willing to fix the mistake? Anyways I also checked my entire harness for shorts and it runs ok on the stock ecu. Just a little disappointed for 820 dollars... I guess it could happen
with anything. Also on a side note diyautotune needs a phone number haha!
with anything. Also on a side note diyautotune needs a phone number haha!
Reply
0
0
11-25-2013, 10:17 AM
#2
Supporting Vendor
Join Date: Sep 2006
Posts: 2,332
Total Cats: 67
We had a supplier change transistors on us without warning to ones that had a slightly different package size. These could contact the case and short out. As soon as we found out about the problem, we came up with a way to fix it, but a couple slipped out before we realized what's going on. Sounds like you got one from that batch. We can get these repaired and turned around in a few days; it's an easy fix. Sorry for the inconvenience.
Reply
0
0
11-25-2013, 06:33 PM
#3
Newb
Thread Starter
Join Date: Jul 2013
Posts: 36
Total Cats: 0
No problem I appreciate the fast response. I'll test it out of the casing, and keep you guys updated. I've been working with Stephen a little bit on the issue. Can't wait to get off work and be able to drive the miata again!
Reply
0
0
12-13-2013, 01:25 PM
#6
Junior Member
Join Date: Sep 2012
Location: Cranston, RI
Posts: 283
Total Cats: 12
I also had not heard anything from Matt since Monday. I got a response today after leaving a voicemail yesterday. I guess one of the techs was on the road all week and the other was dealing with some urgent issues.
Reply
0
0
07-18-2014, 02:41 PM
#12
Tweaking Enginerd
iTrader: (2)
Join Date: Mar 2013
Location: Boulder, CO
Posts: 1,770
Total Cats: 351
Sorry, should have been more descriptive ....
So basically I came across a situation where the MSPNP worked great when not in the enclosure, but as soon as I buttoned it up the car would behave very strangely. This includes rough idle, rich AFR, poor starting, and operational changes with connections/disconnections of the USB cable. I discovered that we were getting battery voltage into the case, which was creating various shorting paths (through the USB cable for example). This is measurable by using a DMM between any of the connector shells to the GND reference. You will see a non-zero voltage.
The cause is a TO package mounted to the connector panel (presumably for heat dissipation) shorting the TAB connection to the enclosure close to the screw from the connector panel into the extrusion. I simply used a hack-saw to cut the tab back (on a diagonal) such that the tab no longer made contact with the enclosure when closed. The hacksaw fix damaged the insulation pad under the TO package, so I used electrical tape to provide electrical insulation.
It should be noted that I doubt this unit was DOA. It was given to me by a miata buddy who has gone Hydra. I am pretty sure he picked it up pre-owned, so I have to think somebody used it before, with good results.
So if your car starts running super rich, and showing operational changes with USB connect/disconnect events, I would look here first. I do not have a picture handy, but if I were to describe the location; it is on the baro sensor side, MS connector panel (not the car side), last TO package in the bank of 4.
So basically I came across a situation where the MSPNP worked great when not in the enclosure, but as soon as I buttoned it up the car would behave very strangely. This includes rough idle, rich AFR, poor starting, and operational changes with connections/disconnections of the USB cable. I discovered that we were getting battery voltage into the case, which was creating various shorting paths (through the USB cable for example). This is measurable by using a DMM between any of the connector shells to the GND reference. You will see a non-zero voltage.
The cause is a TO package mounted to the connector panel (presumably for heat dissipation) shorting the TAB connection to the enclosure close to the screw from the connector panel into the extrusion. I simply used a hack-saw to cut the tab back (on a diagonal) such that the tab no longer made contact with the enclosure when closed. The hacksaw fix damaged the insulation pad under the TO package, so I used electrical tape to provide electrical insulation.
It should be noted that I doubt this unit was DOA. It was given to me by a miata buddy who has gone Hydra. I am pretty sure he picked it up pre-owned, so I have to think somebody used it before, with good results.
So if your car starts running super rich, and showing operational changes with USB connect/disconnect events, I would look here first. I do not have a picture handy, but if I were to describe the location; it is on the baro sensor side, MS connector panel (not the car side), last TO package in the bank of 4.
Reply
1
1
Thread
Thread Starter
Forum
Replies
Last Post
