-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update installation instructions/plan for support? #85
Comments
Hi, I am not part of the Fairwaves team, just more of an interested party. I am working on updating the documentation as I am testing and making sure it all works on my end. At some point, I will submit a pull request to update the instructions. As for future support, I have reached out to them via multiple methods to no avail. Hopefully, someone responds in the near future. |
Hi both, @RFNOD : I am willing to help improve on documentation of current status by trying out and reviewing with my setup here. My plans are to use this SDR in a https://network.satnogs.org/ ground station. Currently I am trying to get my head around, which layers of libraries are best to use and how to integrate into other software without too much coding/changes on my behalves ... So every piece of documentation of the current state of all APIs would definitely help a lot! |
@RobertK66 : if you manage to have your XTRX work with the PCIe adapter, I'd glad to have details. I've installed mine on Linux Mint 19.3 for a while, managed to compile everything (I may provide info if needed), ran test_xtrx without error (but I don't know how to check its results), and I also run SoapySDR or osmocom based app (gnuradio) without error but I always get a flat signal. To my great disappointment, Fairwvare team has never answered me and had provided with no support. I even wonder sometimes if they are alive (their CTO has left a few months ago). |
@OhSoGood : OK, i will let you know when the adapter arrives. (this could take some time - there was a 3 week delivery schedule indicated and it has to pass customs here. so pls. be patient with me ...) |
@RFNOD : are you working with the USB or the PCIe version of the XTRX ? And is it a XTRX (CS, 1st gen) or a XTRX Pro ? |
@OhSoGood I am using the PCIe version of the XTRX Pro. @RobertK66 - here is some info on a fork of gr-osmosdr that works with the XTRX. Apparently, it has been merged with the Master branch. I haven't tested it yet. gr-osmosdr PR#20. |
Updated instructions have been merged. |
Even with latest update (from early December), my XTRX still receive a flat spectrum, with seldom jumps. I wonder if the board is worth trying again. @RobertK66 : Have you managed to use the XTRX with the PCIe adapter? @RFNOD: What's your status with your own board? Do you manage to receive and/or transmit? Merry Christmas to All! |
Hi, I have got the board now, but no time to try till now, sorry. Hope i get hands on the hardware some when in January. |
I had quite the rollercoaster getting everything up and running for this library/talking to the board. After having to clean install Ubuntu at least once in the process, I was able to get things running.
The installation instructions call for python 2 installation because "cheetah is not supported by python 3", which may have been correct at the time, but Cheetah3 exists now, and the build supports it.
Just because I struggled with documentation to support any issues I had with building, SoapySDR was the best way to get something to communicate with the board in an efficient manner.
Like other people have found, things with the sample rates get fuzzy after 70 MHz, I saw the issue on modifying the VIO and the other issue regarding changing the buffer size on the board. While it's nice to know there are potential ways to make this board work, the support to translate these changes into troubleshoot approaches seems to be lacking.
Is there any plan to continue supporting this project or any type of template plans to include more support for the low/high level APIs?
The text was updated successfully, but these errors were encountered: