To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.roboticsOpen lugnet.robotics in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / 18302
18301  |  18303
Subject: 
Re: Several hardware questions.. Laser link Hardware expansion n' more
Newsgroups: 
lugnet.robotics
Date: 
Fri, 5 Jul 2002 14:24:57 GMT
Viewed: 
647 times
  
I've been working on just such a robot.  (two RCXs, two rotation sensors, four light sensors, and two touch sensors)

Currently, my biggest problem has been communicating between RCXs.  I keep getting collisions with my messages.

I've had to limit the messages to one direction.  That seems to be working better.

Steve

----- Original Message -----
From: "John Barnes" <barnes@sensors.com>
Date: Fri, 5 Jul 2002 12:17:12 GMT
To: lugnet.robotics@lugnet.com
Subject: Re: Several hardware questions.. Laser link Hardware expansion n' more

problem. As an example, if you are building a tracked platform with left and
right side rotation sensors, the easiest way to partition the task is to use
two RCXs communicating via their infrared ports set to low power. One RCX is
set up as being responsible for platform movement (controlling the main
drive motors and handling the rotation sensor inputs to close the tread
speed loops) while the other takes care of the higher level control and
navigation functions. This simplifies the communication tasks to motor
control commands being sent one way and motor status reponses being sent the
other. Low level bump sensor overrides then also route into the motor
control RCX. It often seems to me that six sensor ports and six motor ports
seems more than twice as capable as three and three.

JB



--
_______________________________________________
Talk More, Pay Less with Net2Phone Direct(R), up to 1500 minutes free!
http://www.net2phone.com/cgi-bin/link.cgi?143



Message has 3 Replies:
  Re: Several hardware questions.. Laser link Hardware expansion n' more
 
This is an interesting aspect of using two RCXs. My only experience is with NQC and the single byte "Message" function, but I have succeeded in making the communication link bi-directional and reliable. I simply create a process in the "master RCX" (...) (22 years ago, 5-Jul-02, to lugnet.robotics)
  Re: Several hardware questions.. Laser link Hardware expansion n' more
 
could not the voltage level deside what relays should be turned on for instance on port 1? Now it might go wrong if the battery turns to be bad. ----- Original Message ----- From: "Steve Hassenplug" <hassenplug@mail.com> To: (...) (22 years ago, 5-Jul-02, to lugnet.robotics)
  Re: Several hardware questions.. Laser link Hardware expansion n' more
 
(...) In my system (one RCX and three Scouts), I had one 'master' and three 'slaves'. The rule was that no slave is allowed to talk unless first addressed by the master. I've finally gotten around to writing up this setup and putting it on the web. (...) (22 years ago, 9-Jul-02, to lugnet.robotics)

4 Messages in This Thread:



Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    
Active threads in Robotics

 
Verified and Trusted Team of Hackers
13 hours ago
Custom Search

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