[FADCA] Welcome Rich

[email protected] [email protected]
Mon, 22 Apr 2002 10:05:35 -0400


Hmm, I see that a very interesting concept has been
brought back into this whole thing. I guess a lot of
us had been thinking about this idea about the same time
but nothing much happened, I think more than anything
else due to apathy from some of the APRS people, as
we were at times refered to as the "network gods" by
some of them, but let us let that rest, as I think that
bandwidth has reared it's head and shown why we need
each other.

Rich, indeed there is code in both the last version of
ROSE and now FPAC to handle what you want to do. In truth
the best bet is indeed for us to move on the LINUX version
of FPAC as there are specific bits and pieces in that
version that are dedicated to handling some of what you
want in a more transparent way. One of the abilities of
LINUX FPAC is to be able to match a connection string to
a incoming connection request, that mechanisim may also
hold for UI packets in which case you could have a designated
APRS device to which all switches are aimed and when a
incoming APRS frame is heard it is routed to the APRS
server. If you used a common X.121 address you could
then just send all of your APRS messages to that address
which would correspond to the APRS server. The server would
not only know where (GPS data) you were but will know what
switch you are on (due to the incoming X.121 address data
on the inbound APRS data as it is seen from the server
end). I think that perhaps the DOS code has probably reached
it's end in this respect, I am trying to get a hold of Tom
and see about the code, but I think he maybe traveling as I
have not got a reply from him. I know that much automation
has taken place in the LINUX code, it also has a automated
whitepages which can be turned on and allowed to exchange
data on users such that you again only issue a connect to
a user call via switch, it looks up the address where the
target was last heard and set up the call based on that
data. That function is selectable as it does place additional
burden on the network in the form of whitepage updates.


> -----Original Message-----
> From: Rich Garcia [mailto:[email protected]]
> Sent: Sunday, April 21, 2002 09:00 PM
> To: [email protected]
> Subject: RE: [FADCA] Welcome Rich
> 
> 
> FPAC ok I know that was about but not that widespread. Now 
> that it is run on
> a PC maybe more can be done in the way of fancy code that could not be
> worked into the ROSE chip.
> 
> Who does the FPAC coding..
> 
> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]]On
> Behalf Of n4xeo
> Sent: Sunday, April 21, 2002 7:39 PM
> To: [email protected]
> Subject: [FADCA] Welcome Rich
> 
> 
> At 12:54 PM 4/21/2002 -0400, you wrote:
> >I will join the list soon Bill.
> 
> 
> Hi Rich and Welcome to the list. Lets see what we might be 
> able to work
> with to get aprs across the FPAC network.
> 
> We don't use rose any more, we use the computer version of rose called
> FPAC. We only have a hand full of rose sites in the state now 
> and we are
> working on getting them converted over to FPAC.
> 
> 
> 
> 73, Bill N4XEO
> 
> E- Mail mailto: [email protected]
> home page: http://www.qsl.net/n4xeo
> F.A.D.C.A.: http://www.fadca.org
> FPAC: http://www.qsl.net/fpac
> ICQ: 19219163
> 
> 
> _______________________________________________
> FADCA mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/fadca
> 
> 
> _______________________________________________
> FADCA mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/fadca
> 


*****************************************************************
This e-mail and any files transmitted with it are confidential and are
intended solely for the use of the individual or entity to whom it is
addressed. If you have received this transmission in error, please notify
the sender immediately and destroy any hard copies you may have printed and
remove all copies of the e-mail from your hard drive. Opinions, conclusions
and other information in this message that do not relate to the official
business of Utility Partners, Inc shall be understood as neither given nor
endorsed by it.

Visit us on the web at http://www.utilpart.com 
*****************************************************************