SatNOGS Wiki - User contributions [en]

Software Defined Radio

2020-10-03T17:05:42Z

Cshields: minor updates to USRP soapy doc

==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.

====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 TX/RX and RX2, 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]

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__

MediaWiki:Sidebar

2020-09-11T00:26:54Z

Cshields: moving frequency coordination

* Build
** Build|[Station] Build a Ground Station
** Raspberry_Pi|[Station] Install a Raspberry Pi
** SatNOGS_Client_Setup|[Station] Configure/Update your Station
** Omnidirectional_Station_How_To|[Station] Omnidirectional Howto
** Radio|SDR Support
** Troubleshooting|Client Troubleshooting
* Operate
** Satellite_Operator_Guide|Add your Mission
** Operation|Managing Observations
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets
** Telemetry_Dashboards|Telemetry Dashboards
** :Category:RF Modes|RF Modes
* Contribute
** Get_Started|Get Started
** SatNOGS_DB|Crowd-Sourced Satellite Info
** Software_contribution|Software Contribution
** Server_Development_Environment|Server Development Environment
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module
** SatNOGS_Client_Development|SatNOGS Client Development
** Adding_a_new_data_decoder|Adding a new data decoder
** Academic_Papers|Academic Papers citing SatNOGS
** Provide_documentation|Provide Documentation
** SatNOGS_Operations_Manual|SatNOGS Operations Manual
* Learn
** Rotators|Rotators
** Antennas|Antennas
** Understanding_satnogs-flowgraphs| SatNOGS Flowgraphs
** SDR_Setup| SatNOGS SDR setup
** Spectrum_Management | Spectrum Management and Frequency Coordination
** Glossary|Glossary
* Contact
** Get_In_Touch|Get In Touch
** https://community.libre.space|Forums
** Press|Press
* Links
** https://db.satnogs.org|SatNOGS DB
** https://network.satnogs.org|SatNOGS Network
** https://dashboard.satnogs.org|SatNOGS Dashboard
** https://community.libre.space|SatNOGS Forums
** https://libre.space|Libre Space Foundation
** https://status.libre.space|System Status
* SEARCH

Spectrum Management

2020-09-11T00:26:05Z

Cshields: Cshields moved page Frequency Coordination to Spectrum Management: Thanks to Pierros for calling this out as a better title

Frequency coordination matters.

Frequency Coordination

2020-09-11T00:26:05Z

Cshields: Cshields moved page Frequency Coordination to Spectrum Management: Thanks to Pierros for calling this out as a better title

#REDIRECT [[Spectrum Management]]

MediaWiki:Sidebar

2020-09-11T00:12:41Z

Cshields: adding frequency coordination page to the menu

* Build
** Build|[Station] Build a Ground Station
** Raspberry_Pi|[Station] Install a Raspberry Pi
** SatNOGS_Client_Setup|[Station] Configure/Update your Station
** Omnidirectional_Station_How_To|[Station] Omnidirectional Howto
** Radio|SDR Support
** Troubleshooting|Client Troubleshooting
* Operate
** Satellite_Operator_Guide|Add your Mission
** Operation|Managing Observations
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets
** Telemetry_Dashboards|Telemetry Dashboards
** :Category:RF Modes|RF Modes
* Contribute
** Get_Started|Get Started
** SatNOGS_DB|Crowd-Sourced Satellite Info
** Software_contribution|Software Contribution
** Server_Development_Environment|Server Development Environment
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module
** SatNOGS_Client_Development|SatNOGS Client Development
** Adding_a_new_data_decoder|Adding a new data decoder
** Academic_Papers|Academic Papers citing SatNOGS
** Provide_documentation|Provide Documentation
** SatNOGS_Operations_Manual|SatNOGS Operations Manual
* Learn
** Rotators|Rotators
** Antennas|Antennas
** Understanding_satnogs-flowgraphs| SatNOGS Flowgraphs
** SDR_Setup| SatNOGS SDR setup
** Frequency_Coordination | Frequency Coordination
** Glossary|Glossary
* Contact
** Get_In_Touch|Get In Touch
** https://community.libre.space|Forums
** Press|Press
* Links
** https://db.satnogs.org|SatNOGS DB
** https://network.satnogs.org|SatNOGS Network
** https://dashboard.satnogs.org|SatNOGS Dashboard
** https://community.libre.space|SatNOGS Forums
** https://libre.space|Libre Space Foundation
** https://status.libre.space|System Status
* SEARCH

Spectrum Management

2020-09-10T23:59:23Z

Cshields: Created page with "Frequency coordination matters."

Frequency coordination matters.

User:Jebba

2020-01-26T02:06:29Z

Cshields: Cshields moved page User:Librespace1 to User:Jebba without leaving a redirect: Automatically moved page while renaming the user "Librespace1" to "Jebba"

I'm Jeff Moe, username jebba on the rest of libre.space / satnogs.org.

When the auth server created my wiki account, it gave me username Librespace1 automatically.

Ground stations:

* [https://network.satnogs.org/stations/1133/ cruftpi3]

* [https://network.satnogs.org/stations/1152/ cruftpi1]

Operation

2019-07-10T23:57:52Z

Cshields: change docs to reflect new deletion restriction

__TOC__

==Scheduling your first test observation==

'''Assumptions:'''

*You've set up your [[Raspberry Pi 3|SatNOGS client successfully]]
*You've created an account on the [[Network]], created a ground station, and it's showing up as "online"

If you've run into any problems with those steps, check out the [[Troubleshooting]] page or ask for help in [https://community.libre.space/c/satnogs the community forum], [https://riot.im/app/#/room/#satnogs:matrix.org the Matrix room], or on IRC at #satnogs on Freenode.

'''SatNOGS Network:'''

*Navigate your ground station page in the [https://network.satnogs.org Network Environment] (user name -> "My Profile" -> click on the name of your ground station).
*Select the "Upcoming passes" tab.
*Look for a pass with a "schedule" button that isn't greyed out, and click it. Ensure it is a good (high) pass of an operational satellite (check the color bar on the satellite)
*In the "New Observation" page that comes up, click the "Calculate" button, then click "Schedule".
*You should now see a page for that observation; in the "Waterfall" tab, you should see "Waiting for waterfall".

'''Ground Station'''

Now SSH to your ground station computer and run these steps:

*Follow the satnogs-client logs. Depending on your setup, this might be done with <code>journalctl -f -u satnogs-client.service</code>, or <code>tail -F /var/log/supervisor/satnogs.log</code>
*Before the observation is scheduled to start, you should see your client wake up once per minute to check for new jobs:

<pre>
Oct 02 00:16:02 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:02,477 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 02 00:16:02 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:02,479 - satnogsclient - DEBUG - Sending message: [{"origin": "network", "transmitter": "uXJ8NQNcH8b9osRc
Oct 02 00:16:02 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:02,488 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2
Oct 02 00:16:59 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:59,615 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next r
Oct 02 00:16:59 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:59,661 - apscheduler.executors.default - INFO - Running job "post_data (trigger: interval[0:02:00], next
Oct 02 00:16:59 raspberrypi satnogs-client[10124]: 2017-10-02 00:16:59,668 - apscheduler.executors.default - INFO - Job "post_data (trigger: interval[0:02:00], next run at:
Oct 02 00:17:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:17:00,906 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 02 00:17:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:17:00,908 - satnogsclient - DEBUG - Sending message: [{"origin": "network", "transmitter": "uXJ8NQNcH8b9osRc
Oct 02 00:17:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:17:00,912 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2
</pre>

*At the scheduled time for the observation, you should see the client kick off the observation:

<pre>
Oct 02 00:18:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:00,774 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 02 00:18:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:00,776 - satnogsclient - DEBUG - Sending message: [{"origin": "network", "transmitter": "uXJ8NQNcH8b9osRc
Oct 02 00:18:00 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:00,781 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,022 - apscheduler.executors.default - INFO - Running job "spawn_observer (trigger: date[2017-10-02 00:
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,082 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:4533
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,109 - satnogsclient - DEBUG - Sending message: p
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,110 - satnogsclient - DEBUG - Received message: 0.000000
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 0.000000
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,111 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:4532
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,115 - satnogsclient - DEBUG - Sending message: P 188.276951189 -0.0155264223734
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,119 - satnogsclient - DEBUG - Received message: RPRT -1
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,143 - satnogsclient - DEBUG - Sending message: F 436038107
Oct 02 00:18:22 raspberrypi satnogs-client[10124]: 2017-10-02 00:18:22,144 - satnogsclient - DEBUG - Received message: RPRT 0
</pre>

*After the observation is over, you should see the client submit the data to the SatNOGS network

In the SatNOGS Stage Environment, refresh the Observation page. You should now see a waterfall plot for your data.

If that all worked -- congratulations! You've just successfully completed your first SatNOGS observation.

If it didn't work, don't feel bad -- it can take a few attempts before you get it right. Have a look at the [[Troubleshooting]] page for tips, and don't forget to contact the community if you need help.

==Rating observations==

Once your observation results are posted back in the Network by your satnogs-client, you should go to Network to rate your observations. Any orange marked observations need vetting by users.
{{Message|The main purpose of validating observations is to know if the satellite/transmitter is alive, if it transmits in the listed frequency/ies, and if the TLEs we have are accurate.}}
{{Message|The functionality may change in the future, but for now even a faint sign on the waterfall is enough to make it valid.}}

[[File:Screenshot from 2017-10-15 11-59-59.png|frame|Orange need your rating!]]

Categories of observations:

*'''Good'''
**You should mark observations as "Good" when it is clear from the waterfall and/or audio recording that a satellite is present.
*'''Bad'''
**You should mark observations as "Bad" when by examining the waterfall and/or audio it is obvious that there was no satellite detected in this observation.
*'''Failed'''
**You should mark observations as "Failed" when the station failed entirely: the waterfall and/or audio is empty or not present, or there's too much noise.

Below is a collection of waterfalls with possible results of observations:
<gallery heights="400px" widths="200px">
File:Waterfall_20657_2017-10-15T10-07-51.png|'''Good''': Satellite is visible (bars-bursts of data in the middle). ''Note that the tangent-shaped lines are local noise''
File:Waterfall_20534_2017-10-15T07-21-24.png|'''Bad''': Typical empty waterfall with no visible signals.
File:Waterfall 20499 2017-10-15T07-17-32.png|'''Good''': Although drifting, satellite is clearly visible around the center.
File:Waterfall 20506 2017-10-15T06-47-36.png|'''Good''': Faint CW signal around center-left. ''Note you might have to expand image to notice it''
File:Waterfall_20571_2017-10-15T05-25-56.png|'''Good''': Clearly visible FM transmission. ''Note that the swinging lines are terrestrial noise''
File:Waterfall 20483 2017-10-15T05-12-49.png|'''Good''': Straight line in the center bottom is a satellite. ''Note transmission on left bottom is the same satellite on a different frequency''
File:Waterfall_145037_2018-05-26T15-18-18.png|'''Good''': Packets clearly seen in the middle of the observation. ''Note transmission starting middle bottom then moving to left and back to right *is* a space object (satellite). It is not the one we are tracking though (different TLE, thus this type if curve).''
</gallery>

[[File:Observation_with_discuss_button_highlighted.png|thumb|frame|Click the "Discuss" button to post in our web forum. (Note: this will only appear in the SatNOGS network.)]]

===Discuss===
If you're still unsure about an observation, click the "Discuss" button, near the top right of the observation's page; that will post a link to it on [https://community.libre.space/c/observations the Observations forum], where you can ask for feedback.

==Scheduling observations in standalone mode==

===Scheduling a NOAA observation in standalone mode===

Instructions for scheduling a NOAA observation, including decoding of the APT images, can be found [http://ixion.csd.uoc.gr/vardakis/index.php/satnogs-noaa-apt-decoder-walkthrough/ here].

==Network permissions matrix==

{| class="wikitable" style="text-align:center"
|-
! scope="col" |User
! scope="col" |View and discuss observation
! scope="col" |Vet observation
! scope="col" |Delete future observation
! scope="col" |Schedule observation
|-
|Non Authenticated
|All
|None
|None
|None
|-
|Authenticated
|All
|None
|None
|None
|-
|Station Owner (Future)
|All
|None
|None
|None
|-
|Station Owner (Offline)
|All
|Own(stations or observations)
|Own(stations or observations)
|None
|-
|Station Owner (Testing)
|All
|Own(stations or observations)
|Own(stations or observations)
|Own(stations)
|-
|Station Owner (Online)
|All
|All
|Own(stations or observations)
|All(online stations)
|-
|Moderator
|All
|All
|All
|All
|-
|Admin
|All
|All
|All
|All
|}
Examples:

*Authenticated user can view and discuss on all the observation. User can not vet or delete an observation. User can not schedule observation in any station.

*Station Owner with at least one online station can view and discuss on all observations. Online station owner can vet or delete observations on stations that owns. Online station owner can vet or delete observation that has scheduled. Online station owner can schedule observations on all online stations.

SatNOGS DB

2019-06-15T19:08:11Z

Cshields:

__NOTOC__

[https://db.satnogs.org/ SatNOGS DB] is an effort to create a holistic, unified, global transmitter database for all satellite transmitters. You can export the data or even connect your application using our API. It's part of the SatNOGS project.

==Data==
The DB is open to everyone. Anyone is able to submit suggestions or use the existing Transmitters. All data are public and freely under the Creative Commons Atribution-Share Alike license.

==Contribute==

===Adding Satellites===
If you are a moderator you can add new satellites on the DB. For that follow the instructions:

#Log in to db.satnogs.org
#Navigate to https://db.satnogs.org/admin (if you are seeing a login screen, you are either not logged in to db.satnogs.org, or don't have moderator permissions)
#Click on Base::Satellite [https://db.satnogs.org/admin/base/satellite/add/ Add button]
#Complete the information to the best of your knowledge. Norad ID and Name are mandatory. Add multiple names on the "Names" field.
#Click Save and you are done!
#You can now move on to the next steps: suggesting and approving transmitters for this satellite.

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Suggesting transmitters===
[[File:Db transmitter suggestion.png|center|thumb]]
We rely on crowd-sourced information to keep our transmitter details up to date. Anyone with a SatNOGS login can submit transmitter details. Moderators are notified and approve submissions frequently.
 

*Description: This is the name that will appear for this transmitter across DB, Network, and API users. Please use the following notations
**Band, for instance VHF, or for a transceiver, MODE U/V
**Baud (if applicable), in the format 9k6 for 9600
**Mode, for instance FSK
**Rough type description, ie TLM for "telemetry", or "FM Transponder" for repeater
**Examples
***UHF 9k6 FSK TLM
***MODE U/V FM Transceiver
***VHF CW TLM
*Status
**Active: alive and well
**Inactive: not functional or powered down
**Invalid: this is a legacy transmitter that should be hidden from UI
*Type
**Transmitter: one-way downlink (telemetry)
**Transceiver: repeats an uplinked signal intact
**Transponder: interacts with an uplinked signal or downlinks after signal modification
*Downlink: Published frequency, in Hz
*Downlink Drifted: Observed frequency, or what frequency should be used to properly tune (with doppler correction). In most cases this should be the same as the Downlink frequency. This field '''must be entered''' even if there is no drift.
*Mode: The modulation mode for this transmitter
*Baud rate: the baud rate, if applicable. If this is a CW beacon, use WPM
*Citation URL: a URL to link to in providing the details for your suggestion.

===Approving transmitters===
If you are a moderator you can approved suggestions for transmitters. For that follow the instructions:

#Log in to db.satnogs.org
#Navigate to https://db.satnogs.org/admin (if you are seeing a login screen, you are either not logged in to db.satnogs.org, or don't have moderator permissions)
#Click on Base::Suggestions
#Click on the suggestion you want to review and carefully check the data, especially the citation URL
#When you are ready to approve or delete the suggestion, go back to the [https://db.satnogs.org/admin/base/suggestion/ full list of suggestions]
#Select the suggestions you want to act upon and from the drop down above either approve them or reject them
#You are done!

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Coding===
Fluent in Python and/or JS? We need you to help with the satnogs-db web application! Take a look at our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db source code], or visit our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues? issues tracker] to start filling bugs, feature requests or code fixes for existing ones.

==API==

The SatNOGS DB API is available to anyone at https://db.satnogs.org/api/
More docs to come....

==Installation==

===[https://docs.satnogs.org/en/stable/satnogs-db/docs/installation-docker.html Docker Installation]===

===[https://docs.satnogs.org/en/stable/satnogs-db/docs/installation-virtualenv.html VirtualEnv Installation]===

SatNOGS DB

2019-06-15T18:58:21Z

Cshields: transmitter suggestion docs

__NOTOC__

[https://db.satnogs.org/ SatNOGS DB] is an effort to create a holistic, unified, global transmitter database for all satellite transmitters. You can export the data or even connect your application using our API. It's part of the SatNOGS project.

==Data==
The DB is open to everyone. Anyone is able to submit suggestions or use the existing Transmitters. All data are public and freely under the Creative Commons Atribution-Share Alike license.

==Contribute==

===Adding Satellites===
If you are a moderator you can add new satellites on the DB. For that follow the instructions:

#Log in to db.satnogs.org
#Navigate to https://db.satnogs.org/admin (if you are seeing a login screen, you are either not logged in to db.satnogs.org, or don't have moderator permissions)
#Click on Base::Satellite [https://db.satnogs.org/admin/base/satellite/add/ Add button]
#Complete the information to the best of your knowledge. Norad ID and Name are mandatory. Add multiple names on the "Names" field.
#Click Save and you are done!
#You can now move on to the next steps: suggesting and approving transmitters for this satellite.

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Suggesting transmitters===
[[File:Db transmitter suggestion.png|center|thumb]]
We rely on crowd-sourced information to keep our transmitter details up to date. Anyone with a SatNOGS login can submit transmitter details. Moderators are notified and approve submissions frequently.
 

* Description: This is the name that will appear for this transmitter across DB, Network, and API users. Please use the following notations
** Band, for instance VHF, or for a transceiver, MODE U/V
** Baud (if applicable), in the format 9k6 for 9600
** Mode, for instance FSK
** Rough type description, ie TLM for "telemetry", or "FM Transponder" for repeater
** Examples
*** UHF 9k6 FSK TLM
*** MODE U/V FM Transceiver
*** VHF CW TLM
* Status
** Active: alive and well
** Inactive: not functional or powered down
** Invalid: this is a legacy transmitter that should be hidden from UI
* Type
** Transmitter: one-way downlink (telemetry)
** Transceiver: repeats an uplinked the signal intact
** Transponder: interacts with an uplinked signal or downlinks after signal modification
* Downlink: Published frequency, in Hz
* Downlink Drifted: Observed frequency, or what frequency should be used to properly tune (with doppler correction). In most cases this should be the same as the Downlink frequency. This field '''must be entered''' even if there is no drift.
* Mode: The modulation mode for this transmitter
* Baud rate: the baud rate, if applicable. If this is a CW beacon, use WPM
* Citation URL: a URL to link to in providing the details for your suggestion.

===Approving transmitters===
If you are a moderator you can approved suggestions for transmitters. For that follow the instructions:

#Log in to db.satnogs.org
#Navigate to https://db.satnogs.org/admin (if you are seeing a login screen, you are either not logged in to db.satnogs.org, or don't have moderator permissions)
#Click on Base::Suggestions
#Click on the suggestion you want to review and carefully check the data, especially the citation URL
#When you are ready to approve or delete the suggestion, go back to the [https://db.satnogs.org/admin/base/suggestion/ full list of suggestions]
#Select the suggestions you want to act upon and from the drop down above either approve them or reject them
#You are done!

Note: this process may change in the future; see [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues?milestone_title=Improved+User+Experience the Gitlab issues list] for details.

===Coding===
Fluent in Python and/or JS? We need you to help with the satnogs-db web application! Take a look at our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db source code], or visit our [https://gitlab.com/librespacefoundation/satnogs/satnogs-db/issues? issues tracker] to start filling bugs, feature requests or code fixes for existing ones.

==API==

The SatNOGS DB API is available to anyone at https://db.satnogs.org/api/
More docs to come....

==Installation==

===[https://docs.satnogs.org/en/stable/satnogs-db/docs/installation-docker.html Docker Installation]===

===[https://docs.satnogs.org/en/stable/satnogs-db/docs/installation-virtualenv.html VirtualEnv Installation]===

File:Db transmitter suggestion.png

2019-06-15T18:46:38Z

Cshields: Cshields uploaded a new version of File:Db transmitter suggestion.png

db transmitter suggestion

File:Db transmitter suggestion.png

2019-06-15T18:42:22Z

Cshields:

db transmitter suggestion

MediaWiki:Sidebar

2019-02-17T00:03:52Z

Cshields: update link

* Build
** Raspberry_Pi_3|Install a Raspberry Pi
** Build|Build a Ground Station
** Rotators|Rotators
** Antennas|Antennas
** Omnidirectional_Station_How_To| Omnidirectional Station
** Radio|SDR Support
** Troubleshooting|Client Troubleshooting
** SatNOGS_Client_Ansible#Updating_SatNOGS_Client_software|Updating your SatNOGS Client
* Operate
** Operation|Managing Observations
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets
** Telemetry_Dashboards|Telemetry Dashboards
** :Category:RF Modes|RF Modes
** SatNOGS_Client_Ansible#Updating_SatNOGS_Client_software|Updating your SatNOGS Client
* Contribute
** Satnogs_DB|Crowd-Sourced Satellite Info
** Software_contribution|Software Contribution
** Development_Environment|Development Environment
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module
** SatNOGS_Client_Development|SatNOGS Client Development
** Academic_Papers|Academic Papers citing SatNOGS
** Provide_documentation|Provide Documentation
* Contact
** Get_In_Touch|Get In Touch
** https://community.libre.space|Forums
* Links
** https://db.satnogs.org|SatNOGS DB
** https://network.satnogs.org|SatNOGS Network
** https://dashboard.satnogs.org|SatNOGS Dashboard
** https://community.libre.space|SatNOGS Forums
** https://libre.space|Libre Space Foundation
** https://status.libre.space|System Status
* SEARCH

MediaWiki:Sidebar

2019-02-17T00:03:30Z

Cshields: update link

* Build
** Raspberry_Pi_3|Install a Raspberry Pi
** Build|Build a Ground Station
** Rotators|Rotators
** Antennas|Antennas
** Omnidirectional_Station_How_To| Omnidirectional Station
** Radio|SDR Support
** Troubleshooting|Client Troubleshooting
* Operate
** Operation|Managing Observations
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets
** Telemetry_Dashboards|Telemetry Dashboards
** :Category:RF Modes|RF Modes
** SatNOGS_Client_Ansible#Updating_SatNOGS_Client_software|Updating your SatNOGS Client
* Contribute
** Satnogs_DB|Crowd-Sourced Satellite Info
** Software_contribution|Software Contribution
** Development_Environment|Development Environment
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module
** SatNOGS_Client_Development|SatNOGS Client Development
** Academic_Papers|Academic Papers citing SatNOGS
** Provide_documentation|Provide Documentation
* Contact
** Get_In_Touch|Get In Touch
** https://community.libre.space|Forums
* Links
** https://db.satnogs.org|SatNOGS DB
** https://network.satnogs.org|SatNOGS Network
** https://dashboard.satnogs.org|SatNOGS Dashboard
** https://community.libre.space|SatNOGS Forums
** https://libre.space|Libre Space Foundation
** https://status.libre.space|System Status
* SEARCH

Antennas

2019-02-14T00:51:01Z

Cshields: new turnstile link

__NOTOC__
The type of antenna largely depends on the type of ground station. A no rotator ground station will benefit from a different type of antenna (omnidirectional) than a rotator based ground station (directional). The two different approaches are explored below. In addition to the choice of antenna the choice of location for the ground station will have an effect on the quality of observations.

==Non-Rotator Ground Station (Omnidirectional)==
This type of ground station will require an antenna that will give a broad coverage from its fixed position. It is therefore not just the antenna that needs to be considered but also the proximity of buildings, geography or metallic structures that might be in the path of a line of sight between the ground station and satellite.Typical ground stations have had success with simple wire antennas that can be commercially bought or made at home. Colinear or ‘white stick’ antennas are vertically polarised omnidirectional antennas. These have anecdotally been used for successful satellite work but should be avoided. The following are considered suitable choices:'''It is highly recommended that you use a mast-mounted Low-Noise Amplifier (LNA) with these antennas.'''
{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Antennas ===
!
! style="width: 49%" |
=== Homebrew Antennas ===
|-
|[[File:WiMo TA-1.gif|left|frameless|160x160px]]

==== WiMo TA-1 ====
VHF Turnstile

Estimated cost: 90€

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/141/ 141 - balcony-only-east-passes]

[https://network.satnogs.org/stations/33/ 33 - G7KSE]

[https://network.satnogs.org/stations/129/ 129 - Chabot Space And Science Center]

* [https://www.wimo.com/scanner-antennas_e.html#004 Product link]
* [http://oz9aec.net/antennas/air-tests-wimo-ta-1-turnstile-antenna OZ9AEC Review]
|
|[[File:VHF Turnstile.jpg|left|frameless|100x100px]]

==== Turnstile ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/13/ 13 - OZ9AEC-VHF1]

[https://network.satnogs.org/stations/7/ 7 - Stony]

[https://network.satnogs.org/stations/16/ 16 - VK5QI-70CM]

* SatNOGS Turnstile Antenna (TBD)
* [https://www.vk4adc.com/web/vhfuhf-projects/26-multiband-ants/156-turnstile-vhf-uhf-fds VK4ADC instructions for VHF and UHF Turnstile antennas]
* [https://www.aeronetworks.ca/2017/12/amateur-satcom-rx-antenna-for-2-meter.html Six-element tape-measure VHF Turnstile with modeled patterns (could be used as directional) by Herman Oosthuysen]
* [https://iz7boj.wordpress.com/2018/12/02/double-turnstile-construction-for-satellites-receiving-in-435mhz-band/ Double turnstile construction for 435MHz]
|-
|[[File:M2 Eggbeaters.png|left|frameless|100x100px]]

==== M2 Eggbeater ====
VHF / UHF Eggbeater Antennas

Estimated cost: $304 (VHF), $280 (UHF), $573 (combo)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/50/ 50 - N5CNB-UHF]

[https://network.satnogs.org/stations/77/ 77 - N5CNB-VHF]

* [https://www.m2inc.com/FGEB144RK2M Product link for VHF]
* [https://www.m2inc.com/FGEB432RK70CM Product link for UHF]
* [https://www.m2inc.com/FGSATPACK1 Product link for combination package]
|
|[[File:VHF EZ-Lindenblad.png|left|frameless|112x112px]]

==== Lindenblad ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/12/ 12 - W2BFJ]

[https://network.satnogs.org/stations/98/ 98 - Grove-UHF-01]

[https://network.satnogs.org/stations/442/ 442 - DL1UNX-FFB VHF]

* [https://www.amsat.org/wordpress/wp-content/uploads/2015/08/An-EZ-Lindenblad-Antenna-for-2-Meters2.pdf AA2TX EZ-Lindenblad design can be found at this AMSAT PDF]
* [https://www.qsl.net/py4zbz/DCA.pdf KD6JDJ instructions can be found at this QST PDF]
* [https://www.amsat.org/articles/w6shp/lindy.html W6SHP instructions for VHF and UHF Lindenblad]
|-
|[[File:Winkler Turnstile.jpg|left|frameless|100x100px]]

==== Winkler Turnstile ====
VHF/UHF Turnstile Antennas

Estimated cost: 40€ (VHF), 30€ (UHF)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/47/ 47 - DB0RV]

* [http://www.winklerantennenbau.de/sonst.htm Pricing page]
* [http://www.winklerantennenbau.de/kreuz137.htm Product link for VHF]
* [http://www.winklerantennenbau.de/kreuz446.htm Product link for UHF]
|
|[[File:UHF Paralindy.jpg|left|frameless|100x100px]]

==== UHF Parasitic Lindenblad ====
Estimated cost: $15 (with access to a 3D printer)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/300/ 300 - KB9JHU-Experimental]

[https://network.satnogs.org/stations/32/ 32 - SV1QZZ - UHF #2]

[https://network.satnogs.org/stations/187/ 187 - K3LRD UHF Lindenblad]

* [https://www.amsat.org/wordpress/wp-content/uploads/2014/01/70ParaLindy.pdf Instructions can be found at this AMSAT PDF by AA2TX]
|-
|
|
|[[File:Quadrifilar Antennas.png|left|frameless|100x100px]]

==== Quadrifilar Helix Antenna (QFH) ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/272/ 272 - K3LRD VHF QFH]

[https://network.satnogs.org/stations/255/ 255 - EA5BZ - Elche]

[https://network.satnogs.org/stations/183/ 183 - SPUTNIX-R2ANF-VHF/UHF-stationary]

* [http://www.g4ilo.com/qfh.html G4ILO QFH Instructions]
* [https://www.aeronetworks.ca/2017/12/parasitic-quadrifilar-helical-antenna.html VHF Model/patterns for QFH by Herman Oosthuysen]
* [http://jcoppens.com/ant/qfh/calc.en.php QFH Calculator by ON6JC/LW3HAZ]
* [https://community.libre.space/t/an-easy-3d-printed-quadrifilar-helix-antenna/1487 3D Printed UHF QFH Antenna by surligas]
|-
|
|
|[[File:Vhf moxon turnstile.png|left|frameless|100x100px]]

==== "Turnstiled" Moxon ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

TBD

* [https://sat.fg8oj.com/images/VHFUHFSatelite.pdf Instructions can be found at this QST article by W4RNL]
|}


==Rotator Ground Station==
A rotator based ground station is able to make use of directional antennas. These will have a directional gain, meaning that you will need to point them in the direction of the satellite but the signal you receive will be stronger and for longer. They will allow much lower to the horizon passes to be received and more successful observations. These are not complex antennas but the choice will depend on the type of satellite and there are variations on the main types: yagi, helical and quad.

{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Antennas ===
!
! style="width: 49%" |
=== Homebrew Antennas ===
|-
|[[File:M2 Leopack.png|left|frameless|100x100px]]

==== M2 Circularly Polarized Yagis ====
VHF/UHF Cross-element Yagi

Estimated cost: $296 (UHF), $296 (VHF), $638 (Combo kit)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/2/ 2 - KB9JHU]

[https://network.satnogs.org/stations/109/ 109 - EA6WQ - Tomas Orzaez]

[https://network.satnogs.org/stations/25/ 25 - N7IPY]

* [https://www.m2inc.com/FG2MCP8A Product link - VHF]
* [https://www.m2inc.com/FG436CP16 Product link - UHF]
* [https://www.m2inc.com/FGLEOPACK Product link - Combo kit]
|
|[[File:Cross element UHF yagi.jpg|left|frameless|133x133px]]

==== Yagi Antennas, Cross-element yagi antennas ====
VHF/UHF directional antenna

Estimated cost: TBD

A common type of antenna that is either horizontally or vertically polarised. Simple to construct and suitable for a large number of satellites.

Some SatNOGS stations using this antenna:

TBD

* TBD: Assembly instructions
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Yagi Source code for SatNOGS yagi antenna designs are here].
|-
|[[File:Wimo xquad vhf.jpg|left|frameless|100x100px]]

==== WiMo X Quad ====
VHF/UHF Cross-element Quad

Estimated cost: 149€ (VHF), 149€ (UHF)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

[https://network.satnogs.org/stations/49/ 49 - OZ7SAT]

[https://network.satnogs.org/stations/232/ 232 - VK5QI-AZ/EL]

* [https://www.wimo.com/xquad-antennas_e.html Product link]
|
|[[File:Satnogs helical v1.jpg|left|frameless|100x100px]]

==== Helical Antennas ====
UHF circularly polarized directional antenna

Estimated cost: TBD

A less common type that are circularly polarized. The antenna looks a bit like a corkscrew and can be either LHCP (Left hand circular polarisation) or RHCP (right hand circular polarisation).

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

* v4 [https://satnogs.dozuki.com/Guide/Helical+Antenna+v4/11 Assembly instructions]
* [https://ohai.satnogs.org/project/helical-antenna-v5/ v5 Assembly instructions]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical Source code for SatNOGS helical antenna designs are here.]
|-
|[[File:Arrow Portable Yagi.jpg|left|frameless|100x100px]]

==== Arrow Dual-band portable yagi ====
VHF/UHF portable yagi

Estimated cost: $83-$149

Some SatNOGS stations using this antenna:

TBD

* [http://www.arrowantennas.com/arrowii/146-437.html Product price/ordering link]
* [http://www.arrowantennas.com/sub/arrowiiyagi.html Product details link]
|
|
|-
|[[File:Elk Log Periodic.jpg|left|frameless|112x112px]]

==== Elk Log Periodic ====
VHF/UHF portable yagi

Estimated cost: $130-$163

Some SatNOGS stations using this antenna:

TBD

* [https://elkantennas.com/product/dual-band-2m440l5-log-periodic-antenna/ Product link]
|
|
|}


A radome design is available from SatNOGS. This will protect the ground station from the elements in all but extra ordinary conditions. The design can be found [https://gitlab.com/librespacefoundation/satnogs/satnogs-radome/blob/master/satnogs-radome-v1-bom.ods here] and construction guide [https://ohai.satnogs.org/project/satnogs-radome-v1/hardware/ here]. 
[[Category:Antennas]]
__NOEDITSECTION__
[[Category:Omnidirectional Antennas]]
[[Category:Directional Antennas]]

Dashboard

2019-02-09T23:40:52Z

Cshields:

__NOTOC__

=== https://dashboard.satnogs.org<nowiki/>===
We are using [https://www.influxdata.com/ InfluxDB] and [https://grafana.com/ Grafana] for our telemetry dashboards. [https://www.influxdata.com/ InfluxDB] is a time-series database designed to be efficient for time-series data like the telemetry we collect in SatNOGS.

I'm going to drop a few things to get the reader going on telemetry dashboard in SatNOGS, and expect that the reader also reference the [https://docs.grafana.org Grafana documentation] for more details on building dashboards.

This doc also assumes you have an account to edit dashboards. You can generate an account by clicking the Sign In link, and then [[Get In Touch|contacting us]] to escalate your permissions. You will be put into a group with access to the "Scratchpad - New Users" folder at first.

Today there is a top level folder hierarchy designed as such:

* Telemetry (where telemetry dashboards should be stored, publicly accessible)
* General (for stats about our data collection itself, meta-dashboards, publicly accessible)
* Scratchpad (a playground for making grafana dashboards and testing functionality, not publicly accessible)

=== Creating a dashboard ===
Clicking the + icon will allow you to create a new dashboard. When you do this a new panel is started for you. This panel can be resized at the lower-right corner, and moved around by dragging once more panels are added.

Now - before you get started please note that '''you have to save your changes!! They do not save automatically!'''

Click "Graph" to make this a graph panel. Click the graph title and then Edit to edit this specific graph.

[[File:Grafana panel edit.png|frameless|600x600px]]

A few things you will want to edit:

==== General ====

Give it a meaningful title, of course. Description is not required, but offers a popup of more details to the user if you want to add more details.

==== Metrics ====
Select the metric by clicking "select measurement". What you will see here are the names of all measurements available which are the NORAD ID of the satellite in the database. You can type part of the NORAD ID to filter.

[[File:Grafana select measurement.png|frameless|600x600px]]

In most cases you will want to leave the WHERE clause blank, but from here you can also filter data based on the tag that the data has (such as filtering on a specific observer).

[[File:Grafana filter tag.png|frameless|600x600px]]

Next, select the telemetry field you are looking to graph by clicking on field("value"). If there is data in the database that has been properly decoded you should see the relevant fields for that satellite displayed here:

[[File:Grafana field value.png|frameless|600x600px]]

See any data in your graph yet? If not, change your timeframe in the upper-right corner to something like "last 30 days" as the default of "last 6 hours" may not have data decoded (especially true for our dev instance, where we have no steady stream of recent data)

SELECT: mean() (default), distinct(), and last() are likely to be the most useful for us. Keep in mind that there is the possibility for multiple data points from multiple stations and observations, some overlapping. InfluxDB handles this for us. The timeframe selected is also taken into account in these measurements. This line is where you may need to add math to make the number human-readable. For instance, for CubeBel-1, to calculate voltage we have to take (Measured value) / 4096×2.5×3.75, which looks like this:

[[File:Grafana math.png|frameless|900x900px]]

GROUP BY: you may wish to change the fill value here, there are a number of options. Be careful as this may be misleading to users if we are dealing with very sparse data sets, as this option will fill in any gaps, yet "none" or "linear" may be options to use to make the graphs look better.

You can also add multiple queries to the same graph with the Add Query button at the bottom

==== Axes ====

You may want to change the Unit here, as "Short" may be undesired for certain figures, and "None" would be better.

==== Display ====

If you are doing a line graph and do not want the shading below the line, change the "Fill" value here to 0.

=== Graph Settings ===

In the gear icon for a graph are the graph settings. Some things to change here:

* Name
* Folder (see the hierarchy above)
* "Now delay now-" - I suggest 30d (the last 30d) as without it the default is 6 hours

"Save As" will allow you to make a copy of a graph and hack on it.
[[Category:Development]]
[[Category:Telemetry]]
__NOEDITSECTION__

Repositories Policy

2019-02-02T21:19:28Z

Cshields: deprecated warning

{{Warning|This page is out of date and should be removed soon.}}

Intro
-----
SatNOGS uses GitHub for code, hardware, designs and issues repositories around the project. Each repository has a main and a co- maintainer who are ultimately responsible for committing code, versioning, accepting pull requests, triaging issues and generally owning the repo.

Naming
---------
Any repo originating from SatNOGS project is named using `satnogs-<name>` (e.g. `satnogs-rotator`). We also maintain forks of other projects retaining their original names (e.g. `rtl-sdr`)

Versioning
------------
Most **hardware** repos will be following this scheme:

- `master` is for current dev work.
- major versions will be branched out of `master` with major version number (e.g. `v2`).
- minor versions will be tags (e.g. `v2.1`).

All **software** repos are following this scheme:

- `master` reflects the production-ready state of the code.
- `dev` reflects the latest development code changes. This is the default merge target for Pull Requests.
- featured branches are created for development (e.g. `feature-add-single-view`),
- tags will be created for major revisions that we want to point to (e.g. `v3`).

Some repos (minority, like `satnogs-antennas`) will be following a folders-based versioning as it fits more their development scheme. (sorry git lovers!)

List of repos with descriptions and maintainers
----

- [`satnogs-rotator`](https://github.com/satnogs/satnogs-rotator)
- *Description*: Designs for SatNOGS Rotator
- *Maintainer*: Manthos Papamatthaiou
- *Co-maintainer*: Agis Zisimatos
- [`satnogs-rotator-controller`](https://github.com/satnogs/satnogs-rotator-controller)
- *Description*: Electronics for SatNOGS Rotator
- *Maintainer*: Agis Zisimatos
- *Co-maintainer*: Manthos Papamatthaiou
- [`satnogs-docs`](https://github.com/satnogs/satnogs-docs)
- *Description*: Documentation for SatNOGS software projects
- *Maintainer*: John Nemo Giannelos
- *Co-maintainer*: Nikos Roussos
- [`satnogs-software`](https://github.com/satnogs/satnogs-software)
- *Description*: Various Software used in SatNOGS project
- *Maintainer*: Vasilis Tsiligiannis
- *Co-maintainer*: Ioannis Charitopoulos
- [`satnogs-org`](https://github.com/satnogs/satnogs-org)
- *Description*: Repo for organizational purposes and assets
- *Maintainer*: Pierros Papadeas
- *Co-maintainer*: Papamathaiou Manthos
- [`satnogs-preso`](https://github.com/satnogs/satnogs-preso)
- *Description*: Presentations about SatNOGS project
- *Maintainer*: Pierros Papadeas
- *Co-maintainer*: Eleytherios Kosmas
- [`satnogs-antennas`](https://github.com/satnogs/satnogs-antennas)
- *Description*: Designs for SatNOGS Antennas
- *Maintainer*: Vasilis Tsiligiannis
- *Co-maintainer*: Dimitris Papadeas
- [`satnogs-diplexer`](https://github.com/satnogs/satnogs-diplexer)
- *Description*: Designs and plans for SatNOGS Diplexer
- *Maintainer*: Agis Zisimatos
- *Co-maintainer*: Vasilis Tsiligiannis
- [`satnogs-tripod`](https://github.com/satnogs/satnogs-tripod)
- *Description*: Designs for SatNOGS Tripod
- *Maintainer*: Dimitris Papadeas
- *Co-maintainer*: Pierros Papadeas
- [`satnogs-radome`](https://github.com/satnogs/satnogs-radome)
- *Description*: Designs for SatNOGS Radome
- *Maintainer*: Dimitris Papadeas
- *Co-maintainer*: Pierros Papadeas
- [`satnogs-client`](https://github.com/satnogs/satnogs-client)
- *Description*: Software for SatNOGS Client
- *Maintainer*: John Nemo Giannelos
- *Co-maintainer*: Ioannis Charitopoulos
- [`satnogs-ansible`](https://github.com/satnogs/satnogs-ansible)
- *Description*: Ansible recipes and templates for our infrastructure setup
- *Maintainer*: Nikos Roussos
- *Co-maintainer*: Axilleas Pipinellis
- [`satnogs-network`](https://github.com/satnogs/satnogs-network)
- *Description*: Software for SatNOGS Network
- *Maintainer*: Nikos Roussos
- *Co-maintainer*: John Nemo Giannelos
- [`satnogs-db`](https://github.com/satnogs/satnogs-db)
- *Description*: Software for SatNOGS DB
- *Maintainer*: Nikos Roussos
- *Co-maintainer*: John Nemo Giannelos
- [`satnogs-rotator`](https://github.com/satnogs/satnogs-rotator)
- *Description*: Designs and plans for SatNOGS Rotator
- *Maintainer*: Manthos Papamatthaiou
- *Co-maintainer*: Agis Zisimatos
- [`upscuits`](https://github.com/satnogs/upscuits)
- *Description*: Our service monitoring site
- *Maintainer*: Pierros Papadeas
- *Co-maintainer*: Axilleas Pipinellis
- [`rtl-sdr`](https://github.com/satnogs/rtl-sdr)
- *Description*: SatNOGS maintained rtl-sdr fork
- *Maintainer*: Vasilis Tsiligiannis
- *Co-maintainer*: none

Rotators

2019-02-02T21:17:20Z

Cshields:

__NOTOC__

The SatNOGS Client uses [http://hamlib.sourceforge.net/ hamlib] to speak to a rotator. With this, we are able to support almost any commercially available rotator, and have the flexibility to support home built rotators that implement protocols like [https://www.mustbeart.com/software/easycomm.txt EasyComm] or Yaesu GS-232.

If you would rather start with a stationary antenna setup (no rotator), see our [[Omnidirectional Station How To|omnidirectional guide]].

{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Rotators ===
!
! style="width: 49%" |
=== Homebuilt Rotators ===
|-
|[[File:G5500.jpg|left|frameless|100x100px]]

==== [[G-5500|Yaesu G-5500]] ====
The G-5500 is a common rotator for amateur radio AZ/EL applications. The SatNOGS client interfaces with this rotator via the hamlib library. While a commercial computer interface is available from Yaesu, the SatNOGS project provides an open hardware design that is much cheaper.
* [[G-5500|G-5500 SatNOGS Wiki page]]
* G-5500 Arduino interface
* [https://www.yaesu.com/indexVS.cfm?cmd=DisplayProducts&ProdCatID=104&encProdID=79A89CEC477AA3B819EE02831F3FD5B8 Yaesu G-5500 Product link]
|
|[[File:30033213301 ef78e64120 k.jpg|left|frameless|133x133px]]

====[[SatNOGS Rotator v2]]====
The v2 rotator is not recommended, as v3 provides much greater strength and durability. These docs remain for historical purposes.
* [[SatNOGS Rotator v2|SatNOGS v2 Wiki page]]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v2 SatNOGS v3 source code]
|-
|[[File:Portable Rotation.jpg|left|frameless|100x100px]]

==== Portable Rotation AZ/EL ====
Docs to be written, but we do have successful stations using this rotator with the SatNOGS client.

* [http://portablerotation.com/shop/azel-portable-rotor-system/ Portable Rotation product link]
|
|[[File:V3.jpg|left|frameless|100x100px]]

====[[SatNOGS Rotator v3]]====
The v3 rotator is a complete overhaul on the v2 design. The 2020 slotted extrusion frame and larger gears provide for a stronger rotator with greater wind loading.
* [[SatNOGS Rotator v3|SatNOGS v3 Wiki page]]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v3.0 SatNOGS v3 source code]
|-
|[[File:Alfa Spid.jpg|left|frameless|133x133px]]

==== Alfa Spid X-Y ====

* [[SPID Big RAS|Alfa Spid SatNOGS Wiki page]]
* [http://alfaradio.ca/alfaspid-azel.html Alfa Spid product link]
|
|
|-
|[[File:Dwingleloo.png|left|frameless|100x100px]]

==== Dwingleloo Radio Observatory ====
(okay, you're not likely to keep a deep space observatory on the network, but it has been done!)
* [https://www.youtube.com/watch?v=wGJh139EDfk Video of the observatory in action on SatNOGS (YouTube)]
* [https://network.satnogs.org/stations/384/ Dwingleloo on SatNOGS network]
* [[wikipedia:Dwingeloo_Radio_Observatory|About the Dwingleloo Radio Observatory (wikipedia)]]
|
|
|}

[[ Category:Rotator ]]
__NOEDITSECTION__

Rotators

2019-02-02T21:08:41Z

Cshields: added Dwingleloo to rotators (lol)

File:Dwingleloo.png

2019-02-02T21:05:36Z

Cshields:

Dwingleloo Radio Observatory

Antennas

2019-02-02T21:03:37Z

Cshields: found a station using the winkler turnstile

__NOTOC__
The type of antenna largely depends on the type of ground station. A no rotator ground station will benefit from a different type of antenna (omnidirectional) than a rotator based ground station (directional). The two different approaches are explored below. In addition to the choice of antenna the choice of location for the ground station will have an effect on the quality of observations.

==Non-Rotator Ground Station (Omnidirectional)==
This type of ground station will require an antenna that will give a broad coverage from its fixed position. It is therefore not just the antenna that needs to be considered but also the proximity of buildings, geography or metallic structures that might be in the path of a line of sight between the ground station and satellite.Typical ground stations have had success with simple wire antennas that can be commercially bought or made at home. Colinear or ‘white stick’ antennas are vertically polarised omnidirectional antennas. These have anecdotally been used for successful satellite work but should be avoided. The following are considered suitable choices:'''It is highly recommended that you use a mast-mounted Low-Noise Amplifier (LNA) with these antennas.'''
{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Antennas ===
!
! style="width: 49%" |
=== Homebrew Antennas ===
|-
|[[File:WiMo TA-1.gif|left|frameless|160x160px]]

==== WiMo TA-1 ====
VHF Turnstile

Estimated cost: 90€

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/141/ 141 - balcony-only-east-passes]

[https://network.satnogs.org/stations/33/ 33 - G7KSE]

[https://network.satnogs.org/stations/129/ 129 - Chabot Space And Science Center]

* [https://www.wimo.com/scanner-antennas_e.html#004 Product link]
* [http://oz9aec.net/antennas/air-tests-wimo-ta-1-turnstile-antenna OZ9AEC Review]
|
|[[File:VHF Turnstile.jpg|left|frameless|100x100px]]

==== Turnstile ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/13/ 13 - OZ9AEC-VHF1]

[https://network.satnogs.org/stations/7/ 7 - Stony]

[https://network.satnogs.org/stations/16/ 16 - VK5QI-70CM]

* SatNOGS Turnstile Antenna (TBD)
* [https://www.vk4adc.com/web/vhfuhf-projects/26-multiband-ants/156-turnstile-vhf-uhf-fds VK4ADC instructions for VHF and UHF Turnstile antennas]
* [https://www.aeronetworks.ca/2017/12/amateur-satcom-rx-antenna-for-2-meter.html Six-element tape-measure VHF Turnstile with modeled patterns (could be used as directional) by Herman Oosthuysen]
|-
|[[File:M2 Eggbeaters.png|left|frameless|100x100px]]

==== M2 Eggbeater ====
VHF / UHF Eggbeater Antennas

Estimated cost: $304 (VHF), $280 (UHF), $573 (combo)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/50/ 50 - N5CNB-UHF]

[https://network.satnogs.org/stations/77/ 77 - N5CNB-VHF]

* [https://www.m2inc.com/FGEB144RK2M Product link for VHF]
* [https://www.m2inc.com/FGEB432RK70CM Product link for UHF]
* [https://www.m2inc.com/FGSATPACK1 Product link for combination package]
|
|[[File:VHF EZ-Lindenblad.png|left|frameless|112x112px]]

==== Lindenblad ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/12/ 12 - W2BFJ]

[https://network.satnogs.org/stations/98/ 98 - Grove-UHF-01]

[https://network.satnogs.org/stations/442/ 442 - DL1UNX-FFB VHF]

* [https://www.amsat.org/wordpress/wp-content/uploads/2015/08/An-EZ-Lindenblad-Antenna-for-2-Meters2.pdf AA2TX EZ-Lindenblad design can be found at this AMSAT PDF]
* [https://www.qsl.net/py4zbz/DCA.pdf KD6JDJ instructions can be found at this QST PDF]
* [https://www.amsat.org/articles/w6shp/lindy.html W6SHP instructions for VHF and UHF Lindenblad]
|-
|[[File:Winkler Turnstile.jpg|left|frameless|100x100px]]

==== Winkler Turnstile ====
VHF/UHF Turnstile Antennas

Estimated cost: 40€ (VHF), 30€ (UHF)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/47/ 47 - DB0RV]

* [http://www.winklerantennenbau.de/sonst.htm Pricing page]
* [http://www.winklerantennenbau.de/kreuz137.htm Product link for VHF]
* [http://www.winklerantennenbau.de/kreuz446.htm Product link for UHF]
|
|[[File:UHF Paralindy.jpg|left|frameless|100x100px]]

==== UHF Parasitic Lindenblad ====
Estimated cost: $15 (with access to a 3D printer)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/300/ 300 - KB9JHU-Experimental]

[https://network.satnogs.org/stations/32/ 32 - SV1QZZ - UHF #2]

[https://network.satnogs.org/stations/187/ 187 - K3LRD UHF Lindenblad]

* [https://www.amsat.org/wordpress/wp-content/uploads/2014/01/70ParaLindy.pdf Instructions can be found at this AMSAT PDF by AA2TX]
|-
|
|
|[[File:Quadrifilar Antennas.png|left|frameless|100x100px]]

==== Quadrifilar Helix Antenna (QFH) ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/272/ 272 - K3LRD VHF QFH]

[https://network.satnogs.org/stations/255/ 255 - EA5BZ - Elche]

[https://network.satnogs.org/stations/183/ 183 - SPUTNIX-R2ANF-VHF/UHF-stationary]

* [http://www.g4ilo.com/qfh.html G4ILO QFH Instructions]
* [https://www.aeronetworks.ca/2017/12/parasitic-quadrifilar-helical-antenna.html VHF Model/patterns for QFH by Herman Oosthuysen]
* [http://jcoppens.com/ant/qfh/calc.en.php QFH Calculator by ON6JC/LW3HAZ]
* [https://community.libre.space/t/an-easy-3d-printed-quadrifilar-helix-antenna/1487 3D Printed UHF QFH Antenna by surligas]
|-
|
|
|[[File:Vhf moxon turnstile.png|left|frameless|100x100px]]

==== "Turnstiled" Moxon ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

TBD

* [https://sat.fg8oj.com/images/VHFUHFSatelite.pdf Instructions can be found at this QST article by W4RNL]
|}


==Rotator Ground Station==
A rotator based ground station is able to make use of directional antennas. These will have a directional gain, meaning that you will need to point them in the direction of the satellite but the signal you receive will be stronger and for longer. They will allow much lower to the horizon passes to be received and more successful observations. These are not complex antennas but the choice will depend on the type of satellite and there are variations on the main types: yagi, helical and quad.

{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Antennas ===
!
! style="width: 49%" |
=== Homebrew Antennas ===
|-
|[[File:M2 Leopack.png|left|frameless|100x100px]]

==== M2 Circularly Polarized Yagis ====
VHF/UHF Cross-element Yagi

Estimated cost: $296 (UHF), $296 (VHF), $638 (Combo kit)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/2/ 2 - KB9JHU]

[https://network.satnogs.org/stations/109/ 109 - EA6WQ - Tomas Orzaez]

[https://network.satnogs.org/stations/25/ 25 - N7IPY]

* [https://www.m2inc.com/FG2MCP8A Product link - VHF]
* [https://www.m2inc.com/FG436CP16 Product link - UHF]
* [https://www.m2inc.com/FGLEOPACK Product link - Combo kit]
|
|[[File:Cross element UHF yagi.jpg|left|frameless|133x133px]]

==== Yagi Antennas, Cross-element yagi antennas ====
VHF/UHF directional antenna

Estimated cost: TBD

A common type of antenna that is either horizontally or vertically polarised. Simple to construct and suitable for a large number of satellites.

Some SatNOGS stations using this antenna:

TBD

* TBD: Assembly instructions
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Yagi Source code for SatNOGS yagi antenna designs are here].
|-
|[[File:Wimo xquad vhf.jpg|left|frameless|100x100px]]

==== WiMo X Quad ====
VHF/UHF Cross-element Quad

Estimated cost: 149€ (VHF), 149€ (UHF)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

[https://network.satnogs.org/stations/49/ 49 - OZ7SAT]

[https://network.satnogs.org/stations/232/ 232 - VK5QI-AZ/EL]

* [https://www.wimo.com/xquad-antennas_e.html Product link]
|
|[[File:Satnogs helical v1.jpg|left|frameless|100x100px]]

==== Helical Antennas ====
UHF circularly polarized directional antenna

Estimated cost: TBD

A less common type that are circularly polarized. The antenna looks a bit like a corkscrew and can be either LHCP (Left hand circular polarisation) or RHCP (right hand circular polarisation).

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

* v4 [https://satnogs.dozuki.com/Guide/Helical+Antenna+v4/11 Assembly instructions]
* [https://ohai.satnogs.org/project/helical-antenna-v5/ v5 Assembly instructions]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical Source code for SatNOGS helical antenna designs are here.]
|-
|[[File:Arrow Portable Yagi.jpg|left|frameless|100x100px]]

==== Arrow Dual-band portable yagi ====
VHF/UHF portable yagi

Estimated cost: $83-$149

Some SatNOGS stations using this antenna:

TBD

* [http://www.arrowantennas.com/arrowii/146-437.html Product price/ordering link]
* [http://www.arrowantennas.com/sub/arrowiiyagi.html Product details link]
|
|
|-
|[[File:Elk Log Periodic.jpg|left|frameless|112x112px]]

==== Elk Log Periodic ====
VHF/UHF portable yagi

Estimated cost: $130-$163

Some SatNOGS stations using this antenna:

TBD

* [https://elkantennas.com/product/dual-band-2m440l5-log-periodic-antenna/ Product link]
|
|
|}


A radome design is available from SatNOGS. This will protect the ground station from the elements in all but extra ordinary conditions. The design can be found [https://gitlab.com/librespacefoundation/satnogs/satnogs-radome/blob/master/satnogs-radome-v1-bom.ods here] and construction guide [https://ohai.satnogs.org/project/satnogs-radome-v1/hardware/ here]. 
[[Category:Antennas]]
__NOEDITSECTION__
[[Category:Omnidirectional Antennas]]
[[Category:Directional Antennas]]

Rotators

2019-02-02T21:01:51Z

Cshields: /* Alfa Spid X-Y */

SatNOGS Rotator v2

2019-02-02T20:58:36Z

Cshields: adding deprecation warning

{{Warning|v2 of the SatNOGS rotator has been deprecated with the much more robust [[SatNOGS Rotator v3]]. If you are starting a new build please consider building v3 instead. This documentation is provided for historical purposes.}}
{{Template:Rotator
|Rotator-Name=SatNOGS Rotator v2
|image= 29854586940 d47e229453 k.jpg
|type= Az/El
|cost= ~200 (with electronics)
|status= Beta
|latest-release= https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tags/v2.0
|latest-release-name= v2
|source-repo= https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/ gitlab
|documentation= https://satnogs.dozuki.com/c/SatNOGS_Hardware dozuki
}}

== Intro ==

v2 is the first attempt to build a rotator for SatNOGS project.

[[File:30033213301 ef78e64120 k.jpg|thumb|center|800x420px|alt=|Inside the v2 rotator]]

== Assembly ==

Assembly instructions can be found [https://satnogs.dozuki.com/Guide/SatNOGS+Ground+Station+v2+Electronics+Assembly/2 here].

All the parts are placed [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tags/v2.0 here].
The electronics and firmware to control the motors are placed [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-controller/tags/v1 here].
The v2 rotator could be also controlled by the [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-controller/tags/v2.2 v2.2]
controller. The [https://wiki.satnogs.org/SatNOGS_Rotator_Controller v2.2 rotator controller wiki].

In the [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-controller/tags/v1 v1] board the new [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware firmware] hasn't been tested. At first changes in [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware/blob/master/libraries/rotator_pins.h rotator_pins.h] header file must be done to match with v1 board pins. But the different mcu Atmega32u4, optiboot bootloader and WDT peripheral may create problems to nominal operation of the rotator.

Related posts in [https://community.libre.space/ libre space community]:

* [https://community.libre.space/t/design-files-for-satnogs-v2-box/468 Design files for SatNOGS v2 box]
* [https://community.libre.space/t/iz5rzr-satnogs-v-2-from-italy/1001 IZ5RZR Satnogs V.2 from Italy]
* [https://community.libre.space/t/newbie-wants-to-build-a-v2-ground-station/3189 Newbie wants to build a V2 ground station]

[[ Category:Rotator ]]

Rotators

2019-02-02T20:55:11Z

Cshields: Linking alfa spid page

__NOTOC__

The SatNOGS Client uses [http://hamlib.sourceforge.net/ hamlib] to speak to a rotator. With this, we are able to support almost any commercially available rotator, and have the flexibility to support home built rotators that implement protocols like [https://www.mustbeart.com/software/easycomm.txt EasyComm] or Yaesu GS-232.

If you would rather start with a stationary antenna setup (no rotator), see our [[Omnidirectional Station How To|omnidirectional guide]].

{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Rotators ===
!
! style="width: 49%" |
=== Homebuilt Rotators ===
|-
|[[File:G5500.jpg|left|frameless|100x100px]]

==== [[G-5500|Yaesu G-5500]] ====
The G-5500 is a common rotator for amateur radio AZ/EL applications. The SatNOGS client interfaces with this rotator via the hamlib library. While a commercial computer interface is available from Yaesu, the SatNOGS project provides an open hardware design that is much cheaper.
* [[G-5500|G-5500 SatNOGS Wiki page]]
* G-5500 Arduino interface
* [https://www.yaesu.com/indexVS.cfm?cmd=DisplayProducts&ProdCatID=104&encProdID=79A89CEC477AA3B819EE02831F3FD5B8 Yaesu G-5500 Product link]
|
|[[File:30033213301 ef78e64120 k.jpg|left|frameless|133x133px]]

====[[SatNOGS Rotator v2]]====
The v2 rotator is not recommended, as v3 provides much greater strength and durability. These docs remain for historical purposes.
* [[SatNOGS Rotator v2|SatNOGS v2 Wiki page]]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v2 SatNOGS v3 source code]
|-
|[[File:Portable Rotation.jpg|left|frameless|100x100px]]

==== Portable Rotation AZ/EL ====
Docs to be written, but we do have successful stations using this rotator with the SatNOGS client.

* [http://portablerotation.com/shop/azel-portable-rotor-system/ Portable Rotation product link]
|
|[[File:V3.jpg|left|frameless|100x100px]]

====[[SatNOGS Rotator v3]]====
The v3 rotator is a complete overhaul on the v2 design. The 2020 slotted extrusion frame and larger gears provide for a stronger rotator with greater wind loading.
* [[SatNOGS Rotator v3|SatNOGS v3 Wiki page]]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v3.0 SatNOGS v3 source code]
|-
|[[File:Alfa Spid.jpg|left|frameless|133x133px]]

==== Alfa Spid X-Y ====
Docs to be written, but we do have successful stations using this rotator with the SatNOGS client.

* [[SPID Big RAS|Alfa Spid SatNOGS Wiki page]]
* [http://alfaradio.ca/alfaspid-azel.html Alfa Spid product link]
|
|
|}

[[ Category:Rotator ]]

RF noise

2019-02-02T20:53:18Z

Cshields: redirect to troubleshooting

#REDIRECT [[Troubleshooting]]

If you notice a noise in the waterfall every time motors are spinning, you will need to :

- Twist each pair or the motor wire

- Add properly grounding

- Add capacitor to the DC input of drivers

- wrap the motors wire with adhesite aluminum and then connect it to GND on driver side

- add ferites to motors wires

[[File:Rf_noise.png]]

Troubleshooting Legacy

2019-02-02T20:52:42Z

Cshields: adding RF noise

== Client troubleshooting ==

=== Client not showing up on the network? ===

* Check that you have ticked the "Is it operational?" checkbox on the groundstation page.
* Check your settings and ensure that the API token and station ID are correct. You can get these from your profile page on the SatNOGS network site. If you have accounts in both dev and prod, make sure you're using the token and station ID from the right environment.
* Check your SATNOGS_NETWORK_API_URL. It should point to https://network.satnogs.org/api/ (prod) or https://network-dev.satnogs.org/api/ (dev).
* Check your network connectivity. Can you ping network.satnogs.org or network-dev.satnogs.org? Try running <code>curl https://network.satnogs.org</code> or <code>curl https://network-dev.satnogs.org</code>.
* Check the logs for an error (<code>journalctl -f -u satnogs-client.service</code> or <code>less /var/log/supervisor/satnogs-error.log</code>) and post to our forums at https://community.libre.space

=== "satnogsclient - ERROR - Cannot connect to socket 127.0.0.1:4533" ===

The client is trying to connect to rotctld but is unable to.

* If you have a no-rotator setup, ensure that satnogs-client is configured as such; see the [[Raspberry Pi 3]] page for info on how to do this.

* If you do have a rotator, ensure that rotctld is running.

== Signal troubleshooting ==

=== Not receiving anything? ===

* Make sure the satellite you are testing observations against is active and recently received by others on [https://network.satnogs.org our production network site]. If you click on a satellite name, a popup will appear and give you the option to click on "Past Observations". If everything in the past shows red, then the problem is likely with that satellite.

* SO-50 is a good satellite to use for testing as it is a strong FM voice signal assuming you have UHF capabilities. Schedule using "PE0SAT - Mode V/U FM Voice - 436.794 MHz". Here is an example to compare against: https://network.satnogs.org/observations/3334/

* ISS is a good test for VHF as the APRS digipeater is alive again (as of this writing; check [https://www.issfanclub.com/ issfanclub.com] for up-to-date information). When you schedule it, be sure to select the APRS downlink.

* If you're using an rtlsdr, check that it can be seen and is operating correctly by running rtl_test. Let it run for 30 seconds or so, then hit Ctrl-c to kill it:

<pre>
pi@raspberrypi:~ $ rtl_test
Found 1 device(s):
0: Realtek, RTL2838UHIDIR, SN: 00000001

Using device 0: Generic RTL2832U OEM
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6
[R82XX] PLL not locked!
Sampling at 2048000 S/s.

Info: This tool will continuously read from the device, and report if
samples get lost. If you observe no further output, everything is fine.

Reading samples in async mode...
^CSignal caught, exiting!

User cancel, exiting...
Samples per million lost (minimum): 0
</pre>

* You can also try a manual run of satnogs_fm_demod.py to make sure that works:

<pre>
$ cd /tmp
$ satnogs_fm_demod.py --rx-sdr-device=rtlsdr --rx-freq=444000000 --file-path=./audio-out.ogg --waterfall-file-path=./waterfall.dat
</pre>

Let it run for a minute or so. If everything is working, this should create an .ogg file and a .dat file of non-zero size (probably a few MB each).

[[File:Waterfall_3519_2017-04-24T04-48-48_resized.png|frame|Check your location!]]
=== Observations seem off-frequency? ===
* '''PPM drift''' While newer SDR devices are very good and stable, there still may be some PPM drift to compensate for if you notice that signals are consistently off center. The SATNOGS_PPM_ERROR setting in /etc/supervisord.d/satnogs.ini can be used to correct for this.
* '''Clock sync''' Make sure your clock is synced. Ensure ntp is configured and running (especially with the Raspberry Pi which lacks a real time clock)
* '''Wrong location''' If your signal seems to be on but drifts at the apex like in this image, check to make sure your Latitude, Longitude, and Elevation coordinates are set properly and in the right format.
[[File:Rf noise.png|alt=RF Noise|left|thumb|400x400px|Too much RF Noise]]

=== RF Noise ===
If you notice a noise in the waterfall every time motors are spinning, you will need to:
* Twist each pair or the motor wire
* Add proper grounding
* Add capacitor to the DC input of drivers
* wrap the motors wire with adhesite aluminum and then connect it to GND on driver side
* add ferites to motors wires

Provide documentation

2019-02-02T20:47:42Z

Cshields: update

Documentation is ''always'' welcome. Here's how you can contribute:

* Edit this wiki! If you see something out of date, or don't see a page, create an account and get started!
* Submit pull requests to the [https://gitlab.com/librespacefoundation/satnogs/satnogs-docs Gitlab Read The Docs] repository
* Much information about the SatNOGS project is in the [https://community.libre.space SatNOG discussion forums], and can be recorded in the wiki or other documentation sites
* Porting tutorials from [https://satnogs.dozuki.com satnogs.dozuki.com] to the newer [https://gitlab.com/librespacefoundation/satnogs/satnogs-ohai ohai site]

MediaWiki:Sidebar

2019-02-02T20:44:02Z

Cshields: add provide documentation to menu bar

* Build
** Raspberry_Pi_3|Install a Raspberry Pi
** Build|Build a Ground Station
** Rotators|Rotators
** Antennas|Antennas
** Omnidirectional_Station_How_To| Omnidirectional Station
** Radio|SDR Support
** Troubleshooting|Client Troubleshooting
* Operate
** Operation|Managing Observations
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets
** Telemetry_Dashboards|Telemetry Dashboards
** :Category:RF Modes|RF Modes
* Contribute
** Satnogs_DB|Crowd-Sourced Satellite Info
** Software_contribution|Software Contribution
** Development_Environment|Development Environment
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module
** SatNOGS_Client_Development|SatNOGS Client Development
** Academic_Papers|Academic Papers citing SatNOGS
** Provide_documentation|Provide Documentation
* Contact
** Get_In_Touch|Get In Touch
** https://community.libre.space|Forums
* Links
** https://db.satnogs.org|SatNOGS DB
** https://network.satnogs.org|SatNOGS Network
** https://dashboard.satnogs.org|SatNOGS Dashboard
** https://community.libre.space|SatNOGS Forums
** https://libre.space|Libre Space Foundation
** https://status.libre.space|System Status
* SEARCH

GS Software

2019-02-02T20:40:33Z

Cshields: deprecated warning

{{Warning|Information on this page is outdated! Relevant information can be found through the menu at the top of the screen, and this page should be deleted someday.}}

SatNOGS includes an open-source modular software stack, developed from scratch or utilizing existing projects. The versatility of the architecture enables communication with existing software or easy development of custom software for specific needs.

For all following Software components you can select to either use the SatNOGS software of the equivalent software for non-networked operations.

==Tracking==

Two options for tracking are available. Operators may use the popular GPredict for real-time satellite tracking and orbit prediction or a custom build solution in Python that provides API for custom or remote unattended tracking. Both solutions are communicating with the mount using rotctld over Easycomm protocol.

===SatNOGS tracking software===

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client]
* [http://gpredict.oz9aec.net/ GPredict]

==Web services==

The main parts of SatNOGS web services are the Network, for orchestrating the network of distributed ground stations, and DB, for crowdsourcing Transmitter data.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-network satnogs network]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-db satnogs db]

Adding a new data decoder

2019-02-02T20:39:21Z

Cshields: category

== How to create the parser for a new satellite downlink ==

For satellite downlinks where SatNOGS provides demodulated data, but no decoder exists yet.

# Find and read documentation of the satellite downlink.
# Extract raw frames either from satnogs-network or satnogs-db.
#* from network: Open good observations whith demodulated data,
#*: then open the observation via the API,
#*: copy the link to the payloads and download them (e.g. via wget)
#* from db: Export frames of your satellite (how?), then convert them from hex to raw
# Write the Kaitai Struct (.ksy-file)
#* Open the [Kaitai WebIDE](https://ide.kaitai.io/)
#* Create a new .ksy-format file (press the empty sheet button in the lower left)
#* Upload the previously fetched raw frames as example data (press the cloud button in the lower left, select all files with raw frames)
#* Write the kaitai struct. Use already existing parsers for reference.
#* Always add the used documentation to the Kaitai struct (how?). If several sources are used, provide these sources when submitting the parser
#* Check the parsed output (object tree) for correctness

# Check the results of your parser
#* If another parser exists, cross-check your results with the output it provides.
#* Sometimes there are examples frames or examples recordings provided. Use them for verification (if the data is well-known.)

# Submit the created kaitai struct (how?)

Resources:
* http://doc.kaitai.io/user_guide.html
[[Category:Telemetry]]

Fedora Installation

2019-02-02T20:37:57Z

Cshields: adding unsupported warning to fedora

= Installing SatNOGS on Fedora runnning on a Raspberry Pi 3 =

{{Warning|This is not a supported method of running gr-satnogs and the SatNOGS client. Your success may vary.}}

This tutorial assumes the following:

1. You have a Raspberry Pi 3 with external power (5V, 2A).

2. USB keyboard, HDMI screen, HDMI cable, network cable (Wi-Fi isn't working on Fedora for now) and a Class 10 SDHC card at least 8GB.

3. One of the following sdr devices: RTL-SDR or USRP B200.

4. You have an account and a ground station registered on either [https://network.satnogs.org network.satnogs.org] or [https://network-dev.satnogs.org network-dev.satnogs.org]_. This is needed for getting your ground station ID number and your SatNOGS Network API key.

== Prepare Raspberry Pi ==

* Download fedora minimal or server RPi image (current 26) from [https://arm.fedoraproject.org/ Fedora ARM Project] (server edition provides a nice web interface, admin console, with several stats and SSH access).

* Connect SD card to your computer/laptop and prepare it as described at [https://fedoraproject.org/wiki/Raspberry_Pi#Preparing_the_SD_card Fedora wiki] (don't forget to [https://fedoraproject.org/wiki/Raspberry_Pi#Resizing_the_root_partition resize the root partition]).

* Attach sdcard to your RPi, plug in the HDMI cable, keyboard and ethernet and turn on the HDMI screen. Plug RPi to the power source.

* Fedora installation starts, follow the steps that show up in the screen. You'll have to setup:
** root password
** network connection
** timezone and ntp server, add at least one, `pool.ntp.org` is suggested
** a new user, e.g. `satnogs`. Don't forget to set administrator flag and add user to `dialout` group (needed for having access to sdr device).

* From now on you are able to access you RPi directly or through SSH. You can also use admin console if you have selected the fedora server version.

* Update fedora package to the latest version by running:

<pre>
sudo dnf -y update
</pre>

* Install dependencies for gr-satnogs and satnogs-client:

<pre>
sudo dnf install -y util-linux-user git gcc redhat-rpm-config python-devel redis vorbis-tools hamlib gnuradio gnuradio-devel cmake swig fftw3-devel gcc-c++ cppunit cppunit-devel doxygen gr-osmosdr libnova libnova-devel gnuplot libvorbis-devel libffi-devel openssl-devel libpng-devel
</pre>

* In order to expand the lifetime of the SD Card, edit /etc/fstab file with your favourite editor:
** Comment out the line of the swap partition
** Only if you used the "minimal" Fedora installation (not the "server" build), change options of root partition line (/ ext4) from `defaults,noatime` to `defaults,noatime,commit=1800`. This change means that changes on root partition will be written on SD Card every 30min
** Move /var/log and /var/tmp directories to memory by adding the following two lines:

<pre>
tmpfs /var/tmp tmpfs defaults,noatime,nosuid,size=120m 0 0
tmpfs /var/log tmpfs defaults,noatime,nosuid,mode=0755,size=80m 0 0
</pre>

* Automate creating of redis directory in /var/log path after boot by running:

<pre>
sudo sh -c 'echo "#Type Path Mode UID GID Age Argument" > /etc/tmpfiles.d/logdirs.conf'
sudo sh -c 'echo "d /var/log/redis 0750 redis redis 1d -" >> /etc/tmpfiles.d/logdirs.conf'
</pre>

* Enable and start Redis service in order to run automatically on startup:

<pre>
sudo systemctl enable redis.service
sudo systemctl start redis.service
</pre>

* Configure automatic cleanup of old data (while this is an optional step, if old files are not cleaned out regularly you run the risk of filling your disk over time)
** As-is this will clean out files older than 1 week. Adjust mtime to your liking
** Create /etc/cron.daily/satnogs with your favorite editor and add the following:

<pre>
#!/bin/sh
find /tmp/.satnogs/data -type f -mtime +7 -delete
</pre>

** Then run:

<pre>
sudo chmod +x /etc/cron.daily/satnogs
</pre>

* If you used Fedora Server, configure firewall for SatNOGS web user interface
** Create /usr/lib/firewalld/services/satnogs.xml and add the following:

<pre>
<?xml version="1.0" encoding="utf-8"?>
<service>
<short>SatNOGS (HTTP)</short>
<description>HTTP is the protocol used to serve Web pages. If you plan to make your Web server publicly available, enable this option. This option is not required for viewing pages locally or developing Web pages.</description>
<port protocol="tcp" port="5000"/>
</service>
</pre>

** If you used the server image run:

<pre>
sudo firewall-cmd --zone=FedoraServer --add-service=satnogs --permanent
sudo firewall-cmd --zone=FedoraServer --add-service=satnogs
</pre>

** Or for the minimal image:

<pre>
sudo firewall-cmd --zone=public --add-service=satnogs --permanent
sudo firewall-cmd --zone=public --add-service=satnogs
</pre>

== Install gr-satnogs ==

SatNOGS Client uses GNU Radio scripts in order to get observation data from satelites, gr-satnogs provide this functionality.

* Run the following command to install the packaged version of SatNOGS Client:

<pre>
git clone https://github.com/satnogs/gr-satnogs.git
cd gr-satnogs
mkdir build
cd build
cmake -DLIB_SUFFIX=64 -DCMAKE_INSTALL_PREFIX=/usr ..
make -j4
sudo make install
sudo sh -c 'echo /usr/lib64 > /etc/ld.so.conf.d/lib64.conf'
sudo ldconfig
</pre>

== Install satnogs-client ==

Building from source is outside of the scope of this document, we will use the packaged install for now.

Run the following command to install the packaged version of SatNOGS Client

<pre>
sudo pip install satnogsclient
</pre>

== Configure satnogs-client ==

SatNOGS Client needs some configuration before running:

* Create a .env file in your home directory (`~/.env`) and add station's details as they are defined at SatNOGS Network:

<pre>
export SATNOGS_API_TOKEN="1234567890qwertyuiopasdfghjklzxcvbnm1234"
export SATNOGS_STATION_ID="65"
export SATNOGS_STATION_LAT="40.662"
export SATNOGS_STATION_LON="23.337"
export SATNOGS_STATION_ELEV="150"
export SATNOGS_NETWORK_API_URL="https://network-dev.satnogs.org/api/"
</pre>

=== Optional settings ===

* There are more option you can export in the created .env file. You will probably need to change the default values of the settings bellow:

* SATNOGS_RX_DEVICE
** Defines the sdr device. It could be 'usrpb200' or 'rtlsdr'.
** Default Type: string
** Default Value: 'rtlsdr'

*SATNOGS_PPM_ERROR
** Defines PPM error of sdr, check :doc:`finding-ppm` for more details on PPM.
** Default Type: integer
** Default Value: 0

Other optional settings:

* SATNOGS_APP_PATH
** Defines the path where the sqlite database will be created.
** Default Type: string
** Default Value: '/tmp/.satnogs'

* SATNOGS_OUTPUT_PATH
** Defines the path where the observation data will be saved.
** Default Type: string
** Default Value: '/tmp/.satnogs/data'

* SATNOGS_COMPLETE_OUTPUT_PATH
** Defines the path where data will be moved after succesful upload on network.
** Default Type: string
** Default Value: ''

* SATNOGS_INCOMPLETE_OUTPUT_PATH
** Defines the path where data will be moved after unsuccesful upload on network.
** Default Type: string
** Default Value: '/tmp/.satnogs/data/incomplete'

* SATNOGS_ROT_IP
** Defines IP address where rotctld process listens.
** Default Type: string
** Default Value: '127.0.0.1'

* SATNOGS_ROT_PORT
** Defines port where rotctld process listens.
** Default Type: integer
** Default Value: 4533

* SATNOGS_RIG_IP
** Defines IP address where rigctld process listens.
** Default Type: string
** Default Value: '127.0.0.1'

* SATNOGS_RIG_PORT
** Defines port where rigctld process listens.
** Default Type: integer
** Default Value: 4532

== Prepare SDR Device ==

In order to have access and use SDR device you need to follow the next steps for your device:
The next step is to access and use the SDR device you have. Which steps you follow depends on your device.

=== USRP B200 ===

* Install uhd package:

<pre>
sudo dnf install -y uhd
</pre>

* Download uhd images:

<pre>
sudo /usr/bin/uhd_images_downloader
</pre>

* As the access will be only by ssh and not by direct login we are not be able to access SDR device through [https://en.wikipedia.org/wiki/Access_control_list Access Control List (ACL)], so we need to setup the appropriate udev rules by following the next steps:

* Copy udev rules from `/usr/lib/udev/rules.d/10-usrp-uhd.rules` to `/etc/udev/rules.d/10-usrp-uhd.rules`:

<pre>
sudo cp /usr/lib/udev/rules.d/10-usrp-uhd.rules /etc/udev/rules.d/10-usrp-uhd.rules
</pre>

* Replace ACL reference:

<pre>
sudo sed -i 's/0", ENV{ID_SOFTWARE_RADIO}="1"/6"/g' /etc/udev/rules.d/10-usrp-uhd.rules
</pre>

* Reload udev rules:

<pre>
sudo udevadm control --reload-rules
</pre>

* Confirm access on device by running (without sudo, just as single user):

<pre>
uhd_find_devices
</pre>

* In case you don't have access, make sure that the device is connected and that the created user is member of the `dialout` group by running:

<pre>
groups
</pre>

* If user isn't member of `dialout` group run (replace satnogs with the username of your user):

<pre>
sudo usermod -aG dialout satnogs
</pre>

=== RTL-SDR ===

As the access will be only by ssh and not by direct login we are not be able to access SDR device through [https://en.wikipedia.org/wiki/Access_control_list Access Control List (ACL)], so we need to setup the appropriate udev rules by following the next steps:

* Copy udev rules from `/usr/lib/udev/rules.d/10-rtl-sdr.rules` to `/etc/udev/rules.d/10-rtl-sdr.rules`:

<pre>
sudo cp /usr/lib/udev/rules.d/10-rtl-sdr.rules /etc/udev/rules.d/10-rtl-sdr.rules
</pre>

* Replace ACL reference and change group ownership:

<pre>
sudo sed -i 's/0", ENV{ID_SOFTWARE_RADIO}="1"/6"/g' /etc/udev/rules.d/10-rtl-sdr.rules
sudo sed -i 's/rtlsdr/dialout/g' /etc/udev/rules.d/10-rtl-sdr.rules
</pre>

* Reload udev rules:

<pre>
sudo udevadm control --reload-rules
</pre>

* If your rtlsdr device was already plugged in, you will need to unplug it and plug it back in. Otherwise, it is safe to plug it in now.

* In case you don't have access, make sure that the device is connected and that the created user is member of the `dialout` group by running:

<pre>
groups
</pre>

* If user isn't member of `dialout` group run (replace satnogs with the username of your user):

<pre>
sudo usermod -aG dialout satnogs
</pre>

* If you had to take that step, log out and log back in.

== Run satnogs-client ==

=== Manually ===

In order to manually run satnogs-client you need to follow the next steps:

* Export all the environment variables:

<pre>
source .env
</pre>

* Start rotctl daemon(note: given example parameters bellow, you may need to change, add or omit some of them. For a Yaesu G-5500 use -m 601 and -s 9600):

<pre>
rotctld -m 202 -r /dev/ttyACM0 -s 19200 &
</pre>

* Run the SatNOGS Client:

<pre>
satnogs-client
</pre>

**At this point your client should be fully functional! It will check in with the network URL at a 1 minute interval. You should check your ground station page on the website, the station ID will be in a red box until the station checks in, at which time it will turn green. There are many ways to automate the running and control of satnogs, we will give you 2 options below, supervisord and systemd.**

=== Automaticaly with Supervisord ===

[http://supervisord.org/introduction.html Supervisord] is one of the ways to automatically run SatNOGS Client. This is very useful especialy after a power failure or reboot of raspberry pi.

In order to setup supervisord we need to follow the next steps:

* Install supervisord:

<pre>
sudo dnf install -y supervisor
</pre>

* Automate creating of supervisor directory in /var/log path after boot by running:

<pre>
sudo sh -c 'echo "d /var/log/supervisor 0750 root root 3d -" >> /etc/tmpfiles.d/logdirs.conf'
</pre>

* Configure supervisord for rotctld

Open with sudo and your favorite editor and add this into /etc/supervisord.d/rotctld.ini:

<pre>
[program:rotctld]
command=/usr/bin/rotctld <rotctld PARAMETERS>
autostart=true
autorestart=true
user=<USERNAME>
priority=1
stdout_logfile=/var/log/supervisor/rotctld.log
stderr_logfile=/var/log/supervisor/rotctld-error.log
</pre>

Replace <USERNAME> with the username of the user you have created and <rotctld PARAMETERS> with the parameters needed to run rotctl in your case.

* Configure supervisord for satnogs-client

Add this into /etc/supervisord.d/satnogs.ini:

<pre>
[program:satnogs]
command=/usr/bin/satnogs-client
autostart=true
autorestart=true
user=<USERNAME>
environment=SATNOGS_NETWORK_API_URL="<URL>",SATNOGS_API_TOKEN="<TOKEN>",SATNOGS_STATION_ID="<ID>",SATNOGS_STATION_LAT="<LATITUDE>",SATNOGS_STATION_LON="<LONGITUDE>",SATNOGS_STATION_ELEV="<ELEVATION>"
stdout_logfile=/var/log/supervisor/satnogs.log
stderr_logfile=/var/log/supervisor/satnogs-error.log
</pre>

Replace <USERNAME> with the username of the user you have created.
Replace <...> instances in environment with the values you used in .env file,
you can also add in this list any other of the :ref:`optional settings <optional_settings>`.

* Reloading supervisord to get the new configuration:

<pre>
sudo systemctl enable supervisord.service
sudo systemctl start supervisord.service
</pre>

With that rotctld and satnogs-client should have started, you can follow the logs in /var/log/supervisor/.

*NOTE:* In case that you want to change something in .ini files like satnogs environment variables (url from the dev one to production one), then you will need to run:

sudo supervisorctl reload

=== Automaticaly with Systemd ===

[https://www.freedesktop.org/wiki/Software/systemd/ Systemd] is one of the ways to automatically run SatNOGS Client. This is very useful especialy after a power failure or reboot of raspberry pi.

In order to setup systemd we need to follow the next steps:

* Create the script which will initialize and run rotctld and satnogs-client in your home directory (`~/start-satnogs-client.sh`) with the following content:

<pre>
rotctld <rotctld PARAMETERS> &
date >> satnogs-auto.log
source .env
satnogs-client
</pre>

Replace <rotctld PARAMETERS> with the parameters needed to run rotctl in your case.

* Create as root the file /lib/systemd/system/satnogs-client.service and add the following content:

<pre>
[Unit]
Description=Satnogs Client
Requires=redis.service
After=redis.service

[Service]
User=<USERNAME>
WorkingDirectory=/home/<USERNAME>/
ExecStart=/bin/bash start-satnogs-client.sh
KillMode=control-group

[Install]
WantedBy=multi-user.target
</pre>

Replace <USERNAME> with the username of the user you have created.

* Enable and start satnogs-client.service:

<pre>
sudo systemctl enable satnogs-client.service
sudo systemctl start satnogs-client.service
</pre>

With that rotctld and satnogs-client should have started, you can follow the logs with journactl:

<pre>
journalctl -u satnogs-client.service
</pre>

Use `-f` flag if you want to see the latest updates on logs:

<pre>
journalctl -f -u satnogs-client.service
</pre>

*NOTE:* In case that you want to change something in start-satnogs-client.sh, make the change and then run:

<pre>
sudo systemctl stop satnogs-client.service
sudo systemctl start satnogs-client.service
</pre>

*NOTE:* In case that you want to change something in satnogs-client.service, make the change and then run:

<pre>
sudo systemctl daemon-reload
</pre>

Software Defined Radio

2019-02-02T20:32:59Z

Cshields:

{{DISPLAYTITLE:Software Defined Radio}}

SatNOGS can use a variety of SDRs. The most cost-effective solution is to use an RTL-SDR with a Raspberry Pi. More advanced SDRs can also be used, but they require more processing power than what a Raspberry Pi can offer.

=== RTL-SDR: RTL2832U & R820T2-Based Software Defined Radios ===
SatNOGS uses the RTL-SDR as the default signal receiver and tuner. 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.

These RTL-SDR "dongles" are known to work with Raspberry Pi 2 or greater:
* [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

=== Advanced Software Defined Radios ===
The following advanced SDRs are supported by SatNOGS. These may require more processing power than a Raspberry Pi 3b can offer.
* [https://www.ettus.com/product/category/USRP-Bus-Series USRP b200]
* [https://www.ettus.com/product/category/USRP-Networked-Series USRP2] (not compatible with the SatNOGS client on Raspberry Pi 3)
* [https://airspy.com/ Airspy] (not compatible with the SatNOGS client on Raspberry Pi 3)
* [https://greatscottgadgets.com/hackrf/ HackRF One] (not compatible with the SatNOGS client on Raspberry Pi 3)

=== 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:SDR]]
[[Category:Radio]]
__NOEDITSECTION__

Software Defined Radio

2019-02-02T20:32:27Z

Cshields: adding links, categories

{{DISPLAYTITLE:Software Defined Radio (SDR)}}

SatNOGS can use a variety of SDRs. The most cost-effective solution is to use an RTL-SDR with a Raspberry Pi. More advanced SDRs can also be used, but they require more processing power than what a Raspberry Pi can offer.

=== RTL-SDR: RTL2832U & R820T2-Based Software Defined Radios ===
SatNOGS uses the RTL-SDR as the default signal receiver and tuner. 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.

These RTL-SDR "dongles" are known to work with Raspberry Pi 2 or greater:
* [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

=== Advanced Software Defined Radios ===
The following advanced SDRs are supported by SatNOGS. These may require more processing power than a Raspberry Pi 3b can offer.
* [https://www.ettus.com/product/category/USRP-Bus-Series USRP b200]
* [https://www.ettus.com/product/category/USRP-Networked-Series USRP2] (not compatible with the SatNOGS client on Raspberry Pi 3)
* [https://airspy.com/ Airspy] (not compatible with the SatNOGS client on Raspberry Pi 3)
* [https://greatscottgadgets.com/hackrf/ HackRF One] (not compatible with the SatNOGS client on Raspberry Pi 3)

=== 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:SDR]]
[[Category:Radio]]
__NOEDITSECTION__

MediaWiki:Sidebar

2019-02-02T20:25:57Z

Cshields: adding sdr page to main menu

* Build
** Raspberry_Pi_3|Install a Raspberry Pi
** Build|Build a Ground Station
** Rotators|Rotators
** Antennas|Antennas
** Omnidirectional_Station_How_To| Omnidirectional Station
** Radio|SDR Support
** Troubleshooting|Client Troubleshooting
* Operate
** Operation|Managing Observations
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets
** Telemetry_Dashboards|Telemetry Dashboards
** :Category:RF Modes|RF Modes
* Contribute
** Satnogs_DB|Crowd-Sourced Satellite Info
** Software_contribution|Software Contribution
** Development_Environment|Development Environment
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module
** SatNOGS_Client_Development|SatNOGS Client Development
** Academic_Papers|Academic Papers citing SatNOGS
* Contact
** Get_In_Touch|Get In Touch
** https://community.libre.space|Forums
* Links
** https://db.satnogs.org|SatNOGS DB
** https://network.satnogs.org|SatNOGS Network
** https://dashboard.satnogs.org|SatNOGS Dashboard
** https://community.libre.space|SatNOGS Forums
** https://libre.space|Libre Space Foundation
** https://status.libre.space|System Status
* SEARCH

Rotators

2019-02-02T20:22:10Z

Cshields: add product links

__NOTOC__

The SatNOGS Client uses [http://hamlib.sourceforge.net/ hamlib] to speak to a rotator. With this, we are able to support almost any commercially available rotator, and have the flexibility to support home built rotators that implement protocols like [https://www.mustbeart.com/software/easycomm.txt EasyComm] or Yaesu GS-232.

If you would rather start with a stationary antenna setup (no rotator), see our [[Omnidirectional Station How To|omnidirectional guide]].

{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Rotators ===
!
! style="width: 49%" |
=== Homebuilt Rotators ===
|-
|[[File:G5500.jpg|left|frameless|100x100px]]

==== [[G-5500|Yaesu G-5500]] ====
The G-5500 is a common rotator for amateur radio AZ/EL applications. The SatNOGS client interfaces with this rotator via the hamlib library. While a commercial computer interface is available from Yaesu, the SatNOGS project provides an open hardware design that is much cheaper.
* [[G-5500|G-5500 SatNOGS Wiki page]]
* G-5500 Arduino interface
* [https://www.yaesu.com/indexVS.cfm?cmd=DisplayProducts&ProdCatID=104&encProdID=79A89CEC477AA3B819EE02831F3FD5B8 Yaesu G-5500 Product link]
|
|[[File:30033213301 ef78e64120 k.jpg|left|frameless|133x133px]]

====[[SatNOGS Rotator v2]]====
The v2 rotator is not recommended, as v3 provides much greater strength and durability. These docs remain for historical purposes.
* [[SatNOGS Rotator v2|SatNOGS v2 Wiki page]]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v2 SatNOGS v3 source code]
|-
|[[File:Portable Rotation.jpg|left|frameless|100x100px]]

==== Portable Rotation AZ/EL ====
Docs to be written, but we do have successful stations using this rotator with the SatNOGS client.

* [http://portablerotation.com/shop/azel-portable-rotor-system/ Portable Rotation product link]
|
|[[File:V3.jpg|left|frameless|100x100px]]

====[[SatNOGS Rotator v3]]====
The v3 rotator is a complete overhaul on the v2 design. The 2020 slotted extrusion frame and larger gears provide for a stronger rotator with greater wind loading.
* [[SatNOGS Rotator v3|SatNOGS v3 Wiki page]]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v3.0 SatNOGS v3 source code]
|-
|[[File:Alfa Spid.jpg|left|frameless|133x133px]]

==== Alfa Spid X-Y ====
Docs to be written, but we do have successful stations using this rotator with the SatNOGS client.

* [http://alfaradio.ca/alfaspid-azel.html Alfa Spid product link]
|
|
|}

[[ Category:Rotator ]]

Decode Telemetry and Packets

2019-02-02T20:17:17Z

Cshields: category

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

== Scholarly Articles ==
[[Category:Telemetry]]
__NOEDITSECTION__

Dashboard

2019-02-02T20:16:46Z

Cshields: categories

__NOTOC__

=== https://dashboard.satnogs.org<nowiki/>===
We are using [https://www.influxdata.com/ InfluxDB] and [https://grafana.com/ Grafana] for our telemetry dashboards. [https://www.influxdata.com/ InfluxDB] is a time-series database designed to be efficient for time-series data like the telemetry we collect in SatNOGS.

I'm going to drop a few things to get the reader going on telemetry dashboard in SatNOGS, and expect that the reader also reference the [https://docs.grafana.org Grafana documentation] for more details on building dashboards.

This doc also assumes you have an account to edit dashboards. You can generate an account by clicking the Sign In link.

Today there is a top level folder hierarchy designed as such:

* Telemetry (where telemetry dashboards should be stored, publicly accessible)
* General (for stats about our data collection itself, meta-dashboards, publicly accessible)
* Scratchpad (a playground for making grafana dashboards and testing functionality, not publicly accessible)

=== Creating a dashboard ===
Clicking the + icon will allow you to create a new dashboard. When you do this a new panel is started for you. This panel can be resized at the lower-right corner, and moved around by dragging once more panels are added.

Now - before you get started please note that '''you have to save your changes!! They do not save automatically!'''

Click "Graph" to make this a graph panel. Click the graph title and then Edit to edit this specific graph.

[[File:Grafana panel edit.png|frameless|600x600px]]

A few things you will want to edit:

==== General ====

Give it a meaningful title, of course. Description is not required, but offers a popup of more details to the user if you want to add more details.

==== Metrics ====
Select the metric by clicking "select measurement". What you will see here are the names of all measurements available which are the NORAD ID of the satellite in the database. You can type part of the NORAD ID to filter.

[[File:Grafana select measurement.png|frameless|600x600px]]

In most cases you will want to leave the WHERE clause blank, but from here you can also filter data based on the tag that the data has (such as filtering on a specific observer).

[[File:Grafana filter tag.png|frameless|600x600px]]

Next, select the telemetry field you are looking to graph by clicking on field("value"). If there is data in the database that has been properly decoded you should see the relevant fields for that satellite displayed here:

[[File:Grafana field value.png|frameless|600x600px]]

See any data in your graph yet? If not, change your timeframe in the upper-right corner to something like "last 30 days" as the default of "last 6 hours" may not have data decoded (especially true for our dev instance, where we have no steady stream of recent data)

SELECT: mean() (default), distinct(), and last() are likely to be the most useful for us. Keep in mind that there is the possibility for multiple data points from multiple stations and observations, some overlapping. InfluxDB handles this for us. The timeframe selected is also taken into account in these measurements. This line is where you may need to add math to make the number human-readable. For instance, for CubeBel-1, to calculate voltage we have to take (Measured value) / 4096×2.5×3.75, which looks like this:

[[File:Grafana math.png|frameless|900x900px]]

GROUP BY: you may wish to change the fill value here, there are a number of options. Be careful as this may be misleading to users if we are dealing with very sparse data sets, as this option will fill in any gaps, yet "none" or "linear" may be options to use to make the graphs look better.

You can also add multiple queries to the same graph with the Add Query button at the bottom

==== Axes ====

You may want to change the Unit here, as "Short" may be undesired for certain figures, and "None" would be better.

==== Display ====

If you are doing a line graph and do not want the shading below the line, change the "Fill" value here to 0.

=== Graph Settings ===

In the gear icon for a graph are the graph settings. Some things to change here:

* Name
* Folder (see the hierarchy above)
* "Now delay now-" - I suggest 30d (the last 30d) as without it the default is 6 hours

"Save As" will allow you to make a copy of a graph and hack on it.
[[Category:Development]]
[[Category:Telemetry]]
__NOEDITSECTION__

Antennas

2019-02-02T20:12:34Z

Cshields: categories

__NOTOC__
The type of antenna largely depends on the type of ground station. A no rotator ground station will benefit from a different type of antenna (omnidirectional) than a rotator based ground station (directional). The two different approaches are explored below. In addition to the choice of antenna the choice of location for the ground station will have an effect on the quality of observations.

==Non-Rotator Ground Station (Omnidirectional)==
This type of ground station will require an antenna that will give a broad coverage from its fixed position. It is therefore not just the antenna that needs to be considered but also the proximity of buildings, geography or metallic structures that might be in the path of a line of sight between the ground station and satellite.Typical ground stations have had success with simple wire antennas that can be commercially bought or made at home. Colinear or ‘white stick’ antennas are vertically polarised omnidirectional antennas. These have anecdotally been used for successful satellite work but should be avoided. The following are considered suitable choices:'''It is highly recommended that you use a mast-mounted Low-Noise Amplifier (LNA) with these antennas.'''
{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Antennas ===
!
! style="width: 49%" |
=== Homebrew Antennas ===
|-
|[[File:WiMo TA-1.gif|left|frameless|160x160px]]

==== WiMo TA-1 ====
VHF Turnstile

Estimated cost: 90€

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/141/ 141 - balcony-only-east-passes]

[https://network.satnogs.org/stations/33/ 33 - G7KSE]

[https://network.satnogs.org/stations/129/ 129 - Chabot Space And Science Center]

* [https://www.wimo.com/scanner-antennas_e.html#004 Product link]
* [http://oz9aec.net/antennas/air-tests-wimo-ta-1-turnstile-antenna OZ9AEC Review]
|
|[[File:VHF Turnstile.jpg|left|frameless|100x100px]]

==== Turnstile ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/13/ 13 - OZ9AEC-VHF1]

[https://network.satnogs.org/stations/7/ 7 - Stony]

[https://network.satnogs.org/stations/16/ 16 - VK5QI-70CM]

* SatNOGS Turnstile Antenna (TBD)
* [https://www.vk4adc.com/web/vhfuhf-projects/26-multiband-ants/156-turnstile-vhf-uhf-fds VK4ADC instructions for VHF and UHF Turnstile antennas]
* [https://www.aeronetworks.ca/2017/12/amateur-satcom-rx-antenna-for-2-meter.html Six-element tape-measure VHF Turnstile with modeled patterns (could be used as directional) by Herman Oosthuysen]
|-
|[[File:M2 Eggbeaters.png|left|frameless|100x100px]]

==== M2 Eggbeater ====
VHF / UHF Eggbeater Antennas

Estimated cost: $304 (VHF), $280 (UHF), $573 (combo)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/50/ 50 - N5CNB-UHF]

[https://network.satnogs.org/stations/77/ 77 - N5CNB-VHF]

* [https://www.m2inc.com/FGEB144RK2M Product link for VHF]
* [https://www.m2inc.com/FGEB432RK70CM Product link for UHF]
* [https://www.m2inc.com/FGSATPACK1 Product link for combination package]
|
|[[File:VHF EZ-Lindenblad.png|left|frameless|112x112px]]

==== Lindenblad ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/12/ 12 - W2BFJ]

[https://network.satnogs.org/stations/98/ 98 - Grove-UHF-01]

[https://network.satnogs.org/stations/442/ 442 - DL1UNX-FFB VHF]

* [https://www.amsat.org/wordpress/wp-content/uploads/2015/08/An-EZ-Lindenblad-Antenna-for-2-Meters2.pdf AA2TX EZ-Lindenblad design can be found at this AMSAT PDF]
* [https://www.qsl.net/py4zbz/DCA.pdf KD6JDJ instructions can be found at this QST PDF]
* [https://www.amsat.org/articles/w6shp/lindy.html W6SHP instructions for VHF and UHF Lindenblad]
|-
|[[File:Winkler Turnstile.jpg|left|frameless|100x100px]]

==== Winkler Turnstile ====
VHF/UHF Turnstile Antennas

Estimated cost: 40€ (VHF), 30€ (UHF)

Some SatNOGS stations using this antenna:

TBD

* [http://www.winklerantennenbau.de/sonst.htm Pricing page]
* [http://www.winklerantennenbau.de/kreuz137.htm Product link for VHF]
* [http://www.winklerantennenbau.de/kreuz446.htm Product link for UHF]
|
|[[File:UHF Paralindy.jpg|left|frameless|100x100px]]

==== UHF Parasitic Lindenblad ====
Estimated cost: $15 (with access to a 3D printer)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/300/ 300 - KB9JHU-Experimental]

[https://network.satnogs.org/stations/32/ 32 - SV1QZZ - UHF #2]

[https://network.satnogs.org/stations/187/ 187 - K3LRD UHF Lindenblad]

* [https://www.amsat.org/wordpress/wp-content/uploads/2014/01/70ParaLindy.pdf Instructions can be found at this AMSAT PDF by AA2TX]
|-
|
|
|[[File:Quadrifilar Antennas.png|left|frameless|100x100px]]

==== Quadrifilar Helix Antenna (QFH) ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/272/ 272 - K3LRD VHF QFH]

[https://network.satnogs.org/stations/255/ 255 - EA5BZ - Elche]

[https://network.satnogs.org/stations/183/ 183 - SPUTNIX-R2ANF-VHF/UHF-stationary]

* [http://www.g4ilo.com/qfh.html G4ILO QFH Instructions]
* [https://www.aeronetworks.ca/2017/12/parasitic-quadrifilar-helical-antenna.html VHF Model/patterns for QFH by Herman Oosthuysen]
* [http://jcoppens.com/ant/qfh/calc.en.php QFH Calculator by ON6JC/LW3HAZ]
* [https://community.libre.space/t/an-easy-3d-printed-quadrifilar-helix-antenna/1487 3D Printed UHF QFH Antenna by surligas]
|-
|
|
|[[File:Vhf moxon turnstile.png|left|frameless|100x100px]]

==== "Turnstiled" Moxon ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

TBD

* [https://sat.fg8oj.com/images/VHFUHFSatelite.pdf Instructions can be found at this QST article by W4RNL]
|}


==Rotator Ground Station==
A rotator based ground station is able to make use of directional antennas. These will have a directional gain, meaning that you will need to point them in the direction of the satellite but the signal you receive will be stronger and for longer. They will allow much lower to the horizon passes to be received and more successful observations. These are not complex antennas but the choice will depend on the type of satellite and there are variations on the main types: yagi, helical and quad.

{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Antennas ===
!
! style="width: 49%" |
=== Homebrew Antennas ===
|-
|[[File:M2 Leopack.png|left|frameless|100x100px]]

==== M2 Circularly Polarized Yagis ====
VHF/UHF Cross-element Yagi

Estimated cost: $296 (UHF), $296 (VHF), $638 (Combo kit)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/2/ 2 - KB9JHU]

[https://network.satnogs.org/stations/109/ 109 - EA6WQ - Tomas Orzaez]

[https://network.satnogs.org/stations/25/ 25 - N7IPY]

* [https://www.m2inc.com/FG2MCP8A Product link - VHF]
* [https://www.m2inc.com/FG436CP16 Product link - UHF]
* [https://www.m2inc.com/FGLEOPACK Product link - Combo kit]
|
|[[File:Cross element UHF yagi.jpg|left|frameless|133x133px]]

==== Yagi Antennas, Cross-element yagi antennas ====
VHF/UHF directional antenna

Estimated cost: TBD

A common type of antenna that is either horizontally or vertically polarised. Simple to construct and suitable for a large number of satellites.

Some SatNOGS stations using this antenna:

TBD

* TBD: Assembly instructions
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Yagi Source code for SatNOGS yagi antenna designs are here].
|-
|[[File:Wimo xquad vhf.jpg|left|frameless|100x100px]]

==== WiMo X Quad ====
VHF/UHF Cross-element Quad

Estimated cost: 149€ (VHF), 149€ (UHF)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

[https://network.satnogs.org/stations/49/ 49 - OZ7SAT]

[https://network.satnogs.org/stations/232/ 232 - VK5QI-AZ/EL]

* [https://www.wimo.com/xquad-antennas_e.html Product link]
|
|[[File:Satnogs helical v1.jpg|left|frameless|100x100px]]

==== Helical Antennas ====
UHF circularly polarized directional antenna

Estimated cost: TBD

A less common type that are circularly polarized. The antenna looks a bit like a corkscrew and can be either LHCP (Left hand circular polarisation) or RHCP (right hand circular polarisation).

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

* v4 [https://satnogs.dozuki.com/Guide/Helical+Antenna+v4/11 Assembly instructions]
* [https://ohai.satnogs.org/project/helical-antenna-v5/ v5 Assembly instructions]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical Source code for SatNOGS helical antenna designs are here.]
|-
|[[File:Arrow Portable Yagi.jpg|left|frameless|100x100px]]

==== Arrow Dual-band portable yagi ====
VHF/UHF portable yagi

Estimated cost: $83-$149

Some SatNOGS stations using this antenna:

TBD

* [http://www.arrowantennas.com/arrowii/146-437.html Product price/ordering link]
* [http://www.arrowantennas.com/sub/arrowiiyagi.html Product details link]
|
|
|-
|[[File:Elk Log Periodic.jpg|left|frameless|112x112px]]

==== Elk Log Periodic ====
VHF/UHF portable yagi

Estimated cost: $130-$163

Some SatNOGS stations using this antenna:

TBD

* [https://elkantennas.com/product/dual-band-2m440l5-log-periodic-antenna/ Product link]
|
|
|}


A radome design is available from SatNOGS. This will protect the ground station from the elements in all but extra ordinary conditions. The design can be found [https://gitlab.com/librespacefoundation/satnogs/satnogs-radome/blob/master/satnogs-radome-v1-bom.ods here] and construction guide [https://ohai.satnogs.org/project/satnogs-radome-v1/hardware/ here]. 
[[Category:Antennas]]
__NOEDITSECTION__
[[Category:Omnidirectional Antennas]]
[[Category:Directional Antennas]]

Get In Touch

2019-02-02T20:05:25Z

Cshields:

__NOTOC__
== Ask questions on the forum==

You can ask questions about SatNOGS at https://community.libre.space/, our web forum.

== Chat with us on our Matrix/IRC room==
You can chat with the SatNOGS community at https://riot.im/app/#/room/#satnogs:matrix.org, or on IRC at #satnogs on [https://freenode.net/ Freenode]. Keep in mind that due to timezone differences, you might have to wait a little while for a response.

== File an issue on our Gitlab repositories==

If you've found a bug in the SatNOGS software, or have a feature you'd like to see added, you can file an issue in the appropriate [https://gitlab.com/librespacefoundation/satnogs/ Gitlab repository]. (If you're not sure where it should go, feel free to ask on [https://community.libre.space the web forum] or [https://riot.im/app/#/room/#satnogs:matrix.org the Matrix chat room].

== Check our status page==

The status of the various SatNOGS components (network, db and so on) can be found at https://status.libre.space/.

__NOEDITSECTION__

Get In Touch

2019-02-02T20:04:58Z

Cshields:

__NOTOC__
== Ask questions on the forum==

You can ask questions about SatNOGS at https://community.libre.space/, our web forum.

==Chat with us on our Matrix/IRC room==
You can chat with the SatNOGS community at https://riot.im/app/#/room/#satnogs:matrix.org, or on IRC at #satnogs on [https://freenode.net/ Freenode]. Keep in mind that due to timezone differences, you might have to wait a little while for a response.

== File an issue on our Gitlab repositories==

If you've found a bug in the SatNOGS software, or have a feature you'd like to see added, you can file an issue in the appropriate [https://gitlab.com/librespacefoundation/satnogs/ Gitlab repository]. (If you're not sure where it should go, feel free to ask on [https://community.libre.space the web forum] or [https://riot.im/app/#/room/#satnogs:matrix.org the Matrix chat room].

== Check our status page==

The status of the various SatNOGS components (network, db and so on) can be found at https://status.libre.space/.

__NOEDITSECTION__

Antennas

2019-02-02T20:03:32Z

Cshields:

__NOTOC__
The type of antenna largely depends on the type of ground station. A no rotator ground station will benefit from a different type of antenna (omnidirectional) than a rotator based ground station (directional). The two different approaches are explored below. In addition to the choice of antenna the choice of location for the ground station will have an effect on the quality of observations.

==Non-Rotator Ground Station (Omnidirectional)==
This type of ground station will require an antenna that will give a broad coverage from its fixed position. It is therefore not just the antenna that needs to be considered but also the proximity of buildings, geography or metallic structures that might be in the path of a line of sight between the ground station and satellite.Typical ground stations have had success with simple wire antennas that can be commercially bought or made at home. Colinear or ‘white stick’ antennas are vertically polarised omnidirectional antennas. These have anecdotally been used for successful satellite work but should be avoided. The following are considered suitable choices:'''It is highly recommended that you use a mast-mounted Low-Noise Amplifier (LNA) with these antennas.'''
{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Antennas ===
!
! style="width: 49%" |
=== Homebrew Antennas ===
|-
|[[File:WiMo TA-1.gif|left|frameless|160x160px]]

==== WiMo TA-1 ====
VHF Turnstile

Estimated cost: 90€

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/141/ 141 - balcony-only-east-passes]

[https://network.satnogs.org/stations/33/ 33 - G7KSE]

[https://network.satnogs.org/stations/129/ 129 - Chabot Space And Science Center]

* [https://www.wimo.com/scanner-antennas_e.html#004 Product link]
* [http://oz9aec.net/antennas/air-tests-wimo-ta-1-turnstile-antenna OZ9AEC Review]
|
|[[File:VHF Turnstile.jpg|left|frameless|100x100px]]

==== Turnstile ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/13/ 13 - OZ9AEC-VHF1]

[https://network.satnogs.org/stations/7/ 7 - Stony]

[https://network.satnogs.org/stations/16/ 16 - VK5QI-70CM]

* SatNOGS Turnstile Antenna (TBD)
* [https://www.vk4adc.com/web/vhfuhf-projects/26-multiband-ants/156-turnstile-vhf-uhf-fds VK4ADC instructions for VHF and UHF Turnstile antennas]
* [https://www.aeronetworks.ca/2017/12/amateur-satcom-rx-antenna-for-2-meter.html Six-element tape-measure VHF Turnstile with modeled patterns (could be used as directional) by Herman Oosthuysen]
|-
|[[File:M2 Eggbeaters.png|left|frameless|100x100px]]

==== M2 Eggbeater ====
VHF / UHF Eggbeater Antennas

Estimated cost: $304 (VHF), $280 (UHF), $573 (combo)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/50/ 50 - N5CNB-UHF]

[https://network.satnogs.org/stations/77/ 77 - N5CNB-VHF]

* [https://www.m2inc.com/FGEB144RK2M Product link for VHF]
* [https://www.m2inc.com/FGEB432RK70CM Product link for UHF]
* [https://www.m2inc.com/FGSATPACK1 Product link for combination package]
|
|[[File:VHF EZ-Lindenblad.png|left|frameless|112x112px]]

==== Lindenblad ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/12/ 12 - W2BFJ]

[https://network.satnogs.org/stations/98/ 98 - Grove-UHF-01]

[https://network.satnogs.org/stations/442/ 442 - DL1UNX-FFB VHF]

* [https://www.amsat.org/wordpress/wp-content/uploads/2015/08/An-EZ-Lindenblad-Antenna-for-2-Meters2.pdf AA2TX EZ-Lindenblad design can be found at this AMSAT PDF]
* [https://www.qsl.net/py4zbz/DCA.pdf KD6JDJ instructions can be found at this QST PDF]
* [https://www.amsat.org/articles/w6shp/lindy.html W6SHP instructions for VHF and UHF Lindenblad]
|-
|[[File:Winkler Turnstile.jpg|left|frameless|100x100px]]

==== Winkler Turnstile ====
VHF/UHF Turnstile Antennas

Estimated cost: 40€ (VHF), 30€ (UHF)

Some SatNOGS stations using this antenna:

TBD

* [http://www.winklerantennenbau.de/sonst.htm Pricing page]
* [http://www.winklerantennenbau.de/kreuz137.htm Product link for VHF]
* [http://www.winklerantennenbau.de/kreuz446.htm Product link for UHF]
|
|[[File:UHF Paralindy.jpg|left|frameless|100x100px]]

==== UHF Parasitic Lindenblad ====
Estimated cost: $15 (with access to a 3D printer)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/300/ 300 - KB9JHU-Experimental]

[https://network.satnogs.org/stations/32/ 32 - SV1QZZ - UHF #2]

[https://network.satnogs.org/stations/187/ 187 - K3LRD UHF Lindenblad]

* [https://www.amsat.org/wordpress/wp-content/uploads/2014/01/70ParaLindy.pdf Instructions can be found at this AMSAT PDF by AA2TX]
|-
|
|
|[[File:Quadrifilar Antennas.png|left|frameless|100x100px]]

==== Quadrifilar Helix Antenna (QFH) ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/272/ 272 - K3LRD VHF QFH]

[https://network.satnogs.org/stations/255/ 255 - EA5BZ - Elche]

[https://network.satnogs.org/stations/183/ 183 - SPUTNIX-R2ANF-VHF/UHF-stationary]

* [http://www.g4ilo.com/qfh.html G4ILO QFH Instructions]
* [https://www.aeronetworks.ca/2017/12/parasitic-quadrifilar-helical-antenna.html VHF Model/patterns for QFH by Herman Oosthuysen]
* [http://jcoppens.com/ant/qfh/calc.en.php QFH Calculator by ON6JC/LW3HAZ]
* [https://community.libre.space/t/an-easy-3d-printed-quadrifilar-helix-antenna/1487 3D Printed UHF QFH Antenna by surligas]
|-
|
|
|[[File:Vhf moxon turnstile.png|left|frameless|100x100px]]

==== "Turnstiled" Moxon ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

TBD

* [https://sat.fg8oj.com/images/VHFUHFSatelite.pdf Instructions can be found at this QST article by W4RNL]
|}


==Rotator Ground Station==
A rotator based ground station is able to make use of directional antennas. These will have a directional gain, meaning that you will need to point them in the direction of the satellite but the signal you receive will be stronger and for longer. They will allow much lower to the horizon passes to be received and more successful observations. These are not complex antennas but the choice will depend on the type of satellite and there are variations on the main types: yagi, helical and quad.

{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Antennas ===
!
! style="width: 49%" |
=== Homebrew Antennas ===
|-
|[[File:M2 Leopack.png|left|frameless|100x100px]]

==== M2 Circularly Polarized Yagis ====
VHF/UHF Cross-element Yagi

Estimated cost: $296 (UHF), $296 (VHF), $638 (Combo kit)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/2/ 2 - KB9JHU]

[https://network.satnogs.org/stations/109/ 109 - EA6WQ - Tomas Orzaez]

[https://network.satnogs.org/stations/25/ 25 - N7IPY]

* [https://www.m2inc.com/FG2MCP8A Product link - VHF]
* [https://www.m2inc.com/FG436CP16 Product link - UHF]
* [https://www.m2inc.com/FGLEOPACK Product link - Combo kit]
|
|[[File:Cross element UHF yagi.jpg|left|frameless|133x133px]]

==== Yagi Antennas, Cross-element yagi antennas ====
VHF/UHF directional antenna

Estimated cost: TBD

A common type of antenna that is either horizontally or vertically polarised. Simple to construct and suitable for a large number of satellites.

Some SatNOGS stations using this antenna:

TBD

* TBD: Assembly instructions
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Yagi Source code for SatNOGS yagi antenna designs are here].
|-
|[[File:Wimo xquad vhf.jpg|left|frameless|100x100px]]

==== WiMo X Quad ====
VHF/UHF Cross-element Quad

Estimated cost: 149€ (VHF), 149€ (UHF)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

[https://network.satnogs.org/stations/49/ 49 - OZ7SAT]

[https://network.satnogs.org/stations/232/ 232 - VK5QI-AZ/EL]

* [https://www.wimo.com/xquad-antennas_e.html Product link]
|
|[[File:Satnogs helical v1.jpg|left|frameless|100x100px]]

==== Helical Antennas ====
UHF circularly polarized directional antenna

Estimated cost: TBD

A less common type that are circularly polarized. The antenna looks a bit like a corkscrew and can be either LHCP (Left hand circular polarisation) or RHCP (right hand circular polarisation).

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

* v4 [https://satnogs.dozuki.com/Guide/Helical+Antenna+v4/11 Assembly instructions]
* [https://ohai.satnogs.org/project/helical-antenna-v5/ v5 Assembly instructions]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical Source code for SatNOGS helical antenna designs are here.]
|-
|[[File:Arrow Portable Yagi.jpg|left|frameless|100x100px]]

==== Arrow Dual-band portable yagi ====
VHF/UHF portable yagi

Estimated cost: $83-$149

Some SatNOGS stations using this antenna:

TBD

* [http://www.arrowantennas.com/arrowii/146-437.html Product price/ordering link]
* [http://www.arrowantennas.com/sub/arrowiiyagi.html Product details link]
|
|
|-
|[[File:Elk Log Periodic.jpg|left|frameless|112x112px]]

==== Elk Log Periodic ====
VHF/UHF portable yagi

Estimated cost: $130-$163

Some SatNOGS stations using this antenna:

TBD

* [https://elkantennas.com/product/dual-band-2m440l5-log-periodic-antenna/ Product link]
|
|
|}


A radome design is available from SatNOGS. This will protect the ground station from the elements in all but extra ordinary conditions. The design can be found [https://gitlab.com/librespacefoundation/satnogs/satnogs-radome/blob/master/satnogs-radome-v1-bom.ods here] and construction guide [https://ohai.satnogs.org/project/satnogs-radome-v1/hardware/ here]. 
[[Category:Antennas]]
__NOEDITSECTION__

Dashboard

2019-02-02T19:41:40Z

Cshields:

__NOTOC__

=== https://dashboard.satnogs.org ===
We are using [https://www.influxdata.com/ InfluxDB] and [https://grafana.com/ Grafana] for our telemetry dashboards. [https://www.influxdata.com/ InfluxDB] is a time-series database designed to be efficient for time-series data like the telemetry we collect in SatNOGS.

I'm going to drop a few things to get the reader going on telemetry dashboard in SatNOGS, and expect that the reader also reference the [https://docs.grafana.org Grafana documentation] for more details on building dashboards.

This doc also assumes you have an account to edit dashboards. You can generate an account by clicking the Sign In link.

Today there is a top level folder hierarchy designed as such:

* Telemetry (where telemetry dashboards should be stored, publicly accessible)
* General (for stats about our data collection itself, meta-dashboards, publicly accessible)
* Scratchpad (a playground for making grafana dashboards and testing functionality, not publicly accessible)

=== Creating a dashboard ===
Clicking the + icon will allow you to create a new dashboard. When you do this a new panel is started for you. This panel can be resized at the lower-right corner, and moved around by dragging once more panels are added.

Now - before you get started please note that '''you have to save your changes!! They do not save automatically!'''

Click "Graph" to make this a graph panel. Click the graph title and then Edit to edit this specific graph.

[[File:Grafana panel edit.png|frameless|600x600px]]

A few things you will want to edit:

==== General ====

Give it a meaningful title, of course. Description is not required, but offers a popup of more details to the user if you want to add more details.

==== Metrics ====
Select the metric by clicking "select measurement". What you will see here are the names of all measurements available which are the NORAD ID of the satellite in the database. You can type part of the NORAD ID to filter.

[[File:Grafana select measurement.png|frameless|600x600px]]

In most cases you will want to leave the WHERE clause blank, but from here you can also filter data based on the tag that the data has (such as filtering on a specific observer).

[[File:Grafana filter tag.png|frameless|600x600px]]

Next, select the telemetry field you are looking to graph by clicking on field("value"). If there is data in the database that has been properly decoded you should see the relevant fields for that satellite displayed here:

[[File:Grafana field value.png|frameless|600x600px]]

See any data in your graph yet? If not, change your timeframe in the upper-right corner to something like "last 30 days" as the default of "last 6 hours" may not have data decoded (especially true for our dev instance, where we have no steady stream of recent data)

SELECT: mean() (default), distinct(), and last() are likely to be the most useful for us. Keep in mind that there is the possibility for multiple data points from multiple stations and observations, some overlapping. InfluxDB handles this for us. The timeframe selected is also taken into account in these measurements. This line is where you may need to add math to make the number human-readable. For instance, for CubeBel-1, to calculate voltage we have to take (Measured value) / 4096×2.5×3.75, which looks like this:

[[File:Grafana math.png|frameless|900x900px]]

GROUP BY: you may wish to change the fill value here, there are a number of options. Be careful as this may be misleading to users if we are dealing with very sparse data sets, as this option will fill in any gaps, yet "none" or "linear" may be options to use to make the graphs look better.

You can also add multiple queries to the same graph with the Add Query button at the bottom

==== Axes ====

You may want to change the Unit here, as "Short" may be undesired for certain figures, and "None" would be better.

==== Display ====

If you are doing a line graph and do not want the shading below the line, change the "Fill" value here to 0.

=== Graph Settings ===

In the gear icon for a graph are the graph settings. Some things to change here:

* Name
* Folder (see the hierarchy above)
* "Now delay now-" - I suggest 30d (the last 30d) as without it the default is 6 hours

"Save As" will allow you to make a copy of a graph and hack on it.

Dashboard

2019-02-02T19:41:15Z

Cshields:

__NOTOC__

=== https://dashboard.satnogs.org ===
We are using [https://www.influxdata.com/ InfluxDB] and [https://grafana.com/ Grafana] for our telemetry dashboards. [https://www.influxdata.com/ InfluxDB] is a time-series database designed to be efficient for time-series data like the telemetry we collect in SatNOGS.

I'm going to drop a few things to get the reader going on telemetry dashboard in SatNOGS, and expect that the reader also reference the [https://docs.grafana.org Grafana documentation] for more details on building dashboards.

This doc also assumes you have an account to edit dashboards. You can generate an account by clicking the Sign In link.

Today there is a top level folder hierarchy designed as such:

* Telemetry (where telemetry dashboards should be stored, publicly accessible)
* General (for stats about our data collection itself, meta-dashboards, publicly accessible)
* Scratchpad (a playground for making grafana dashboards and testing functionality, not publicly accessible)

=== Creating a dashboard ===
Clicking the + icon will allow you to create a new dashboard. When you do this a new panel is started for you. This panel can be resized at the lower-right corner, and moved around by dragging once more panels are added.

Now - before you get started please note that '''you have to save your changes!! They do not save automatically!'''

Click "Graph" to make this a graph panel. Click the graph title and then Edit to edit this specific graph.

[[File:Grafana panel edit.png|frameless|600x600px]]

A few things you will want to edit:

==== General ====

Give it a meaningful title, of course. Description is not required, but offers a popup of more details to the user if you want to add more details.

==== Metrics ====
Select the metric by clicking "select measurement". What you will see here are the names of all measurements available which are the NORAD ID of the satellite in the database. You can type part of the NORAD ID to filter.

[[File:Grafana select measurement.png|frameless|600x600px]]

In most cases you will want to leave the WHERE clause blank, but from here you can also filter data based on the tag that the data has (such as filtering on a specific observer).

[[File:Grafana filter tag.png|frameless|600x600px]]

Next, select the telemetry field you are looking to graph by clicking on field("value"). If there is data in the database that has been properly decoded you should see the relevant fields for that satellite displayed here:

[[File:Grafana field value.png|frameless|600x600px]]

See any data in your graph yet? If not, change your timeframe in the upper-right corner to something like "last 30 days" as the default of "last 6 hours" may not have data decoded (especially true for our dev instance, where we have no steady stream of recent data)

SELECT: mean() (default), distinct(), and last() are likely to be the most useful for us. Keep in mind that there is the possibility for multiple data points from multiple stations and observations, some overlapping. InfluxDB handles this for us. The timeframe selected is also taken into account in these measurements. This line is where you may need to add math to make the number human-readable. For instance, for CubeBel-1, to calculate voltage we have to take (Measured value) / 4096×2.5×3.75, which looks like this:

[[File:Grafana math.png|frameless|900x900px]]

GROUP BY: you may wish to change the fill value here, there are a number of options. Be careful as this may be misleading to users if we are dealing with very sparse data sets, as this option will fill in any gaps, yet "none" or "linear" may be options to use to make the graphs look better.

You can also add multiple queries to the same graph with the Add Query button at the bottom

==== Axes ====

You may want to change the Unit here, as "Short" may be undesired for certain figures, and "None" would be better.

==== Display ====

If you are doing a line graph and do not want the shading below the line, change the "Fill" value here to 0.

=== Graph Settings ===

In the gear icon for a graph are the graph settings. Some things to change here:

* Name
* Folder (see the hierarchy above)
* "Now delay now-" - I suggest 30d (the last 30d) as without it the default is 6 hours

"Save As" will allow you to make a copy of a graph and hack on it.

Dashboard

2019-02-02T19:40:21Z

Cshields: major revamp, new screenshots

=== https://dashboard.satnogs.org ===
We are using [https://www.influxdata.com/ InfluxDB] and [https://grafana.com/ Grafana] for our telemetry dashboards. [https://www.influxdata.com/ InfluxDB] is a time-series database designed to be efficient for time-series data like the telemetry we collect in SatNOGS.

I'm going to drop a few things to get the reader going on telemetry dashboard in SatNOGS, and expect that the reader also reference the [https://docs.grafana.org Grafana documentation] for more details on building dashboards.

This doc also assumes you have an account to edit dashboards. You can generate an account by clicking the Sign In link.

Today there is a top level folder hierarchy designed as such:

* Telemetry (where telemetry dashboards should be stored, publicly accessible)
* General (for stats about our data collection itself, meta-dashboards, publicly accessible)
* Scratchpad (a playground for making grafana dashboards and testing functionality, not publicly accessible)

=== Creating a dashboard ===
Clicking the + icon will allow you to create a new dashboard. When you do this a new panel is started for you. This panel can be resized at the lower-right corner, and moved around by dragging once more panels are added.

Now - before you get started please note that '''you have to save your changes!! They do not save automatically!'''

Click "Graph" to make this a graph panel. Click the graph title and then Edit to edit this specific graph.

[[File:Grafana panel edit.png|frameless|600x600px]]

A few things you will want to edit:

==== General ====

Give it a meaningful title, of course. Description is not required, but offers a popup of more details to the user if you want to add more details.

==== Metrics ====
Select the metric by clicking "select measurement". What you will see here are the names of all measurements available which are the NORAD ID of the satellite in the database. You can type part of the NORAD ID to filter.

[[File:Grafana select measurement.png|frameless|600x600px]]

In most cases you will want to leave the WHERE clause blank, but from here you can also filter data based on the tag that the data has (such as filtering on a specific observer).

[[File:Grafana filter tag.png|frameless|600x600px]]

Next, select the telemetry field you are looking to graph by clicking on field("value"). If there is data in the database that has been properly decoded you should see the relevant fields for that satellite displayed here:

[[File:Grafana field value.png|frameless|600x600px]]

See any data in your graph yet? If not, change your timeframe in the upper-right corner to something like "last 30 days" as the default of "last 6 hours" may not have data decoded (especially true for our dev instance, where we have no steady stream of recent data)

SELECT: mean() (default), distinct(), and last() are likely to be the most useful for us. Keep in mind that there is the possibility for multiple data points from multiple stations and observations, some overlapping. InfluxDB handles this for us. The timeframe selected is also taken into account in these measurements. This line is where you may need to add math to make the number human-readable. For instance, for CubeBel-1, to calculate voltage we have to take (Measured value) / 4096×2.5×3.75, which looks like this:

[[File:Grafana math.png|frameless|900x900px]]

GROUP BY: you may wish to change the fill value here, there are a number of options. Be careful as this may be misleading to users if we are dealing with very sparse data sets, as this option will fill in any gaps, yet "none" or "linear" may be options to use to make the graphs look better.

You can also add multiple queries to the same graph with the Add Query button at the bottom

==== Axes ====

You may want to change the Unit here, as "Short" may be undesired for certain figures, and "None" would be better.

==== Display ====

If you are doing a line graph and do not want the shading below the line, change the "Fill" value here to 0.

=== Graph Settings ===

In the gear icon for a graph are the graph settings. Some things to change here:

* Name
* Folder (see the hierarchy above)
* "Now delay now-" - I suggest 30d (the last 30d) as without it the default is 6 hours

"Save As" will allow you to make a copy of a graph and hack on it.

File:Grafana math.png

2019-02-02T19:39:15Z

Cshields:

grafana math example

File:Grafana field value.png

2019-02-02T19:33:27Z

Cshields:

grafana field value

File:Grafana filter tag.png

2019-02-02T19:29:43Z

Cshields:

grafana filter tag

File:Grafana select measurement.png

2019-02-02T19:27:18Z

Cshields:

grafana select measurement

File:Grafana panel edit.png

2019-02-02T19:24:11Z

Cshields:

Grafana panel edit

Antennas

2019-02-02T19:09:41Z

Cshields:

__NOTOC__
The type of antenna largely depends on the type of ground station. A no rotator ground station will benefit from a different type of antenna (omnidirectional) than a rotator based ground station (directional). The two different approaches are explored below. In addition to the choice of antenna the choice of location for the ground station will have an effect on the quality of observations.

==Non-Rotator Ground Station (Omnidirectional)==
This type of ground station will require an antenna that will give a broad coverage from its fixed position. It is therefore not just the antenna that needs to be considered but also the proximity of buildings, geography or metallic structures that might be in the path of a line of sight between the ground station and satellite.Typical ground stations have had success with simple wire antennas that can be commercially bought or made at home. Colinear or ‘white stick’ antennas are vertically polarised omnidirectional antennas. These have anecdotally been used for successful satellite work but should be avoided. The following are considered suitable choices:'''It is highly recommended that you use a mast-mounted Low-Noise Amplifier (LNA) with these antennas.'''
{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Antennas ===
!
! style="width: 49%" |
=== Homebrew Antennas ===
|-
|[[File:WiMo TA-1.gif|left|frameless|160x160px]]

==== WiMo TA-1 ====
VHF Turnstile

Estimated cost: 90€

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/141/ 141 - balcony-only-east-passes]

[https://network.satnogs.org/stations/33/ 33 - G7KSE]

[https://network.satnogs.org/stations/129/ 129 - Chabot Space And Science Center]

* [https://www.wimo.com/scanner-antennas_e.html#004 Product link]
* [http://oz9aec.net/antennas/air-tests-wimo-ta-1-turnstile-antenna OZ9AEC Review]
|
|[[File:VHF Turnstile.jpg|left|frameless|100x100px]]

==== Turnstile ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/13/ 13 - OZ9AEC-VHF1]

[https://network.satnogs.org/stations/7/ 7 - Stony]

[https://network.satnogs.org/stations/16/ 16 - VK5QI-70CM]

* SatNOGS Turnstile Antenna (TBD)
* [https://www.vk4adc.com/web/vhfuhf-projects/26-multiband-ants/156-turnstile-vhf-uhf-fds VK4ADC instructions for VHF and UHF Turnstile antennas]
* [https://www.aeronetworks.ca/2017/12/amateur-satcom-rx-antenna-for-2-meter.html Six-element tape-measure VHF Turnstile with modeled patterns (could be used as directional) by Herman Oosthuysen]
|-
|[[File:M2 Eggbeaters.png|left|frameless|100x100px]]

==== M2 Eggbeater ====
VHF / UHF Eggbeater Antennas

Estimated cost: $304 (VHF), $280 (UHF), $573 (combo)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/50/ 50 - N5CNB-UHF]

[https://network.satnogs.org/stations/77/ 77 - N5CNB-VHF]

* [https://www.m2inc.com/FGEB144RK2M Product link for VHF]
* [https://www.m2inc.com/FGEB432RK70CM Product link for UHF]
* [https://www.m2inc.com/FGSATPACK1 Product link for combination package]
|
|[[File:VHF EZ-Lindenblad.png|left|frameless|112x112px]]

==== Lindenblad ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/12/ 12 - W2BFJ]

[https://network.satnogs.org/stations/98/ 98 - Grove-UHF-01]

[https://network.satnogs.org/stations/442/ 442 - DL1UNX-FFB VHF]

* [https://www.amsat.org/wordpress/wp-content/uploads/2015/08/An-EZ-Lindenblad-Antenna-for-2-Meters2.pdf AA2TX EZ-Lindenblad design can be found at this AMSAT PDF]
* [https://www.qsl.net/py4zbz/DCA.pdf KD6JDJ instructions can be found at this QST PDF]
* [https://www.amsat.org/articles/w6shp/lindy.html W6SHP instructions for VHF and UHF Lindenblad]
|-
|[[File:Winkler Turnstile.jpg|left|frameless|100x100px]]

==== Winkler Turnstile ====
VHF/UHF Turnstile Antennas

Estimated cost: 40€ (VHF), 30€ (UHF)

Some SatNOGS stations using this antenna:

TBD

* [http://www.winklerantennenbau.de/sonst.htm Pricing page]
* [http://www.winklerantennenbau.de/kreuz137.htm Product link for VHF]
* [http://www.winklerantennenbau.de/kreuz446.htm Product link for UHF]
|
|[[File:UHF Paralindy.jpg|left|frameless|100x100px]]

==== UHF Parasitic Lindenblad ====
Estimated cost: $15 (with access to a 3D printer)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/300/ 300 - KB9JHU-Experimental]

[https://network.satnogs.org/stations/32/ 32 - SV1QZZ - UHF #2]

[https://network.satnogs.org/stations/187/ 187 - K3LRD UHF Lindenblad]

* [https://www.amsat.org/wordpress/wp-content/uploads/2014/01/70ParaLindy.pdf Instructions can be found at this AMSAT PDF by AA2TX]
|-
|
|
|[[File:Quadrifilar Antennas.png|left|frameless|100x100px]]

==== Quadrifilar Helix Antenna (QFH) ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/272/ 272 - K3LRD VHF QFH]

[https://network.satnogs.org/stations/255/ 255 - EA5BZ - Elche]

[https://network.satnogs.org/stations/183/ 183 - SPUTNIX-R2ANF-VHF/UHF-stationary]

* [http://www.g4ilo.com/qfh.html G4ILO QFH Instructions]
* [https://www.aeronetworks.ca/2017/12/parasitic-quadrifilar-helical-antenna.html VHF Model/patterns for QFH by Herman Oosthuysen]
* [http://jcoppens.com/ant/qfh/calc.en.php QFH Calculator by ON6JC/LW3HAZ]
* [https://community.libre.space/t/an-easy-3d-printed-quadrifilar-helix-antenna/1487 3D Printed UHF QFH Antenna by surligas]
|-
|
|
|[[File:Vhf moxon turnstile.png|left|frameless|100x100px]]

==== "Turnstiled" Moxon ====
Estimated cost: TBD

Some SatNOGS stations using this antenna:

TBD

* [https://sat.fg8oj.com/images/VHFUHFSatelite.pdf Instructions can be found at this QST article by W4RNL]
|}


==Rotator Ground Station==
A rotator based ground station is able to make use of directional antennas. These will have a directional gain, meaning that you will need to point them in the direction of the satellite but the signal you receive will be stronger and for longer. They will allow much lower to the horizon passes to be received and more successful observations. These are not complex antennas but the choice will depend on the type of satellite and there are variations on the main types: yagi, helical and quad.

{| class="wikitable" style="width: 100%;"
! style="width: 49%" |
=== Commercial Antennas ===
!
! style="width: 49%" |
=== Homebrew Antennas ===
|-
|[[File:M2 Leopack.png|left|frameless|100x100px]]

==== M2 Circularly Polarized Yagis ====
VHF/UHF Cross-element Yagi

Estimated cost: $296 (UHF), $296 (VHF), $638 (Combo kit)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/2/ 2 - KB9JHU]

[https://network.satnogs.org/stations/109/ 109 - EA6WQ - Tomas Orzaez]

[https://network.satnogs.org/stations/25/ 25 - N7IPY]

* [https://www.m2inc.com/FG2MCP8A Product link - VHF]
* [https://www.m2inc.com/FG436CP16 Product link - UHF]
* [https://www.m2inc.com/FGLEOPACK Product link - Combo kit]
|
|[[File:Cross element UHF yagi.jpg|left|frameless|133x133px]]

==== Yagi Antennas, Cross-element yagi antennas ====
VHF/UHF directional antenna

Estimated cost: TBD

A common type of antenna that is either horizontally or vertically polarised. Simple to construct and suitable for a large number of satellites.

Some SatNOGS stations using this antenna:

TBD

* TBD: Assembly instructions
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Yagi Source code for SatNOGS yagi antenna designs are here].
|-
|[[File:Wimo xquad vhf.jpg|left|frameless|100x100px]]

==== WiMo X Quad ====
VHF/UHF Cross-element Quad

Estimated cost: 149€ (VHF), 149€ (UHF)

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

[https://network.satnogs.org/stations/49/ 49 - OZ7SAT]

[https://network.satnogs.org/stations/232/ 232 - VK5QI-AZ/EL]

* [https://www.wimo.com/xquad-antennas_e.html Product link]
|
|[[File:Satnogs helical v1.jpg|left|frameless|100x100px]]

==== Helical Antennas ====
UHF circularly polarized directional antenna

Estimated cost: TBD

A less common type that are circularly polarized. The antenna looks a bit like a corkscrew and can be either LHCP (Left hand circular polarisation) or RHCP (right hand circular polarisation).

Some SatNOGS stations using this antenna:

[https://network.satnogs.org/stations/6/ 6 - Apomahon]

* v4 [https://satnogs.dozuki.com/Guide/Helical+Antenna+v4/11 Assembly instructions]
* [https://ohai.satnogs.org/project/helical-antenna-v5/ v5 Assembly instructions]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical Source code for SatNOGS helical antenna designs are here.]
|-
|[[File:Arrow Portable Yagi.jpg|left|frameless|100x100px]]

==== Arrow Dual-band portable yagi ====
VHF/UHF portable yagi

Estimated cost: $83-$149

Some SatNOGS stations using this antenna:

TBD

* [http://www.arrowantennas.com/arrowii/146-437.html Product price/ordering link]
* [http://www.arrowantennas.com/sub/arrowiiyagi.html Product details link]
|
|
|-
|[[File:Elk Log Periodic.jpg|left|frameless|112x112px]]

==== Elk Log Periodic ====
VHF/UHF portable yagi

Estimated cost: $130-$163

Some SatNOGS stations using this antenna:

TBD

* [https://elkantennas.com/product/dual-band-2m440l5-log-periodic-antenna/ Product link]
|
|
|}


A radome design is available from SatNOGS. This will protect the ground station from the elements in all but extra ordinary conditions. The design can be found [https://gitlab.com/librespacefoundation/satnogs/satnogs-radome/blob/master/satnogs-radome-v1-bom.ods here] and construction guide [https://ohai.satnogs.org/project/satnogs-radome-v1/hardware/ here].