OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   14.02.03 10:05l 227 Lines 9435 Bytes #999 (0) @ WW
BID : 891-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 11, 3/5
Path: DB0FHN<DB0ZWI<DB0HST<ON0DXC<WA7V<RZ6HXA<SP7MGD<VK7AX<ZL2BAU<ZL3VML
Sent: 030213/0531Z @:ZL3VML.#80.NZL.OC #:59324 [Chch-NZ] FBB7.00i $:891-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

Subject: Re: Family Radio Service about to change
From: "Mike Yetsko" <myetsko@insydesw.com>
Date: Tue, 11 Feb 2003 14:03:36 -0500
X-Message-Number: 16

>It is already unpleasant to use FRS radios with the alert tones. The PL
>alone should be sufficient. In some areas they push the alert tone every

>so often to drive others from THIER channel.

Hmm, hadn't thought of that, but that may be correct.  If you can't have
a private channel, make it irritating for others to stay there!

>Listening to constant aprs will degrade the FRS service.

In this I have to agree.  FRS is 14 channels.  It's already crowded. Yes, I
know, it's 'empty' in most places.  But, the places you almost allways seem
to need it are the places that everyone else also seems to need it.  Adding
data to the congestion will just further congest things.

Besides, FRS is 2 mile or less (usually under most PRACTICAL conditions).
Does it really NEED APRS?  Are we (hams) trying to be a solution looking
for a problem?

Mike

----------------------------------------------------------------------

Subject: RE: utility to connect to multiple servers?
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Tue, 11 Feb 2003 13:11:30 -0600
X-Message-Number: 17

>-----Original Message-----
>From: Curt Mills, WE7U [mailto:hacker@tc.fluke.com]
>Posted At: Tuesday, February 11, 2003 11:27 AM
>Subject: [aprssig] RE: utility to connect to multiple servers?
>
>This brings up another idea that I've been thinking of:  A
>network type identifier sent by the server when you connect.
>Have an identifier for BEACOnet, one for APRS-IS, one for
>FIRENET.  Assign these as each new parallel network comes online.
>
>This identifier would be used to assure that packets don't
>cross between different types of networks unless the operator
>specifically overrides it somehow (it should not be easy to
>accidentally override it).  This would protect the APRS-IS
>from firenet, and BEACOnet from all the APRS nets.

Interesting thought.  Instead of sending the type identifier at connect
time, though, how about having it in each packet header?  If we go this
route, the q construct already supports this though there hasn't been
much done to handle non-APRS packets.  The q construct, as it stands now
is qPT where P is the protocol and T is the type of access the packet
entered the Internet at.  Currently, only A (APRS) is defined for the
protocol.  It wouldn't be hard to add B for BEACONet and F for FIRENET.
The server software would then be told what protocol/network it is and
what additional protocol(s)/network(s) to pass, if any.

Fully backwards compatible with current servers/clients but would add an
extra layer of "safety" between networks for future server releases.

73,

Pete Loveall AE5PL
pete@ae5pl.net

----------------------------------------------------------------------

Subject: RE: Family Radio Service about to change
From: "AE5PL Lists" <HamLists@ametx.com>
Date: Tue, 11 Feb 2003 13:15:12 -0600
X-Message-Number: 18

>-----Original Message-----
>From: Alex [mailto:kr1st@amsat.org]
>Posted At: Tuesday, February 11, 2003 7:38 AM
>Subject: [aprssig] Family Radio Service about to change
>
>It's just too bad that the FCC chooses to protect commercial interests
>by not allowing external devices to be attached to > a FRS transceiver.
>They use the excuse that attachments that would allow for store and
>forward mechanisms, which virtually

This was done solely for Garmin.  Garmin pushed for the change to make
their FRS radios legal and they, apparently, got what they wanted.

73,

Pete Loveall AE5PL
pete@ae5pl.net

----------------------------------------------------------------------

Subject: RE: utility to connect to multiple servers?
From: "Spider" <spider@rivcom.net>
Date: Tue, 11 Feb 2003 12:35:31 -0700
X-Message-Number: 19

----- Original Message -----
From: "Ramon F. Kolb" <ramon@ieee.org>
To: "TAPR APRS Special Interest Group" <aprssig@lists.tapr.org>
Sent: Tuesday, February 11, 2003 6:33 AM
Subject: [aprssig] RE: utility to connect to multiple servers?

OK, I admit I worded my original email a little awkwardly. I didn't mean
to imply that I'd want to connect to the same source of information
multiple times, rather to different sources (APRS-IS, FireNet, BEACONet,
etc.) simultaneously. In the mean time, I also learned that FireNet
includes the information that is available on APRS-IS, so I don't have
to connect to it separately.

I knew what you were saying, Ramon...no worries!  If you are connected to
FireNet as a client, you are also connected to the APRS-IS and the APRS-IS
sees all client activity on FireNet. A Firenet client sees all Firenet Data
as well as all APRS-IS activity.  However, the APRS-IS does not see the
FireNet Data feed, unless we are testing or I screw up...which has been
known to happen! :)
You as a client, can not affect the path your data takes while connected to
Firenet.

You can see Firenet info at   www.seaofblue.net   if you need more
information.

Jim, WA6OFT

----------------------------------------------------------------------

Subject: RE: utility to connect to multiple servers?
From: "Curt Mills, WE7U" <hacker@tc.fluke.com>
Date: Tue, 11 Feb 2003 11:49:34 -0800 (PST)
X-Message-Number: 20

On Tue, 11 Feb 2003, AE5PL Lists wrote:

>Interesting thought.  Instead of sending the type identifier at connect
>time, though, how about having it in each packet header?  If we go this
>route, the q construct already supports this though there hasn't been
>much done to handle non-APRS packets.  The q construct, as it stands now
>is qPT where P is the protocol and T is the type of access the packet
>entered the Internet at.  Currently, only A (APRS) is defined for the
>protocol.  It wouldn't be hard to add B for BEACONet and F for FIRENET.
>The server software would then be told what protocol/network it is and
>what additional protocol(s)/network(s) to pass, if any.

As long as you're not adding any more bytes to the Q-construct!  It
sounds like in this case you're not.

Personally I'd rather have it be sent out by the server in one
packet shortly after connect/reconnect time, or perhaps at periodic
intervals, rather than in each and every packet.  That way it could
be easily implemented in servers that did not implement the
Q-construct.

You're making the "protocol" definition a bit fuzzy here though,
'cuz all Firenet packets are still APRS packets.  It's the BEACOnet
ones that aren't.  Minor point though.

>Fully backwards compatible with current servers/clients but would add an
>extra layer of "safety" between networks for future server releases.

Compatible for those software packages that currently implement the
Q-construct.  Is there a list of those that do/don't w.r.t. client
and server programs that are in common use?

Xastir doesn't implement the Q-construct.  I've heard arguments both
for and against it.  Some people don't see the usefulness of adding
multiple bytes to every packet.  I'm undecided at this point.  Is it
true that in some cases multiple callsigns can get inserted?  I
haven't researched the issue at all, having plenty of other things
to work on.  Yea, I know there are web pages with the info, I just
haven't delved into them yet.

Xastir has had the ",I" injection point stuff implemented for some
time.  This is a minimal addition to the packet intended only to
show the injection point, not necessarily to prevent looping,
although it can be used in some ways for that as well.  It's likely
that the ",I" and the Q-construct are solutions to two entirely
different problems.  Again, I haven't researched it.  Someday I'll
get around to doing that.

-- 
Curt Mills, WE7U                    hacker_NO_SPAM_@tc.fluke.com
Senior Methods Engineer/SysAdmin
"Lotto:    A tax on people who are bad at math!"
"Windows:  Microsoft's tax on computer illiterates!" -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

----------------------------------------------------------------------

Subject: Re: PCsat NORMAL OPS soon
From: larry Also <larrytooalso@yahoo.com>
Date: Tue, 11 Feb 2003 12:16:07 -0800 (PST)
X-Message-Number: 21

Not sure how effective this was, but we used to place diodes across each
cell of our radio control battery packs.  If a cell "opened" or went flat,
the idea was that the diode would provide the path to keep the radio
functioning.  This would also limit the reverse charge to about half a
volt, don't know if that would save the cell though.

Alex <kr1st@amsat.org> wrote:Bob Bruninga wrote:

>This will cease as soon as one of the cells shorts or reverses, so use her
>while you can, she wont last long... (knock on wood)....

Let me throw in a really dumb question. Why is this condition allowed to
occur on a satellite? I'm not talking specifically about PCSAT, but any
such satellite. 

Couldn't a watchdog circuit (not necessarily electronic, but maybe
chemical, or perhaps even (semi-) passive) be added so that if this
condition occurs, then the batteries will be disengaged or switched to a
fresh set, or solar only? I'd think that it is a highly undesireable
situation that a sattelite becomes uncontrollable just because (one of)
the power sources gives up. I'm not a space expert so it may be just
foolish talk I'm uttering here.

73,
--Alex KR1ST

----------------------------------------------------------------------



Read previous mail | Read next mail


 16.11.2026 01:25:59lGo back Go up