|
|
 | | Re: Communication with PC using NQC
|
| (...) Taking the example of the maze-walker, the PC software should be able to keep track of the position of the robot and direct it through the maze. (...) Yes, I looked at the code and it only needs a higher-level wrapper. (...) Yes, it does, (...) (25 years ago, 9-Nov-99, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
| | | | | Re: Long range IR mode.
|
| (...) Just scanned through Kekoka's excellent dissection of the ROM routines. Seems like system variable/register at address $ff7b contains the relevant Long range/Short range bit flag, ie. bit 0 toggles the IR range 0 = Long, 1 = Short. Could I (...) (25 years ago, 9-Nov-99, to lugnet.robotics.rcx.pbforth)
| | | | | Re: RCX motor voltage
|
| (...) I am using the motors that came with the RCX. (...) Hmmm - do you propose to ensure the delay in the relay circuit or programmatically? If in the circuit, how? (...) (25 years ago, 9-Nov-99, to lugnet.robotics.rcx)
| | | | | Re: RCX motor voltage
|
| Wes, relays would work pretty well. (Still, how much current do your motors draw???) The LEGO motors draw about .35 Amps (350 Milliamperes) You could connect two 5V coil relays , each with a diode in series with the coil, connected oppositely to (...) (25 years ago, 9-Nov-99, to lugnet.robotics.rcx)
| | | | | Re: Communication with PC using NQC
|
| (...) Could you be more specific on "querying its state" and "high-level commands"? If you're willing to write custom C++ code, you can pretty much do whatever you want on top of the rcxlib stuff from the NQC source base. Its pretty easy to send (...) (25 years ago, 9-Nov-99, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
|
