To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.scoutOpen lugnet.robotics.scout in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / Scout / 212
211  |  213
Subject: 
Extensions to Scout via VLL
Newsgroups: 
lugnet.robotics.vll, lugnet.robotics.scout
Date: 
Mon, 25 Feb 2002 03:49:44 GMT
Viewed: 
60 times
  
Hi,
I am a newbe to lugnet so please forgive me for verboseness and the cross
post to the two groups, but my request seems to be across both.

My son has been using a scout & microscout in combination for 3 motor robots
for some time, using the scout SDK and/or RCXcc/NQC for control/programing.
The problem he has is that this produces somewhat unbalanced creations plus
he would like yet more motors. Rather than just buy the RCX for just one
more motor the thought occured to me that we might be able to add a simple
extension onto the scout using the VLL output. In short the idea was to
connect a PIC via a phototransistor to the scout VLL and decode say 16 of
the 127 VLL codes (many of which appear to be currently unused)to provide
say forward, back, stop, and brake, for four additional motors. So for the
four motors you would have a 16 pin PIC such as a 16F84 and a couple of
motor controler IC's such as L293's which should be buildable into a
reasonably small package.
My spare time for doing this sort of thing is somewhat limited so I have
been looking around on the internet to try and find if anybody has done
something similar with no success to date. There is a bit arround on
generating VLL but nothing on receiving it. So:
1/. Does anybody have a code snippit that receives VLL, PIC would be nice
but I would take anything?
2/. I found one site that talked about VLL as a sort of barcode, but I set
up a phototransistor on a CRO probe and I saw something very similar to what
is described but there is no stop bit, has anyone else seen this?
3/. Any comments/suggestions on which codes to use for the various motors,
and do I make them momentry in action as in the current use for motor C
(microscout) ie. you have to continuously send the code to keep the motor
turning, or should a code lock on until it gets another code to stop, which
is what I would have thought?

Thanks for your time.
Paul McMahon



1 Message 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