 | | Re: Rechargable battery questions
|
|
I use an external battery pack whenever possible/practical. It has 8 (not 6) NiMh cells, providing a total of 9.6 volts. Works fine. Actually, it produces a little more power than ordinary batteries. You need a socket for external power on the RCX (...) (25 years ago, 15-Jan-00, to lugnet.robotics.rcx)
|
| |
| | Re: Rechargable battery questions
|
|
(...) I prefer rechargeable alkalines myself (such as Rayovac Renewal). They have the same nominal cell voltage as alkalines, charge quickly, have excellent shelf life, and no memory effect. The downside is that their total charge is somewhat less (...) (25 years ago, 15-Jan-00, to lugnet.robotics.rcx)
|
| |
| | Re: NQC 2.1 b2 in beta test
|
|
(...) the exec (...) The answer isn't pretty.... As near as I can tell (sorry, not much of a Windows expert), the command line gets passed in its entirety to the executable, which then is responsible for parsing it into separate arguments. For the (...) (25 years ago, 15-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC default output file
|
|
(...) I just added the error check to nqc. I haven't changed the directory yet, though. Using the source directory was strictly from laziness. Assuming there aren't massive objections, I'll switch to using the current directory. Dave Baum (25 years ago, 15-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Rechargable battery questions
|
|
Greetings, I am yet another lucky person graced with an RIS this holiday season. I already seem doomed to buying more Lego sets for extra parts. I was quickly thwarted trying to build examples in Jonathan Knudsen's book which I assume is based on (...) (25 years ago, 14-Jan-00, to lugnet.robotics.rcx)
|
| |
| | Mindstorm firmware C compiler for W95 platform ready for download.
|
|
Having trouble getting the Hitachi H8 Mindstorm firmware compiler to run on a W95 platform? Francesco Ferrara has a ready to run installation on his website! (URL) . Download, un-rar, add c:\qc\bin to your path and you're all set. You can have your (...) (25 years ago, 14-Jan-00, to lugnet.robotics.rcx.legos, lugnet.robotics)
|
| |
| | Re: NQC 2.1 b2 in beta test
|
|
(...) The same problem was already present with the b1 (I had asked about it in this newsgroup but got no reply). Also, I don't think it is related to the parameters. I have now checked the exec call of RcxCC with a debugger and found this is the (...) (25 years ago, 14-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 b2 in beta test
|
|
(...) Hmmm - the only reason I can think of for this would be if RcxCC is using one of the deprecated options that were removed in 2.1 (-o, -e, and -s which were replaced by -O, -E, and -S). If Mark can confirm which (if any) of these options are (...) (25 years ago, 14-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: offtopicy sort of thing
|
|
(...) It's offtopic in .nqc, but not in lugnet.robotics in general. (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: offtopicy sort of thing
|
|
I think that's a really good idea. I tried it, and found out that the motor recieving power spins slower than the motor you spin. This is about 4:3. This could be a really good speed reduction technique that doesn't use gears, or you could power (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC default output file
|
|
(...) I don't want the outfile to go where the executable is -- I want it to go to the current working directory. So nqc goes in /usr/local/bin, and I can run it from "binaries" directory on source files that might be located elsewhere (the test.nqc (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC default output file
|
|
I don't think it's nonintuitive. I think it makes sense to have the output go to the same directory as the input. That way you can have a directory set up for the executable with only read/execute permissions, and yet have all of your source & (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC default output file
|
|
I was checking to see if NQC already does have an option to spit bytecodes to stdout (-L would work, if rcxcomm would understand the format) and I came across something that seems nonintuitive to me. The default output file is "named the same as the (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 b2 in beta test
|
|
(...) If this is done, the compiler should have an option to spit out compiled bytecode on stdout, and the rcxcomm program should have a matching option to accept bytecodes on stdin and send them to the rcx. And then there should be a wrapper that (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | More details : "Exploration Mars" and "Ultimate Accessory Set" for the RCX available in march ?
|
|
Hi again all, Thanks to Jesper Kjaer, here is posted more information and detailled pictures for these to sets. Please see : (URL) large pictures posted). About Exploration Mars (#9736) : - Unfortunately, this set doesn't seems to contain a cam... - (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx)
|
| |
| | LegOS Firmware Problem
|
|
I'm using LegOS 0.2.3 under a Slackware 7 Linux install and everything seemed to work perfectly to begin with. I've recently tried altering the kernel a bit -- everything compiled fine as far as I could tell. When I tried to use firmdl3 to download (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.legos)
|
| |
| | RE: TpForth Project ?
|
|
(...) The basic problem, Mark, is time. I just don't have the time to properly support a compiler for three platforms. I can barely keep up with the demands pbForth makes of my spare time. I write strict ANSI-C all day long, and pbForth is a bit of (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: TpForth Project ?
|
|
(...) The basic problem, Mark, is time. I just don't have the time to properly support a compiler for three platforms. I can barely keep up with the demands pbForth makes of my spare time. I write strict ANSI-C all day long, and pbForth is a bit of (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: NQC 2.1 b2 in beta test
|
|
(...) I think NQC should be strictly a compiler. It seems like it would be more manageable for both developers and users if the RCX communication pieces were in a separate executable. This change should make NQC completely portable (if there is such (...) (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC 2.1 b2 in beta test
|
|
(...) The beta does not seem to work with RcxCC. All it does is display the parameters for NQC and then exits. No compile. --- DonC donc@cccd.edu (25 years ago, 13-Jan-00, to lugnet.robotics.rcx.nqc)
|
