Moates adapter causing my no-start condition?

Sy Guy 0024

Member
I"m having a no-start problem now, and I think I have it narrowed down to my Moates adapter. Here's the deal: truck would fire but not run. Was getting no code 12 from the ecm, so switched it out. Still no code 12. So I tried switching out eeproms. Tried 4 different ones, still no change. Pulled the Moates adapter, and inserted just the memcal. Got a code 12. Tried to start truck, truck started and idled with the stock memcal even though I have 50lbers.

So is it safe to assume that something is wrong with my Moates adapter? Has anyone had theirs go bad?

Mine seemed to get hot while I was waiting on the code 12 to flash. Also, I had my WB box sitting on top of the ECM, I think one of the wires might have shorted out against the ECM or perhaps the moates adapter.

What do you think?

Corbin
 

PPI Typhoon

DIY Madman
Re: Moates adapter causing my no-start condition?

Sy Guy 0024 said:
I"m having a no-start problem now, and I think I have it narrowed down to my Moates adapter. Here's the deal: truck would fire but not run. Was getting no code 12 from the ecm, so switched it out. Still no code 12. So I tried switching out eeproms. Tried 4 different ones, still no change. Pulled the Moates adapter, and inserted just the memcal. Got a code 12. Tried to start truck, truck started and idled with the stock memcal even though I have 50lbers.

So is it safe to assume that something is wrong with my Moates adapter? Has anyone had theirs go bad?

Mine seemed to get hot while I was waiting on the code 12 to flash. Also, I had my WB box sitting on top of the ECM, I think one of the wires might have shorted out against the ECM or perhaps the moates adapter.

What do you think?

Corbin

The latest adapter I got from him had a manufacturing defect on it, causing a short, which would not let my truck run either. Are you running the G3?? If so, are you using the EX?

Another board member is having problems with his adapter too (TheJokr), and I'll be looking at that soon too.

Has it EVER run with the moates adapter?? If it has, there's no reason why it would suddenly stop. The adapter is simply a pass through board, so a short could very well cause problems, but it wouldn't be intermittent.

Anyhow, post back what happens.

Also, try burning the stock bin to the EEPROM so that you can test if it's in the programming or in the adapter.

Just a note, the short in my adapter completely killed my ECM, so it wouldn't throw any code 12 either.

Post back and we should be able to figure it out.

Good luck.
 

Sy Guy 0024

Member
I'm using the G1 non-switchable kind with a ZIF socket attached.

My truck has always run fine with the adapter until now. I've been having Nolan tune it for me, so I would burn the chips and run the truck. All was fine until my WB just stopped working. So one day with the truck running, I started jiggling the wires on my WB to see if something was just loose (my WB is in my glovebox on top of my ECM). When I jiggled, the truck stumbled and died. I have not been able to get it to run right since.

Thats what makes me think I might have shorted something. I checked my ECM connections, all the wires are in tite. I even looked in the syty service manual and followed instructions for a "ECM won't flash code 12", and it pointed to either the ECM or memcal. I think I've ruled both out. Unless I'm missing something...

The adapter did get HOT while I was checking things. That can't be right. I hate to buy another adapter and ZIF just to check it out, but I can't think of anything else to try? Can you?
 

PPI Typhoon

DIY Madman
Sy Guy 0024 said:
I'm using the G1 non-switchable kind with a ZIF socket attached.

My truck has always run fine with the adapter until now. I've been having Nolan tune it for me, so I would burn the chips and run the truck. All was fine until my WB just stopped working. So one day with the truck running, I started jiggling the wires on my WB to see if something was just loose (my WB is in my glovebox on top of my ECM). When I jiggled, the truck stumbled and died. I have not been able to get it to run right since.

Thats what makes me think I might have shorted something. I checked my ECM connections, all the wires are in tite. I even looked in the syty service manual and followed instructions for a "ECM won't flash code 12", and it pointed to either the ECM or memcal. I think I've ruled both out. Unless I'm missing something...

The adapter did get HOT while I was checking things. That can't be right. I hate to buy another adapter and ZIF just to check it out, but I can't think of anything else to try? Can you?

Well, there's nothing really on the Moates adapter that can "short out". That's the problem, especially being the G1, which is simply a pass through board. There aren't any components that can go bad.

Keep in mind that the truck can start and idles with NO EEPROM at all.......unless you hit the gas. I learned this a couple years ago when experimenting with my first truck.

I would take one of the EEPROM's you have and burn a stock bin to it. See if that makes any difference.

Being that fact that you shorted out a wire against the ECM.........you might have a damaged ECM. Unlike the adapter, the ECM is easily damaged by shorting out. It's really tough to say at this point. This is really strange too that the adapter is getting hot. Technically, there is nothing on the adapter that can draw current causing it to heat up except the EEPROM, or if a trace was shorted. Check the adapter traces for anything shorted. It's only a 1 layer, 2 side board, so you can see all the traces. A shorted trace can be seen by holding up the adapter to the light and see if you see a physical bridge between two connections. If you have a DVM, you can also check it with that. There's a remote chance if there's enough current in the wire that you said shorted out.....

When that short happened, did you see or hear a spark indicating a high current situation?

Worst case is your ECM............

Also......dumb question.......are your EEPROMs installed correctly?? A backwards EEPROM could very easily cause these problems as well. I doubt that's the case with what you have described so far, but it never hurts to check everything. :)
 
Top