[FADCA] 144.99 MHz

[Chuck Hast]

On 8/24/06, bud Thompson <budt at cfl.rr.com> wrote:
>
>
> * * *
> Yes, the use of LANS for interconnecting is not recommended.  But we do what
> we can do where there is little interest/activity between two areas that
> need connectivity.  This is part of re-building and adding to the old
> network.
>
Indeed,  in a case like this you have to make do. But it looks like you have a
plan...

> We are presently using the route - ORL - DeLand - DAB - STA - via UHF
> Backbone. STA is a ROSE switch with only two ports: 144.99 LAN and 441.150
> backbone.  The STA backbone port with back-to-back beams sharing the power
> serves to link southward to DAB and northward toward Jacksonville to -
> somewhere that no longer can make the UHF jump.  So we switch at STA from
> 441.150 to the LAN where there is an X1J- node northward near JAX that takes
> us on into JAX (after switching 2M frequencies to 144.01 I think.) Presently
> all this starting with DAB northward is 1200b.
>
What a mess, I bet you all are going to be happy to see that get changed.

> This link from Orlando to JAX will become full -network compatible- with our
> current plans to install new switches (either FPAC or ROSE) by the end of
> the year.
>
I would try to replace them all with linux FPAC so that you pick up the WP
facilities, remember that if there is a rose or dos fpac in the path the wp
piece can no longer do it's thing because each neighbor talks to the next
exchanging wp data, so a rose of dos siwtch can not do wp.

> ORL-DeLand-DAB-STA-Orange Park - JAX and will all be at 9.6kb.  The use of
> 144.99 for backbone links will no longer be required.
>
That will be good, and at 9k6 should have a good response.


-- 
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."