[aprssig] Packet Node on 144.390 ?

[Robert Bruninga]

I am all for BBS's and other conventional packet systems, but
there is no need for them on 144.39.  Put them on a dedicated
frequency (maybe 145.01) and then make sure there are some
145.01 digis on the air too.  Then one can download from the BBS
without QRM from APRS and APRS can operate without QRM from the
BBS.  

The two modes are totally different.  There is no reason
whatsoever to have them on the same frequency when a simple
button push will QSY any radio for optinum use on either.

BUT, be sure and have a BEACON on the APRS frquency (DIRECT ONLY
in the DIRECT area of the BBS) that shows the BBS on the map for
those that might need it.  An object placed in the LT of a local
digi would do that nicely.  The object would be the BBS ICON and
the object text would be something like.  "145.01 MHz AARC BBS.
Join us"  This would show up nicely on the D7 and D700 displays.

De Wb4APR, Bob


> -----Original Message-----
> From: aprssig-bounces at lists.tapr.org 
> [mailto:aprssig-bounces at lists.tapr.org] On Behalf Of Geoffrey
Dick
> Sent: Sunday, September 10, 2006 8:07 AM
> To: aprssig at lists.tapr.org
> Subject: Re: [aprssig] Packet Node on 144.390 ?
> 
> Subject: Re: [aprssig] Packet Node on 144.390 ?
> 
> William McKeehan, KI4HDU wrote:
> > I'm really looking for reasons to give someone to NOT put a
packet 
> > node (BBS or just PBBS) on 144.39.
> 
> This largest reason I can think of is that packet bulletin 
> board traffic
> would block time-sensitive APRS information.   Position and 
> weather fall
> in this category.  Unconnected APRS packets are less than a 
> second long,
> and are not retransmitted. If the channel is busy, an APRS 
> station will
> delay to a set interval for fresh position or weather 
> information.  If 
> the channel is busy, then time-sensitive information is 
> permanently lost.
>    
> Each transmission is unique for those who can receive them,
and each 
> APRS packet burst is separated by minute to several minutes to
allow 
> others to share the channel.  With DCD taking precedence,
Connected 
> Packet will impede others from sharing the channel. 
> 
> Simply put, are speaking of two AX25 packet operating modes
competing 
> on a single frequency: 
> 
>     connected-long-burst verses unconnected-short burst  
> 
> Two connected Packet stations, transmitting, confirming, and 
> retransmitting 
> will tie up the frequency for several minutes, preventing a 
> multitude of
> short-burst APRS stations from sharing the channel.  This is 
> not a good 
> plan for a shared frequency of 10 to 250 active stations in 
> an ALOHA circle. 
> 
> Kind regards,
> 
> Geoffrey Dick, wa4ikq
> Winter Park, FL
> 
> 
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> https://lists.tapr.org/cgi-bin/mailman/listinfo/aprssig
>