[aprssig] 2 Port Digitpeater was: APRS UHF freq? (9600 baud)

[Ev Tupis]

It is best to do independent research first.  Spit-balling a frequency before doing that is full of problems.
Here is an approach that establishes availability quite authoritatively...

First, build a coalition of like-minded people who are both motivated and willing to put in some work.  If that can't be done, stop. ;-)

Check documentation of repeater councils across the country...even if you think you are choosing a frequency in the "simplex sub-band".  

One crucial and authoritative step is to setup automated monitoring stations on a desired frequency ... to monitor 24/7/365.  Yep, for a year.  You may find that operation on a given frequency occurs at "non standard" (to you) times of the day and year.
Another is to "test fly" the frequency AFTER the aforementioned step...across the country.  Setup operations at altitude and be ready-willing-able to cease operations if QRM occurs (there are plenty of simplex nets out there).
There is more...but to Steve's point earlier...it takes dedication, effort, leadership and some luck.
Best regards,Ev, W2EV


      From: Greg D <ko6th.greg at gmail.com>
 To: TAPR APRS Mailing List <aprssig at tapr.org> 
 Sent: Wednesday, January 25, 2017 2:58 PM
 Subject: Re: [aprssig] 2 Port Digitpeater was: APRS UHF freq? (9600 baud)
   
+1 

How about 223.60, if nothing else, to start the discussion?  I see
references to this as a backbone frequency for packet, mostly on maps
from the late 1990's.  Time for use by APRS, or are the BBS nodes still
active there?  Don't want one backbone use to swamp the other.

Greg  KO6TH


Peter Laws N5UWY wrote:
> On Wed, Jan 25, 2017 at 12:28 PM, Bob Mueller <bob at funautical.com> wrote:
>> I also think 220 is a good place for APRS.  Since there is hardly any other
>> activity on that band.
> 219-220 MHz is begging for activity ... at least for point-to-point ...
>
>

_______________________________________________
aprssig mailing list
aprssig at tapr.org
http://www.tapr.org/mailman/listinfo/aprssig


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20170126/18090a38/attachment.html>