 | | Re: Reading sensors at equal intervals. —Kekoa Proudfoot
|
| | | (...) By standard firmware, I assume you mean using the byte codes ala NQC or something similar. If you only want semi-precise timing, you can use the wait opcode to delay for approximately 100 ms between sensor samples. If you want something more (...) (26 years ago, 25-Apr-99, to lugnet.robotics)
|
| | | |
| | | | | Re: Reading sensors at equal intervals. —Dennis Clark
|
| | | | (...) I though that the four "Timer()" values read out in 100ms increments only. Is there a way to get a 1ms timer with NQC? thanks, DLC (26 years ago, 25-Apr-99, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Reading sensors at equal intervals. —Kekoa Proudfoot
|
| | | | (...) You are right, the timer values as seen by the firmware are in 1/10ths of a second. I lost myself in H8-land, which has a 1 ms timer that gets divided down before being seen by the firmware. -Kekoa (26 years ago, 25-Apr-99, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Reading sensors at equal intervals. —S. Crawshaw
|
| | | | (...) <snip> (...) That looks like a "no" then... How does the timing of tasks work? I seem to recall reading somewhere that the firmware executes the tasks in sequence - is there any timing element to this, or does it just do task 1, then (...) (26 years ago, 26-Apr-99, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Reading sensors at equal intervals. —Kekoa Proudfoot
|
| | | | (...) IIRC, it preferentially executes a single instruction received from the IR connection, otherwise takes the next instruction from the next task and executes that instead. (...) Probably. I don't think LegOS supports (what I'd call) a software (...) (26 years ago, 26-Apr-99, to lugnet.robotics)
|
| | | | |
