ericsbestshot

iTrader: (2)

Hello,

I have built a diypnp for my 2000 miata. I'm at the point of loading firmware but have yet to be successful. Trying to load MS2EXTRA 3.2.2

I have yet to get higher than 78% of the load. Then it fails with a 0x0 error code and kicks me out. I can try again but it then says I have a connectivity issue. The firmware loader knows which COM to use but will say waiting a few times then fails. I can unplug everything from the diypnp for a few minutes and try again but I still fails.

I have used portcheck and it will pass but if I try it again a couple minutes later it will fail.

Thanks in advance for the help

ericsbestshot

iTrader: (2)

well i think i was able to get firmware loaded. I see the file name in tunerstudio when starting new project. Eventually got a message saying i wasn't connected.

ericsbestshot

iTrader: (2)

Well I actually was not able to get the firmware loaded. I took the microsquirt module to DIYAUTOTUNE and they plugged it into a diypnp they had lying around and had the same issues. They said the module was bad and gave me another one.

I got home soldered it all together and gave the firmware upload a try. No good. Same issue. I made sure the solder joint were good on everything and gave it another try with no luck. But since i reheated the solder joint it seems like the problem is worse. The load is slower and it pauses every 10 seconds or so.

I am dumbfounded on what is going on. I kinda seems like something on the board or connected to it is killing the microsquirt module.

ericsbestshot

iTrader: (2)

Well i'm getting plenty of views but no responses. No one else has a clue?

ManicGTI

Have you posted over on MSextra forums? They were very helpful with me when I had an issue with my DIYPNP adaptor board. My issue was different though.

ericsbestshot

iTrader: (2)

I did post over there. Decent amount of help with my issue. But a few days ago with no reason (that I can think of) the firmware load worked. I'm not having any issues with communication.

Matt Cramer

I was working with Eric - he had set the debug level to 4 and it loaded the firmware correctly. I suspect there was a noise problem of some sort and this setting slowed things down enough to get around the noise issue.

ericsbestshot

iTrader: (2)

It is weird though that i tried level 4 debug before and It didn't help anything.