To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / 3039
3038  |  3040
Subject: 
Re: BrickOS Threading...
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Fri, 13 Dec 2002 19:24:40 GMT
Viewed: 
2975 times
  
Joe,

I will take a look at your function tonight and try to get it into
systime.c right away.  Maybe we can rig up a change that will cause the
"glitch" to occur more often (increment sys_time twice per tick, or
something)

Maybe a special kernel build for testing purposes that
increments the lower sys_time word by 0x4000 instead
of 1.  This will greatly increase the opportunity for this
glitch to occur (from once every 65 seconds to once every
4ms.)  You might need to disable certain other parts of the
kernel since they might find this fast-fowarding of time
objectionable.

Thanks for looking into this!

Mark



Message is in Reply To:
  Re: BrickOS Threading...
 
Steve, I checked in some changes this morning (into cvs) to put the motor controller back at the 1 ms interval. However, I want to complete the get_sys_time() updates that Mark Riley has proposed; so that can be tested as well. I am not sure when (...) (22 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)

7 Messages in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR