Serial comm testing - cable ok, jibberish on screen
Read the manual to see if your question is answered there before posting. Many users will not reply if the answer is already available in the manual.
If your question is about troubleshooting, configuration, or tuning, you MUST include your processor type (MS-I or MS-II) and code version in your post. If your question is about PCB assembly or modifications, you must also include the main board version number (1.01, 2.2 or 3.0).
If you have questions about MS1/Extra or MS2/Extra code configuration or tuning, please post them at www.msextra.com Such questions posted here will be moved to: a temporary MSextra sub-forum, where they will be removed after 7 days
The full forum rules are here: Forum Rules, be sure to read them all regularly.
Re: Serial comm testing - cable ok, jibberish on screen
I put the Max232 into the socket that I had previously soldered onto the board, jumpered 12 and 13 together (right in front of R44) and then connected the stimulator. NOTHING on hyperterminal. NO jibberish, but also no echo. Occasionally I will get the cursor to move 1 space upon the first touch of a key, or 1 house shaped character. I have baud set at 115200, data bits 8, stop bits 1, flow control none and parity none. I also tried the jumpering right at the underside of the Max232, pins 11&12 to rule out a processor socket issue. Nope. If I turn echo on I do see the keys I type, but only 1 not 2 of each.
I've wiggled the serial connector to make sure there is no loose connection. No change. I checked continuity between each input hole on the DB9 and its connection on the PCB andthe Max232 socket. I performed the voltage and continuity checks per the trouble shooting guide. All are as they should be per step 3. I have ensured that all components are in place per the instructions, including any polarity. I know how to solder boards and components, so I am very confident in the integrity of the connections. Whole thing has been de fluxed using acetone and toothbrush.
I'm at a total loss. Other than the Max232 and the mechanical connections to DB9, the only other components in this loop are the 4 (.1microfarad) capacitors, C26, C27, C28, C29, right? I know the voltage circuit is fine, so that is ruled out. Chances of 2 bad Max232s is slim, how about something with the capacitors?????? I've double checked their connections - all solid, clean and pass any wiggle test. Hold on, let me do a board check using the diagram in section 3............
VOILA!!!!!!!!!! I'm not insane! Capacitor C28 has continuity on one leg to MAX232 pin #4, but the other leg (or hole either) has no continuity with MAX232 pin #5 as it should!!! There's a bad connection in the PCB!!!!!!!! Ok..I just jumpered it and it works!!! I HATE THESE KINDS OF PROBLEMS, BUT I LOVE SOLVING THEM! Moving on now..... guess it wasn't a bad Max232 after all. Oh well, there goes $7.
Re: Serial comm testing - cable ok, jibberish on screen
Is there a means to replicate this function using the MSII board? Essentially I need to energize the solenoid at idle, disable it otherwise. Can you steer me in the right direction?
Thanks,
Owen.
-
Matt Cramer
- Super Squirter
- Posts: 2951
- Joined: Sat Jul 03, 2004 11:35 am
Re: Serial comm testing - cable ok, jibberish on screen
http://www.megamanual.com/ms2/spare.htm
You can build a relay control circuit to turn on below X RPM and above Y degrees of coolant temperature easily enough.
Re: Serial comm testing - cable ok, jibberish on screen
Any words of warning/benefit on having MSII manage the ignition timing too? I know I have a juper to go change somewhere and a couple of things to double check......
