[hpsdr] No smoke! (but distorted audio)

[Paul Beckmann]

Thanks, Graham.

It's likely not the computer performance. I'm running a new ATOM box that,
with the SDR-1K, runs at 16-25% processor utilization. I just upgraded from
an under-powered computer so I know that that crud sounds like and this
isn't it. It is 'roughness' in the audio but no background buzz or noise
that is unusual with no signal tuned in.

Just running Ozy and Mercury at this time so I'll try putting them in
adjacent slots.

The setup for clock sources is as you say. I'll check again to make sure I
didn't take out J8 on the Mercury board. I have not upgraded any firmware on
either Ozy or Mercury. I don't own any special blaster hardware but will
look at the svn repository readme when I return home.

I'll also look at the signal level calibration tonight.

Thanks for your thoughts.

73
--Paul, wa0rse



On Fri, Jan 23, 2009 at 9:43 AM, Graham / KE9H <KE9H at austin.rr.com> wrote:

> Paul:
>
> It could be a couple of things. Likely not shielding or your grounding.
>
> A low performance computer can get overloaded by processing and leave a lot
> of audio gaps, or you could be hearing what a marginally locked or unlocked
> clock recovery sounds like (crackling sound).
>
> If a crackling sound...
> If you are running just Ozy and Mercury, put them in adjacent slots on the
> bus. Do NOT take out jumper J8 on Mercury. Make sure Mercury is selected as
> the source of both 10 MHz and 122.88 MHz clocks at SetUp->General->HPSDR.
> If still present, go to the SVN...
> \repos_sdr_hpsdr\trunk\USBBlaster-Binaries
> and follow the instructions in the ReadMe to upgrade the firmware in
> Mercury to version 2.4.
>
> If repetitive gaps in audio...
> Usually a computer with marginal horsepower.
> Stop all applications on your computer, other than PowerSDR.
> Make sure Sample size under SetUp->Audio is set to maximum size (2048).
> If that doesn't work, , go to the SVN...
> \repos_sdr_hpsdr\trunk\USBBlaster-Binaries
> and follow the instructions in the ReadMe to upgrade the firmware in
> Mercury to version 2.4.
> Then, set "sample rate" at SetUp->Audio is set to 48000, for minimum CPU
> loading.
>
> --- Graham / KE9H
>
> ==
>
>
> Paul Beckmann wrote:
>
>> ***** High Performance Software Defined Radio Discussion List *****
>>
>> Well, I jumped the Tortoise/svn, USBIO, and board power-up hurdles tonight
>> with Atlas, Ozy, and Mercury and actually heard WWV and some CW on 80
>> meters. Understand that I have the Atlas just sitting on a piece of paper
>> with the boards plugged in, an old Dell supply sitting right next to it, and
>> the board only grounded through the PS and the 3rd wire of the power cord.
>>  What I did notice, however, was very distorted audio, scratchy. (Actually
>> it sounded a lot like a 10GHz rainscatter signal!) Is this to be expected
>> with the entire lack of shielding or would the gurus of the group expect
>> something isn't quite functioning properly? (I do have extensive static
>> control devices on the antenna and was careful to discharge potential static
>> on the P.S. chassis every time I wanted to plug something in.
>>
>> Or did I just do something really stupid?
>>
>> Best 73's!
>>
>> --Paul, wa0rse
>>
>> P.S. Windows XP likes you to "eject" Ozy before powering it off, just like
>> any other USB device! Duh!
>> ==
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/attachments/20090123/fa008662/attachment-0003.htm>