 | | 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 (...) (25 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 (...) (25 years ago, 13-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | 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 (...) (25 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 (...) (25 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 (...) (25 years ago, 9-Apr-00, to lugnet.robotics.rcx.nqc)
|
