I'm sorry if it sounded like I was putting down na. I write software
and realize that over the years it is always up to the software writers
to adapt to different hardware. Hardware makers never check on what the
software wants, they pick something that is easy to make and out it
comes, then the software adds something to talk to it. Just look at the
mess with all the different radios, rotors, dvk/dvps, tncs, that ham
programs have to support, not to mention printers, monitors, keyboards,
and other peripherals that are out there... if all of those were
standardized writing software in a pc world would be easy! I use ct
here mostly because of the Ethernet networking(how many of the na users
that have asked me how to network na with Ethernet have asked for it
here??) and because it works with the hardware that I have (except for
the ts-2000 that I am bugging ken to add), unfortunately there are some
contests that it doesn't support and some guest ops would like to use it
for s/o... so it just seemed logical to add another option to the
already long list of options for setting the radio a/b bit.
David Robbins K1TTT
e-mail: mailto:k1ttt@arrl.net
web: http://www.k1ttt.net
AR-Cluster node: 145.69MHz or telnet://dxc.k1ttt.net
> -----Original Message-----
> From: David A. Pruett [mailto:k8cc@comcast.net]
> Sent: Thursday, August 15, 2002 23:38
> To: David Robbins; na-user@contesting.com
> Subject: Re: [NA-User] radio a/b bit
>
> At 08:16 PM 8/15/02 +0000, David Robbins wrote:
> >Is there any way to get the radio a/b pin on the parallel port to
work
> >like ct?? I hate to have to butcher the so2r master that works with
ct
> >or tr but not na just for this.
>
> For my own personal sanity, I have to make this statement:
>
> In 1996 we published the first schematic for a computer controlled
SO2R
> box. I e-mailed K1EA and N6TR in an attempt to commonize the
necessary
> port signals. I never got any answer from K1EA. N6TR's answer was
that
> no
> SO2R box was necessary with TRLog because it had separate keying ports
> (fine for CW but ignores SSB). I went ahead and commonized the other
LPT
> bits with TRLog as my best attempt at standardization.
>
> CT's SO2R bit bounced around between different port pins on LPT1 and
LPT2
> then finally settled down somewhere. At some point TRLog decided to
> support an SO2R bit and mimic'd CT. I don't see why these programs
could
> not have followed the standard which had already been established for
> several years.
>
> The other culprit in this is Array Solutions, who produced the SO2R
Master
> with alleged NA support based on third hand information which turned
out
> to
> be wrong. Now users like Dave Robbins have to modify their boxes just
to
> make NA work.
>
> If all the SO2R Master users need is the A/B select bit I'm willing
> provide
> a way to support this. Just tell me what the pin number or bit number
is.
>
> I realize that all of this is futile, like trying to nail jello to a
> tree. I'm sorry but it really irks me when NA is made to sound like
it's
> the oddball when the truth is in this regard it was the leader.
>
> Dave
|