Subject:
|
Re: Strange problem using 2 active sensors at the same time with 0.2.4
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Thu, 16 Nov 2000 08:14:26 GMT
|
Viewed:
|
1340 times
|
| |
|
|
I also have a LegOS 0.2.4 program that uses two rotation sensors on
input ports 1 and 3 as well as another active sensor (the Technostuff
Dual IRPD sensor) on port 2. All work flawlessly, no counter drift
noted on the rotation sensor.
Perhaps it is a problem with your LegOS build? Did some of the dsensor
files from 0.2.3 get mixed in with the 0.2.4 files?
Dave
Michael J Ash wrote:
>
> On Tue, 14 Nov 2000, Carsten Müller wrote:
>
> > In a actual project, i'm using the following setup:
> > Input:
> > 1 Rotation sensor (steering)
> > 2 nc
> > 3 Rotation sensor (distance measuring)
> >
> > Output:
> > A drive motor
> > B nc
> > C steering motor
> >
> > If more than one sensor is set to active, only the first (steering) one
> > can be used to read 'real' values. The reading from the second
> > (distance) rotation sensor are completely out of track toggling
> > 'randomly' around the starting value. This behavior is independent of
> > the state of the motors but is influenced by the state of the sensors
> > (active || passive). A second current sink on one of the other sensor
> > ports disables the formerly working one. This behavior is independent
> > from the state of the batteries. I've tested it with freshly loaded NiMh
> > and with nearly empty NiCd (not with normal batteries) and also with two
> > other RCX's.
> >
> > If i use legOS-0.2.3 from http://www.noga.de/legOS/legOS-0.2.3.tar.gz
> > with dsensor-new.c instead of dsensor.c everything works as expected.
> >
> > now my question:
> > Is there a patches against 0.2.4 which solves this very strange problem
> > with active sensors?
>
> I don't have a solution, but I thought I'd throw in my experiences. I
> curently have a robot that uses two rotation sensors, and I've never had
> trouble with them under either 0.2.3 or 0.2.4. I looked through your code
> briefly and couldn't find anything obviously wrong. You do a
> ds_rotation_set() before a ds_rotation_on(), and mine are in the opposite
> order, but I don't think that would really cause the problems that you
> describe. You might try switching them around, but don't expect results.
> Otherwise everything seemed fine, but I didn't have time for a thorough
> examination. Given my experiences I would expect it to be something
> strange in your code that was ok under 0.2.3 but that broke under 0.2.4
> rather than an actual problem with the OS.
|
|
Message has 1 Reply:
Message is in Reply To:
5 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
|
|
|
|
