 | | Re: time sampling under the rcx standard OS
|
|
(...) From what I've seen, the standard firmware takes about 3ms per command, and the same program will run on BrickOS about 100 times faster. I usually set up my BrickOS programs so they use the internal timer, and only update the motor setting (...) (20 years ago, 17-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: time sampling under the rcx standard OS
|
|
(...) Francois, I think you should be able to get much faster sampling. I can easily get 10-20 Hz, and others have claimed to get down to 3 ms. Whether it can be done at a constant rate, I'm not sure, and think it probably depends on what else is in (...) (20 years ago, 17-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | time sampling under 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 loops at (...) (20 years ago, 17-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | 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 (...) (20 years ago, 17-Sep-05, to lugnet.robotics.rcx.legos)
|
| |
| | 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 (...) (20 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 (...) (20 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? (...) (20 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! (...) (20 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 (...) (20 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 (...) (20 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 (...) (20 years ago, 15-Sep-05, to lugnet.robotics.rcx)
|
| |
| | Re: RCX to RCX NQC
|
|
(...) I'm pretty sure, both the remote, and the send message commands only have one op-code, and are done differently from the rest. Steve (20 years ago, 14-Sep-05, to lugnet.robotics.rcx)
|
| |
| | Re: RCX to RCX NQC
|
|
(...) Ahh, now I understand why it is called a "toggle bit" - I somehow misinterpreted this to mean a new command had the toggle bit set (to 1), and if the sending unit doesn't recieve a reply it should re-transmit the command with the toggle bit (...) (20 years ago, 14-Sep-05, to lugnet.robotics.rcx)
|
| |
| | Re: 1.0 brick not responding
|
|
(...) Powerbook 5300 with MacNQC: After about 4 seconds "No response or bad response from RCX. Make sure the RCX's receiver is facing the IR device and the RCX is turned on." Palm 130 with PBrick Demo: play sound 1, play sound 2, and play sound 3 (...) (20 years ago, 14-Sep-05, to lugnet.robotics.rcx)
|
| |
| | Re: 1.0 brick not responding
|
|
(...) Generally, that means the IR tower is working. It's possible the tower has become broken, while it sat in a closet, but that's not very likely. So, knowing things worked before, you may be forgetting something. Make sure the memory is cleared. (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx)
|
| |
| | Re: 1.0 brick not responding
|
|
(...) Yes, it flashes. (...) Yes it did work, but it's been in storage for a couple of years. (...) At this point, just download firmware. Once I get the communication issues resolved, I'll do programming. (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx)
|
| |
| | Re: direct manipulation of bits in RCX registers using NQC
|
|
(...) I agree with Steve that the code samples you posted are probably BrickOS. Now to acheive what you want, it might be a waste of power, but you could always blank off the light itself with a peice of black card or thin black packing plastic. If (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: direct manipulation of bits in RCX registers using NQC
|
|
(...) Matt, There are a few ways you can program your RCX. The main choice is if you use the standard firmware, or not. The firmware is pretty much like Windows Operating System. If you use NQC & the standard firmware, you don't need to worry about (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: direct manipulation of bits in RCX registers using NQC
|
|
(...) inside the RCX *directly*, not running programs layered on top of the standard firmware. And if you want to use NQC, you have to work within the limits of the standard firmware (OK, ignoring Dick Swan's firmware, which I've still not been able (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: direct manipulation of bits in RCX registers using NQC
|
|
(...) Hi Brian, Thanks for your response. (...) I'm not sure if I get this, because of C code examples I've seen, which I'll discuss again below. (...) I've tried this already, and as you say, it works, but the sensitivity goes waay down. For a (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: RCX to RCX NQC
|
|
On Mon, September 12, 2005 8:03 pm, Brian Davis wrote: ... (...) ... Somewhere in there, it tells you the RCX will not accept the same command twice in a row. Each command has two op codes that are 8 digits apart. So (I think) for SetWatch you (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx)
|
| |
| | Re: direct manipulation of bits in RCX registers using NQC
|
|
(...) Perhaps - but the standard firmware implements a "virtual machine", and so you don't generally have access to physical registers. But... (...) You can configure the input port that the light sensor is connected to as a "passive" sensor (so (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | RCX to RCX NQC
|
|
In a semi-followup to Steve's earlier "remote battery tester"... While the standard firmware provides almost no way to get bytes into the RCX (other than "Message()", one byte at a time), it can certainly export them ("SendSerial"). And it occured (...) (20 years ago, 13-Sep-05, to lugnet.robotics.rcx)
|
| |
| | direct manipulation of bits in RCX registers using NQC
|
|
Hi all, Can anyone tell me if it is possible to use NQC to directly set bits in RCX registers? And if so, how does one do it? I've seen C code examples of this in a few places, but no NQC examples. Specifically, I want to turn on and off the red (...) (20 years ago, 12-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: 1.0 brick not responding
|
|
(...) Tammy, A couple questions... 1) Does the light on the IR tower flash when you're trying to communicate? 2) Did it ever work (did it work before, but stop, or is this the first time you've tried communicating?) 3) What are you trying to (...) (20 years ago, 12-Sep-05, to lugnet.robotics.rcx)
|
| |
| | 1.0 brick not responding
|
|
mac powerbook 5300 communicates with the IR tower, but no response from the brick. palm 130 with pbrick, also no response from the brick. The brick powers on and beeps, just no communication with the powerbook or the palm for programming. Since it (...) (20 years ago, 12-Sep-05, to lugnet.robotics.rcx)
|
| |
| | Re: RCX to RCX LNP
|
|
(...) So, I finally sat down and figured out how the lnp state machine works in BrickOS. Turns out it was pretty easy to add in a new set of states so it can process a standard OpCode & store the parameters in variables. At this point, I'm not (...) (20 years ago, 8-Sep-05, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Arrays and functions in NQC
|
|
(...) No. No. From the NQC Guide: The RCX2, Swan, and Spybotics targets support arrays (the other targets do not have suitable support in firmware for arrays). Arrays are declared the same way as ordinary variables, but with the size of the array (...) (20 years ago, 8-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Arrays and functions in NQC
|
|
Two little questions for the NQC gurus... - Is it possible to use 2-dimentionnal arrays in NQC? - Is it possible (and if yes what is the syntax) to pass an array as an inline function parameter? TIA, Philo (20 years ago, 8-Sep-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: dll 'error deleting program' with briskOS-0.9.0
|
|
(...) I am also encountering this same problem: - I am working with a Linux 2.6 (Fedora Core 3). - The system was downloaded successfully to the RCX 1.0 brick with firmdl3. - But I COULD NOT load ANY program with the dll utility! Each time I got an (...) (20 years ago, 25-Aug-05, to lugnet.robotics.rcx.legos)
|
| |
| | An idea concerning the new RC trains and a new RCX
|
|
Hi, all, I know this might just be a shot in the blue sky, but anyway: Lego is most propably working on a new RCX system. At the Legofan site, there is a discussion about things that should be in a new RCX, and someone mentioned Bluetooth as a (...) (20 years ago, 23-Aug-05, to lugnet.trains, lugnet.dear-lego, lugnet.robotics.rcx)
|
| |
| | Re: different output power at different ports?
|
|
(...) I've discovered a thread in legofan (URL) that talks about new features of a possible RCX 3.0. Is there more information that can be handed out? - Dave (20 years ago, 22-Aug-05, to lugnet.robotics.rcx, lugnet.robotics.rcx.robolab)
|
| |
| | Re: container in a container error
|
|
(...) Thanks Claude. I look forward to implementing the correction. Tom (20 years ago, 17-Aug-05, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: RCX to RCX LNP
|
|
Hi. (...) That would be a fun state machine to set up... ;-) (...) It only does so when it receives opcodes between 0xf0 - 0xf7 or a standard firmware message (0x55). Of the first eight, only 0xf0 and 0xf1 currently require further action, with 0xf0 (...) (20 years ago, 17-Aug-05, to lugnet.robotics.rcx.legos)
|
| |
| | Re: container in a container error
|
|
(...) This just was an forgotten bug that with older Robolab versions didn't harm. The solution is to remove the "Value of red container" and replace it by a blue container constant list ("User3") while selecting "RED". -Claude (20 years ago, 15-Aug-05, to lugnet.robotics.rcx.robolab)
|
| |
| | container in a container error
|
|
I have been working with the RoboLab programs created by the Convict School to help me with a project of mine and to teach myself RoboLab. Recently I found the new work done by the school in 2002 (URL) download the files and placed them into the (...) (20 years ago, 13-Aug-05, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: RCX to RCX LNP
|
|
(...) AFAIK there is no way to receive Lego-Messages, except by editing lnp.c and adding that by hand. The only Lego-Messages that brickos knows of, are those from the remote control and the "send message" opcode (0xf7). It may be worthwhile to add (...) (20 years ago, 12-Aug-05, to lugnet.robotics.rcx.legos)
|
| |
| | AW: lejos program terminating immediately
|
|
Hi Jason, you have to loop within your main program, otherwise main() will be left. E.g. use while (true) { Thread.sleep (1000); } or, use a button listener, and exit when some button has been pressed. HTH, Jochen (...) (20 years ago, 11-Aug-05, to lugnet.robotics.rcx.java)
|
| |
| | RCX to RCX LNP
|
|
I'm trying to write a BrickOS program that I can use to check the voltage on other RCXs (which use standard firmware). I want to send the Get Battery Power command (0x30 and 0x38), and display the returned value on the display. Can anyone tell me if (...) (20 years ago, 10-Aug-05, to lugnet.robotics.rcx.legos)
|
| |
| | lejos program terminating immediately
|
|
Hi, I'm trying to use leJOS to display the current value of the rotation sensor I have hooked up to Sensor Port 1, but when I run the program, the RCX just beeps and ends the program immediately. Here's my code: import josx.platform.rcx.*; public (...) (20 years ago, 10-Aug-05, to lugnet.robotics.rcx.java)
|
