MSefi.com read only forum (Jan.15,2018)

I have a 1985 volvo 740gle running MS2 v3.57 my code revision is 2.88600... i think.

I am using a registered version of tunerstudio to calibrate the ms2. I have not started the car but wave calibrated the tps, coolant and iat. I was having a problem opening the ve tables to set them. i tried to load my tune with megatune 2.25 to see if i could establish ve tables there. i completely saved and shut down tunerstudio before doing this. in megatune i was unable to detect my megasquirt. aditionally when i tried to reconnect via tunerstudio I was unable to communicate. furthermore the fuel pump relay and injectors seem to be cycling on and off continuously. Up until this point i had verified that all wiring was correct. all previous attempts to power on the unit were normal with the prime from the fuel pump and injectors, and all of the sensors were reporting normally. any help would be gratly appreciated. I am stuck.

thanks,
Juan

Juan,

You might want to read the red text in the blue box here: http://www.megamanual.com/ms2/code.htm

Lance.

I had already set my MS type in the general dialog box and have set most of my required fuel parameters. Is there a chance that they did not take? I did communicate with the MS enough to calibrate the tps, iat and clt. I had previously established communication with the MS but I can't now...

Juan

Was it possible that when I tried to open megatune and communicate with MS after using TS that it could wipe out the work that I had done? It would make sense that the fuel pump relay is cycling when it is powered on. my unit is from DIYAutoTune and does not have indicator leds. As it stands now i can't communicate with it. Is there any way for me to force communication. It all worked before i tried opening it with megatune.

i went out to check on it once more, here is what is happening when I boot my tune I get this error message.
1 Warnings:
Warning: Constants entry missing comma after ], but corrected., Problem at:
[mainController.ini]:[Line:247]: DualSpkOptn = bits , U08, 601, [0:3] "No Dual Spark", "Dual Tach Inputs", "Falling Cam Sync with Tach or Wheel", "Rising Cam Sync with Tach or Wheel", "Single Crank Wheel Input", "Single Cam Wheel Input", "Dual Inputs, Timing from 1 cam tooth", "M-0 Wheel w/ Falling Crank Sync", "M-0 Wheel w/ Rising Crank Sync", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID", "INVALID" ; * (1 byte)

When powered up the MS is cycling only one bank of injectors at the same rate as both the fuel pump and iac (which has been wired as a fan control through a relay)

no communication still.

gezpacho,

Your code may be corrupt. If this was mine, I would re-load the code using the downloader. But I wouldn't use 2.886, I would use 2.905, which is the current release code. The 2.905 code, INI, and instructions are here: http://www.megamanual.com/ms2/code.htm

2.886 code is quite old now, and there were several revisions around that time to fix bugs. You should be able to load a 2.886 MSQ file into 2.905. A few user parameters will have been added, and TunerStudio will warn you about the ones that are missing from the MSQ.

Take a note of those from the warning, and look them up here: http://www.megamanual.com/mt29.htm and adjust them accordingly (the added parameters will have the default values in them, and these defaults are usually compatible with older MSQs, but check to be sure).

However, that assumes your MSQ isn't corrupted as well, and you should check all of the settings to make sure they are what they should be for your configuration.

Lance.

Ok after a bit of fooling with the com setting I get this when I communicate.

MegaSquirt Download 2.00

Reading C:/Documents and Settings/User/My Documents/Downloads/Monitor_v2.905.abs.s19:
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3db360
File read successfully.

Opened comm port 1 at 115200.
Erasing main FLASH:
ERROR: Command not recognized, e=0xE1
Elapsed time: 0.41 seconds

What does this mean and what do I do from here.

Thank you for your help,
Juan

Juan,

Check the tips here: http://www.megamanual.com/connect.htm#ms2

Lance.

so this is the message that I have now...

MegaSquirt Download 2.00

Reading C:/Documents and Settings/User/My Documents/Downloads/Monitor_v2.905.abs.s19:
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3db360
File read successfully.

Opened comm port 8 at 115200.
Erasing main FLASH:
Erased.
Writing:
Setting page register 0x3c:
Page set.
Erasing page 0x3c:
Erased.
Setting page register 0x3d:
Page set.
Erasing page 0x3d:
Erased.
Write complete, 1467 records, 46849 bytes.
Verifying:
Setting page register 0x00:
Page set.
Setting page register 0x3c:
Page set.
Setting page register 0x3d:
Page set.
Verification succeeded, 1467 records total (4 skipped).
Elapsed time: 49.83 seconds
MegaSquirt Download 2.00

Reading C:/Documents and Settings/User/My Documents/Downloads/Monitor_v2.905.abs.s19:
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3db360
File read successfully.

Opened comm port 8 at 115200.
Erasing main FLASH:
ERROR: Command not recognized, e=0xE1
Elapsed time: 0.47 seconds

After playing with com settings I managed to connect with my MS. I assume that i have sucessfully updated the firmware to v2.905. however I am still unable to establish a connection through TS. TS is telling me that the COm port is invalid. How is this possible when I have just used the port to connect with MS through the boot loader. I have removed the jumper afterward. SHoul I uninstall and reinstall TS?

i tried verifying info with the MSbootloader....

MegaSquirt Download 2.00

Reading C:/Documents and Settings/User/My Documents/Downloads/Monitor_v2.905.abs.s19:
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3db360
File read successfully.

Opened comm port 1 at 115200.
Verifying:
Verification failed: At 0x4000 expected 0x06, found 0xFF.
Exception caught: 4

I got this message, sorry if I am being a pain, I am very unfamiliar with this.

I've never tried the verify only operation on the downloader, but I can tell you that your last download with 2.905 was successful. The tipoff is "vwerification succeeded". This means the PC was able to read the code it downloaded and burned in Flash memory back and compare it with what it sent out, and they matched perfectly. Just ignore the error message at the very end - I get it all the time. If I knew how to fix it I would.

When you went to TS and it said you had the wrong comm port, that is a separate issue. In TS, go under communications/ Settings and it will let you pick different comm ports and test them. Once you get the right one it will keep it and you should be able to connect.

I've never tried the verify only operation on the downloader

Al,

Just passing along my own experience here, FWIW.....

I have found that using the 'verify only' function works quite well immediately after loading the firmware.

If you have written to the MS (ie. burned a tune) it will not verify, which makes sense to me anyway.

Regards,

Ken

Ken,
I am using the verify function immediately after writing to the controller and after I try to connect. It seems that I am not having a problem connecting to my MS to write the code. I am not familiar enough with this to make a judgement on that though. It connects and writes to the controller just as the the instructions say. However, I am unable to connect to MS via TS. I have tried uninstalling and reinstalling TS and have tried many different COM settings. Is there any known reason why I would be able to detect and write to MS via the bootloader and then not be able to establish communication through TS without changing anything? I have not said it previously my MSII is a pre assembled unit v3.57 board. Is it possible that my daughtercard is damaged?

I am super frustrated with this....

Thanks for your help,
Juan

Sorry, I did not read the post by Grippo.

Thank you, I'm glad that I got this right.

I have specified the COM port through the device manager to a number of unused ports, and I have tested those ports in TS and it fails every time. I have also killed extraneous programs to make sure that nothing is trying to use a port. Is it possible that there may be a mistake that I am making or should I just be patient and keep at it.

Thank you,
Juan

I find if I connect my laptop (win7) to the powered up MS before loading TS, it works right off. If load TS first, I usually have to fiddle with the port setting in TS. Sometimes coming back to the one it first said, but didn't see. I always use the same physical USB socket. But my USB to serial adaptor isn't an approved type - just an Ebay cheapy.

The Saga continues...

I have connected sucessfully to the MS by loading all of the software onto another computer running Windows 7. Initially TS recognized the controller but saw that there was no firmware insattled onto the MS. I downloaded the bootlader and retried installing v2.905. It was sucessful and no error report was generated at the end. TS recognized it right away and I has access to all tables once I set the MS type to "1" in the general settings.

Which bring me to my next question, the first problem that I encountered was that TS did not let me acess the basic tables on my laptop. I tried to overcome this problem by starting MT and trying to access them there. That is when my controller went crazy. I retried connecting with TS on my laptop now and I have the same problem that I started with. I can connect just fine without any problems but my basic tables are greyed out. I have tried reinstalling TS and unregistering it to see if that solves the problem but it has not. My laptop runs windows XP tablet edition. I have not had any problem with the second computer. Does anyone think that I might have to boot and nuke my laptop to resolve this? Is there somthing else that I might be missing?

Once again,

Thank you for all your help,
Juan