 | | Re: Multitasker test script
|
|
Perhaps I should not have stripped all the comments for speed :) \ The rationale for the delay above and the delay after the IR flash is \ that the message is 77 bits of 417 microseconds each, a total \ transmission time of 32 milliseconds, the (...) (25 years ago, 13-May-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Multitasker test script
|
|
(...) It was this line that trashed the task chain when the power button was pressed, I thought I'd checked it a few times but perhaps it was something else. (...) Yes. What I really want is an equivalent of SendMessage in NQC (which maps to opcode (...) (25 years ago, 13-May-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Rom sensor read routine
|
|
Hi Kekoa, (...) I am fixing this right now. (...) The current legOS sensor read cycle is this (i=illuminate, c=A/D conversion) S1: iii iii iii ccc S2: ccc iii iii iii S3: iii ccc iii iii S4: iii iii ccc iii If you find your sensor 2 readings to be (...) (25 years ago, 2-May-99, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Multitasker test script
|
|
John, I've been looking at your ping routine and note the following... Even if FF EMIT did not block, the wait makes things irrelevant. At 2400 baud, the FF is out the port within 4 msec. In fact, if EMIT did not block, you could probably wait jsut (...) (25 years ago, 13-May-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | FORTH documentation on line
|
|
No, it's not documentation for pbFORTH - yet. I have found a decent book on line, it is Tim Hendtlass's Real-Time FORTH book. It is really geared for FPC, a dialect that is available for the PC, but the sections on numbers, stack manipulation, (...) (25 years ago, 13-May-99, to lugnet.robotics.rcx.pbforth)
|
