-
I'm a total newbie at SDR and would just like to get started. I have my Cariboulite inserted in my Pi 4, and have GRC installed and operational on Bullseye (64bit). Antenna's are installed and the LEDs are lit. Any tips on how do I get my first radio running? I've never used any of the SDR tools before so I'm scrambling through GRC tutorials. Looks like I need some kind of source for the cariboulite but dont see anything in the GRC. I did read that this device is based on top of Soapy API and I do have a Soapy source (and an OSMOCOM source too) but don't see how to configure it. Does anyone have an example radio I could load to try this board out? Pointers would be very much appreciated. Thanks Mike. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
By no means I possess the in-depth knowledge on everything surrounding SDR, not even close, but I will give it a try to get you some directions based on what I’ve setup so far, which is not much. First and foremost, I don’t think cariboulite has gotten to the point of being a ready to use state yet. There will likely be more development on the software side. My setup is based on a freshly installed 64bit bullseye desktop version on a pi 4 (I wanted to make sure everything works properly before switching over to a headless setup). Once everything is ready, you can run the install script “./install.sh” in the cariboulite folder you pulled through git. It’s under the started and installation section on the code page. The installation script should install SoapySDRUtil and SoapySDRServer for you before compiling the drivers for cariboulite device. However, I found that SoapySDRServer never got installed properly for me so I had to compile it myself. At this point, you can use “cariboulite_test_app” and “cariboulite_util” in the cariboulite/build folder to manually interact with cariboulite.
I believe you can use the source code pulled by the script or just follow the instructions from pothosware/SoapyRemote git page as following:
Once SoapyRemote (SoapySDRServer) is compiled and installed properly, you can use SoapySDRServer to connect to it remotely using native SDR software like cubicsdr (I’ve yet to get sdrpp install properly on my pi, gqrx also has issue connecting to Soapy).
After the server is started, you will be able to connect using cubicsdr using ip:55132. I was able to get cubicsdr, openwebrx and gqrx to see both radios on caribou using 0.0.0.0 on local host. However, gqrx seemed to have issue staying connected with SoapyRemote and cubicsdr and openwebrx are both showing poor signal strength using antennas (a 70cm/2m hand held antenna, a multi band discone and a rubber duckie) that produce adequate to good signal strength on local radio stations (~100MHz) for the RTL SDR dongle on the same pi setup, so I’m guess either I’m still missing something or the driver still needs some work. I don’t know enough to tell for sure. This is how far I’ve gotten recently, and I hope this helps to get you started. I hope I has not made too much mistakes in write this as well. |
Beta Was this translation helpful? Give feedback.
-
Which antennas did you use for your Caribou Lite? I presume I can use something like 915MHz antenna from FPV drone for the sub 1GHz range - though I'm not completely sure. But for 6GHz I don't have any 6GHz antennas available, and I reckon 5.8GHz from a WiFi router may not work properly - because of the standing wave ratio (SWR) mismatch etc. Does anyone have any advices on this? |
Beta Was this translation helpful? Give feedback.
By no means I possess the in-depth knowledge on everything surrounding SDR, not even close, but I will give it a try to get you some directions based on what I’ve setup so far, which is not much.
First and foremost, I don’t think cariboulite has gotten to the point of being a ready to use state yet. There will likely be more development on the software side.
My setup is based on a freshly installed 64bit bullseye desktop version on a pi 4 (I wanted to make sure everything works properly before switching over to a headless setup).
Before you run the official install.sh, you can add “dtparam=i2c_vc=on” to /boot/config.txt to avoid error during environment check at the end of the install scr…