 | | TIMER 0 is flakey
|
|
Hi Ralph, It looks like TIMER 0 is hosed in v1.05. Take a gander at this: ----- : time RCX_INIT 0 0 TIMER_SET 32 0 DO 0 TIMER_GET . LOOP ; ok time 0 0 0 0 0 0 0 0 0 0 0 0 1 1 -32639 -32639 130 130 -32638 131 131 131 -32637 132 132 132 133 -32635 (...) (25 years ago, 27-Jul-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | Do the high resolution timers work?
|
|
Hi Ralph, Are timer_SET and timer_GET working? I can't seem to get any non-zero values from them: RCX_INIT ok 0 FFFF timer_SET ok 0 timer_GET . 0 ok Am I missing something? Thanks, Jonathan (25 years ago, 27-Jul-99, to lugnet.robotics.rcx.pbforth)
|
| |
| | RE: Couple of questions about the Mindstorms software
|
|
<Silly fly thread snipped...it WAS funny though> (...) Well, pbFORTH DOES have the ability to emit arbitrary bytes by the use of the EMIT word. And it has the ability to receive arbitrary bytes since that's how the terminal program talks to it. It's (...) (25 years ago, 20-Jul-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | Re: Couple of questions about the Mindstorms software
|
|
(...) LOL! BTW, speaking of viruses (in the good sense) and on-the-fly bytecode compiling, do any of the RCX packages currently support the spontaneous exchange of high-level code between two or more RCX bricks? It seems like it would almost be a (...) (25 years ago, 19-Jul-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| |
| | [ANN] pbFORTH 1.0.5 for RCX
|
|
Finally, I have got pbFORTH to where I can release it again. It now has: - A simple cooperative tasker - A marker word so you can erase things easily - Support for poweroff - High res (10msec) count down and stop timers - Various and sundry fixes (...) (25 years ago, 21-Jun-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
