SatNOGS Wiki - User contributions [en]

Satellite services

2019-07-02T05:49:43Z

Ppapadeas: Created page with "Aeronautical Amateur Broadcasting Earth Exploration Fixed Inter-satellite Maritime Meteorological Mobile Radiolocation Radionavigational Space Operation Space Research Standar..."

Aeronautical
Amateur
Broadcasting
Earth Exploration
Fixed
Inter-satellite
Maritime
Meteorological
Mobile
Radiolocation
Radionavigational
Space Operation
Space Research
Standard Frequency and Time Signal
Unknown

SPF5189 LNA measurements

2019-04-24T15:52:57Z

Ppapadeas: Ppapadeas moved page SPF1589 LNA measurements to SPF5189 LNA measurements

If you want to improve your receiving station performances, you could consider to add an LNA near your antenna.
One of the cheapeset LNA available on the market is SPF5189. It's available already mounted on a PCB, shielded and connectorized, as in the figure below.

[[File:Foto.jpg|center]]

I bought one board for few euros on ebay. It arrived in a pair of weeks, then I measured it on a Vector Network Analyzer, in order to compare the real gain with the datasheet.

Once the LNA has been powered at 5V, the current absorption is 90mA, perfectly aligned with the datasheet range.

Here below, the S21, S11 and S22 plots are reported between 50MHz and 3GHz (the LNA reaches 4GHz but the VNA not).

I placed these 4 markers: 144MHz, 435MHz, 1GHz, 2GHz .

[[File:S11.jpg|600px|center]]
[[File:S21.jpg|600px|center]]
[[File:S22.jpg|600px|center]]

When I downloaded the datahseet, I saw that the SPF5189Z has two possible configurations:

- Optimized matching at 900MHz
- Optimized matching at 1900MHz

From ebay description and board P/N, it’s not possible to understand the frequency optimization.

Here below, I reported a comparison the datasheet (green line) and the measurement (red line) data, for both configurations. The frequency range of the datasheet is smaller than my measurements, sto the comparison is only on the datasheet frequencies and not wide-band.

[[File:900MHz_measured_vs_datasheet.png|600px|center]]

[[File:1900MHz_measured_vs_datasheet.png|600px|center]]

The gain seems to be 1dB less than the datasheet on both configurations, while the input matching shows better results on 900MHz range.

At the end, the LNA is quite wide-band and is a compromise between the 900MHz and 1900MHz configurations.

SPF1589 LNA measurements

2019-04-24T15:52:57Z

Ppapadeas: Ppapadeas moved page SPF1589 LNA measurements to SPF5189 LNA measurements

#REDIRECT [[SPF5189 LNA measurements]]

Omnidirectional Station How To

2019-02-14T08:22:46Z

Ppapadeas:

[[File:Omnidirectional VHF Turnstile Antenna.jpg|alt=VHF Turnstile Antenna|thumb|VHF Turnstile antenna, [https://network.satnogs.org/stations/23/ SatNOGS Station 23]]]
This How-To is written to get you quickly receiving satellite data with an Omnidirectional antenna (an antenna that does not move).

== Prerequisites/Background ==
I'm assuming that you are a bit familiar with amateur radio, or linux in general, or you already have a Raspberry Pi.

=== Expectation Management ===
First off, I'd like to set some expectations around a SatNOGs station with an omnidirectional antenna. Yes, you will be able to hear satellites, Morse code beacons, maybe even some voice contacts on a FM transponder. But for CubeSats with 1 watt transmitters at 9600 baud, it's going to be really difficult to actually decode any data with an omni antenna. You'll definitely see squiggly lines on the waterfall plot, but demodulating the signal and extracting satellite telemetry is going to be pretty difficult.

The only way to get more signal is a better antenna. And a better antenna with more gain is going to be more directional, which means you will need a way to point that antenna at the satellite, and this How-To just got a lot more complicated. So we're not going there.

A better preamp helps a bit, see the LNA section below.

=== Hardware Required ===
This is a list of the hardware for indoor/testing purposes:
* Raspberry Pi
** Power supply + cable (see note below)
** Up to 16 GB Micro SD card
** Ethernet cable
* RTL SDR Blog v3 dongle
* Various short lengths of coax
* Preamp/LNA - Or not if your coax is short, see LNA section below
* Omnidirectional antenna - just a dual mag-mount on a cookie sheet will work OK for stronger satellites

== Setting up the Raspberry Pi ==
I chose the [https://www.raspberrypi.org/products/raspberry-pi-3-model-b/ Raspberry Pi 3 Model B] for my station.

=== Downloading/Writing the SD image ===
The SatNOGs team has done a great job creating a Raspbian image with all the required software. Simply navigate over to the [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/tags latest tag on Gitlab], and click on the "Zipped image" link under the latest tag. It's about 650 MBytes.

For linux:
# Unzip the downloaded file: '''unzip image_2018-08-03-Raspbian-SatNOGS-lite.zip'''
# Figure out which device is the SD card. SD cards are usually start with mmcblk. '''sudo lsblk'''
# Write the image. This will take a while. Make sure you don't overwrite your host OS: '''sudo dd if=2018-08-03-Raspbian-SatNOGS-lite.img of=/dev/mmcblk0'''

=== Power notes ===
Thinking I could save a few bucks, I used a no-name generic 2.4 amp "tablet" USB power supply I got as a freebie, and a micro-USB cable I use for charging my phone. What a mistake! The Micro-USB cable wire gauge was too small, so there was too much voltage drop on the cable, so the Raspberry Pi reported power problems every time it was doing anything.

Power problems are indicated by either a lightning bolt in the upper right of the monitor, or the red power LED flashes on the board itself. If The Raspberry Pi processor itself is pretty forgiving of power droops because it runs at 3.3 volts. But the 5v USB ports are directly tied to input power, so undervoltage conditions will cause problems for USB devices, such as the RTL SDR dongle.

== Software Configuration ==

=== Creating a SatNOGs Network account ===
There are several different websites to be aware of and sign in to. As of 12/2018, most of our websites use a unified login provided by Auth0, so when you create an account on one of these sites it will work across the others as well:
* Required: [https://network.satnogs.org/ Network]: for registering your station and adding data to the network.
* Recommended: [https://community.libre.space Forums]: for asking questions.
* Optional: [https://db.satnogs.org/ Database]: Only if you want to add satellites/modes. Not necessary for receiving satellite data.

=== Registering the station ===
Log in to your Network account, and click the "+ Add Ground Station" button, or click [https://network.satnogs.org/stations/edit/ here] Fill out the short form, and your station will be added to the database. For "Antenna", pick something that encompasses the frequency range of your antenna. For wideband reception, use VHF Discone 26-1200 MHz.

The important info you'll need later on is the Station ID number, lat/lon/altitiude. I would also use a Minimum Horizon of 30 degrees or so, this will keep your station from allowing low-elevation passes to be scheduled. Make sure to keep the "Testing" flag checked, as this lets people know that your station isn't quite ready for real use.

=== Booting and Configuring Raspbian ===
After you have the image burned onto a Micro-SD card, boot it! I would recommend hooking up a keyboard and HDMI monitor, you can watch the boot process. If it doesn't boot at all, double check that you wrote the SatNOGs Raspbian image correctly.

After a successful boot, log in with username '''pi''' and password '''raspbian''':
# Change your password! '''passwd'''
# Update and upgrade raspbian strech: '''sudo apt update''' then '''sudo apt upgrade'''
# You'll probably update a lot of packages and get a new kernel, so reboot after this: '''sudo reboot'''
# Run '''sudo raspi-config''' to set up the base OS. ''Tab'' switches between the options and ''select''.
## 4 Localisation Options: I1 Change Locale: en_US.UTF-8 UTF-8
## 4 Localisation Options: I2 Change Timezone: None of the above: UTC
## 4 Localisation Options: I3 Change Keyboard Layout:
## 7 Advanced Options: A1 Expand Filesystem This will expand the ~2GB Micro-SD card partition to fill the entire SD card.
The Raspberry Pi needs to reboot to expand the filesystem, so do this now. It might take a while. '''sudo reboot''

==== Disabling WiFi and Bluetooth ====
To disable WiFi and Bluetooth, edit the /boot/config.txt file, and add the following lines at the bottom:
# Disable WiFi and bluetooth
dtoverlay=pi3-disable-wifi
dtoverlay=pi3-disable-bt

Then reboot again. To make sure that it worked, run '''ifconfig''' and make sure that ''wlan0'' isn't listed. I'm not sure how to tell if bluetooth is turned off.

==== Additional software ====
I like to install this additional software with '''sudo apt install bmon''' ...
* bmon - a graphical network usage analyzer.
* vnstat - keeps track of your bandwidth usage
* vim - the world's best text editor ;)
* irssi - a terminal IRC client, for chatting on the #satnogs IRC channel

If you can't tell by now, I'm always a big fan of rebooting. It certainly doesn't take that long... '''sudo reboot'''

=== Configuring the satnogs-client ===
Once you have the base Raspbian Strech OS installed, updated, and looking good, you can configure SatNOGs. Plug in your RTL SDR if you haven't already.

First thing to do is update the satnogs-setup program. Run '''sudo satnogs-setup'''. This will probably take a while, then '''Update''', which will also take a while. Per usual, after the update I like to reboot the raspberry pi just to make sure everything was updated and is actually running the new code.

==== Basic Configuration ====
Then the actual configuration of the station:
# Run '''sudo satnogs-setup''' again
# Basic Configuration:
## SATNOGS_API_TOKEN: After logging in to network.satnogs.org, this is in the upper right under "API Key"
## SATNOGS_RX_DEVICE: rtlsdr
## SATNOGS_STATION_ELEV: station elevation in meters
## SATNOGS_STATION_ID: The number of your station. Newer stations are high 200s.
## SATNOGS_STATION_LAT and LON: Latitude and Longitude in decimal degrees
## HAMLIB_UTILS_ROT_ENABLE: no
Then back to the main menu and ''Apply'' to save the configuration. Ansible will run, change some stuff, and probably take a while. If you want to quit, just keep pressing ''back'' to exit.

==== Setting the gain ====
The next step is to set the gain on the RTL SDR. You're looking for a total gain of about 25 dB. If you have a 25dB LNA, perfect, set the RTL SDR gain at zero. Otherwise, do the math. There are only a few gain options that the RTL SDR supports. The easiest way to see what the options are is to run the rtl_test command. Ctrl-C immediatly to stop:
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
pi@raspberrypi:~ $

Since I have a LNA with a gain of slightly under 20dB, I picked 8.7dB of gain for the RTL SDR. This value goes into the SATNOGS_RF_GAIN setting under Advanced settings in satnogs-setup.

=== Checking the setup ===
SatNOGs come with a built-in web server on port 5000. So just surf over to IP address of your Raspberry Pi on port 5000, and you should see a screen similar to this:

== Hardware Configuration ==
Basic hardware configuration is Antenna > Short coax > LNA > Coax > RTL SDR.

=== LNA ===
The way to measure the performance of an antenna is using a figure of merit called the Antenna gain-to-noise-temperature (G/T). It's a positive unitless number, higher the better.

G/T is comprised of antenna gain (in dB) on the top, and the system noise temperature (in Kelvins) on the bottom. There's a lot of somewhat-hard math involved, but here's the bottom line: to make your system perform better, you either need to increase the antenna gain or decrease the system noise temp. [https://en.wikipedia.org/wiki/Antenna_gain-to-noise-temperature Wikipedia]

Increasing the antenna gain is difficult, only because we decided on an omnidirectional antenna as the basis for this How-To. Omnidirectional antennas top out at maybe 7 dB gain or so, and that's just from pushing the radiation pattern up to the sky away from the ground. Any more gain than that and it's not an omni antenna; it's got a direction that the antenna needs to be pointed in. And we want to stay away from pointing antennas for now.

Reducing the system temperature is the the way forward then. The RTL-SDR dongle has a noise figure of [https://network.satnogs.org/stations/edit/ 6dB or so], depending on frequency, which is pretty horrible. But it turns out that the system noise temperature is largely determined by the first device in the receive chain. Since we can't change the antenna, adding a low-noise amplifier helps quite a bit. See this [https://www.youtube.com/watch?v=snifc_x_2sE youtube video] from Adam 9A4QV on how a LNA helps. (Also check out his other videos about the RTL SDR dongle, and SDR in general)

More info on noise and preamps:
* [https://en.wikipedia.org/wiki/Noise_temperature System noise from wikipedia], pretty high-level
* [https://www.rtl-sdr.com/tutorial-on-properly-positioning-a-preamp-lna-in-a-radio-system/ Where to put an LNA], from rtl-sdr.com

=== Antenna ===
For testing on the bench, pretty much any antenna will do. Or if you have a whip antenna already outside for repeater work, use that. As I mentioned before, I've successfully used a mag-mount antenna stuck to a cookie sheet, sitting inside my living room window.

Also, remember that some new low emissivity double-pane windows use metal films to keep heat inside. Unfortunately, this also attenuates pretty much all RF signals, see [https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5501855/ this article] for more background.

== Testing the station ==
[[File:Pass predictions.png|300px|right]]
Now that you have the hardware and software up and running, go ahead and schedule some passes. Navigate to your station page, and click on the Schedule button on the right side of some promising passes. The green and red bars beneath the satellite name is a quick visual indication of the number of Good and Bad passes on the network. Unfortunately, this data is not time-stamped at all, so a satellite that had a lot of Good observations a long time ago, but recently died, would still show as Green.

=== Rating an Observation ===
[[File:Rating.png|right]]
After each observatios, you should rate it. More information [https://wiki.satnogs.org/Operation#Rating_observations here], but the bottom line is rate the observation:
* '''Good''' if the satellite is seen in the waterfall at all. The satellite will be a straight line in the middle of the waterfall plot.
* '''Bad''' if the satellite is not seen.
* '''Failed''' if there was a problem with the station, such as a mis-configuration, or if the waterfall is missing or a solid color.

=== Calibrating frequency offset (PPM) ===
This is not super important for a new station.

== Next Steps ==
Now that you've got this station working on the bench, what's next?

For permanent mast-mounted installation, I would recommend adding:
* [https://www.adafruit.com/product/3785 PoE splitter] - Make sure to get one that actually conforms to the 48-volt IEEE 802.3af standard
* POE injector for powering station remotely - Again, get a real 48-volt IEEE 802.3af standard
* Large mast-mounted waterproof box
* Waterproof cord grips, both to keep out the rain but also spiders and critters
* Desiccant to keep the humidity down
* Mastic tape for weatherproofing antenna connectors
* Better omnidirectional antenna

=== Building a Box ===

== External links ==
* IQ3KU Omnidirectional station [https://www.i3vfj.net/SATNOGS/Satnogs_348_notes.pdf build write-up].
[[ Category:How-tos ]]
[[ Category:Omnidirectional Antennas ]]

Main Page

2018-12-09T08:41:47Z

Ppapadeas: restructure

__NOTOC__
SatNOGS is an integral part of the [https://libre.space Libre Space Foundation]. The project aims to build a global network of satellite ground stations. Designed as an open source participatory project based on the users operating a ground station that is accessed via a web page for all of the network users. A basic ground station can be made up of commercial off the shelf components that are commonly available with a static through to more complex stations with multiple movable antennas.
If you would like to build your own ground station and have limited knowledge then it is recommended that you follow a non-rotator build with a simple RTL-SDR dongle and a Raspberry Pi. This will get you on to the network quickly and allow you to start scheduling observations. There are a few choices to be made but he community are available to help if you need it. More complex, movable, antenna systems can be steered with either the SatNOGS designed rotator or a commercial unit such as the Yaesu GS5500, Spid XY or similar. It is recommended that these types of builds are for more experienced operators but there is no reason why these can not be put into operation, they just require more work.
The reference design uses a Raspberry Pi 3 + RTL-SDR dongle + either a VHF or UHF antenna. A Raspberry Pi image is available to make software installation simpler. Much of the decision making is down to personal choice but sometimes additional hardware is needed to help filter out local noise, such as strong broadcast stations. Both the community and Matrix / IRC offer support and assistance.
<div style="border-radius: 3px; width: 16%; height: 400px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>What is SatNOGS?</h2>
[[Intro|Introduction to SatNOGS]]
[[Ground Stations|What is a ground station?]]
[[Glossary]]
</div>
<div style="border-radius: 3px; width: 16%; height: 400px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Build</h2>
[[Omnidirectional Station How To|Quick start]]
[[Get_Started|Learn how to get started]]
[[Build|Build a ground station]]
[[Rotators|Rotators]]
[[Antennas|Antennas]]
[[Radio|Signal Reception]]
</div>
<div style="border-radius: 3px; width: 16%; height: 400px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Operate</h2>
[[Network|SatNOGS Network]]
[[Operation|Scheduling your first observation and operating your station]]
[[Adjusting the SatNOGS Client|Tuning and adjusting your station]]
[[Satnogs DB]]
[[Decode Telemetry and Packets]]
[[Audio Editing Tools]]
[[Telemetry Dashboards]]
 
</div>
<div style="border-radius: 3px; width: 16%; height: 400px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Contribute</h2>
[[Software contribution]]
[[Provide documentation]]
[[Satnogs DB]]
[[Troubleshooting|Troubleshooting]]
[[Get_In_Touch|Get in touch and ask for help]]
 
</div>

[[File:SatNOGS_explanation.png|center]]

Build

2018-08-31T09:26:07Z

Ppapadeas: updated sample setup

== Intro ==

Thanks for your interest on building a satellite ground station!

First things first: you need to understand all the different components of a ground station. Read on to learn more about ground stations. Once you have familiarized yourself with all the components, you need to make a selection on what you are going to be building (and/or buying).
== Options for Ground Stations ==

A satellite ground station is made up from different parts. The following diagram can help you select your setup based on your needs and/or your existing setup.

[[File:Satnogs_imagemap.png|center]]

Here are some links explaining the different options:

{| class="wikitable" style="margin: 0 auto;"
! Platform
! Controller
! Rotator
! Radio
! Antenna
|-
| [[Raspberry_Pi_3|Raspberry Pi 3]]
| [[SatNOGS Rotator Controller|SatNOGS Controller]]
| [[SatNOGS_Rotator_v3|SatNOGS Rotator]]
| [[Radio#SDR|SDR]]
| [[Antennas|Yagi]]
|-
| [[SatNOGS_Client_Ansible|Debian system]]
| [http://spid.net.pl/en/rot2prog-2/ Rot2Prog]
| [[SPID Big RAS]]
| [[Radio#HW Radio|Transceiver]]
| [[Antennas|Helical]]
|-
| [[Linux Desktop]]
| [[G-5500|lsf-g5500]]
| [[G-5500|Yaesu G5500]]
|
| [[Antennas|Vertical]]
|-
|
|
| [[No rotator]]
|
| [[Antennas|Cross-Yagi]]
|}

{{Message|Use the above table to select your setup. E.g. RPi3 > Yaesu G550 > SDR > UHF helical & VHF Cross Yagi}}

== How do I pick? ==

'''Client''': The Raspberry Pi 3 is the reference platform for SatNOGS, and is currently the option that has the best support from the community. Certain SDRs may benefit from a more powerful CPU, like what you'd find in a desktop machine; however, currently you'll need to set that up on your own.

'''Rotator''': A rotator, like the [[SatNOGS_Rotator_v3|SatNOGS Rotator v3]], will allow your antenna to follow satellites as they move across the sky, and thus pick up fainter signals. But if you want to get started quickly, or don't have the hardware skills to build your own, you can still pick up stronger signals (the ISS, NOAA and Meteor weather satellites) with a [[No_rotator|no-rotator]] setup. If you already have [https://github.com/Hamlib/Hamlib/wiki/Supported-Rotators a rotator supported by rotctl], you can use that.

'''Signal Reception''': The reference radio for SatNOGS is the [https://www.rtl-sdr.com RTL-SDR v3], but other latest-generation SDRs like the [http://www.nooelec.com/store/nesdr-smart-sdr.html NooElec NESDR SMart] should work as well. Higher-end SDRs should work as well, but can get a bit expensive. Alternately, [https://sourceforge.net/p/hamlib/wiki/Supported%20Radios/ any radio supported by rigctl] should work.

Amplification is generally done by a low noise amplifier, or LNA. There are multiple options:

* A wide-band LNA next to your SDR (see [http://lna4all.blogspot.com/ LNA4ALL] and similar)
* A band specific (or two) pre-amplifiers next to your antennas ([http://www.wimo.com/mast-preamplifier_e.html example])
* No amplification at all...just pump the gain of your SDR. (This is not recommended for the rtl-sdr.)

'''Antenna''': Stationary antennas (eg: [https://en.wikipedia.org/wiki/Turnstile_antenna Turnstile], [https://community.libre.space/t/parasitic-lindenblad-on-uhf/1128/2 Lindenblad]) will be easy to build and mount, as they won't require rotator hardware. They will let you receive stronger broadcasts, like NOAA weather satellites and ISS broadcasts, but may not work for receiving fainter cubesat broadcasts. Directional antennas (eg: Yagis, Helicals) can be more complicated to build, but will also require a rotator to track satellites across the sky. The advantage is that they will let you pick up fainter broadcasts from cubesats or ham radio satellites.

== Next steps ==

Once you have a ground station ready, you should go ahead and operate it! More info can be found on the [[Operation]] wiki page.

Linux Desktop

2018-06-22T18:37:25Z

Ppapadeas:

{{Warning|This page provides deprecated or unsupported information, please consider using [[SatNOGS Client Ansible]] instructions for installing SatNOGS client on a linux machine}}

Here you will find instructions on installing SatNOGS to a Linux Desktop running Ubuntu 16.04 LTS.

== Prep Work ==

Install dependencies

<pre>
sudo apt-get update
sudo apt-get install -y python-pip python-dev supervisor cmake libusb-1.0-0-dev libhamlib-utils vorbis-tools software-properties-common unzip
</pre>

Install gnuradio libs from myriadrf since we need a newer version than Ubuntu provides for 16.04

<pre>
sudo apt-get purge --auto-remove libgnuradio*
sudo add-apt-repository -y ppa:myriadrf/drivers
sudo add-apt-repository -y ppa:myriadrf/gnuradio
sudo apt-get update
sudo apt-get install -y gnuradio-dev libboost-dev libnova-dev libpng-dev
</pre>

== Install gr-satnogs ==

Grab the latest gr-satnogs debian package, unpack it, and install the appropriate deb file:
<pre>
wget -O archive.zip https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/-/jobs/35403119/artifacts/download (broken link here)
unzip archive.zip -d gr-satnogs
</pre>

== Install satnogs client ==
<pre>
pip install satnogsclient
</pre>

Linux Desktop

2018-06-22T18:36:39Z

Ppapadeas:

{{Warning|This page provides deprecated or unsupported information, please consider using [[SatNOGS Client Ansible]] instructions for installing SatNOGS client on a linux machine}}

'''This article to create a Linux Desktop client is not currently working. Use it as a hints and kinks rather than a cookbook.'''

Here you will find instructions on installing SatNOGS to a Linux Desktop running Ubuntu 16.04 LTS.

== Prep Work ==

Install dependencies

<pre>
sudo apt-get update
sudo apt-get install -y python-pip python-dev supervisor cmake libusb-1.0-0-dev libhamlib-utils vorbis-tools software-properties-common unzip
</pre>

Install gnuradio libs from myriadrf since we need a newer version than Ubuntu provides for 16.04

<pre>
sudo apt-get purge --auto-remove libgnuradio*
sudo add-apt-repository -y ppa:myriadrf/drivers
sudo add-apt-repository -y ppa:myriadrf/gnuradio
sudo apt-get update
sudo apt-get install -y gnuradio-dev libboost-dev libnova-dev libpng-dev
</pre>

== Install gr-satnogs ==

Grab the latest gr-satnogs debian package, unpack it, and install the appropriate deb file:
<pre>
wget -O archive.zip https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/-/jobs/35403119/artifacts/download (broken link here)
unzip archive.zip -d gr-satnogs
</pre>

== Install satnogs client ==
<pre>
pip install satnogsclient
</pre>

Operation

2018-05-26T16:03:49Z

Ppapadeas:

__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"| Group
! scope="col"| Schedule observation
! scope="col"| Delete observation
! scope="col"| Vet observation
! scope="col"| Discuss observation
|-
| Auth users
| No
| No
| No
| Any
|-
| Station owners
| Any (on online stations) & Own stations (on test stations)
| Own (stations or observations)
| Own (stations or observations)
| Any
|-
| Moderators
| Any (on online stations)& Own stations (on test stations)
| Any
| Any
| Any
|-
| Admins
| Any
| Any
| Any
| Any
|}

File:Waterfall 145037 2018-05-26T15-18-18.png

2018-05-26T16:01:46Z

Ppapadeas:

SatNOGS Rotator Controller

2018-05-23T04:35:15Z

Ppapadeas:

{{Template:Development
|Name= SatNOGS Rotator Controller
|image= Rotator controller v2.jpg
|type= Rotator Controller for SatNOGS rotator.
|cost= 60-80€
|status= Working
|latest-release-name= -
|latest-release= v2.2
|source-repo= https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-controller satnogs-rotator-controller - GitLab
|documentation= https://wiki.satnogs.org/index.php?title=SatNOGS_Rotator_Controller SatNOGS wiki
}}

== Intro ==
SatNOGS Rotator Controller refers to the set of electronics designed to operate a SatNOGS Rotator. There have been multiple iterations of the rotator controller design, but the modularity of the approach enables operations between different versions of the controller and the rotator.
Since the start of 2016, the rotator controller design is able to facilitate a DC-motors or stepper-motors rotator design. We intend to keep this modularity for the electronics and firmware design to facilitate the variety of build by our community.

== Rotator Controller v2 ==
<gallery>
Pcb_schema_v2_revC.png
Pcb_board_v2_revC.png
</gallery>

The PCB are tested in this [https://network.satnogs.org/stations/9/ ground station].

=== Features ===
* It is designed to fit the entire electronics needed to control rotator in Euroboard 80x50 mm.
* Main micro-controller is [https://store.arduino.cc/arduino-pro-mini Arduino pro-mini], [https://github.com/sparkfun/Arduino_Pro_Mini_328 SparkFun's Arduino Pro Mini 328] dev-board with ATmega328p.
* The modular design includes plug-in either [https://www.pololu.com/product/2133 DRV8825]/[https://www.pololu.com/product/1182 A4988] or [https://www.pololu.com/product/1213/resources DC motor drivers] (MC33926).
* The power supply in embed in the same board in contrast with previous version.
* Filtered power supply of micro controller.
* An I2C multiplexer is used to connect I2C encoders AS5601 (same ID) to get position feedback for each axis.
* A temperature sensor TC-74 monitoring the temperature inside the controller box in order to protect them from over-heating.
* There are some spare dev-pins in order to connect other peripherals like IMU or an LCD display.
* Pins with integrated RC-Low Pass filter for end-stops connection.
* Default communication interface is RS-485 but it can also be used as a UART.
* Using different paths for digital and power (motors) GND.
* Electrolytic capacitor and TVS-diode in PSU input
* Flashed either by using UART or ISP header

=== Build sequence ===
* Make sure you have a [[SatNOGS Rotator v3|mechanical assembly]] of the rotator constructed and ready
* Buy the PCB. [https://oshpark.com OshPark], [http://dirtypcbs.com DirtyPCBs.com], [https://www.elecrow.com/ Elecrow] have been used in the past with good results.
** You can order the v2.2 of the board directly using [https://oshpark.com/shared_projects/w0s8d4OJ this OSHPark link] or [https://dirtypcbs.com/store/designer/details/6933/5904/satnogs-v3-motor-controller-zip this DirtyPCBs link].
* Get all the necessary components according to BOM from latest tag (or the version that you want to build), [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-controller/tags Gitlab Tags]
* Assemble the PCB, by soldering the components
* Burn the firmware
* Using the wiring diagram, connect the controller to the Rotator
* You are ready! Proceed with testing

==== Assembly Guide ====

[[File:Rotator_controller_sheet1.png|thumb|center|800x420px|alt=|Rotator Controller sheet 1/2]]
[[File:Rotator_controller_sheet2.png|thumb|center|800x420px|alt=|Rotator Controller sheet 2/2]]

==== Microcontroller ====
<gallery mode=packed heights="250px">
Uc.png|Microcontroller
Uc_orientation.png|Microcontroller Orientation
I2c_pullup.png|I2C pull-up resistors
</gallery>


The main micro-controller of the board is arduino pro-mini 5V@16MHz, ATmega328P.
The +5V of the controller are produced from arduino pro-mini.
Some clones do not use correct parts in LDO, like the original one, with
result, when it powers up with +12V, burned.

Some examples,
* [https://community.libre.space/t/v2-controller-board-magic-smoke/1878 SatNOGS Community]
* [http://westsideelectronics.com/blew-up-a-cheap-arduino-pro-mini-clone/ West Side Electronics]

One Solution is not use clones, use [https://www.sparkfun.com/products/11113# Sparkfun's arduiuno pro-mini 5V@16MHz, ATmega328P].
The second solution is to add a LDO, like [https://gr.mouser.com/datasheet/2/268/mic5205-778789.pdf MIC5205] (maybe in a new revision of v2).

The power consumption in +5V is:

{| class="wikitable"
|-
! -
! QTY.
! VCC(V)
! IDD(mA)
! Total(mA)
|-
| AS5601
| 2
| 5
| 6.5
| 13
|-
| PCA9540B
| 1
| 5
| 0.1
| 0.1
|-
| SN65HVD485E
| 1
| 5
| 2
| 2
|-
| TC74
| 1
| 5
| 0.35
| 0.35
|-
| arduino pro mini
| 1
| 5
| 20
| 20
|-
| MC33926
| 2
| 5
| 0.2
| 0.4
|-
| DRV8825
| 2
| 5
| 0.1
| 0.2
|}

The LDO MIC5205 guaranteed 150mA output, for Stepper motors ~35-40mA, for DC motors ~35-40mA.

==== Motor Drivers ====
===== Stepper motor driver =====
[[File:Stepper_2.png|thumb|320x240px|Stepper motor driver]]
[[File:Stepper_1.png|thumb|320x240px|Jumpers]]
[[File:Stepper_orientation.jpg|thumb|320x240px|Orientation]]

For the stepper motor driver 2 options have been tested, [https://www.pololu.com/product/2133 DRV8825] and [https://www.pololu.com/product/1182 A4988].
For both options it is necessary to solder:
* 2 electrolytic capacitors C3, C4 100uF
* 4 single 0.1" male connectors for U3, U4
* 2 fixed terminal blocks P7, P8, Amphenol-VI0421550000G
* 6 jumpers to adjust the micro-step, '''default option is Full Step'''
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''JP3/JP6'''
| align="center" style="background:#f0f0f0;"|'''JP2/JP5'''
| align="center" style="background:#f0f0f0;"|'''JP1/JP4'''
| align="center" style="background:#f0f0f0;"|'''Microstep Resolution'''
|-
| align="center" style="background:#f0f000;"|'''Low''' || align="center" style="background:#f0f000;"|'''Low''' || align="center" style="background:#f0f000;"|'''Low''' || align="center" style="background:#f0f000;"|'''Full step'''
|-
| align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''Low''' || align="center"|'''Half step'''
|-
| align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''1/4 step'''
|-
| align="center"|'''High''' || align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''1/8 step'''
|-
| align="center"|'''Low''' || align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''1/16 step'''
|-
| align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''1/32 step'''
|-
| align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''High''' || align="center"|'''1/32 step'''
|-
| align="center"|'''High''' || align="center"|'''High''' || align="center"|'''High''' || align="center"|'''1/32 step'''
|-
|}

* Do'''NOT''' solder 2 resistors 100k, R4, R7 in default configuration (full step)
* If you have A4988 for stepper motor drive and you want to use micro stepping, when the MS1 is HIGH
it is necessary to solder R4, R7 according to [https://www.pololu.com/product/1201 A4983 Stepper Motor Driver Carrier, Step (and microstep) size].

In case of DRV8825, all pins MS1, MS2, MS3 have internal pull-up resistor.

Be careful:
* [http://reprap.org/wiki/Pololu_stepper_driver_board adjust the current (current limiting) for stepper motors]
* add a heat-sink.
* plug the stepper motor drivers

The stepper motor that is used, is [https://www.omc-stepperonline.com/hybrid-stepper-motor/nema-17-bipolar-59ncm-84ozin-2a-42x48mm-4wires-w-1m-cable-and-connector-17hs19-2004s1.html Nema 17 Bipolar 59Ncm],
* Size: ▱42 x 48 mm
* Weight: 390 g
* Shaft diameter: 5 mm
* Step Angle: 1.8 deg
* Nominal speed @ 12V: 720deg/s
* Rated Current/phase: 2.0A
* Stall torque @ 12V: 0.59Nm

===== DC motor driver =====
[[File:Dc_motor_driver.png|thumb|320x240px|DC motor driver]]

It is necessary to solder:
* Solder U6 with 0.1" female connectors as shown in picture
* Solder 2 pads in yellow circle by using ~1mm diameter wire
* Solder 2 2-pin 3.5mm terminal blocks for 2 DC motors

The DC motor controller is [https://www.pololu.com/product/1213 Dual MC33926 Motor Driver Carrier ]

* Motor driver: MC33926
* Motor channels: 2
* Minimum operating voltage: 5V
* Maximum operating voltage: 28V
* Operating voltage: 12V
* Continuous output current per channel: 2.5A
* Current sense: 0.525 V/A
* Maximum PWM frequency: 20 kHz
* Operating PWM frequency: 3921.5Hz (~4kHz)
* Minimum logic voltage: 2.5V
* Operating logic voltage: 5V
* Maximum logic voltage: 5.5V

The DC motor that we use is [https://www.pololu.com/product/1104 50:1 Metal Gearmotor 37Dx54L mm],
* Size: 37D x 54L mm
* Weight: 195 g
* Shaft diameter: 6 mm
* Free-run speed @ 12V: 200 rpm
* Free-run current @ 12V: 300 mA
* Stall current @ 12V: 5000 mA
* Stall torque @ 12V: 1.2Nm

 

==== Communication ====
===== ''UART'' =====
[[File:Jumper.png|thumb|320x240px|UART Jumpers]]
[[File:Rs 485.png|thumb|320x240px|Pin Header]]

To use UART:
* solder JP7 and JP8
* solder pin header 0.1" female connector
* not solder C1, U2, R18, R19 R9, R8, R1, D3
* A is TX and B is RX

===== ''RS-485'' =====
[[File:RS485_solder.png|thumb|320x240px|RS485]]
[[File:Missing_rs485_r19.png|thumb|320x240px|RS485]]

To use RS485:
* solder pin header 0.1" female connector
* solder C1, U2, R18, R19 R9, R8, R1, D3
* not solder JP7 and JP8

If you use PCB without R19 footprint, you can add it in arduino pro-mini UART header.

 

==== Power Supply ====
[[File:Psu.png|thumb|320x240px|Power Supply]]

Recommended power supply for rotator controller is: 48V @ 1A DC.
A good choice is the [https://gr.mouser.com/ProductDetail/709-LRS50-48 MEAN WELL LRS-50-48]

The switching power supply could get as input voltage, 19-60V DC. 
In different input voltages, must be change the components like D4 and F1. 
Default PCB components works at 48VDC.

 

==== Endstops ====
[[File:Endstop_part.png|thumb|320x240px|Endstop Specification]]
[[File:Endstop.jpg|thumb|320x240px|Endstop]]

In reference design, mechanical endstops (the [https://www.aliexpress.com/item/10PCS-MICROSWITCH-LIMIT-SWITCH-3pin-N-O-N-C-MICRO-SWITCH-free-shipping/32692144896.html?spm=2114.search0104.8.13.2f3c2457pmCyFH&transAbTest=ae803_5&priceBeautifyAB=0 P/N SS0505] of endstop is specified in [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator satnogs rotator BOM]) , are used.

The controller has the capability to accommodate optical or magnetic endstop which connected to
P2 header with silkscreen, SW1, SW2, +5V and GND.

Mechanical endstops are connected to
* SW1 and GND for azimuth axis
* SW2 and GND for elevation axis

 

==== Encoders ====
For stepper motor setup is optional (AS5601 encoder).

For DC motor setup is necessary.

[[File:Encoder_sheet1.png|thumb|center|800x420px|alt=|Rotary Encoder sheet 1/2]]
[[File:Encoder_sheet2.png|thumb|center|800x420px|alt=|Rotary Encoder sheet 2/2]]

 

==== Wiring ====

[[File:Wiring_diagram.png|thumb|center|800x420px|alt=|Wiring Diagram]]

 

==== Rotator Controller enclosure - Placement ====
Mount the rotator controller enclosure by using two sides adhesive tape (as mentioned in BOM)

[[File:Box_placement.png|thumb|center|800x420px|alt=|Rotator Controller enclosure - Placement]]

 

=== Firmware and Pin Assignments ===

===== Firmware =====

[https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware For stepper motors] 
[https://github.com/ph4as/dc_pid_control For DC motors]

===== Pins Configuration =====
* M1IN1 10, Step or PWM1
* M1IN2 9, Direction or PWM2
* M1SF 7, Status flag
* M1FB A1, Load measurment

* M2IN1 11, Step or PWM1
* M2IN2 3, Direction or PWM2
* M2SF 6, Status flag
* M2FB A0, Load measurment

* MOTOR_EN 8, Enable/Disable motors

* SW1 5, Endstop for axis 1
* SW2 4, Endstop for axis 2

* RS485_DIR 2, RS485 Half Duplex direction pin

* SDA_PIN 3, Data I2C pin
* SCL_PIN 4, Clock I2C pin

* PIN12 12, Digital output pin
* PIN13 13, Digital output pin
* A2 A2, Analog input pin
* A3 A3, Analog input pin

 

=== Pre-Flight Check ===

[[File:Pcb_testing_points.png|thumb|center|800x420px|alt=|Testing Points]]

* Power your PCB with 48VDC, without plug-in arduino pro-mini and motor drivers, measure with multimeter the voltage in point 1. Expected voltage +12V (reference to GND).
* Plug arduino pro-mini and measure with multimeter the voltage in point 2. Expected voltage +5V (reference to GND).
* Plug motor drivers (for steppermotors ensure the current is adjusted properly)
* Connect all peripheral devices like motors, sensors, endstops

If the two first steps fail, something is wrong (maybe there is a short circuit) in PCB. Check the connections with a multimeter.

Then the board is ready to run the firmware, [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware satnogs-rotator-firmware].

 

== Rotator Controller v1 ==

SatNOGS Rotator v3

2018-05-18T16:14:54Z

Ppapadeas: /* Sourcing */

{{Template:Rotator
|Rotator-Name=SatNOGS Rotator v3
|image=V3.jpg
|type= Az/El
|cost=~200 USD
|status= Beta
|latest-release= https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v3.0.1
|latest-release-name= Torx Flathead (v3.0.1)
|source-repo= https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/
|documentation= https://ohai.satnogs.org/project/satnogs-rotator-v3-mechanical-assembly/hardware/
}}

== Intro ==

v3 marks a major re-haul of the SatNOGS Rotator design, with learnings from [[SatNOGS Rotator v2|v2]] applied. You can see a lot of the thinking and background research that was conducted prior to v3 development in this [https://community.satnogs.org/t/satnogs-rotator-version-3/226 thread].

==Specifications==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''''
| align="center" style="background:#f0f0f0;"|'''SatNOGS v3 Rotator'''
|-
| Plastic Parts || 26
|-
| Non Printed Parts approx.||345
|-
| Cost||~ $220
|-
| Controller Electronics|| [[SatNOGS Rotator Controller]]
|-
| Type||AZ/EL (possible X/Y)
|-
| Motors||2x NEMA 17 Stepper or 2x DC Motors
|-
| Frame Material|| Aluminum T-slot 20x20
|-
| Speed (deg/sec) || 6.5 (Stepper motor), 20 (DC motor)
|-
| Torque (Nm) || ~26 (Stepper motor), ~64 (DC motor)
|-
| Dimensions (mm) || 306.5x197x142.5 (AZ/EL)
|-
| Weight (kg) || 6.2
|-
| Pro||
|-
| Con||
|-
|
|}

== Sourcing ==

'''3d Printing at a Fab Lab or your local hackerspace:''' If you don't have your own 3d printer, then a local Fab Lab or hackerspace may be able to do it for you. Fab Labs and hackerspaces are places that have invested in the machinery and you can take the designs to them. Generally they need .stl files to import into the software that runs the machines, but this should be discussed with the Fab Lab or hackerspace. You then pay for the material, time or a combination of the two for each of the parts or any other agreement in place.

* [http://www.fabfoundation.org/fab-labs/ FabLabs]
* [https://wiki.hackerspaces.org/List_of_Hacker_Spaces List of hacker spaces]

Most people building the rotator have had success builds with simple ABS material for the 3D printing parts.

'''T Slot''' - If you don't want to cut the pieces yourself, then you may be able to find a supplier that will do this for you. ([http://www.kjnltd.co.uk/ Here's one in the United Kingdom].)

Hidden corner connectors - AliExpress gave the cheapest supplier

A good US source is [http://us.misumi-ec.com/ MISUMI-USA]; they will also cut to length. MISUMI has several other global locations [https://www.misumi-ec.com].

Beware, the 20-series T-slot from [https://8020.net/ 80/20 Inc.] in the US has slots that are only 5.2mm wide. The hidden corner connectors from e.g. AliExpress '''will not fit'''.

'''Stepper Motors''' - eBay

'''Belts''' - eBay

'''Fixings / Pipe''' - eBay

== Build Sequence ==

* Make sure you have all parts
* Follow the [https://ohai.satnogs.org/project/satnogs-rotator-v3-mechanical-assembly/hardware/ instructions for mechanical assembly]
* Once mechanical assembly is ready, construct the SatNOGS Rotator Controller and connect it to the assembly.
* You are ready! Proceed with testing.

== Test Sequence ==

Test sequence needed

== Documentation ==

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v3.0.1 Rotator hardware v3 release files]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-controller Rotator controller v3 release files]
* [https://ohai.satnogs.org/project/satnogs-rotator-v3-mechanical-assembly/hardware/ Instructions for mechanical assembly]

[[Category:Rotator]]

SatNOGS Rotator Controller

2018-05-14T00:52:47Z

Ppapadeas:

{{Template:Development
|Name= SatNOGS Rotator Controller
|image= Rotator controller v2.jpg
|type= Rotator Controller for SatNOGS rotator.
|cost= 60-80€
|status= Working
|latest-release-name= -
|latest-release= v2.2
|source-repo= https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-controller satnogs-rotator-controller - GitLab
|documentation= https://wiki.satnogs.org/index.php?title=SatNOGS_Rotator_Controller SatNOGS wiki
}}

== Intro ==
SatNOGS Rotator Controller refers to the set of electronics designed to operate a SatNOGS Rotator. There have been multiple iterations of the rotator controller design, but the modularity of the approach enables operations between different versions of the controller and the rotator.
Since the start of 2016, the rotator controller design is able to facilitate a DC-motors or stepper-motors rotator design. We intend to keep this modularity for the electronics and firmware design to facilitate the variety of build by our community.

== Rotator Controller v2 ==
<gallery>
Pcb_schema_v2_revC.png
Pcb_board_v2_revC.png
</gallery>

The PCB are tested in this [https://network.satnogs.org/stations/9/ ground station].

=== Features ===
* It is designed to fit the entire electronics needed to control rotator in Euroboard 80x50 mm.
* Main micro-controller is [https://store.arduino.cc/arduino-pro-mini Arduino pro-mini], [https://github.com/sparkfun/Arduino_Pro_Mini_328 SparkFun's Arduino Pro Mini 328] dev-board with ATmega328p.
* The modular design includes plug-in either [https://www.pololu.com/product/2133 DRV8825]/[https://www.pololu.com/product/1182 A4988] or [https://www.pololu.com/product/1213/resources DC motor drivers] (MC33926).
* The power supply in embed in the same board in contrast with previous version.
* Filtered power supply of micro controller.
* An I2C multiplexer is used to connect I2C encoders AS5601 (same ID) to get position feedback for each axis.
* A temperature sensor TC-74 monitoring the temperature inside the controller box in order to protect them from over-heating.
* There are some spare dev-pins in order to connect other peripherals like IMU or an LCD display.
* Pins with integrated RC-Low Pass filter for end-stops connection.
* Default communication interface is RS-485 but it can also be used as a UART.
* Using different paths for digital and power (motors) GND.
* Electrolytic capacitor and TVS-diode in PSU input
* Flashed either by using UART or ISP header

=== Build sequence ===
* Make sure you have a [[SatNOGS Rotator v3|mechanical assembly]] of the rotator constructed and ready
* Buy the PCB. [https://oshpark.com OshPark], [http://dirtypcbs.com DirtyPCBs.com], [https://www.elecrow.com/ Elecrow] have been used in the past with good results.
** You can order the v2.2 of the board directly using [https://oshpark.com/shared_projects/w0s8d4OJ this OSHPark link].
* Get all the necessary components according to BOM from latest tag (or the version that you want to build), [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-controller/tags Gitlab Tags]
* Assemble the PCB, by soldering the components
* Burn the firmware
* Using the wiring diagram, connect the controller to the Rotator
* You are ready! Proceed with testing

==== Assembly Guide ====

[[File:Rotator_controller_sheet1.png|thumb|center|800x420px|alt=|Rotator Controller sheet 1/2]]
[[File:Rotator_controller_sheet2.png|thumb|center|800x420px|alt=|Rotator Controller sheet 2/2]]

==== Microcontroller ====
<gallery mode=packed heights="250px">
Uc.png|Microcontroller
Uc_orientation.png|Microcontroller Orientation
I2c_pullup.png|I2C pull-up resistors
</gallery>


The main micro-controller of the board is arduino pro-mini 5V@16MHz, ATmega328P.
The +5V of the controller are produced from arduino pro-mini.
Some clones do not use correct parts in LDO, like the original one, with
result, when it powers up with +12V, burned.

Some examples,
* [https://community.libre.space/t/v2-controller-board-magic-smoke/1878 SatNOGS Community]
* [http://westsideelectronics.com/blew-up-a-cheap-arduino-pro-mini-clone/ West Side Electronics]

One Solution is not use clones, use [https://www.sparkfun.com/products/11113# Sparkfun's arduiuno pro-mini 5V@16MHz, ATmega328P].
The second solution is to add a LDO, like [https://gr.mouser.com/datasheet/2/268/mic5205-778789.pdf MIC5205] (maybe in a new revision of v2).

The power consumption in +5V is:

{| class="wikitable"
|-
! -
! QTY.
! VCC(V)
! IDD(mA)
! Total(mA)
|-
| AS5601
| 2
| 5
| 6.5
| 13
|-
| PCA9540B
| 1
| 5
| 0.1
| 0.1
|-
| SN65HVD485E
| 1
| 5
| 2
| 2
|-
| TC74
| 1
| 5
| 0.35
| 0.35
|-
| arduino pro mini
| 1
| 5
| 20
| 20
|-
| MC33926
| 2
| 5
| 0.2
| 0.4
|-
| DRV8825
| 2
| 5
| 0.1
| 0.2
|}

The LDO MIC5205 guaranteed 150mA output, for Stepper motors ~35-40mA, for DC motors ~35-40mA.

==== Motor Drivers ====
===== Stepper motor driver =====
[[File:Stepper_2.png|thumb|320x240px|Stepper motor driver]]
[[File:Stepper_1.png|thumb|320x240px|Jumpers]]
[[File:Stepper_orientation.jpg|thumb|320x240px|Orientation]]

For the stepper motor driver 2 options have been tested, [https://www.pololu.com/product/2133 DRV8825] and [https://www.pololu.com/product/1182 A4988].
For both options it is necessary to solder:
* 2 electrolytic capacitors C3, C4 100uF
* 4 single 0.1" male connectors for U3, U4
* 2 fixed terminal blocks P7, P8, Amphenol-VI0421550000G
* 6 jumpers to adjust the micro-step, '''default option is Full Step'''
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''JP3/JP6'''
| align="center" style="background:#f0f0f0;"|'''JP2/JP5'''
| align="center" style="background:#f0f0f0;"|'''JP1/JP4'''
| align="center" style="background:#f0f0f0;"|'''Microstep Resolution'''
|-
| align="center" style="background:#f0f000;"|'''Low''' || align="center" style="background:#f0f000;"|'''Low''' || align="center" style="background:#f0f000;"|'''Low''' || align="center" style="background:#f0f000;"|'''Full step'''
|-
| align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''Low''' || align="center"|'''Half step'''
|-
| align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''1/4 step'''
|-
| align="center"|'''High''' || align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''1/8 step'''
|-
| align="center"|'''Low''' || align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''1/16 step'''
|-
| align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''1/32 step'''
|-
| align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''High''' || align="center"|'''1/32 step'''
|-
| align="center"|'''High''' || align="center"|'''High''' || align="center"|'''High''' || align="center"|'''1/32 step'''
|-
|}

* Do'''NOT''' solder 2 resistors 100k, R4, R7 in default configuration (full step)
* If you have A4988 for stepper motor drive and you want to use micro stepping, when the MS1 is HIGH
it is necessary to solder R4, R7 according to [https://www.pololu.com/product/1201 A4983 Stepper Motor Driver Carrier, Step (and microstep) size].

In case of DRV8825, all pins MS1, MS2, MS3 have internal pull-up resistor.

Be careful:
* [http://reprap.org/wiki/Pololu_stepper_driver_board adjust the current (current limiting) for stepper motors]
* add a heat-sink.
* plug the stepper motor drivers

The stepper motor that is used, is [https://www.omc-stepperonline.com/hybrid-stepper-motor/nema-17-bipolar-59ncm-84ozin-2a-42x48mm-4wires-w-1m-cable-and-connector-17hs19-2004s1.html Nema 17 Bipolar 59Ncm],
* Size: ▱42 x 48 mm
* Weight: 390 g
* Shaft diameter: 5 mm
* Step Angle: 1.8 deg
* Nominal speed @ 12V: 720deg/s
* Rated Current/phase: 2.0A
* Stall torque @ 12V: 0.59Nm

===== DC motor driver =====
[[File:Dc_motor_driver.png|thumb|320x240px|DC motor driver]]

It is necessary to solder:
* Solder U6 with 0.1" female connectors as shown in picture
* Solder 2 pads in yellow circle by using ~1mm diameter wire
* Solder 2 2-pin 3.5mm terminal blocks for 2 DC motors

The DC motor controller is [https://www.pololu.com/product/1213 Dual MC33926 Motor Driver Carrier ]

* Motor driver: MC33926
* Motor channels: 2
* Minimum operating voltage: 5V
* Maximum operating voltage: 28V
* Operating voltage: 12V
* Continuous output current per channel: 2.5A
* Current sense: 0.525 V/A
* Maximum PWM frequency: 20 kHz
* Operating PWM frequency: 3921.5Hz (~4kHz)
* Minimum logic voltage: 2.5V
* Operating logic voltage: 5V
* Maximum logic voltage: 5.5V

The DC motor that we use is [https://www.pololu.com/product/1104 50:1 Metal Gearmotor 37Dx54L mm],
* Size: 37D x 54L mm
* Weight: 195 g
* Shaft diameter: 6 mm
* Free-run speed @ 12V: 200 rpm
* Free-run current @ 12V: 300 mA
* Stall current @ 12V: 5000 mA
* Stall torque @ 12V: 1.2Nm

 

==== Communication ====
===== ''UART'' =====
[[File:Jumper.png|thumb|320x240px|UART Jumpers]]
[[File:Rs 485.png|thumb|320x240px|Pin Header]]

To use UART:
* solder JP7 and JP8
* solder pin header 0.1" female connector
* not solder C1, U2, R18, R19 R9, R8, R1, D3
* A is TX and B is RX

===== ''RS-485'' =====
[[File:RS485_solder.png|thumb|320x240px|RS485]]
[[File:Missing_rs485_r19.png|thumb|320x240px|RS485]]

To use RS485:
* solder pin header 0.1" female connector
* solder C1, U2, R18, R19 R9, R8, R1, D3
* not solder JP7 and JP8

If you use PCB without R19 footprint, you can add it in arduino pro-mini UART header.

 

==== Power Supply ====
[[File:Psu.png|thumb|320x240px|Power Supply]]

Recommended power supply for rotator controller is: 48V @ 1A DC.
A good choice is the [https://gr.mouser.com/ProductDetail/709-LRS50-48 MEAN WELL LRS-50-48]

The switching power supply could get as input voltage, 19-60V DC. 
In different input voltages, must be change the components like D4 and F1. 
Default PCB components works at 48VDC.

 

==== Endstops ====
[[File:Endstop_part.png|thumb|320x240px|Endstop Specification]]
[[File:Endstop.jpg|thumb|320x240px|Endstop]]

In reference design, mechanical endstops (the [https://www.aliexpress.com/item/10PCS-MICROSWITCH-LIMIT-SWITCH-3pin-N-O-N-C-MICRO-SWITCH-free-shipping/32692144896.html?spm=2114.search0104.8.13.2f3c2457pmCyFH&transAbTest=ae803_5&priceBeautifyAB=0 P/N SS0505] of endstop is specified in [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator satnogs rotator BOM]) , are used.

The controller has the capability to accommodate optical or magnetic endstop which connected to
P2 header with silkscreen, SW1, SW2, +5V and GND.

Mechanical endstops are connected to
* SW1 and GND for azimuth axis
* SW2 and GND for elevation axis

 

==== Encoders ====
For stepper motor setup is optional (AS5601 encoder).

For DC motor setup is necessary.

[[File:Encoder_sheet1.png|thumb|center|800x420px|alt=|Rotary Encoder sheet 1/2]]
[[File:Encoder_sheet2.png|thumb|center|800x420px|alt=|Rotary Encoder sheet 2/2]]

 

==== Wiring ====

[[File:Wiring_diagram.png|thumb|center|800x420px|alt=|Wiring Diagram]]

 

==== Rotator Controller enclosure - Placement ====
Mount the rotator controller enclosure by using two sides adhesive tape (as mentioned in BOM)

[[File:Box_placement.png|thumb|center|800x420px|alt=|Rotator Controller enclosure - Placement]]

 

=== Firmware and Pin Assignments ===

===== Firmware =====

[https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware For stepper motors] 
[https://github.com/ph4as/dc_pid_control For DC motors]

===== Pins Configuration =====
* M1IN1 10, Step or PWM1
* M1IN2 9, Direction or PWM2
* M1SF 7, Status flag
* M1FB A1, Load measurment

* M2IN1 11, Step or PWM1
* M2IN2 3, Direction or PWM2
* M2SF 6, Status flag
* M2FB A0, Load measurment

* MOTOR_EN 8, Enable/Disable motors

* SW1 5, Endstop for axis 1
* SW2 4, Endstop for axis 2

* RS485_DIR 2, RS485 Half Duplex direction pin

* SDA_PIN 3, Data I2C pin
* SCL_PIN 4, Clock I2C pin

* PIN12 12, Digital output pin
* PIN13 13, Digital output pin
* A2 A2, Analog input pin
* A3 A3, Analog input pin

 

=== Pre-Flight Check ===

[[File:Pcb_testing_points.png|thumb|center|800x420px|alt=|Testing Points]]

* Power your PCB with 48VDC, without plug-in arduino pro-mini and motor drivers, measure with multimeter the voltage in point 1. Expected voltage +12V (reference to GND).
* Plug arduino pro-mini and measure with multimeter the voltage in point 2. Expected voltage +5V (reference to GND).
* Plug motor drivers
* Connect all peripheral devices like motors, sensors, endstops

If the two first steps fail, something is wrong (maybe there is a short circuit) in PCB. Check the connections with a multimeter.

Then the board is ready to run the firmware, [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware satnogs-rotator-firmware].

 

== Rotator Controller v1 ==

Operation

2018-03-15T09:43:30Z

Ppapadeas:

__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 (Production)|production Network environment]], 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''
</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 production 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.
{{Message|Discuss button is only shown in the production instance of the SatNOGS network. If you have an observation in the dev instance you want help with, you can still post it manually to [https://community.libre.space/c/observations the Observations forum], and we'll be happy to help.}}

== 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"| Group
! scope="col"| Schedule observation
! scope="col"| Delete observation
! scope="col"| Vet observation
! scope="col"| Discuss observation
|-
| Auth users
| No
| No
| No
| Any
|-
| Station owners
| Any (on online stations) & Own stations (on test stations)
| Own (stations or observations)
| Own (stations or observations)
| Any
|-
| Moderators
| Any (on online stations)& Own stations (on test stations)
| Any
| Any
| Any
|-
| Admins
| Any
| Any
| Any
| Any
|}

Operation

2018-03-15T09:42:08Z

Ppapadeas:

__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 (Production)|production Network environment]], 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 Stage 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.
* 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''
</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 production 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.
{{Message|Discuss button is only shown in the production instance of the SatNOGS network. If you have an observation in the dev instance you want help with, you can still post it manually to [https://community.libre.space/c/observations the Observations forum], and we'll be happy to help.}}

== 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"| Group
! scope="col"| Schedule observation
! scope="col"| Delete observation
! scope="col"| Vet observation
! scope="col"| Discuss observation
|-
| Auth users
| No
| No
| No
| Any
|-
| Station owners
| Any (on online stations) & Own stations (on test stations)
| Own (stations or observations)
| Own (stations or observations)
| Any
|-
| Moderators
| Any (on online stations)& Own stations (on test stations)
| Any
| Any
| Any
|-
| Admins
| Any
| Any
| Any
| Any
|}

Operation

2018-03-15T09:41:57Z

Ppapadeas:

__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 (Production)|production Network environment], 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 Stage 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.
* 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''
</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 production 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.
{{Message|Discuss button is only shown in the production instance of the SatNOGS network. If you have an observation in the dev instance you want help with, you can still post it manually to [https://community.libre.space/c/observations the Observations forum], and we'll be happy to help.}}

== 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"| Group
! scope="col"| Schedule observation
! scope="col"| Delete observation
! scope="col"| Vet observation
! scope="col"| Discuss observation
|-
| Auth users
| No
| No
| No
| Any
|-
| Station owners
| Any (on online stations) & Own stations (on test stations)
| Own (stations or observations)
| Own (stations or observations)
| Any
|-
| Moderators
| Any (on online stations)& Own stations (on test stations)
| Any
| Any
| Any
|-
| Admins
| Any
| Any
| Any
| Any
|}

Get Started

2018-03-12T11:08:59Z

Ppapadeas: Updated for production changes

== Intro ==

Welcome to the SatNOGS community! Here you can find all the info needed to get you started.

== Who are you? ==

* '''Radio Amateur''': Most members of SatNOGS community are radio amateur operators licensed in may different countries around the world.
* '''Space enthusiast''': You love space and space data? SatNOGS is just the project for you! There are many learning opportunities around our community, and you can start easily with accessible projects, while you gradually become a space expert!
* '''Satellite operator''': You have your own satellite project? That's awesome! Many SatNOGS ground stations are built by satellite operators to gain extended access on their satellite telemetry and use the stations for telecommand and control.

== STEP 1: Join the community ==

First things first: make sure to get connected with fellow SatNOG-ers!

* Sign up for our [http://librespacefoundation.us10.list-manage.com/subscribe?u=77c76098dbbebaa4de35d0746&id=29409b0533 newsletter].
* Join the [https://community.libre.space community forums] and [https://community.libre.space/t/new-users-welcome/29 announce yourself].
* Follow us on [https://twitter.com/satnogs Twitter], [https://www.facebook.com/satnogs/ Facebook], and [https://plus.google.com/+SatnogsOrgProject Google+].
* Join our live discussions over at IRC #satnogs on the Freenode network, or via [https://riot.im/app/#/room/#satnogs:matrix.org the Matrix #satnogs room].

== STEP 2: Choose and deploy your ground station ==

Learn about the different options for [https://wiki.satnogs.org/Build ground stations and software], and create your station.

== STEP 3: Create an account on Network ==

SatNOGS runs a network instance at [https://network.satnogs.org/ https://network.satnogs.org]. It's used to operate various ground stations around the world, but it's also the right place for you to test your ground station. [https://network.satnogs.org/accounts/signup/ Sign up for an account]. Once you've verified your email address, log in and create a ground station entry and an API key. (Save the API key -- you'll need that when you install the SatNOGS client.

(And if you notice any bugs along the way -- [https://gitlab.com/librespacefoundation/satnogs/satnogs-network/issues please let us know]!)

== STEP 4: Test your setup ==

In this step, you will install the SatNOGS client (if you haven't already), and ensure that it can connect to the Network. Once that's done, you can [[Operation|schedule your first observation]].

== STEP 5: Move your station out of testing ==

Once you feel confident with your observations, post your successful observations to [https://community.libre.space/c/observations the community]. When you feel ready and feedback from the community is positive, edit your station in Network and remove the "Testing" flag from it! Now continue scheduling observations!

== STEP +: Consider wider contributions ==

There are many ways to contribute to the SatNOGS project:

* [[Software contribution|Contributing to the software that runs SatNOGS]]
* [[Provide documentation|Improving the documentation for the project]]
* [[Satnogs DB|Improving the SatNOGS database]]

SatNOGS Rotator Controller

2018-03-10T22:53:55Z

Ppapadeas: /* Build sequence */

{{Template:Development
|Name= SatNOGS Rotator Controller
|image= Rotator controller v2.jpg
|type= Rotator Controller for SatNOGS rotator.
|cost= ?
|status= Working
|latest-release-name= v2
|latest-release= v2
|source-repo= https://github.com/satnogs/satnogs-rotator-controller SatNOGS Rotator Controller
|documentation= https://wiki.satnogs.org/index.php?title=SatNOGS_Rotator_Controller SatNOGS wiki
}}

== Intro ==
SatNOGS Rotator Controller refers to the set of electronics designed to operate a SatNOGS Rotator. There have been multiple iterations of the rotator controller design, but the modularity of the approach enables operations between different versions of the controller and the rotator.
Since the start of 2016, the rotator controller design is able to facilitate a DC-motors or stepper-motors rotator design. We intend to keep this modularity for the electronics and firmware design to facilitate the variety of build by our community.

== Rotator Controller v2 ==
<gallery>
Schematic.png
Pcb.png
</gallery>

The PCB are tested in this [https://network.satnogs.org/stations/9/ ground station].

=== Features ===
* It is designed to fit the entire electronics needed to control rotator in Euroboard 80x50 mm.
* Main micro-controller is [https://store.arduino.cc/arduino-pro-mini Arduino pro-mini] dev-board with ATmega328p.
* The modular design includes plug-in either [https://www.pololu.com/product/2133 DRV8825]/[https://www.pololu.com/product/1182 A4988] or [https://www.pololu.com/product/1213/resources DC motor drivers] (MC33926).
* The power supply in embed in the same board in contrast with previous version.
* Filter in power supply of micro controller.
* It has an I2C multiplexer to connect I2C encoders AS5601 (same ID) to get position feedback for each axis.
* A temperature sensor TC-74 monitoring the temperature inside the controller box in order to protect them from over-<s>temperature</s>heating.
* More dev-pins to connect other peripherals like IMU, LCD display.
* Pins with RC-Low Pass filter for end-stops.
* Default communication interface is RS-485 (WIP) but it can <s>be</s> also be used as a UART.
* Avoid connection with GNDD directly with motor GND use keep out area.
* Electrolytic capacitor and TVS-diode in PSU input

=== Build sequence ===
* Make sure you have a [[SatNOGS Rotator v3|mechanical assembly]] of the rotator constructed and ready
* Buy the PCB. [https://oshpark.com OshPark] or [http://dirtypcbs.com DirtyPCBs.com] have been used in the past with good results.
* Assemble the PCB, by soldering the components
* Burn the firmware
* Using the wiring diagram, connect the controller to the Rotator
* You are ready! Proceed with testing

==== Micro controller ====
<gallery mode=packed heights="250px">
Uc.png|Microcontroller
Uc_orientation.png|Microcontroller Orientation
I2c_pullup.png|I2C pull-up resistors
</gallery>


==== Motor Specification ====
Maximum specification
* rotation speed: ~1200(200RPM) deg/s (after 1.8*30 = 54 gear reduction ~20deg/s and we want 5deg/s according to [https://community.libre.space/t/satnogs-rotator-version-3/226 v3 rotator specification]
* stall torque: 1.2Nm (after 1.8*30 = 54 gear reduction 64.5Nm)

Minimum specification
* rotation speed: ~360(60RPM) deg/s (after 1.8*30 = 54 gear reduction ~6.5deg/s and we want 5deg/s according to [https://community.libre.space/t/satnogs-rotator-version-3/226 v3 rotator specification]
* stall torque: 0.48Nm (after 1.8*30 = 54 gear reduction 25.92Nm)

You can design an adapter, to mount any motor to motor mount, like [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/blob/master/rotator_parts/motor_mount_flange.fcstd dc motor flange].
This is the [https://grobotronics.com/stepper-motor-mount-nema-17.html motor mount].

The DC motor that we use is [https://www.pololu.com/product/1104 50:1 Metal Gearmotor 37Dx54L mm],
* Size: 37D x 54L mm
* Weight: 195 g
* Shaft diameter: 6 mm
* Free-run speed @ 12V: 200 rpm
* Free-run current @ 12V: 300 mA
* Stall current @ 12V: 5000 mA
* Stall torque @ 12V: 1.2Nm

The stepper motor that we use is [https://www.omc-stepperonline.com/hybrid-stepper-motor/nema-17-bipolar-59ncm-84ozin-2a-42x48mm-4wires-w-1m-cable-and-connector-17hs19-2004s1.html Nema 17 Bipolar 59Ncm],
* Size: ▱42 x 48 mm
* Weight: 390 g
* Shaft diameter: 5 mm
* Step Angle: 1.8 deg
* Nominal speed @ 12V: 720deg/s
* Rated Current/phase: 2.0A
* Stall torque @ 12V: 0.59Nm

 

==== Motor Drivers ====
===== Stepper motor driver =====
[[File:Stepper_2.png|thumb|320x240px|Stepper motor driver]]
[[File:Stepper_1.png|thumb|320x240px|Jumpers]]
[[File:Stepper_orientation.jpg|thumb|320x240px|Orientation]]

For the stepper motor driver 2 options are tested, [https://www.pololu.com/product/2133 DRV8825] and [https://www.pololu.com/product/1182 A4988].
For both options it is necessary to solder:
* 2 electrolytic capacitors C3, C4 100uF
* 4 single 0.1" male connectors for U3, U4
* 2 fixed terminal blocks, Phoenix 1985467
* 6 jumpers to adjust the micro-step, '''default option is Full Step'''
* '''Not''' solder 2 resistors 100k, R4, R7

Be careful:
* [http://reprap.org/wiki/Pololu_stepper_driver_board adjust the current (current limiting) for stepper motors]
* add a heat-sink.
* plug the stepper motor drivers

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''JP3/JP6'''
| align="center" style="background:#f0f0f0;"|'''JP2/JP5'''
| align="center" style="background:#f0f0f0;"|'''JP1/JP4'''
| align="center" style="background:#f0f0f0;"|'''Microstep Resolution'''
|-
| align="center" style="background:#f0f000;"|'''Low''' || align="center" style="background:#f0f000;"|'''Low''' || align="center" style="background:#f0f000;"|'''Low''' || align="center" style="background:#f0f000;"|'''Full step'''
|-
| align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''Low''' || align="center"|'''Half step'''
|-
| align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''1/4 step'''
|-
| align="center"|'''High''' || align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''1/8 step'''
|-
| align="center"|'''Low''' || align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''1/16 step'''
|-
| align="center"|'''High''' || align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''1/32 step'''
|-
| align="center"|'''Low''' || align="center"|'''High''' || align="center"|'''High''' || align="center"|'''1/32 step'''
|-
| align="center"|'''High''' || align="center"|'''High''' || align="center"|'''High''' || align="center"|'''1/32 step'''
|-
|}

===== DC motor driver =====
The DC motor controller is [https://www.pololu.com/product/1213 Dual MC33926 Motor Driver Carrier ]

* Motor driver: MC33926
* Motor channels: 2
* Minimum operating voltage: 5V
* Maximum operating voltage: 28V
* Operating voltage: 12V
* Continuous output current per channel: 2.5A
* Current sense: 0.525 V/A
* Maximum PWM frequency: 20 kHz
* Operating PWM frequency: 3921.5Hz (~4kHz)
* Minimum logic voltage: 2.5V
* Operating logic voltage: 5V
* Maximum logic voltage: 5.5V
 

==== Communication ====
===== ''UART'' =====
[[File:Jumper.png|thumb|320x240px|UART Jumpers]]
[[File:Rs 485.png|thumb|320x240px|Pin Header]]

To use UART:
* solder JP7 and JP8
* solder pin header 0.1" female connector
* not solder C1, U2, R18, R9, R8, R1, D3
* A is TX and B is RX

===== ''RS-485'' =====
WIP

 

==== Power Supply ====
[[File:Psu.png|thumb|320x240px|Power Supply]]

Recommended power supply for rotator controller is: 48V @ 1A DC.
A good choice is [https://gr.mouser.com/ProductDetail/709-LRS50-48 MEAN WELL LRS-50-48]

The switching power supply could get as input voltage, 19-60V DC.
In different input voltages, must be change the components like
D4 and F1.

 

==== Endstops ====
* Mechanical Endstops

[[File:Endstop.jpg|thumb|320x240px|Endstop]]

 

==== Encoders ====
For stepper motor setup is optional (AS5601 encoder).

WIP

 

==== Wiring ====

[[File:Tmp_wiring.jpg|thumb|center|800x420px|alt=|Temporary wiring]]

 

==== Rotator Controller enclosure - Placement ====

WIP

 

=== Firmware and Pin Assignments ===

===== Firmware =====

[https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware More info in gitlab repository]
[https://github.com/ph4as/dc_pid_control For DC motors]

===== Pins Configuration =====
* M1IN1 6, Step or PWM1
* M1IN2 5, Direction or PWM2
* M1SF 7, Status flag
* M1FB A1, Load measurment

* M2IN1 11, Step or PWM1
* M2IN2 3, Direction or PWM2
* M2SF 10, Status flag
* M2FB A0, Load measurment

* MOTOR_EN 8, Enable/Disable motors

* SW1 9, Endstop for axis 1
* SW2 4, Endstop for axis 2

* RS485_DIR 2, RS485 Half Duplex direction pin

* SDA_PIN 3, Data I2C pin
* SCL_PIN 4, Clock I2C pin

* PIN12 12, Digital output pin
* PIN13 13, Digital output pin
* A2 A2, Analog input pin
* A3 A3, Analog input pin

 

=== Pre-Flight Check ===
Need to add testing procedure here.

How do you align the rotator?

 

== Rotator Controller v1 ==

Main Page

2018-03-09T15:47:17Z

Ppapadeas:

__NOTOC__
SatNOGS is an integral part of the [https://libre.space Libre Space Foundation]. The project aims to build a global network of satellite ground stations. Designed as an open source participatory project which is straightforward to build using commonly available parts and some 3D printed elements. A ground station is built to interact with a website that holds key satellite information. The web interface allows a user to schedule a satellite observation of any of the networked ground stations.
Here you can find more information on how to get started with SatNOGS, building and operating a satellite ground station and joining the SatNOGS Network.
A SatNOGS ground station can be made in a variety of ways. The reference design uses a Raspberry Pi and RTL-SDR dongle with either stationary antennas or either a SatNOGS rotator or a commercial amateur radio rotator. There is provision to use amateur radio transceivers or alternative SDR technology. The image below explains the system.
[[File:Satnogs_imagemap.png|center]]
<div style="border-radius: 3px; width: 16%; height: 300px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
__NOTOC__
<h2>What is SatNOGS</h2>
[[Intro|Intro to SatNOGS]]
[[Ground Stations|Intro to ground stations]]
[[Glossary]]
</div>
<div style="border-radius: 3px; width: 16%; height: 300px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Build</h2>
[[Get_Started|Learn how to get started]]
[[Build|Build a ground station]]
[[Rotators|Rotators]]
[[Antennas|Antennas]]
[[Radio|Signal Reception]]
</div>
<div style="border-radius: 3px; width: 16%; height: 300px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Operate</h2>
[[Network (Production)]]
[[Development Environment]]
[[Operation|Scheduling your first observation and operating your station]]
[[Adjusting the SatNOGS Client|Tuning and adjusting your station]]

[[Satnogs DB]]
 
</div>
<div style="border-radius: 3px; width: 16%; height: 300px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Contribute</h2>
[[Software contribution]]
[[Provide documentation]]
[[Satnogs DB]]
[[Troubleshooting|Troubleshooting]]
[[Get_In_Touch|Get in touch and ask for help]]
 
</div>

SatNOGS Network

2018-03-09T15:46:26Z

Ppapadeas:

The production instance of the SatNOGS Network website is where the scheduling, reviewing and operations happen for the SatNOGS project. The instance can be found in [https://network.satnogs.org network.satnogs.org]

==Purpose==
The production environment is the default place to get started on creating and connecting a ground station client. All SatNOGS operations (scheduling and reviewing satellite observations) happen in the production instance of our Network.

==Getting started==

* Head to network.satnogs.org
* Create a new account
* Verify your email
* On your user page, click on `Add Ground Station`
* Fill out all the information
* Head to your client and complete the setup of it using the information you supplied on the Network, plus you API key and the ID you got assigned.

Your station should now appear on the [https://network.satnogs.org/stations/ Ground Stations list] marked as yellow "Testing".

==Moving out of testing==
The production environment needs reliable ground stations that perform within the constraints that would be expected. A ground station should perform in a way that is comparable to its peers and it line with the constraints of the geography, antenna type, location and the other aspects which will make a ground station different to another.

Once you feel that your station has been performing well for a period of time under the "Testing" flag then you should go ahead and edit the station, remove the testing flag and announce the availability of a new station in our community channels!

The ground station should also be reliable. This does not mean that it should be available 24 hours a day, 7 days a week. Downtime is expected, it should however, not be unduly off line or unreliable. If you're ground station fits within these guidelines then it is good to have a conversation about if it is ready for the production environment.

==What is next==

* Keep your station busy! Schedule observations or reach out to the community for scheduling help.
* Keep reviewing your ground station performance.
* Reach out to others in community for help on any issue.

==Development==
The SatNOGS Network application is a project by itself with constant development. We do test the Network application in our [[Network (development)]|development instance], and always welcome python/javascript developers to help us in our [https://gitlab.com/librespacefoundation/satnogs/satnogs-network repository]

SatNOGS Network

2018-03-09T15:46:12Z

Ppapadeas:

The production instance of the SatNOGS Network website is where the scheduling, reviewing and operations happen for the SatNOGS project. The instance can be found in [https://network.satnogs.org network.satnogs.org]

==Purpose==
The production environment is the default place to get started on creating and connecting a ground station client. All SatNOGS operations (scheduling and reviewing satellite observations) happen in the production instance of our Network.

==Getting started==

* Head to network.satnogs.org
* Create a new account
* Verify your email
* On your user page, click on `Add Ground Station`
* Fill out all the information
* Head to your client and complete the setup of it using the information you supplied on the Network, plus you API key and the ID you got assigned.

Your station should now appear on the [https://network.satnogs.org/stations/ Ground Stations list] marked as yellow "Testing".

==Moving out of testing==
The production environment needs reliable ground stations that perform within the constraints that would be expected. A ground station should perform in a way that is comparable to its peers and it line with the constraints of the geography, antenna type, location and the other aspects which will make a ground station different to another.

Once you feel that your station has been performing well for a period of time under the "Testing" flag then you should go ahead and edit the station, remove the testing flag and announce the availability of a new station in our community channels!

The ground station should also be reliable. This does not mean that it should be available 24 hours a day, 7 days a week. Downtime is expected, it should however, not be unduly off line or unreliable. If you're ground station fits within these guidelines then it is good to have a conversation about if it is ready for the production environment.

==What is next==

- Keep your station busy! Schedule observations or reach out to the community for scheduling help.
- Keep reviewing your ground station performance.
- Reach out to others in community for help on any issue.

==Development==
The SatNOGS Network application is a project by itself with constant development. We do test the Network application in our [[Network (development)]|development instance], and always welcome python/javascript developers to help us in our [https://gitlab.com/librespacefoundation/satnogs/satnogs-network repository]

SatNOGS Network

2018-03-09T15:45:40Z

Ppapadeas: Fixed for registration directly on production

The production instance of the SatNOGS Network website is where the scheduling, reviewing and operations happen for the SatNOGS project. The instance can be found in [https://network.satnogs.org network.satnogs.org]

==Purpose==
The production environment is the default place to get started on creating and connecting a ground station client. All SatNOGS operations (scheduling and reviewing satellite observations) happen in the production instance of our Network.

==Getting started==
- Head to network.satnogs.org
- Create a new account
- Verify your email
- On your user page, click on `Add Ground Station`
- Fill out all the information
- Head to your client and complete the setup of it using the information you supplied on the Network, plus you API key and the ID you got assigned.

Your station should now appear on the [https://network.satnogs.org/stations/ Ground Stations list] marked as yellow "Testing".

==Moving out of testing==
The production environment needs reliable ground stations that perform within the constraints that would be expected. A ground station should perform in a way that is comparable to its peers and it line with the constraints of the geography, antenna type, location and the other aspects which will make a ground station different to another.

Once you feel that your station has been performing well for a period of time under the "Testing" flag then you should go ahead and edit the station, remove the testing flag and announce the availability of a new station in our community channels!

The ground station should also be reliable. This does not mean that it should be available 24 hours a day, 7 days a week. Downtime is expected, it should however, not be unduly off line or unreliable. If you're ground station fits within these guidelines then it is good to have a conversation about if it is ready for the production environment.

==What is next==

- Keep your station busy! Schedule observations or reach out to the community for scheduling help.
- Keep reviewing your ground station performance.
- Reach out to others in community for help on any issue.

==Development==
The SatNOGS Network application is a project by itself with constant development. We do test the Network application in our [[Network (development)]|development instance], and always welcome python/javascript developers to help us in our [https://gitlab.com/librespacefoundation/satnogs/satnogs-network repository]

SatNOGS Network

2018-03-09T15:31:28Z

Ppapadeas: Ppapadeas moved page Production Environment to Network (Production)

==What is the purpose of the production environment==
The production environment is the natural successor to the [[Development Environment]]. Once a station has been effectively commissioned and has gone through a necessary confidence period it can be moved to the production environment. This network is a place to be considered the place to move a station once you are comfortable with its performance and reliability.

==Getting onto the production environment==
The production environment needs reliable ground stations that perform within the constraints that would be expected. This means that for static, non rotator ground stations would not be expected to perform as well as rotator based systems. A ground station should perform in a way that is comparable to its peers and it line with the constraints of the geography, antenna type, location and the other aspects which will make a ground station different to another.

The ground station should also be reliable. This does not mean that it should be available 24 hours a day, 7 days a week. Downtime is expected, it should however, not be unduly off line or unreliable. If you're ground station fits within these guidelines then it is good to have a conversation about if it is ready for the production environment.

===Requesting inclusion===
Because the production has constraints to it and by virtue restricted. Ground stations operators are required to request an 'invitation'. This can be done via the [https://community.libre.space/ community].

Production Environment

2018-03-09T15:31:28Z

Ppapadeas: Ppapadeas moved page Production Environment to Network (Production)

#REDIRECT [[Network (Production)]]

No rotator

2018-02-24T17:07:48Z

Ppapadeas: /* Operation */

{{Template:Development
|Name= No-Rotator
|image= No rotator.jpg
|type= No-Rotator ground station for SatNOGS network.
|cost=
|status= Working
|latest-release=
|latest-release-name=
|source-repo=
|documentation=
}}

No-Rotator ground station uses a static antenna usually in VHF.
A Turnstile antenna that tunes at ~137MHz is used for NOAA satellites.
Some Turnstile antenna design, are wide enough to receive VHF band at 144 - 146 MHz.
For more vertical satellite passes, UHF Helical antennas receive satellites at 432 - 438 MHz,
e.g. [https://network.satnogs.org/stations/8/]

{{Message| Same setup could be used for a ground station with rotator.}}

= Bill of Materials =

The materials are categorized into 4 groups:
* RF components
* Client components
* Hardware components
* Tools

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Part'''
| align="center" style="background:#f0f0f0;"|'''Qty'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Price per Unit ($)'''
|-
| RTL-SDR || 1 || [https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-smart-sdr.html] || 21
|-
| SMA Male to SMA Male Connector Pigtail Cable || 1 || [http://www.ebay.com/itm/6-5-Length-SMA-Male-to-SMA-Male-Connector-Pigtail-Cable-/182286107527?epid=1749479193&hash=item2a71194387:g:X~gAAOSwOyJX3z4o] || 1
|-
| LNA with FM-Notch || 1 || [http://www.ebay.com/itm/Wideband-LNA-with-FM-notch-filter-Low-noise-amplifier-RTL-SDR-Airband-FM-stop/122344824822] || 35
|-
| RG-58 cable, 2.2m || 1 || [] || -
|-
| SMA Male cable connector || 1 || [] || -
|-
| Type-N Female chassis connector || 1 || [] || -
|-
| Type-N Male cable connector || 2 || [] || -
|-
| Turnstile antenna with Type-N Female connector || 1 || [] || -
|-
| Raspberry Pi 3 - Model B || 1 || [https://grobotronics.com/raspberry-pi-3-model-b.html] || 40
|-
| Raspberry Pi 3 Case || 1 || [https://grobotronics.com/raspberry-pi-2-square-case-transparent.html] || 5
|-
| SD Card, Class 10, 32GB, kingston, sandisk || 1 || [] || 16
|-
| Micro USB Active POE Splitter Power for Raspberry pi 3 Board (48V to 5V 2.4A) || 1 || [https://www.cableworks.gr/ilektronika/raspberry/raspberry-trofodotika/micro-usb-active-poe-splitter-power-for-raspberry-pi-3-board-48v-to-5v-2.4a-oem/] || 12
|-
| POE-48-24W-BULK POE Adapter 48V, 0.5A, 24W || 1 || [https://www.xpatit.gr/index.php?option=com_virtuemart&view=productdetails&virtuemart_product_id=1766&Itemid=0] || 13
|-
| Ethernet LAN RJ45 Outdoor Waterproof Connector || 1 || [http://www.ebay.com/itm/Ethernet-LAN-RJ45-Outdoor-Waterproof-Connector-M20-Stable-Signal-Black-/271524476589?epid=700279670&hash=item3f381eb6ad:g:9z8AAOSwopRYb3v-] || 3.6
|-
| cable, Male USB Micro to Male USB A, L=25cm || 1 || [] || 1
|-
| cable, Female USB A to Male USB A, L=25cm || 1 || [] || 1
|-
| Ring Core Ferrite Bead for USB cables || 2 || [] || 0.8
|-
| Ethernet cable, outdoor, CAT5, L=?m || 1 || [] ||
|-
| || 1 || [] ||
|-
|}

= Assembly instructions =
[[File:Liverpool_no_rotator_1.jpeg|400px|thumb|right|Inside the box 1]]
[[File:IMG 20170621 100727.jpg|400px|thumb|right|RF Detail]]

= Operation =

Follow the instructions for setting up the [[Raspberry_Pi_3|Raspberry Pi 3]] to setup your station.
Then consult the [[Operation]] page for getting started on our Network.

Raspberry Pi

2018-01-04T17:32:23Z

Ppapadeas: /* Advanced Setup */

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

= Intro =

The Raspberry Pi 3 is the reference platform for SatNOGS. You can try using various distributions for this (eg. Arch, Fedora), but the one we suggest is our custom image based on latest Raspbian.

= Raspbian =

== Download ==

You can download the latest Raspbian SatNOGS image following the links from the [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/tags latest tag on GitLab].

=== Artifacts list ===

The current artifacts list consists of:
* A Zipped image file
* An Image info file
* A SHA256 checksums file

== Data integrity verification ==

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

Example:
<pre>
$ sha256sum -c sha256sums
2017-09-29-Raspbian-SatNOGS-master-lite.info: OK
image_2017-09-29-Raspbian-SatNOGS-master-lite.zip: OK
</pre>

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

== Networking ==

If you are using wired Ethernet you should get connectivity right away. If you are using wireless then see [https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md this doc for network configuration instructions].

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

You will want to be sure to do the following:

* Set a strong, unique password
* Change localization settings:
** by default the rpi locale is configured for EN-GB, change as appropriate (ie: to EN_US.UTF-8)
** set timezone (we recommend UTC so your logs match the times in Network)
** set keyboard layout, again this is defaulting to a UK layout
** set wifi country
** expand filesysten
* Finish and reboot

Next, run
<pre>
sudo apt-get update && sudo apt-get -y upgrade
</pre>

== Setup ==

SSH to the Raspberry Pi with user "pi" and password "raspberry" (no quotes).

# Run "sudo satnogs-setup"
# Select "Update" to update the configuration tool
# Set basic configuration
# Select "Apply" and the Raspberry Pi will configure itself; this may take some time
# Select "Back" to exit

* Note: you can always reconfigure the software by running "sudo satnogs-setup" again.

=== Basic setup ===

* '''SATNOGS_API_TOKEN''': The API token assigned to your ground station on the SatNOGS Network website.

* '''SATNOGS_NETWORK_API_URL''': The API for the SatNOGS network site. If you're working on the stage environment, this is <code><nowiki>https://network-dev.satnogs.org/api/</nowiki></code>; if you're working on the prod environment, this is <code><nowiki>https://network.satnogs.org/api/</nowiki></code>.

* '''SATNOGS_RX_DEVICE''': If you are using an RTL-SDR, this is <code>rtlsdr</code>. Other devices supported by gr-satnogs include <code>usrpb200</code>, <code>usrp2</code>, <code>airspy</code> or <code>hackrf</code>; a complete list can be found [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/blob/master/apps/flowgraphs/satellites/README.md here].

* '''SATNOGS_STATION_ELEV''': The elevation of your ground station in metres.

* '''SATNOGS_STATION_ID''': The ID assigned to your station in the SatNOGS network site (either stage or prod).

* '''SATNOGS_STATION_LAT''': The latitude of your station. North is positive, south is negative.

* '''SATNOGS_STATION_LONG''': The longitude of your station. East is positive, west is negative.

* '''HAMLIB_UTILS_ROT_ENABLED''': Whether or not to enable the Hamlibs rotator daemon. Rotctld is a software daemon that provides a network server to control a rotator on a serial port. If you don't have a rotator (like the [https://wiki.satnogs.org/No_rotator No rotator setup]), enter <code>False</code>.

* '''HAMLIB_UTILS_ROT_OPTS''': Options for rotcld. For a yaesu rotator, use <code>-m 601 -r /dev/ttyACM0 -s 9600 -T 0.0.0.0</code>

=== Advanced Setup ===

* '''SATNOGS_CLIENT_URL''': If you to try a development version of satnogs-client, you can change the URL here. The URL needs to be in [https://pip.pypa.io/en/stable/reference/pip_install PIP format]. Here are some examples:
** git+https://gitlab.com/librespacefoundation/satnogs/satnogs-client.git@0 -- the '0' branch (the current development version) of satnogs-client
** git+https://gitlab.com/jdoe/satnogs-client.git@new-feature -- the 'new-feature' branch of jdoe's fork of satnogs-client
* '''SATNOGS_RADIO_GR_SATNOGS_PACKAGE''': This options allows you to change the installed package of gr-satnogs. For example, to install nightly development builds use:
** https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/-/jobs/artifacts/master/raw/build/debian/output/armhf/gr-satnogs_armhf.deb?job=nightly
* '''RF_GAIN''': RF Gain value for your SDR hardware. Defaults can be found [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/blob/master/python/hw_settings.py here].
** For rtl-sdr possible values are the following: 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

{{Message|Changing these settings is ''not'' recommended unless you're developing SatNOGS.}}

== Updating ==

To update SatNOGS software, re-run <code>sudo satnogs-setup</code>. Select "Update" to pull the latest Ansible playbook and then "Apply" to apply any updates.

Raspbian packages can be updated using the normal APT updating methods (e.g. <code>apt-get upgrade</code> or <code>aptitude</code>).

WARNING: An update can potentially interrupt a running observation!

== Testing ==

To see if satnogs-client has started successfully, check the logs with journalctl:

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

You should see entries running approximately once per minute that look like this:

<pre>
Oct 01 23:02:13 raspberrypi satnogs-client[6695]: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
Oct 01 23:02:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:02:14,466 - satnogsclient - INFO - [LD] Downlink thread waiting for first downlink packet
Oct 01 23:03:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:14,450 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:03:14 UTC)" (scheduled at 2017-10-01 23:03:14.423393+00:00)
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,324 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,325 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,327 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,453 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.423393+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,484 - apscheduler.executors.default - INFO - Running job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.436367+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,489 - apscheduler.executors.default - INFO - Job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,627 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,628 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,629 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:05:14 UTC)" executed successfully
</pre>

You can also try visiting satnog-client's web interface. In your browser, go to '''<nowiki>http://(ip address of your raspberry pi):5000</nowiki>'''. You should see something like this:

[[File:SatNOGS_client_screenshot.png|400px|thumb|center|SatNOGS client web page]]

If you see that, great -- you're ready to [[Operation|schedule your first observation]]! If not, check out the [[Troubleshooting]] page.

= Fedora =

Instructions for installing on Fedora can be found [[Fedora_Installation|here]].

Raspberry Pi

2017-12-12T18:02:33Z

Ppapadeas:

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

= Intro =

The Raspberry Pi 3 is the reference platform for SatNOGS. You can try using various distributions for this (eg. Arch, Fedora), but the one we suggest is our custom image based on latest Raspbian.

= Raspbian =

== Download ==

You can download the latest Raspbian SatNOGS image following the links from the [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/tags latest tag on GitLab].

=== Artifacts list ===

The current artifacts list consists of:
* A Zipped image file
* An Image info file
* A SHA256 checksums file

== Data integrity verification ==

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

Example:
<pre>
$ sha256sum -c sha256sums
2017-09-29-Raspbian-SatNOGS-master-lite.info: OK
image_2017-09-29-Raspbian-SatNOGS-master-lite.zip: OK
</pre>

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

== Networking ==

If you are using wired Ethernet you should get connectivity right away. If you are using wireless then see [https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md this doc for network configuration instructions].

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

You will want to be sure to do the following:

* Set a strong, unique password
* Change localization settings:
** by default the rpi locale is configured for EN-GB, change as appropriate (ie: to EN_US.UTF-8)
** set timezone (we recommend UTC so your logs match the times in Network)
** set keyboard layout, again this is defaulting to a UK layout
** set wifi country
** expand filesysten
* Finish and reboot

Next, run
<pre>
sudo apt-get update && sudo apt-get -y upgrade
</pre>

== Setup ==

SSH to the Raspberry Pi with user "pi" and password "raspberry" (no quotes).

# Run "sudo satnogs-setup"
# Select "Update" to update the configuration tool
# Set basic configuration
# Select "Apply" and the Raspberry Pi will configure itself; this may take some time
# Select "Back" to exit

* Note: you can always reconfigure the software by running "sudo satnogs-setup" again.

=== Basic setup ===

* '''SATNOGS_API_TOKEN''': The API token assigned to your ground station on the SatNOGS Network website.

* '''SATNOGS_NETWORK_API_URL''': The API for the SatNOGS network site. If you're working on the stage environment, this is <code><nowiki>https://network-dev.satnogs.org/api/</nowiki></code>; if you're working on the prod environment, this is <code><nowiki>https://network.satnogs.org/api/</nowiki></code>.

* '''SATNOGS_RX_DEVICE''': If you are using an RTL-SDR, this is <code>rtlsdr</code>. Other devices supported by gr-satnogs include <code>usrpb200</code>, <code>usrp2</code>, <code>airspy</code> or <code>hackrf</code>; a complete list can be found [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/blob/master/apps/flowgraphs/satellites/README.md here].

* '''SATNOGS_STATION_ELEV''': The elevation of your ground station in metres.

* '''SATNOGS_STATION_ID''': The ID assigned to your station in the SatNOGS network site (either stage or prod).

* '''SATNOGS_STATION_LAT''': The latitude of your station. North is positive, south is negative.

* '''SATNOGS_STATION_LONG''': The longitude of your station. East is positive, west is negative.

* '''HAMLIB_UTILS_ROT_ENABLED''': Whether or not to enable the Hamlibs rotator daemon. Rotctld is a software daemon that provides a network server to control a rotator on a serial port. If you don't have a rotator (like the [https://wiki.satnogs.org/No_rotator No rotator setup]), enter <code>False</code>.

* '''HAMLIB_UTILS_ROT_OPTS''': Options for rotcld. For a yaesu rotator, use <code>-m 601 -r /dev/ttyACM0 -s 9600 -T 0.0.0.0</code>

=== Advanced Setup ===

* '''SATNOGS_CLIENT_URL''': If you to try a development version of satnogs-client, you can change the URL here. The URL needs to be in [https://pip.pypa.io/en/stable/reference/pip_install PIP format]. Here are some examples:
** git+https://gitlab.com/librespacefoundation/satnogs/satnogs-client.git@0 -- the '0' branch (the current development version) of satnogs-client
** git+https://gitlab.com/jdoe/satnogs-client.git@new-feature -- the 'new-feature' branch of jdoe's fork of satnogs-client

{{Message|Changing this setting is ''not'' recommended unless you're developing satnogs-client itself.}}

== Updating ==

To update SatNOGS software, re-run <code>sudo satnogs-setup</code>. Select "Update" to pull the latest Ansible playbook and then "Apply" to apply any updates.

Raspbian packages can be updated using the normal APT updating methods (e.g. <code>apt-get upgrade</code> or <code>aptitude</code>).

WARNING: An update can potentially interrupt a running observation!

== Testing ==

To see if satnogs-client has started successfully, check the logs with journalctl:

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

You should see entries running approximately once per minute that look like this:

<pre>
Oct 01 23:02:13 raspberrypi satnogs-client[6695]: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
Oct 01 23:02:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:02:14,466 - satnogsclient - INFO - [LD] Downlink thread waiting for first downlink packet
Oct 01 23:03:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:14,450 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:03:14 UTC)" (scheduled at 2017-10-01 23:03:14.423393+00:00)
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,324 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,325 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,327 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,453 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.423393+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,484 - apscheduler.executors.default - INFO - Running job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.436367+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,489 - apscheduler.executors.default - INFO - Job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,627 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,628 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,629 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:05:14 UTC)" executed successfully
</pre>

You can also try visiting satnog-client's web interface. In your browser, go to '''<nowiki>http://(ip address of your raspberry pi):5000</nowiki>'''. You should see something like this:

[[File:SatNOGS_client_screenshot.png|400px|thumb|center|SatNOGS client web page]]

If you see that, great -- you're ready to [[Operation|schedule your first observation]]! If not, check out the [[Troubleshooting]] page.

= Fedora =

Instructions for installing on Fedora can be found [[Fedora_Installation|here]].

Rotators

2017-12-04T14:21:43Z

Ppapadeas:

==SatNOGS Rotators==
Our tracking mechanism is designed from scratch, parametric by default, 3D printed in under 8 hours. Utilizing two NEMA14 stepper motors we have unconstrained movement in Altitude and Azimuth.

===SatNOGS Rotator v2===

* [[SatNOGS Rotator v2|Wiki page]]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v2 Design files]

===SatNOGS Rotator v3===

* [[SatNOGS Rotator v3|Wiki page]]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v3.0 Design files]

==Commercial rotators==

===[http://download.qrz.ru/pub/hamradio/antenna/rotators/G-800SA_1000SA.pdf Yaesu G800]===

===[[G-5500|Yaesu G-5500]]===

===SPID X-Y===

==[[SatNOGS Rotator Controller|Electronics]]==
Our driving electronics are made of two Stepper motor drivers and an Arduino controlling them. Simple yet accurate.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-controller Design files]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware Firmware]

Main Page

2017-12-04T11:48:02Z

Ppapadeas: no toc

__NOTOC__
SatNOGS is an integral part of the Libre Space Foundation [https://libre.space]. The project aims to build a global network of satellite ground stations. Designed as an open source participatory project which is straightforward to build using commonly available parts and some 3D printed elements. A ground station is built to interact with a website that holds key satellite information. The web interface allows a user to schedule a satellite observation of any of the networked ground stations.
Here you can find more information on how to get started with SatNOGS, building and operating a satellite ground station and joining the SatNOGS Network.
A SatNOGS ground station can be made in a variety of ways. The reference design uses a Raspberry Pi and RTL-SDR dongle with either stationary antennas or either a SatNOGS rotator or a commercial amateur radio rotator. There is provision to use amateur radio transceivers or alternative SDR technology. The image below explains the system.The image below explains the system.
[[File:Satnogs_imagemap.png|center]]
<div style="border-radius: 3px; width: 25%; height: 200px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
__NOTOC__
<h2>What is SatNOGS</h2>
[[Intro|Intro to SatNOGS]]
[[Ground Stations|Intro to ground stations]]
[[Glossary]]
</div>
<div style="border-radius: 3px; width: 25%; height: 200px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Build</h2>
[[Get_Started|Learn how to get started]]
[[Build|Build a ground station]]
[[Rotators|Rotators]]
[[Antennas|Antennas]]
[[Receiver|Signal Reception]]
</div>
<div style="border-radius: 3px; width: 25%; height: 200px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Operate</h2>
[[Development Environment]]
[[Production Environment]]
[[Satnogs DB]]
 
</div>
<div style="border-radius: 3px; width: 25%; height: 200px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Contribute</h2>
[[Software contribution]]
[[Provide documentation]]
[[Satnogs DB]]
[[Troubleshooting|Troubleshooting]]
[[Get_In_Touch|How to get in touch and ask for help]]
 
</div>

Main Page

2017-11-09T23:26:26Z

Ppapadeas:

Welcome to [https://satnogs.org/ ''SatNOGS''] wiki. Here you can find more information on how to get started with SatNOGS, building and operating a satellite ground station and joining the SatNOGS Network. Feel free to edit the wiki and add your own ground station designs ([[rotators]], [[antennas]], [[Rotators|electronics]]).

[[File:Satnogs_imagemap.png|center]]

<div style="border-radius: 3px;width:25%;height:120px;background-color:#F6F6F6;float:left;display:block;margin:1.5%;border: 1px solid #A7D7F9;text-align:center;padding:2.5%;padding-top:0px">
<h2>What is SatNOGS</h2>
[[Intro|Intro to SatNOGS]]
[[Ground Stations|Intro to ground stations]]
[[Glossary]]
</div>
<div style="border-radius: 3px;width:25%;height:170px;background-color:#F6F6F6;float:left;display:block;margin:1.5%;border: 1px solid #A7D7F9;text-align:center;padding:2.5%;padding-top:0px">
<h2>Join SatNOGS</h2>
[[Get_Started|Learn how to get started]]
[[Build|Build a ground station]]
[[Operation|Operate a ground station]]
[[Troubleshooting|Troubleshooting]]
[[Get_In_Touch|How to get in touch and ask for help]]
</div>
<div style="border-radius: 3px;width:25%;height:120px;background-color:#F6F6F6;float:left;display:block;margin:1.5%;border: 1px solid #A7D7F9;text-align:center;padding:2.5%;padding-top:0px">
<h2>Contribute</h2>
[[Software contribution]]
[[Provide documentation]]
[[Satnogs DB]]

</div>

Main Page

2017-11-09T23:26:15Z

Ppapadeas:

Welcome to [https://satnogs.org/ ''SatNOGS''] wiki. Here you can find more information on how to get started with SatNOGS, building and operating a satellite ground station and joining the SatNOGS Network. Feel free to edit the wiki and add your own ground station designs ([[rotators]], [[antennas]], [[Rotators|electronics]]).

[[File:Satnogs_imagemap.png|center|900px|]]

<div style="border-radius: 3px;width:25%;height:120px;background-color:#F6F6F6;float:left;display:block;margin:1.5%;border: 1px solid #A7D7F9;text-align:center;padding:2.5%;padding-top:0px">
<h2>What is SatNOGS</h2>
[[Intro|Intro to SatNOGS]]
[[Ground Stations|Intro to ground stations]]
[[Glossary]]
</div>
<div style="border-radius: 3px;width:25%;height:170px;background-color:#F6F6F6;float:left;display:block;margin:1.5%;border: 1px solid #A7D7F9;text-align:center;padding:2.5%;padding-top:0px">
<h2>Join SatNOGS</h2>
[[Get_Started|Learn how to get started]]
[[Build|Build a ground station]]
[[Operation|Operate a ground station]]
[[Troubleshooting|Troubleshooting]]
[[Get_In_Touch|How to get in touch and ask for help]]
</div>
<div style="border-radius: 3px;width:25%;height:120px;background-color:#F6F6F6;float:left;display:block;margin:1.5%;border: 1px solid #A7D7F9;text-align:center;padding:2.5%;padding-top:0px">
<h2>Contribute</h2>
[[Software contribution]]
[[Provide documentation]]
[[Satnogs DB]]

</div>

File:Satnogs imagemap.png

2017-11-09T23:25:38Z

Ppapadeas: Ppapadeas uploaded a new version of File:Satnogs imagemap.png

Logical SatNOGS layout with options, to be used as an imagemap.

Operation

2017-10-28T22:11:20Z

Ppapadeas: /* Rating observations */

__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 [https://network-dev.satnogs.org/ Stage Environment], 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 Stage 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.
* 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.

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''
</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 production 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.
{{Message|Discuss button is only shown in the production instance of the SatNOGS network. If you have an observation in the dev instance you want help with, you can still post it manually to [https://community.libre.space/c/observations the Observations forum], and we'll be happy to help.}}

Operation

2017-10-18T19:16:19Z

Ppapadeas: /* Rating observations */

__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 [https://network-dev.satnogs.org/ Stage Environment], 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 Stage 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.
* 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.

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 hyperbola 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''
</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 production 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.
{{Message|Discuss button is only shown in the production instance of the SatNOGS network. If you have an observation in the dev instance you want help with, you can still post it manually to [https://community.libre.space/c/observations the Observations forum], and we'll be happy to help.}}

Operation

2017-10-15T11:57:28Z

Ppapadeas: added sample observations

== Scheduling your first test observation ==

'''Assumptions:'''

* You've set up your [[Raspberry Pi 3|SatNOGS client successfully]]
* You've created an account on the [https://network-dev.satnogs.org/ Stage Environment], 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 Stage 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.
* 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.
[[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.

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 hyperbola 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''
</gallery>

File:Waterfall 20483 2017-10-15T05-12-49.png

2017-10-15T11:55:12Z

Ppapadeas:

File:Waterfall 20571 2017-10-15T05-25-56.png

2017-10-15T11:17:09Z

Ppapadeas:

File:Waterfall 20506 2017-10-15T06-47-36.png

2017-10-15T11:14:44Z

Ppapadeas:

File:Waterfall 20499 2017-10-15T07-17-32.png

2017-10-15T11:13:22Z

Ppapadeas:

File:Waterfall 20534 2017-10-15T07-21-24.png

2017-10-15T11:12:14Z

Ppapadeas:

File:Waterfall 20657 2017-10-15T10-07-51.png

2017-10-15T11:08:26Z

Ppapadeas:

File:Screenshot from 2017-10-15 11-59-59.png

2017-10-15T11:00:23Z

Ppapadeas:

Raspberry Pi

2017-10-02T15:22:08Z

Ppapadeas: no rotator fixes

= Intro =

The Raspberry Pi 3 is the reference platform for SatNOGS. As of September 2017, there are two methods of installing the SatNOGS client on a Raspberry Pi:

* Using Fedora for ARM, and following the instructions at [http://satnogs.readthedocs.io/en/stable/satnogs-client/doc/raspi-install.html satnogs.readthedocs.io]
* Installing the custom-built SatNOGS Raspbian image

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

= Fedora =

Start by downloading the "Server" or "Minimal" image from the [https://arm.fedoraproject.org/ the Fedora ARM project page]. After that, follow the instructions at [http://satnogs.readthedocs.io/en/stable/satnogs-client/doc/raspi-install.html satnogs.readthedocs.io].

* If you run into anything in the instructions that is unclear, please submit an issue against [https://gitlab.com/librespacefoundation/satnogs/satnogs-docs the documentation repository].

= Raspbian =

== Download ==

The latest Raspbian SatNOGS image artifacts can be downloaded from [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/jobs GitLab].

=== Artifacts list ===

The current artifacts list consists of:
* A Zipped image file
* An Image info file
* A SHA256 checksums file

== Data integrity verification ==

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

Example:
<pre>
$ sha256sum -c sha256sums
2017-09-10-Raspbian-SatNOGS-master-lite.info: OK
image_2017-09-10-Raspbian-SatNOGS-master-lite.zip: OK
</pre>

== Flashing ==

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

== Networking ==

If you are using wired Ethernet you should get connectivity right away. If you are using wireless then see [https://www.raspberrypi.org/documentation/configuration/wireless/wireless-cli.md this doc for network configuration instructions].

== Setup ==

SSH to the Raspberry Pi with user "pi" and password "raspberry" (no quotes). Run "sudo satnogs-setup" to set basic configuration. Select "quit" when you are finished, and the Raspberry Pi will reconfigure itself; this may take some time.

* Note: you can always reconfigure the software by running "sudo satnogs-setup -n" again.

* Note: You may find further details about the following options on the [http://satnogs.readthedocs.io/en/stable/satnogs-client/doc/raspi-install.html satnogs.readthedocs.io] page.

=== Basic setup ===

* '''SATNOGS_API_TOKEN''': The API token assigned to your ground station on the SatNOGS Network website.

* '''SATNOGS_NETWORK_API_URL''': The API for the SatNOGS network site. If you're working on the stage environment, this is https://network-dev.satnogs.org/api/; if you're working on the prod environment, this is https://network.satnogs.org/api/.

* '''SATNOGS_RX_DEVICE''': If you are using an RTL-SDR, this is <code>rtlsdr</code>. Other devices supported by gr-satnogs include <code>usrpb200</code>, <code>usrp2</code>, <code>airspy</code> or <code>hackrf</code>; a complete list can be found [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/blob/master/apps/flowgraphs/satellites/README.md here].

* '''SATNOTS_STATION_ELEV''': The elevation of your ground station in metres.

* '''SATNOTS_STATION_ID''': The ID assigned to your station in the SatNOGS network site (either stage or prod).

* '''SATNOTS_STATION_LAT''': The latitude of your station. North is positive, south is negative.

* '''SATNOTS_STATION_LONG''': The longitude of your station. East is positive, west is negative.

* '''HAMLIB_UTILS_ROT_ENABLED''': Whether or not to enable the Hamlibs rotator daemon. Rotctld is a software daemon that provides a network server to control a rotator on a serial port. If you don't have a rotator (like the [https://wiki.satnogs.org/No_rotator No rotator setup]), enter <code>False</code>.

* '''HAMLIB_UTILS_ROT_OPTS''': Options for rotcld.

== Updating ==

To update SatNOGS software, re-run <code>sudo satnogs-setup</code>. This will pull the latest Ansible playbook and update if necessary.

Raspbian packages can be updated using the normal APT updating methods (e.g. <code>apt-get upgrade</code> or <code>aptitude</code>).

WARNING: An update can potentially interrupt a running observation!

== Testing ==

To see if satnogs-client has started successfully, check the logs with journalctl:

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

You should see entries running approximately once per minute that look like this:

<pre>
Oct 01 23:02:13 raspberrypi satnogs-client[6695]: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
Oct 01 23:02:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:02:14,466 - satnogsclient - INFO - [LD] Downlink thread waiting for first downlink packet
Oct 01 23:03:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:14,450 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:03:14 UTC)" (scheduled at 2017-10-01 23:03:14.423393+00:00)
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,324 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,325 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,327 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,453 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.423393+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,484 - apscheduler.executors.default - INFO - Running job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.436367+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,489 - apscheduler.executors.default - INFO - Job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,627 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,628 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,629 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:05:14 UTC)" executed successfully
</pre>

If you see that, great -- you're ready to [[Operation|schedule your first observation]]! If not, check out the [[Troubleshooting]] page.

Get Started

2017-07-28T17:30:54Z

Ppapadeas:

== Intro ==
Welcome to the SatNOGS community! Here you can find all info to get you started.

== Who are you ==

=== Radio Amateur ===
Most members of SatNOGS community are radio amateur operators licensed in may different countries around the world.
=== Satellite enthusiast ===
You love space and space data? SatNOGS is just the project for you! There are many learning opportunities around our community, and you can start easily with accessible projects, while you gradually become a space expert!
=== Satellite operator ===
You have your own satellite project, that's awesome! Many SatNOGS ground stations are built by satellite operators to gain extended access on their satellite telemetry and use the stations for telecommand and control.

== STEP 1: Join the community ==
First things first make sure to get connected with fellow SatNOG-ers:

# Sign up for our [http://librespacefoundation.us10.list-manage.com/subscribe?u=77c76098dbbebaa4de35d0746&id=29409b0533 newsletter].
# Join the [https://community.libre.space community forums] and [https://community.libre.space/t/new-users-welcome/29 announce yourself].
# Follow us on [https://twitter.com/satnogs twitter], facebook, google+
# Join our live discussions over at IRC #satnogs @freenode or via [https://riot.im/app/#/room/#satnogs:matrix.org Matrix #satnogs room]

== STEP 2: Choose and deploy your setup ==

== STEP 3: Create an account on Dev Network ==

== STEP 4: Test your setup ==

== STEP 5: Request a production account ==

== STEP +: Consider wider contributions ==

Get Started

2017-07-28T17:01:48Z

Ppapadeas:

Get Started

2017-07-28T16:55:25Z

Ppapadeas:

== Intro ==
Welcome to the SatNOGS community! Here you can find all info to get you started.

== Who are you ==

=== Radio Amateur ===
Most members of SatNOGS community are radio amateur operators licensed in may different countries around the world.
=== Satellite enthusiast ===
You love space and space data? SatNOGS is just the project for you! There are many learning opportunities around our community, and you can start easily with accessible projects, while you gradually become a space expert!
=== Satellite operator ===
You have your own satellite project, that's awesome! Many SatNOGS ground stations are built by satellite operators to gain extended access on their satellite telemetry and use the stations for telecommand and control.

== Join the community ==
Once you selected your setup, make sure to get connected with fellow SatNOG-ers:

# Sign up for our [http://librespacefoundation.us10.list-manage.com/subscribe?u=77c76098dbbebaa4de35d0746&id=29409b0533 newsletter].
# Join the [https://community.satnogs.org community forums] and [https://community.satnogs.org/t/new-users-welcome/29 announce yourself].
# Follow us on [https://twitter.com/satnogs twitter], facebook, google+
# Create an account to [https://db.satnogs.org SatNOGS DB] and start contributing!

No rotator

2017-06-25T18:12:57Z

Ppapadeas:

{{Template:Development
|Name= No-Rotator
|image= No rotator.jpg
|type= No-Rotator ground station for SatNOGS network.
|cost=
|status= Working
|latest-release=
|latest-release-name=
|source-repo=
|documentation=
}}

No-Rotator ground station it uses a static antenna usually in VHF.
A Turnstile antenna that tuned at ~137MHz is used for NOAA satellites.
Some Turnstile antenna designs, it's wide enough to receive VHF band at 144 - 146 MHz.
For more vertical satellite passes, UHF Helical antennas receives satellites at 432 - 438 MHz,
e.g. [https://network.satnogs.org/stations/8/]

{{Message| Same setup could be used for a ground station with rotator.}}

= Bill of Materials =

The materials are categorized into 4 groups:
* RF components
* Client components
* Hardware components
* Tools

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Part'''
| align="center" style="background:#f0f0f0;"|'''Qty'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Price per Unit ($)'''
|-
| RTL-SDR || 1 || [https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-smart-sdr.html] || 21
|-
| SMA Male to SMA Male Connector Pigtail Cable || 1 || [http://www.ebay.com/itm/6-5-Length-SMA-Male-to-SMA-Male-Connector-Pigtail-Cable-/182286107527?epid=1749479193&hash=item2a71194387:g:X~gAAOSwOyJX3z4o] || 1
|-
| LNA with FM-Notch || 1 || [http://www.ebay.com/itm/Wideband-LNA-with-FM-notch-filter-Low-noise-amplifier-RTL-SDR-Airband-FM-stop/122344824822] || 35
|-
| RG-58 cable, 2.2m || 1 || [] || -
|-
| SMA Male cable connector || 1 || [] || -
|-
| Type-N Female chassis connector || 1 || [] || -
|-
| Type-N Male cable connector || 2 || [] || -
|-
| Turnstile antenna with Type-N Female connector || 1 || [] || -
|-
| Raspberry Pi 3 - Model B || 1 || [https://grobotronics.com/raspberry-pi-3-model-b.html] || 40
|-
| Raspberry Pi 3 Case || 1 || [https://grobotronics.com/raspberry-pi-2-square-case-transparent.html] || 5
|-
| SD Card, Class 10, 32GB, kingston, sandisk || 1 || [] || 16
|-
| Micro USB Active POE Splitter Power for Raspberry pi 3 Board (48V to 5V 2.4A) || 1 || [https://www.cableworks.gr/ilektronika/raspberry/raspberry-trofodotika/micro-usb-active-poe-splitter-power-for-raspberry-pi-3-board-48v-to-5v-2.4a-oem/] || 12
|-
| POE-48-24W-BULK POE Adapter 48V, 0.5A, 24W || 1 || [https://www.xpatit.gr/index.php?option=com_virtuemart&view=productdetails&virtuemart_product_id=1766&Itemid=0] || 13
|-
| Ethernet LAN RJ45 Outdoor Waterproof Connector || 1 || [http://www.ebay.com/itm/Ethernet-LAN-RJ45-Outdoor-Waterproof-Connector-M20-Stable-Signal-Black-/271524476589?epid=700279670&hash=item3f381eb6ad:g:9z8AAOSwopRYb3v-] || 3.6
|-
| cable, Male USB Micro to Male USB A, L=25cm || 1 || [] || 1
|-
| cable, Female USB A to Male USB A, L=25cm || 1 || [] || 1
|-
| Ring Core Ferrite Bead for USB cables || 2 || [] || 0.8
|-
| Ethernet cable, outdoor, CAT5, L=?m || 1 || [] ||
|-
| || 1 || [] ||
|-
|}

= Assembly instructions =
[[File:Liverpool_no_rotator_1.jpeg|400px|thumb|right|Inside the box 1]]
[[File:IMG 20170621 100727.jpg|400px|thumb|right|RF Detail]]

= Operation =

[http://docs.satnogs.org/en/stable/satnogs-client/doc/installation.html SatNOGS Client Installation]

File:IMG 20170621 100727.jpg

2017-06-25T18:12:21Z

Ppapadeas:

No rotator

2017-06-25T18:11:09Z

Ppapadeas:

{{Template:Development
|Name= No-Rotator
|image= No rotator.jpg
|type= No-Rotator ground station for SatNOGS network.
|cost=
|status= Working
|latest-release=
|latest-release-name=
|source-repo=
|documentation=
}}

No-Rotator ground station it uses a static antenna usually in VHF.
A Turnstile antenna that tuned at ~137MHz is used for NOAA satellites.
Some Turnstile antenna designs, it's wide enough to receive VHF band at 144 - 146 MHz.
For more vertical satellite passes, UHF Helical antennas receives satellites at 432 - 438 MHz,
e.g. [https://network.satnogs.org/stations/8/]

{{Message| Same setup could be used for a ground station with rotator.}}

= Bill of Materials =

The materials are categorized into 4 groups:
* RF components
* Client components
* Hardware components
* Tools

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Part'''
| align="center" style="background:#f0f0f0;"|'''Qty'''
| align="center" style="background:#f0f0f0;"|'''Source'''
| align="center" style="background:#f0f0f0;"|'''Price per Unit ($)'''
|-
| RTL-SDR || 1 || [https://www.nooelec.com/store/sdr/sdr-receivers/nesdr-smart-sdr.html] || 21
|-
| SMA Male to SMA Male Connector Pigtail Cable || 1 || [http://www.ebay.com/itm/6-5-Length-SMA-Male-to-SMA-Male-Connector-Pigtail-Cable-/182286107527?epid=1749479193&hash=item2a71194387:g:X~gAAOSwOyJX3z4o] || 1
|-
| LNA with FM-Notch || 1 || [http://www.ebay.com/itm/Wideband-LNA-with-FM-notch-filter-Low-noise-amplifier-RTL-SDR-Airband-FM-stop/122344824822] || 35
|-
| RG-58 cable, 2.2m || 1 || [] || -
|-
| SMA Male cable connector || 1 || [] || -
|-
| Type-N Female chassis connector || 1 || [] || -
|-
| Type-N Male cable connector || 2 || [] || -
|-
| Turnstile antenna with Type-N Female connector || 1 || [] || -
|-
| Raspberry Pi 3 - Model B || 1 || [https://grobotronics.com/raspberry-pi-3-model-b.html] || 40
|-
| Raspberry Pi 3 Case || 1 || [https://grobotronics.com/raspberry-pi-2-square-case-transparent.html] || 5
|-
| SD Card, Class 10, 32GB, kingston, sandisk || 1 || [] || 16
|-
| Micro USB Active POE Splitter Power for Raspberry pi 3 Board (48V to 5V 2.4A) || 1 || [https://www.cableworks.gr/ilektronika/raspberry/raspberry-trofodotika/micro-usb-active-poe-splitter-power-for-raspberry-pi-3-board-48v-to-5v-2.4a-oem/] || 12
|-
| POE-48-24W-BULK POE Adapter 48V, 0.5A, 24W || 1 || [https://www.xpatit.gr/index.php?option=com_virtuemart&view=productdetails&virtuemart_product_id=1766&Itemid=0] || 13
|-
| Ethernet LAN RJ45 Outdoor Waterproof Connector || 1 || [http://www.ebay.com/itm/Ethernet-LAN-RJ45-Outdoor-Waterproof-Connector-M20-Stable-Signal-Black-/271524476589?epid=700279670&hash=item3f381eb6ad:g:9z8AAOSwopRYb3v-] || 3.6
|-
| cable, Male USB Micro to Male USB A, L=25cm || 1 || [] || 1
|-
| cable, Female USB A to Male USB A, L=25cm || 1 || [] || 1
|-
| Ring Core Ferrite Bead for USB cables || 2 || [] || 0.8
|-
| Ethernet cable, outdoor, CAT5, L=?m || 1 || [] ||
|-
| || 1 || [] ||
|-
|}

= Assembly instructions =
[[File:Liverpool_no_rotator_1.jpeg|300px|thumb|right|Inside the box 1]]

= Operation =

[http://docs.satnogs.org/en/stable/satnogs-client/doc/installation.html SatNOGS Client Installation]

File:Liverpool no rotator 1.jpeg

2017-06-25T18:10:55Z

Ppapadeas: