-
Notifications
You must be signed in to change notification settings - Fork 20
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
More detailed instructions? #12
Comments
I think that, perhaps, more detailed instructions about how to build/compile from source are available on the world wide web internet google device |
specifically what OS you are running + build + gcc. you need a bunch of extra "packages' to build an application from source, all of these are readily available. I charge a lot of money to answer these questions on the phone; too. |
On Sun, Apr 5, 2015 at 9:18 AM, Steen Eiler Jørgensen <
Tomasz Lemiech |
I think I know how to build/compile from source, but I don't know which file to compile! |
Okay, I think maybe I've located the issue. The readme file says
Done.
Done.
Done.
What's this? I have a folder called rtl-sdr, but typing make in this dir gives me an error. Or what is the "project folder"? |
On Sun, Apr 5, 2015 at 6:07 PM, Steen Eiler Jørgensen <
Have you cloned the RTLSDR_Airband repository ( git clone will create the directory named RTLSDR_Airband. You cd to it and Tomasz Lemiech |
Aha! Thank you! So I guess what's missing from the instructions is
before the "command into project directory" line. Now I have the project, but when I issue the command "make", I get this message:
Is this normal? |
On Sun, Apr 5, 2015 at 6:45 PM, Steen Eiler Jørgensen <
You may want to clone https://github.com/szpajder/RTLSDR-Airband instead, Tomasz Lemiech |
I cloned your repository instead, and now I get
It's a standard RaspberryPi model B. |
On Sun, Apr 5, 2015 at 7:59 PM, Steen Eiler Jørgensen <
Have you replaced the hello_fft subdirectory? Don't do this. hello_fft is already included in my repo and it should work Tomasz Lemiech |
Ah. Great - thanks! It seems to work now! Now I only need to figure out how to set up Icecast or Shoutcast... ;-) |
Hmm do i need to do the command sudo mknod char_dev c 100 0 Now i also have to figure out to set up icecast and rest of the program .. :-) //SA7ADV |
On Mon, Apr 13, 2015 at 3:29 PM, sa7adv notifications@github.com wrote:
char_dev is needed to run the program, not to build it. Tomasz Lemiech |
Can you please give us an example of the config.txt? I am stuck trying to figure out how to edit it. Thanks. |
An example is provided in the file named config.txt.example. Syntax is
described in README.md (section "Configuring").
If you still have a problem, then describe it and paste your config file
(preferably without passwords).
|
Here's what I have: I get this error: What's wrong? I have edited the template.txt file based on the contents it had. |
You can try this configuration. However this won't work as the dongle won't have enough bandwidth to receive the channels. The channels must be within 2.56MHz
|
Ok. It works now. Thanks, Tomasz! Another question: is there a way to make the program run in the background whenever I power my Raspberry PI 2 with Raspbian OS? |
You can add the command to |
Would the command look like ./rtl_airband_neon ? Sorry for the silly question but I am new to Linux stuff. |
Use the full path like If you are not sure what the full path is you can use |
Done. Rebooting now to see how it works. )))) One more question: what's the location/path of the mountpoint files? I need to configure the icecast server to stream them but I am not exactly sure how to get that done. Thanks again! You are very helpful! |
There is no file. As long as you configured the icecast server properly (i think you only need to change the default password), once you start the rtlsdr_airband program the mountpoints will be created automatically and start streaming. |
Ok. I will need to check my settings then on the icecast since I am not seeing any streams yet on it. |
You might as well do the following (assuming that your source directory is
2>&1 | logger -t rtl_airband -p local3.info ) & (press enter, press Ctrl+D)
Then edit the file /etc/rc.local (e.g "sudo nano /etc/rc.local") and add
Diagnostic messages will be logged to /var/log/messages . If you are feeling adventureous, you may try the unstable branch of my fork |
Strange: I have added the following line to the rc.local but to no avail: When I run top command I don't see the application running in the list of what's there now. |
It's probably looking for config.txt or char_dev device node in current
directory, which is "/" when the system boots. As it's not there, it fails.
You have to cd to the dir where char_dev and config.txt are located.
Better off, just use the short script I have pasted above.
|
OK. Will use the script you have pasted above. That sounds good. |
I have made the script and added it to the rc.local as per your instructions. Still can't see the rtl_airband_neon in the list of processes. Any idea on what to check? Thanks. |
Have you changed the path from /usr/src/RTLSDR-Airband to Have you tried to launch the script by hand from command prompt? Does it Tomasz Lemiech |
Tomasz, here's what I get when I try to launch the script manually: /bin/bash: ( cd /home/pi/RTLSDR-Airband && ./rtl_airband_neon --quiet 2>&1 | logger -t rtl_airband -p local3.info ) &: No such file or directory I have checked the path - it's correct. |
OK. I have found the problem - in your script the last character was & instead of ). The only strange thing now is why I don't see the rtl_airband_neon in the list of processes when running the 'top' command from shell? |
Tomasz, any idea what that is - no rtl_airband_neon in the list of current processes? |
If you copied the content of the script directly from the GitHub message, you might have ended up merging it into one line. |
Thanks. That solved the issue. Now I have the rtl_airband_neon in the list of running processes. However I still cannot get the audio into the icecast server. If you use icecast, can you give me a copy of your mpd.conf file? |
You should try the program and test the audio first before making it run on boot. If you run the program in terminal you should be able to see the channel levels (just like in README). That would be much easier to debug. At least you won't have to reboot every time after changing the config. |
Why mpd.conf? Most of us use Icecast software from http://icecast.org. Configuration goes into Most of the settings can be kept at their defaults. You should definitely change passwords in |
Tony, thanks. I have done that and could see levels. Everything is fine. Now I need to solve the remaining issues with the icecast server which refuses to run here: Latest errors: |
I've followed the instructions for the RaspberryPi, and everything worked fine until the "make" command, which obviously needs some parameter. Also, it says I should run the "program" with sudo, but it doesn't say which program. It also says I should edit the file config.txt, but there is no such file. Is there a manual somewhere?
The text was updated successfully, but these errors were encountered: