 | | time control : BrickOS versus the RCX standard OS ?
|
|
Hi list, I'm trying to implement a position regulation (using a motor and a rotation sensor), using for instance a PID (Proportional-Integr...erivative) regulation. I tried to code it in NQC, using the standard OS, but it seems that the RCX standard (...) (21 years ago, 17-Sep-05, to lugnet.robotics.rcx.legos)
|
| |
 | | 5-DOF arm
|
|
Hi everyone -- I have recently completed my Nth version of a 5-DOF arm plus claw. Finally, I am guardedly happy with the result. I think it's about as minimalist as such a thing can be; it's much smaller than models with similar capability I've seen (...) (21 years ago, 17-Sep-05, to lugnet.robotics)
|
| |
 | | IR-based proximity measurement
|
|
I'm changing the subject line in the middle of the thread. Wonder what the server will do with that... I tried out Brian's "Max-picking" ping method, as well as a few other things. Here's a summary of what I found: 1) If the active sensor readings (...) (21 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: direct manipulation of bits in RCX registers using NQC
|
|
(...) Correct. A NQC command (say, "Wait(10);") is converted to one or more "bytecodes" (in this case, one bytecode, namely a string of 4 bytes (0x43 0x02 0x0a 0x00), the first of which is a command (0x43) while the following three are information (...) (21 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: direct manipulation of bits in RCX registers using NQC
|
|
Hey, Thanks for all the helpful responses, everyone. Brian: (...) I guess that "firmware" must be the code that tells RCX how to interpret user instructions (NQC, C, IC, opcodes, or whatever), and convert them to binary machine-specific code. Right? (...) (21 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: RCX to RCX NQC
|
|
(...) And that explains why I was having so much trouble with my custom Tcl based uploader in high speed mode. I fixed it a while ago by adding a slight bit of extra time between messages, but never got to the root of the problem. Thanks Dick! (...) (21 years ago, 15-Sep-05, to lugnet.robotics.rcx)
|
| |
 | | RCX to RCX NQC
|
|
One last email on this topic. There's new opcodes in the Swan firmware to support many data bytes in a single "mailbox" message. The standard firmware supports "mailbox" messages with a single byte parm. I found this very restrictive in building RCX (...) (21 years ago, 15-Sep-05, to lugnet.robotics.rcx)
|
| |
 | | RE: RCX to RCX NQC
|
|
There's another little problem that you may need to program around. There's a bug in the ROM firmware that could end up requiring a 30-millisecond delay between when a RCX sends out a message and when you should start sending the first character of (...) (21 years ago, 15-Sep-05, to lugnet.robotics.rcx)
|
| |
 | | RE: RCX to RCX NQC
|
|
The message "toggle" bit was a good concept that has very limited value in practical use. I guess the intent was to prevent unexpected behavior when a PC program attempts retransmission after a message failure. Suppose the failure condition was that (...) (21 years ago, 15-Sep-05, to lugnet.robotics.rcx)
|
| |
 | | I wonder if they'll work with Lego pneumatics
|
|
(URL) double acting soleniod valve looks "very" interesting! Anyone know any more about this? JB (21 years ago, 15-Sep-05, to lugnet.robotics)
|