Subject:
|
Re: multiplexor and legOS
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Tue, 5 Feb 2002 04:08:53 GMT
|
Viewed:
|
2633 times
|
| |
|
|
Since I'm now fairly sure that i've got the timing taken care of I'm wondering
if the power cycling that ds_handler does is somehow causing the problem? I
thought I might take control of this stuff in my test code. I assume if I set
the sensor for passive and then write procedures (in assembly) to turn on and
off the power to the mux things should be safe? Would there be a problem when
ds_handler attempted to read the senor? I assume it wouldn't work but
currently I'm just trying to get the switching going.
I looked through ds_handler trying to pick out the assembly that would be
needed but my attempts just end in a locked RCX. If anyone farmilar with H8
assembly can post the few lines of assembly to power a sensor on and off that
would be very helpful.
thanks,
mark
|
|
Message has 1 Reply:
 | | Re: multiplexor and legOS
|
| Ok, my last port didn't make much sense let me try that again. for an active sensor ds_handler will periodically power the sensor off to read the value. The standard firmware does this to but at a different interval. I'm wondering if this is part of (...) (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
| | Re: multiplexor and legOS
|
| (...) It looks like the semaphore task_sm should prevent another task from being scheduled if I hold it for the length of the train. I've now tried this as well as incresing the timeslice to 100ms. It looks better but still is not consistent. Since (...) (23 years ago, 5-Feb-02, to lugnet.robotics.rcx.legos)
|
19 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
