Go back to previous topic
Forum nameEngine Management Systems & Controllers
Topic subjectMegasquirt technical/programming problem
Topic URLhttp://forums.2gnt.com/dcboard.php?az=show_topic&forum=54&topic_id=4370
4370, Megasquirt technical/programming problem
Posted by kevox, Dec-31-69 06:00 PM
Ok so I'm out of ideas here....my engine is all put back together and should start up fine BUT we can not for the life of us figure out why Megasquirt keeps throwing this error everytime we power it on to try and program it! I don't recall the exact error but it initializes and then on the laptop it shows a bunch of things it sets up but every single time it stops with an error at one particular point. We have had email replies from symtech labs but they have proved less than helpful. We are awaiting an email response from diyautotune hoping they might know something....and here I am asking if any of you guys have run into this kinda problem with MS before? The car has been this close to being done for about 3 weeks now and its killing me just seeing it sit there in the driveway while I take the bus everywhere over a mere technical fault! Please someone direct me....
4373, RE: Megasquirt technical/programming problem
Posted by teklein, Dec-31-69 06:00 PM
I am not too familiar with MS at all, but I moved your post into here, where people who DO know a ton about MS frequent :)

Good luck!
4374, RE: Megasquirt technical/programming problem
Posted by CODE4, Dec-31-69 06:00 PM
What version firmware are you running? What code are you using? MSns Extra? MS1? There are several variants. And depending on what generation board you are using some code requires board mods. Are you MS1? MSII?

At what point does it give you the error? When I initialize Megatune, the only window I get is asking which car/project to select. Then my next screen goes to the gauges.
4377, RE: Megasquirt technical/programming problem
Posted by kevox, Dec-31-69 06:00 PM
Umm I know it is MSII and that it came preassembled from diyautotune so which firmware I have no idea...I'll try and find out the detailed info on which error code it keeps throwing for you soon..
4378, RE: Megasquirt technical/programming problem
Posted by VelocitaPaola, Dec-31-69 06:00 PM
If you're able to open the case, take detailed photographs of the top and bottom of the board and post them here, we may be able to tell you if the hardware is properly configured. Beyond that, it's all software, which is exhaustively documented at http://www.msextra.com/ms2extra/.
4379, RE: Megasquirt technical/programming problem
Posted by kevox, Dec-31-69 06:00 PM
Originally posted by VelocitaPaola
If you're able to open the case, take detailed photographs of the top and bottom of the board and post them here, we may be able to tell you if the hardware is properly configured. Beyond that, it's all software, which is exhaustively documented at http://www.msextra.com/ms2extra/.


I'll try and get pics up for ya - main problem being I do not know where our USB cable for the camera is! We just moved here a little over a week ago so it may not be easy to find...

As for details on the error this is what it says.....
...
reading ms2_extra.s19:
mas2_extra.s19
Detected MS-II (HCS12) code.
Entry point: 0xc000
Code range : 0c4000-0x3db4b0
file read successfully

Opened comm prt 5 at 115200
ERROR: Timed out reading response, 0xE0
4380, RE: Megasquirt technical/programming problem
Posted by VelocitaPaola, Dec-31-69 06:00 PM
That error code is almost always caused by the combination of using a USB-serial converter with MS2 firmware. We occasionally see it, and when we do, we just try loading the firmware over and over until it works. Sometimes we try different boot jumper configurations upon powering up the ECU (i.e. leaving it installed while applying power, or having it initially removed, as the download-firmware.bat instructions seem to suggest); but I don't know if doing this necessarily helps.

My only other suggestion is to move whatever other device you have installed at COM1 to another port. Then upgrade the USB-serial adapter's firmware to the latest version you can find, and set it to COM1.

Good luck!


I generated this page in 0.010627031326294 seconds, executing 7 queries.