Subject:
|
Re: LinuxPPC and "No response from RCX" problem
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Sat, 4 Nov 2000 16:22:22 GMT
|
Viewed:
|
1988 times
|
| |
|
|
In lugnet.robotics.rcx.nqc, Dave Baum writes:
>
> Do you have a second computer (running a different OS) with a terminal
> program handy? If so, hook the two up with a null modem cable. Hack
> RCX_Link::Open() to write an ascii string (e.g. "Hello World") to the
> port after opening and setting the speed. Make sure the terminal on the
> second computer is set for 2400 baud, 8 data, 1 start, 1 stop, odd
> parity. See if "Hello World" comes through...if not, then the parity is
> probably not happening (try using no parity on the terminal to verify).
This helped me track down the problem - the minute I add the odd parity
bit the serial driver changes the word length from 8 to 7. Doesn't look
like I can do much about it from the Linux side either.
:(
Thanks for the help everyone, looks like I'll just have to use the
Windows box..
Chris
|
|
Message has 1 Reply:
Message is in Reply To:
 | | Re: LinuxPPC and "No response from RCX" problem
|
| (...) Perhaps timing is a problem. Try: nqc -t 1000 -raw 10 This forces a longer (1 second) timeout per packet instead of the dynamic retry timing. Is the output any different? Echo is coming back from the tower, which means communication between (...) (24 years ago, 4-Nov-00, to lugnet.robotics.rcx.nqc)
|
11 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
