OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   08.02.03 10:48l 264 Lines 9232 Bytes #999 (0) @ WW
BID : 870-ZL3AI
Read: GUEST
Subj: TAPR Digest, Feb 05, 4/5
Path: DB0FHN<DB0ZWI<DB0HST<F6GGY<ON4HU<IK6PYS<ON0AR<ZL2BAU<ZL3VML
Sent: 030207/1012Z @:ZL3VML.#80.NZL.OC #:58990 [Chch-NZ] FBB7.00i $:870-ZL3AI
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW

Subject: Re: KISS TNC nearly a digipeater...
From: Henk de Groot <henk.de.groot@hetnet.nl>
Date: Wed, 05 Feb 2003 21:35:31 +0100
X-Message-Number: 24

At 09:20 5-2-03 -0500, John Kraus wrote:
>A much more elegant solution is to use Henk's Amazing Instant Digi Disk
>with any old 286 or better PC with that KISS TNC.  Works great.
>
>http://www.homepages.hetnet.nl/~remko/software/diginedE_partner.htm#easy

I don't think it has been updated to point to the instant floppy. It points 
to the floppies we used for both our test digis PI1APA and PI1APK, as an 
example. These require manual editing to configure your own digi.

The floppy with the configuration program that can be configured in less 
than a minute is still stored on my own web page:
<http://www.homepages.hetnet.nl/~pe1dnn/#DIGI_NED>

This is the second version that now also should work out of the box for a 
TM-D700 and TS-2000 and is a little more friendly for forign keyboards to 
fill in an SSID.

Remko who maintains the home of DIGI_NED is cooking up ideas to restructure 
the pages. I guess when that is done the floppy will move there too.

Kind regards,

Henk.

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

Subject: Glossy Eyed Readers [was: aprs spec/words of warning]
From: "Ev Tupis (W2EV)" <w2ev@arrl.net>
Date: Wed, 05 Feb 2003 15:48:24 -0500
X-Message-Number: 25

This disucssion is a-w-e-s-o-m-e.

Please, though...consider migrating it to the APRSspec list?  There is a
significant number of folks here who have a difficult time understanding
the nuances of WIDEn-N,ID vs. WIDEn-N,NOID, let alone understand things
such as bit-level encoding. :o)

I'm simply afraid that the discussion may be intimidating enough folks that
they may simply "go away".  On the other hand, the APRSspec list is the
perfect place for such things...and those interested may certainly
subscribe there.

To make that easy...visit here:
http://www.tapr.org/cgi-bin/lyris.pl?site=tapr&join=aprsspec

For what it's worth...keep the effort moving forward, pioneers!

Warm regards,
Ev Tupis, W2EV

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

Subject: Re: Glossy Eyed Readers [was: aprs spec/words of warning]
From: Jeff King <jeff@aerodata.net>
Date: Wed, 05 Feb 2003 14:59:27 -0600 (CST)
X-Message-Number: 26

I have a difficult time understanding the nuances of Power Poles Ev. I just 
delete the posts. 

What is being discussed may not even be "APRS" hence I'm not sure it is
proper to try and bring it to the APRS-WG, which the APRS-SPEC list is for.

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

Subject: Re: Glossy Eyed Readers [was: aprs spec/words of warning]
From: "Ev Tupis (W2EV)" <w2ev@arrl.net>
Date: Wed, 05 Feb 2003 16:21:56 -0500
X-Message-Number: 27

Jeff King wrote:
> 
>I have a difficult time understanding the nuances of Power Poles Ev. I just
>delete the posts.

Since you bring it up...does the + go on the left or the right? :o)

Hey, I was meaning to ask you...will the
lunchbox-computer-turned-stand-alone-router/digipeater work with things as
simple as AGWPE, two sound cards, and UI-View (on a Windows operating system)?

Ev

PS...just to keep this on thread...I still think a spec-list would allow
the discussion to not add to the "N" side of sig S/N ratio for the average
reader...especially if one considers it to not even be an APRS discussion
in the first place.

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

Subject: Re: Glossy Eyed Readers [was: aprs spec/words of warning]
From: "stanzepa@earthlink.net" <stanzepa@earthlink.net>
Date: Wed, 5 Feb 2003 16:32:46 -0500
X-Message-Number: 28

(This is a self-serving message to let you all know that I'm trying to earn
my keep.)

FWIW, a week or so ago, I asked Scott to consider moving the spec
discussion to aprsspec. I guess he considered it and did not move it. And
so it goes.

Stan, WA1LOU, aprssig/aprsspec administrator

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

Subject: Re: findU changes
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 5 Feb 2003 16:40:26 -0500 (EST)
X-Message-Number: 29

A WELL DONE to all concerned.  What a great system!
Great work!   I think we often fail to recognize how FINDU is so important
to the global APRS system...  Thanks Steve and everyone else that helped m
make this possible.      de WB4APR, Bob

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

Subject: Re: Glossy Eyed Readers [was: aprs spec/words of wa	rning]
From: Miller Scott Contr 30SCS/FTI <Scott.Miller@vandenberg.af.mil>
Date: Wed, 5 Feb 2003 21:45:39 -0000
X-Message-Number: 30

Sorry about that... I started moving it over there and I keep popping in
here to get opinions from the user community, but I guess I've gotten a
little carried away.  =]  I'll try to keep the technical stuff on the spec
list.

Scott / N1VG

(Ok, someone's going to have to explain the power pole thing to me...)

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

Subject: re: aprs spec/words of warning
From: Bob Bruninga <bruninga@usna.edu>
Date: Wed, 5 Feb 2003 16:56:01 -0500 (EST)
X-Message-Number: 31

I agree.  The small advantage of Binary is more than offset by dozens of
reasons to stick with printable ascii.   BOb, WB4APR

On Wed, 5 Feb 2003, Paetzold, Kevin wrote:

>My two cents on the thread about character based protocol spec vs. binary:
>
>One issue with binary is the big-endian/little endian issue.  When
>representing
>a numeric quantity larger than one byte which way will it be represented?
>Most protocols (eg. TCP/IP) are defined with a big endian perspective even
>though
>most computers these days are little endian.  However I can assure you that
>there are lots of big endian machines out there.  Character strings would
>not seem to have this issue and would avoid potential misunderstandings (and
>bugs)
>IMHO.
>
>Another potential issue (which is something that has been hard for many
>people to learn) is that many of the official ANSI specs for various
>programming languages are not at all clear on how bit fields are represented
>
>in memory.  Although I do not lay awake at night reading the ANSI C spec
>the last time it was clear that bit field operations are not ANSI standard.
>This would seem to have the potential for many transportability issues,
>misunderstandings (and bugs) IMHO.
>
>73,
>K1KWP

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

Subject: re: aprs spec/words of warning
From: "Ev Tupis (W2EV)" <w2ev@arrl.net>
Date: Wed, 05 Feb 2003 18:00:28 -0500
X-Message-Number: 32

cc:ing this to the APRSspec list to migrate it there...

>I agree.  The small advantage of Binary is more than offset by dozens of
>reasons to stick with printable ascii.   BOb, WB4APR

I suppose it all depends on what the excersise is trying to accomplish.

If it's simply binary-encoding the existing spec, then then I agree.

From what I'm reading, though...this newly emerging protocol will include:
o finer detail (smaller stept) than what is available in the
  existing protocol
o new parameters that the existing protocol doesn't address

That being said, this new protocol work appears to have more advantage than
what may appear on the surface.

Of course, my opinion and 99-cents gets you a Big-Gulp at the corner
mini-market.

Regards,
Ev, W2EV

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

Subject: Re: [aprsspec] re: aprs spec/words of warning
From: Roger Barker <roger@peaksys.co.uk>
Date: Wed, 5 Feb 2003 23:16:43 +0000
X-Message-Number: 33

In article <LYR26815-119181-2003.02.05-17.49.32--roger#peaksys.co.uk@lis
ts.tapr.org>, Ev Tupis (W2EV) <w2ev@arrl.net> writes
>cc:ing this to the APRSspec list to migrate it there...
>
>>I agree.  The small advantage of Binary is more than offset by dozens of
>>reasons to stick with printable ascii.   BOb, WB4APR
>
>I suppose it all depends on what the excersise is trying to accomplish.
>
>If it's simply binary-encoding the existing spec, then then I agree.
[snip]

Have I missed something here? People are discussing a binary protocol?
And we still have IGATEs and internet servers deliberately mangling
Mic-E posits, because their operators think the APRS-IS cannot reliably
transport 8 bit data...

So is this going to be 7 bit binary?  ;-)

-- 
Roger Barker, G4IDE - roger@peaksys.co.uk
For UI-View go to - http://www.UI-View.com
For WinPack go to - http://www.peaksys.co.uk

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

[commercial content deleted]

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

Subject: Re: Glossy Eyed Readers [was: aprs spec/words of warning]
From: Alex <kr1st@amsat.org>
Date: Tue, 04 Feb 2003 00:35:34 -0500
X-Message-Number: 35

I think it really needs to go to the HT list... Who in the world cares?! 

>...and those interested may certainly subscribe there.

I'm glad we got the thumbs up from you, Eve, to subscribe to the
APRSspec list. Thank you so much.

73,
--Alex KR1ST

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



Read previous mail | Read next mail


 16.11.2026 02:51:56lGo back Go up