PDA

View Full Version : error messages in megatune. ini file wiped


242Bleek
11-18-2008, 12:18 AM
Im kinda freaking out about this one. I've always driven my car on a pretty decent slightly modified base map. I havent messed with the tunning in forever, so tonight I go out and hook the laptop back up to get things going again I open the MSQ file I have all my settings in then burn the values to the controller. Then right after that very moment all kinda weird stuff started to happen and the car just shut off and wont start back up. I close megatune and re-open it to see a message pop up saying "megatune 029q file doesnt match the controller terminate megatune now?" if you click no megatune comes up with all kinda absurd readings on the gauges like 1290739730% duty cycle and all kinda alien looking writing at the top of the browser bar. How should I go about fixing this? How would I get back to try and reflash the ini. file? btw its MSnS-e v2.2

linuxman51
11-18-2008, 09:32 AM
you have to reload the firmware. sounds like you either grabbed the wrong version of megatune and blitzed the map, or something wierd happened when you loaded the new map (which happens). I'd reload the firmware and try things again.

242Bleek
11-18-2008, 10:41 PM
you have to reload the firmware. sounds like you either grabbed the wrong version of megatune and blitzed the map, or something wierd happened when you loaded the new map (which happens). I'd reload the firmware and try things again.

So are you saying I should just reflash the the mt program? I tried that once but it changed nothing. Do I need to go into my laptop and just delete everything MS related and start from scratch? To what extreme do I go to?


Here is the message I get upon opening mt
5530

linuxman51
11-18-2008, 11:23 PM
yeah sounds like you need to reload the firmware.

which doesn't involve deleting anything on your laptop. you need the .s19 file for 29q, you'll want to unhook your injectors and coil(s) prior to flashing, etc.

242Bleek
11-19-2008, 12:07 AM
Ok thanks king kenny! Will do.

Matt Cramer
11-19-2008, 11:07 AM
Also, make sure you have it set for the right COM port. If it is reading a diagnostic port that echos back every symbol you send it, you'll get the message you posted there.

242Bleek
11-19-2008, 01:45 PM
Also, make sure you have it set for the right COM port. If it is reading a diagnostic port that echos back every symbol you send it, you'll get the message you posted there.

Well im using my second usb to serial port adapter and it reads success on com 4 sometimes, but then again it doesnt work half the time anyway so I really cant pinpoint the exact problem. It might just be this new adapter...Cheap ebay garbage!

BabyBlue240
11-19-2008, 02:16 PM
And be sure to run the corresponding copyini file after flashing the firmware.

242Bleek
11-20-2008, 09:23 AM
Well, after several unsuccessful reflashes of every variant of 029 at least 30 times I still get nothing and the ms still wont turn on. I am using the boot jumper. If anyones has anymore ideas or possible solutions please chime in. Thanks

Nick
11-20-2008, 09:38 AM
What are you using to download the files?

When mine did a similar antic, I ended up using the seperate download software (not the cmd-style program that comes with the firmware package). Iirc, I used this:

http://www.megamanual.com/files/software/ms2dl200_setup.exe

and it worked. Give it a shot.

BabyBlue240
11-20-2008, 09:58 AM
so you mean it won't even reflash the code or MT is still giving you the same message? Have you read this?

If the INI file does not correspond to the code you have load, MegaTune will generate an error message when starting. The error you see is telling you that the signature in the INI doesn't match what MegaTune is receiving from MegaSquirt. This can be for a number of reasons, the most common are:

* you have no communications at all (testing at the serial stage should have verified that you do have communications, but you might not have set the right com port or speed - 115200 for MS-II). A 'Received: 0x53' likely means a comm error is sending back an "S" (0x53) as the first character

http://www.megamanual.com/mt31.htm

Maybe someone else can chime in on why the S gets in there. Have you checked your comm port settings in device manager and MT? I'd go to the page on installing MS firmware and read through it all just to make sure you aren't forgetting something easy. Hope it works out man, I wanna see this beast this weekend.

Matt Cramer
11-20-2008, 12:12 PM
Try powering up the Megasquirt, and with MegaTune closed, run PortCheck.exe. Then post a screen shot of that here. This will help narrow things down.

242Bleek
11-20-2008, 08:19 PM
What are you using to download the files?

When mine did a similar antic, I ended up using the seperate download software (not the cmd-style program that comes with the firmware package). Iirc, I used this:

http://www.megamanual.com/files/software/ms2dl200_setup.exe

and it worked. Give it a shot.

I just tried it. Seems to be for MS2 and it wouldnt do dick for me. But thanks anyway

so you mean it won't even reflash the code or MT is still giving you the same message? Have you read this?


No it lets me reflash it, but all I get is..."download failed. expected boot but got &^%^*fgfd" so none of them are ever successful. I know man, I want you guys to see it even more.

Try powering up the Megasquirt, and with MegaTune closed, run PortCheck.exe. Then post a screen shot of that here. This will help narrow things down.

Trying this but how exactly do you open port checker? It gives me the option on MTcfg but no way to really open it.

Matt Cramer
11-21-2008, 01:20 PM
It's just a little EXE file. If you need a copy of it, get it here:

http://www.diyautotune.com/downloads/tuning_software/portCheck.zip

242Bleek
11-24-2008, 10:50 PM
Well, im still struggleing with this. I even bought a good usb-serial port adapter from DIY auto tune and ran portchecker. COM 3 is open and good, but every time I attempt to reflash it I get this message every single time without fail..
http://img355.imageshack.us/img355/8658/errorzt0.jpg
Its rediculous, its like whatever I do doesnt even make a difference for anything. Also, does anyone know exactly what 0X53 means? Thats what it says my controller has on it.

242Bleek
11-24-2008, 11:24 PM
Im willing to try anything at this point because nothing has worked so far and I need my car back. Any ideas are welcome

mikes02ls1
11-25-2008, 12:08 AM
You try a different laptop?

Matt Cramer
11-25-2008, 11:26 AM
What happens when you try the port check program?

242Bleek
11-25-2008, 01:08 PM
It just came up as COM 3 available 9600 baud or something. I'll get a pic of the screen tonight.

242Bleek
11-27-2008, 06:31 PM
Ahhhhhh, it runs!!! I just had to do some further installation of the new USB/serial adapter, which opened COM 6 and allowed me to reflash it. So from there I just went into MT, loaded my previous project and burned the values to the controller and whalllaaa! She fires up and MT works flawlessly. Thanks so much for the help everyone, I really appreciate it.

BabyBlue240
11-27-2008, 09:54 PM
good to hear.