Ms3pnp quit communicating with tuner studio

[bpimm]

This morning while trying to clear an output to use for tach out (I think this has been resolved but can't verify until this new problem is solved.) I shut off the boost control, I'm NA, and cycled MS off and on as requested and they stopped communicating. Power indicators on the ms show power is on,

I have tried 2 different computers that have communicated in the past and neither will work,
I even unplugged all the connectors to the ms so it had no power in hopes of it resetting whatever is wrong.

The car has been running a year without any problems, other than tune issues, What happened? and how do I troubleshoot this?

Thanks

[Matt Cramer]

First, try running Port Check with the MSPNP connected and powered up. Please post the results here.

[bpimm]

port check failed, I used mini terminal to run a loop back test and it works with a jumper on the end of the cable that plugs into the MS so I think my port and cable are good.

Learning this com port stuff as I go...

Brian

[Matt Cramer]

Try opening the case, install the boot jumper, and repeat the Port Check test. Does it find an ECU in bootloader mode? If so, try reloading the firmware.

[bpimm]

Where is the boot jumper, I don't see it. is there a board layout that shows it?

[bpimm]

Found it, there is no jumper installed just holes in the board. Are you giving me authority to solder on this board without voiding the warranty?

[Matt Cramer]

Don't solder anything to it - use a paper clip to short the two holes together before powering it up.

[blaqrob]

I recently had this issue. I find it a bit disconcerting that the fw can corrupt under normal use.

Sent from my SM-N900V using Tapatalk

[Matt Cramer]

We've now put together a method of recovering the settings out of an ECU with a "corrupted firmware" problem. Every time we've used this tool, it has turned out the problem came from a settings configuration that wasn't possible, but that the code did not have an error handling feature for - two examples have been an alternator control pin conflict that hadn't been checked for (OK, that was a minor oversight), and setting up a two tooth trigger wheel with two teeth missing (a setting so bizarre it didn't occur to the code team to check for it until we caught an example "in the wild"). And when someone does this, reloading the firmware is a fairly straightforward fix.

[blaqrob]

That is what caused my issue was a decoder wheel setting incident.

Sent from my SM-N900V using Tapatalk

[blaqrob]

In my case it was a 12-1 with a single cam gear tooth and using sequential with cops.

Sent from my SM-N900V using Tapatalk

[blaqrob]

Switched to a 36-1 crank and a cam tooth gear and it was fine.

Sent from my SM-N900V using Tapatalk

[Matt Cramer]

In my case it was a 12-1 with a single cam gear tooth and using sequential with cops.

Sent from my SM-N900V using Tapatalk

That should be supported, for a four or six cylinder engine. Can you post a copy of the MSQ that crashed it?