[time-nuts] Oncore VP problem

Rick Hambly (W2GPS) w2gps at cnssys.com
Sat Jul 21 13:44:02 EDT 2007


Your computer may be sensing the serial data stream and declaring it to be a
mouse. This is a generic problem having nothing to do with Tac32 but it and
the solution are in the CNS Clock II and Tac32 manual available where you
got the software.

P.S., I am in the UK at the AMSAT-UK conference.

-----Original Message-----
From: time-nuts-bounces at febo.com [mailto:time-nuts-bounces at febo.com] On
Behalf Of GandalfG8 at aol.com
Sent: Thursday, July 19, 2007 6:13 AM
To: time-nuts at febo.com
Subject: Re: [time-nuts] Oncore VP problem

); SAEximRunCond expanded to false
Errors-To: time-nuts-bounces+w2gps=cnssys.com+w2gps=cnssys.com at febo.com

In a message dated 19/07/2007 02:44:42 GMT Daylight Time,
tom.k3io at gmail.com 

My  suggestion is that you pick up a free evaluation copy of Rick
Hambly's  TAC32 software at http://cnssys.com/cnsclock/Tac32Software.html
. TAC32  knows all the quirks & options that ever existed in a  Motorola
receiver, going all the way back to the Rev.3 PVT6. Then if you  find it
useful, a legal copy can be purchased from Rick, or at members  discount
from TAPR  (http://www.tapr.org/gps_tac32.html).

Hi Tom
Many thanks for the suggestion.
You may have seen my subsequent post in which I commented that I had tried  
TAC32 without solving my problem, only to find the kit was working ok but
an incorrectly labelled connector.
TAC32 does look useful though so I'll check it over more thoroughly  later.
One "interesting" side effect......
Some time after shutting down TAC32 last night, but with the Oncore still  
connected to the serial port and outputting data, my PS2 connected mouse
 misbehaving, with the pointer jumping all over the place then settling down

for  a while before repeating the performance.
It didn't occur to me at first that the incoming serial data might have  
anything to do with it until it started again this morning and I eventually

stopped it by disconnecting the serial lead from the receiver.
Whilst I can't say for sure that running TAC32 was what caused it, it's not

something I've ever seen in the past nor previously this past few  days
running WinOncore.
I'll check later to see if the port shut down properly and also take a look

at the Oncore message stream, perhaps TAC32 may have changed something
as part of its auto setup routine?

time-nuts mailing list -- time-nuts at febo.com
To unsubscribe, go to
and follow the instructions there.

More information about the time-nuts mailing list