SatNOGS Wiki - User contributions [en]

Satellite Operator Guide

2023-01-10T10:07:02Z

Pe2bz: /* 3.1 Launch Operations / Satellite Identification */ added to share photos of the new satellite

{{warning|This guide is intended for Satellite Operators. For SatNOGS Operations moderators please see [[SatNOGS Operations Manual]]}}
==Introduction==
You are building a satellite? Congratulations! The information below will be helpful for the Communications and Operations part of your mission. Plan early and invest time in COMMS and Ground Segment. As a community, SatNOGS is here to help you in the process!

Although the information is tailored for missions that will be using Amateur Radio bands of the spectrum, some information is still relevant for other parts of the band too.

==Process==
===0. Early Stage===
It's strongly advised to get in touch with the AMSAT of you country at the beginning of your project. It enables that the radio amateur requirements are taken in account at the early stage on your project. It avoids false expectations and miscommunications along the way. In order to use an Amateur Radio band, your mission needs to be Amateur Radio related. Broadly speaking this includes and Amateur Radio service (like a transponder) or Amateur Radio experiment (new modulations, propagation experiments etc).
===1. Frequency Coordination===
First you need to determine whether you'll require an amateur frequency, a non-amateur frequency, or both.

Historically educational but non-Amateur Radio satellite operators (e.g. university research projects) were often improperly permitted to use amateur spectrum on a not-commercial basis. As this practice has led to serious congestion of the Amateur Radio Service, the IARU will no longer coordinate amateur frequency allocation for this purpose. Therefore:

*If your satellite will be purely for Amateur Radio use (i.e. all of its major functions will be available for use by all licensed Amateur Radio operators), then you're usually able to request Amateur Radio Space Service frequency coordination from IARU. You remain free to perform limited control functions on Amateur Radio spectrum. If there is an AMSAT organization in your country, start there. If not, approach your national Amateur Radio body. They will usually help you to get a radio amateur frequency coordination from IARU your allocation. It will take time: usually between six months and a year. If you don't ask for an IARU coordination, the launcher of your satellite may not allow you to launch the satellite.
*If your satellite will have substantial non-Radio Amateur use (sensor data, imagery, space-qualification of components, ...) then you will usually require a (non-amateur) Space Service license and frequency allocation. Approach your local radio communication regulator directly to start this process, which will have to finalized through ITU.
*If your satellite will do both, then you'll require licenses and frequency allocation/coordination for both services. A recent example is [https://www.amsat.org/falconsat-3/ FalconSAT-3].

====1.1 Publicly and openly document your Communications====
If you are planning to use a Radio Amateur band you are required to publicly and openly document ever singe detail of your transmission. That includes your modulation, encoding, framing and various functions. Your uplink and TC operations might not be publicly documented if you choose so.

Regardless of your band usage, we would strongly advise you to openly document your Communications since Open Data is a core pillar of sustainable and efficient Space operations. See the [https://manifesto.libre.space/ Libre Space Manifesto] for more info.

===2. Integration with SatNOGS===
====2.1 Reasons to Join====
You have recently discovered SatNOGS and you are involved in a mission. Here are the top 10 reasons why your mission should join SatNOGS:

#SatNOGS can help streamline your mission operations (Dashboards, Monitoring, Telemetry acquisition)
#SatNOGS is open source technology. Every piece of technology we develop is licensed as an open source project (software and hardware), which you can learn from, re-mix, re-use and contribute!
#SatNOGS is a global community of satellite enthusiasts, radio amateurs and satellite operators! [[Get In Touch|Join our community and be part of it.]]
#SatNOGS is best suited for educational, research, non-profit, experimental and amateur missions. Libre Space Foundation[https://libre.space/] that runs SatNOGS is committed on supporting those missions.
#SatNOGS is the largest global ground station network. 400 stations online with a spread around the world. No other network can beat that :)
#SatNOGS is non-profit. Our sustainability is funded through development funds, custom development if needed and a viral model of adding ground stations to the network. Using the network is as simple as adding another station to it!
#SatNOGS is full of educational opportunities. Great learning material, documentation and a vibrant community can help you get up to speed for mission COMMS and Operations.
#SatNOGS modular technology stack allows you to integrate with your existing space and ground station hardware easily. We support many COTS hardware or can easily add support for more.
#SatNOGS provides also a vertical approach if you choose to opt-in for tested integration through Libre Space Foundation space qualified hardware COMMS options (SatNOGS COMMS[https://gitlab.com/librespacefoundation/satnogs-comms/] and PQ9ISH COMMS[https://gitlab.com/librespacefoundation/pq9ish/pq9ish-comms-vu-hw/]).
#SatNOGS is a project abiding to the Libre Space Manifesto [https://manifesto.libre.space/].

 

====2.2 Add a new Mission====
Do you want to integrate your mission with SatNOGS? Cool! Here is a short guide how to do this. Please also reach out to us via [[Get In Touch|chat or community]] so that we can support you. Checklist:

#SatNOGS DB
#*Suggest to add your satellite to satnogs-db by creating an issue in [https://gitlab.com/librespacefoundation/satnogs-ops/issues satnogs-ops] providing the following information:
#**Name
#**NORAD catalog number (if already assigned)
#**Amateur Radio call sign (if Amateur service)
#**Description
#**Project Website
#**Image of the satellite
#*Once the new satellite was added to satnogs-db by one of the satnogs-ops team members, find your satellite in [https://db.satnogs.org/ db.satnogs.org] and add a transmitter suggestion for each transmitter of your satellite
#SatNOGS GNURadio
#*Choose one of the existing flowgraphs in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs] or provide a new one
#SatNOGS Client
#*If you added a new flowgraph under the previous point, make sure to add support for it in [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client]
#*Wait for the next release of [https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible/ satnogs-client-ansible], then let the station owners know that your satellite is supported now and ask them to update their stations.
#SatNOGS Decoders
#*Add a decoder written in [https://kaitai.io/ Kaitai] to [https://gitlab.com/librespacefoundation/satnogs/satnogs-decoders satnogs-decoders]
#SatNOGS Dashboard
#*To obtain editor permissions to build a SatNOGS Dashboard for your mission you need an account in the LSF SSO system. To get this, go to https://dashboard.satnogs.org/login and press "Sign-in with Auth0". On the following page select sign-up to register.
#*Sign-in to https://dashboard.satnogs.org once (you will have read permissions for now).
#*Please create an issue in https://gitlab.com/librespacefoundation/satnogs-ops/-/issues with the following details:
#**The Satellite
#**Your Satellite Team
#**Your email address used for the login
#*Once you got editor permissions, you can create a new dashboard in [https://dashboard.satnogs.org dashboard.satnogs.org] for your satellite.
{{warning|In order to have scheduling rights in SatNOGS Network, you need to own an operational Online Station in the Network. Consider building one, or donating one in the Network.}}
==3. Operations==

===3.1 Launch Operations / Satellite Identification===
A few weeks / days before the launch, a contributor will create the '''Launch Thread''' for every planned launch in the [https://community.libre.space/c/satellites-observations/launches/26 Launches] category of our community. This thread is supposed to collect information about the satellites that will be launched and about when and where this will happen.

After the launch all communication about identifications / deployments / determined orbits / operational status are shared in this launch thread. Keeping the information for all satellites of a single launch in one thread is tremendously helpful for coordinating between missions! For example identifying two of three satellites in a train will allow the identification by exclusion principle of the third one. Note however that for launches with many satellites this thread is quite busy. So if you e.g. intent to describe your mission in detail you can open a separate thread for your mission in the [https://community.libre.space/c/satellites-observations/16 Satellites & Observations] category.

You are highly welcomed to participate in this thread, for example by stating the affiliation with your mission, sharing the expected orbit, frequencies and modulations or sharing the identification and photos / images of your satellite. If you share identifications please always shortly explain how you got to a certain TLE (e.g. from on-board GPS, via doppler measurements or using the exclusion principle).

'''<big>We wish you a successful mission. Claim Space, the Libre Way!</big>'''
 
==See Also==

*[[DB|SatNOGS DB]]
*[[Network|SatNOGS Network]]
*[[Forum|Community Forum]]
*[[Get In Touch]]

[[Category:Satellite]]
[[Category:RF Modes]]

Raspberry Pi

2021-11-15T13:48:47Z

Pe2bz: /* Download */ After over an year I still need to add the ssh file manually to the boot partition.

[[File:B3342fcc865731d69e0c9d7a8b1abb887185bc13 1 531x500.jpg|alt=Libre Space Foundation Raspberry Pi Case|thumb|Libre Space Foundation Raspberry Pi Case, [https://www.thingiverse.com/thing:3233687 on thingiverse]]]

==Introduction==

The Raspberry Pi (version 3 and 4) is the reference platform for SatNOGS (see our [[SatNOGS Client Ansible|Ansible guide]] to install SatNOGS on other Linux machines). You can try using various distributions for this (eg. Debian/Armbian, Arch, Fedora), but the one we suggest is our custom image based on latest Raspbian.

{{Message|This page assumes you have an account and a ground station registered on either network.satnogs.org or network-dev.satnogs.org. Make note of your station ID and API Key.}}

==Download==
'''<big>Raspbian SatNOGS Image:</big> <big>[https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/jobs/artifacts/2020122700/download?job=release artifacts.zip]</big> ''' (Release: 2020122700)

Download the latest Raspbian SatNOGS Image from above (or via the "Download" icon on the right side of the [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/tags latest tag page on GitLab]). This image has the SatNOGS setup script installed, the SSH server enabled ( 2021-11-15 edit by PE2BZ there is no ssh file in the boot partition, this has to be added else the Pi will not be accessible by SSH) and all required packages preinstalled. You will get an <code>artifacts.zip</code> file with the following content:

*A Zipped image file
*An Image info file
*A SHA256 checksum file

===Data integrity verification===

You should verify the data integrity of the artifacts by comparing the SHA256 checksums. On Linux, run <code>sha256sum -c sha256sums</code> in the directory where the artifacts are downloaded and unzipped.

Example:
<pre>
$ sha256sum -c sha256sums
2020-12-27-Raspbian-SatNOGS-master-lite.info: OK
image_2020-12-27-Raspbian-SatNOGS-master-lite.zip: OK
</pre>

==Flashing==
[https://www.raspberrypi.org/documentation/installation/installing-images/README.md Follow the usual Raspbian flashing instructions], and boot your Raspberry Pi.

==Getting console access==
You can log in the Raspberry Pi by connecting it to a keyboard and monitor or through network via an SSH connection.

===Keyboard and monitor===
Once your Raspberry Pi is booted, log in with username "'''pi'''" password "'''raspberry'''".

===Ethernet===
If you are using wired Ethernet you should get connectivity right away. You just need to find the IP address of Raspberry Pi (e.g. in your router management interface). Log in with SSH using username "'''pi'''" password "'''raspberry'''", for example:
$ ssh pi@192.168.1.2
If your network supports [[wikipedia:Zero-configuration_networking|<code>zeroconf</code>]], then you can use the hostname of your Pi:
$ ssh pi@raspberrypi.local

===Pre-boot wireless configuration===
If neither keyboard/monitor, nor a wired Ethernet are available, you can set up a WiFi connection before boot by mounting the boot partition of the flashed SD card and editing files directly. Note your OS may mount boot partition in a different location. [https://raspberrypi.stackexchange.com/questions/10251/prepare-sd-card-for-wifi-on-headless-pi#comment98121_57023 Windows users have line ending problems]. Suggested actions:

$ $EDITOR /media/Raspbian_SatNOGS-boot/wpa_supplicant.conf

contents: (note key_mgmt options include NONE, WPA-PSK, WPA-EAP)

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=US

network={
ssid="NETWORK_NAME"
psk="password"
key_mgmt=WPA-PSK
}

==Configuration==

===Raspberry Pi Setup===
Once your Raspberry Pi is booted, log in with username "'''pi'''" password "'''raspberry'''" and run:
<pre>
$ sudo raspi-config
</pre>

You will want to be sure to do the following:

*Set a strong, unique password
*Change localization settings:
**by default the rpi locale is configured for EN-GB, change as appropriate (ie: to EN_US.UTF-8)
**set timezone (we recommend UTC so your logs match the times in Network; UTC is under the 'none of the above' submenu)
**set keyboard layout, again this is defaulting to a UK layout
**set wifi country
**expand filesystem (under the Advanced menu)
*Configure network or WiFi (see [https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md this doc for network configuration instructions])
*Finish and reboot

===SatNOGS Setup===
SSH to the Raspberry Pi with user "'''pi'''" and your new password.

Follow [[SatNOGS Client Setup]] instructions to configure the system.

[[Category:Build]]
[[Category:Software]]

Software Defined Radio

2021-05-22T12:49:21Z

Pe2bz: typo specifing changed to specifying in HackRF Settings Field

==Introduction==

Built upon [https://gnuradio.org/ GNU Radio] and [https://github.com/pothosware/SoapySDR/wiki SoapySDR] by using the [https://gitlab.com/librespacefoundation/gr-soapy gr-soapy] module SatNOGS supports a large variety of Software-Defined Radios (SDRs). The gr-soapy module was developed in the [https://sdrmaker.space/ SDR Makerspace] and is maintained by Libre Space Foundation to bring the vendor-neutral SDR support by SoapySDR to the flexible gnuradio ecosystem.

The most cost-effective solution is to use an RTL-SDR with a Raspberry Pi. More advanced SDRs are also used, but they require more processing power and thus might require a more powerful computing platform than the Raspberry Pi.

==Supported Devices==

SoapySDR supports SDR devices through runtime-loadable modules [https://github.com/pothosware/SoapySDR/wiki#plugin-architecture]. You can find all available modules in the [https://github.com/pothosware/SoapySDR/wiki#modules SoapySDR wiki] (see right column). Most SDR modules are installed by default when setting up a SatNOGS station.

The following SDRs are supported by SatNOGS. SatNOGS uses the RTL-SDR as the recommended beginner signal receiver and tuner.
The more advanced SDRs may require more processing power than a Raspberry Pi 3b or 4 can offer.

*[[Software Defined Radio#RTL-SDR Support|RTL-SDR]]
**[https://www.nooelec.com/store/sdr/sdr-receivers.html NooElec NESDR SMArt]
**[https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/ RTL-SDR Blog R820T2 RTL2832U]
**Full band UV HF RTL-SDR USB Tuner Receiver

*[[Software Defined Radio#USRP support|USRP devices]]
**[https://www.ettus.com/product/category/USRP-Bus-Series USRP B200]

*[[Software Defined Radio#Airspy support|Airspy]]
*[[Software Defined Radio#LimeSDR support|LimeSuite devices]]
**[https://limemicro.com/products/boards/limesdr-mini/ LimeSDR mini]
*[[Software Defined Radio#PlutoSDR support|PlutoSDR]]
**[https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/adalm-pluto.html#eb-overview ADALM-PLUTO] (untested)

{{Message|There are probably a lot more devices supported since the transition from gr-osmosdr to gr-soapy. Please update this list when you were able to successfully run a SatNOGS station with a new radio family or model. You can also link your station as an example to give others the ability to compare performance.}}

==Supported Devices with closed-source drivers==
Unfortunately some vendors require closed-source drivers in their SoapySDR modules and thus those modules or dependencies can't be redistributed by others. Thus they must be manually installed by the user. The following devices require closed-source drivers:

*[[Software Defined Radio#SDRPlay support|SDRPlay]]

==Unsupported Devices==
{{Warning|This section might be outdated due to the transition to gr-soapy. Please update when possible.}}
 

*[https://greatscottgadgets.com/hackrf/ HackRF One] (not compatible with the SatNOGS client on Raspberry Pi, ''Update: works fine now on a Pi4, only tested with the 8GB version of the Pi4. Will probably work with a 2/4GB version too. Not tested on a Pi3, might not be powerful enough to handle 8MS/s'')

==RTL-SDR Support==
The RTL-SDR is based on two chips -- the versatile [http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=35&Level=4&Conn=3&ProdID=257 RTL2832U chip] and the [https://rtl-sdr.com/wp-content/uploads/2013/04/R820T_datasheet-Non_R-20111130_unlocked.pdf R820T tuner]. The RTL-SDR is currently the cheapest, most common, and most performing solution available in terms of general sensitivity having a frequency range of 24 – 1766 MHz. A metal enclosure with SMA connector is preferred, along with a stable TCXO (low ppm). HF coverage is optional.

 

===Using RTL-SDR.com V3 Dongle's Bias-T Power Supply===
The RTL-SDR.com V3 dongle has a built in software activated Bias-T voltage supply intended to be used for applications such as powering inline LNAs (Low Noise Amplifiers). There are several ways to turn on the voltage, but through initial testing (as of this writing, 17 Aug 2019) it seems that the following procedure works best.

The below relates to Raspberry Pi installs only. No testing has been performed on other systems as of yet.

{{Warning|Turning on the Bias-T with no LNA installed and a "shorted" style antenna (such as loops, egg-beaters, etc.) can damage the RTL-SDR.com V3 dongle. Never activate the bias-t with no LNA installed between the antenna and the SDR dongle.}}

'''Requirements:'''

#Raspberry Pi running Raspbian Buster or newer (latest release of SatNogs image, [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/tags 2019091100], is demonstrated to work)
#[https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/ RTL-SDR.com V3 SDR dongle]
#[https://www.rtl-sdr.com/rtl-sdr-blog-v-3-dongles-user-guide/ RTL-SDR.com Bias-T Software Switch] for linux systems
#LNA capable of being powered via feedline coax (note that some LNAs need modifications to be powered by the coax, and some cannot be powered by the coax at all. Check the specifications for your LNA prior to attempting to turn on the Bias-T power supply)

 

====Instructions for installing RTL-SDR.com Bias-T Software Switch====

#Log into your SatNogs station either directly or via SSH
#If your station does not have cmake installed (SatNogs Image 2019091100 does not), install cmake with <code>sudo apt install cmake</code>
#Clone the source for the Bias-T software switch with <code>git clone <nowiki>https://github.com/rtlsdrblog/rtl_biast</nowiki></code>
#<code>cd rtl_biast</code>
#<code>mkdir build</code>
#<code>cd build</code>
#<code>cmake ..</code> (if you get a <code>LibUSB 1.0 required to compile rtl-sdr</code> error here, then do <code>sudo apt install libusb-1.0-0-dev</code> prior to attempting <code>cmake ..</code> again)
#<code>make</code>

The software switch should now be installed in the "src" directory. If you <code>cd src</code>, you can turn on the bias-t with the command <code>./rtl_biast -b 1</code> and turn it off with <code>./rtl_biast -b 0</code>. Note that the developers of this switch have warned against attempting to <code>sudo make install</code> so that this command can be executed from ouside the src directory. Testing has shown this warning to be accurate, so don't plan on running these commands from anywhere but the src directory, or else be sure to use the full path.

Switching the Bias-T on should yield between 4.5V and 5.0V across the center conductor and shield of the coax. The voltage should rise almost instantly. When switched off, the voltage seems to decrease gradually, over 5 to 10 seconds.

====Instructions to activate the bias-t for SatNogs Observations automatically:====

#Log into your SatNogs station either directly or via SSH
#<code>sudo satnogs-setup</code>
#select <code>Advanced</code>
#for <code>Radio</code> -><code>SATNOGS_RF_GAIN</code>, enter a low gain value supported by your RTL-SDR.com V3 dongle (entering <code>rtl_test</code> at the command line prior to starting <code>satnogs-setup</code> will give you all allowable values of RF gain) and select <code>Ok</code>
#for <code>Scripts</code> -><code>SATNOGS_PRE_OBSERVATION_SCRIPT,</code> enter <code>/home/pi/rtl_biast/build/src/rtl_biast -b 1</code> and select <code>Ok</code>
#for <code>Scripts</code> -><code>SATNOGS_POST_OBSERVATION_SCRIPT,</code> enter <code>/home/pi/rtl_biast/build/src/rtl_biast -b 0</code> and select <code>Ok</code>
#Select <code>Back</code>
#Select <code>Apply</code> (allow system to update and hit enter when prompted)
#Select <code>Back</code>

Your station is now set up to turn the Bias-T on for each scheduled observation (using the <code>SATNOGS_PRE_OBSERVATION_SCRIPT</code> string) and then turn it off at the conclusion of each observation (using the <code>SATNOGS_POST_OBSERVATION_SCRIPT</code>).

You should now schedule several observations to fine tune the <code>SATNOGS_RF_GAIN</code> value to get the best S/N performance for your station. Some have reported needing zero RF gain, others have reported low RF gain required (between 5 and 10 db), and others have said they see little benefit even with very high gain. Each station will be different.

====E4000 Tuner Gain Settings====
The RTLSDR Driver exposes six (!) IF gain settings (IF1 through IF6) for the E4000 tuner, along with a TUNER gain setting, which is actually a combined LNA and Mixer gain control. Details on the gain stages are available in page 28 of the E4000 data-sheet here: https://www.nooelec.com/files/e4000datasheet.pdf

When you follow the '[[Omnidirectional Station How To#Setting the gain|Setting the Gain]]' guide, all gain sliders (IF1 through IF6, and TUNER) should be presented in SoapySDR, allowing the user to adjust them to optimise for best performance. Once the correct values have been determined, you will need to define these specifically in satnogs-setup as follows:

*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>
*<code>SATNOGS_OTHER_SETTINGS</code>=<code>"IF1=6,IF2=3,IF2=2,IF3=0,IF4=0,IF5=2,IF6=3,TUNER=30"</code>

(Replacing the values in the line above with the ones you determined)

====R820T Gain Settings====
Unfortunately librtlsdr only exposes a single gain control for the R820T/T2 tuners, even though multiple gain adjustments are available. Use the standard SATNOGS_RF_GAIN option, with a gain between 0 and 42 (dB), as optimised for your station via the '[[Omnidirectional Station How To#Setting the gain|Setting the Gain]]' guide.

==Airspy support==
Vendor: [https://airspy.com/ Airspy]

required SoapySDR module: [https://github.com/pothosware/SoapyAirspy/wiki SoapyAirspy]

'''Note than none of the settings below should be entered with the " " around the value. This is only for better readability in the Wiki !'''

===Gain settings===
There are two possible gain modes:

*<code>SATNOGS_GAIN_MODE</code>=<code>"Overall"</code>: (default) Use a single gain value. Set the overall gain with <code>SATNOGS_RF_GAIN</code>,e.g. <code>SATNOGS_RF_GAIN</code>=<code>43</code>.
*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>: Use granular gain values. Set the different gain stages separately:
**without pre-amp: <code>SATNOGS_OTHER_SETTINGS</code>=<code>"LNA=12,MIX=8,VGA=11"</code>
**with pre-amp: <code>SATNOGS_OTHER_SETTINGS</code>=<code>"LNA=9,MIX=6,VGA=11"</code> (used in [https://network.satnogs.org/stations/49/ 49 - OZ7SAT])

For reference see also the Airspy driver library linearity gain settings in [https://github.com/airspy/airspyone_host/blob/bceca18f9e3a5f89cff78c4d949c71771d92dfd3/libairspy/src/airspy.c#L117-L122 libairspy/src/airspy.c#L117-L122].

===Sample rates===

*Airspy R2: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>2.5e6 or 10e6</code>
*Airspy Mini: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>3e6 or 6e6</code>
*Airspy HF+: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>768e3</code>

source: [https://twitter.com/DutchSpace/status/1241305651168661504]

If you want to activate the integrated bias tee, set <code>SATNOGS_DEV_ARGS</code>=<code>"biastee=true"</code>.
Bit packing ("Enable packing 4 12-bit samples into 3 16-bit words for 25% less USB trafic.") could be enabled with <code>SATNOGS_DEV_ARGS</code>=<code>"bitpacking=true"</code> (untested). Device arguments can be concatenated with comma as delimiter.

==SDRPlay support==
Vendor: [http://www.sdrplay.com/ SDRPlay]

required SoapySDR module: [https://github.com/pothosware/SoapySDRPlay SoapySDRPlay]

The following settings [https://network.satnogs.org/observations/?norad=&observer=&station=1354&results=d1&start=2020-02-20+00%3A00&end=2020-02-24+23%3A59 worked well] for an [https://www.sdrplay.com/rspduo/ SDRplay RSPduo] when using cross-yagis and good [https://www.ssb.de/en/amplifiers/preamplifier/vox/100w SSB low-noise amplifiers]:

*<code>SATNOGS_SOAPY_RX_DEVICE="driver=sdrplay"</code>
*<code>SATNOGS_RX_SAMP_RATE=2e6</code>
*<code>SATNOGS_RX_BANDWIDTH=600e3</code>
*<code>SATNOGS_RF_GAIN=34</code>
*<code>SATNOGS_ANTENNA="Tuner 1 50 ohm"</code>

Note that 14-bits ADC resolution is only available when using sample rates below 6.048 MSPS, above which the resolution is reduced gradually to 12, 10, and 8 bits.

==USRP support==
Vendor: [https://ettus.com Ettus Research]

required SoapySDR module: [https://github.com/pothosware/SoapyUHD/wiki SoapyUHD]

Recent USRPs that use the Analog Devices [https://www.analog.com/en/products/ad9361.html AD9361 RFIC] can use almost arbitrary sample rates and analog bandwidth settings. It can be an advantage to set the sample rate as high as the host computer can handle and the analog bandwidth to as narrow as meaningful. The following settings [https://network.satnogs.org/observations/?norad=&observer=&station=1353&results=d1&start=2020-02-20+00%3A00&end=2020-02-24+23%3A59 worked well] for a [https://www.ettus.com/all-products/ub210-kit/ USRP B210] when using cross-yagis and good [https://www.ssb.de/en/amplifiers/preamplifier/vox/100w SSB low-noise amplifiers]:

*<code>SATNOGS_SOAPY_RX_DEVICE="driver=uhd"</code>
*<code>SATNOGS_RX_SAMP_RATE=2e6</code>
*<code>SATNOGS_RX_BANDWIDTH=600e3</code>
*<code>SATNOGS_RF_GAIN=50</code>
*<code>SATNOGS_ANTENNA="RX2"</code>
**on the B200 your Antenna options are <code>TX/RX</code> and <code>RX2</code>, be sure you select the right option for your configuration!

==LimeSDR support==
Vendor: [https://limemicro.com Lime microsystems]

required SoapySDR module: [https://github.com/myriadrf/LimeSuite/tree/master/SoapyLMS7 SoapyLMS7 wrapper]

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=lime"</code>
*<code>SATNOGS_RX_SAMP_RATE</code>=<code>"2.048e6"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"LNAW"</code>
*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>20</code>
*<code>SATNOGS_OTHER_SETTINGS</code>=<code>"TIA=12,PGA=0,LNA=12"</code>

(untested, copied from station 1378)

Example stations:

*[https://network.satnogs.org/stations/1378/ 1378 - Wolbach library]

==PlutoSDR support==
Vendor: [https://www.analog.com Analog Devices]

required SoapySDR module: [https://github.com/pothosware/SoapyPlutoSDR/wiki SoapyPlutoSDR]

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=plutosdr"</code>
*<code>SATNOGS_RX_SAMP_RATE</code>=<code>"2e6"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"A_BALANCED"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>50</code>

==HackRF support==
Vendor: [https://greatscottgadgets.com/hackrf/ Great Scott Gadgets]

required SoapySDR module: [https://github.com/pothosware/SoapyHackRF SoapyHackRF]

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=hackrf"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"TX/RX"</code>
*<code>SATNOGS_RX_SAMP_RATE="8e6"</code>
**HackRF supports 8 to 20MS/s. Higher than 8MS/s has not been tested with SatNOGS on a RaspberryPi
**HackRF can run lower than 8MS/s, but it is not recommended as the ADC's filter is not designed for samplerates lower than 8MS/s

There are two possible gain modes:

"Overal", specifying just one global gain:

*<code>SATNOGS_GAIN_MODE</code>=<code>"Overall"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>"64"</code> (Supported gain range: 0-116dB)

"Settings Field", specifying the individual gains.

*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>
*<code>SATNOGS_OTHER_SETTINGS</code>=<code>"AMP=14,LNA=40,VGA=48"</code>
**AMP: supports 0 (amp disabled) and 14 (amp enabled)
**LNA: supports 0-40dBin 8dB steps
**VGA: supports 0-62dB in 2dB steps

To activate bias-T power on the antenna port:

*<code>SATNOGS_DEV_ARGS</code>=<code>bias_tx=true</code>

Example stations:

*[https://network.satnogs.org/stations/1868/ 1868 - HB9FXX S-Band]

==Remote==
Using the SoapySDRServer running on the same machine or over the network.

Required SoapySDRServer module: [https://github.com/pothosware/SoapyRemote/wiki SoapyRemote].
Optional SoapySDRUtil to probe for SDR and settings.
Make sure to match the antenna and gain setting from the actual device connected to the remote. Also possible to select remote drivers and other parameters; <code>driver=remote,remote:driver=rtlsdr</code>

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=remote"</code>
*<code>SATNOGS_RX_SAMP_RATE</code>=<code>"2e6"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"RX"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>20.7</code>

Not stable.

==References==

*[https://www.rtl-sdr.com/rtlsdr4everyone-review-of-5-rtl-sdr-dongles/ Review of 5 RTL-SDR Dongles]
*[https://hackaday.com/2017/09/05/19-rtl-sdr-dongles-reviewed/ 19 RTL-SDR Dongles Reviewed]
*[https://www.rtl-sdr.com/review-airspy-vs-sdrplay-rsp-vs-hackrf/ Review: Airspy VS. SDRplay RSP VS. HackRF]

[[Category:Build]]
[[Category:Hardware]]
[[Category:Software]]

__NOEDITSECTION__

Decode Telemetry and Packets

2020-11-26T15:55:22Z

Pe2bz:

== Introduction ==

There are several tools available to decode telemetry and packets. SatNOGS provides some built-in demodulators for various data formats. There are also additional tools that allow you the decoding of telemetry.

==Built-in Demodulators ==
[[File:SatNOGS-Observation-Data.png]]

Although the SatNOGS servers support many satellites with many modes, only the following modes are supported with built-in demodulators:

*[[APT]] (Automatic Picture Transmission)
*[[AFSK]] 1k2 (Audio Frequency Shift Keying)
*AX.25 (Amateur Radio adaptation of X.25 packet protocol)
*[[CW]] (Continuous Wave, Morse Code)
*[[DUV]] (Data Under Voice)
*[[GFSK]] 9k6 (Gaussian Frequency Shift Keying)
*[[FSK]] 9k6 (Frequency Shift Keying)
*[[LRPT]] (Low Resolution Picture Transmission)

==External Demodulator/Decoders==
If for some reason, the above built-in decoders are not doing enough, there are many [[Satellite specific telemetry decoders]]. Also, there are more generic decoders listed below.

==SoX - Sound eXchange==
SoX is the Swiss Army knife of sound processing programs. SoX is cross-platform and is available for many operating systems (Windows, Linux, MacOS X, etc.).

SoX supports demodulating the following modes:

*[[SoX_CW|CW]] (Continuous Wave, Morse Code)

===References===

*Chris Bagwell SoX − Sound eXchange http://sox.sourceforge.net/sox.html

==Fldigi in audio playback mode==
Fldigi can be used to decode a variety of data modes.

*[[Fldigi_CW|CW]] (Continuous Wave, Morse Code)

==FoxTelem for FOX1 series satellites==
[[FoxTelem]] currently supports decoding DUV telemetry the following satellites:

*AO-85 (Fox-1A)
*AO-91 (Radfxsat / Fox1-B)
*AO-92 (Fox1-D)
*Fox-1Cliff, and
*Fox-1E.

===References===

*AC2CZ FoxTelem - AMSAT Ground Station Software http://www.g0kla.com/foxtelem/

==multimon-ng==

Multimon-ng is a general purpose decoder. It can take wav or raw files and decode
a variety of modes among which: CW, AFSK, FSK...

===How to CW===
First you have to use sox to convert ogg files from SatNOGS download to 22050Hz raw file: 
sox file.ogg -r 22050 file.raw gain 6 
The gain is in dB and has a considerable impact on the decoding
in the special case of CW. You have to adjust gain to get proper decoding.

Then you must apply on the raw file the proper decoder: 
multimon-ng -a MORSE_CW -t raw file.raw

===How to AFSK===

First convert to raw sound file (sampling frequency 22050Hz) using sox 
sox -t ogg $file -r 22050 -t raw file.raw $soxopts 

Then use multimon-ng with AFSK1200 decoder 
multimon-ng -t raw -a AFSK1200 $file.raw

You can add more decoders if needed with additionnal "-a" options

===References===

*Elia Oenal Multimon-ng https://github.com/EliasOenal/multimon-ng

==Direwolf==

Direwolf is a software encoder/decoder for APRS (AX.25). It can take raw files and decode APRS.

===How to===
First you have to use sox to convert ogg files from SatNOGS download to 22050Hz raw file 
sox file.ogg -esigned-integer -b 16 -r 48000 file.raw 

then launch direwolf 
direwolf -B 1200 -b 16 -n 1 -r 48000 -q hd -t 0 -q h -q d -d p -d t -a 0 - < file.raw

Both commands can be combined with a pipe: 
<nowiki>sox -t ogg satnogs_386252_2018-12-29T02-54-45.ogg -esigned-integer -b 16 -r 48000 -t raw - | direwolf -B 1200 -b 16 -n 1 -r 48000 -q hd -t 0 -q h -q d -d p -d t -a 0 -</nowiki> 
([https://community.libre.space/t/observation-386252-x-cubesat-42707/3093/2 source])

==QSSTV==
[http://users.telenet.be/on4qz/qsstv/index.html QSSTV] is a modem software to send and receive SSTV
([https://en.wikipedia.org/wiki/Slow-scan_television Slow Scan Television]).

===Usage===

*Download the ogg file and convert it to wav with: <nowiki>sox satnogs_154162_2018-06-06T12-46-40.ogg output154162.wav rate 48000</nowiki>

*Open QSSTV and specify "Sound>Sound Input: from file"
*Press the play button and you will be asked to select the previously generated wav file. The decoding should start now.

===References===
Direwolf WB2OSZ https://github.com/wb2osz/direwolf

 

==WXtoImg==

WXtoImg is a program used to produce neat weather pictures from APT format receptions of NOAA satellites.

SatNOGS client produces automatically such weather map. However, if you want to add overlays or test some part of the processing, you can do it manually.

It uses a .wav file and produces weather picture with possible nice overlays (frontiers, colors...).

===Usage===

*Download for example the ogg file from observation #1193773 and convert it to wav with:

sox satnogs/satnogs_1193773_2019-11-12T07-13-50.ogg -r 11025 satnogs/satnogs_1193773_2019-11-12T07-13-50.wav

*Then invoke command line interface of WXtoIMG with:

wxtoimg -t n -e HVC -N satnogs/satnogs_1193773_2019-11-12T07-13-50.wav > satnogs/satnogs_1193773_2019-11-12T07-13-50.png
 

===References===
WXtoImg restored: https://wxtoimgrestored.xyz/
 

== See also ==
* [[Software]]
* [https://www.satblog.info/software/ Satellite specific telemetry decoders] ( Up to Date German)
* [https://www.dk3wn.info/wp/digital/ digital telemetry decoders] (German)
* [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs#adding-a-new-satellite-demodulator gr-satnogs Adding a New Satellite]

[[Category:Operate]]
[[Category:Software]]
[[Category:RF Modes]]
[[Category:Develop]]
[[Category:Telemetry]]

__NOEDITSECTION__

Software Defined Radio

2020-06-05T09:45:50Z

Pe2bz: Added a comment about not to use the quotation marks in settings fields, only the values

==Introduction==

Built upon [https://gnuradio.org/ GNU Radio] and [https://github.com/pothosware/SoapySDR/wiki SoapySDR] by using the [https://gitlab.com/librespacefoundation/gr-soapy gr-soapy] module SatNOGS supports a large variety of Software-Defined Radios (SDRs). The gr-soapy module was developed in the [https://sdrmaker.space/ SDR Makerspace] and is maintained by Libre Space Foundation to bring the vendor-neutral SDR support by SoapySDR to the flexible gnuradio ecosystem.

The most cost-effective solution is to use an RTL-SDR with a Raspberry Pi. More advanced SDRs are also used, but they require more processing power and thus might require a more powerful computing platform than the Raspberry Pi.

==Supported Devices==

SoapySDR supports SDR devices through runtime-loadable modules [https://github.com/pothosware/SoapySDR/wiki#plugin-architecture]. You can find all available modules in the [https://github.com/pothosware/SoapySDR/wiki#modules SoapySDR wiki] (see right column). Most SDR modules are installed by default when setting up a SatNOGS station.

The following SDRs are supported by SatNOGS. SatNOGS uses the RTL-SDR as the recommended beginner signal receiver and tuner.
The more advanced SDRs may require more processing power than a Raspberry Pi 3b or 4 can offer.

*[[Software Defined Radio#RTL-SDR Support|RTL-SDR]]
**[https://www.nooelec.com/store/sdr/sdr-receivers.html NooElec NESDR SMArt]
**[https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/ RTL-SDR Blog R820T2 RTL2832U]
**Full band UV HF RTL-SDR USB Tuner Receiver

*[[Software Defined Radio#USRP support|USRP devices]]
**[https://www.ettus.com/product/category/USRP-Bus-Series USRP B200]

*[[Software Defined Radio#Airspy support|Airspy]]
*[[Software Defined Radio#LimeSDR support|LimeSuite devices]]
**[https://limemicro.com/products/boards/limesdr-mini/ LimeSDR mini]
*[[Software Defined Radio#PlutoSDR support|PlutoSDR]]
**[https://www.analog.com/en/design-center/evaluation-hardware-and-software/evaluation-boards-kits/adalm-pluto.html#eb-overview ADALM-PLUTO] (untested)

{{Message|There are probably a lot more devices supported since the transition from gr-osmosdr to gr-soapy. Please update this list when you were able to successfully run a SatNOGS station with a new radio family or model. You can also link your station as an example to give others the ability to compare performance.}}

==Supported Devices with closed-source drivers==
Unfortunately some vendors require closed-source drivers in their SoapySDR modules and thus those modules or dependencies can't be redistributed by others. Thus they must be manually installed by the user. The following devices require closed-source drivers:

*[[Software Defined Radio#SDRPlay support|SDRPlay]]

==Unsupported Devices==
{{Warning|This section might be outdated due to the transition to gr-soapy. Please update when possible.}}
 

*[https://greatscottgadgets.com/hackrf/ HackRF One] (not compatible with the SatNOGS client on Raspberry Pi)
*USRP2 (not compatible with the SatNOGS client on Raspberry Pi)

==RTL-SDR Support==
The RTL-SDR is based on two chips -- the versatile [http://www.realtek.com.tw/products/productsView.aspx?Langid=1&PFid=35&Level=4&Conn=3&ProdID=257 RTL2832U chip] and the [https://rtl-sdr.com/wp-content/uploads/2013/04/R820T_datasheet-Non_R-20111130_unlocked.pdf R820T tuner]. The RTL-SDR is currently the cheapest, most common, and most performing solution available in terms of general sensitivity having a frequency range of 24 – 1766 MHz. A metal enclosure with SMA connector is preferred, along with a stable TCXO (low ppm). HF coverage is optional.

 

===Using RTL-SDR.com V3 Dongle's Bias-T Power Supply===
The RTL-SDR.com V3 dongle has a built in software activated Bias-T voltage supply intended to be used for applications such as powering inline LNAs (Low Noise Amplifiers). There are several ways to turn on the voltage, but through initial testing (as of this writing, 17 Aug 2019) it seems that the following procedure works best.

The below relates to Raspberry Pi installs only. No testing has been performed on other systems as of yet.

{{Warning|Turning on the Bias-T with no LNA installed and a "shorted" style antenna (such as loops, egg-beaters, etc.) can damage the RTL-SDR.com V3 dongle. Never activate the bias-t with no LNA installed between the antenna and the SDR dongle.}}

'''Requirements:'''

#Raspberry Pi running Raspbian Buster or newer (latest release of SatNogs image, [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/tags 2019091100], is demonstrated to work)
#[https://www.rtl-sdr.com/buy-rtl-sdr-dvb-t-dongles/ RTL-SDR.com V3 SDR dongle]
#[https://www.rtl-sdr.com/rtl-sdr-blog-v-3-dongles-user-guide/ RTL-SDR.com Bias-T Software Switch] for linux systems
#LNA capable of being powered via feedline coax (note that some LNAs need modifications to be powered by the coax, and some cannot be powered by the coax at all. Check the specifications for your LNA prior to attempting to turn on the Bias-T power supply)

 

====Instructions for installing RTL-SDR.com Bias-T Software Switch====

#Log into your SatNogs station either directly or via SSH
#If your station does not have cmake installed (SatNogs Image 2019091100 does not), install cmake with <code>sudo apt install cmake</code>
#Clone the source for the Bias-T software switch with <code>git clone <nowiki>https://github.com/rtlsdrblog/rtl_biast</nowiki></code>
#<code>cd rtl_biast</code>
#<code>mkdir build</code>
#<code>cd build</code>
#<code>cmake ..</code> (if you get a <code>LibUSB 1.0 required to compile rtl-sdr</code> error here, then do <code>sudo apt install libusb-1.0-0-dev</code> prior to attempting <code>cmake ..</code> again)
#<code>make</code>

The software switch should now be installed in the "src" directory. If you <code>cd src</code>, you can turn on the bias-t with the command <code>./rtl_biast -b 1</code> and turn it off with <code>./rtl_biast -b 0</code>. Note that the developers of this switch have warned against attempting to <code>sudo make install</code> so that this command can be executed from ouside the src directory. Testing has shown this warning to be accurate, so don't plan on running these commands from anywhere but the src directory, or else be sure to use the full path.

Switching the Bias-T on should yield between 4.5V and 5.0V across the center conductor and shield of the coax. The voltage should rise almost instantly. When switched off, the voltage seems to decrease gradually, over 5 to 10 seconds.

====Instructions to activate the bias-t for SatNogs Observations automatically:====

#Log into your SatNogs station either directly or via SSH
#<code>sudo satnogs-setup</code>
#select <code>Advanced</code>
#for <code>Radio</code> -><code>SATNOGS_RF_GAIN</code>, enter a low gain value supported by your RTL-SDR.com V3 dongle (entering <code>rtl_test</code> at the command line prior to starting <code>satnogs-setup</code> will give you all allowable values of RF gain) and select <code>Ok</code>
#for <code>Scripts</code> -><code>SATNOGS_PRE_OBSERVATION_SCRIPT,</code> enter <code>/home/pi/rtl_biast/build/src/rtl_biast -b 1</code> and select <code>Ok</code>
#for <code>Scripts</code> -><code>SATNOGS_POST_OBSERVATION_SCRIPT,</code> enter <code>/home/pi/rtl_biast/build/src/rtl_biast -b 0</code> and select <code>Ok</code>
#Select <code>Back</code>
#Select <code>Apply</code> (allow system to update and hit enter when prompted)
#Select <code>Back</code>

Your station is now set up to turn the Bias-T on for each scheduled observation (using the <code>SATNOGS_PRE_OBSERVATION_SCRIPT</code> string) and then turn it off at the conclusion of each observation (using the <code>SATNOGS_POST_OBSERVATION_SCRIPT</code>).

You should now schedule several observations to fine tune the <code>SATNOGS_RF_GAIN</code> value to get the best S/N performance for your station. Some have reported needing zero RF gain, others have reported low RF gain required (between 5 and 10 db), and others have said they see little benefit even with very high gain. Each station will be different.

==Airspy support==
Vendor: [https://airspy.com/ Airspy]

required SoapySDR module: [https://github.com/pothosware/SoapyAirspy/wiki SoapyAirspy]

'''Note than none of the settings below should be entered with the " " around the value. This is only for better readability in the Wiki !'''

===Gain settings===
There are two possible gain modes:

*<code>SATNOGS_GAIN_MODE</code>=<code>"Overall"</code>: (default) Use a single gain value. Set the overall gain with <code>SATNOGS_RF_GAIN</code>,e.g. <code>SATNOGS_RF_GAIN</code>=<code>43</code>.
*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>: Use granular gain values. Set the different gain stages separately:
**without pre-amp: <code>SATNOGS_OTHER_SETTINGS</code>=<code>"LNA=12,MIX=8,VGA=11"</code>
**with pre-amp: <code>SATNOGS_OTHER_SETTINGS</code>=<code>"LNA=9,MIX=6,VGA=11"</code> (used in [https://network.satnogs.org/stations/49/ 49 - OZ7SAT])

For reference see also the Airspy driver library linearity gain settings in [https://github.com/airspy/airspyone_host/blob/bceca18f9e3a5f89cff78c4d949c71771d92dfd3/libairspy/src/airspy.c#L117-L122 libairspy/src/airspy.c#L117-L122].

===Sample rates===

*Airspy R2: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>2.5e6 or 10e6</code>
*Airspy Mini: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>3e6 or 6e6</code>
*Airspy HF+: <code>SATNOGS_RX_SAMPLE_RATE</code>=<code>768e3</code>

source: [https://twitter.com/DutchSpace/status/1241305651168661504]

If you want to activate the integrated bias tee, set <code>SATNOGS_DEV_ARGS</code>=<code>"biastee=true"</code>.
Bit packing ("Enable packing 4 12-bit samples into 3 16-bit words for 25% less USB trafic.") could be enabled with <code>SATNOGS_DEV_ARGS</code>=<code>"bitpacking=true"</code> (untested). Device arguments can be concatenated with comma as delimiter.

==SDRPlay support==
Vendor: [http://www.sdrplay.com/ SDRPlay]

required SoapySDR module: [https://github.com/pothosware/SoapySDRPlay SoapySDRPlay]

The following settings [https://network.satnogs.org/observations/?norad=&observer=&station=1354&results=d1&start=2020-02-20+00%3A00&end=2020-02-24+23%3A59 worked well] for an [https://www.sdrplay.com/rspduo/ SDRplay RSPduo] when using cross-yagis and good [https://www.ssb.de/en/amplifiers/preamplifier/vox/100w SSB low-noise amplifiers]:

*<code>SATNOGS_SOAPY_RX_DEVICE="driver=sdrplay"</code>
*<code>SATNOGS_RX_SAMP_RATE=2e6</code>
*<code>SATNOGS_RX_BANDWIDTH=600e3</code>
*<code>SATNOGS_RF_GAIN=34</code>
*<code>SATNOGS_ANTENNA="Tuner 1 50 ohm"</code>

Note that 14-bits ADC resolution is only available when using sample rates below 6.048 MSPS, above which the resolution is reduced gradually to 12, 10, and 8 bits.

==USRP support==
Vendor: [https://ettus.com Ettus Research]

required SoapySDR module: [https://github.com/pothosware/SoapyUHD/wiki SoapyUHD]

Recent USRPs that use the Analog Devices [https://www.analog.com/en/products/ad9361.html AD9361 RFIC] can use almost arbitrary sample rates and analog bandwidth settings. It can be an advantage to set the sample rate as high as the host computer can handle and the analog bandwidth to as narrow as meaningful. The following settings [https://network.satnogs.org/observations/?norad=&observer=&station=1353&results=d1&start=2020-02-20+00%3A00&end=2020-02-24+23%3A59 worked well] for a [https://www.ettus.com/all-products/ub210-kit/ USRP B210] when using cross-yagis and good [https://www.ssb.de/en/amplifiers/preamplifier/vox/100w SSB low-noise amplifiers]:

*<code>SATNOGS_SOAPY_RX_DEVICE="uhd"</code>
*<code>SATNOGS_RX_SAMP_RATE=2e6</code>
*<code>SATNOGS_RX_BANDWIDTH=600e3</code>
*<code>SATNOGS_RF_GAIN=50</code>
*<code>SATNOGS_ANTENNA="RX2"</code>

==LimeSDR support==
Vendor: [https://limemicro.com Lime microsystems]

required SoapySDR module: [https://github.com/myriadrf/LimeSuite/tree/master/SoapyLMS7 SoapyLMS7 wrapper]

*<code>SATNOGS_SOAPY_RX_DEVICE</code>=<code>"driver=lime"</code>
*<code>SATNOGS_RX_SAMP_RATE</code>=<code>"2.048e6"</code>
*<code>SATNOGS_ANTENNA</code>=<code>"LNAW"</code>
*<code>SATNOGS_GAIN_MODE</code>=<code>"Settings Field"</code>
*<code>SATNOGS_RF_GAIN</code>=<code>20</code>
*<code>SATNOGS_OTHER_SETTINGS</code>=<code>"TIA=12,PGA=0,LNA=12"</code>

(untested, copied from station 1378)

Example stations:

*[https://network.satnogs.org/stations/1378/ 1378 - Wolbach library]

==PlutoSDR support==
Vendor: [https://www.analog.com Analog Devices]

required SoapySDR module: [https://github.com/pothosware/SoapyPlutoSDR/wiki SoapyPlutoSDR]

Untested.

==References==

*[https://www.rtl-sdr.com/rtlsdr4everyone-review-of-5-rtl-sdr-dongles/ Review of 5 RTL-SDR Dongles]
*[https://hackaday.com/2017/09/05/19-rtl-sdr-dongles-reviewed/ 19 RTL-SDR Dongles Reviewed]
*[https://www.rtl-sdr.com/review-airspy-vs-sdrplay-rsp-vs-hackrf/ Review: Airspy VS. SDRplay RSP VS. HackRF]

[[Category:Build]]
[[Category:Hardware]]
[[Category:Software]]

__NOEDITSECTION__

Software Defined Radio

2020-03-26T15:53:23Z

Pe2bz: removed 1.5 e6 from the Airspy Mini as supported samplerate.

Software Defined Radio

2020-03-22T16:14:18Z

Pe2bz: Sample rate for Airspy Mini no longer correct (3.072e6 not supporter bij device)