Re: [Discuss-gnuradio] (no subject)

2018-10-22 Thread D J
So it works ok with the ettus radio, but I really want to use the
xb200/bladerf combo for the tx filtering capability.  Also, The IF coming
out of the system under test can actually be anywhere between 10MHz and
70MHz.  Looks like I'll be working on it more tomorrow.

On Mon, Oct 22, 2018, 10:43 AM D J  wrote:

> Hello GNURadio friends,
>
> I'm trying to build a simple repeater that receives a 70MHz IF signal over
> a cable and retransmits it at around 200MHz.  Essentially, I want to use an
> SDR as a upconverter.  What's the best way to do this?  Do I just use a
> sink and source block referring to the same SDR?  I have a bladeRF/xb200
> and an Ettus B200 to choose from.  I tried the bladeRF/xb200 with Osmocom
> src/sink blocks but Gnuradio throws an error when I try to run it.  It asks
> if I forgot to specify nchan (number of channels?).   Thanks!
>
> Dustin
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] (no subject)

2018-10-22 Thread D J
Hello GNURadio friends,

I'm trying to build a simple repeater that receives a 70MHz IF signal over
a cable and retransmits it at around 200MHz.  Essentially, I want to use an
SDR as a upconverter.  What's the best way to do this?  Do I just use a
sink and source block referring to the same SDR?  I have a bladeRF/xb200
and an Ettus B200 to choose from.  I tried the bladeRF/xb200 with Osmocom
src/sink blocks but Gnuradio throws an error when I try to run it.  It asks
if I forgot to specify nchan (number of channels?).   Thanks!

Dustin
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] UDP Re-transmission

2018-06-18 Thread D J
Hello all,

I need some advice.  I'm trying to take UDP datagrams from one port,
transport them over an RF link to a receiver, and then send them back over
another UDP port.  Sounds simple, but I'm having a difficult time with it.

Originally I was doing this to transmit text and image files:

[file source]-->[Packet Encoder]-->[GFSK Mod]-->[UHD USRP Sink (B200)]

[Osmocom SDR Source (BladeRF)]-->[GFSK Demod]-->[Packet Decoder]-->[file
sink]

It worked great using files, but once I replaced the File source and sink
blocks with UDP source (port 9003) and sink (port 9004), It wouldn't work.
I also had to remove the packet encoder and decoder blocks.

[UDP source 9003]-->[gfsk mod]-->[UHD USRP Sink (B200]
[Osmocom SDR Source (BladeRF]-->[gfsk demod]-->[UDP sink 9004]

Troubleshooting: Using Wireshark to sniff the source and sink ports, I
could see that the data going to the UDP sink port (9004) was completely
different from what was sent on the UDP source port.  When I connect the
UDP source/sinks together directly, UDP traffic is passed and the datagrams
match. I removed the radios and connected the GFSK mod/demod blocks
directly and the problem persists.  Also, unless I decimated the received
samples by 8, the datagrams on the UDP sink port were different sizes from
those on the UDP source port.  The UDP, IP, and Ethernet headers are
intact, but the payload on the receive side is just random hex 01 and hex
00.

Has anyone implemented something like this before? What am I doing wrong?

Thank you,
Dustin
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] New to Gnu

2018-02-02 Thread D J
Hello all,

I've been doing radio and satellite communications professionally for about
10 years now.  I've just started working with SDR and I have to say...wow.
Even after 10 years as an RF tech, and university training in Computer
Science, this stuff isn't easy to just "pick up".  Thanks to all of you who
actively work on developing Gnu Radio, OOT modules, answer questions on
forums/mailing lists, and maintain repositories to help this project.
You're making it easier for people like me.

Regards,

Dustin
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] Audio Sink for pi

2018-01-24 Thread D J
I had to force reload alsa on a linux box once.  You could try that, too.

On Jan 24, 2018 8:32 AM, "Müller, Marcus (CEL)"  wrote:

> Hello David,
>
> No experience with audio on the pi, but:
> I usually just work with "default" on Linux.
> You can query the possible strings using "aplay -L", if you have aplay
> (ALSA player) installed; not sure hw:1,0 actually maps to something
> that can be used for playback. You could check that reading
> /proc/asound/devices contains kind of a "tree" notation, in a format
> that's basically
>
> X: [ N - M]: digital audio playback
>
> and that would equivalent to hw:N,M, usually. (ALSA's naming remains to
>  be a big f'up, imho). For example, I have a
>
>   7: [ 1]   : control
>   8: [ 1- 3]: digital audio playback
>   9: [ 1- 7]: digital audio playback
>
> in there, so hw:1,7 works, but hw:1,0 doesn't. (I still use
> "hdmi:CARD=NVidia,DEV=1", which I got from "aplay -L".)
>
> Best regards,
> Marcus
>
> On Tue, 2018-01-23 at 22:56 -0600, David Hertel wrote:
> > Hello,
> >
> > I am new here and having big troubles getting the audio sink to work on
> a pi.
> > Everything was cool in windows then I switched to the pi because i want
> to dedicate a box to running my layout full time.
> > Here is my error.
> > audio_alsa_sink0 - [hw:1,0]: snd_pcm_sw_params: Invalid argument
> >
> > I don't know what to put in the Device Name box.  Can anyone help me?
> > --
> > David Hertel
> > Newman-Kees Engineering
> > Evansville, In
> > Cell 812-760-9071
> > ___
> > Discuss-gnuradio mailing list
> > Discuss-gnuradio@gnu.org
> > https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


Re: [Discuss-gnuradio] sending sine wave, but created another unwanted frequency component

2018-01-22 Thread D J
What he said^^

https://en.wikipedia.org/wiki/Nyquist_frequency

On Sun, Jan 21, 2018 at 12:18 PM, Jeff Long  wrote:

> Try reducing the RX filter bandwidth, the gain of the receiver and/or
> transmitter, or moving the TX and RX apart, and see what happens. This is
> aliasing, and probably has nothing to do with software.
>
> On Sun, Jan 21, 2018 at 12:56 PM, Yang Liu  wrote:
>
>> Dear all,
>>
>> In this application, I am trying to send a sine wave at a specific
>> frequency to usrp x310:
>>   sine wave generator ---> usrpx310
>>
>> For the sine wave generator, I use blocks.sig_source_c from gnuradio. The
>> parameters at the transmitter are in the following:
>> center frequency: 1e9 (usrp tuning frequency)
>> sampling_rate: 5e6
>> waveform frequency:  -2.4193125e6 (at the boundary of this frequency
>> band).
>>
>> At the receiver side, I tuned the usrp to 1e9, and used 10e6 to sample
>> the received data. According to the spectrum I observed, there are two
>> frequency components, one is at -2.4193125e6, another one is around at
>> -2.4193125e6 + 5e6 (not very sure if they are exactly symmetric). Actually,
>> this happens when the sine wave is very close to the boundary (near -2.5e6
>> or 2.5e6). As I moved the waveform frequency to the center (1e9), the
>> second frequency disappeared.  Firstly, I thought that it is the power
>> issue, however, after I decreased power level, the second component is
>> still there.
>>
>> According to the function (blocks.sig_source_c), what it generates is a
>> exp(j*2*pi*f_waveform/f_s). Therefore, there should not exist any second
>> frequency component. I feel very confused about why this can happen.
>>
>> Any thoughts about this will be greatly appreciated!
>>
>> Best,
>> Yang
>>
>> ___
>> Discuss-gnuradio mailing list
>> Discuss-gnuradio@gnu.org
>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>>
>>
>
> ___
> Discuss-gnuradio mailing list
> Discuss-gnuradio@gnu.org
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
>
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio