discuss-gnuradio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: vector source python block


From: Kyeong Su Shin
Subject: Re: vector source python block
Date: Wed, 18 Dec 2019 09:43:56 +0000

Hello Sarandis (and to whom it may concern):

The GRC file in concern is apparantly written for GNU Radio 3.8, and is not backward compatible to GNU Radio 3.7. I suspect that you are using GNU Radio 3.7.

I can provide the compiled version of the flowgraph, but it will require GNU Radio 3.8 to run anyway. Instead, you can look at "epy_block_0_0.py ( https://github.com/duggabe/gr-morse-code-gen/blob/master/epy_block_0_0.py )", because I guess that is what Barry wants to show you (maybe I am wrong, though). You may need to make a few changes due to Python 2 / Python 3 compatibility issues, but with that, you should be able to embed that code to your flowgaph using a "Python Block" (for testing purposes, maybe).

Regards,
Kyeong Su Shin

보낸 사람: sarandis. Doulgeris <address@hidden> 대신 Discuss-gnuradio <discuss-gnuradio-bounces+ksshin=address@hidden>
보낸 날짜: 2019년 12월 18일 수요일 오후 5:53
받는 사람: Barry Duggan <address@hidden>
참조: Discuss Gnuradio <address@hidden>
제목: Re: vector source python block
 
Thanks Barru but i have a minor problem opening the grc file
Loading: "C:\Users\infrared\Documents\gnuradi_whatevers\MorseGen.grc"
Error: file:/C:/Users/infrared/Documents/gnuradi_whatevers/MorseGen.grc:1:1:FATAL:PARSER:ERR_DOCUMENT_EMPTY: Start tag expected, '<' not found
>>> Failure

Στις Τρί, 17 Δεκ 2019 στις 11:34 μ.μ., ο/η Barry Duggan <address@hidden> έγραψε:
Hi,

Without seeing your flowgraph, it is hard to tell what you plan to do
with the vectors. In gereral, the "speed" ultimately is determined by
input and/or output devices such as USB or a sound card. If you have
neither one, a throttle block will limit the throughput.

As an example of a custom vector source, see
https://github.com/duggabe/gr-morse-code-gen which generates vectors of
dots and dashes for Morse Code. If you start at the audio output (48khz)
and work backwards, you will see how the sample rates determine the
desired speed in words per minute.

If you haven't already done so, it would be helpful for you to work
through the
https://wiki.gnuradio.org/index.php/Tutorials#Guided_Tutorials

Let us know if you have more specific questions.

Best wishes,
--
Barry Duggan KV4FV

reply via email to

[Prev in Thread] Current Thread [Next in Thread]