SatNOGS Wiki - User contributions [en]

Continuous Development

2018-06-05T14:55:50Z

Comzeradd: CD page

The Continuous Deployment workflow for both Netowrk and DB consists of the three steps below.

=== GitLab CI ===

We have two different jobs (stage and production) that are triggered when there is a new merge on dev or master respectively. These jobs can been seen at the [https://gitlab.com/librespacefoundation/satnogs/satnogs-network/blob/dev/.gitlab-ci.yml .gitlab-ci.yml] file on both of these repositories.

=== GitLab Variables ===

GitLab hosts some secret variables for each environment. Such as IP address, ssh keypairs, etc. GitLab CI uses that variables to remotely push the new code to the servers.

=== Git Hooks ===

On servers there is a post-update git hook that runs the deployment tasks (collectstatic, reload gunicorn, etc), on each push.

MediaWiki:Spam-whitelist

2018-04-05T09:03:30Z

Comzeradd: whitelist aliexpress

# <pre>
# External URLs matching this list will *not* be blocked even if they would
# have been blocked by blacklist entries.
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts inside URLs

aliexpress\.com

#</pre>

Adjusting the SatNOGS Client

2018-03-17T11:53:14Z

Comzeradd: Fix link

(This page is a port of [https://community.libre.space/t/how-to-do-some-client-adjustments/1604/1 DL4PD's excellent post] to the SatNOGS forum.)

== Prerequisites / dependencies ==

This page assumes:

* you've read all the [[Get Started|Getting Started]] page, as well as the pages linked under "Build" and "Operate" on the [[Main Page]]
* you've already made your [[Operation|first observations]] and have some waterfalls in the [[Network]]
* you've installed [http://gqrx.dk/download install gqrx] on your local computer.

== SatNOGS station adjustments ==

Now you've come to a point where you want to know how well your station is performing. The first step is to determine your frequency offset.

To start, please connect to your Raspberry Pi's local web interface. By default the URL is something like "http://192.168.0.5:5000"; you'll need to figure out what it is for your client. In the upper right corner there is a big green button where you can set your ground station in standalone mode.

Here's how it looks in network mode:

<p>[[File:SatNOGS_local_network_mode.png|center|600px]]</p>

And here's how it looks when it's switched to standalone mode:

<p>[[File:SatNOGS_local_standalone_mode.png|center|600px]]</p>

{{Message|
* Do not forget to set this back to network mode when done with your adjustments!
* While your station is in standalone mode, no observations from the SatNOGS network will be executed!}}

After setting to standalone mode, please SSH to your SatNOGS Pi with your well-known user account; by default, this is the user "pi". After successful authorization you will see a prompt like this:

<pre>
Linux satnogs190-dev 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Jan 12 07:34:11 2018 from 192.168.10.35
pd@satnogs190-dev:~ $
</pre>

Now go ahead and start the "RTL SDR spectrum server":

$ rtl_tcp -a 0.0.0.0

If everything is fine, you will get an output like this:

<pre>
Found 1 device(s):
0: Generic, RTL2832U, SN: 77771111153705700

Using device 0: Generic RTL2832U
Found Rafael Micro R820T tuner
[R82XX] PLL not locked!
Tuned to 100000000 Hz.
listening...

Use the device argument 'rtl_tcp=0.0.0.0:1234' in OsmoSDR (gr-osmosdr) source to receive samples in GRC and control rtl_tcp parameters (frequency, gain, ...). No further output will be generated until you connect to this server. Hitting C-c will stop it and the command line appears.
</pre>

{{Message|You will have to stop this server if you want to go back to network mode - do not forget about this!}}

Now go ahead and start gqrx:

<p>[[File:Startup_gqrx.png|center|600px]]</p>

You will have to go to the setup menu, either by clicking on the "harde" symbol, or navigating through the menu item called "File -> I/O Devices"

<p>[[File:Gqrx_io_configuration.png|center]]</p>

Click on "Device" and chose "RTL-SDR Spectrum Server"
Edit "Device string" to match your Pi's IP address, Port defaults to 1234,
which is the same as the default setting for your server you just started on
the Pi.
Set "Input Rate" to something network friendly - we do not need the whole spectrum the RTL SDR is able to convert. 1,8 MSPS (1800000) should be OK
Depending on this setting your network will get very busy. Using wireless LAN is not recommended. Every sample has a data size of 16 bits, so the previous setting of 1,8MSPS/s results in a network load of 28,8 MBit/s:

<pre>1,8 MSPS * 16 bit/s = 28,8 MBit/s</pre>

"Audio Output -> Device" and "-> Sample rate" should be set by default,
values on average soundcards would be something like "Default, 48 kHz"
Close the dialogue by clicking "OK"
Your RTL-SDR spectrum server on the Pi should now show up a connection from
your computer running gqrx.

<pre>
client accepted!
set gain mode 1
set agc mode 0
set direct sampling 0
Disabled direct sampling mode
set offset tuning 0
set sample rate 960000
ll+, now 1
ll+, now 2
set freq correction 42
set freq 144500000
set gain mode 0
set agc mode 1
set gain 0
set freq 145814000
ll-, now 0
ll+, now 1
ll+, now 2
ll+, now 3
ll+, now 4
ll+, now 5
ll+, now 6
ll+, now 7
ll+, now 8
ll+, now 9
ll+, now 10
ll+, now 11
ll+, now 12
ll+, now 13
</pre>

The only thing left now is to "Start DSP" - from the menu item "File", by hitting C-d or simply clicking the Play-Button.

<p>[[File:Gqrx_running.png|center|600px]]</p>

Go for a known local HAM radio repeater or a CW beacon transmitter and set your demodulator accordingly. Narrow Band FM or CW is best to discover ppm error offset, which is the frequency offset in parts per million (ppm) which is always there with standard RTL-SDR dongles. It is also highly temperature dependent, so one might have to re-evaluate this from time to time. Enter the known frequency of your chosen transmitter (NFM repaeter or CW beacon). I have chosen a very known CW beacon just some km away from my home: ON4VHF on 144.718000 MHz. Walk through the tab called "Receiver options" and change the settings to fit the beacon: "Filter width Normal", "Filter shape Normal", "Mode CW-L", "AGC Medium". Set Squelch to something low, so you can hear noise from your speakers. Maybe you have to Adjust the audio "Gain" to something like "0.0 dB". You can adjust this to fit your needs to hear noise. With ppm error, which is default, set to 0.0 ppm, one can just guess where your receiver is listening. Anyway, just set it to 144.718000 MHz and try to find your beacon. You can see the result for my RTL SDR dongle down here:

<p>[[File:Gqrx_ppm-error_offset.png|center|600px]]</p>

Now got to the tab called "Input controls" and find an input field called "Freq. correction". By default this should show "0,0 ppm". Set frequency back to your beacons transmit frequency. After this you have to increase the Freq. correction value as long until you can hear the beacon. Now zoom into the panorama by locating your mouse pointer in the range where the frequency values are printed below the panorama, just above the waterfall. Try to fit the Freq. correction value as good as possible, that your receivers red indication line is just in the middle of the transmitters bandwidth.

<p>[[File:Gqrx_ppm-error_corrected.png|center]]</p>

Now write down the evaluated ppm correction value and exit gqrx as well as the RTL SDR spectrum server. In the command line now available start satnogs-setup:

$ sudo satnogs-setup

Navigate to "Advanced -> SATNOGS_PPM_ERROR" and enter the new value.

<p>[[File:Fcecd26ca08cf3d23dffce719ef1dd13a4f7109d.png|center]]</p>

Exit the satnogs-setup with "Back", then "Apply Configuration" (this might take a while) and "Back".

You are done with frequency offset correction.

{{Message|With gqrx, you get a nice tool to do some SDR stuff by the way. Just play around a bit and get familiar with all that stuff. Just keep in mind that, as long as you run the RTL SDR Spectrum server or you have set your client into standalone mode, nothing is done from network.}}

== Enhancements ==

=== Waterfall color improvements ===

To get some nicer waterfalls one has to dig into waterfall plotting script. This is a static one and, so far, cannot be configured through satnogs-setup. Anyway: there is no magic behind it and one can understand what the changes are once you have seen them.

Log into the Pi and start at making a copy of /usr/share/satnogs/scripts/satnogs_waterfall.gp, just in case:

$ cp /usr/share/satnogs/scripts/satnogs_waterfall.gp ~/.

Now you can start editing the script:

$ sudo nano /usr/share/satnogs/scripts/satnogs_waterfall.gp

Search for a line starting with cbtics:

# Spectravue palette and scale
set cbtics (-110, -105, -100, -95, -90, -85, -80, -75, -70, -65, -60, -55, -50, -55, -40)

Comment it out by adding a #, copy, paste and edit that new line that it matches something like this:

# Spectravue palette and scale
#set cbtics (-110, -105, -100, -95, -90, -85, -80, -75, -70, -65, -60, -55, -50, -55, -40)
set cbtics (-90, -85, -80, -75, -70, -65, -60, -55, -50, -55, -45, -40, -35, -40, -25)

Now go ahead and find a line with cbrange:

set ylabel 'Time (seconds)'
set cbrange [-100:-50]

I guess, one already gets the point - change cbrange to match the new cbtics:

set ylabel 'Time (seconds)'
#set cbrange [-100:-50]
set cbrange [-85:-35]

Save the file and you are done. Schedule some observations and watch the new colors. Maybe you can just improve it a little more but keep in mind: always keep a bit of the noise floor into the waterfalls, so you can see the whole signals dynamic range. I love it, when there are only a few dots of the noise.

Operation

2018-03-17T11:51:12Z

Comzeradd: Remove production wording

__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''
</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
|}

Main Page

2018-03-17T11:49:22Z

Comzeradd:

__NOTOC__
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>[[File:Satnogs_imagemap.png|center]]</p>
<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>
<p>[[Intro|Intro to SatNOGS]]</p>
<p>[[Ground Stations|Intro to ground stations]]</p>
<p>[[Glossary]]</p>
</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>
<p>[[Get_Started|Learn how to get started]]</p>
<p>[[Build|Build a ground station]]</p>
<p>[[Rotators|Rotators]]</p>
<p>[[Antennas|Antennas]]</p>
<p>[[Radio|Signal Reception]]</p>
</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>
<p>[[Network|SatNOGS Network]]</p>
<p>[[Operation|Scheduling your first observation and operating your station]]</p>
<p>[[Adjusting the SatNOGS Client|Tuning and adjusting your station]]</p>
<p>[[Satnogs DB]]</p>
<p> </p>
</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>
<p>[[Software contribution]]</p>
<p>[[Provide documentation]]</p>
<p>[[Satnogs DB]]</p>
<p>[[Troubleshooting|Troubleshooting]]</p>
<p>[[Get_In_Touch|Get in touch and ask for help]]</p>
<p> </p>
</div>

Main Page

2018-03-17T11:49:06Z

Comzeradd: Remove production wording

__NOTOC__
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>[[File:Satnogs_imagemap.png|center]]</p>
<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>
<p>[[Intro|Intro to SatNOGS]]</p>
<p>[[Ground Stations|Intro to ground stations]]</p>
<p>[[Glossary]]</p>
</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>
<p>[[Get_Started|Learn how to get started]]</p>
<p>[[Build|Build a ground station]]</p>
<p>[[Rotators|Rotators]]</p>
<p>[[Antennas|Antennas]]</p>
<p>[[Radio|Signal Reception]]</p>
</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>
<p>[[SatNOGS Network]]</p>
<p>[[Operation|Scheduling your first observation and operating your station]]</p>
<p>[[Adjusting the SatNOGS Client|Tuning and adjusting your station]]</p>
<p>[[Satnogs DB]]</p>
<p> </p>
</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>
<p>[[Software contribution]]</p>
<p>[[Provide documentation]]</p>
<p>[[Satnogs DB]]</p>
<p>[[Troubleshooting|Troubleshooting]]</p>
<p>[[Get_In_Touch|Get in touch and ask for help]]</p>
<p> </p>
</div>

SatNOGS Network

2018-03-17T11:48:38Z

Comzeradd: Comzeradd moved page Network (Production) to Network: Remove development documentation from the wiki

==Scope==

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]

==Getting started==

* Head to https://network.satnogs.org/accounts/signup/ to create a new account
* Verify your email

Now you're ready to create a ground station!

===Creating a ground station===

* On your user page, click on "Add Ground Station"
* Fill out all the information. You'll need to provide some essential information about your ground station:

<ul>
<li>Where is the station? We'll need the height above ground level and [https://en.wikipedia.org/wiki/Maidenhead_Locator_System maidenhead locator]</li>
<li>Is the antenna static, or does it have a rotator?</li>
<li>What type of antennas does the station have?</li>
</ul>

All this information is then saved by the network, and used to determine which satellites can be received by your station. This will help other users to schedule passes on your ground station, but it can also help you improve your station. For example, perhaps you would like to receive the latest [https://en.wikipedia.org/wiki/Automatic_picture_transmission NOAA APT weather images] which are VHF transmissions. You could schedule an observation with your ground station and multiple other ground stations in order to determine if your set up has comparable performance. Without the station detail, this would not be possible.

* Finally, head to your client and [[Raspberry_Pi_3#Setup|complete its setup]], using the information you supplied on the Network, plus the API key and the ID you were assigned.

The image below shows the web page for a typical ground station:
<p>[[File:Dev_ground_station.PNG|center|800px]]</p>

===Observing a pass===

The central point of the system is the ability to schedule a pass. You'll find all the information about scheduling and how to assess the quality of the observation as part of [[Operation|scheduling your first observation]].

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

==Moving out of testing==

The Network 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 in 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.

==What's 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 test the Network application in our [[Development Environment|development environment]], and [[Software contribution|always welcome python/javascript developers to help us]]!

Network (Production)

2018-03-17T11:48:38Z

Comzeradd: Comzeradd moved page Network (Production) to Network: Remove development documentation from the wiki

#REDIRECT [[Network]]

SatNOGS Network

2018-03-17T11:48:00Z

Comzeradd: Remove production wording

File:SatNOGS client screenshot.png

2017-12-23T19:50:29Z

Comzeradd: Comzeradd uploaded a new version of File:SatNOGS client screenshot.png

Screenshot of status page from SatNOGS client

Main Page

2017-12-04T12:26:20Z

Comzeradd: Fit boxes to one row

__NOTOC__
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>[[File:Satnogs_imagemap.png|center]]</p>
<div style="border-radius: 3px; width: 16%; 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>
<p>[[Intro|Intro to SatNOGS]]</p>
<p>[[Ground Stations|Intro to ground stations]]</p>
<p>[[Glossary]]</p>
</div>
<div style="border-radius: 3px; width: 16%; 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>
<p>[[Get_Started|Learn how to get started]]</p>
<p>[[Build|Build a ground station]]</p>
<p>[[Rotators|Rotators]]</p>
<p>[[Antennas|Antennas]]</p>
<p>[[Receiver|Signal Reception]]</p>
</div>
<div style="border-radius: 3px; width: 16%; 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>
<p>[[Development Environment]]</p>
<p>[[Production Environment]]</p>
<p>[[Satnogs DB]]</p>
<p> </p>
</div>
<div style="border-radius: 3px; width: 16%; 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>
<p>[[Software contribution]]</p>
<p>[[Provide documentation]]</p>
<p>[[Satnogs DB]]</p>
<p>[[Troubleshooting|Troubleshooting]]</p>
<p>[[Get_In_Touch|Get in touch and ask for help]]</p>
<p> </p>
</div>

Operation

2017-11-18T17:39:31Z

Comzeradd: Add permissions matrix

__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.}}

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

Fedora Installation

2017-10-11T08:28:53Z

Comzeradd: Move fedora docs to wiki

{{MARKDOWN}}

## Installing SatNOGS on a Raspberry Pi 3

This tutorial assumes the following:

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

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

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

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

### 1. Prepare Raspberry Pi

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

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

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

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

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

**Step 1.6:** Update fedora package to the latest version by running::

sudo dnf -y update

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

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

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

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

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

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

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

sudo systemctl enable redis.service
sudo systemctl start redis.service

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

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

* Then run::

sudo chmod +x /etc/cron.daily/satnogs

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

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

* If you used the server image run::

sudo firewall-cmd --zone=FedoraServer --add-service=satnogs --permanent
sudo firewall-cmd --zone=FedoraServer --add-service=satnogs

* Or for the minimal image::

sudo firewall-cmd --zone=public --add-service=satnogs --permanent
sudo firewall-cmd --zone=public --add-service=satnogs

### 2. Install gr-satnogs

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

**Step 2.1:**: Install gr-satnogs by running the next commands::

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

### 3. Install satnogs-client

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

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

sudo pip install satnogsclient

### 4. Configure satnogs-client

SatNOGS Client needs some configuration before running:

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

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

.. _optional_settings:

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

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

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

**Step 4.3:** Other optional settings:

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

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

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

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

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

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

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

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

### 5. Prepare SDR Device

In order to have access and use SDR device you need to follow the next steps for you device:

^^^^^^^^^^^^
1. USRP B200
^^^^^^^^^^^^
**Step 5.1.1:** Install uhd package::

sudo dnf install -y uhd

**Step 5.1.2:** Download uhd images::

sudo /usr/bin/uhd_images_downloader

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

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

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

* Replace ACL reference::

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

* Reload udev rules::

sudo udevadm control --reload-rules

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

uhd_find_devices

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

groups

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

sudo usermod -aG dialout satnogs

^^^^^^^^^^^^
2. RTL-SDR
^^^^^^^^^^^^
**Step 5.2.1:** As the access will be only by ssh and not by direct login we are not be able to access SDR device through `Access Control List(ACL) <https://en.wikipedia.org/wiki/Access_control_list>`_, so we need to setup the appropriate udev rules by following the next steps:

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

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

* Replace ACL reference and change group ownership::

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

* Reload udev rules::

sudo udevadm control --reload-rules

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

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

groups

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

sudo usermod -aG dialout satnogs

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

### 6. Run satnogs-client

^^^^^^^^^^^
1. Manually
^^^^^^^^^^^
In order to manually run satnogs-client you need to follow the next steps:

**Step 6.1.1:** Export all the environment variables::

source .env

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

rotctld -m 202 -r /dev/ttyACM0 -s 19200 &

**Step 6.1.3:** Run the SatNOGS Client::

satnogs-client

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

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2. Automaticaly with Supervisord
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

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

**Step 6.2.1:** Install supervisord::

sudo dnf install -y supervisor

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

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

**Step 6.2.3:** Configure supervisord for rotctld

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

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

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

**Step 6.2.4:** Configure supervisord for satnogs-client

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

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

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

**Step 6.2.5:** Reloading supervisord to get the new configuration::

sudo systemctl enable supervisord.service
sudo systemctl start supervisord.service

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

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

sudo supervisorctl reload

^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3. Automaticaly with Systemd
^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

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

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

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

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

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

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

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

[Install]
WantedBy=multi-user.target

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

**Step 6.3.3:** Enable and start satnogs-client.service::

sudo systemctl enable satnogs-client.service
sudo systemctl start satnogs-client.service

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

journalctl -u satnogs-client.service

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

journalctl -f -u satnogs-client.service

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

sudo systemctl stop satnogs-client.service
sudo systemctl start satnogs-client.service

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

sudo systemctl daemon-reload

Raspberry Pi

2017-10-02T15:44:02Z

Comzeradd: Remove Fedora section

{{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].

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

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

Raspberry Pi

2017-10-02T15:39:45Z

Comzeradd: /* Download */ point to tags page for images

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

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

Operation

2017-10-02T14:08:22Z

Comzeradd: Minor formatting changes

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

G-5500

2017-10-02T14:02:04Z

Comzeradd: /* Control Electronics */ replace repo link with gitlab

{{Template:Rotator
|Rotator-Name=Yaesu G-5500
|image=G5500.jpg
|type= Az/El
|cost=900 USD
|status= Production
|source-repo=N/A
|documentation= http://www.yaesu.com/downloadFile.cfm?FileID=8814&FileCatID=155&FileName=G%2D5500%5FIM%5FENG%5FE12901004.pdf&FileContentType=application%2Fpdf
}}

== Intro ==

G-5000 AZ/EL is a rotator built by Yaesu.

==Specifications==

The Azimuth Rotator features a turning range of 450°, while the Elevation Rotator has a rotation range of 180°.

== Control Electronics ==

Yaesu sells a computer control device, the G-232A. Since then many alternative, more cost-efficient alternatives have appeared on the home brew market. The SatNOGS project has an arduino shield that, when combined with K3NG Arduino code, can act as a Yaesu G-5500 controller for little cost. See the [https://gitlab.com/librespacefoundation/satnogs/g5500-ardushield arduino shield].

== Documentation ==

See Yaesu's documentation at http://www.yaesu.com/downloadFile.cfm?FileID=8814&FileCatID=155&FileName=G%2D5500%5FIM%5FENG%5FE12901004.pdf&FileContentType=application%2Fpdf

[[Category:Rotator]]

Main Page

2017-10-02T13:40:38Z

Comzeradd: align diagram to center

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|800px|]]

<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>
<p>[[Intro|Intro to SatNOGS]]</p>
<p>[[Ground Stations|Intro to ground stations]]</p>
<p>[[Glossary]]</p>
</div>
<div style="border-radius: 3px;width:25%;height:150px;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>
<p>[[Get_Started|Learn how to get started]]</p>
<p>[[Build|Build a ground station]]</p>
<p>[[Operation|Operate a ground station]]</p>
<p>[[Troubleshooting|Troubleshooting]]</p>
</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>
<p>[[GS Software|Software contribution]]</p>
<p>[[Provide documentation]]</p>
<p>[[Satnogs DB]]</p>
<p></p>
</div>

Socis 2016 ideas

2017-08-29T10:21:04Z

Comzeradd: add markdown tag

{{MARKDOWN}}

These ideas were contributed by our developers and users for SOCIS 2016. Some of them may be rough. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are it's [forum](http://community.satnogs.org) and it's [github repositories](http://github.com/satnogs).

ESA SOCIS summer of code is an European Space Agency initiative, we encourage every party interested to visit it's [website](http://sophia.estec.esa.int/socis) and read it's [FAQ](http://sophia.estec.esa.int/socis/faq)

Instructions
====
Students wishing to participate in SOCIS must realise this is more than a mere formality. You will be required to produce code for Libre Space Foundation projects in 3 months.

You don't have to be a proven developer -- in fact, this whole program is meant to facilitate joining Open Source communities. However, experience in coding and/or experience with Python libraries and applications is welcome.

You should start familiarizing yourself with the components that you plan on working on before the start date. LSF developers are available on the community site and on IRC for help.
Recommended steps
=====
* Read ESA's instructions for participating
* Take a look at the list of ideas
* Come up with project that you're interested in
* Write a first draft proposal and get someone to review it for you
* Submit it using Google's web interface

Coming up with an interesting idea is probably the most difficult part of all. It should be something interesting for **SatNOGS**, for **Open Source in Space** and particularly for **you**.

Finding out what the most pressing issues are in the projects you're interested in is a good start.Learning the codebase and even submitting issues and identifying bugs is also a good way to start. We recommend strongly doing that and we will look favorably on applications from students who have started to act like Open Source developers.

***

# Software Projects

## [SatNOGS Network](https://github.com/satnogs/satnogs-network)
### Data Dashboards using SatNOGS observation data/metadata
* **Description** Supply an overview of the observation data/metadata collected instead of the detailed view currently available
* **Skills needed** Django/Python , HTML, CSS3, Javascript
* **Expected results** Create standards based user facing dashboards for SatNOGS recorded data and metadata to provide an overview of a SatNOGS observation.
* **Mentor**: @comzeradd

### Concatenate observational data
* **Description**: An observer should be able to access a concatenated view of an observation that is calculated (and compiled) by multiple data from different ground stations. Still SatNOGS Network must be able to provide a single url page for a single observation part (ie by one ground station pass).
* **Skills needed**: Django/Python, HTML, CSS3, Javascript.
* **Expected results**: Single URL for a single observation part to allow sharing of data, page must be accessible in all modern browsers
* **Mentor**: @comzeradd

## [SatNOGS Client](https://github.com/satnogs/satnogs-client)
### Build a web based controller able to control the SatNOGS client
* **Description**: Expand the current web interface of satnogs-client with a web based controller to allow users to connect to their rotator using a browser without the need to connect to the internet.
* **Skills needed**: Python, Flask
* **Expected results**: An embeddable web application able to control SatNOGS client via a web browser
* **Mentor**: @jinxcat

### Package SatNOGS client for different distributions
* **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
* **Skills needed**: Packaging on major distributions.
* **Expected results**: Released and submitted upstream packages on major distributions.
* **Mentor**: @axilleas

## SatNOGS Infrastructure
### Improve logging and monitoring
* **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Logs and Monitoring capabilities for the Network administrators
* **Mentor**: @axilleas

### Improve distributed storage of observation data
* **Description**: SatNOGS observation data must be able to be stored in a distributed manner
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: A distributed storage option for observation data
* **Mentor**: @jinxcat

### Add error rate and karma policies for SatNOGS clients
* **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Error and karma policies applied to observation job prioritization
* **Mentor**: @jinxcat

***

# [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)

## [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)

### Closed loop system with feedback (encoders, stepper motors)
* **Description**: Design a closed loop system with positioning feedback, based on the existing tracker design, as an alternative to the current setup.
* **Skills needed**: Electronics, Arduino, PID tuning, Encoder circuits
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.
* **Mentor**: @zisi

### Design and implement a stand alone open source stepper controller
* **Description**: Create a stand alone open source stepper controller to modularize our electronics. Use an established protocol to communicate with our microprocessor (e.g. I2C).
* **Skills needed**: Electronics, Arduino, Stepper controllers, I2C ,SPI or 1Wire
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.
* **Mentor**: @zisi

### Arduino Firmware restructure with tests and fixes
* **Description**: Rewriting the current Arduino firmware to resolve overflow errors and implement tests for extreme conditions and use cases.
* **Skills needed**: Arduino, Embedded programming, Embedded debugging, Algorithm Design
* **Expected results**: A new Arduino firmware with less function overflow errors compared to the current and tests.
* **Mentor**: @zisi

### Optimize rotor movement algorithm
* **Description**: Implement an improved and optimized rotor movement algorithm, to minimize path (length and time), apply tracking continuity (on extreme points) and apply instrumental limitations (cable twisting, horizon limits, extreme points, extreme conditions)
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.
* **Mentor**: @papamat

### Homing and setup bootstrap functions, testing functions
* **Description**: Design and implement a setup bootstrapping (first-run) and testing of ground station suite.
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.
* **Mentor**: @zisi

[[Category:SOC]]

GSOC 2015 Ideas

2017-08-29T10:20:51Z

Comzeradd: add markdown tag

{{MARKDOWN}}

These ideas were contributed by our developers and users for [Google Summer of Code 2015](http://www.google-melange.com/gsoc/homepage/google/gsoc2015). Some of them may be rough. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are it's [forum](http://community.satnogs.org) and it's [github repositories](http://github.com/satnogs). All interested students must apply their proposals at info@satnogs.org if selected they will be assigned two mentors (a primary and alternative mentor).

***

# Software Projects

## [SatNOGS Network](https://github.com/satnogs/satnogs-network)
### Data Dashboards using SatNOGS observation data/metadata
* **Description** Supply an overview of the observation data/metadata collected instead of the detailed view currently available
* **Skills needed** Django/Python , HTML, CSS3, Javascript
* **Expected results** Create standards based user facing dashboards for SatNOGS recorded data and metadata to provide an overview of a SatNOGS observation.

### Concatenate observational data
* **Description**: An observer should be able to access a concatenated view of an observation that is calculated (and compiled) by multiple data from different ground stations. Still SatNOGS Network must be able to provide a single url page for a single observation part (ie by one ground station pass).
* **Skills needed**: Django/Python, HTML, CSS3, Javascript.
* **Expected results**: Single URL for a single observation part to allow sharing of data, page must be accessible in all modern browsers

## [SatNOGS DB](https://github.com/satnogs/satnogs-db)
### Transition our proof of concept SatNOGS DB to a working product.
* **Description** Design and assist implementing a transition of the SatNOGS DB project from a working prototype to a product
* **Skills needed** Angular.js CouchDB
* **Expected results** SatNOGS DB must be able to accept data from crowd-sourcing and expose them in an API.

### Connect SatNOGS network to DB to get up-to-date transponder information.
* **Description**: Design, and implement a SatNOGS Network to SatNOGS DB connection (via an open API) to populate SatNOGS Network with up to date transponder information and SatNOGS DB with up to date tle satellite listings.
* **Skills needed**: Django, AngularDB
* **Expected results**: SatNOGS DB must be able to populate SatNOGS Network with all transponder data.

## [SatNOGS Client](https://github.com/satnogs/satnogs-client)
### Build a web based controller able to control the SatNOGS client
* **Description**: Build a web based controller to allow users to connect to the SatNOGS client using a browser without the need to connect to the internet.
* **Skills needed**: HTML5, OpenWRT, JS, CSS3
* **Expected results**: An embeddable web application able to control SatNOGS client via a web browser

### Package SatNOGS client for different distributions
* **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
* **Skills needed**: Packaging on major distributions.
* **Expected results**: Released and submitted upstream packages on major distributions.

## SatNOGS Infrastructure
### Improve logging and monitoring
* **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Logs and Monitoring capabilities for the Network administrators

### Improve distributed storage of observation data
* **Description**: SatNOGS observation data must be able to be stored in a distributed manner
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: A distributed storage option for observation data

### Add error rate and karma policies for SatNOGS clients
* **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Error and karma policies applied to observation job prioritization

### Docker-ise SatNOGS setup (for both client and network)
* **Description**: To provide a streamlined setup process for interested parties a Docker image for SatNOGS client and SatNOGS network should be created.
* **Skills needed**: Docker, Python
* **Expected results**: Fully functional Docker images for SatNOGS Client Network.

***

# [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)

## [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)

### Closed loop system with feedback (encoders, stepper motors)
* **Description**: Design a closed loop system with positioning feedback, based on the existing tracker design, as an alternative to the current setup.
* **Skills needed**: Electronics, Arduino, PID tuning, Encoder circuits
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.

### Design and implement a stand alone open source stepper controller
* **Description**: Create a stand alone open source stepper controller to modularize our electronics. Use an established protocol to communicate with our microprocessor (e.g. I2C).
* **Skills needed**: Electronics, Arduino, Stepper controllers, I2C ,SPI or 1Wire
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.

### Arduino Firmware restructure with tests and fixes
* **Description**: Rewriting the current Arduino firmware to resolve overflow errors and implement tests for extreme conditions and use cases.
* **Skills needed**: Arduino, Embedded programming, Embedded debugging, Algorithm Design
* **Expected results**: A new Arduino firmware with less function overflow errors compared to the current and tests.

### Implement or extend rotor control protocols in order to handle additional commands and errors
* **Description**: Additional errors and commands should be implemented to the current control protocols used in Easycomm2 and rotctrl
* **Skills needed**: Serial communications, Arduino, Embedded programming, Embedded debugging
* **Expected results**: Implementing or extending rotor control protocols which will handle addition commands and errors.

### Optimize rotor movement algorithm
* **Description**: Implement an improved and optimized rotor movement algorithm, to minimize path (length and time), apply tracking continuity (on extreme points) and apply instrumental limitations (cable twisting, horizon limits, extreme points, extreme conditions)
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.

### Homing and setup bootstrap functions, testing functions
* **Description**: Design and implement a setup bootstrapping (first-run) and testing of ground station suite.
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.

[[Category:SOC]]

GSOC 2016 Ideas

2017-08-29T10:20:42Z

Comzeradd: add markdown tag

{{MARKDOWN}}

These ideas were contributed by our developers and users for [Google Summer of Code 2016](https://summerofcode.withgoogle.com). Some of them may be rough. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are it's [forum](http://community.satnogs.org) and it's [github repositories](http://github.com/satnogs).

Instructions
====
Students wishing to participate in Summer of Code must realise this is more than a mere formality. You will be required to produce code for Libre Space Foundation projects in 3 months.

You don't have to be a proven developer -- in fact, this whole program is meant to facilitate joining Open Source communities. However, experience in coding and/or experience with Python libraries and applications is welcome.

You should start familiarizing yourself with the components that you plan on working on before the start date. LSF developers are available on the community site and on IRC for help.
Recommended steps
=====
* Read Google's instructions for participating
* Take a look at the list of ideas
* Come up with project that you're interested in
* Write a first draft proposal and get someone to review it for you
* Submit it using Google's web interface

Check the KDE's [Student Proposal Guidelines](https://community.kde.org/GSoC#Student_proposal_guidelines) for more hints on what your application should look like.

Coming up with an interesting idea is probably the most difficult part of all. It should be something interesting for **LSF**, for **Open Source in Space** and particularly for **you**.

Finding out what the most pressing issues are in the projects you're interested in is a good start.Learning the codebase and even submitting issues and identifying bugs is also a good way to start. We recommend strongly doing that and we will look favorably on applications from students who have started to act like Open Source developers.

***

# Software Projects

## [SatNOGS Network](https://github.com/satnogs/satnogs-network)
### Data Dashboards using SatNOGS observation data/metadata
* **Description** Supply an overview of the observation data/metadata collected instead of the detailed view currently available
* **Skills needed** Django/Python , HTML, CSS3, Javascript
* **Expected results** Create standards based user facing dashboards for SatNOGS recorded data and metadata to provide an overview of a SatNOGS observation.
* **Mentor**: @comzeradd

### Concatenate observational data
* **Description**: An observer should be able to access a concatenated view of an observation that is calculated (and compiled) by multiple data from different ground stations. Still SatNOGS Network must be able to provide a single url page for a single observation part (ie by one ground station pass).
* **Skills needed**: Django/Python, HTML, CSS3, Javascript.
* **Expected results**: Single URL for a single observation part to allow sharing of data, page must be accessible in all modern browsers
* **Mentor**: @comzeradd

## [SatNOGS Client](https://github.com/satnogs/satnogs-client)
### Build a web based controller able to control the SatNOGS client
* **Description**: Expand the current web interface of satnogs-client with a web based controller to allow users to connect to their rotator using a browser without the need to connect to the internet.
* **Skills needed**: Python, Flask
* **Expected results**: An embeddable web application able to control SatNOGS client via a web browser
* **Mentor**: @jinxcat

### Package SatNOGS client for different distributions
* **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
* **Skills needed**: Packaging on major distributions.
* **Expected results**: Released and submitted upstream packages on major distributions.
* **Mentor**: @axilleas

## SatNOGS Infrastructure
### Improve logging and monitoring
* **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Logs and Monitoring capabilities for the Network administrators
* **Mentor**: @axilleas

### Improve distributed storage of observation data
* **Description**: SatNOGS observation data must be able to be stored in a distributed manner
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: A distributed storage option for observation data
* **Mentor**: @jinxcat

### Add error rate and karma policies for SatNOGS clients
* **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Error and karma policies applied to observation job prioritization
* **Mentor**: @jinxcat

## [Diactoros Firmware](https://github.com/librespacefoundation/diactoros)
### Enhance diactoros firmware
* **Description** Implement baud rate negotiation for ground-satellite communications based on link status
* **Skills needed** C, RF
* **Expected results**: Significant improvement in data rate of satellite to ground communications
* **Mentor**: @manostheodoridis

***

# [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)

## [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)

### Closed loop system with feedback (encoders, stepper motors)
* **Description**: Design a closed loop system with positioning feedback, based on the existing tracker design, as an alternative to the current setup.
* **Skills needed**: Electronics, Arduino, PID tuning, Encoder circuits
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.
* **Mentor**: @zisi

### Design and implement a stand alone open source stepper controller
* **Description**: Create a stand alone open source stepper controller to modularize our electronics. Use an established protocol to communicate with our microprocessor (e.g. I2C).
* **Skills needed**: Electronics, Arduino, Stepper controllers, I2C ,SPI or 1Wire
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.
* **Mentor**: @zisi

### Arduino Firmware restructure with tests and fixes
* **Description**: Rewriting the current Arduino firmware to resolve overflow errors and implement tests for extreme conditions and use cases.
* **Skills needed**: Arduino, Embedded programming, Embedded debugging, Algorithm Design
* **Expected results**: A new Arduino firmware with less function overflow errors compared to the current and tests.
* **Mentor**: @zisi

### Optimize rotor movement algorithm
* **Description**: Implement an improved and optimized rotor movement algorithm, to minimize path (length and time), apply tracking continuity (on extreme points) and apply instrumental limitations (cable twisting, horizon limits, extreme points, extreme conditions)
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.
* **Mentor**: @papamat

### Homing and setup bootstrap functions, testing functions
* **Description**: Design and implement a setup bootstrapping (first-run) and testing of ground station suite.
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.
* **Mentor**: @zisi

[[Category:SOC]]

GSOC 2017 Ideas

2017-08-29T10:20:31Z

Comzeradd: add markdown tag

{{MARKDOWN}}

These ideas were contributed by our developers and users for [Google Summer of Code 2017](https://summerofcode.withgoogle.com). Some of them may be in a rough state, but they can certainly be refined. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are its [forum](http://community.satnogs.org) and its [github repositories](http://github.com/satnogs).

Instructions
====
Students wishing to participate in Summer of Code must realise this is more than a mere formality. You will be required to produce code for Libre Space Foundation projects in 3 months.

You don't have to be a proven developer, in fact, this whole program is meant to facilitate joining Open Source communities. However, experience in coding and/or experience with Python libraries and applications is welcome.

You should start familiarizing yourself with the components that you plan on working on before the start date. LSF developers are available on the community site and on IRC for help.

Recommended steps
=====
* Read Google's instructions for participating
* Take a look at the list of ideas
* Come up with project that you're interested in
* Write a first draft proposal and get someone to review it for you
* Submit it using Google's web interface

Check the KDE's [Student Proposal Guidelines](https://community.kde.org/GSoC#Student_proposal_guidelines) for more hints on what your application should look like.

Coming up with an interesting idea is probably the most difficult part of all. It should be something interesting for **LSF**, for **Open Source in Space** and particularly for **you**.

Finding out what the most pressing issues are in the projects you're interested in is a good start. Learning the codebase and even submitting issues and identifying bugs is also a good way to start. We recommend strongly doing that and we will look favorably on applications from students who have started to act like Open Source developers.

***

# Software Projects

## [SatNOGS DB](https://github.com/satnogs/satnogs-db)
### Enhance frontend suggestions and moderation capabilities
* **Description**: Supply the ability for users to suggest new satellites. Supply the ability to moderators to approve or amend satellite and transmitters suggestions.
* **Skills needed**: Django/Python , HTML, CSS3, Javascript
* **Expected results**: All satellite and transmitters data should be crowdsourced and moderated through a simple UI.
* **Mentor**: @comzeradd

## [SatNOGS Client](https://github.com/satnogs/satnogs-client)
### Build a web based controller able to control the SatNOGS client
* **Description**: Expand the current web interface of satnogs-client with a web based controller to allow users to connect to their rotator using a browser without the need to connect to the internet.
* **Skills needed**: Python, Flask
* **Expected results**: An embeddable web application able to control SatNOGS client via a web browser
* **Mentor**: @jinxcat

### Package SatNOGS client for different distributions
* **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
* **Skills needed**: Packaging on major distributions.
* **Expected results**: Released and submitted upstream packages on major distributions.
* **Mentor**: @axilleas

## SatNOGS Infrastructure
### Improve logging and monitoring
* **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Logs and Monitoring capabilities for the Network administrators
* **Mentor**: @axilleas

### Improve distributed storage of observation data
* **Description**: SatNOGS observation data must be able to be stored in a distributed manner
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: A distributed storage option for observation data
* **Mentor**: @jinxcat

### Add error rate and karma policies for SatNOGS clients
* **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Error and karma policies applied to observation job prioritization
* **Mentor**: @jinxcat

***

# [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)

## [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)
### Title
* **Description**:
* **Skills needed**:
* **Expected results**:
* **Mentor**:

### Title
* **Description**:
* **Skills needed**:
* **Expected results**:
* **Mentor**:

[[Category:SOC]]

Socis 2015 ideas

2017-08-29T10:20:16Z

Comzeradd: add markdown tag

{{MARKDOWN}}

These ideas were contributed by our developers and users. Some of them may be rough. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are it's [forum](http://community.satnogs.org) and it's [github repositories](http://github.com/satnogs). All interested students must apply their proposals at info@satnogs.org if selected they will be assigned two mentors (a primary and alternative mentor).

ESA SOCIS summer of code is an European Space Agency initiative, we encourage every party interested to visit it's [website](http://sophia.estec.esa.int/socis) and read it's [FAQ](http://sophia.estec.esa.int/socis/faq)

***

# Software Projects

## [SatNOGS Network](https://github.com/satnogs/satnogs-network)
### Data Dashboards using SatNOGS observation data/metadata
* **Description** Supply an overview of the observation data/metadata collected instead of the detailed view currently available
* **Skills needed** Django/Python , HTML, CSS3, Javascript
* **Expected results** Create standards based user facing dashboards for SatNOGS recorded data and metadata to provide an overview of a SatNOGS observation.

### Concatenate observational data
* **Description**: An observer should be able to access a concatenated view of an observation that is calculated (and compiled) by multiple data from different ground stations. Still SatNOGS Network must be able to provide a single url page for a single observation part (ie by one ground station pass).
* **Skills needed**: Django/Python, HTML, CSS3, Javascript.
* **Expected results**: Single URL for a single observation part to allow sharing of data, page must be accessible in all modern browsers

## [SatNOGS DB](https://github.com/satnogs/satnogs-db)
### Transition our proof of concept SatNOGS DB to a working product.
* **Description** Design and assist implementing a transition of the SatNOGS DB project from a working prototype to a product
* **Skills needed** Angular.js CouchDB
* **Expected results** SatNOGS DB must be able to accept data from crowd-sourcing and expose them in an API.

### Connect SatNOGS network to DB to get up-to-date transponder information.
* **Description**: Design, and implement a SatNOGS Network to SatNOGS DB connection (via an open API) to populate SatNOGS Network with up to date transponder information and SatNOGS DB with up to date tle satellite listings.
* **Skills needed**: Django, AngularDB
* **Expected results**: SatNOGS DB must be able to populate SatNOGS Network with all transponder data.

## [SatNOGS Client](https://github.com/satnogs/satnogs-client)
### Build a web based controller able to control the SatNOGS client
* **Description**: Build a web based controller to allow users to connect to the SatNOGS client using a browser without the need to connect to the internet.
* **Skills needed**: HTML5, OpenWRT, JS, CSS3
* **Expected results**: An embeddable web application able to control SatNOGS client via a web browser

### Package SatNOGS client for different distributions
* **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
* **Skills needed**: Packaging on major distributions.
* **Expected results**: Released and submitted upstream packages on major distributions.

## SatNOGS Infrastructure
### Improve logging and monitoring
* **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Logs and Monitoring capabilities for the Network administrators

### Improve distributed storage of observation data
* **Description**: SatNOGS observation data must be able to be stored in a distributed manner
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: A distributed storage option for observation data

### Add error rate and karma policies for SatNOGS clients
* **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Error and karma policies applied to observation job prioritization

### Docker-ise SatNOGS setup (for both client and network)
* **Description**: To provide a streamlined setup process for interested parties a Docker image for SatNOGS client and SatNOGS network should be created.
* **Skills needed**: Docker, Python
* **Expected results**: Fully functional Docker images for SatNOGS Client Network.

***

# [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)

## SatNOGS RF components
### LNA design
* **Description**: Design a Low Noise Amplifier to specifically cover the needs of satellite data coverage. VHF, UHF and S-Band should be covered.
* **Skills needed**: RF Electronics design. Filter design, signal theory.
* **Expected results**: Schematic, routing, board design and preferably a sample implementation.

### Diplexer design
* **Description**: Design a Diplexer to specifically cover the need of the SatNOGS Ground Station
* **Skills needed**: RF Electronics design. Filter design, signal theory.
* **Expected results**: Schematic, routing, board design and preferably a a working prototype.

### Polarization switching design for Uda-Yagi antennas
* **Description**: Create a polarization switching design to allow cross Uda-Yagi antenna configuration to switch polarization on the fly.
* **Skills needed**: RF Electronics design. Antenna design, signal theory.
* **Expected results**: Schematic, routing, board design and preferably a a working prototype.

## [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)

### Closed loop system with feedback (encoders, stepper motors)
* **Description**: Design a closed loop system with positioning feedback, based on the existing tracker design, as an alternative to the current setup.
* **Skills needed**: Electronics, Arduino, PID tuning, Encoder circuits
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.

### Design and implement a stand alone open source stepper controller
* **Description**: Create a stand alone open source stepper controller to modularize our electronics. Use an established protocol to communicate with our microprocessor (e.g. I2C).
* **Skills needed**: Electronics, Arduino, Stepper controllers, I2C ,SPI or 1Wire
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.

### Arduino Firmware restructure with tests and fixes
* **Description**: Rewriting the current Arduino firmware to resolve overflow errors and implement tests for extreme conditions and use cases.
* **Skills needed**: Arduino, Embedded programming, Embedded debugging, Algorithm Design
* **Expected results**: A new Arduino firmware with less function overflow errors compared to the current and tests.

### Implement or extend rotor control protocols in order to handle additional commands and errors
* **Description**: Additional errors and commands should be implemented to the current control protocols used in Easycomm2 and rotctrl
* **Skills needed**: Serial communications, Arduino, Embedded programming, Embedded debugging
* **Expected results**: Implementing or extending rotor control protocols which will handle addition commands and errors.

### Optimize rotor movement algorithm
* **Description**: Implement an improved and optimized rotor movement algorithm, to minimize path (length and time), apply tracking continuity (on extreme points) and apply instrumental limitations (cable twisting, horizon limits, extreme points, extreme conditions)
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.

### Homing and setup bootstrap functions, testing functions
* **Description**: Design and implement a setup bootstrapping (first-run) and testing of ground station suite.
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.

[[Category:SOC]]

Repositories Policy

2017-08-29T10:19:44Z

Comzeradd: add markdown tag

{{MARKDOWN}}

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

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

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

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

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

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

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

List of repos with descriptions and maintainers
----

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

Repositories Policy

2017-08-26T13:54:31Z

Comzeradd: Repositories Policy

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

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

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

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

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

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

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

List of repos with descriptions and maintainers
----

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

Category:SOC

2017-08-26T13:53:30Z

Comzeradd: Created page with "Ideas for various "Summer of Code" programs"

Ideas for various "Summer of Code" programs

Socis 2016 ideas

2017-08-26T13:52:50Z

Comzeradd: Socis 2016 ideas

These ideas were contributed by our developers and users for SOCIS 2016. Some of them may be rough. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are it's [forum](http://community.satnogs.org) and it's [github repositories](http://github.com/satnogs).

ESA SOCIS summer of code is an European Space Agency initiative, we encourage every party interested to visit it's [website](http://sophia.estec.esa.int/socis) and read it's [FAQ](http://sophia.estec.esa.int/socis/faq)

Instructions
====
Students wishing to participate in SOCIS must realise this is more than a mere formality. You will be required to produce code for Libre Space Foundation projects in 3 months.

You don't have to be a proven developer -- in fact, this whole program is meant to facilitate joining Open Source communities. However, experience in coding and/or experience with Python libraries and applications is welcome.

You should start familiarizing yourself with the components that you plan on working on before the start date. LSF developers are available on the community site and on IRC for help.
Recommended steps
=====
* Read ESA's instructions for participating
* Take a look at the list of ideas
* Come up with project that you're interested in
* Write a first draft proposal and get someone to review it for you
* Submit it using Google's web interface

Coming up with an interesting idea is probably the most difficult part of all. It should be something interesting for **SatNOGS**, for **Open Source in Space** and particularly for **you**.

Finding out what the most pressing issues are in the projects you're interested in is a good start.Learning the codebase and even submitting issues and identifying bugs is also a good way to start. We recommend strongly doing that and we will look favorably on applications from students who have started to act like Open Source developers.

***

# Software Projects

## [SatNOGS Network](https://github.com/satnogs/satnogs-network)
### Data Dashboards using SatNOGS observation data/metadata
* **Description** Supply an overview of the observation data/metadata collected instead of the detailed view currently available
* **Skills needed** Django/Python , HTML, CSS3, Javascript
* **Expected results** Create standards based user facing dashboards for SatNOGS recorded data and metadata to provide an overview of a SatNOGS observation.
* **Mentor**: @comzeradd

### Concatenate observational data
* **Description**: An observer should be able to access a concatenated view of an observation that is calculated (and compiled) by multiple data from different ground stations. Still SatNOGS Network must be able to provide a single url page for a single observation part (ie by one ground station pass).
* **Skills needed**: Django/Python, HTML, CSS3, Javascript.
* **Expected results**: Single URL for a single observation part to allow sharing of data, page must be accessible in all modern browsers
* **Mentor**: @comzeradd

## [SatNOGS Client](https://github.com/satnogs/satnogs-client)
### Build a web based controller able to control the SatNOGS client
* **Description**: Expand the current web interface of satnogs-client with a web based controller to allow users to connect to their rotator using a browser without the need to connect to the internet.
* **Skills needed**: Python, Flask
* **Expected results**: An embeddable web application able to control SatNOGS client via a web browser
* **Mentor**: @jinxcat

### Package SatNOGS client for different distributions
* **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
* **Skills needed**: Packaging on major distributions.
* **Expected results**: Released and submitted upstream packages on major distributions.
* **Mentor**: @axilleas

## SatNOGS Infrastructure
### Improve logging and monitoring
* **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Logs and Monitoring capabilities for the Network administrators
* **Mentor**: @axilleas

### Improve distributed storage of observation data
* **Description**: SatNOGS observation data must be able to be stored in a distributed manner
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: A distributed storage option for observation data
* **Mentor**: @jinxcat

### Add error rate and karma policies for SatNOGS clients
* **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Error and karma policies applied to observation job prioritization
* **Mentor**: @jinxcat

***

# [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)

## [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)

### Closed loop system with feedback (encoders, stepper motors)
* **Description**: Design a closed loop system with positioning feedback, based on the existing tracker design, as an alternative to the current setup.
* **Skills needed**: Electronics, Arduino, PID tuning, Encoder circuits
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.
* **Mentor**: @zisi

### Design and implement a stand alone open source stepper controller
* **Description**: Create a stand alone open source stepper controller to modularize our electronics. Use an established protocol to communicate with our microprocessor (e.g. I2C).
* **Skills needed**: Electronics, Arduino, Stepper controllers, I2C ,SPI or 1Wire
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.
* **Mentor**: @zisi

### Arduino Firmware restructure with tests and fixes
* **Description**: Rewriting the current Arduino firmware to resolve overflow errors and implement tests for extreme conditions and use cases.
* **Skills needed**: Arduino, Embedded programming, Embedded debugging, Algorithm Design
* **Expected results**: A new Arduino firmware with less function overflow errors compared to the current and tests.
* **Mentor**: @zisi

### Optimize rotor movement algorithm
* **Description**: Implement an improved and optimized rotor movement algorithm, to minimize path (length and time), apply tracking continuity (on extreme points) and apply instrumental limitations (cable twisting, horizon limits, extreme points, extreme conditions)
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.
* **Mentor**: @papamat

### Homing and setup bootstrap functions, testing functions
* **Description**: Design and implement a setup bootstrapping (first-run) and testing of ground station suite.
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.
* **Mentor**: @zisi

[[Category:SOC]]

Socis 2015 ideas

2017-08-26T13:52:08Z

Comzeradd: Socis 2015 ideas

These ideas were contributed by our developers and users. Some of them may be rough. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are it's [forum](http://community.satnogs.org) and it's [github repositories](http://github.com/satnogs). All interested students must apply their proposals at info@satnogs.org if selected they will be assigned two mentors (a primary and alternative mentor).

ESA SOCIS summer of code is an European Space Agency initiative, we encourage every party interested to visit it's [website](http://sophia.estec.esa.int/socis) and read it's [FAQ](http://sophia.estec.esa.int/socis/faq)

***

# Software Projects

## [SatNOGS Network](https://github.com/satnogs/satnogs-network)
### Data Dashboards using SatNOGS observation data/metadata
* **Description** Supply an overview of the observation data/metadata collected instead of the detailed view currently available
* **Skills needed** Django/Python , HTML, CSS3, Javascript
* **Expected results** Create standards based user facing dashboards for SatNOGS recorded data and metadata to provide an overview of a SatNOGS observation.

### Concatenate observational data
* **Description**: An observer should be able to access a concatenated view of an observation that is calculated (and compiled) by multiple data from different ground stations. Still SatNOGS Network must be able to provide a single url page for a single observation part (ie by one ground station pass).
* **Skills needed**: Django/Python, HTML, CSS3, Javascript.
* **Expected results**: Single URL for a single observation part to allow sharing of data, page must be accessible in all modern browsers

## [SatNOGS DB](https://github.com/satnogs/satnogs-db)
### Transition our proof of concept SatNOGS DB to a working product.
* **Description** Design and assist implementing a transition of the SatNOGS DB project from a working prototype to a product
* **Skills needed** Angular.js CouchDB
* **Expected results** SatNOGS DB must be able to accept data from crowd-sourcing and expose them in an API.

### Connect SatNOGS network to DB to get up-to-date transponder information.
* **Description**: Design, and implement a SatNOGS Network to SatNOGS DB connection (via an open API) to populate SatNOGS Network with up to date transponder information and SatNOGS DB with up to date tle satellite listings.
* **Skills needed**: Django, AngularDB
* **Expected results**: SatNOGS DB must be able to populate SatNOGS Network with all transponder data.

## [SatNOGS Client](https://github.com/satnogs/satnogs-client)
### Build a web based controller able to control the SatNOGS client
* **Description**: Build a web based controller to allow users to connect to the SatNOGS client using a browser without the need to connect to the internet.
* **Skills needed**: HTML5, OpenWRT, JS, CSS3
* **Expected results**: An embeddable web application able to control SatNOGS client via a web browser

### Package SatNOGS client for different distributions
* **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
* **Skills needed**: Packaging on major distributions.
* **Expected results**: Released and submitted upstream packages on major distributions.

## SatNOGS Infrastructure
### Improve logging and monitoring
* **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Logs and Monitoring capabilities for the Network administrators

### Improve distributed storage of observation data
* **Description**: SatNOGS observation data must be able to be stored in a distributed manner
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: A distributed storage option for observation data

### Add error rate and karma policies for SatNOGS clients
* **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Error and karma policies applied to observation job prioritization

### Docker-ise SatNOGS setup (for both client and network)
* **Description**: To provide a streamlined setup process for interested parties a Docker image for SatNOGS client and SatNOGS network should be created.
* **Skills needed**: Docker, Python
* **Expected results**: Fully functional Docker images for SatNOGS Client Network.

***

# [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)

## SatNOGS RF components
### LNA design
* **Description**: Design a Low Noise Amplifier to specifically cover the needs of satellite data coverage. VHF, UHF and S-Band should be covered.
* **Skills needed**: RF Electronics design. Filter design, signal theory.
* **Expected results**: Schematic, routing, board design and preferably a sample implementation.

### Diplexer design
* **Description**: Design a Diplexer to specifically cover the need of the SatNOGS Ground Station
* **Skills needed**: RF Electronics design. Filter design, signal theory.
* **Expected results**: Schematic, routing, board design and preferably a a working prototype.

### Polarization switching design for Uda-Yagi antennas
* **Description**: Create a polarization switching design to allow cross Uda-Yagi antenna configuration to switch polarization on the fly.
* **Skills needed**: RF Electronics design. Antenna design, signal theory.
* **Expected results**: Schematic, routing, board design and preferably a a working prototype.

## [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)

### Closed loop system with feedback (encoders, stepper motors)
* **Description**: Design a closed loop system with positioning feedback, based on the existing tracker design, as an alternative to the current setup.
* **Skills needed**: Electronics, Arduino, PID tuning, Encoder circuits
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.

### Design and implement a stand alone open source stepper controller
* **Description**: Create a stand alone open source stepper controller to modularize our electronics. Use an established protocol to communicate with our microprocessor (e.g. I2C).
* **Skills needed**: Electronics, Arduino, Stepper controllers, I2C ,SPI or 1Wire
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.

### Arduino Firmware restructure with tests and fixes
* **Description**: Rewriting the current Arduino firmware to resolve overflow errors and implement tests for extreme conditions and use cases.
* **Skills needed**: Arduino, Embedded programming, Embedded debugging, Algorithm Design
* **Expected results**: A new Arduino firmware with less function overflow errors compared to the current and tests.

### Implement or extend rotor control protocols in order to handle additional commands and errors
* **Description**: Additional errors and commands should be implemented to the current control protocols used in Easycomm2 and rotctrl
* **Skills needed**: Serial communications, Arduino, Embedded programming, Embedded debugging
* **Expected results**: Implementing or extending rotor control protocols which will handle addition commands and errors.

### Optimize rotor movement algorithm
* **Description**: Implement an improved and optimized rotor movement algorithm, to minimize path (length and time), apply tracking continuity (on extreme points) and apply instrumental limitations (cable twisting, horizon limits, extreme points, extreme conditions)
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.

### Homing and setup bootstrap functions, testing functions
* **Description**: Design and implement a setup bootstrapping (first-run) and testing of ground station suite.
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.

[[Category:SOC]]

GSOC 2017 Ideas

2017-08-26T13:51:15Z

Comzeradd: GSOC 2017 Ideas

These ideas were contributed by our developers and users for [Google Summer of Code 2017](https://summerofcode.withgoogle.com). Some of them may be in a rough state, but they can certainly be refined. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are its [forum](http://community.satnogs.org) and its [github repositories](http://github.com/satnogs).

Instructions
====
Students wishing to participate in Summer of Code must realise this is more than a mere formality. You will be required to produce code for Libre Space Foundation projects in 3 months.

You don't have to be a proven developer, in fact, this whole program is meant to facilitate joining Open Source communities. However, experience in coding and/or experience with Python libraries and applications is welcome.

You should start familiarizing yourself with the components that you plan on working on before the start date. LSF developers are available on the community site and on IRC for help.

Recommended steps
=====
* Read Google's instructions for participating
* Take a look at the list of ideas
* Come up with project that you're interested in
* Write a first draft proposal and get someone to review it for you
* Submit it using Google's web interface

Check the KDE's [Student Proposal Guidelines](https://community.kde.org/GSoC#Student_proposal_guidelines) for more hints on what your application should look like.

Coming up with an interesting idea is probably the most difficult part of all. It should be something interesting for **LSF**, for **Open Source in Space** and particularly for **you**.

Finding out what the most pressing issues are in the projects you're interested in is a good start. Learning the codebase and even submitting issues and identifying bugs is also a good way to start. We recommend strongly doing that and we will look favorably on applications from students who have started to act like Open Source developers.

***

# Software Projects

## [SatNOGS DB](https://github.com/satnogs/satnogs-db)
### Enhance frontend suggestions and moderation capabilities
* **Description**: Supply the ability for users to suggest new satellites. Supply the ability to moderators to approve or amend satellite and transmitters suggestions.
* **Skills needed**: Django/Python , HTML, CSS3, Javascript
* **Expected results**: All satellite and transmitters data should be crowdsourced and moderated through a simple UI.
* **Mentor**: @comzeradd

## [SatNOGS Client](https://github.com/satnogs/satnogs-client)
### Build a web based controller able to control the SatNOGS client
* **Description**: Expand the current web interface of satnogs-client with a web based controller to allow users to connect to their rotator using a browser without the need to connect to the internet.
* **Skills needed**: Python, Flask
* **Expected results**: An embeddable web application able to control SatNOGS client via a web browser
* **Mentor**: @jinxcat

### Package SatNOGS client for different distributions
* **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
* **Skills needed**: Packaging on major distributions.
* **Expected results**: Released and submitted upstream packages on major distributions.
* **Mentor**: @axilleas

## SatNOGS Infrastructure
### Improve logging and monitoring
* **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Logs and Monitoring capabilities for the Network administrators
* **Mentor**: @axilleas

### Improve distributed storage of observation data
* **Description**: SatNOGS observation data must be able to be stored in a distributed manner
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: A distributed storage option for observation data
* **Mentor**: @jinxcat

### Add error rate and karma policies for SatNOGS clients
* **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Error and karma policies applied to observation job prioritization
* **Mentor**: @jinxcat

***

# [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)

## [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)
### Title
* **Description**:
* **Skills needed**:
* **Expected results**:
* **Mentor**:

### Title
* **Description**:
* **Skills needed**:
* **Expected results**:
* **Mentor**:

[[Category:SOC]]

GSOC 2016 Ideas

2017-08-26T13:50:21Z

Comzeradd: GSOC 2016 Ideas

These ideas were contributed by our developers and users for [Google Summer of Code 2016](https://summerofcode.withgoogle.com). Some of them may be rough. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are it's [forum](http://community.satnogs.org) and it's [github repositories](http://github.com/satnogs).

Instructions
====
Students wishing to participate in Summer of Code must realise this is more than a mere formality. You will be required to produce code for Libre Space Foundation projects in 3 months.

You don't have to be a proven developer -- in fact, this whole program is meant to facilitate joining Open Source communities. However, experience in coding and/or experience with Python libraries and applications is welcome.

You should start familiarizing yourself with the components that you plan on working on before the start date. LSF developers are available on the community site and on IRC for help.
Recommended steps
=====
* Read Google's instructions for participating
* Take a look at the list of ideas
* Come up with project that you're interested in
* Write a first draft proposal and get someone to review it for you
* Submit it using Google's web interface

Check the KDE's [Student Proposal Guidelines](https://community.kde.org/GSoC#Student_proposal_guidelines) for more hints on what your application should look like.

Coming up with an interesting idea is probably the most difficult part of all. It should be something interesting for **LSF**, for **Open Source in Space** and particularly for **you**.

Finding out what the most pressing issues are in the projects you're interested in is a good start.Learning the codebase and even submitting issues and identifying bugs is also a good way to start. We recommend strongly doing that and we will look favorably on applications from students who have started to act like Open Source developers.

***

# Software Projects

## [SatNOGS Network](https://github.com/satnogs/satnogs-network)
### Data Dashboards using SatNOGS observation data/metadata
* **Description** Supply an overview of the observation data/metadata collected instead of the detailed view currently available
* **Skills needed** Django/Python , HTML, CSS3, Javascript
* **Expected results** Create standards based user facing dashboards for SatNOGS recorded data and metadata to provide an overview of a SatNOGS observation.
* **Mentor**: @comzeradd

### Concatenate observational data
* **Description**: An observer should be able to access a concatenated view of an observation that is calculated (and compiled) by multiple data from different ground stations. Still SatNOGS Network must be able to provide a single url page for a single observation part (ie by one ground station pass).
* **Skills needed**: Django/Python, HTML, CSS3, Javascript.
* **Expected results**: Single URL for a single observation part to allow sharing of data, page must be accessible in all modern browsers
* **Mentor**: @comzeradd

## [SatNOGS Client](https://github.com/satnogs/satnogs-client)
### Build a web based controller able to control the SatNOGS client
* **Description**: Expand the current web interface of satnogs-client with a web based controller to allow users to connect to their rotator using a browser without the need to connect to the internet.
* **Skills needed**: Python, Flask
* **Expected results**: An embeddable web application able to control SatNOGS client via a web browser
* **Mentor**: @jinxcat

### Package SatNOGS client for different distributions
* **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
* **Skills needed**: Packaging on major distributions.
* **Expected results**: Released and submitted upstream packages on major distributions.
* **Mentor**: @axilleas

## SatNOGS Infrastructure
### Improve logging and monitoring
* **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Logs and Monitoring capabilities for the Network administrators
* **Mentor**: @axilleas

### Improve distributed storage of observation data
* **Description**: SatNOGS observation data must be able to be stored in a distributed manner
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: A distributed storage option for observation data
* **Mentor**: @jinxcat

### Add error rate and karma policies for SatNOGS clients
* **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Error and karma policies applied to observation job prioritization
* **Mentor**: @jinxcat

## [Diactoros Firmware](https://github.com/librespacefoundation/diactoros)
### Enhance diactoros firmware
* **Description** Implement baud rate negotiation for ground-satellite communications based on link status
* **Skills needed** C, RF
* **Expected results**: Significant improvement in data rate of satellite to ground communications
* **Mentor**: @manostheodoridis

***

# [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)

## [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)

### Closed loop system with feedback (encoders, stepper motors)
* **Description**: Design a closed loop system with positioning feedback, based on the existing tracker design, as an alternative to the current setup.
* **Skills needed**: Electronics, Arduino, PID tuning, Encoder circuits
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.
* **Mentor**: @zisi

### Design and implement a stand alone open source stepper controller
* **Description**: Create a stand alone open source stepper controller to modularize our electronics. Use an established protocol to communicate with our microprocessor (e.g. I2C).
* **Skills needed**: Electronics, Arduino, Stepper controllers, I2C ,SPI or 1Wire
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.
* **Mentor**: @zisi

### Arduino Firmware restructure with tests and fixes
* **Description**: Rewriting the current Arduino firmware to resolve overflow errors and implement tests for extreme conditions and use cases.
* **Skills needed**: Arduino, Embedded programming, Embedded debugging, Algorithm Design
* **Expected results**: A new Arduino firmware with less function overflow errors compared to the current and tests.
* **Mentor**: @zisi

### Optimize rotor movement algorithm
* **Description**: Implement an improved and optimized rotor movement algorithm, to minimize path (length and time), apply tracking continuity (on extreme points) and apply instrumental limitations (cable twisting, horizon limits, extreme points, extreme conditions)
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.
* **Mentor**: @papamat

### Homing and setup bootstrap functions, testing functions
* **Description**: Design and implement a setup bootstrapping (first-run) and testing of ground station suite.
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.
* **Mentor**: @zisi

[[Category:SOC]]

GSOC 2015 Ideas

2017-08-26T13:49:36Z

Comzeradd: GSOC 2015 Ideas

These ideas were contributed by our developers and users for [Google Summer of Code 2015](http://www.google-melange.com/gsoc/homepage/google/gsoc2015). Some of them may be rough. If you wish to submit a proposal based on these ideas, you may wish to contact the developers and find out more about the particular suggestion you're looking at. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community.

The major communication and coordination systems of the SatNOGS project are it's [forum](http://community.satnogs.org) and it's [github repositories](http://github.com/satnogs). All interested students must apply their proposals at info@satnogs.org if selected they will be assigned two mentors (a primary and alternative mentor).

***

# Software Projects

## [SatNOGS Network](https://github.com/satnogs/satnogs-network)
### Data Dashboards using SatNOGS observation data/metadata
* **Description** Supply an overview of the observation data/metadata collected instead of the detailed view currently available
* **Skills needed** Django/Python , HTML, CSS3, Javascript
* **Expected results** Create standards based user facing dashboards for SatNOGS recorded data and metadata to provide an overview of a SatNOGS observation.

### Concatenate observational data
* **Description**: An observer should be able to access a concatenated view of an observation that is calculated (and compiled) by multiple data from different ground stations. Still SatNOGS Network must be able to provide a single url page for a single observation part (ie by one ground station pass).
* **Skills needed**: Django/Python, HTML, CSS3, Javascript.
* **Expected results**: Single URL for a single observation part to allow sharing of data, page must be accessible in all modern browsers

## [SatNOGS DB](https://github.com/satnogs/satnogs-db)
### Transition our proof of concept SatNOGS DB to a working product.
* **Description** Design and assist implementing a transition of the SatNOGS DB project from a working prototype to a product
* **Skills needed** Angular.js CouchDB
* **Expected results** SatNOGS DB must be able to accept data from crowd-sourcing and expose them in an API.

### Connect SatNOGS network to DB to get up-to-date transponder information.
* **Description**: Design, and implement a SatNOGS Network to SatNOGS DB connection (via an open API) to populate SatNOGS Network with up to date transponder information and SatNOGS DB with up to date tle satellite listings.
* **Skills needed**: Django, AngularDB
* **Expected results**: SatNOGS DB must be able to populate SatNOGS Network with all transponder data.

## [SatNOGS Client](https://github.com/satnogs/satnogs-client)
### Build a web based controller able to control the SatNOGS client
* **Description**: Build a web based controller to allow users to connect to the SatNOGS client using a browser without the need to connect to the internet.
* **Skills needed**: HTML5, OpenWRT, JS, CSS3
* **Expected results**: An embeddable web application able to control SatNOGS client via a web browser

### Package SatNOGS client for different distributions
* **Description**: SatNOGS client must be available in a binary package form for several distributions to further it's ease of modularity.
* **Skills needed**: Packaging on major distributions.
* **Expected results**: Released and submitted upstream packages on major distributions.

## SatNOGS Infrastructure
### Improve logging and monitoring
* **Description**: Improve SatNOGS logging and monitoring capabilities to allow SatNOGS Network to monitor which ground station are operating properly
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Logs and Monitoring capabilities for the Network administrators

### Improve distributed storage of observation data
* **Description**: SatNOGS observation data must be able to be stored in a distributed manner
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: A distributed storage option for observation data

### Add error rate and karma policies for SatNOGS clients
* **Description**: SatNOGS clients should be able to use error rate and karma policies in order to prioritize observation jobs.
* **Skills needed**: DevOps, DB and Sysadmin skills, open to technology suggestions
* **Expected results**: Error and karma policies applied to observation job prioritization

### Docker-ise SatNOGS setup (for both client and network)
* **Description**: To provide a streamlined setup process for interested parties a Docker image for SatNOGS client and SatNOGS network should be created.
* **Skills needed**: Docker, Python
* **Expected results**: Fully functional Docker images for SatNOGS Client Network.

***

# [SatNOGS Hardware](https://github.com/satnogs/satnogs-hardware)

## [SatNOGS Arduino](https://github.com/satnogs/satnogs-arduino)

### Closed loop system with feedback (encoders, stepper motors)
* **Description**: Design a closed loop system with positioning feedback, based on the existing tracker design, as an alternative to the current setup.
* **Skills needed**: Electronics, Arduino, PID tuning, Encoder circuits
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.

### Design and implement a stand alone open source stepper controller
* **Description**: Create a stand alone open source stepper controller to modularize our electronics. Use an established protocol to communicate with our microprocessor (e.g. I2C).
* **Skills needed**: Electronics, Arduino, Stepper controllers, I2C ,SPI or 1Wire
* **Expected results**: Schematic, routing, board design, Arduino software that implements it and preferably a working prototype.

### Arduino Firmware restructure with tests and fixes
* **Description**: Rewriting the current Arduino firmware to resolve overflow errors and implement tests for extreme conditions and use cases.
* **Skills needed**: Arduino, Embedded programming, Embedded debugging, Algorithm Design
* **Expected results**: A new Arduino firmware with less function overflow errors compared to the current and tests.

### Implement or extend rotor control protocols in order to handle additional commands and errors
* **Description**: Additional errors and commands should be implemented to the current control protocols used in Easycomm2 and rotctrl
* **Skills needed**: Serial communications, Arduino, Embedded programming, Embedded debugging
* **Expected results**: Implementing or extending rotor control protocols which will handle addition commands and errors.

### Optimize rotor movement algorithm
* **Description**: Implement an improved and optimized rotor movement algorithm, to minimize path (length and time), apply tracking continuity (on extreme points) and apply instrumental limitations (cable twisting, horizon limits, extreme points, extreme conditions)
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.

### Homing and setup bootstrap functions, testing functions
* **Description**: Design and implement a setup bootstrapping (first-run) and testing of ground station suite.
* **Skills needed**: Arduino, Embedded programming, Algorithm Design
* **Expected results**: Arduino code that implements the use cases on description.

[[Category:SOC]]

GS Software

2016-10-29T17:33:40Z

Comzeradd: Fix categories and typography

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

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

==Tracking==

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

===SatNOGS tracking software===

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

==Web services==

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

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

SatNOGS Rotator v3

2015-11-21T21:01:28Z

Comzeradd:

{{Template:Rotator
|Rotator-Name=SatNOGS Rotator v3
|image=V3.jpg
|type= Az/El
|status= Beta
|latest-release= https://github.com/satnogs/satnogs-rotator
|latest-release-name= v3
|source-repo= https://github.com/satnogs/satnogs-rotator
|documentation= http://satnogs.dozuki.com/Guide/SatNOGS+Rotator+v3+Mechanical+Assembly
}}

== Intro ==

== Sourcing ==

== Documentation ==

File:V3.jpg

2015-11-21T20:59:32Z

Comzeradd: Comzeradd uploaded a new version of File:V3.jpg

File:V3.jpg

2015-11-21T20:49:49Z

Comzeradd: Comzeradd uploaded a new version of File:V3.jpg

File:V3.jpg

2015-11-20T16:39:31Z

Comzeradd: Comzeradd uploaded a new version of File:V3.jpg

File:Idea.png

2015-10-16T15:01:10Z

Comzeradd: Comzeradd uploaded a new version of File:Idea.png

File:Idea.png

2015-10-16T14:53:45Z

Comzeradd: Comzeradd uploaded a new version of File:Idea.png

File:Idea.png

2015-10-16T14:52:44Z

Comzeradd: Comzeradd uploaded a new version of File:Idea.png

File:Idea.png

2015-10-16T14:52:28Z

Comzeradd: Comzeradd uploaded a new version of File:Idea.png