On 05/15/2019 05:45 PM, Glen I Langston wrote:
Hi Marcus,
That’s great. What could you hear/detect with the 90 kHz bandwidth?
Glen
I used it strictly for SIDs in the VLF band up to 40kHz or so...
I had a loop antenna, about 1.2m diameter, and about 10 windings of
#20ga wire. No tuning
Hi Marcus,
That’s great. What could you hear/detect with the 90 kHz bandwidth?
Glen
> On May 15, 2019, at 5:28 PM, Marcus D. Leech wrote:
>
> On 05/15/2019 03:23 PM, Brad Hein wrote:
>> Great suggestion thank you! This also gives me new topics to read up on as I
>> am still a VLF amateur.
On 05/15/2019 03:23 PM, Brad Hein wrote:
Great suggestion thank you! This also gives me new topics to read up
on as I am still a VLF amateur.
[Sent from mobile device]
I used a Berhringer "mini-MIC" microphone amplifier, which has a
balanced, XLR, input, and has bandwidth out to
about
Great suggestion thank you! This also gives me new topics to read up on as
I am still a VLF amateur.
[Sent from mobile device]
On Wed, May 15, 2019, 1:20 PM John Coppens On Thu, 2 May 2019 16:22:24 -0400
> Brad Hein wrote:
>
> > I took a Raspberry Pi and attached a 48KHz USB sound card, with a
On Thu, 2 May 2019 16:22:24 -0400
Brad Hein wrote:
> I took a Raspberry Pi and attached a 48KHz USB sound card, with a big
> magnetic loop antenna fed into the mic.
Just a suggestion: If you have a loop antenna, which is a symmetrical antenna,
and couple it to an asymmetrical input (MIC), you
On 05/15/2019 10:46 AM, Achilleas Anastasopoulos wrote:
Hi all,
I have recently run an old experiment that used to work fine:
One UHD:USRP Tx is sending a constant tone at 1GHz
One UHD:USRP Rx is receiving at 1GHz and displays in X-Y mode.
Observations:
1) When the 2 USRPs have default
Hi all,
I have recently run an old experiment that used to work fine:
One UHD:USRP Tx is sending a constant tone at 1GHz
One UHD:USRP Rx is receiving at 1GHz and displays in X-Y mode.
Observations:
1) When the 2 USRPs have default (internal) clock I see a circle (due to
frequency instability).
My suggestion at this point is to take the -exact- "work" code from a block
that seems to be causing this memory issue and move it into a test program as a
subroutine. Then, from "main" create a replicated set of calls to this "work"
and see what happens. The goal here is to remove the GR part
Hello Ben,
In order to test the current hypothesis, I upgraded my system from Ubuntu
16.04 to 18.04 and GNU Radio from 3.7.11 to 3.7.13.5.
Still, the leak persists. Surprisingly, Michael didn't experience the issue
on his MacOS, running the exact code I'm running at the moment.
I'm not sure what
