APRS is working on GO-32.
Saw W3ADO sending text messages. Bob seemed to have fun :-)
................................................ "Fm W3ADO to APRS via 4XTECH* <ui pid=F0 LEN=40 > [18:27:41]
hello world. Bob just typing away...
...............................................
Message was received with UISS. TNC was configured for 9600baud. TS2000 and cross yagi on RX and TX.
Uplink was 145.850 (for APRS text messages).
Worked for me also.
................................................ "Fm VE4NSA to APRS via 4XTECH* <ui pid=F0 LEN=6 > [18:32:00]
Test
...............................................
Will try position data on 145.930 on the next pass.
73, Stefan VE4NSA
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
Bob,
Have you been able to get the 145.930 APRS position working? What would be the setup for a non_D700. 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@usna.edu] Sent: September-17-07 7:44 PM To: 'Stefan Wagener'; amsat-bb@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
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@usna.edu] Sent: September-17-07 7:44 PM To: 'Stefan Wagener'; amsat-bb@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
Think I cracked some UI lines via GO-32 this evening during the 2051 to 2105 BST pass.
Shouldn't the Unproto be APRS via 4XTECH-12 ?
Didn't see any other activity from EU though. Did anyone else try ?
I used paKet 6 and a DSP2232 with an ICOM 910.
Cheers,
Dave.
Think I cracked some UI lines via GO-32 this evening during the 2051 to 2105 BST pass. Shouldn't the Unproto be APRS via 4XTECH-12 ?
No, the SSID is not needed. I have never teseted to see if will work, but I don know that "APRS VIA 4XTECH" with no SSID does work. And of course, only on the 145.85 uplink.
Bob, Wb4APR
Hi All,
I have been unable to decode the satellite on my TH-D7 at all.. I have followed you instructions Bob about changing the UNPROTO to STATUS and also back to normal APT002 in my case, and still couldn't decode.
I am using a 5 element 70cms beam, so just wondered if anyone has been successful mobile/HT?
Thanks,
Chris - M0DQO Fareham, UK
-----Original Message----- From: amsat-bb-bounces@amsat.org [mailto:amsat-bb-bounces@amsat.org] On Behalf Of Dave Aitch Sent: 19 September 2007 22:11 To: bruninga@usna.edu; 'Stefan Wagener'; amsat-bb@amsat.org Subject: [amsat-bb] Re: Manual UI pcakets via GO-32 in APRS format
Think I cracked some UI lines via GO-32 this evening during the 2051 to 2105 BST pass.
Shouldn't the Unproto be APRS via 4XTECH-12 ?
Didn't see any other activity from EU though. Did anyone else try ?
I used paKet 6 and a DSP2232 with an ICOM 910.
Cheers,
Dave.
_______________________________________________ Sent via AMSAT-BB@amsat.org. Opinions expressed are those of the author. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
I have been unable to decode the satellite on my TH-D7 at all.. I have followed you instructions Bob about changing the UNPROTO to STATUS and also back to normal APT002 in my case, and still couldn't decode.
Although the original D7 had a 1200/9600 baud TNC built in, there was no menu to select the TNC for 9600 baud, since APRS was only a 1200 baud mobile application. But in 1998, we asked Kenwood to add 9600 baud to the selection menu. They did that and made several more changes to facilitate 9600 buad Satelite operations. This version came out as the D7(g) model.
Any D7 could be upgraded to the "g" model for about $50.
However, since your version appears to be APK002, which is the "g" model It should work.
HOWEVER, people with the non-"g" model can still do 9600 baud in packet mode. So connect a PC and operate in dumb terminal or external APRS software, and it should work. Or send in the HT for a firmware upgrade if it is not the "g" model...?
But again. 9600 baud takes about 7 dB more power than 1200 baud, so maybe you have not had a strong enough signal yet. Be sure to tune for Doppler on the downlink?
I have not actually been out doors with my HT yet to test the dowlink (I have only tested the HT uplink...
Bob
I am using a 5 element 70cms beam, so just wondered if anyone
has been
successful mobile/HT?
Thanks,
Chris - M0DQO Fareham, UK
-----Original Message----- From: amsat-bb-bounces@amsat.org [mailto:amsat-bb-bounces@amsat.org] On Behalf Of Dave Aitch Sent: 19 September 2007 22:11 To: bruninga@usna.edu; 'Stefan Wagener'; amsat-bb@amsat.org Subject: [amsat-bb] Re: Manual UI pcakets via GO-32 in APRS
format
Think I cracked some UI lines via GO-32 this evening during the 2051 to 2105 BST pass.
Shouldn't the Unproto be APRS via 4XTECH-12 ?
Didn't see any other activity from EU though. Did anyone else try ?
I used paKet 6 and a DSP2232 with an ICOM 910.
Cheers,
Dave.
Sent via AMSAT-BB@amsat.org. Opinions expressed are those of the author. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings:
http://amsat.org/mailman/listinfo/amsat-bb
-- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.487 / Virus Database: 269.13.22/1015 - Release Date: 18/09/2007 11:53
No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.487 / Virus Database: 269.13.25/1018 - Release Date: 19/09/2007 15:59
No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.487 / Virus Database: 269.13.25/1018 - Release Date: 19/09/2007 15:59
Sent via AMSAT-BB@amsat.org. Opinions expressed are those of the author. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings:
The GO32 header/beacon now shows uplink frequencies for the new modes. Thanks to ground control for this update and reminder for those of use using multiple modes on.
WinPack Users: See the SCRIPT folder under \WINPACK or wherever you installed the program for a script TM-D700.TXT For GO-32, this file requires some editing; specifically "SEND UNPROTO change this from the variable $BBS to APRS VIA 4XTECH etc ", "SEND HB 9600", "SEND MYCALL change it from the variable $MYCALL to your hardcoded call" , and at the end you could optionally add "SEND CONV"
You can also add 2 lines to the top of the script "HOTKEY F?" where ? is an unused F-Key in your WinPack scripts and a second line similar to "TITLE GO-32 APRS" so that you can initialize your TNC with a single F-Key.
Perhaps someone using the D7 could post their working script for WinPack.
... from an olde packet user from the '80's who as found a new use for the olde MFJ1270C with the 9600 daughter board. Just dusted it off and it works great with the FT-847 and WISP32 too. See y'all on GO-32
... Enjoy and 73, Alan VE4YZ AMSAT 35968 http://www.mts.net/~ve4wsc/ AMSAT A-485
participants (5)
-
Alan
-
Chris Bloy
-
Dave Aitch
-
Robert Bruninga
-
Stefan Wagener