Page 1 of 1

Which version of the embedded code?

Posted: Wed Sep 14, 2011 1:16 am
by mini23
Hi

Purchased my megasquirt unit some years ago and after initial failed attempts to get it up and running I gave up and stored it in the back of a cupboard.

No I wish to try again.
Firstly I have ordered and recieved a stim from DIY auto tune ( :evil: import duty), thinking this will make it easier to getting started.

The PCB has printed on it Megasquirt V3.0 and the text below is taken from the Configuring MegaSquirt II files.

The question is- how do I know what embedded code i'm running?


Start up the MT Configurator (mtCfg.exe), which opens automatically during the installation process (it can be opened directly from the MegaTune folder at any later time). Open the MegaTune2.25bxxx tree item, and you'll see a number of megasquirt-II.ini.N.N files. Pick the one where N.N matches the version of embedded code you are running, highlight the .ini file version that you wish to use and execute File -> Activate.

Re: Which version of the embedded code?

Posted: Wed Sep 14, 2011 4:36 am
by Matt Cramer
When in doubt, ask the MegaSquirt itself. To do this check, you'll need the Port Check program, which comes with most MegaTune versions, including the one on the DIYAutoTune.com website. You'll find it in the MegaTune2.25 folder. If you don't have a copy, download it here:

http://www.DIYAutoTune.com/downloads/tu ... tCheck.zip

Power up the Megasquirt and connect it to your PC. You do not need to open the case and should not put the boot jumper in place for this test. Close MegaTune if it's running, and run the port check program. When this program starts, it will scan the available COM ports.

If the port it's scanning is not connected to a working Megasquirt, or it's on the wrong speed, it'll say "No connection made." If it's on the right port and right speed, it will give you the version of the Megasquirt firmware that's on the Megasquirt. Note that some Megasquirt firmware versions will look like earlier versions with this test - for example, 029V identifies it as 029Q. This is for backwards compatibility.

If you get a port where it replies with "S" or something else that doesn't look like a firmware version, this port is probably a fake COM port that echos back everything that's typed.