thats not his problem though... since it had been working and is now dead.
also, when ct can't keep up it usually produces a 'buffer overrun' error instead
of 'radio timeout'. the 'radio timeout' message is usually when the computer
asks for an update and the radio doesn't respond in time.
however, if you use ethernet for the network you can have everyone talking to
their radios and spinning dials and watch the alt-j windows update as fast as
the frequencies can come out of the radios. losing the radio interface when you
have spots to grab can be a real slowdown.
"Jim White, K4OJ" wrote:
>
> a fly in the ointment, eh?
>
> imho radio timeout usually occurs when the computers cannot keep up with the
> baud rate and slowing things down a notch can cure - i.e. going to 4800 from
> 9600...mebbe your shack computers are norunning another software program and
> the system has reached that point where it says too much I can't take it
> anymore!
>
> I have never been able to get and entire network of computers to be fully
> talking and it is the radio interface that has been sacrificed...
>
> Jim, K4OJ
>
> ----- Original Message -----
> From: "Robert Shohet" <kq2m@mags.net>
> To: <1000mp@qth.net>; <ct-user@contesting.com>
> Sent: Saturday, July 07, 2001 7:39 AM
> Subject: [ct-user] FT1000MP radio control problem
>
> >
> > Hi Guys,
> >
> > Weird problem just developed with BOTH FT1000MP's.
> >
> > I am using 2 FT1000MP's on 2 computers with CT ver 9.53. When I used this
> > setup in WPXCW, CT, BOTH radios and both computers talked to each other
> > flawlessly.
> >
> > Now, six weeks later, the same 2 FT1000MP's can't talk to the computers.
> > BOTH radios give me a "radio timeout" message. For control purposes, I
> went
> > back into the WPXCW logs with NO settings changed. What worked perfectly
> 6
> > six weeks ago, does not work now. Nothing in the setup has changed nor
> have
> > any cables been moved.
> >
> > The radios can talk to each other using the Alt G ("Gab") function, but
> > whenever I try to change freq. using the keyboard I get the "radio
> timeout"
> > message. Likewise, when I change bands with the radio, the computer does
> > not note the freq. change.
> >
> > Several weeks ago I was banging something on the operating table and I
> > wondered whether or not this might have affected the 'MP's - but there
> > appear to be no ill effects other than the radios/computers can't talk
> with
> > each other.
> >
> > Any thoughts on what the problem might be and how to diagnose it?
> >
> > If one radio didn't talk to the computer I might think it was a damaged
> > radio/computer interface, but BOTH radios?
> >
> > Your help and thoughts please.
> >
> > Tnx & 73
> >
> > Bob KQ2M
> >
> >
> >
> > --
> > WWW: http://www.k1ea.com/
> > Submissions: ct-user@contesting.com
> > Administrative requests: ct-user-REQUEST@contesting.com
> > Problems: owner-ct-user@contesting.com
> >
>
> --
> WWW: http://www.k1ea.com/
> Submissions: ct-user@contesting.com
> Administrative requests: ct-user-REQUEST@contesting.com
> Problems: owner-ct-user@contesting.com
--
David Robbins K1TTT
e-mail: mailto://k1ttt@berkshire.net
web: http://www.k1ttt.net
AR-Cluster node: 145.69MHz or telnet://k1ttt.net
--
WWW: http://www.k1ea.com/
Submissions: ct-user@contesting.com
Administrative requests: ct-user-REQUEST@contesting.com
Problems: owner-ct-user@contesting.com
|