 | | Re: direct manipulation of bits in RCX registers using NQC —
|
| | | (...) I agree with Steve that the code samples you posted are probably BrickOS. Now to acheive what you want, it might be a waste of power, but you could always blank off the light itself with a peice of black card or thin black packing plastic. If (...) (19 years ago, 13-Sep-05, to lugnet.robotics.rcx.nqc)
|
| | | |
| | | | | Re: direct manipulation of bits in RCX registers using NQC —Mathew V. Jones
|
| | | | Hey, Thanks for all the helpful responses, everyone. Brian: (...) I guess that "firmware" must be the code that tells RCX how to interpret user instructions (NQC, C, IC, opcodes, or whatever), and convert them to binary machine-specific code. Right? (...) (19 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: direct manipulation of bits in RCX registers using NQC —Brian Davis
|
| | | | (...) Correct. A NQC command (say, "Wait(10);") is converted to one or more "bytecodes" (in this case, one bytecode, namely a string of 4 bytes (0x43 0x02 0x0a 0x00), the first of which is a command (0x43) while the following three are information (...) (19 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | IR-based proximity measurement —Mathew V. Jones
|
| | | | I'm changing the subject line in the middle of the thread. Wonder what the server will do with that... I tried out Brian's "Max-picking" ping method, as well as a few other things. Here's a summary of what I found: 1) If the active sensor readings (...) (19 years ago, 16-Sep-05, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: IR-based proximity measurement —Ralph Toepper
|
| | | | (...) i have downloaded the SerialPing.nqc program hoping to get an easy to use proximity sensor. i have modified it to work with only one light sensor. but it shows always -90 on the display. ok, sometimes -89 too. can anybody tell me, what i did (...) (18 years ago, 9-Jun-06, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: IR-based proximity measurement —Brian Davis
|
| | | | (...) Well, there were a couple of typos, but only one I found that was critical. If you are using a "max-picking LIDAR" method, you do *not* want to divide by the number of samples. The variable "eyeon" in your code should end up with the brightest (...) (18 years ago, 9-Jun-06, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: IR-based proximity measurement —Ralph Toepper
|
| | | | Brian, thanks for your advice. it has told me what is happening physically. i build a one shot measurement program to answer your questions. here is the measurement result: Distance to wall: 26 cm (at night) 7740 7696 7666 7641 7639 7613 7613 7593 (...) (18 years ago, 11-Jun-06, to lugnet.robotics.rcx.nqc)
|
| | | | |
| | | | | | Re: IR-based proximity measurement —Brian Davis
|
| | | | (...) You're welcome - it's a fun problem. At least partially because it's one of the few times I've had to worry about the speed of bytecode execution under the standard firmware (see below). (...) Given what you are transmitting and how you are (...) (18 years ago, 11-Jun-06, to lugnet.robotics.rcx.nqc)
|
| | | | |
