signature error ?

[940 T.U.R.B.O]

MS2/ v3 pcb/
I'm at a point in installation, where i was trying to do a simple comms. check between megatune and the MS and it gave me a error message saying that the the controller code (?) was not a match with the signature, and gave the warning how it could cause serious problem with corruption. I have a crappy mouse pad on my laptop so using the keystroke tried to terminate MT and accidentally opened it instead.

I closed megatune immediately, and hit the search trail looking for advice.
I first downloaded the MSDownloader program from the Megamanual link to try to determine the embedded code on the board (i didn't assemble the MS so i didn't know which it was), but it would not connect at all.

then looking back at my notes, that error message it kicked back "Received: 0x51..." which after searching the megamanual made reference to that exact message being a problem with not connecting to the controller at all. I went through schematic with my DMM and all the pins on the DB-9 are good. My usb-to-serial cable has been used to help tune a friends squirted VW, so i don't think its a problem there.

could my accidental openning of MT have corrupted files bad enough to cause a problem like this where I get no comms between the two? or does this sound like a assembly issue with there being no comm? I'm really wishing I would have assembled it myself at this point. I'm looking at buyin a new daughterboard but wanted to check before I did. I'm running out of ideas, and can't really push forward til this is resolved.

Mike (as usual)

[linuxman51]

make sure the ms is on when you try to connect, and then try again.

[Matt Cramer]

The 0x51 error message often pops up if you're on the wrong COM port.

[940 T.U.R.B.O]

I've went through the device manager, and verified the recognized port for the serial-to-usb adapter, and made sure that under the settings menu in MSDownloader, that its on the appropriate com port (Port 7), and its kicks back that "the com port opened succesfully, but that signature unavailable/unverified, possibly not connected" (I'm paraphrasing as I'm at work now not in front of it all) I didn't suspect the serial cable, but maybe I should try a new one.

[940 T.U.R.B.O]

make sure the ms is on when you try to connect, and then try again.

I checked on the board w/a DMM and verified power on the board. Opened Megatune (MT) again and received the same error message. "Received: 0x51" "Expected: MSII Rev 2.88600"

The 0x51 error message often pops up if you're on the wrong COM port.

Is there a way to change the default port that MT looks at for the controller without actually opening MT?
I used the portCheck utility and it found 1 valid port (COM3). With the MSdownloader program, settings corrected to use COM3 @115200 it reads the signature as "Signature: "s" ". Which is default for no connection correct? or am i misreading that in the megamanual?

i would ask if I have the wrong firmware, could just erase/reflash it from the controller and start from scratch, but i'm not even sure I'm connecting to do so.

[Matt Cramer]

It sounds like COM3 is not a real COM port but a fake diagnostic port. You can ignore the message, open MegaTune, and set it to the real port.

[940 T.U.R.B.O]

sorry i didn't remember to respond to this until the alert popped up in my e-mail.

Thats actually exactly what was happening. I also had a issue with my serial-to-usb adapter that is fixed as well. I've got comms now, so i can go ahead and finish wiring.

thanks for the the input though Matt, likewise Kenny.

mike (as usual)