Re: ofdm adalm-pluto

[Kyeong Su Shin]

Hello Özkan,

Yes, it should be possible.

I haven't tried this by myself, so I don't know if it works, but maybe you can use a File Source with /dev/tty* as an input file. Alternatively, you can write a simple Python source block (see: https://wiki.gnuradio.org/index.php/Embedded_Python_Block , https://pyserial.readthedocs.io/en/latest/shortintro.html  ) . Simply set "in_sig=[np.complex64]" to "in_sig=[]" and it will behave as a source block.

Please note that this may introduce the rate mismatch issues, as the sampling rate of the serial port and the SDR won't (usually) agree. Maybe you can get away with your current codes, because you are already using packetized data, but you may want to look into this issue further if anything breaks.

Regards,

Kyeong Su Shin

---

보낸 사람: Özkan Sezer <ozkansezer@gmail.com> 대신 Discuss-gnuradio <discuss-gnuradio-bounces+ksshin=postech.ac.kr@gnu.org>
보낸 날짜: 2021년 12월 18일 토요일 오전 4:26
받는 사람: discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>
제목: Fwd: ofdm adalm-pluto

 

Thanks for your help Kyeong,

file transfer completed successfully, the periodic error still occurs but is not critical. I want to transmit live data (serial port data) instead of files. Is it possible with python block or another block?

---------- Forwarded message ---------
Gönderen: Kyeong Su Shin <ksshin@postech.ac.kr>
Date: 16 Ara 2021 Per, 20:17
Subject: Re: ofdm adalm-pluto
To: Özkan Sezer <ozkansezer@gmail.com>, discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>

Hello Özkan,

I haven't looked into the flowgraphs carefully yet, but you MUST not use a throttle block SDR source/sink is in the same path. GNU Radio gave you a warning about this:

>>> Warning: This flow graph contains a throttle block and another rate limiting block, e.g. a hardware source or sink. This is usually undesired. Consider removing the throttle block.

Throttle block is used to intentionally slow down the execution of the flowgraph, for simulation purposes. It causes data drops if used with real hardware.

Regards,

Kyeong Su Shin

---

보낸 사람: Özkan Sezer <ozkansezer@gmail.com> 대신 Discuss-gnuradio <discuss-gnuradio-bounces+ksshin=postech.ac.kr@gnu.org>
보낸 날짜: 2021년 12월 17일 금요일 오전 2:00
받는 사람: discuss-gnuradio@gnu.org <discuss-gnuradio@gnu.org>
제목: Fwd: ofdm adalm-pluto

 

yes, I want to send a file with transmitter adalm-pluto to receiver adalm-pluto. there is no problem with a direct connection (without adalm-pluto SDRs). And I take periodic faults with adalm-pluto SDRs like these

Block paths:
/usr/share/gnuradio/grc/blocks

Loading: "/home/sezer/Masaüstü/tx_ofdm.grc"
>>> Done

Generating: '/home/sezer/Masaüstü/tx_ofdm.py'
>>> Warning: This flow graph contains a throttle block and another rate limiting block, e.g. a hardware source or sink. This is usually undesired. Consider removing the throttle block.

Executing: /usr/bin/python3 -u /home/sezer/Masaüstü/tx_ofdm.py

ERROR: Unable to find host: İsim ya da servis bilinmiyor
ERROR: Unable to find host: İsim ya da servis bilinmiyor
Traceback (most recent call last):
  File "/home/sezer/Masaüstü/tx_ofdm.py", line 395, in <module>
    main()
  File "/home/sezer/Masaüstü/tx_ofdm.py", line 371, in main
    tb = top_block_cls(uri=options.uri)
  File "/home/sezer/Masaüstü/tx_ofdm.py", line 191, in __init__
    self.iio_pluto_source_0 = iio.pluto_source(uri, 2400000000, 2084000, 20000000, 32768, True, True, True, 'manual', 64, '', True)
  File "/usr/lib/python3/dist-packages/iio/iio_pluto_source_swig.py", line 92, in make
    return _iio_pluto_source_swig.pluto_source_make(*args, **kwargs)
RuntimeError: Unable to create context

>>> Done (return code 1)

Generating: '/home/sezer/Masaüstü/tx_ofdm.py'
>>> Warning: This flow graph contains a throttle block and another rate-limiting block, e.g. a hardware source or sink. This is usually undesired. Consider removing the throttle block.

Executing: /usr/bin/python3 -u /home/sezer/Masaüstü/tx_ofdm.py

WARNING: Unknown parameter '0' in <context>
WARNING: Unknown parameter '23' in <context>
WARNING: Unknown parameter 'v0.23' in <context>
gr::log :INFO: packet_headerparser_b0 - Detected an invalid packet at item 0
gr::log :INFO: header_payload_demux0 - Parser returned #f
gr::log :INFO: packet_headerparser_b0 - Detected an invalid packet at item 48
gr::log :INFO: header_payload_demux0 - Parser returned #f
gr::log :INFO: packet_headerparser_b0 - Detected an invalid packet at item 96
gr::log :INFO: header_payload_demux0 - Parser returned #f
gr::log :INFO: packet_headerparser_b0 - Detected an invalid packet at item 144
gr::log :INFO: header_payload_demux0 - Parser returned #f
gr::log :INFO: packet_headerparser_b0 - Detected an invalid packet at item 192
gr::log :INFO: header_payload_demux0 - Parser returned #f
gr::log :INFO: packet_headerparser_b0 - Detected an invalid packet at item 240
gr::log :INFO: header_payload_demux0 - Parser returned #f
gr::log :INFO: packet_headerparser_b0 - Detected an invalid packet at item 288

I think the periodic item is 48 and plus,

Are the same faults with other SDRs?

---------- Forwarded message ---------
Gönderen: Marcin Puchlik <m.puchlik@is-wireless.com>
Date: 16 Ara 2021 Per, 17:15
Subject: Re: ofdm adalm-pluto
To: Özkan Sezer <ozkansezer@gmail.com>
Cc: GNURadio Discussion List <discuss-gnuradio@gnu.org>

Hi,

Is this a periodic problem with the same packets?

Marcin

czw., 16 gru 2021 o 14:54 Özkan Sezer <ozkansezer@gmail.com> napisał(a):

Hi Marcus,
Thanks for your answer, yes it's unexpected because the transmitter and receiver are so
close. OFDM block same as gr-digital; is the extra spec for Adalm-pluto SDR?

--

Özkan SEZER

--

Özkan SEZER