[amsat-bb] Manual UI pcakets via GO-32 in APRS format

[Robert Bruninga]

> Have you been able to get the GO-32 
> 145.930 APRS position uplink working? 

Yes, works perfectly.

> What would be the setup for a non_D700.

That channel requires a Mic-E formatted packet.  Which is not
human readable and is not trivial to type.  Much easier to
simply operate normal APRS position reporting on 145.85.

Anyone with a 9600 baud TNC can manually communicate with anyone
else and all APRS operators as follows.  The simplest manually
typed APRS compatible packet is a GRID SQUARE format.
1) Set UNPROTO APRS VIA 4XTECH
2) Set TNC to CONVERSE
3) Type this or any similar line:

[FM19] bob here calling CQ GO32.

If the packet begins with the 4 digit grid square exactly as
shown, then it is a proper APRSformat and all APRS radios will
show you on the map.  Anything can be on the same line after the
[GG##] format.

Or you can be more specific with a [GG##gg] ... Format.

Once your position is successful, you don't need to keep sending
it.  You can send simple STATUS packets by only typing a line
starting with a ">"...

So this line:

>Hi everyone.  Bob here with 50W into my mobile whip.

And all APRS stations will see:

STATUS: Hi everyone.  Bob here with 50W into my mobile whip.

So anyone with a 9600 baud TNC can play.  Just start each line
with a GRID SQUARE in brackets if you want to send a position
report, or start it with ">" to send a one line status.

You will then also poentially show up on FINDU.COM under your
call if ther e is an Igate capturing the downlink.  Just go to
http://map.findu.com/URCALL

Where you type in URCALL

Bob, WB4APR

 and transmit your position there I seem to have a hard time
getting 
> my position
> data starting with 1 to 7 using UISS on the PC.  
> 
> Text messaging on 145.850 through GO-32 is working beautiful. 
> Thanks to all
> the folks that made it work. I hope I have someone to chat 
> with on the next
> pass (yes, non-interfering and within reason). Never had a 
> "live" digital
> QSO on GO-32.
> 
> 73, Stefan 
> 
> -----Original Message-----
> From: Robert Bruninga [mailto:bruninga at usna.edu] 
> Sent: September-17-07 7:44 PM
> To: 'Stefan Wagener'; amsat-bb at amsat.org
> Subject: RE: [amsat-bb] GO-32 and APRS working!
> 
> > APRS is working on GO-32. 
> > Saw W3ADO sending text messages. 
> > ................................................
> > "Fm W3ADO to APRS via 4XTECH* <ui pid=F0 LEN=40 > [18:27:41]
> > > hello world.  Bob just typing away...
> > ...............................................
> 
> I just left the receiver on the 435.230 (which is +5Khz) 
> downlink and heard
> the satellite out over the Atlantic.  SO I used HYPERTERM and 
> just typed
> away..  With my OSCAR array and no one else logged on, I got 
> nearly 100%
> digipeats of everything I typed.  This was using the D700 in 
> packet mode.
> 
> I also noticed that I could copy to the end of the pass while 
> still being
> tuned 5 KHz high right on the published center frequency.  
> Makes me think
> the satellite might actually be a few KHz higher than
published?
> 
> Also, since GO-32 is in "PTT" mode, meaning it does not keep 
> the TX on all
> the time, this means there is a key-up delay for APRS UI 
> packets.  This is
> GREAT news compared to APRS via ECHO.  This delay means there 
> is no problem
> for the D700 or D7 users in seeing their own packets
digipeated.
> 
> On ECHO, being full duplex and always on, the turn around on 
> the satellite
> was faster than the TNC in the D7 or D700, so you could 
> usually not see your
> own packets.
> 
> NOTE:  Non APRS users, who want to "chat" in dumb terminal 
> mode, can use the
> simplest APRS format to make sure all the mobiles and HT's 
> can see them.
> That is, preceed each message line with the ">" character.  
> SO typing this:
> 
> >Hello world...
> 
> Will display nicely on the D7 and D700 radio front panels.  
> But they will
> only see the first 20 bytes on the D7 and only the first 28 
> bytes on the
> D700.  But usually keyboard contacts are short anyway..  Oh, 
> and be sure
> your TNC UNPROTO is set to UNPROTO APRS VIA 4XTECH, and 9600
baud of
> course...
> 
> Bob, Wb4APR
> 
> 
> 
>