Return-Path: Received: (qmail 17414 invoked from network); 4 May 2000 08:15:27 -0000 Received: from unknown (HELO post.thorcom.com) (212.172.148.70) by grants.core.plus.net.uk with SMTP; 4 May 2000 08:15:27 -0000 Received: from majordom by post.thorcom.com with local (Exim 3.02 #1) id 12nGgK-00002s-00 for rsgb_lf_group-outgoing@blacksheep.org; Thu, 04 May 2000 09:08:24 +0100 Content-Transfer-Encoding: 8bit Received: from bob.dera.gov.uk ([192.5.29.90]) by post.thorcom.com with esmtp (Exim 3.02 #1) id 12nGgG-00002n-00 for rsgb_lf_group@blacksheep.org; Thu, 04 May 2000 09:08:20 +0100 Received: by bob.dera.gov.uk; (8.8.8/1.3/10May95) id JAA03626; Thu, 4 May 2000 09:11:11 +0100 (BST) X-Priority: 3 X-MSMail-Priority: Normal Received: (qmail 8929 invoked from network); 4 May 2000 09:04:19 -0000 Received: from gauntlet.mail.dera.gov.uk (172.16.9.10) by baton.dera.gov.uk with SMTP; 4 May 2000 09:04:19 -0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Received: by gauntlet.mail.dera.gov.uk; id HAA20379; Thu, 4 May 2000 07:53:10 GMT Received: from unknown(146.80.11.40) by gauntlet.mail.dera.gov.uk via smap (3.2) id xma020290; Thu, 4 May 00 07:52:36 GMT Received: from frn-gold-1.dera.gov.uk (unverified) by mailguard.dera.gov.uk (Content Technologies SMTPRS 4.1.5) with ESMTP id for ; Thu, 4 May 2000 09:11:53 +0100 Received: by FRN-GOLD-1 with Internet Mail Service (5.0.1460.8) id <2J09085M>; Thu, 4 May 2000 09:06:20 +0100 Message-ID: <3617AC3245C2D1118A840000F805359C017528B5@pdw-mercury-1.dera.gov.uk> From: "Talbot Andrew" To: rsgb_lf_group@blacksheep.org Subject: LF: Spectran accuracy Date: Thu, 4 May 2000 09:06:18 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1460.8) Content-Type: text/plain; charset=iso-8859-1; format=flowed Precedence: bulk Reply-To: rsgb_lf_group@blacksheep.org X-Listname: rsgb_lf_group Sender: Another problem with soundcards is that of timebase accuracy, and in some cases even stability. Many cases of severe errors were identified by G3PLX during the development of PSK31 In the better cards (real Soundblaster compatibles) the frequencies are derived from dedicated correct frequency crystals so the CD sampling rates derived from 44100 Hz are exact (well, within crystal accuracy anyway). The 8 kHz rate is a different matter though. This cannot be derived exactly from the same xtal as the 44k1 rates, and an approximation is often taken by selecting the nearest integer divide ratio. Errors seen here amount to several Hz at 8 kHz depending on the individual chip set in use. The best cards have a separate xtal for this rate and the exact frequency is generated. Some SB hardware built onto PC motherboards uses whatever crystal is in the PC (often the 14.318 MHz one) to generate the SB sampling rates. Again with integer dividers errors of several Hz can be seen. The worst, according to Peter, is a CR controlled system. I have never seen anything this bad and the story may be apocryphal, but he has had errors of many 10s of Hz at 8kHz reported. I have checked the following : 1) Older 16 bit true Soundblaster - all sampling rates exact (meaning within about 10 parts per million of the true values) 2) Newer PCI bus compatible true Soundblaster - ditto. 3) Onboard SB hardware on a wide range of Dell pentiums (Pentia ? :-) - 44k1 derivatives 'exact'. Errors from 0 to 6 Hz on the 8 kHz rate depending on age / type of machine. 4) Toshiba satellite laptop - 44k1 derivatives 'exact' , 8 kHz rate - 7 Hz error PSK31 has a calibration routine built in to take out this sampling rate error and store the calibration constant. But with the temperature ranges that PCs go through from turn on to several hours of operation, the crude packaged oscillators they use can easily move a few 10s of PPM. At 8 kHz this drift alone is several times the minimum Sprectran resolution and a few Hz initial error is off the scale without calibration ! Andy G4JNT > >>Further I noticed that launching another application while running > Spectran > >>caused a kind of 'frequency shift' (see screenshot at my webpage). > >> > >Alberto found this same problem, but he says that debugging will be > difficult, > >and will probably take some time. Incidentally, he is releasing a new > "beta" > >version (beta3). > > Just to straigthen things a bit up : we are talking of two different > problems : > > 1) The frequency error Marco is talking about, is known to me since > some time, > and it is caused by a wrong initial design assumption of Spectran, > i.e. that the > frequency ruler scale must start at an integral multiple of 1 Hz. > This because at > that time Spectran was meant for EME use, where sub-Hertz > resolutions are not > needed. Now that with beta 3 we can do down to 21 milliHz, this > must revised. > > 2) The frequency shift observed and reported by Rik and Alan, is a > completely new > thing, for which, at the moment, I have no explanation. I saw, one > time only, a shift > of 0.5 Hz, which I attributed to my RX. I wasn't launching or > using any other > application at the moment. As this shift has been signalled by > more than one person, > and on signals locked to some standards, then I must investigated > into it. > > Thanks for those reports, and don't be shy to send others. The very > first reason for > putting out a beta before the final release was just to receive this > kind of reports. > > 73s > Alberto I2PHD > ----------------- > > -- The Information contained in this E-Mail and any subsequent correspondence is private and is intended solely for the intended recipient(s). For those other than the recipient any disclosure, copying, distribution, or any action taken or omitted to be taken in reliance on such information is prohibited and may be unlawful.