[Date Prev][Date Next][Thread Prev][Thread Next] - [Date Index][Thread Index][Author Index]
Re: SatPC32 Question
- Subject: [amsat-bb] Re: SatPC32 Question
- From: "Alan P. Biddle" <APBIDDLE@xxxxxxxxxx>
- Date: Sun, 14 Jan 2007 15:19:15 -0600
- DKIM-Signature: a=rsa-sha1; c=relaxed/simple; d=united.net; s=spiritmail;t=1168809560; bh=0K3lciK0dXLJULEAB3wezfcEJHM=; h=Reply-To:From:To:References:Subject:Date:Organization:Message-ID:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-MimeOLE:Thread-Index:In-Reply-To:X-Virus-Scanned:X-Virus-Status; b=m63W/1SI/eM+NKkbSC2HyXv01aAsRqCvS6IQPlU2r8Eu5ygaDzI8c7pMeLOMRFqHN6K1IKq+naiVZD/fhSvavw==
Steve,
A couple of areas to look at. First, take a look at the CAT menu, and see
what your update frequency interval is. I use 20 Hz for SSB. That gives a
smooth tracking, and once netted, SATPC32 will track through a full pass.
It WILL update every few seconds, but the jump should be small enough that
it is just barely audible. You can get by with a much larger step size, but
of course the jump will be more noticeable, but still usable.
Are you using a USB serial port, or a "real" port? There is nothing wrong
with a USB serial port per se, but some of them are rather flakey. I had
one which required about 5 times the recommended CAT delay to work at all,
and would usually eventually cause the radio to lose tracking exactly as you
describe. The was not a problem with SATPC32!! Nothing else worked
reliably with that port either, so I finally gave up on it and went back to
a real serial port, since I had one to spare.
Alan
WA4SCA
_______________________________________________
Sent via AMSAT-BB@amsat.org. Opinions expressed are those of the author.
Not an AMSAT-NA member? Join now to support the amateur satellite program!
Subscription settings: http://amsat.org/mailman/listinfo/amsat-bb
AMSAT Home