 | | NQC Ignores based on your pbrink
|
|
Dave Can you setup NQC to automatically ignore things a pbrink doesn't understand? For example The scout. I have a program that I use in my 2 RCX's and my 1 scout. But Constantly have to /* */ the offending code for the scout. Is there some way we (...) (25 years ago, 8-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: problem building bugbot3.nqc in cybermaster
|
|
(...) Why not do something like this? #ifdef __RCX SetSensor(...) ; #endif (25 years ago, 8-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC in Boston University Linux :)
|
|
(...) cool :) Heh, did you look at 6.2 yet? I installed it today, though I haven't noticed any major difference yet... :) Dan btw, since you're at BU, have you ever heard of Three Kingdoms, or more commonly, 3K? ;) (25 years ago, 7-Apr-00, to lugnet.robotics.rcx.nqc, lugnet.off-topic.geek)
|
| |
| | NQC in Boston University Linux :)
|
|
So, when we release BU Linux R1 next Tuesday [1], it will be the first [2] Linux distribution to ship with NQC included. (URL), if you care. [1] or maybe Wednesday or Thursday. Hopefully Tuesday. Depends on the wheels of bureaucracy. [2] not (...) (25 years ago, 7-Apr-00, to lugnet.robotics.rcx.nqc, lugnet.off-topic.geek)
|
| |
| | Re: problem building bugbot3.nqc in cybermaster
|
|
(...) Just delete the SetSensor() lines. CyberMaster only supports touch sensors, so the entire sensor configuration thing isn't needed...in fact CyberMaster doesn't support some of those bytecodes (which is why many of the constants and functions (...) (25 years ago, 3-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | problem building bugbot3.nqc in cybermaster
|
|
When I try to compila bugbot3.nqc (the code of the Dave's wonderfull book) using my cybermaster as target, the compiler return twice the following error: SENSOR_TOUCH not defined I used the command line nqc -TCM bugbot3.nqc with NQC 2.3 thanks in (...) (25 years ago, 3-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: sending output to LCD possible?
|
|
(...) Not possible with the existing RCX firmware. However the RCX 2.0 firmware (currently in early-alpha) does support displaying a variable (and almost anything else) on the LCD. These operations will be available in NQC...but only when targetting (...) (25 years ago, 3-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | sending output to LCD possible?
|
|
I skimmed through the NQC docs but I didn't see anything about sending messages to the display on the RCX. Is it possible? More specifically, sending the value of a variable to the display? I have a little robot that I plan to use to count things, I (...) (25 years ago, 3-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC and RIS2.0 Firmware
|
|
(...) I found the problem... When verifying the checksum, the ROM scans [8000, cc00). Since it zeros out this area initially, this would indeed reflect the checksum of the firmware, provided it is less than 4400 bytes long (in hex). NQC sums the (...) (25 years ago, 2-Apr-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC and RIS2.0 Firmware
|
|
(...) I've been looking at that for most of today. The 2489 is basically the last packet to go to the RCX, and the error is a "checksum error" coming back from the RCX. As far as I can tell, nqc breaks with any firmware file bigger than 20K (...) (25 years ago, 2-Apr-00, to lugnet.robotics.rcx.nqc)
|
