 | | Re: LinuxPPC and "No response from RCX" problem
|
|
(...) This may not be a driver bug - it may be a hardware limitation. AFAIK, parity is most commonly used with 7 bit words - support for a ninth bit (8 data plus parity) is poor or non-existant on some UARTs. Dave (24 years ago, 4-Nov-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: LinuxPPC and "No response from RCX" problem
|
|
(...) 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 (...) (24 years ago, 4-Nov-00, to lugnet.robotics.rcx.nqc)
|
| |
| | 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)
|
| |
| | Re: LinuxPPC and "No response from RCX" problem
|
|
(...) Have you tried using setserial to set the correct baud rate and other options? Also note that when using "su" it sometimes doesn't take over all the settings from the user account that you used to log on. Perhaps the sudo command would work (...) (24 years ago, 4-Nov-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: LinuxPPC and "No response from RCX" problem
|
|
(...) Umm.. note the prompt ;)) I'd done an su root before testing to avoid permissions problems. This seems like a problem with nqc on LinuxPPC 3Q99, but I can't understand quite what it is as the tower obviously works - the green light is visible (...) (24 years ago, 3-Nov-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: LinuxPPC and "No response from RCX" problem
|
|
(...) Did you set the correct permissions for the serial ports (normally they're only accessible by root under Linux) Do a chmod 777 for /dev/ttyS0 (24 years ago, 3-Nov-00, to lugnet.robotics.rcx.nqc)
|
| |
| | LinuxPPC and "No response from RCX" problem
|
|
Hi, I recently bought an RIS kit and from my Windows box it works fine. When I try using LinuxPPC off my PPC Amiga I get the following: [root] /home/chris/nqc/nqc-2.2.r2 >bin/nqc -v -raw 10 Tx: 55 ff 00 10 ef 10 ef Rx: 55 ff 00 10 ef 10 ef Tx: 55 ff (...) (24 years ago, 3-Nov-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Programmable RCX display
|
|
One of the missing "nice-to-have" features with the RCX is a programmable display. It would be great if LEGO implemented this feature. One way could be to attach a number 0 - 6 for each segment of the four 7-segment numbers and set a corresponding (...) (24 years ago, 3-Nov-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Monitor() and Event()
|
|
(...) The "monitor" control structure (as well as "acquire") is a very useful supplement of the existing control structures, such as "if", "while", "until", etc. Dave Baum already gave an example and with the following I also want to point out a (...) (24 years ago, 26-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Electrical Data Link between 2 RCXs
|
|
(...) Have you tried using SENSOR_MODE_EDGE or PULSE? Maybe it can keep track of it better? Edge could be very useful as it can count both on's and off's whereas pulse counts only on's. Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego (...) (24 years ago, 25-Oct-00, to lugnet.robotics.rcx.nqc)
|
