Message-ID: <4D7FB6B4.5000002@iup.uni-heidelberg.de>
Date: Tue, 15 Mar 2011 19:57:56 +0100
From: =?ISO-8859-1?Q?Stefan_Sch=E4fer?= <Stefan.Schaefer@iup.uni-heidelberg.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.8) Gecko/20100227 Thunderbird/3.0.3
MIME-Version: 1.0
To: rsgb_lf_group@blacksheep.org
References: <AANLkTiksDowcKxyJ86R=p-4SqvwcbAQBjQrGY1efm_jN@mail.gmail.com><003201cbde72$606d6090$0401a8c0@xphd97xgq27nyf><543492.45357.qm@web28102.mail.ukl.yahoo.com><998C9385-2AEE-4C44-91FE-86FE85F09BA9@gmail.com><6F4ACB3DA2BB4E338E9278EEDE300D20@JimPC><4D791085.6000304@freenet.de><C6A2668001FE48DDA6604A3D1C53F5C5@JimPC> <AANLkTimN8Qb6rDFd5FMAYqdcmWeC6PPpBZseXDPp7NTv@mail.gmail.com> <88166509D1CC44BD89560D815F2A8BBA@JimPC> <46829E04645940D4A51EB04524B6C7D7@JimPC>
In-Reply-To: <46829E04645940D4A51EB04524B6C7D7@JimPC>
Subject: Re: LF: Re: VLF Stability and soundcard locking
Content-Type: multipart/alternative;
 boundary="------------050403020201090507030100"
Sender: owner-rsgb_lf_group@blacksheep.org
Precedence: bulk
Reply-To: rsgb_lf_group@blacksheep.org


--------------050403020201090507030100
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Jim, VLF,

Am 12.03.2011 01:51, schrieb James Moritz:
> Dear Andy, Wolf, LF Group,
>
> Over last night and today I did some further tests with my cheapo USB 
> sound card and calibration source, but this time using a different 
> laptop PC. Result - after some fiddling, sample rate error indicated 
> by SpecLab matches measured error of clock crystal frequency, and a 
> nice glitch-free spectral line with 180uHz FFT resolution. So the 
> erratic measured sample rate would seem to be more specific-PC-related 
> than sound card related. I also got glitch-free results using the 
> internal sound card of the desktop machine I tried the USB sound card 
> with previously, which I guess would at least suggest the cause of the 
> problem is not within SpecLab. [...]

Absolutely! I have done some TX tests in the last weeks after the mishap 
in my 10th experiment. There the DFCW-600 transmissions were quite 
fuzzy. I found that the reason seems not the be a EMC problem (strong 
local E fields near the antenna) but rather the PC. Local tests with 
locking to DHO38 showed that the signal was still fuzzy, so the GPS 
module isn't the source of errors as well.
Later i found that the signal is much clearer with another PC (more than 
10 years old HP notebook, once running at win95).

Back to the netbook (running at win7): In the task manager i observed 
the CPU load and found some short and sudden peaks to 100% although no 
other programs were running and WLAN was disabled. I knew that 
everything was fine in the 9th experiment, with exactly the same 
hardware. So something must habe been changed.

The solution: Before some time i changed the _netbooks energy saving 
mode_. It reduces the CPU power if traffic is low. But the reduced power 
seems not to be enough for SL, sometimes. So the system toggles between 
low and high load and this seemed to produce the massive phase glitches. 
Now i choosed "_maximum power_" mode (QRO! :-) )and get a nice and 
stable trace, even in the 6000 window. The trace looks "perfect" in 600 
of course.

So i hope to be able to produce a well readable signal in my 11th 
experiment that will be in April.

73, Stefan/DK7FC





--------------050403020201090507030100
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"   http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Jim, VLF,<br>
<br>
Am 12.03.2011 01:51, schrieb James Moritz:
<blockquote cite="mid:46829E04645940D4A51EB04524B6C7D7@JimPC"   type="cite">Dear Andy, Wolf, LF Group,
  <br>
  <br>
Over last night and today I did some further tests with my cheapo USB
sound card and calibration source, but this time using a different
laptop PC. Result - after some fiddling, sample rate error indicated by
SpecLab matches measured error of clock crystal frequency, and a nice
glitch-free spectral line with 180uHz FFT resolution. So the erratic
measured sample rate would seem to be more specific-PC-related than
sound card related. I also got glitch-free results using the internal
sound card of the desktop machine I tried the USB sound card with
previously, which I guess would at least suggest the cause of the
problem is not within SpecLab.
[...]<br>
</blockquote>
<br>
Absolutely! I have done some TX tests in the last weeks after the
mishap in my 10th experiment. There the DFCW-600 transmissions were
quite fuzzy. I found that the reason seems not the be a EMC problem
(strong local E fields near the antenna) but rather the PC. Local tests
with locking to DHO38 showed that the signal was still fuzzy, so the
GPS module isn't the source of errors as well. <br>
Later i found that the signal is much clearer with another PC (more
than 10 years old HP notebook, once running at win95).<br>
<br>
Back to the netbook (running at win7): In the task manager i observed
the CPU load and found some short and sudden peaks to 100% although no
other programs were running and WLAN was disabled. I knew that
everything was fine in the 9th experiment, with exactly the same
hardware. So something must habe been changed. <br>
<br>
The solution: Before some time i changed the <u>netbooks energy saving
mode</u>. It reduces the CPU power if traffic is low. But the reduced
power seems not to be enough for SL, sometimes. So the system toggles
between low and high load and this seemed to produce the massive phase
glitches. Now i choosed "<u>maximum power</u>" mode (QRO! :-) )and get
a nice and stable trace, even in the 6000 window. The trace looks
"perfect" in 600 of course. <br>
<br>
So i hope to be able to produce a well readable signal in my 11th
experiment that will be in April.<br>
<br>
73, Stefan/DK7FC<br>
<br>
<br>
<br>
<br>
</body>
</html>

--------------050403020201090507030100--