OpenBCM V1.13 (Linux)

Packet Radio Mailbox

DB0FHN

[JN59NK Nuernberg]

 Login: GUEST





  
ZL3AI  > APRDIG   20.12.00 16:01l 239 Lines 7747 Bytes #999 (0) @ WW
BID : 35138_ZL3AI
Read: GUEST
Subj: TAPR Digest, Dec 18, 3/10
Path: DB0ABH<DB0CWS<DB0ROF<DB0XPO<DB0FC<DF0HMB<DB0HES<OZ7BOX<OZ2DIZ<RV3DHC<
      HA3PG<PP5BLU<PY3KW<ZL2TZE<ZL2TZE<ZL2WA<ZL2BAU<ZL3VML
Sent: 001218/2320Z @:ZL3VML.#80.NZL.OC #:51011 [Chch-NZ] FBB7.00g25 $:35138_ZL3
From: ZL3AI@ZL3VML.#80.NZL.OC
To  : APRDIG@WW
Date: Mon, 18 Dec 2000 10:29:29 -0600

X-Message-Number: 13

Okay, Great, Now I have it! It WAS simple.

Now can I get some Hints on Getting an I-gate to work?


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

Subject: Re: 9600 Baud Cxxx
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 18 Dec 2000 12:25:58 -0500 (EST)
X-Message-Number: 14

On Mon, 18 Dec 2000, Jeff King corrected me...(but alas incorrectly)

> > Something that USA Amateurs had refused to use (in general) even 18 years
> > after 9600 baud TNC's were available.
> 
> Lets look at U.S. packet history... (1200 bd) No store-bought or kit
> TNC's were available in the U.S. AX.25 didn't exist.... The only real
> activity was in Canada, from which these first U.S. amateurs took their
> technology.

Wrong, we in AMRAD in Washington DC had the Vancouver boards on the
air long before 1982. It was at the SAME time that we in AMRAD were
writing the AX.25 SPEC!  I was there and was a member of the Board.  My
AMRAD BBS in Vienna VA, using a Vancouver board was one of the first in
the country, I think it was 1979 but don't have time to go dig it all up.

> In 1985 ... we had our first 9600bps modem design,
> from K9NG. TAPR shortly picked this up as a kit later in 1985/86. 

OK, I was wrong.  9600bd was 15 instead of 18 years ago..  Still today, in
2000, I do not see 9600 baud in general use in the USA.  I think anyone
should be able to see that point.

de WB4APR, Bob




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

Subject: Re: Changeing callsign in APRSdos
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 18 Dec 2000 12:29:45 -0500 (EST)
X-Message-Number: 15

On Mon, 18 Dec 2000, Stephen M. King wrote:

> I have APRSdos on my main computer and I would like to add a ssid to my
> call.  How do I change the callsign?

Two ways.

1) Restart the program at the dos prompt with the "/new" on the end
2) edit the first two lines in the C:\CFIG8??.APR file

de WB4APR, Bob



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

Subject: Re: Aprs Serve
From: Bill Diaz <billdiaz@megsinet.net>
Date: Mon, 18 Dec 2000 12:15:43 -0600
X-Message-Number: 16

Bob,
  Be advised that many position packets output by ver 2.4.6 contain garbage 
control characters in the payload.
I am using a registered version of 2.4.7 with APRServe.

Bill KC9XG

On Monday, December 18, 2000 10:22 AM, Guy Story [SMTP:kc5goi@tapr.org] wrote:
> Bob, try backing up to 2.4.6 if you can.  I connected to second.aprs.net
> and did not receive the message.  Only not having registered software
> should keep you from igating, not software being out of date.  2.4.7 is
> the most current version of WinAPRS.  There is no reason for it to show
> being out of date.

> 73,
>
> Guy Story
> KC5GOI
> kc5goi@tapr.org
> http://www.kc5goi.net
>


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

Subject: Re: 9600bps radios
From: Bob Bruninga <bruninga@usna.edu>
Date: Mon, 18 Dec 2000 13:53:04 -0500 (EST)
X-Message-Number: 17

Could this possibly end the Great 9600 baud Debate? 

> Jeff now says:  ... The fact that Kenwood got so close ..., is quite
> commendable for a "jack of all trades" cadilliac type radio. But it is
> not reflective of a state of the art dedicated 9600bps data  radio. This
> is no dig on you or ... Kenwood. They did a good job....

> But anyone that wants to do medium (9.6k) speed packet, is better served 
> by buying a radio designed from the ground up for that purpose...
> Why are we having this debate then?
> -Jeff

Bingo.  We have been debating your earlier repetative Public claims of
"shoddy engineering" and "Kenwood is showing DISRESPECT to the the
worldwide ham market by selling a flawed product".. *were unfair*.

Now that you have *softened your retoric* I think we both look forward to
some good measurements on some of the "other" radios to help guide us to
what is practical in amateur practice..  

What I have objected to is your biased and repeated negativism toward
a pretty darn good radio for what it was designed to do.

Why dont we stop here.
de WB4APR, Bob

But there were other missrepresentations and corrections for those
following this junk:

Jeff said:
> I DIDN'T say that 9600 GMSK("fsk") should outperform 1200 AFSK by 15 dB, 
> I said with the radio in question there was a 15 db DISADVANTAGE (or
> difference) from what things ideally should be.

Maybe what you MEANT to say, but Here is exactly what you said:

QUOTE
There may be a 7db difference, but in reality we are looking at the
Kenwood being at a 15db DISADVANTAGE of where it really should be at. 
UNQUOTE

Such biased statements discredit your arguments and is what compells me
to respond..  There is no radio on earth that can do 15 dB better than 0.5
uv at 9600 baud.  I am only taking to task your continuing obfuscation of
facts and references to cover your biased opinion.

> This never had anything to do with radio reviews, just your statement that
> 1200 baud AFSK is 9dB better then direct 9600bps modulation.....

Again, I **** never said that ****.  Everyone knows that is not true at
all.. I said 1200 baud is 9dB better than 9600 baud when ****both are
using appropriately matched FSK bandwidths/modulation***.  Which we are
not...

> This supports the statements...  That is, that state of the art
> amateur 9600bps performance should be similar to 1200baud AFSK, and in some
> cases, slightly better. 

"Should be" is the key word.  You keep slam dunking the Kenwood where
I made some measurements.  I simply want to see some measurements from the
other "amateur 9600 bps performance" to which you refer.  We would all
like to see how much better they can be or how disserving your claims are
of "shoddy engineering" and "Kenwood is showing DISRESPECT to the the
worldwide ham market by selling a flawed product"..

de WB4APR, Bob



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

Subject: Re: Aprs Serve
From: Bill Vodall <wa7nwp@yahoo.com>
Date: Mon, 18 Dec 2000 11:19:49 -0800 (PST)
X-Message-Number: 18

--- Guy Story <kc5goi@tapr.org> wrote:
> Bob, try backing up to 2.4.6 if you can>

But don't use 2.4.6 for an Igate...  It drops bits on
Mic-E packets...  122 degrees Longitude becomes 22 degrees.

Bill

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

Subject: Re: 9600bps radios
From: Timothy J Salo <tjs@tc.umn.edu>
Date: Mon, 18 Dec 2000 13:21:54 -0600
X-Message-Number: 19

> Date: Mon, 18 Dec 2000 13:53:04 -0500 (EST)
> From: Bob Bruninga <bruninga@usna.edu>
> Subject: [aprssig] Re: 9600bps radios
> 	[...]
> Could this possibly end the Great 9600 baud Debate? 

Well, it may be unlikely, given that we appear to two guys who are neither
able to let the other have the last word nor able to definitely provide the
last word themselves.

> Why dont we stop here.
>	[...]

Hmmm...   You didn't (or couldn't).

-tjs

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

Subject: Re: 9600 Baud Cxxx
From: Bill Vodall <wa7nwp@yahoo.com>
Date: Mon, 18 Dec 2000 11:40:52 -0800 (PST)
X-Message-Number: 20



> Still
> today, in
> 2000, I do not see 9600 baud in general use in the USA.  I think
> anyone
> should be able to see that point.
> 
> de WB4APR, Bob

WETNET in the Puget Sound area has FOUR 9600 baud repeaters and
a fifth one on the way.   I'd call that general use.

Considering that a repeater gives about 38% of the available bandwidth
compared to 18% for Aloha (no carrier sense) or 10% (or less) for a
digipeater hindered channel like 144.39, we will be able to "share"
all of the NWAPRS traffic and a good portion of the world wide



Read previous mail | Read next mail


 16.11.2026 19:54:43lGo back Go up