|
|
 | | RoboLab updates
|
| If you only read the Robolab newsgroup then you may have missed a helpful post that did not appear in the RoboLab newsgroup. If so, then look at: "Robolab 2.5 patches" (URL) (23 years ago, 10-Apr-02, to lugnet.robotics.rcx.robolab)
| | | | | Re: Light Sensor help
|
| (...) Well, I can think of lots of reasons why you might want trig - if you know what direction you are moving in and how far you've travelled, trig will let you figure out where you are relative to where you started. Using an NQC lookup table isn't (...) (23 years ago, 10-Apr-02, to lugnet.robotics)
| | | | | Re: Light Sensor help
|
| Yuck How much time is the brick spending sleeping then? Roland (...) (23 years ago, 10-Apr-02, to lugnet.robotics)
| | | | | Re: Light Sensor help
|
| (...) Yes, it all appears to be synchronous. However, only one bytecode instruction is run in any given 3ms; any active tasks interleave their instructions. If you have two tasks running, they will each be getting an instruction every other 3ms. If (...) (23 years ago, 10-Apr-02, to lugnet.robotics)
| | | | | Re: Light Sensor help
|
| "T. Alexander Popiel" <lego-robotics@crynwr.com> wrote in message news:20020409200644....eep.com... (...) time (...) loop (...) I did some similar tests and found similar results. The results held up well up to about 3 tasks, but by the time we (...) (23 years ago, 9-Apr-02, to lugnet.robotics)
|
|
