Re: [USRP-users] USRP B210 TX-Issues

2018-02-12 Thread Marcus D. Leech via USRP-users 
Sounds about right. 

Sent from my iPhone

> On Feb 12, 2018, at 5:20 PM, Jonathan B  wrote:
> 
> Hi Marcus,
> 
> Thanks! Didn't realise there was a larger range for the B2xx family. At 60dB 
> it seems to perform as well as 20dB on the N210. Is that normal?
> 
> But either way - something I can work with. Thanks.
> 
>   Virus-free. www.avast.com
> 
> 2018-02-09 20:53 GMT+01:00 Marcus D. Leech via USRP-users 
> :
>>> On 02/09/2018 02:48 PM, Jonathan B via USRP-users wrote:
>>> Hi Jeff,
>>> 
>>> Thanks for the response.
>>> 
>>> In both cases a gain of 20dB.
>>> 
>>> Best,
>>> Jonathan
>> The total gain-control range on the B2xx family is larger (80dB) than on the 
>> cards used on X3xxx, N2xx, etc (typically 30.5dB)
>> 
>> Try larger gain values on the B210, like 40 or 50dB.
>> 
>> 
>>> 
 On Feb 9, 2018 8:23 PM, "Jeff Long via USRP-users" 
  wrote:
 What are you using for gain settings?
 
> On 02/09/2018 01:09 PM, Jonathan B via USRP-users wrote:
> Hi everyone,
> 
> I seem to be having issues with the B210 transmitting at an incredibly 
> low power.
> 
> I seem to be getting a 60db difference at the receiver (spectrum 
> analyzer) between the B210 and N210 with perfectly identically configured 
> transmissions using the simple uhd "tx_waveform" example program.
> 
> Has anyone experienced such an issue. I have two B210s that seem to be 
> acting the same way.
> 
> Thanks in advance.
> 
> Best Regards,
> Jonathan
> 
> -
> 
> Probe Output of the B210:
> 
> -- Loading firmware image: C:\Program 
> Files\GNURadio-3.7\share\uhd\images\usrp_b200_fw.hex...
> -- Detected Device: B210
> -- Loading FPGA image: C:\Program 
> Files\GNURadio-3.7\share\uhd\images\usrp_b210_fpga.bin... done
> -- Operating over USB 3.
> -- Detecting internal GPSDO No GPSDO found
> -- Initialize CODEC control...
> -- Initialize Radio control...
> -- Performing register loopback test... pass
> -- Performing register loopback test... pass
> -- Performing CODEC loopback test... pass
> -- Performing CODEC loopback test... pass
> -- Setting master clock rate selection to 'automatic'.
> -- Asking for clock rate 16.00 MHz...
> -- Actually got clock rate 16.00 MHz.
> -- Performing timer loopback test... pass
> -- Performing timer loopback test... pass
>_
>   /
> |   Device: B-Series Device
> | _
> |/
> |   |   Mboard: B210
> |   |   revision: 4
> |   |   product: 2
> |   |   serial: 3113A66
> |   |   name: MyB210
> |   |   FW Version: 8.0
> |   |   FPGA Version: 14.0
> |   |
> |   |   Time sources:  none, internal, external, gpsdo
> |   |   Clock sources: internal, external, gpsdo
> |   |   Sensors: ref_locked
> |   | _
> |   |/
> |   |   |   RX DSP: 0
> |   |   |
> |   |   |   Freq range: -8.000 to 8.000 MHz
> |   | _
> |   |/
> |   |   |   RX DSP: 1
> |   |   |
> |   |   |   Freq range: -8.000 to 8.000 MHz
> |   | _
> |   |/
> |   |   |   RX Dboard: A
> |   |   | _
> |   |   |/
> |   |   |   |   RX Frontend: A
> |   |   |   |   Name: FE-RX2
> |   |   |   |   Antennas: TX/RX, RX2
> |   |   |   |   Sensors: temp, rssi, lo_locked
> |   |   |   |   Freq range: 50.000 to 6000.000 MHz
> |   |   |   |   Gain range PGA: 0.0 to 76.0 step 1.0 dB
> |   |   |   |   Bandwidth range: 20.0 to 5600.0 step 0.0 Hz
> |   |   |   |   Connection Type: IQ
> |   |   |   |   Uses LO offset: No
> |   |   | _
> |   |   |/
> |   |   |   |   RX Frontend: B
> |   |   |   |   Name: FE-RX1
> |   |   |   |   Antennas: TX/RX, RX2
> |   |   |   |   Sensors: temp, rssi, lo_locked
> |   |   |   |   Freq range: 50.000 to 6000.000 MHz
> |   |   |   |   Gain range PGA: 0.0 to 76.0 step 1.0 dB
> |   |   |   |   Bandwidth range: 20.0 to 5600.0 step 0.0 Hz
> |   |   |   |   Connection Type: IQ
> |   |   |   |   Uses LO offset: No
> |   |   | _
> |   |   |/
> |   |   |   |   RX Codec: A
> |   |   |   |   Name: B210 RX dual ADC
> |   |   |   |   Gain Elements: None
> |   | _
> |   |/

Re: [USRP-users] USRP B210 TX-Issues

2018-02-12 Thread Derek Kozel via USRP-users 
Hello Jonathan,

The gain setting in the USRPs are indexed from minimum gain. On most this
means a gain of 0 is actually an attenuation of the signal. The N210's gain
range is based on what amplifiers and attenuators are on the daughterboard
that is installed. The ranges aren't calibrated to be aligned across
different USRP products so what you are seeing is completely normal.

On Feb 12, 2018 10:21 PM, "Jonathan B via USRP-users" <
usrp-users@lists.ettus.com> wrote:

Hi Marcus,

Thanks! Didn't realise there was a larger range for the B2xx family. At
60dB it seems to perform as well as 20dB on the N210. Is that normal?

But either way - something I can work with. Thanks.


Virus-free.
www.avast.com

<#m_-3868461721852336890_m_4051027392395733961_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2018-02-09 20:53 GMT+01:00 Marcus D. Leech via USRP-users <
usrp-users@lists.ettus.com>:

> On 02/09/2018 02:48 PM, Jonathan B via USRP-users wrote:
>
> Hi Jeff,
>
> Thanks for the response.
>
> In both cases a gain of 20dB.
>
> Best,
> Jonathan
>
> The total gain-control range on the B2xx family is larger (80dB) than on
> the cards used on X3xxx, N2xx, etc (typically 30.5dB)
>
> Try larger gain values on the B210, like 40 or 50dB.
>
>
>
> On Feb 9, 2018 8:23 PM, "Jeff Long via USRP-users" <
> usrp-users@lists.ettus.com> wrote:
>
>> What are you using for gain settings?
>>
>> On 02/09/2018 01:09 PM, Jonathan B via USRP-users wrote:
>>
>>> Hi everyone,
>>>
>>> I seem to be having issues with the B210 transmitting at an incredibly
>>> low power.
>>>
>>> I seem to be getting a 60db difference at the receiver (spectrum
>>> analyzer) between the B210 and N210 with perfectly identically configured
>>> transmissions using the simple uhd "tx_waveform" example program.
>>>
>>> Has anyone experienced such an issue. I have two B210s that seem to be
>>> acting the same way.
>>>
>>> Thanks in advance.
>>>
>>> Best Regards,
>>> Jonathan
>>>
>>> -
>>>
>>> Probe Output of the B210:
>>>
>>> -- Loading firmware image: C:\Program Files\GNURadio-3.7\share\uhd\i
>>> mages\usrp_b200_fw.hex...
>>> -- Detected Device: B210
>>> -- Loading FPGA image: C:\Program 
>>> Files\GNURadio-3.7\share\uhd\images\usrp_b210_fpga.bin...
>>> done
>>> -- Operating over USB 3.
>>> -- Detecting internal GPSDO No GPSDO found
>>> -- Initialize CODEC control...
>>> -- Initialize Radio control...
>>> -- Performing register loopback test... pass
>>> -- Performing register loopback test... pass
>>> -- Performing CODEC loopback test... pass
>>> -- Performing CODEC loopback test... pass
>>> -- Setting master clock rate selection to 'automatic'.
>>> -- Asking for clock rate 16.00 MHz...
>>> -- Actually got clock rate 16.00 MHz.
>>> -- Performing timer loopback test... pass
>>> -- Performing timer loopback test... pass
>>>_
>>>   /
>>> |   Device: B-Series Device
>>> | _
>>> |/
>>> |   |   Mboard: B210
>>> |   |   revision: 4
>>> |   |   product: 2
>>> |   |   serial: 3113A66
>>> |   |   name: MyB210
>>> |   |   FW Version: 8.0
>>> |   |   FPGA Version: 14.0
>>> |   |
>>> |   |   Time sources:  none, internal, external, gpsdo
>>> |   |   Clock sources: internal, external, gpsdo
>>> |   |   Sensors: ref_locked
>>> |   | _
>>> |   |/
>>> |   |   |   RX DSP: 0
>>> |   |   |
>>> |   |   |   Freq range: -8.000 to 8.000 MHz
>>> |   | _
>>> |   |/
>>> |   |   |   RX DSP: 1
>>> |   |   |
>>> |   |   |   Freq range: -8.000 to 8.000 MHz
>>> |   | _
>>> |   |/
>>> |   |   |   RX Dboard: A
>>> |   |   | _
>>> |   |   |/
>>> |   |   |   |   RX Frontend: A
>>> |   |   |   |   Name: FE-RX2
>>> |   |   |   |   Antennas: TX/RX, RX2
>>> |   |   |   |   Sensors: temp, rssi, lo_locked
>>> |   |   |   |   Freq range: 50.000 to 6000.000 MHz
>>> |   |   |   |   Gain range PGA: 0.0 to 76.0 step 1.0 dB
>>> |   |   |   |   Bandwidth range: 20.0 to 5600.0 step 0.0 Hz
>>> |   |   |   |   Connection Type: IQ
>>> |   |   |   |   Uses LO offset: No
>>> |   |   | _
>>> |   |   |/
>>> |   |   |   |   RX Frontend: B
>>> |   |   |   |   Name: FE-RX1
>>> |   |   |   |   Antennas: TX/RX, RX2
>>> |   |   |   |   Sensors: temp, rssi, lo_locked
>>> |   |   |   |   Freq range: 50.000 to 6000.000 MHz
>>> |   |   |   |   Gain range PGA: 0.0 to 76.0 step 1.0 dB
>>> |   |   |   |   Bandwidth range: 20.0 to

Re: [USRP-users] "Additional signa"l after a packet transmission

2018-02-12 Thread Marcus Müller via USRP-users 
Hi!

This might really be the fact that the amplifier takes some time to
shut down. This, paired with the possibility of TX/RX crosstalk might
be a contributing factor: That might actually change the DC offset on
the receiving side, and trigger the step response of the DC offset
cancellation (which is observable for about 40-60 ms, if I remember
correctly). You can try to disable the DC offset cancellation on the
USRP source and see if that helps (but probably introduces a DC offset,
which doesn't matter for practical OFDM).

If I read your flow graph correctly, you're using 0 gain on TX and RX -
can you try *a little more* gain on each end? This might change the
ratio of received signal to in-device crosstalk sufficiently that you
won't be able to spot this relative to your signal amplitude.

Regarding consecutive packets: if you look at that overlayed signal,
compared to your OFDM symbol, it's very slowly changing – almost
constant.

In other words, this will end up in the DC bin of the next OFDM frame
anyways, and those are usually not used at all. This would have no
adverse effects at all!

Best regards,
Marcus

On Mon, 2018-02-12 at 14:29 +0100, NAVES Raphael wrote:
> Hi Marcus,
> 
> Thanks for your answer. I will try to be clearer.
> 
> You may find attached the screen shot of my Gnuradio flowgraph which
> is 
> a classical OFDM transmission. First, I'm getting PDU on the
> described 
> socket. PDU are sent on the socket every 25ms by another python
> script 
> running in parallel. Then the message is transormed to a tagged
> stream 
> and go through an classical OFDM modulator. I'm plotting the
> received 
> symbols at the same USRP (reception antenna).
> 
> The problem is described on the screen shot of the received samples.
> As 
> you may see, after each burst, the received samples take few time to
> go 
> back to "the ambient noise level".
> In that case it's not a problem because following packets are
> separated 
> enough in time and have the same power. However, imagine the case
> where 
> I want to receive directly after a packet with high power, a new
> packet 
> with lower power : this packet reception will be disturbed by the
> noise 
> coming after the first packet. How could I remove the noise following
> a 
> packet burst ? Is that a problem of turning off the power amplifier
> in 
> the transmission part ?
> 
> Do not hesitate if I'm not clear enough
> 
> Best,
> 
> Raphael
> 
> 
> On Sat, 10 Feb 2018 17:56:11 +0100, Marcus Müller wrote:
> > Hi Raphaël,
> > 
> > not quite sure I get your problem, but this is rather hard to debug
> > without knowing exactly what your transmitter does.
> > 
> > For example, if you transmit something that isn't zero-mean, then
> > the
> > DC offset cancellation *in* the receiving end would start to cancel
> > out. As that cancellation is effectively a narrow high-pass filter,
> > you'd see its (inverted) step response after you turn off the
> > transmitter.
> > 
> > So, if you could share both your full transmit block diagram as
> > well 
> > as
> > your receiving block diagram, we might be able to help you!
> > 
> > Best regards,
> > Marcus
> > On Fri, 2018-02-09 at 09:28 +0100, NAVES Raphael via USRP-users 
> > wrote:
> > > Hello,
> > > 
> > > For more details, please find attached the received signal in the
> > > time
> > > domain. Clearly after the end of the packet, the signal takes a
> > > certain
> > > time to come back to "the ambient noise". If I zoom, I notice
> > > there
> > > is
> > > still some noise 40ms after the packet. It can disturb the
> > > reception
> > > of
> > > the following packet if its power is less than this additional 
> > > noise.
> > > 
> > > What do you suggest to cancel it ? I'm using the USRP sink/source
> > > blocks from gnuradio for the transmission/reception parts.
> > > 
> > > Best,
> > > 
> > > Raphaël
> > > 
> > > 
> > > On Thu, 08 Feb 2018 21:48:10 +0100, NAVES Raphael via USRP-users
> > > wrote:
> > > > Hello Dan,
> > > > 
> > > > Thanks for your answer. I'm using for transmitting the
> > > > traditional
> > > > USRP sink block provided by Gnuradio Companion. Each packet
> > > > coming
> > > > to
> > > > this block is tagged with its length at the first sample. For
> > > > the
> > > > receiving part, I'm using the USRP source block. Both are used 
> > > 
> > > with
> > > > basic parameters.
> > > > 
> > > > Do you think I should modify/use different parameters for these
> > > > blocks ?
> > > > 
> > > > Raphaël
> > > > 
> > > > On Thu, 8 Feb 2018 11:54:07 -0500, Dan Veeneman wrote:
> > > > > Hello Rafael,
> > > > > 
> > > > > Are you sure the transmitter has stopped radiating
> > > > > immediately
> > > > > after
> > > > > the
> > > > > end of a packet?  The power amplifier on the transmitter may 
> > > 
> > > take
> > > > > a
> > > > > small amount of time to go from powered up to powered down,
> > > > > although
> > > > > 40
> > > > > milliseconds may be excessive.
> > > > > 
> > > > > Do you have a writeup

[USRP-users] add more than 10 blocks in uhd_image_builder

2018-02-12 Thread Snehasish Kar via USRP-users 
Hello


Is it somehow possible to add more than 10  gnu-radio blocks in 
uhd_image_builder.


BR

Snehasish

___
USRP-users mailing list
USRP-users@lists.ettus.com
http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com