Subject:
|
Re: Ir transmission
|
Newsgroups:
|
lugnet.robotics.rcx.pbforth
|
Date:
|
Sat, 17 Apr 1999 02:51:25 GMT
|
Reply-To:
|
robots@=StopSpammers=jpsc.co.uk
|
Viewed:
|
1812 times
|
| |
|
|
> As far as multitasking goes, we really need to figure
> out how many tasks we need. There are essentially six tasks in the RCX as far
> as I can tell. They independently handle things like motors, sensors, timers,
> RCX code, etc.
Well, in the spirit of FORTH there should be no finite number, just create and
destroy them on the fly as and whan you need them. I have been wandering around
the internet looking and found that hForth has one already:
\ hForth multitasker
\
\ Originally written by Bill Muench.
\ Adapted to hForth by Wonyong Koh
\
\ Usage:
\ HAT ( user_size ds_size rs_size "<spaces>name" -- )
\ Run-time: ( -- tid )
\ Create a new task.
\ BUILD ( tid -- )
\ Initialize and link new task into PAUSE chain.
\ ACTIVATE ( tid -- )
\ Activate the task identified by tid. ACTIVATE must be used
\ only in definition. The code following ACTIVATE must not
\ EXIT. In other words it must be infinite loop like QUIT.
\ .TASKS ( -- )
\ Display tasks list in status-follower chain.
\ SLEEP ( tid -- )
\ Sleep another task.
\ AWAKE ( tid -- )
\ Awake another task.
\ PAUSE ( -- )
\ Stop current task and transfer control to the task of which
\ 'status' USER variable is stored in 'follower' USER variable
\ of current task.
\ STOP ( -- )
\ Sleep current task.
Looks like everything I could need there.
--
John Cooper, Wallington, UK
|
|
Message is in Reply To:
 | | RE: Ir transmission
|
| (...) I think its around 16 Mhz for the crystal and 4 MHz for the cycle time. I think there is a msec timer buried in the OC1A handler (see Kekoa's disassembly) I agree that we want something to trigger a run flag instead of having to check the (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
|
9 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
