MTTTY Serial Problem
MTTTY Serial Problem
Yesterday everything worked great! Today I tried running MTTTY and now can't type any characters like "A". After looking at my COM1 serial port settings on my desktop I found that the baud rate was set to 9600. I looked at MTTTY's setting and it is set to 115200 baud. If this what was set all along -- how did MTTTY ever communicate with my MOD5282 dev brd before today? So next I set the baud rate of COM1 to match MTTTY's setting to no avail. I still cannot type any letters into MTTTY. It's like my keyboard doesn't work only in MTTTY now. I checked and rechecked to try and make sure the COM1 settings match MTTTY's settings and nothing works. I even rebooted my computer a couple of times. I also duplicated the problem using "HyperTerminal". Any sugestions would be greatly appreciated.
-
Chris Ruff
- Posts: 222
- Joined: Thu Apr 24, 2008 4:09 pm
- Location: topsail island, nc
- Contact:
Re: MTTTY Serial Problem
MTTTY "owns" the serial port it is using. If MTTTY sets the port to 115200 it makes no difference what any other programs in the computer, the control panel applet, etc. thinks the COM port baud rate is.
When things go quiet you can sometimes go to TTY/Flow Control and set flow control to NONE. Garbage on the line can invoke XOFF and stop comm, although I don't believe this is what you problem is.
Connect a "null modem" cable between two COM ports and use two MTTTYs to prove that your desktop is not the problem. (null modem: DB9_1 pin 5 to DB9_2 pin 5, pin 2 to 3, pin 3 to 2)
IF the two MTTTYs are rattling to each other your module is no longer talking.
Chris
When things go quiet you can sometimes go to TTY/Flow Control and set flow control to NONE. Garbage on the line can invoke XOFF and stop comm, although I don't believe this is what you problem is.
Connect a "null modem" cable between two COM ports and use two MTTTYs to prove that your desktop is not the problem. (null modem: DB9_1 pin 5 to DB9_2 pin 5, pin 2 to 3, pin 3 to 2)
IF the two MTTTYs are rattling to each other your module is no longer talking.
Chris
Real Programmers don't comment their code. If it was hard to write, it should be hard to understand
Re: MTTTY Serial Problem
Thanks Chris!
Turns out I have been communicating via USB all along and didn't even know it since I also had RS232 connected. I swiched the jumper to "RS232" on my MOD5282 dev brd and MTTTY worked the 1st time. I switched it back to USB since now I only need one connection for both power and debug. I just have to remember that "COM3" and not "COM1" in MTTTY is my USB port.
Take care, Pat
Turns out I have been communicating via USB all along and didn't even know it since I also had RS232 connected. I swiched the jumper to "RS232" on my MOD5282 dev brd and MTTTY worked the 1st time. I switched it back to USB since now I only need one connection for both power and debug. I just have to remember that "COM3" and not "COM1" in MTTTY is my USB port.
Take care, Pat