Order Tray | Contact Us | Home | SIG Lists

[aprssig] Rotor control

scott at opentrac.org scott at opentrac.org
Mon Jun 19 22:18:28 UTC 2006


Cool, thanks for checking that out.  What if you feed it a bunch of
unrelated text?  Does that bother it?  I'm curious if I need to bother
making sure that the tracker never outputs anything else (e.g., waypoints or
incoming messages) in rotor control mode.

I figure I'll implement both a manual control and tracking mode, so you'll
be able to aim the rotor remotely using APRS messages, or change the station
being tracked.

I should have the second batch of Tracker2 prototype boards ready soon...
I'll try to make sure at least one of those makes it to someone who was an
appropriate rotor system to test with.

Scott
N1VG 

> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org 
> [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Ron Tonneson
> Sent: Monday, June 19, 2006 3:10 PM
> To: TAPR APRS Mailing List
> Subject: Re: [aprssig] Rotor control
> 
> I just tried it on my Rotor-EZ.
> 
> AP1080<CR> will rotate the antenna to 80 degrees.
> 
> AP1090; will store 90 degrees in the Rotor-EZ memory.
> 
> AM1; will rotate the antenna to the value stored with the 
> AP1XXX; command.
> 
> AM1; is NOT needed after AP1xxx<CR>
> 
> Note the the AP and AM must be upper case.
> 
> Ron - K0QVF
> 
> scott at opentrac.org wrote:
> > I got just about the same thing from Idiom a few minutes ago...
> > 
> > "AP1xxx<CR>" sets target bearing to "xxx" degrees where xxx 
> are three 
> > digits between 000 and 360, and executes. A typical command 
> to rotate to 
> > 080 degrees would be AP1080<CR> Note that the <CR> is often labeled 
> > <Enter> on many keyboards.
> > 
> > "AP1xxx;" sets the target bearing but does not execute. 
> > 
> > I wonder if one of those is incorrect, or if it's really a 
> difference in
> > command structure.  I guess you could always send 
> AP1xxx<CR>AM1;<CR> just to
> > be sure.
> > 
> > Anyway, should be a piece of cake to add.  Dead reckoning 
> would add some
> > complexity, but hopefully it won't be needed.
> > 
> > Scott
> > N1VG
> > 
> >> -----Original Message-----
> >> From: aprssig-bounces at lists.tapr.org 
> >> [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Bill Bell
> >> Sent: Monday, June 19, 2006 11:58 AM
> >> To: 'TAPR APRS Mailing List'
> >> Subject: RE: [aprssig] Rotor control
> >>
> >> The following codes are for the Rotor-EZ card used in the 
> >> Yaesu SDX series
> >> rotors. I suspect the codes would be the same for the 
> >> Rotor-EX card but
> >> can't say for sure.
> >>
> >> RS232 config requires 4800 8N1 
> >>
> >> "AP1xxx"	sets the target bearing but does not execute 
> >> (leading zeros
> >> must be used)
> >> "AM1;"	executes rotation to the bearing set by the 
> >> above command
> >> "A|1;"	inquires current bearing and responds with 
> >> (000-359) degrees
> >> ";"		terminates rotation
> >>
> >> Each command is followed by a carriage return
> >>
> >> The documentation tells you to select Rotor-EZ or HyGain DCU-1.  
> >>
> >> In the rotor settings for TRX-Manager there are approximately 
> >> 10 different
> >> rotors listed so they apparently each use their own commands.
> >>
> >>
> >> Bill Bell
> >> W9BEL
> >>
> >>
> >>  
> >>
> >> -----Original Message-----
> >> From: aprssig-bounces at lists.tapr.org 
> >> [mailto:aprssig-bounces at lists.tapr.org]
> >> On Behalf Of scott at opentrac.org
> >> Sent: Monday, June 19, 2006 13:00
> >> To: 'TAPR APRS Mailing List'
> >> Subject: RE: [aprssig] Rotor control
> >>
> >>> to follow a satellite. The "KC" (Kansas City) was the name of 
> >>> one such 
> >>> standard long ago. I suspect if you get on Amsat's site and 
> >> All I can find for the Kansas City Tracker is the ISA card.  
> >> Doesn't do much
> >> good for a standalone installation.
> >>
> >> I'm hoping the Rotor-EX takes something simple, like a 
> >> bearing in degrees.
> >> I don't want to get into the low-level details of rotor 
> >> control, I just want
> >> to tell a rotor controller where to point.
> >>
> >> Scott
> >> N1VG
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> aprssig mailing list
> >> aprssig at lists.tapr.org
> >> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >>
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> aprssig mailing list
> >> aprssig at lists.tapr.org
> >> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> >>
> >>
> > 
> > 
> > 
> > 
> > _______________________________________________
> > aprssig mailing list
> > aprssig at lists.tapr.org
> > https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> > 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
> 
> 







More information about the aprssig mailing list