Re: [aprsisce] Feature Request
- On 9/2/2012 8:47 PM, James Ewen wrote:
> Then of course if you are trying to send data of this detail over theI THINK I check to see if the new position is different after encoding
> APRS channel, you're probably going to be hitting the channel pretty
> hard, and possibly sending data then is representing positions of
> higher resolution than the APRS position format you are sending can
it into the desired precision unless I'm beaconing because of a timer
expiration or forced. I know I have that code in there somewhere, but
I'm not exactly sure which part of APRSISCE/32 it applies to. Doesn't
work if the jitter is right on the boundary, but helps in many cases.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
I just found software that does what I want
Habrotate pulls info from the Habitat database and feeds to pstRotator and pstRotator has an APRS option.
Have just paid for pstRotator and waiting for a registration code was only 15 Euro
When it arrives will test it all out and report back
Still think it would be nice to have in APRSIS32 though
https://www.philcrump.co.uk/Habrotate Windows compile
From: email@example.com [mailto: firstname.lastname@example.org ]
Sent: 27 June 2014 23:44
Subject: [aprsisce] Feature Request
Just received my rotator control unit an ERC-M unit only got the USB option I do wonder if the Lan option might be handy as well.
What I would like when Lynn gets the time is the ability to follow a station and have the rotator system track that station.
For me this is mainly for use with Lynn ’s habitat to APRS system for tracking balloons. But also ships in the channel. But it’s obviously useful for tracking anything moving.
So whats needed is a rotator port type the usual TCP/IP, USB, Com.
The software already does bearing so elevation added. Following a station with rotator enabled auto tracks that station.
My control box uses Yaesu GS232A and B protocols which seem standard across various rotators and software
Yaesu GS232 A and B
The only difference in A and B is the format how a position is returned from the ERC
Note 1): This command was added by the Dual-AZ protocol by VE2DX and used to drive 2 AZ-rotators with a 2-axis interface
Command to ERC Description Returned from ERC
A<cr> Stop rotation azimuth <cr>
B<cr> (in GS232A-mode) Request position elevation +0eee<cr><lf>
B<cr> (in GS232B-mode) Request position elevation EL=eee<cr><lf>
C<cr> (in GS232A-mode) Request position azimuth +0aaa<cr><lf>
C<cr> (in GS232B-mode) Request position azimuth AZ=aaa<cr><lf>
C2<cr> (in GS232A-mode) Request position azimuth + elevation +0aaa+0eee<cr><lf>
C2<cr> (in GS232B-mode) Request position azimuth + elevation AZ=aaa<s><s>EL=eee<cr><lf>
D<cr> Rotate DOWN or CCW 2nd axis <cr>
E<cr> Stop rotation elevation <cr>
L<cr> Rotate CCW 1st axis <cr>
Maaa<cr> Rotate azimuth to aaa <cr>
MBeee<cr> 1) Rotate elevation to eee <cr>
R<cr> Rotate CW 1st axis <cr>
S<cr> Stops rotation both axis <cr>
U<cr> Rotate UP or CW 2nd axis <cr>
Waaa eee<cr> Rotate azimuth to aaa and Rotate elevation to eee<cr>
I think A,B,C,E,M and MB, I don’t see a need for D,L,R,S,U