 | | Re: LinuxPPC and "No response from RCX" problem
|
|
(...) Nope, I've written a program to send messages to the RCX (like the send.c program on RCX Internals) for the Amiga side - I can boot into LinuxPPC or AmigaOS - and that works fine. If I can work out the format of the image files nqc generates (...) (24 years ago, 5-Nov-00, to lugnet.robotics.rcx.nqc)
|
| |
| | 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)
|
| |
| | Electrical Data Link between 2 RCXs
|
|
The following describes an "electrical data link" (one direction) between 2 RCXs (see also my subject "Connecting 2 RCXs"). The task is that one RCX sends a number (e.g. a status) to another RCX via a cable. The IR link cannot be used because they (...) (24 years ago, 25-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.2 r2 released
|
|
(...) to get the linux packages updated as soon as I can, and the man page too. (24 years ago, 25-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Connecting 2 RCXs
|
|
Isn't there anywhere in this world I can escape b******* Whnitney Houston? I thought this was a pretty safe bet.... Duq "Bernd Frassek" <bernd.frassek@aache...timaco.de> wrote in message news:G2xFGs.L3x@lugnet.com... (...) (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Connecting 2 RCXs
|
|
(...) Glad I could be of help in passing information. Brick on! Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Connecting 2 RCXs
|
|
Thanks a lot Dean - works perfectly. A good trick - and so evident that I am a bit frustrated not to find it out by myself ... ;-) But this is what friends are for (was it Whitney Houston who sang that?) Bernd (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Timing of RCX statements
|
|
(...) Thanky Dave for your reflections concerning the timing. The thing that caused some astonishment and a little bit of frustration is that the RCX is so slow. O.K. - the code sent to the RCX is interpreted and this needs some time. However, I was (...) (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Monitor() and Event()
|
|
(...) I decided to write a small sample program showing how to configure events. Check out events.nqc at (URL) reply to: dbaum at enteract dot com (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Monitor() and Event()
|
|
(...) Monitoring is automatic (done by the firmware). Monitoring stops when control leaves the monitor statement, so something like this: while(true) { monitor(EVENTS) { } catch { } } will miss a lot of events. You need to configure the events using (...) (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Timing of RCX statements
|
|
(...) I wouldn't expect Wait() to be very precise. I haven't looked at the firmware in great detail, but generally when writing this sort of thing you set up timing chains. Imagine a function that gets called every 1ms for bookkeeping... void (...) (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
