Harry, Ernest,
Its not really the clock time that is the problem because D4,
Timcesync and a number of other utilities will snyc the clock to the
network time... Its the interrupts that drive VAC (and clock time) that
I need to adjust.
Sync'ing the clock time to network time does not correct the
interrupt timingproblem that I have.
AL, K0VM
On 3/9/2013 11:10 AM, Ernest Garcia wrote:
Yes!
Here is a Windows Synchronizer.
I have used this sync system for more than 4 years and my internal
clock is never a second late. I use this sync for JT65-HF; where
time is the upmost important for proper operation. I do not have
remember to check the clock. It's all automatic. NO HUMAN
INTERVENTION!
www.pretentiousname.com/timesync/index.html
<http://www.pretentiousname.com/timesync/index.html>
Very explicit and easy to follow instructions with pictures of
every step.
73, Ernest
> Date: Sat, 9 Mar 2013 10:45:56 -0600
> From: [email protected]
> To: [email protected]
> Subject: [FlexEdge] VAC Latency Drift & Slow Windows Clock Time
>
> Does anyone know of a utility to adjust the internal time reference
> on a PC?
> ( NOT sync clock time to network time )
>
> ----
> I recently added a second drive on my PC and installed Windows 8in
> a dual boot configuration with Win XP.
> On Win8, Windows 8 Clock time looses about 3 minutes and 49 seconds per
> day ( 2650 ppm ).
> Booted on Windows XP, with the same MB, the Clock time lost is less
> than 5 seconds per day.
> I remember three years ago when I initially set up XP, I used some sort
> of utility to adjust the internal time reference, but can not find
it now.
> ----
> On Windows 8, using digital modes with VAC, I encountered as
> significant drift in the latency through VAC.
> So I set up a test (using CHUtime ticks ) where I could measure the
> latency differential between the FLex5000 RCA Line out and PSDR VAC
> output routed through VAC, a VAC audio repeater and a USB sound card
> channel. In six measurement runs of six minutes each, the average
change
> in latency differential was 161 milliseconds per minute ( 2670 ppm ).
> The Win 8, tests included runs with two different versions of PSDR,
> three different versions of VAC and heavily used CPU vs. lightly
loaded CPU.
> Repeating the same test, booted on Windows XP, there was no easily
> observable VAC latency drift.
> ----
> Both the Windows 8 Clock time and the VAClatency drift have the same
> (~2660 ppm error ), which I assume is because they are driven from the
> same interruptsource.
>
> ----
> I can and do use a utility to sync the clock time to network time, but
> that does nothing for the VAC latency drift.
>
> Does anyone know of a utility to adjust the internal time reference
on a PC?
>
>
> AL, K0VM
> _______________________________________________
> Flexedge mailing list
> [email protected]
> http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz
> This is the FlexRadio Systems e-mail Reflector called FlexEdge. It
is used for posting topics related to SDR software innovation and
other technical SDR topics.
_______________________________________________
Flexedge mailing list
[email protected]
http://mail.flex-radio.biz/mailman/listinfo/flexedge_flex-radio.biz
This is the FlexRadio Systems e-mail Reflector called FlexEdge. It is used for
posting topics related to SDR software innovation and other technical SDR
topics.
