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?
Hi,
Is this a periodic problem with the same packets?
Marcin
Hi Marcus,Thanks for your answer, yes it's unexpected because the transmitter and receiver are soclose. OFDM block same as gr-digital; is the extra spec for Adalm-pluto SDR?
--
Özkan SEZER
tx_ofdm.grc