 | | RCX2 Lego Website Address
|
|
Gareth Jones I think this is the address your looking for (URL) (25 years ago, 30-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Need help to put sound in Minerva Program.
|
|
A person with a visual handicap is building Minerva. I would like to add sound to the program while Minerva is going forward, another when she is turning around, and another when she locates something to pick up. This will allow this builder to test (...) (25 years ago, 29-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | RCX2 API Update
|
|
I made some mistakes in the first release, so here is a new version. I've also added counter support. <-Readme.txt-> RCX2 Header file for NQC2.1r2 - 27 April 2000 - James Pritchard rcx2api.nqh - NQC Header file that contains constant and macros for (...) (25 years ago, 29-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Duplex Comms with RCX
|
|
(...) I have given this some thought in the past, although I haven't had the (significant!) time that it would take to try this out. I think the best hope for any kind of two-way communication protocol between the PC and one or more RCXes is to use (...) (25 years ago, 27-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Duplex Comms with RCX
|
|
(...) I actually prefer the "junk" solution to a hardware hack. (25 years ago, 27-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Duplex Comms with RCX
|
|
(...) It seems to me that, given the current hardware, the choices are: send junk or let the tower go dead. My thinking is that if you send junk and trample something, so be it; the tower would have gone dead anyways, forcing you to lose whatever it (...) (25 years ago, 27-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Duplex Comms with RCX
|
|
(...) Fair enough. It's too bad it doesn't have an always-on mode. (...) Definitely agreed. I'll be patient. (25 years ago, 27-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Duplex Comms with RCX
|
|
(...) I just haven't found a non-intrusive method for keeping the tower alive. I hate transmitting garbage every few seconds and possibly trampling incoming data. I'm also not sure this is a very good long-term solution. Really a general purpose (...) (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Duplex Comms with RCX
|
|
(...) Not that there's any pressure or anything. :) (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Duplex Comms with RCX
|
|
(...) Dave had mentioned making a listen mode w/ keep-alive in a future version of nqc. But I don't think he's gotten around to that yet. (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Duplex Comms with RCX
|
|
(...) Yes. Note that it is only half-duplex. You probably expected that. (...) The biggest issue you might run into is the fact that the IR tower used by the PC times out if it doesn't transmit anything for a few seconds. Unless you have constant (...) (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Duplex Comms with RCX
|
|
"James Hammond" <jsh@it-innovation.soton.ac.uk> wrote in message news:3906A2E6.6A40E0...n.ac.uk... (...) Yes it can. There is a standard RCX opcode for sending single byte messages, and you can always use multiple of these commands for more complex (...) (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Duplex Comms with RCX
|
|
It appears Roblab 2.0 would also be an alternative for your project. Robolab has two different direct modes to control the RCX, one of which is using a remote connection like the Internet. Depending on your direct control requirements, you may want (...) (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | RCX2 API
|
|
I've put together a NQC API file that allows you to use some of the RCX2 features. I don't no whether anyone else has already done this but here is mine. This is unofficial so is unsupported. All question should go to the group, not Dave or myself. (...) (25 years ago, 26-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | RCX2 API
|
|
I've put together a NQC API file that allows you to use some of the RCX2 features. I don't no whether anyone else has already done this but here is mine. This is unofficial so is unsupported. All question should go to the group, not Dave or myself. (...) (25 years ago, 26-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Duplex Comms with RCX
|
|
Hi I am sure this has been done many times before, but I am having trouble confirming information. I wish to purchase the RIS 1.5. But before I do I need to be sure that I can communicate with a running program on the RCX and that the RCX can (...) (25 years ago, 26-Apr-00, to lugnet.robotics, lugnet.robotics.tele, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Q: Determining state of outputs
|
|
It works fine. Thanks for your help! Oliver (25 years ago, 25-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: RCX2: ViewSourceValue Help
|
|
(...) asm statements are just followed by a comma-separated list of fields enclosed in braces. In general, each field is evaluated at compile time and the resulting value is truncated to 8 bits. The exception is the & operator. The &x syntax is used (...) (25 years ago, 24-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | RCX2: ViewSourceValue Help
|
|
Hi, I'm back after a break from Lego. (I had exams). I've been playing around with RCX2 firmware and want to use the new ViewSourceValue command. What is the correct asm for this. So far I've got this by guessing and looking at RCX2.NQH #define (...) (25 years ago, 24-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: RCX For Sale.
|
|
The product is sold. ===...=== "Bert Onderdijk" <bert_onderdijk@hotmail.com> wrote in message news:Ft4Cr3.B2w@lugnet.com... (...) (25 years ago, 19-Apr-00, to lugnet.robotics.rcx.nqc)
|
