I'm just trying to get my MegaTune and MS2 started. Running on Windows XP.
I installed Megatune 2.25; activated megasuirt-ll.ini 2.3; set code variant for MS_ll in settings; set port to COM1 and 115,200; set interwrite delay to 5; basically following all instructions correctly.
Problem is when I startup MegaTune and connect the Stim, the gauges go erratic for awhile and flash random values. Then the gauges go pink and the ECU comm test says 'No response'. This is a repeatable result. The test does show 'Success' while showing the erratic gauges.
This is a DIYautotune assembled MS2. I tried to verify/write the embedded code for MS2. I presume it comes with 2.3xxx embedded code. Not sure how to verify this. After setting the B/LD jumper and connecting the stim, the downloader reads the file fine, but gets an 'unknown error' when attempting to communicate with the MS2 through COM1.
I know these are two seperate issues, but they are probably related. I'd appreciate any insight into these problems. I will continue to try and work it out in the meantime. Thanks.
-Steve
Erratic gauges/Connection issues.
Forum rules
Read the manual to see if your question is answered there before posting. If you have questions about MS1/Extra or MS2/Extra or other non-B&G code configuration or tuning, please post them at http://www.msextra.com The full forum rules are here: Forum Rules, be sure to read them all regularly.
Read the manual to see if your question is answered there before posting. If you have questions about MS1/Extra or MS2/Extra or other non-B&G code configuration or tuning, please post them at http://www.msextra.com The full forum rules are here: Forum Rules, be sure to read them all regularly.
Erratic gauges/Connection issues.
I'm just trying to get my MegaTune and MS2 started. Running on Windows XP.
I installed Megatune 2.25; activated megasuirt-ll.ini 2.3; set code variant for MS_ll in settings; set port to COM1 and 115,200; set interwrite delay to 5; basically following all instructions correctly.
Problem is when I startup MegaTune and connect the Stim, the gauges go erratic for awhile and flash random values. Then the gauges go pink and the ECU comm test says 'No response'. This is a repeatable result. The test does show 'Success' while showing the erratic gauges.
This is a DIYautotune assembled MS2. I tried to verify/write the embedded code for MS2. I presume it comes with 2.3xxx embedded code. Not sure how to verify this. After setting the B/LD jumper and connecting the stim, the downloader reads the file fine, but gets an 'unknown error' when attempting to communicate with the MS2 through COM1.
I know these are two seperate issues, but they are probably related. I'd appreciate any insight into these problems. I will continue to try and work it out in the meantime. Thanks.
-Steve
----------------------------------------
This post is at:
http://www.msefi.com/viewtopic.php?p=142611#142611
----------------------------------------
Posted by email.
I installed Megatune 2.25; activated megasuirt-ll.ini 2.3; set code variant for MS_ll in settings; set port to COM1 and 115,200; set interwrite delay to 5; basically following all instructions correctly.
Problem is when I startup MegaTune and connect the Stim, the gauges go erratic for awhile and flash random values. Then the gauges go pink and the ECU comm test says 'No response'. This is a repeatable result. The test does show 'Success' while showing the erratic gauges.
This is a DIYautotune assembled MS2. I tried to verify/write the embedded code for MS2. I presume it comes with 2.3xxx embedded code. Not sure how to verify this. After setting the B/LD jumper and connecting the stim, the downloader reads the file fine, but gets an 'unknown error' when attempting to communicate with the MS2 through COM1.
I know these are two seperate issues, but they are probably related. I'd appreciate any insight into these problems. I will continue to try and work it out in the meantime. Thanks.
-Steve
----------------------------------------
This post is at:
http://www.msefi.com/viewtopic.php?p=142611#142611
----------------------------------------
Posted by email.
-
Bernard Fife
- Super Squirter
- Posts: 1009
- Joined: Mon Feb 16, 2004 3:15 pm
Steve,I presume it comes with 2.3xxx embedded code. Not sure how to verify this.
In MegaTune, go to 'Mini-Terminal' under Communications, and type a captial S. The code version should be returned.
These both sound like comm issues to me. And they 'feel' like hardware issues, rather than a configuration error. I hjust repaired a MegaSquirt that had a similar problem. It would work fine for exactly 4 characters, then all comms would stop. Obviously this made it difficult to load code ort do much of anything else. the problem turned out to be a fired MAX232 chip in that case.
If I had your problem, I would:
- try setting up MegaTune on another computer if you can, and see if that is any better,
- recheck that you are actually using COM1 with a loopback test (see: http://www.megamanual.com/ms2/V3assemble.htm#serial). However I am quite sure COM1 is right, otherwise you wouldn't get even the erratic readings,
- recheck the cable connections (I.e., pin #2 connects to pin #2 at the other end of the cable, #3 -#3, etc. The pin numbers are embedded into the plastic near the pins - you may need a magnifying glass - I do!). Again, I suspect this is right, but it's possible the cable has an intemittent open ciruit on one of the wires, I suppose,
- If you feel like digging into the hardware, on a V3 main board (I think it's the same on a V2.2 board) the following should be connected:
- DB9 pin 2 to MAX232 pin 14
- DB9 pin 3 to MAX232 pin 13
- MAX232 pin 11 to CPU socket pin 12 (TxD)
- MAX232 pin 12 to CPU socket pin 13 (RxD)
Each of those should have less than 1 Ohms resistance. If they have more resistance, or it is not consistent, resolder the applicable components solder joints.
You should check that you have 5.0 Volts (±0.10) on the MAX232 pin 16, and ground on pin 15. Check both while the comms are working, and while they are not. Use the middle pin of the voltage regulator as a ground for measuring the voltage, and check that you have less than 1 Ohms resistance between pin 15 and the center lead of the votlage regulator.
If you have your MAX232 in a socket, make sure it is well seated.
The associated components for the MAX 232 are (on a V3 main board): C26, C27, C28, C29. Make sure they are the right components, and are well soldered and not bridged. You may very well have a cold solder joint, as noted in the troubeshooting instructions here: http://www.megamanual.com/ms2/V3trouble.htm
You should also make sure no other programs are tring to use the COM port, like a fax modem. There are other specific tips here: http://www.megamanual.com/connect.htm
If all of the above are okay, I would replace the MAX232. They tend not to 'wear out', so the amount of use isn't important, but they can fail after a few hours if they have seen a static shock at any point.
If this was mine, though, I would return it to the manufacturer (who was it?) for testing and replacement. Distribtuors are 100% responsible for their build quality, and they should be approached directly on hardware probelms related to assembled units.
Lance.
-
Bernard Fife
- Super Squirter
- Posts: 1009
- Joined: Mon Feb 16, 2004 3:15 pm
Erratic gauges/Connection issues.
Steve,I presume it comes with 2.3xxx embedded code. Not sure how to verify this.
In MegaTune, go to 'Mini-Terminal' under Communications, and type a captial S. The code version should be returned.
These both sound like comm issues to me. And they 'feel' like hardware issues, rather than a configuration error. I hjust repaired a MegaSquirt that had a similar problem. It would work fine for exactly 4 characters, then all comms would stop. Obviously this made it difficult to load code ort do much of anything else. the problem turned out to be a fired MAX232 chip in that case.
If I had your problem, I would:
- try setting up MegaTune on another computer if you can, and see if that is any better,
- recheck that you are actually using COM1 with a loopback test (see: http://www.megamanual.com/ms2/V3assemble.htm#serial). However I am quite sure COM1 is right, otherwise you wouldn't get even the erratic readings,
- recheck the cable connections (I.e., pin #2 connects to pin #2 at the other end of the cable, #3 -#3, etc. The pin numbers are embedded into the plastic near the pins - you may need a magnifying glass - I do!). Again, I suspect this is right, but it's possible the cable has an intemittent open ciruit on one of the wires, I suppose,
- If you feel like digging into the hardware, on a V3 main board (I think it's the same on a V2.2 board) the following should be connected:
- DB9 pin 2 to MAX232 pin 14
- DB9 pin 3 to MAX232 pin 13
- MAX232 pin 11 to CPU socket pin 12 (TxD)
- MAX232 pin 12 to CPU socket pin 13 (RxD)
Each of those should have less than 1 Ohms resistance. If they have more resistance, or it is not consistent, resolder the applicable components solder joints.
You should check that you have 5.0 Volts (±0.10) on the MAX232 pin 16, and ground on pin 15. Check both while the comms are working, and while they are not. Use the middle pin of the voltage regulator as a ground for measuring the voltage, and check that you have less than 1 Ohms resistance between pin 15 and the center lead of the votlage regulator.
If you have your MAX232 in a socket, make sure it is well seated.
The associated components for the MAX 232 are (on a V3 main board): C26, C27, C28, C29. Make sure they are the right components, and are well soldered and not bridged. You may very well have a cold solder joint, as noted in the troubeshooting instructions here: http://www.megamanual.com/ms2/V3trouble.htm
You should also make sure no other programs are tring to use the COM port, like a fax modem. There are other specific tips here: http://www.megamanual.com/connect.htm
If all of the above are okay, I would replace the MAX232. They tend not to 'wear out', so the amount of use isn't important, but they can fail after a few hours if they have seen a static shock at any point.
If this was mine, though, I would return it to the manufacturer (who was it?) for testing and replacement. Distribtuors are 100% responsible for their build quality, and they should be approached directly on hardware probelms related to assembled units.
Lance.
------------------------
<b>Forum Rules</b> (http://www.msefi.com/viewtopic.php?t=13152) --- No responses to your posts? See this. (http://www.msefi.com/viewtopic.php?t=16456)
MegaFAQ (http://www.megamanual.com/) --- MegaManual (http://www.megamanual.com/mtabcon.htm)
----------------------------------------
This post is at:
http://www.msefi.com/viewtopic.php?p=142614#142614
----------------------------------------
Posted by email.
The assembled MS2 comes from http://www.diyautotune.com ; same with the stim and relay board.
Typing an 'S' in Mini Term returned ** (two asterisks). I tried it again and it gave me this: *( ll"$ ; Each time I type a capital 's', it returns some combination of asterisk(s), parenthesis, dollar signs, or sometimes nothing at all. I am not sure what it all means, but it does not sound right.
The board 'looks' clean and well put together (if that means anything). I don't want to try and go back on the manufacturer until I'm confident that I've not missed anything. I should have time in the morning to go through the things you've suggested. Hopefully it is something simple, rather than a hardware problem.
Thanks for the helpful reply. I'll check it out and post what I find.
-Steve
EDIT: Found in device manager that Baud rate was @ 9600. Switched to 115200 and MT will no longer open. Gives error message and will close.
This is the message dialog received when attempting to update the embedded code:
_______
MegaSquirt Download 1.04
Reading C:\Documents and Settings\Steve\Desktop\Monitor_v2.36.abs.s19:
C:\Program Files\Metrowerks\CodeWarrior CW12_V3.1\MSIIC_Proj\bin\Monitor.abs
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3cade0
File read successfully.
Opened comm port 1 at 115200.
ERROR: Unknown error status response, e=0xFF
Elapsed time: 0.01 seconds
Typing an 'S' in Mini Term returned ** (two asterisks). I tried it again and it gave me this: *( ll"$ ; Each time I type a capital 's', it returns some combination of asterisk(s), parenthesis, dollar signs, or sometimes nothing at all. I am not sure what it all means, but it does not sound right.
The board 'looks' clean and well put together (if that means anything). I don't want to try and go back on the manufacturer until I'm confident that I've not missed anything. I should have time in the morning to go through the things you've suggested. Hopefully it is something simple, rather than a hardware problem.
Thanks for the helpful reply. I'll check it out and post what I find.
-Steve
EDIT: Found in device manager that Baud rate was @ 9600. Switched to 115200 and MT will no longer open. Gives error message and will close.
This is the message dialog received when attempting to update the embedded code:
_______
MegaSquirt Download 1.04
Reading C:\Documents and Settings\Steve\Desktop\Monitor_v2.36.abs.s19:
C:\Program Files\Metrowerks\CodeWarrior CW12_V3.1\MSIIC_Proj\bin\Monitor.abs
Detected MS-II (HCS12) code.
Entry point: 0x0000
Code range : 0x4000-0x3cade0
File read successfully.
Opened comm port 1 at 115200.
ERROR: Unknown error status response, e=0xFF
Elapsed time: 0.01 seconds
Erratic gauges/Connection issues.
The assembled MS2 comes from http://www.diyautotune.com ; same with the stim and relay board.
The board 'looks' clean and well put together (if that means anything). I don't want to try and go back on them until I'm confident that I've not missed anything. I should have time in the morning to go through the things you've suggested. Hopefully it is something simple, rather than a hardware problem.
Thanks for the helpful reply. I'll check it out and post what I find.
-Steve
----------------------------------------
This post is at:
http://www.msefi.com/viewtopic.php?p=142692#142692
----------------------------------------
Posted by email.
The board 'looks' clean and well put together (if that means anything). I don't want to try and go back on them until I'm confident that I've not missed anything. I should have time in the morning to go through the things you've suggested. Hopefully it is something simple, rather than a hardware problem.
Thanks for the helpful reply. I'll check it out and post what I find.
-Steve
----------------------------------------
This post is at:
http://www.msefi.com/viewtopic.php?p=142692#142692
----------------------------------------
Posted by email.
A little update on this and what I've figured out so far:
1) Mini-Term fails to return a code version.
2) Cable seems Ok. Also purchased from diyautotune. Sold specifically for this app.
3) Loopback test on CABLE ONLY (pin 2 to pin 3) is successful. Returns characters; double characters with local echo 'on'. COM1 IS correct.
4) FAILS loopback test with pins 12/13 jumpered (stim plugged in/powered up; DB9 plugged into ECU; as per instructions).
______________
So, I think this means Lance's hunch is correct, meaning a probable hardware issue. I think this also rules out a problem with MegaTune, as this test only uses hyperterminal.
I'm a little hesitant to start soldering and replacing components on the board. The whole reason I purchased a complete board was to avoid hassles like this. I'm starting to regret that choice.
I will test the suggested connections with a multi-meter. Hopefully this will pinpoint the problem. Any suggestions? Am I on the right track here?
-Steve
EDIT:
- DB9 pin 2 to MAX232 pin 14
- DB9 pin 3 to MAX232 pin 13
Both of the above connections read ~1.8 ohms resistance. These should be resoldered?? They both read exactly the same resistance...
1) Mini-Term fails to return a code version.
2) Cable seems Ok. Also purchased from diyautotune. Sold specifically for this app.
3) Loopback test on CABLE ONLY (pin 2 to pin 3) is successful. Returns characters; double characters with local echo 'on'. COM1 IS correct.
4) FAILS loopback test with pins 12/13 jumpered (stim plugged in/powered up; DB9 plugged into ECU; as per instructions).
______________
So, I think this means Lance's hunch is correct, meaning a probable hardware issue. I think this also rules out a problem with MegaTune, as this test only uses hyperterminal.
I'm a little hesitant to start soldering and replacing components on the board. The whole reason I purchased a complete board was to avoid hassles like this. I'm starting to regret that choice.
I will test the suggested connections with a multi-meter. Hopefully this will pinpoint the problem. Any suggestions? Am I on the right track here?
-Steve
EDIT:
- DB9 pin 2 to MAX232 pin 14
- DB9 pin 3 to MAX232 pin 13
Both of the above connections read ~1.8 ohms resistance. These should be resoldered?? They both read exactly the same resistance...