OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   01.04.07 22:33l 175 Lines 5767 Bytes #999 (0) @ WW
BID : 9993-ZL3AI
Read: GUEST
Subj: [APRSSIG] Vol 33 #31, 1/1
Path: DB0FHN<DB0MRW<DB0ERF<DB0FBB<DB0IUZ<DB0GOS<ON0AR<HS1LMV<I0TVL<IW8PGT<
      SV1CMG<ZL2BAU
Sent: 070401/2104Z @:ZL2BAU.#79.NZL.OC #:40750 [Waimate] $:9993-ZL3AI
From: ZL3AI@ZL2BAU.#79.NZL.OC
To  : APRDIG@WW

Today's Topics:

1. Regular packet and APRS (Mr Mike)
2. RE: Regular packet and APRS (Robert Bruninga)
3. RE: Regular packet and APRS (kb2scs_at_optonline.net)
4. Not APRS, but a balloon... (Robert Rochte)
5. KC8UCH balloon over western PA right now, reaching NE Maryland by 10am
    (Robert Rochte)
6. RE: APRS -- Chicago to Mackinac Island sailboat race (Bill Borgstrom)

----------------------------------------------------------------------

Message: 1
Date: Fri, 30 Mar 2007 13:21:14 -0700 (PDT)
From: Mr Mike <kf8zn_at_yahoo.com>
Subject: [aprssig] Regular packet and APRS

It is my understanding that APRS is regular packet so to speak?
   
So, is it possible to send a "beacon" in Regular Packet that contains the
info required to display your position to other stations running APRS?

------------------------------

Message: 2
Date: Fri, 30 Mar 2007 16:32:18 -0400
From: "Robert Bruninga" <bruninga_at_usna.edu>
Subject: RE: [aprssig] Regular packet and APRS

>It is my understanding that APRS is regular packet...
>  
>So, is it possible to send a "beacon" in Regular Packet
>that contains the info required to display your position
>to other stations running APRS?

Sure!  Any of these formats will work:
This is what you type in CONV mode:

!DDMM.hhN/DDDMM.hhW$...

That is the simplest format.  For the "$" byte, you can enter any of about
200 different symbol indicators.  Easiest to remember are "-" for a  house,
and ">" for a car

You don't even need to enter that degree of LAT/LONG precision if the
position is estimated.  Only enter the degree of precision you have.  But
replace all unused bytes with SPACE characters.  That maintains the format
and indicates to ALL observers that the position is "ambiguous" to the
degree for which you are transmitting data.  All of the following are
valid:

!DDMM.h N/DDDMM.h W$... <== tenth mile ambiguity
!DDMM.  N/DDDMM.  W$... <== 1 mile ambiguity
!DDM.  N/DDDM.  W$... <== ten mile ambiguity
!DD .  N/DDD .  W$... <== 60 mile ambiguity

Oh, and you can put any free text up to I think it is 53 bytes where
the...'s are...

Enjoy!
Bob, WB4APR

------------------------------

Message: 3
Date: Fri, 30 Mar 2007 17:14:29 -0400
From: kb2scs_at_optonline.net
Subject: RE: [aprssig] Regular packet and APRS

Also set your unproto path to APRS VIA WIDE2-1
This will give one hop.
The path part "WIDE2-1" can be changed to an aprs path that is 
consistent with your area. The WIDE2-1 is just an example.

The important part is the APRS part.

Let us hope we never witness the "Silence Of The Hams"
73 DE John  KB2SCS
E-Mail:            kb2scs_at_arrl.net
APRS-SCS     http://www.tapr.org/~kb2scs
Web Page:     http://www.qsl.net/kb2scs

------------------------------

Message: 4
Date: Fri, 30 Mar 2007 16:55:28 -0400
From: "Robert Rochte" <rochte_at_gmail.com>
Subject: [aprssig] Not APRS, but a balloon...

We have a balloon aloft right now that should be somewhere over SW Ontario,
Canada or maybe downriver from the Detroit area, heading toward the
southeast.  It is only carrying an FM beacon transmitting modulated CW on
445.975.  If anyone copies it and/or has a bearing, please let me know.
And if you could give me your GPS coordinates - maybe from the GPS
connected to your APRS rig - that would be great (see, it's APRS-related!).

Thanks and 73,
Robert  KC8UCH

------------------------------

Message: 5
Date: Sat, 31 Mar 2007 01:05:14 -0500
From: "Robert Rochte" <rochte_at_gmail.com>
Subject: [aprssig] KC8UCH balloon over western PA right now, reaching
NE Maryland by 10am

I promise, SDG-2 will carry APRS equipment (I just need to find a very light
tracker and a GPS that doesn't eat batteries)!

In the meantime, SDG-1 is still aloft over western PA at 2:00am EDT and
tracking to the southeast.  It should be over northeastern Maryland by
mid-morning if icing doesn't take it down tonight.

Listen on 445.975 (FM) - it sends modulated CW containing my call, email
address and battery voltage, followed by 50 dits, then it all starts over.

73,
Robert  KC8UCH

------------------------------

Message: 6
Date: Sat, 31 Mar 2007 04:56:23 -0700 (PDT)
From: Bill Borgstrom <bill_borgstrom_at_yahoo.com>
Subject: RE: [aprssig] APRS -- Chicago to Mackinac Island sailboat race

Pete
   
How do I logon and upload the packet.

>AE5PL Lists <HamLists_at_ametx.com> wrote:
>For a definitive explanation of the login line, go to
>http://www.aprs-is.net/valid.htm Note that www.aprs-is.net is the
>definitive location for APRS-IS formatting including q constructs, etc.
>
>For user, be sure to use a -unique- callsign-SSID (N9TN-VS, for example)
>since you already use N9TN as your home station. Your validation code does
>not change.
>
>The format for your packet can also be found at www.aprs-is.net Since you
>are, in essence, gating the packets to APRS-IS, I recommend using something
>like:
>
>N9TN-9>APRS,qAR,N9TN-VS:_at_092345/4349.13N/08653.55WY306/015Cheap'n'Deep
>sec 6 Chicago Mac race
>
>Note the qAR construct tells APRS-IS that this packet has been received by
>N9TN-VS from RF (or non-APRS-IS means) and is being passed into APRS-IS by
>N9TN-VS. This is assuming that you use the N9TN-VS user callsign-SSID
>combination on login. One of the purposes for the q construct is to show a
>"port of entry" which this does (it is also used for loop detection).
>
>Hope this helps.
>
>73,
>
>Pete Loveall AE5PL
>pete at ae5pl.net
>
>PS: APRServe no longer exists on APRS-IS. The majority of APRS-IS servers
>are running either javAPRSSrvr or aprsD. Just a clarification.

------------------------------

aprssig mailing list
aprssig_at_lists.tapr.org
https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig

End of aprssig Digest, Vol 33, Issue 31



Read previous mail | Read next mail


 27.01.2026 02:37:04lGo back Go up