[Date Prev][Date Next][Thread Prev][Thread Next] - [Date Index][Thread Index][Author Index]

RE: rotor control question



Mike,
I started a project like that a while back and the problem turned out, not
to be the hardware.  The biggest difficulty was getting the unit to respond
to commands from off the shelf software (like Nova).  In order to do that
you have to know the computer-rotor controller interface protocol so that
your controller can respond appropriately.  Trying to get that kind of info
on the "standard" Kansas City Tracker was hard enough that I just lost
interest.  Without the interface data you have a nice manual rotor
controller.

On the bright side though -- check out the articles in  Dec 1998 (p34) and
Jan 1999 (p42) QST magazine on homebrew rotor controls.  They should answer
most of your questions.  I don't remember exactly where, but a recent
article (maybe one of the QST ones) told how to get your homebrew rotor
control to respond to FODtrack interface commands.  FODtrack is supported by
a lot of software now.

Good luck,

Ron
KC5ODM

-----Original Message-----
From: owner-AMSAT-BB@amsat.org [mailto:owner-AMSAT-BB@amsat.org]On
Behalf Of ka7hbb@janel.navicom.com
Sent: Wednesday, March 17, 1999 8:06 AM
To: amsat-bb@AMSAT.Org
Subject: [amsat-bb] rotor control question


Good morning to the BBS.
   I'm afraid I'm not a programer or even a real good technician but
a question about rotor interfaces keeps popping into my head.
   How hard would it be to build an interface for rotor control
using a "basic stamp" approach?
   From the little I've read they come with A>D, D>A, I/O all on one
chip basically.   Could one be set up to read just the numerical
output of some of the current tracking programs?  Then read a A>D
line from the meter of the rotor control  and command the output of
the appropriate line to enable the up / down, left / right lines for
relay control of the rotor?
   I haven't read too much about the various interfaces and don't
remember if any of them use this type of controller or not.
One would think it might be the cheapest way to create an easily
re-producable interface, but with my back ground it's only a guess.
   I'd be interested in hearing from anyone's who's attempted
something like this.
     Thanks, Mike  KA7HBB

ka7hbb@navicom.com
mike_nason@hp.com

----
Via the amsat-bb mailing list at AMSAT.ORG courtesy of AMSAT-NA.
To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org

----
Via the amsat-bb mailing list at AMSAT.ORG courtesy of AMSAT-NA.
To unsubscribe, send "unsubscribe amsat-bb" to Majordomo@amsat.org



AMSAT Top AMSAT Home