Skip to content
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

Request choice of Device through Device_index #57

Closed
Galoosis opened this issue Feb 11, 2021 · 2 comments · Fixed by #58
Closed

Request choice of Device through Device_index #57

Galoosis opened this issue Feb 11, 2021 · 2 comments · Fixed by #58
Labels
enhancement New feature or request

Comments

@Galoosis
Copy link

I would like to see the option to choose a device to connect to. I would like to be able to install this on a RPI with other programs that use dongles and be able to choose which dongle this program uses. IE: Device_index = 1 instead of it using the default device of zero.

@jekhokie
Copy link
Owner

Note to self - this is likely just passing the ‘-d’ switch to the rtl_fm command (http://manpages.ubuntu.com/manpages/trusty/man1/rtl_fm.1.html). Update to include a device selector in config/settings.yml, default to 0, and provide instructions on how to get the device ID in case it’s unknown (rtl_eeprom or something similar that is already part of the rtl binaries installed).

@jekhokie jekhokie added the enhancement New feature or request label Feb 11, 2021
@jekhokie jekhokie linked a pull request Feb 11, 2021 that will close this issue
@jekhokie
Copy link
Owner

@Galoosis should be all set - do a git pull, add the new setting to your config/settings.yml file and specify your device ID that you want to use (the parameter is named "sdr_device_id" in that file - see the config/settings.yml.sample file for an example) and re-run ./install_and_upgrade.sh and you should be off to the races!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants