 | | 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)
|
| |
| | Re: location of NQC group?
|
|
(...) Personally I like the move to robotics.nqc I don't like the idea of splitting it up. Cross posting would make reading the groups very annoying. I'd say make the current one archive only putting a LARGE message like the rules pop up to new (...) (24 years ago, 9-Apr-00, to lugnet.admin.general, lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC Ignores based on your pbrink
|
|
(...) I agree wholeheartedly. I don't want to see people selling their bot code. It's all about sharing and learning. Dean -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Another makefile suggestion
|
|
This particular change would be useful in the lib directories. Instead of using this: SOURCES=memset.c strcmp.c ..... etc. Use this: SOURCES := $(wildcard *.c) Note the use of ':=', not '='. This will pick up ALL .c files in the current directory. (...) (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: NQC Ignores based on your pbrink
|
|
(...) This seems reasonable to me. Plus, it has the added benefit of being inherently open: source is all about "here's how to do this"; binaries are "here's a thing that does this". It's nice to encourage the first attitude. (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC Ignores based on your pbrink
|
|
(...) This first define (__RCX = 2) will happen automatically in NQC when you select RCX 2.0 as the target for compilation. Selecting an RCX 1.0 target will cause the symbol to be defined as 1. (...) I hope I don't have to add a __FIRMWARE symbol... (...) (24 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|
