Grrrr
I seem to fail to understand the APRS mode of GO32:
Kenwood TS2000X HamRadioDeluxe for auto doppler correction
External TNC (PK96) hbaud 8600 u aprs via 4xtech
uplink 145.850 in CONV mode: ":AP hello" ... some days ago this worked twice, then nothing got digipeated
uplink 145.930 in CONV mode: ":2 hello" ... never any success
Then: I see JA stations getting stuff like this over it: JA0CAW]APRS,4XTECH*,qAS,JH4BTI::JA5BLZ :GE ur599 TNXp whereas I would have expected somethin like "AP JA5BLZ ...." (AP in front)
This is the only source of documentation I have: http://web.usna.navy.mil/~bruninga/GO32-ops.html
Which states:
145.85 MHz All APRS messaging (or fixed station non-Mic-E positions). . Only TOCALLs that begin with "APxxxx". 145.93 MHz All APRS Mic-E positions and status(D7, D700 and D710s with comment set to "Committed, Special or PRIORITY"... The reason for these uplink distinctions is due to GO-32 hardware that will only digipeat a packet on 145.85 that has a TOCALL beginning with "A". (All APRS fixed station packets and all APRS messages including D7 and D700's) . The 145.93 channel will only accept packets that begin with a digit between 1,2,3,4,5,6,7. . But fortunately the D7 and D700's do this naturally as long as the position comment is set to "committed, SPecial or PRIORITY"...
Q1: do the TOCALLs need APxxx or Axxx on 850 ? (in CONV mode type :APxxx ?) Q2: should here ":2xxx" work ?
Thanks ! Henk, PA3GUO
.... so lost :-)
What I use is, 145.85 for the uplink (only use 145.93 with mice)
u aprs via 4xtech hbaud 9600 (I guess your 8600 was a typo)
Then you should just be able to send anything like normal I do alot of messages like:
:CQ :Hello on go32
I'm using my d700 in packet mode with aprs software
Also, can you hear go-32 at all? it transmits about every other second with it's bbs stuff, so it should be a constant stream of stuff even if no one is transmitting to it. Pretty much like the ao-51 downlink on 9600baud.
Quoting "Henk, PA3GUO" hamoen@iae.nl:
Grrrr
I seem to fail to understand the APRS mode of GO32:
Kenwood TS2000X HamRadioDeluxe for auto doppler correction
External TNC (PK96) hbaud 8600 u aprs via 4xtech
uplink 145.850 in CONV mode: ":AP hello" ... some days ago this worked twice, then nothing got digipeated
uplink 145.930 in CONV mode: ":2 hello" ... never any success
Then: I see JA stations getting stuff like this over it: JA0CAW]APRS,4XTECH*,qAS,JH4BTI::JA5BLZ :GE ur599 TNXp whereas I would have expected somethin like "AP JA5BLZ ...." (AP in front)
This is the only source of documentation I have: http://web.usna.navy.mil/~bruninga/GO32-ops.html
Which states:
145.85 MHz All APRS messaging (or fixed station non-Mic-E positions). . Only TOCALLs that begin with "APxxxx". 145.93 MHz All APRS Mic-E positions and status(D7, D700 and D710s with comment set to "Committed, Special or PRIORITY"... The reason for these uplink distinctions is due to GO-32 hardware that will only digipeat a packet on 145.85 that has a TOCALL beginning with "A". (All APRS fixed station packets and all APRS messages including D7 and D700's) . The 145.93 channel will only accept packets that begin with a digit between 1,2,3,4,5,6,7. . But fortunately the D7 and D700's do this naturally as long as the position comment is set to "committed, SPecial or PRIORITY"...
Q1: do the TOCALLs need APxxx or Axxx on 850 ? (in CONV mode type :APxxx ?) Q2: should here ":2xxx" work ?
Thanks ! Henk, PA3GUO
.... so lost :-)
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
Is there a problem with AO-27? Lately it seems that the bird is turned on for less than 10 minutes, then is turned off for over an hour. In the last several days, it seems that whenever there is a pass over the USA, it's off.
Just wondering if this is normal, or if there are problems.
73 de W4AS Sebastian
Hi Sebastian!
Is there a problem with AO-27? Lately it seems that the bird is turned on for less than 10 minutes, then is turned off for over an hour. In the last several days, it seems that whenever there is a pass over the USA, it's off.
Just wondering if this is normal, or if there are problems.
AO-27 has apparently been off since last weekend. I worked a pass Friday afternoon, but since then there has been no reported activity. The http://oscar.dcarr.org/ web site appears to confirm that.
For at least the past few years, AO-27 would only be on for a portion of the daylight passes (moving from south to north) over the Northern Hemisphere. For most of the past 19 or 20 months, it would be on for 7 minutes at a time as the satellite crosses 29 degrees North latitude (approximately).
The AO-27 operating schedule is available from the http://www.ao27.org/ web site, but in recent months it appears that the web site schedule would be off by 7 or 8 minutes from the satellite's onboard schedule. There is a Java-based program that will show the satellite's schedule, and that has been more in line with the onboard schedule. If you went by the schedule from the AO-27 web site when the satellite was operational in the last few weeks, you might have heard the last minute or less of the 7-minute repeater time.
With the satellite off for the moment, there has been no update of the AO-27 web site or messages from any of the AO-27 command stations as to whether or not the satellite can be returned to operation. Last time this happened, in late 2006 and early 2007, it took a few months to get things working again.
BTW thanks for the VO-52 QSO last Friday. You were the first station I worked from the convention I attended. My QSL card is on its way.
73!
Patrick WD9EWK/VA7EWK http://www.wd9ewk.net/
I seem to fail to understand the APRS mode of GO32: This is the only source of documentation I have: http://web.usna.navy.mil/~bruninga/GO32-ops.html
Which states:
145.85 MHz All APRS messaging (or fixed station non-Mic-E positions). . Only TOCALLs that begin with "APxxxx".
This is because APRS messaging uses an AX.25 Destination Address of APxxxx where xxxx is a version number. I call that AX.25 Destination address the "TOCALL" for brevity...
And on 145.85 uplink, the GO-32 satellite IGNORES any packet that does not begin with the AX.25 DESTINATION address that begins with "A".
145.93 MHz All APRS Mic-E positions and status(D7, D700 and D710s with comment set to "Committed, Special or PRIORITY"...
On the 145.93 UPLINK, the GO-32 folks opened up additional INITIAL bytes of "2,3,4, or 5" as possible AX.25 DESTINATION addresses. In this case, a Mic-E packet at any LATITUDE between 20 to 59 degrees latitude will begin with one of those digits. ... But only if the "comment" set to the above selections. Because if they are not set to that selection, then the additional bit is used and the leading byte of the AX.25 DEESTINATION field is no longer a digit from 2 to 5.
The reason the GO-32 (and ECHO, AO-51) and other PACSAT-BBS Protocol birds have to have this first-byte filtering, is so that the constant NOISE in the receiver does not forever trigger the 9600 baud interrupt and consume inordinate amounts of processing power on noise. By ignoring all false detections except those that begin with the very first matching byte, then the CPU can ignore 255 out of all 256 possibilities of noise.
The reason for these uplink distinctions is due to GO-32 hardware that will only digipeat a packet on 145.85 that has a TOCALL beginning with "A". (All APRS fixed station packets and all APRS messages including D7 and D700's) . The 145.93 channel will only accept packets that begin with a digit between 1,2,3,4,5,6,7. . But fortunately the D7 and D700's do this naturally as long as the position comment is set to "committed, SPecial or PRIORITY"...
Q1: do the TOCALLs need APxxx or Axxx on 850 ? (in CONV mode type :APxxx ?)
The TOCALLS really refers to the AX.25 DESTINATION address.
Q2: should here ":2xxx" work ?
Neither of these will do anything. I think you are thinking of the APRS MESSAGE TOCALL, and that can be anything. But it has to be the complete format. As in :APRSTOCAL:message text. It must be 9 bytes long ad begin and end with colons followed by text. The BEST APRS messages to send via any satelite should be addressed to :ALL......:hello world..., beause ALL APRS radios will capture a message to ALL. Otherwise it will ignore it. Notice that the ... Dots have to actually be SPACES to work.
Bob, WB4APR
Thanks ! Henk, PA3GUO
.... so lost :-)
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:
participants (5)
-
Henk, PA3GUO -
Patrick Domack -
Patrick STODDARD (WD9EWK/VA7EWK) -
Robert Bruninga -
Sebastian