behalf of Ron Economos <w...@comcast.net>
Sent: Monday, September 30, 2024 5:27:19
PM
To: discuss-gnuradio@gnu.org
<discuss-gnuradio@gnu.org>
Subject: Re: dvbt2 transmitter can not be
---
*From:*
discuss-gnuradio-bounces+ceren.karakose=outlook@gnu.org
on behalf of Ron Economos
*Sent:* Monday, September 30, 2024 5:27:19 PM
*To:* discuss-gnuradio@gnu.org
*Subject:* Re: dvbt2 transmitter can not be real-time wi
that if you ever plan to go above 10M samples/sec, use
>> an ethernet-connected SDR.
>>
>> Get Outlook for Android <https://aka.ms/AAb9ysg>
>> --
>> *From:* discuss-gnuradio-bounces+ceren.karakose=outlook@gnu.org
>> on beha
onomos
*Sent:* Monday, September 30, 2024 5:27:19 PM
*To:* discuss-gnuradio@gnu.org
*Subject:* Re: dvbt2 transmitter can not be real-time with LimeSDR
Sorry, but UHD is a big CPU hog for transmitting (at least with
the B2X0
series of devices).
Ron
On 9/30/
=outlook@gnu.org
on
behalf of Ron Economos
*Sent:* Monday, September 30, 2024 5:27:19 PM
*To:* discuss-gnuradio@gnu.org
*Subject:* Re: dvbt2 transmitter can not be real-time with LimeSDR
Sorry, but UHD is a big CPU hog for transmitting (at least with
the B2X0
ser
On 30/09/2024 10:27, Ron Economos wrote:
Sorry, but UHD is a big CPU hog for transmitting (at least with the
B2X0 series of devices).
Ron
I just did a quick test using "benchmark_rate" into a B210, doing a "tx"
test at 30Msps. That consumed 52% of a single
CPU on my i5-6200 system at 2.7GHz
t Outlook for Android <https://aka.ms/AAb9ysg>
*From:* discuss-gnuradio-bounces+ceren.karakose=outlook@gnu.org
on
behalf of Ron Economos
*Sent:* Monday, September 30, 2024 5:27:19 PM
*To:* discuss-gnuradio@gnu.org
*Subjec
plan to go above 10M samples/sec, use an
> ethernet-connected SDR.
>
> Get Outlook for Android <https://aka.ms/AAb9ysg>
> --
> *From:* discuss-gnuradio-bounces+ceren.karakose=outlook....@gnu.org
> on behalf
> of Ron Economos
> *Sent:* Monday, September 30, 2024 5:27
Subject: Re: dvbt2 transmitter can not be real-time with LimeSDR
Sorry, but UHD is a big CPU hog for transmitting (at least with the B2X0
series of devices).
Ron
On 9/30/24 07:21, Marcus D. Leech wrote:
> You should investigate the transport parameters for UHD USB devices here:
Sorry, but UHD is a big CPU hog for transmitting (at least with the B2X0
series of devices).
Ron
On 9/30/24 07:21, Marcus D. Leech wrote:
You should investigate the transport parameters for UHD USB devices here:
https://files.ettus.com/manual/page_transport.html#transport_usb
UHD *IS* a larg
On 30/09/2024 01:30, Ali G. Dezfuli wrote:
When I run dvbt2 transmitter examples from gr-dtv without any
hardware, “Probe Rate” block in GRC shows 15e6 samples per second at
the output of the Tx (which needs about 9 Msps to work in real-time.)
Next, I connected USRP B200mini, but it showed un
The file gnuradio/gr-dtv/examples/README.dvbt2 contains links to TS
files crafted with the correct bitrate for each example flow graph. For
the vv011-1kfft.grc flow graph, it's:
https://www.w6rz.net/vv011-1kfft.ts
The correct invocation for dvbt2rate is:
./dvbt2rate 8 1 2 1966 48 1 1 0 0 3 0
Thanks Ron!
How can I make the related TS file? (e.g. for vv011-1kfft.grc)
The list in https://github.com/drmpeg/dtv-utils does not include QPSK!
On Mon, Sep 30, 2024 at 4:29 PM Ron Economos wrote:
> You could try DVB-T2 configurations that use less CPU. Both smaller FFT
> size and lower bitrate
You could try DVB-T2 configurations that use less CPU. Both smaller FFT
size and lower bitrate help. For example try the following test flow graphs:
vv009-4kfft.grc 27.588664 Mbps
vv010-2kfft.grc 14.364704 Mbps
vv011-1kfft.grc 6.169662 Mbps
If your receiver allows it, you can also use smaller
14 matches
Mail list logo
