 | | (canceled)
|
|
|
| |
| | Re: Help with RCX.pm
|
|
(...) Aha! OK, sounds like the docs are out of sync with the code. IIRC, John renamed the module from RCX to LEGO::RCX a while back, which means that the new() constructor is actually now in the LEGO::RCX package and no longer in the RCX package. (...) (24 years ago, 14-Apr-00, to lugnet.robotics.rcx)
|
| |
| | Re: Help with RCX.pm
|
|
"Todd Lehman" <lehman@javanet.com> schrieb im Newsbeitrag news:FsyM2E.KoA@lugnet.com... (...) i used the following: use RCX; $rcx = new RCX(); as described in the doc-file that comes with RCX.pm. thanks, Clemens (24 years ago, 14-Apr-00, to lugnet.robotics.rcx)
|
| |
| | Re: Q: Determining state of outputs
|
|
(...) Yes, there is a 'data source' for motor status. I never bothered figuring it all out, so there isn't a defined API for it, but you can add it yourself: #define MotorStatus(motor) @(0x30000 + (motor)) use motor 0 for output A, 1 for B, 2 for C. (...) (24 years ago, 14-Apr-00, to lugnet.robotics.rcx.nqc) !
|
| |
| | Re: Q: Determining state of outputs
|
|
(...) I'm not the expert on this but... I've been playing with firmware 2.0 and I think you can read the state of your sensors directly. (The same way you read the Battery level? Dave?) Hopefully Dave will answer you for sure. Dean -- Coin-Op's For (...) (24 years ago, 13-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Q: Determining state of outputs
|
|
Hello everybody! For the building of my next robot an answer to the following question could be very helpful: Is there any possibility in NQC to get the state of an output (on, off, direction). While running a program I would like to control one (...) (24 years ago, 13-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Help with RCX.pm
|
|
(...) Clemens, What are you using to invoke the new() constructor? Are you using LEGO::RCX->new(...) or LEGO::RCX->new("LEGO::RCX", ...) or new LEGO::RCX(...) or something else? --Todd (24 years ago, 13-Apr-00, to lugnet.robotics.rcx)
|
| |
| | (canceled)
|
|
|
| |
| | Help with RCX.pm
|
|
when using the rcx.pm i only recieved the following error: "can't find method new in module rcx" it seems to me that perl finds the LEGO::RCX module but not its method "new". what am i missing? thanks for any suggestions! (24 years ago, 12-Apr-00, to lugnet.robotics.rcx)
|
| |
| | Re: USB->Serial Converts and IR Tower
|
|
(...) downloaded the latest drivers (Intel based). Also obtained a good troubleshooting doc to determine whether the S9 is configured correctly. Will gladly email to any interested. Problem: Having trouble getting the IR tower to talk to the RCX. I (...) (24 years ago, 12-Apr-00, to lugnet.robotics, lugnet.robotics.rcx)
|
| |
| | problems with random function for WinLegOS
|
|
hy !!! If have compilerproblems with random-function " undefined reference". i use kernel 0.2.3 If had read something about this problem but any solution are for cygwin or linux. i hope anyone can help me marc (24 years ago, 12-Apr-00, to lugnet.robotics.rcx.legos)
|
| |
| | Gdb & LegOS. Progress made & help wanted
|
|
Hi All: I've been trying to get gdb going with legOS for some time now. I've made some progress, but for various reasons, I'm now stuck. I thought I'd post this plea for help. Check this page: (URL) then email me or post a reply with your ideas. (...) (24 years ago, 12-Apr-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Lego Laser
|
|
(...) A resistor+zener fixes that nicely. Dw (24 years ago, 12-Apr-00, to lugnet.robotics.rcx)
|
| |
| | Controlling RCX with game controller
|
|
Hi everyone, I have developed a program for Windows 95/98/2000 that will allow you to control your RCX with a game controller via the infrared transmitter that comes with the RIS set. The program is called Remote Control X. One key feature is the (...) (24 years ago, 12-Apr-00, to lugnet.robotics.rcx)
|
| |
| | no rule to make target Main.o
|
|
I just unzipped emulegos_unix.zip to my RedHat 6.x system. I typed: export RCX_SOURCE=ir-rover make and got: make: *** No rule to make target `Main.o', needed by 'ir-rover^M'. Stop. Anyone know what I failed to do? (24 years ago, 12-Apr-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Lego Laser
|
|
(...) One thing to make sure of is that the RCX outputs are not constant. If you power the pbrick with external power it can shoot to over 9.5 volts. Something to keep in mind. Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 12-Apr-00, to lugnet.robotics.rcx)
|
| |
| | Lego Laser
|
|
Using pointers (pun) from a previous post, I have been building a laser for my robots. I used a miniature laser pointer from Sam Goody which was only $10. The hardest part so far was chopping up the pointer to get out the guts. It turned into a (...) (24 years ago, 11-Apr-00, to lugnet.robotics.rcx)
|
| |
| | Re: location of NQC group?
|
|
(...) Safest thing is a multi-step process: 1. Announce that a new group/list lugnet.robotics.nqc will soon be replacing lugnet.robotics.nqc (i.e., a "heads-up"). 2. [A day or so later] Create lugnet.robotics.nqc and associated web areas and mailing (...) (24 years ago, 9-Apr-00, to lugnet.admin.general, lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC Ignores based on your pbrink
|
|
(...) Yep, you can #ifdef however you want, and NQC supports -D and -U options on the command line that allow you to define (or undefine) symbols before the compile takes place. This is handy if you're using Makefiles, but even in an ordinary shell (...) (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC Ignores based on your pbrink
|
|
I definitely intended to mean portable source. And that the "__FIRMWARE" would be used in compiler directives rather than in the code. It is a simple matter for me to define my own __FIRMWARE (or anything else, right?) and do #ifdef's to my heart's (...) (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|
