 | | using rotation sensor
|
|
Most of you are aware of the speed of the robot often causes parity in distance via the feedback of rotation sensors because of inertia. In our experiment, even with a robot with moderate speed. The parity seems to often occur right at the beginning (...) (19 years ago, 30-Nov-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx.legos)
|
| |
| | Re: Help me convert this train program to use events (NQC)
|
|
(...) Not to my knowledge. (...) Yes. The internal hardware between the 1.0, 1.5, and 2.0 bricks is identical with regards to the firmware, so any firmware will work on any RCX. (19 years ago, 29-Nov-05, to lugnet.robotics.rcx.nqc, FTX)
|
| |
| | Re: Help me convert this train program to use events (NQC)
|
|
(...) I got to try my program tonight. It wouldn't compile, claiming EVENTTYPEHIGH and EVENTTYPEPRESSED were undefined. Eventually I figured out that I had to set the target flag -TRCX2. My compilation command is getting more and more complicated: (...) (19 years ago, 29-Nov-05, to lugnet.robotics.rcx.nqc, FTX)
|
| |
| | Re: Help me convert this train program to use events (NQC)
|
|
(...) That would solve my current umbilical problems. At that length I'd actually be encouraged to shell out some spondulics. Steve (19 years ago, 28-Nov-05, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: Help me convert this train program to use events (NQC)
|
|
(...) And I've never had a problem with low battery firmware corruption... EXCEPT at BF while running the GBC trains. How often does the firmware check the battery level (it seems to be less often than the 3ms the other sensors are polled, based on (...) (19 years ago, 28-Nov-05, to lugnet.robotics.rcx.nqc)
|
