 | | Re: Light Sensor help
|
|
I am posting this to the general robotics newsgroup (I hope) (...) The answer to this bit is easy - the RCX reads the sensors once every 3 mS under the Lego firmware. (I have no idea what the LegOS kernel does.) The purpose of this post however, is (...) (23 years ago, 9-Apr-02, to lugnet.robotics)
|
| |
| | Re: Light Sensor help
|
|
(...) Yes, I just recently did some timing tests, using that exact method. Each bytecode takes 2.9 +/- .2 ms to execute, as near as I can tell. This appears to be independent of which bytecode it is (though I did not test any that I really expected (...) (23 years ago, 9-Apr-02, to lugnet.robotics)
|
| |
| | Re: Light Sensor help
|
|
(...) Wow! That is very interesting. I wonder if the whole thing is synchronous and based on the 3mS sensor read cycle? This would mean that every process gets one of its byte codes "done" during this periodic 3mS spring-clean cycle. I guess the (...) (23 years ago, 9-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)
|
| |
| | 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
|
|
Yuck How much time is the brick spending sleeping then? Roland (...) (23 years ago, 10-Apr-02, to lugnet.robotics)
|
| |
| | 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
|
|
(...) Hrm. Looks like I need to be more thorough with my multi-task timing tests... my results (which seemed to show only one task getting run in any given timeslice) differ from yours. Unfortunately, I didn't keep good notes of all my measurements, (...) (23 years ago, 10-Apr-02, to lugnet.robotics)
|
| |
| | Re: Light Sensor help
|
|
"Steve Baker" <lego-robotics@crynwr.com> wrote in message news:3CB39250.8CC16B...ail.net... (...) what (...) you (...) storage (...) If you need to use a lookup table where you know the values of the table at compile time, using a case statement (...) (23 years ago, 10-Apr-02, to lugnet.robotics)
|
