Open nevetts opened 1 year ago
If you build from main branch you probably won't see the timeouts.
This is a build from main branch
I don't think transmit and receive can easily work together. According to AT86RF215 (the RF chip) datasheet, it has two transceivers (corresponding to the two antenna ports on the boards), each of which can only work in either TX or RX at a given time.
One could in theory select TX in one transceiver and RX in another. But I'm not sure if the current software and firmware support that well. Also, even if it works, the two transceivers work at different frequency ranges. You do get some meaningful overlap in sub-1G with the full version, though.
For my application, I want to use the wide tuning port to transmit and then immediately (after a real time wait of a few microseconds) switch to receive.
I'm new to this, but.....the datasheet suggests that the RF chip should have this functionality (section 6.15.4 Transmit and Switch to Receive (TX2RX) ).
I have the same issue.
I have the same issue, too. running dump1090 with soapy support results in the same error.
Has anyone got the python example scripts working?
Installation etc was not smooth but I have it in a state where SoapySDRUtil --find sees the Cariboulite and the basic transmit / receive examples (capture.py, soapy_synth.py) seem to work.
For the other examples I mostly get a lot time out warnings... in particular I wanted to run soapy_iq_calib.py as an example with both tx and rx streams but the script fails and gives the below output. Not sure what else to try here...
partial output of soapy_iq_calib.py :
I also tried measure_delay.py from the SoapySDR examples. It also uses both tx and rx streams...and throws