[FADCA] 144.99 MHz

[Chuck Hast]

On 8/23/06, bud Thompson <budt at cfl.rr.com> wrote:
> ----- Original Message -----
> From: "Chuck Hast" <wchast at gmail.com>
> To: "FADCA" <fadca at mailman.qth.net>
> Sent: Tuesday, August 22, 2006 23:51
> Subject: [FADCA] 144.99 MHz
>
>
> >I was looking at the availability of 144.99 MHz, I see the wormhole group
> > indicated as being on there, has anyone heard if they are still going or
> > not?
> > They are/were located over in St. Pete. I have not heard anything out of
> > them in some time.
> >
> > I am going to have to put a radio on that channel and see if it is being
> > used, there is more and more alternate APRS activity moving to that
> > freq, and I am hearing some interest in doing so in the area.  If anyone
> > has heard anything from them of late please tell me.
> >
> >
> > --
> > Chuck Hast  -- KP4DJT --
>
>
> ST AUGUSTINE 904829     KF4MX-7/6     144.990   LAN
>
> TAMPA        813282     KP4DJT-11/10  144.990   LAN  9K6  FPAC
>
No, I am not using it for 9k6. Better to use 440 for that. I will probably move
my 145.030 port to 9k6 and be done with it.


>
>
> As of the last time I took an "official" survey of who was using what STA
> was the only LAN on 144.91 except for TAMPA 813282.  In my opinion, which is
> not official policy, "alternate APRS activity"  should be used only on a
> secondary basis - primary is dedicated to APRS on 144.39.  That said, once
> we have the Florida Layered Packet Network in better shape, we could likely
> process APRS stuff pretty good across the network.  I'm not sure what it
> would take to have 144.39 2M LAN ports at the same site.  For instance, an
> APRS port would likely be welcomed at the DeLand FPAC site as there is poor
> APRS coverage there so far as I know.  DeLand LAN is 144.91 - 144.39 might
> be compatible if there was a duplexer of some sort.
>
> None of this is official.  Neil may have more updated information.
>

In order to process APRS all we need to do is add a port to the Linux box,
make sure that the digi function is turned on for that port and set up
the proper
digi call and rules and we are off and running. I want to do the same thing
here and allow the network to process some of the interlinking of aprs traffic.

In many areas 144.99 is being used as a alternate for aprs, more common
than not for WX and other sensor type activities, I know that St Aug. is using
144.99 but that is quite far enough off to not have any problems if we use
it here. I just want to make sure that there is no local operation
still left on it.


-- 
Chuck Hast  -- KP4DJT --
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."