Re: cmakelists.txt fot C++ IDE

2024-08-01 Thread Ali G. Dezfuli
Done! Big Thanks!
I just connected a "Signal Source" to a "Null Sink" in GRC, changed the
Option's "Output Language" to C++,
pushed "Generate" (F5), took a look at the generated CMakeLists.txt, and
found the answer.

Thanks!

On Thu, Aug 1, 2024 at 10:15 PM Marcus Müller  wrote:

> Hi Ali,
>
> since CMake is the default build system we use both for our OOT templates
> (as used by
> gr_modtool) and by the C++ code generated throug GRC, I'd say:
>
> just use the existing work as template.
>
> What you're doing here is mixing modern CMake, i.e. a config/target-based
> method of
> defining the compiler and linker properties of your compilation units,
> with manual
> "include_directories" things. Probably not a great idea! If you compare
> that with what
> `gr_modtool` generates in its lib/CMakeLists.txt, you'll find how we'd, as
> a project,
> would recommend you do it.
>
> Best,
> Marcus
>
> On 01.08.24 11:17, Ali G. Dezfuli wrote:
> > Hi all,
> > I want to work with simple gnuradio objects in a C++ IDE (e.g.
> Qtcreator) using CMake
> > build system.
> > I am running ubuntu 22.04 and gnuradio 3.10.11.0.
> > How can I write its cmakelists.txt?
> >
> > For example, to just test these PMT lines:
> >
> > #include// [...]
> >
> pmt::pmt_tP=pmt::from_long(23);std::cout< >
> > I add the following lines to its cmakelists.tx
> >
> > # Find GNU Radio package, specifying required components
> > find_package(Gnuradio "3.10" REQUIRED COMPONENTS pmt)  # Adjust the
> version and components
> > as needed
> >
> > # Check if GNU Radio is found
> > if(Gnuradio_FOUND)
> >  message(STATUS "GNU Radio found.")
> >  message(STATUS "GNU Radio include dirs: ${Gnuradio_INCLUDE_DIRS}")
> >  message(STATUS "GNU Radio libraries: ${Gnuradio_LIBRARIES}")
> > else()
> >  message(FATAL_ERROR "GNU Radio not found!")
> > endif()
> >
> > # Include directories for your project
> > include_directories(
> >  ${Gnuradio_INCLUDE_DIRS}  # GNU Radio include directories
> >  ${CMAKE_SOURCE_DIR}/include  # Your custom include directories
> > )
> >
> > # Define the executable
> > add_executable(myproject${SOURCES})
> >
> > # Link the executable with GNU Radio libraries
> > target_link_libraries(myproject ${GNURADIO_LIBRARIES})
> >
> > but it doesn't work.
> >
> > I'd be grateful if someone help me write working cmakelists.txt.
> >
> > Thanks!
> >
>
>


cmakelists.txt fot C++ IDE

2024-08-01 Thread Ali G. Dezfuli
Hi all,
I want to work with simple gnuradio objects in a C++ IDE (e.g. Qtcreator)
using CMake build system.
I am running ubuntu 22.04 and gnuradio 3.10.11.0.
How can I write its cmakelists.txt?

For example, to just test these PMT lines:

 #include  // [...] pmt::pmt_t P = pmt::from_long(23);
std::cout << P << std::endl; pmt::pmt_t P2 = pmt::from_complex(0,1);
std::cout << P2 << std::endl; std::cout << pmt::is_complex(P2) <<
std::endl;

I add the following lines to its cmakelists.tx

# Find GNU Radio package, specifying required components
find_package(Gnuradio "3.10" REQUIRED COMPONENTS pmt)  # Adjust the
version and components as needed

# Check if GNU Radio is found
if(Gnuradio_FOUND)
message(STATUS "GNU Radio found.")
message(STATUS "GNU Radio include dirs: ${Gnuradio_INCLUDE_DIRS}")
message(STATUS "GNU Radio libraries: ${Gnuradio_LIBRARIES}")
else()
message(FATAL_ERROR "GNU Radio not found!")
endif()

# Include directories for your project
include_directories(
${Gnuradio_INCLUDE_DIRS}  # GNU Radio include directories
${CMAKE_SOURCE_DIR}/include  # Your custom include directories
)

# Define the executable
add_executable(myproject ${SOURCES})

# Link the executable with GNU Radio libraries
target_link_libraries(myproject ${GNURADIO_LIBRARIES})

but it doesn't work.

I'd be grateful if someone help me write working cmakelists.txt.

Thanks!


qa_fir_filter test fails in make test

2023-12-16 Thread Ali G. Dezfuli
Hi all,
I am installing gnuradio v3.10.8.0
Both UHD and Volk have passed their tests in make test completely (100%)
but as I run make test after building gnuradio v3.10.8.0 I get this single
error:


139/263 Testing: qa_fir_filter
139/263 Test: qa_fir_filter
Command: "/usr/bin/sh" "qa_fir_filter_test.sh"
Directory: /home/ali/opt/gnuradio/build/gr-filter/python/filter
"qa_fir_filter" start time: Dec 16 15:35 +0330
Output:
--
...FF..
==
FAIL: test_fir_filter_fsf_001 (__main__.test_filter)
--
Traceback (most recent call last):
  File "/home/ali/opt/gnuradio/gr-filter/python/filter/qa_fir_filter.py",
line 173, in test_fir_filter_fsf_001
self.assertComplexTuplesAlmostEqual(expected_data, result_data, 5)
  File
"/home/ali/opt/gnuradio/gnuradio-runtime/python/gnuradio/gr_unittest.py",
line 73, in assertComplexTuplesAlmostEqual
return all([
  File
"/home/ali/opt/gnuradio/gnuradio-runtime/python/gnuradio/gr_unittest.py",
line 74, in 
self.assertComplexAlmostEqual(x, y, places, msg)
  File
"/home/ali/opt/gnuradio/gnuradio-runtime/python/gnuradio/gr_unittest.py",
line 37, in assertComplexAlmostEqual
raise self.failureException(
AssertionError: 1 != 2 within 5 places

==
FAIL: test_fir_filter_fsf_002 (__main__.test_filter)
--
Traceback (most recent call last):
  File "/home/ali/opt/gnuradio/gr-filter/python/filter/qa_fir_filter.py",
line 188, in test_fir_filter_fsf_002
self.assertComplexTuplesAlmostEqual(expected_data, result_data, 5)
  File
"/home/ali/opt/gnuradio/gnuradio-runtime/python/gnuradio/gr_unittest.py",
line 73, in assertComplexTuplesAlmostEqual
return all([
  File
"/home/ali/opt/gnuradio/gnuradio-runtime/python/gnuradio/gr_unittest.py",
line 74, in 
self.assertComplexAlmostEqual(x, y, places, msg)
  File
"/home/ali/opt/gnuradio/gnuradio-runtime/python/gnuradio/gr_unittest.py",
line 37, in assertComplexAlmostEqual
raise self.failureException(
AssertionError: 5 != 6 within 5 places

--
Ran 11 tests in 0.028s

FAILED (failures=2)

Test time =   0.12 sec
--
Test Failed.
"qa_fir_filter" end time: Dec 16 15:35 +0330
"qa_fir_filter" time elapsed: 00:00:00
--


I am using Ubuntu 22.04.3.
On a core i9 13900K

p.s. I changed the branch to 3.10.7.0 and v3.10.6.0 but the error remains
the same

Thanks!


phase maintenance in a USRP loop

2023-08-15 Thread Ali G. Dezfuli
Hi all,

I have two transceivers A and B each one is connected by cables to a USRP
B200mini (TX/RX for send and RX2 for receive)

Using GNU Radio, for each iteration, transceiver A starts to send a burst
of RC-filtered, BPSK-modulated PN sequence.
Side B waits for the burst and as soon as it gets that (by correlation),
detects the
phase ramp (because of the carrier frequency offset (CFO)) on the PN
symbols
and makes a new burst with the same phase ramp, and sends its burst back to
side A.
Then I observe the phase of the received symbols at A.

As far as there is no sample loss/insertion, I suppose the phase continuity
is held and
should receive a constant phase on the received symbols at A whose value
depends
on the delay between A and B which is fixed.

I observe these issues:
1- in some iterations, the received phase at A is not fixed.
2- in some iterations, the received phase at A is fixed but does not equal
other iterations.

Would be grateful if anyone could help me with this.
Thanks!


Re: B2xx round trip delay

2023-08-12 Thread Ali G. Dezfuli
By the way, if instead of time, we concentrate on the phase change on the
correlation peaks,
can we get to a better measure to relate it to RTD? For instance, we can
send two sequences
of the same type and track the correlation peaks phase change and relate it
to the RTD?
Thank you!

On Sun, Aug 13, 2023 at 8:15 AM Marcus D. Leech 
wrote:

> On 13/08/2023 00:36, Ali G. Dezfuli wrote:
> > Hi all,
> > I'd like to measure the round-trip delay (RTD) between two B200 USRPs.
> > For that, I send a raised-cosined-filtered, BPSK modulated
> > PN-sequence, and as soon as
> > I get this signal at the receiver, send back the same sequence from
> > the Rx to the Tx, and by correlation, I find the RTD.
> > The question is that the measured RTD is not fixed. I wonder how can I
> > make it fixed when the distance between the two USRPs is fixed.
> > After that (A -> B -> A) I want to do that in reverse order (B -> A ->
> > B) and expect to have the same RTD.
> > Thanks
> In your scenario, the latency will necessarily be variable--after all
> your samples are entering a computer program where those
>samples are processed and then sent back in the other direction.
> Since computer software on a general-purpose operating
>system cannot have fixed latency at fine-grained levels, this is
> completely expected.
>
> This document may help:
>
> https://kb.ettus.com/Synchronizing_USRP_Events_Using_Timed_Commands_in_UHD
>
>
>
>


Re: B2xx round trip delay

2023-08-12 Thread Ali G. Dezfuli
I appreciate the information and advice you have shared and sincerely thank
you for the assistance.

On Sun, Aug 13, 2023 at 8:15 AM Marcus D. Leech 
wrote:

> On 13/08/2023 00:36, Ali G. Dezfuli wrote:
> > Hi all,
> > I'd like to measure the round-trip delay (RTD) between two B200 USRPs.
> > For that, I send a raised-cosined-filtered, BPSK modulated
> > PN-sequence, and as soon as
> > I get this signal at the receiver, send back the same sequence from
> > the Rx to the Tx, and by correlation, I find the RTD.
> > The question is that the measured RTD is not fixed. I wonder how can I
> > make it fixed when the distance between the two USRPs is fixed.
> > After that (A -> B -> A) I want to do that in reverse order (B -> A ->
> > B) and expect to have the same RTD.
> > Thanks
> In your scenario, the latency will necessarily be variable--after all
> your samples are entering a computer program where those
>samples are processed and then sent back in the other direction.
> Since computer software on a general-purpose operating
>system cannot have fixed latency at fine-grained levels, this is
> completely expected.
>
> This document may help:
>
> https://kb.ettus.com/Synchronizing_USRP_Events_Using_Timed_Commands_in_UHD
>
>
>
>


B2xx round trip delay

2023-08-12 Thread Ali G. Dezfuli
Hi all,
I'd like to measure the round-trip delay (RTD) between two B200 USRPs. For
that, I send a raised-cosined-filtered, BPSK modulated PN-sequence, and as
soon as
I get this signal at the receiver, send back the same sequence from the Rx
to the Tx, and by correlation, I find the RTD.
The question is that the measured RTD is not fixed. I wonder how can I make
it fixed when the distance between the two USRPs is fixed.
After that (A -> B -> A) I want to do that in reverse order (B -> A -> B)
and expect to have the same RTD.
Thanks


OOT modules: adding a faulty block causes whole OOT module not to work

2023-06-12 Thread Ali G. Dezfuli
Hi all,
I made an OOT module named gr-tmo, adding some blocks and everything was ok.
But when I add another block which uses gnuradio filter (from
fir_filter.h), the whole module stops working
and even removing the faulty block using gr_modtool doesn't help, which
makes me start the whole module
from the beginning!!!
versions are: GR 3.10.6, ubuntu 22.04
thanks


Re: OOT modules config for versions

2023-06-12 Thread Ali G. Dezfuli
YOU REALLY SAVED MY LIFE Ron!

On Mon, Jun 12, 2023 at 11:28 AM Ron Economos  wrote:

> You just use find_package() now. Here's an example:
>
> https://github.com/drmpeg/gr-atsc3/blob/master/CMakeLists.txt#L77
>
> You also have to link to the modules in lib/CMakeLists.txt. Like so:
>
> https://github.com/drmpeg/gr-atsc3/blob/master/lib/CMakeLists.txt#L42
>
> Ron
> On 6/12/23 00:01, Ali G. Dezfuli wrote:
>
> Hi all,
>
> I'd like to use libgnuradio-filter in my OOT module/blocks.
> I've read the following link which is about configuring OOT modules for
> adding other parts of gnuradio:
> https://wiki.gnuradio.org/index.php/OutOfTreeModulesConfig
> I couldn't find the line:
>
> set(GR_REQUIRED_COMPONENTS RUNTIME)
>
> in the root cmakelists.txt file the OOT module (e.g. here gr-howto).
>
>
> I wonder how I can manage that in newer versions.
>
> Versions are:
>
> GR v3.10.6.0
> Ubuntu 22.04
>
> Thank you very much!
>
>


OOT modules config for versions

2023-06-12 Thread Ali G. Dezfuli
Hi all,

I'd like to use libgnuradio-filter in my OOT module/blocks.
I've read the following link which is about configuring OOT modules for
adding other parts of gnuradio:
https://wiki.gnuradio.org/index.php/OutOfTreeModulesConfig
I couldn't find the line:

set(GR_REQUIRED_COMPONENTS RUNTIME)

in the root cmakelists.txt file the OOT module (e.g. here gr-howto).

I wonder how I can manage that in newer versions.

Versions are:

GR v3.10.6.0
Ubuntu 22.04

Thank you very much!


building OOT blocks in Qt editor

2023-06-04 Thread Ali G. Dezfuli
Hey!
I just switched to the latest versions (GR: 3.6.10, Ubuntu 22.04, UHD
4.3.0, Qt Creator 10.0.1).
I've just added an OOT module and block and could successfully build and
add it to the gnuradio and it works well.
To have a better graphical editor, I just want to develop in Qt editor
(qtcreator).
I wonder what should be put in the .pro file to let me compile it there.
Thanks in advance!


Re: Constellation Modulator delay calculation

2023-01-10 Thread Ali G. Dezfuli
thank you, Jared and Cinead!
Sure it helps Jared!

On Wed, Jan 11, 2023 at 7:39 AM U L  wrote:

> Ali,
>
> I think the example uses the generic_mod block
> <https://github.com/gnuradio/gnuradio/blob/main/gr-digital/python/digital/generic_mod_demod.py>
> inside. This block uses the polyphase arb resampler for antialiasing. The
> line that computes the rrc delay is here
> <https://github.com/gnuradio/gnuradio/blob/0becf06a397edc1b2dcf440785e40b73f76433ad/gr-digital/python/digital/generic_mod_demod.py#L146>.
> Briefly, for your example with sps = 2, it's (11 x 2 x 2 - 2) / 2 = 21. For
> sps = 4, (11 x 4 x 4 - 4) / 2 = 86. I don't know if this helps.
>
> Jared.
>
> On Tue, Jan 10, 2023 at 6:08 PM Cinaed Simson 
> wrote:
>
>> Hi Ali - your flowchart has no device and no throttle. You need to add a
>> throttle.
>>
>> And I don't the expertise or the time to look at the source code.
>>
>> So I'm punting back to the list.
>>
>> -- Cinaed
>>
>>
>> On 1/10/23 03:10, Ali G. Dezfuli wrote:
>> > Hi everybody,expertise
>> >
>> > I just want to know how the delay of the "Constellation Modulator"
>> > block in GRC is calculated.
>> > In fact, whether you set the block's last parameter "truncate filter
>> > transient" or not, a delay of 86 samples could be generated, no matter
>> > how many points are in the constellation.
>> >
>> > This magic number (i.e. 86) also appears in
>> > "linear_equalizer_compare.grc" example (in
>> > gr-digital/examples/equalizers in modulated_sync_word variable).
>> >
>> > I know this delay depends on the "samples per symbol" (sps) parameter
>> > and comes from the built-in pulse shaping with its default taps equal:
>> >firdes.root_raised_cosine(32, 32, 1.0, exess_bw, 32*11*sps)
>> > and with the following sps to delay relation:
>> > (sps=2, delay=21)
>> > (sps=4, delay=86)
>> > (sps=8, delay=348)
>> > etc.
>> >
>> > my GR version is:   v3.11.0.0git-316-gc11667ef
>> > thank you all!
>>
>>
>>


Constellation Modulator delay calculation

2023-01-10 Thread Ali G. Dezfuli
Hi everybody,

I just want to know how the delay of the "Constellation Modulator" block in
GRC is calculated.
In fact, whether you set the block's last parameter "truncate filter
transient" or not, a delay of 86 samples could be generated, no matter how
many points are in the constellation.

This magic number (i.e. 86) also appears in "linear_equalizer_compare.grc"
example (in gr-digital/examples/equalizers in modulated_sync_word variable).

I know this delay depends on the "samples per symbol" (sps) parameter and
comes from the built-in pulse shaping with its default taps equal:
   firdes.root_raised_cosine(32, 32, 1.0, exess_bw, 32*11*sps)
and with the following sps to delay relation:
(sps=2, delay=21)
(sps=4, delay=86)
(sps=8, delay=348)
etc.

my GR version is:   v3.11.0.0git-316-gc11667ef
thank you all!


Re: DQPSK constellation

2023-01-09 Thread Ali G. Dezfuli
Hi Cinaed,
thanks for your reply,
GR version: v3.11.0.0git-316-gc11667ef
the GRC file is attached.
thanks

On Tue, Jan 10, 2023 at 1:49 AM Cinaed Simson 
wrote:

> Hi Ali - please state the version of gnuardio you're using and post the
> flowgraph used to generate your problem.
>
> -- Cinaed
>
> On 1/8/23 23:56, Ali G. Dezfuli wrote:
>
> Hi all,
> I've managed to get to the same signal of the block "Constellation
> Modulator" by using these blocks in concatenation:
>
> {  --> repack bits --> differential encoder --> constellation encoder (or:
> chunks to symbols) --> polyphase arbitrary resampler --> }
>
> and tried them for bpak, qpsk, 8psk, and 16qam, and all OK.
>
> This command digital.constellation_dqpsk().points() gets the following
> points:
>
> [(1.4142135381698608+1.4142135381698608j),
> (-1.4142135381698608+1.4142135381698608j),
> (-1.4142135381698608-1.4142135381698608j),
> (1.4142135381698608-1.4142135381698608j)]
>
> which is different from the documentation of DQPSK which says:
>
> 01 | 00
> ---
> 11 | 10
>
> I wonder how I can get the same result for DQPSK by using the above series
> of blocks.
>
> thanks
>
>
>
>


corr_00_copy.grc
Description: Binary data


DQPSK constellation

2023-01-08 Thread Ali G. Dezfuli
Hi all,
I've managed to get to the same signal of the block "Constellation
Modulator" by using these blocks in concatenation:

{  --> repack bits --> differential encoder --> constellation encoder (or:
chunks to symbols) --> polyphase arbitrary resampler --> }

and tried them for bpak, qpsk, 8psk, and 16qam, and all OK.

This command digital.constellation_dqpsk().points() gets the following
points:

[(1.4142135381698608+1.4142135381698608j),
(-1.4142135381698608+1.4142135381698608j),
(-1.4142135381698608-1.4142135381698608j),
(1.4142135381698608-1.4142135381698608j)]

which is different from the documentation of DQPSK which says:

01 | 00
---
11 | 10

I wonder how I can get the same result for DQPSK by using the above series
of blocks.

thanks


Re: usrp n200 problem: error when running uhd_cal_tx_dc_offset

2022-12-28 Thread Ali G. Dezfuli
Ok, thanks!
You are a great help!

On Thu, Dec 29, 2022 at 8:33 AM Marcus D. Leech 
wrote:

> On 28/12/2022 23:55, Ali G. Dezfuli wrote:
> > seems it's ok:
> >
> > $ uhd_usrp_probe
> > [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
> > UHD_4.3.0.0-14-g1e718d9b
> > [INFO] [USRP2] Opening a USRP2/N-Series device...
> > [INFO] [USRP2] Current recv frame size: 1472 bytes
> > [INFO] [USRP2] Current send frame size: 1472 bytes
> >   _
> >  /
> > |   Device: USRP2 / N-Series Device
> > | _
> > |/
> > |   |   Mboard: N200r4
> > |   |   hardware: 2576
> > |   |   mac-addr: 00:80:2f:0a:ce:45
> > |   |   ip-addr: 192.168.20.2
> > |   |   subnet: 255.255.255.255
> > |   |   gateway: 255.255.255.255
> > |   |   gpsdo: none
> > |   |   serial: F1700B
> > |   |   name: ali_01
> > |   |   FW Version: 12.4
> > |   |   FPGA Version: 11.1
> > |   |
> > |   |   Time sources:  none, external, _external_, mimo
> > |   |   Clock sources: internal, external, mimo
> > |   |   Sensors: mimo_locked, ref_locked
> > |   | _
> > |   |/
> > |   |   |   RX DSP: 0
> > |   |   |
> > |   |   |   Freq range: -50.000 to 50.000 MHz
> > |   | _
> > |   |/
> > |   |   |   RX DSP: 1
> > |   |   |
> > |   |   |   Freq range: -50.000 to 50.000 MHz
> > |   | _
> > |   |/
> > |   |   |   RX Dboard: A
> > |   |   |   ID: WBX v3, WBX v3 + Simple GDB (0x0057)
> > |   |   |   Serial: EDR29PFXW
> > |   |   | _
> > |   |   |/
> > |   |   |   |   RX Frontend: 0
> > |   |   |   |   Name: WBXv3 RX+GDB
> > |   |   |   |   Antennas: TX/RX, RX2, CAL
> > |   |   |   |   Sensors: lo_locked
> > |   |   |   |   Freq range: 68.750 to 2200.000 MHz
> > |   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
> > |   |   |   |   Bandwidth range: 4000.0 to 4000.0 step 0.0 Hz
> > |   |   |   |   Connection Type: IQ
> > |   |   |   |   Uses LO offset: No
> > |   |   | _
> > |   |   |/
> > |   |   |   |   RX Codec: A
> > |   |   |   |   Name: ads62p44
> > |   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB
> > |   |   |   |   Gain range fine: 0.0 to 0.5 step 0.1 dB
> > |   | _
> > |   |/
> > |   |   |   TX DSP: 0
> > |   |   |
> > |   |   |   Freq range: -200.000 to 200.000 MHz
> > |   | _
> > |   |/
> > |   |   |   TX Dboard: A
> > |   |   |   ID: WBX v3 (0x0056)
> > |   |   |   Serial: EDR29PFXW
> > |   |   |   ID: WBX + Simple GDB, WBX v3 + Simple GDB, WBX v4 + Simple
> > GDB, WBX-120 + Simple GDB (0x004f)
> > |   |   |   Serial: EDR29PFGS
> > |   |   | _
> > |   |   |/
> > |   |   |   |   TX Frontend: 0
> > |   |   |   |   Name: WBXv3 TX+GDB
> > |   |   |   |   Antennas: TX/RX, CAL
> > |   |   |   |   Sensors: lo_locked
> > |   |   |   |   Freq range: 68.750 to 2200.000 MHz
> > |   |   |   |   Gain range PGA0: 0.0 to 31.0 step 1.0 dB
> > |   |   |   |   Bandwidth range: 4000.0 to 4000.0 step 0.0 Hz
> > |   |   |   |   Connection Type: IQ
> > |   |   |   |   Uses LO offset: No
> > |   |   | _
> > |   |   |/
> > |   |   |   |   TX Codec: A
> > |   |   |   |   Name: ad9777
> > |   |   |   |   Gain Elements: None
> >
> You might try backing-out to UHD 4.2 or even UHD 4.1.0.5 (which is what
> is packaged with Ubuntu 22.04).
>
> I recall (haven't found the thread on usrp-users yet) that there was a
> problem with the _cal utilities in UHD 4.3.
>
> I'd recommend that you join the usrp-users mailng list, where more
> USRP-specific discussions take place.
>
>
>


Re: usrp n200 problem: error when running uhd_cal_tx_dc_offset

2022-12-28 Thread Ali G. Dezfuli
seems it's ok:

$ uhd_usrp_probe
[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
UHD_4.3.0.0-14-g1e718d9b
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
  _
 /
|   Device: USRP2 / N-Series Device
| _
|/
|   |   Mboard: N200r4
|   |   hardware: 2576
|   |   mac-addr: 00:80:2f:0a:ce:45
|   |   ip-addr: 192.168.20.2
|   |   subnet: 255.255.255.255
|   |   gateway: 255.255.255.255
|   |   gpsdo: none
|   |   serial: F1700B
|   |   name: ali_01
|   |   FW Version: 12.4
|   |   FPGA Version: 11.1
|   |
|   |   Time sources:  none, external, _external_, mimo
|   |   Clock sources: internal, external, mimo
|   |   Sensors: mimo_locked, ref_locked
|   | _
|   |/
|   |   |   RX DSP: 0
|   |   |
|   |   |   Freq range: -50.000 to 50.000 MHz
|   | _
|   |/
|   |   |   RX DSP: 1
|   |   |
|   |   |   Freq range: -50.000 to 50.000 MHz
|   | _
|   |/
|   |   |   RX Dboard: A
|   |   |   ID: WBX v3, WBX v3 + Simple GDB (0x0057)
|   |   |   Serial: EDR29PFXW
|   |   | _
|   |   |/
|   |   |   |   RX Frontend: 0
|   |   |   |   Name: WBXv3 RX+GDB
|   |   |   |   Antennas: TX/RX, RX2, CAL
|   |   |   |   Sensors: lo_locked
|   |   |   |   Freq range: 68.750 to 2200.000 MHz
|   |   |   |   Gain range PGA0: 0.0 to 31.5 step 0.5 dB
|   |   |   |   Bandwidth range: 4000.0 to 4000.0 step 0.0 Hz
|   |   |   |   Connection Type: IQ
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   RX Codec: A
|   |   |   |   Name: ads62p44
|   |   |   |   Gain range digital: 0.0 to 6.0 step 0.5 dB
|   |   |   |   Gain range fine: 0.0 to 0.5 step 0.1 dB
|   | _
|   |/
|   |   |   TX DSP: 0
|   |   |
|   |   |   Freq range: -200.000 to 200.000 MHz
|   | _
|   |/
|   |   |   TX Dboard: A
|   |   |   ID: WBX v3 (0x0056)
|   |   |   Serial: EDR29PFXW
|   |   |   ID: WBX + Simple GDB, WBX v3 + Simple GDB, WBX v4 + Simple GDB,
WBX-120 + Simple GDB (0x004f)
|   |   |   Serial: EDR29PFGS
|   |   | _
|   |   |/
|   |   |   |   TX Frontend: 0
|   |   |   |   Name: WBXv3 TX+GDB
|   |   |   |   Antennas: TX/RX, CAL
|   |   |   |   Sensors: lo_locked
|   |   |   |   Freq range: 68.750 to 2200.000 MHz
|   |   |   |   Gain range PGA0: 0.0 to 31.0 step 1.0 dB
|   |   |   |   Bandwidth range: 4000.0 to 4000.0 step 0.0 Hz
|   |   |   |   Connection Type: IQ
|   |   |   |   Uses LO offset: No
|   |   | _
|   |   |/
|   |   |   |   TX Codec: A
|   |   |   |   Name: ad9777
|   |   |   |   Gain Elements: None



On Thu, Dec 29, 2022 at 8:17 AM Marcus D. Leech 
wrote:

> On 28/12/2022 23:35, Ali G. Dezfuli wrote:
>
> thanks Marcus,
> I have checked benchmark_rate with no lost packets even at the highest
> rate of 25 Ms/s.
> It is connected via ethernet 1G.
>
> Isn't it because of outdated firmware and fpga?
>
> If the FPGA code is out-of-date, UHD will complain.
>
> What does
>
> uhd_usrp_probehave to say about it.
>
>
>
>
> the output of benchmark_rate:
>
> $ ./benchmark_rate --rx_rate 25e6
>
> [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
> UHD_4.3.0.0-14-g1e718d9b
> [00:00:00.000444] Creating the usrp device with: ...
> [INFO] [USRP2] Opening a USRP2/N-Series device...
> [INFO] [USRP2] Current recv frame size: 1472 bytes
> [INFO] [USRP2] Current send frame size: 1472 bytes
> Using Device: Single USRP:
>   Device: USRP2 / N-Series Device
>   Mboard 0: N200r4
>   RX Channel: 0
> RX DSP: 0
> RX Dboard: A
> RX Subdev: WBXv3 RX+GDB
>   TX Channel: 0
> TX DSP: 0
> TX Dboard: A
> TX Subdev: WBXv3 TX+GDB
>
> [00:00:01.466484658] Setting device timestamp to 0...
> [00:00:01.467214590] Testing receive rate 25.00 Msps on 1 channels
> [00:00:11.467783232] Benchmark complete.
>
>
> Benchmark rate summary:
>   Num received samples: 249982026
>   Num dropped samples:  0
>   Num overruns detected:0
>   Num transmitted samples:  0
>   Num sequence errors (Tx): 0
>   Num sequence errors (Rx): 0
>   Num underruns detected:   0
>   Num late commands:0
>   Num timeouts (Tx):0
>   Num timeouts (Rx):0
>
>

Re: usrp n200 problem: error when running uhd_cal_tx_dc_offset

2022-12-28 Thread Ali G. Dezfuli
thanks Marcus,
I have checked benchmark_rate with no lost packets even at the highest rate
of 25 Ms/s.
It is connected via ethernet 1G.

Isn't it because of outdated firmware and fpga?


the output of benchmark_rate:

$ ./benchmark_rate --rx_rate 25e6

[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
UHD_4.3.0.0-14-g1e718d9b
[00:00:00.000444] Creating the usrp device with: ...
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
Using Device: Single USRP:
  Device: USRP2 / N-Series Device
  Mboard 0: N200r4
  RX Channel: 0
RX DSP: 0
RX Dboard: A
RX Subdev: WBXv3 RX+GDB
  TX Channel: 0
TX DSP: 0
TX Dboard: A
TX Subdev: WBXv3 TX+GDB

[00:00:01.466484658] Setting device timestamp to 0...
[00:00:01.467214590] Testing receive rate 25.00 Msps on 1 channels
[00:00:11.467783232] Benchmark complete.


Benchmark rate summary:
  Num received samples: 249982026
  Num dropped samples:  0
  Num overruns detected:0
  Num transmitted samples:  0
  Num sequence errors (Tx): 0
  Num sequence errors (Rx): 0
  Num underruns detected:   0
  Num late commands:0
  Num timeouts (Tx):0
  Num timeouts (Rx):0


Done!

On Thu, Dec 29, 2022 at 8:04 AM Ali G. Dezfuli  wrote:

> thanks Marcus,
> I have checked benchmark_rate with no lost packets even at the highest
> rate of 25 Ms/s.
> It is connected via ethernet 1G.
>
> Isn't it because of outdated firmware and fpga?
>
>
> the output of benchmark_rate:
>
> $ ./benchmark_rate --rx_rate 25e6
>
> [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
> UHD_4.3.0.0-14-g1e718d9b
> [00:00:00.000444] Creating the usrp device with: ...
> [INFO] [USRP2] Opening a USRP2/N-Series device...
> [INFO] [USRP2] Current recv frame size: 1472 bytes
> [INFO] [USRP2] Current send frame size: 1472 bytes
> Using Device: Single USRP:
>   Device: USRP2 / N-Series Device
>   Mboard 0: N200r4
>   RX Channel: 0
> RX DSP: 0
> RX Dboard: A
> RX Subdev: WBXv3 RX+GDB
>   TX Channel: 0
> TX DSP: 0
> TX Dboard: A
> TX Subdev: WBXv3 TX+GDB
>
> [00:00:01.466484658] Setting device timestamp to 0...
> [00:00:01.467214590] Testing receive rate 25.00 Msps on 1 channels
> [00:00:11.467783232] Benchmark complete.
>
>
> Benchmark rate summary:
>   Num received samples: 249982026
>   Num dropped samples:  0
>   Num overruns detected:0
>   Num transmitted samples:  0
>   Num sequence errors (Tx): 0
>   Num sequence errors (Rx): 0
>   Num underruns detected:   0
>   Num late commands:0
>   Num timeouts (Tx):    0
>   Num timeouts (Rx):0
>
>
> Done!
>
> On Wed, Dec 28, 2022 at 7:00 PM Marcus D. Leech 
> wrote:
>
>> On 28/12/2022 04:55, Ali G. Dezfuli wrote:
>> > Hi all,
>> > I have gnuradio on this system:
>> > ubuntu 22.04
>> > uhd 4.3.0.0-14-g1e718d9b
>> > gnuradio v3.11.0.0git-316-gc11667ef
>> >
>> > I have a USRP N200 from 2011 but have not worked with it for the last
>> > couple of years.
>> > After a long while, I just run $ uhd_cal_tx_dc_offset but got the
>> > following error:
>> >
>> > Creating the usrp device with: ,ignore_cal_file=1,ignore-cal-file=1...
>> > [INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
>> > UHD_4.3.0.0-14-g1e718d9b
>> > [INFO] [USRP2] Opening a USRP2/N-Series device...
>> > [INFO] [USRP2] Current recv frame size: 1472 bytes
>> > [INFO] [USRP2] Current send frame size: 1472 bytes
>> > Running calibration for WBXv3 TX+GDB
>> > Daughterboard serial: EDR29PFXW
>> > Calibration frequency range: 68.75 MHz -> 2200 MHz
>> >
>> SSUSUS[WARNING]
>>
>> > TX error detected! Repeating current iteration
>> >
>> SSU[WARNING]
>>
>> > TX error detected! Repeating current iteration
>> >
>> SS[WARNING]
>>
>> > TX error detected! Repeating current iteration
>> > SSS[WARNING] TX error detected! Repeating current
>> > iteration
>> > [WARNING] TX error detected! Repeating current iteration
>> > [WARNING] TX error detected! Repeating current iteration
>> > [WARNING] TX error detected! Repeating current iteration
>> 

usrp n200 problem: error when running uhd_cal_tx_dc_offset

2022-12-28 Thread Ali G. Dezfuli
Hi all,
I have gnuradio on this system:
ubuntu 22.04
uhd 4.3.0.0-14-g1e718d9b
gnuradio v3.11.0.0git-316-gc11667ef

I have a USRP N200 from 2011 but have not worked with it for the last
couple of years.
After a long while, I just run $ uhd_cal_tx_dc_offset but got the following
error:

Creating the usrp device with: ,ignore_cal_file=1,ignore-cal-file=1...
[INFO] [UHD] linux; GNU C++ version 11.3.0; Boost_107400;
UHD_4.3.0.0-14-g1e718d9b
[INFO] [USRP2] Opening a USRP2/N-Series device...
[INFO] [USRP2] Current recv frame size: 1472 bytes
[INFO] [USRP2] Current send frame size: 1472 bytes
Running calibration for WBXv3 TX+GDB
Daughterboard serial: EDR29PFXW
Calibration frequency range: 68.75 MHz -> 2200 MHz
SSUSUS[WARNING]
TX error detected! Repeating current iteration
SSU[WARNING]
TX error detected! Repeating current iteration
SS[WARNING]
TX error detected! Repeating current iteration
SSS[WARNING] TX error detected! Repeating current iteration
[WARNING] TX error detected! Repeating current iteration
[WARNING] TX error detected! Repeating current iteration
[WARNING] TX error detected! Repeating current iteration
[WARNING] TX error detected! Repeating current iteration
[WARNING] TX error detected! Repeating current iteration
[WARNING] TX error detected! Repeating current iteration
terminate called without an active exception
Aborted (core dumped)

I would be grateful if somebody helps me with this error.
regards
AGD


time division duplexing (TDD) with USRP B2xx

2022-01-15 Thread Ali G. Dezfuli
I am going to implement a real-time TDD link (in the order of
one-millisecond burst durations) using two laptops and two USRP B2xx (in
either single antenna or dual-antenna ways). I searched a lot on the net
especially GNU Radio's mailing list but could not find any clear techniques
or tutorials to deal with it. So, I wonder if someone helps me manage that
in a step-by-step way. Thank you!


Re: vector index selector

2021-11-15 Thread Ali G. Dezfuli
Thanks, Marcus, but I actually want to have something like a general
demultiplexer to separate the preamble from the payload.
I couldn't find a SIMPLE demuxer ("Header/Payload Demux" is very
complicated.)
What you kindly said is something like a general downsampler/decimator
which of course has its own use.
For example, with a correlator, I put a tag at the frame start, and with
"Tagged Stream Aligned" and "Stream to Vector" I will have a
ready-to-be-demuxed frame to get to the payload.

On Mon, Nov 15, 2021 at 2:14 PM Marcus Müller  wrote:

> Hi!
> Not in itself, but you can do
>
> ---vector-->
>   [Vector to Stream, num items = n]
>--->
> [Keep M in N, M=1, N=n, initial offset=index]
>  >
>
> Best regards,
> Marcus
>
> PS: A PR to improve "keep M in N" to directly deal with vectors, or to add
> a block "Vector
> Extract" that does what you describe (take vectors in, and have a
> parameter with indices
> to extract) to master, would certainly be welcome.
>
> On 14.11.21 07:55, Ali G. Dezfuli wrote:
> > Hi all,
> > is there a block in GRC to get a vector and output a vector with
> selected indexes (as a
> > parameter)?
> > thanks,
> > AGD
>


vector index selector

2021-11-13 Thread Ali G. Dezfuli
Hi all,
is there a block in GRC to get a vector and output a vector with selected
indexes (as a parameter)?
thanks,
AGD


spectrum analyzer problem

2021-06-30 Thread Ali G. Dezfuli
Hi all,

I wonder if this is a bug or what:
I just make a QPSK constellation on the unit circle with quite random data
and
look at the spectrum by "QT GUI Frequency Sink" block in GRC.
With these parameters:
FFT size = 1000
Window type = None OR Rectangular
I should see a flat line as the spectrum with -30 dB (= -30 dBW) but
surprisingly it
shows -33 dB !!!
I use GNU Radio Companion 3.7.13.4 and ubuntu 16.04.
Would be grateful if you could help me in this matter.

regards,
Ali


qt gui frequency sink problem with PSD level

2021-06-26 Thread Ali G. Dezfuli
Hi all,

I wonder if this is a bug or what:
I just make a QPSK constellation on the unit circle with a quite random
data and
look at the spectrum by "QT GUI Frequency Sink" block in GRC.
With these parameters:
FFT size = 1000
Window type = None OR Rectangular
I should see a flat line as the spectrum with -30 dB (= -30 dBW) but
surprisingly it
shows -33 dB !!!
I use GNU Radio Companion 3.7.13.4 and ubuntu 16.04.
Would be grateful if you could help me in this matter.

regards,
Ali


raspberry pi + dvb-t2

2021-03-18 Thread Ali G. Dezfuli
Hi all,

Is there any experience in transmitting DVB-T2 with gnuradio and raspberry
pi (any version)?
I just wonder if it can work real-time with about 9 MHz sampling frequency
of 8 MHz DVB-T2.
Thank you!

BR,
AGD


qt gui frequency sink in frequency hopping

2020-12-21 Thread Ali G. Dezfuli
Hi all,
I work on a Frequency Hopping (FH) Tx and Rx in the same grc flowchart in
3.7.13.4 in Ubuntu 16.04.
At the end of the Tx chain, I put a "Qt GUI Frequency Sink", but it just
shows part of subchannels in the spectrum!!!
I changed its parameters especially "Update Period" but no change.
The very interesting point is that when I remove the Rx chain (lessen the
complexity), it shows the spectrum of FH correctly!
I really wonder why.

Thanks,
AGD


is there anybody who can search at the GR manual?

2020-10-03 Thread Ali G. Dezfuli
Hi all,
I still have a problem with the GR manual (
https://www.gnuradio.org/doc/doxygen/)
In firefox I receive this error:

Firefox Can’t Open This Page


*To protect your security, www.gnuradio.org  will
not *

*allow Firefox to display the page if another site has *

*embedded it. To see this page, you need to open it in a *


*new window.Learn more…*

is there anybody who is ok with searching at the manual?
Thanks
AGD


GR manual (doxygen) has some errors!

2020-09-23 Thread Ali G. Dezfuli
Hi all,
I'd like to report errors in the GR manual site:
*https://www.gnuradio.org/doc/doxygen/
*
I can't search by typing in the top right box!
I've tested Firefox, Chrome, Chromium, but the same result!
For example in Firefox I got this error:

Firefox Can’t Open This Page
To protect your security, www.gnuradio.org will not allow
Firefox to display the page if another site has embedded
it. To see this page, you need to open it in a new window.

regards,
AGD


comparing scalar vs vector items

2020-09-23 Thread Ali G. Dezfuli
Hi all,
I'd like to compare two GR blocks in terms of performance (especially
throughput)
1- using scalar items together with "set_output_multiple

(int multiple)" at the constructor, and
2- using vector items.
regards,
AGD


comparing scalar items, vector items and tagged streams

2020-09-22 Thread Ali G. Dezfuli
Hi all,
I have two chronic questions and would be grateful if anybody helps me:
1- between passing items as vectors and using streams with tags which
one is more performant?
2- do vector items lose performance comparing scalar items?
Thank you,
AGD


USRP b200mini initial behavior

2020-08-18 Thread Ali G. Dezfuli
Hi all,
In USRP B200mini, when I start off sending, for example, a tone from TX/RX
port and receive it from RX2 port, there is an increasing amplitude signal
at the receiver that could take a pretty long time to converge (e.g. at 4
MHz sample rate, it is as long as 50 to 100 milliseconds.)
I wonder if it is because of the transmitter's initialization or the
receiver's AGC.

I also test a binary OOK-like signal (on-off keying) to check if it happens
during the transmission and found out that it just happens at the start of
transmission.
I would be appreciated if anyone helps me with this.

regards,
Ali G. Dezfuli


transient behavior of "QT GUI Time Sink"

2020-06-05 Thread Ali G. Dezfuli
Hi all,

I would like to know how the "QT GUI Time Sink" block acts when its input
items are limited.
For instance, when I connect a "Vector Source" with range(10) as the
vector, it shows nothing except when I change its "Number of Points" to 8
or less !!!

I really appreciate it!
Regards,
Ali G. Dezfuli


is buffer flushing possible in GNU Radio?

2020-06-05 Thread Ali G. Dezfuli
Hi list,

Is there a way to make a block (in fact general block) flush its internal
buffer at the end (when there are no input items)?

(For example, a simple FIR filter has number of taps more output items than
its input items)

Thanks in advance!
Ali G. Dezfuli


OOT block swig problem (maybe qmake vs cmake)

2020-05-25 Thread Ali G. Dezfuli
Hi all,

The story is this:

I always add all the necessary gr_modtool created files to a new project in
qt-creator named "pre_gr" and develop a new OOT block there. Then, by
building from source, I add the block to GRC, test it, and use it. This way
I have developed some nontrivial practical modems.

BUT

I decided to be more organized by using more object-oriented features.
The problem is: the code in qt-creator compiled OK but when I add the block
to GRC, I get this error:

Generating: '/home/ali/grdrills/top_block.py'
Executing: /usr/bin/python2 -u /home/ali/grdrills/top_block.py
Traceback (most recent call last):
  File "/home/ali/grdrills/top_block.py", line 168, in 
main()
  File "/home/ali/grdrills/top_block.py", line 156, in main
tb = top_block_cls()
  File "/home/ali/grdrills/top_block.py", line 69, in __init__
self.tmp_tmp_cmo_acq0_0 = tmp.tmp_cmo_acq0()
AttributeError: 'module' object has no attribute 'tmp_cmo_acq0'

which is usually related to SWIG.
The point is that the class "_impl.h" has two member variables:
Prm d_p;
ACQ d_acq;
which are Prm class to hold all the parameters, and ACQ class for
acquisition, and in "_impl.cpp" the constructor is like this:
tmp_cmo_acq0_impl::tmp_cmo_acq0_impl()
  : gr::block("tmp_cmo_acq0",
  gr::io_signature::make(1, 1, sizeof(gr_complex)),
  gr::io_signature::make(1, 1, sizeof(gr_complex))),
d_p(awgn, 5),
d_acq(d_p)
{
}
and the problem arises just as I add "d_acq" to the block.
I really wonder why and it drives me crazy these days.
I did a lot of searches but nothing!
I am certain that there are lots of experts on the list and that's my only
hope!

The code is as follows:

tmp_cmo_acq0_impl.h:









*#ifndef INCLUDED_TMP_TMP_CMO_ACQ0_IMPL_H#define
INCLUDED_TMP_TMP_CMO_ACQ0_IMPL_H#include #include
"acq.h"#include "nco.h"#include "prm.h"#include #include
#include #include *






















*namespace gr {  namespace tmp {class tmp_cmo_acq0_impl : public
tmp_cmo_acq0{ private:Prm d_p;ACQ
  d_acq; public:  tmp_cmo_acq0_impl();
~tmp_cmo_acq0_impl();  // Where all the action really happens  void
forecast (int noutput_items, gr_vector_int _items_required);
int general_work(int noutput_items,   gr_vector_int _items,
 gr_vector_const_void_star _items,
 gr_vector_void_star _items);};  } // namespace tmp} //
namespace gr#endif /* INCLUDED_TMP_TMP_CMO_ACQ0_IMPL_H */*



tmp_cmo_acq0_impl.cpp:






























































*#ifdef HAVE_CONFIG_H#include "config.h"#endif#include
#include "tmp_cmo_acq0_impl.h"#include
"acq.h"#include "nco.h"#include "prm.h"#include #include
#include #include namespace gr {
namespace tmp {tmp_cmo_acq0::sptrtmp_cmo_acq0::make(){
return gnuradio::get_initial_sptr(new tmp_cmo_acq0_impl());}
tmp_cmo_acq0_impl::tmp_cmo_acq0_impl()  : gr::block("tmp_cmo_acq0",
  gr::io_signature::make(1, 1, sizeof(gr_complex)),
  gr::io_signature::make(1, 1, sizeof(gr_complex))),
d_p(awgn, 5),d_acq(d_p){}
tmp_cmo_acq0_impl::~tmp_cmo_acq0_impl(){}void
tmp_cmo_acq0_impl::forecast (int noutput_items, gr_vector_int
_items_required){  ninput_items_required[0] =
noutput_items;}inttmp_cmo_acq0_impl::general_work (int
noutput_items,   gr_vector_int _items,
 gr_vector_const_void_star _items,
 gr_vector_void_star _items){const gr_complex *in =
(const gr_complex *) input_items[0];gr_complex *out = (gr_complex
*) output_items[0];// Do <+signal processing+>int i = 0;
for (i = 0; i < noutput_items; ++i) {out[i] = in[i]; //
almost nothing !!!}consume_each (noutput_items);
return noutput_items;}  } /* namespace tmp */} /* namespace gr */*


prm.h:




















*#ifndef PRM_H#define PRM_H#include using namespace
std;using namespace itpp;enum CH_MODE {awgn, rayleigh};class Prm{public:
CH_MODE ch_mode;int n_sb;public:Prm(CH_MODE u_ch_mode, int
u_n_sb);};#endif // PRM_H*



prm.cpp:










*#include "prm.h"#include using namespace std;using
namespace itpp;Prm::Prm(CH_MODE u_ch_mode, int u_n_sb):
ch_mode(u_ch_mode),  n_sb(u_n_sb){}*



acq.h


















*#ifndef ACQ_H#define ACQ_H#include "nco.h"#include "prm.h"#include
#include #include
#include class ACQ {public:const Prm
public:ACQ(const Prm _p);}; // Acq#endif //
ACQ_H*




acq.cpp










*#include "acq.h"#include "nco.h"#include "prm.h"#include
#include ACQ::ACQ(const Prm _p)
  : p(u_p){}*




The versions:
*** cmake: 3.15.1
*** gnuradio: 3.7.13.4
*** ubuntu: 16.04
and IT++ is quite OK in my other OOT blocks. (and of course here)

I really appreciate it,
regards
Ali G. Dezfuli


bug report

2020-04-07 Thread Ali G. Dezfuli
Hi all,
I think the block "Chunks to Symbols" needs to have "Endianness" as a
parameter because it defaults "LSB first" which is not generally true.
For example, in Simulink, we have a block named "bit to integer" to handle
the endianness before rectangular QAM which defaults to MSB first that
causes Simulink and GRC to not have the same output.
regards,
Ali


multiple messages in GRC as different commands

2020-02-17 Thread Ali G. Dezfuli
Hi all,
I wonder if it is possible to command a "Signal Source" block in GRC to
change its frequency to several values with the messages.
For example, I want to change its frequency to 100 different values during
run-time using available blocks (if possible).
thanks in advance


[Discuss-gnuradio] problem with tensorflow in gr-inspector

2019-09-19 Thread Ali G. Dezfuli
Dear friends,
I have a problem installing gr-inspector.
I am using ubuntu 18.04
having gnuradio v3.7.9.3 installed (removing all the updates and installed
just this)
pip version is :
$ pip --version
"pip 19.2.3 from /usr/local/lib/python2.7/dist-packages/pip (python 2.7)"

>>> tf.__version__
'1.14.0'
>>>

*the error report in grc when running for example "amc_cnn.grc" is this:*



*Loading: "/home/masoud/opt/gr-inspector/examples/amc_cnn.grc">>> Done*
























*Showing: "/home/masoud/opt/gr-inspector/examples/amc_cnn.grc"Generating:
'/home/masoud/opt/gr-inspector/examples/top_block.py'Executing:
/usr/bin/python2 -u
/home/masoud/opt/gr-inspector/examples/top_block.pyWARNING:tensorflow:From
/usr/local/lib/python2.7/dist-packages/inspector/tfmodel_vcf.py:80:
load_session_bundle_from_path (from
tensorflow.contrib.session_bundle.session_bundle) is deprecated and will be
removed after 2017-06-30.Instructions for updating:No longer supported.
Switch to SavedModel immediately.Traceback (most recent call last):  File
"/home/masoud/opt/gr-inspector/examples/top_block.py", line 138, in
main()  File
"/home/masoud/opt/gr-inspector/examples/top_block.py", line 126, in main
tb = top_block_cls()  File
"/home/masoud/opt/gr-inspector/examples/top_block.py", line 73, in
__init__self.inspector_tfmodel_vcf_0 =
inspector.tfmodel_vcf("complex64",128,"/tmp/cnn/0001",(),0)  File
"/usr/local/lib/python2.7/dist-packages/inspector/tfmodel_vcf.py", line 64,
in __init__sess, inp, out,classes = self.load_graph(graphfile)  File
"/usr/local/lib/python2.7/dist-packages/inspector/tfmodel_vcf.py", line 80,
in load_graphoutput_graph_path)  File
"/usr/local/lib/python2.7/dist-packages/tensorflow/python/util/deprecation.py",
line 324, in new_funcreturn func(*args, **kwargs)  File
"/usr/local/lib/python2.7/dist-packages/tensorflow/contrib/session_bundle/session_bundle.py",
line 87, in load_session_bundle_from_path
meta_graph_filename)RuntimeError: Expected meta graph file missing
/tmp/cnn/0001/export.meta*

would be grateful if you could possibly help me with this.
regards
Ali
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


[Discuss-gnuradio] multiple gnuradios in parallel

2019-09-18 Thread Ali G. Dezfuli
Dear friends,
I'd like to have at least two gnuradios in parallel in ubuntu and I insist
on installing them "from source" as well.
I would be appreciated if you could possibly help me with this.
regards
Ali
___
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio