SatNOGS Wiki - User contributions [en]

SatNOGS DB

2019-01-06T14:42:08Z

SaintAardvark: Update github to gitlab, minor tidying

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

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

==Contribute==

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

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

=== Suggesting transmitters ===
Detailed instructions on suggesting transmitters can be found [http://docs.satnogs.org/db/contribute.html here].

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

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

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

== API ==

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

==Installation==

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

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

User talk:SaintAardvark

2018-06-12T12:58:44Z

SaintAardvark:

SaintAardvark,
I did an edit of the [[Ground_Stations]] article. Hope you like it. [[User:WA4OSH| WA4OSH]] [[User talk:WA4OSH|talk]] 12:44, 9 June 2018 (UTC)

Hi WA4OSH -- that looks good to me. :-) Thanks for improving the wiki!

User talk:SaintAardvark

2018-06-12T12:58:23Z

SaintAardvark:

SaintAardvark,
I did an edit of the [[Ground_Stations]] article. Hope you like it. [[User:WA4OSH| WA4OSH]] [[User talk:WA4OSH|talk]] 12:44, 9 June 2018 (UTC)

Hi [[User:WA4OSH]] -- that looks good to me. :-) Thanks for improving the wiki!

Ground Stations

2018-06-08T14:19:23Z

SaintAardvark:

A ground station, earth station, or earth terminal is defined as a terrestrial radio station designed for extra planetary telecommunication with spacecraft. It can be thought of as a constituting part of the ground segment of the spacecraft system.

For the SatNOGS project a ground station is piece of hardware and software that is used to receive satellite signals.

There are different types of ground stations but they can be grouped into one of two forms, either one with moveable antennas or one with static antennas. A ground station with moveable antennas makes use of multiple antennas that a rotator points towards and tracks satellites. The rotator can either be a commercial or SatNOGS type. More information can be found on the [[Rotators|rotators page]].

SatNOGS also make provision for non-rotator ground stations. These are typically simpler and rely on no moving parts but require an antenna that has a broad view of the sky. Typical installations tend to work well with higher passes but will struggle to achieve successful observations when satellites pass lower to the horizon.

A ground station also needs a receiver. The RTL-SDR dongle is typically used as a receiver, and the Raspberry Pi is the integration between the ground station and SatNOGS network. Further information can be found in the [[Receiver|receivers page]]

A receiver is then, in turn, connected to an antenna or antennas. The type of antenna used depends on the ground station. Different satellites will have different uplinks and downlinks and the choice of antenna will affect the observation. See the [[Antennas|Antennas page]] for typical ground station set ups.

This wiki will focus on the SatNOGS ground station but it is worth noting that commercial rotators and commercial receivers have been used in some instances.

SatNOGS Rotator v3

2018-05-28T04:07:17Z

SaintAardvark: Add link to controller

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

== Intro ==

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

Also in this [https://www.ethercalc.org/v3specs list] is presented different rotators, either commercial or DIY builds.

==Specifications==

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

==== Brake Torque ====
The greatest force the tracker needs to withstand is the force created by strong wind. The worst case is when one antenna is elevated at 90 degs, facing the direction of the wind. We based our calculations on an [http://k7nv.com/notebook/topics/windload.html article] found online after comparing it to others. We “translated” the second table in metric (because we don’t understand imperial and because we needed same units system in our calculations)

{| class="wikitable"
|-
! Method
! Wind Zone(km/h)
! Height (m)
! Pressure(N/m^2)
|-
| EIA-222-C
| 160
| N/A
| 1280

|-
| EIA-222-F
| 128
| 14
| 1260

|-
| EIA-222-F
| 128
| 21
| 1390

|-
| EIA-222-F
| 128
| 30
| 1500

|-
| UBC'97
| 128
| 14
| 1290

|-
| UBC'97
| 128
| 21
| 1160

|-
| UBC'97
| 128
| 21
| 1390

|-
| UBC'97
| 128
| 30
| 1260

|-
| UBC'97
| 128
| 42
| 990

|-
| UBC'97
| 128
| 42
| 1360

|-
| Generic Formula
| 150
| N/A
| 1270

|}

and we applied the worst case model (EIA-222-F) in 3 different antennas: in the biggest one of our designs, and in two others, for which we obtained data from [http://download.qrz.ru/pub/hamradio/antenna/rotators/G-800SA_1000SA.pdf yaesu G800 rotator manual at page 3]. We assumed that antennas are mounted in 1m away from the azimuth axis. For our antenna with 2m length (actual, not wavelength), made by 2cm square tube, the generated torque was ≈600Kg*cm. For the 144MHz 10-elements Yagi from the article is ≈6000Kg*cm and for the third 430MHz, 12-elements Yagi is ≈1800Kg*cm

==== Moment of inertia ====
Now for the moment of inertia: (for all installation methods we assumed that antennas are counterbalanced in the elevation axis) the worst case scenario here is to use two 3kg (our designs are less than 1kg) back mounted yagis with 3kg counterbalances both mounted in 0.75m away from azimuth axis. The torque you need in order to accelerate this system from ω=0deg/s angular velocity to ω=5deg/s (the math about angular velocity is below) in one second is about 60kg*cm.

Note: we suppose that the mass of antennas is near to the altitude axis, so the torque of this axis that is needed to accelerate is approximately 0.

* M1: torque of Azimuth axis
* L: length of center of mass of antennas from azimuth axis (0.75m)
* m: mass of antennas and of counterweight (3kg + 3kg = 6kg)
* I: moment inertia
* a: angular acceleration of azimuth axis 5deg/s^2
* I = I1 + I2 = m*L^2 + m*L^2 = 2*m*L^2 = 6.75 kg*m^2
* M1 = I*a = 6.75kgm^2 * 0.087rad/s^2 = 0.58 Nm = 5.8 kgm = 58 kgcm

==== Angular velocity ====
(How well do you remember trigonometry?)For the angular velocity max needed in altitude axis the things are straightforward. The closer is the satellite the larger the velocity. According to the wikipedia article about LEO, the lowest height limit is 160 km and the speed unit to orbit earth in this altitude is 7,8 km/s. As a result, maximum velocity in ALT axis is 2,8 deg/s. In ALT AZ rotator design there is a well known limitation: the closer something passes near zenith the biggest gets the velocity of the AZ axis. Therefore, we have analyzed this problem to figure out the optimal velocity and how high we are allowed to track a target in relation to AZ velocity. The picture below illustrates a ground station B which tracks a satellite Γ in X degrees altitude. The satellite velocity at this point is vertical to the screen (page) plane.

[[File:Anglular_velocity.png|thumb|center|800x420px|alt=|Angular Velocity]]

The equations that lead to maximum altitude at which we can track in relation to AZ angular velocity are
* ω : angular velocity of AZ DOF in rad/s
* H = ΑΕ + ΕΓ : Minimum Height of LEO, 160 km
* R = ΑΕ : Radius of Earth, 6500 km
* u : linear velocity of satellite that rotates in 160km height is 7.8 km/s
* ΒΔ = u / ω : ΒΔ in km
* α = atan(ΒΔ / R)
* δ = π - α
* γ = asin( sqrt(R^2+ΒΔ^2) * sin(δ) / (H+R) )
* ά = π - δ - γ
* ΓΔ = (H+R) * sin(ά) / sin(δ)
* χ = atan(ΓΔ / ΒΔ)

Below you can see the plot of the equations mentioned above, where horizontal axis represents angular velocity (ω) in deg/s and vertical axis shows the max track altitude (χ) for lower bound of LEO.

[[File:Anglular_velocity_plot.png|thumb|center|800x420px|alt=|Angular Velocity Plot]]

After studying this diagram, we came up to the conclusion that an angular velocity of 5 deg/s is adequate. For this decision, we took into consideration the main lobe of antenna (Δ3db) which in most situations is about 20 deg.

==== General Specifications ====
Together with the above mentioned specifications, we would also like for the 3rd version of SatNOGS rotator to be:

* inexpensive (less than €300, if possible)
* lightweight and portable (~6Kg, size:~300x~150x~150mm)
* rigid and durable
* easy to build and fix (try to use easily available materials)
* weatherproof
* electromagnetically shielded, so that noise in reception is reduced
* accurate (<1deg, backslash reduction and use of encoders at the axis)

== Sourcing ==

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

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

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

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

Hidden corner connectors - AliExpress gave the cheapest supplier

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

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

'''Stepper Motors''' - eBay

'''Belts''' - eBay

'''Fixings / Pipe''' - eBay

== Build Sequence ==

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

== Worm Gear Box Calculations ==

* Gear ratio: i12 = 30
* Angle between axis of gears: δ = 90 deg
* Number of threads in worm: If i12 >= 30 then z1 = 1
* Number of teeth in worm wheel: z2 = i12*z1 = 30
* Center distance: initial case a = 45.5 mm
* Worm reference diameter: AGMA d01>= 11.5*(a/25.4)^0.875 = 19.15 mm, so d01 = 19.5mm
* Worm wheel reference: d02 = 2*a - d01 = 71.5 mm
* Axial module: ms = d02/z2 = 2.38 , so ms = 2.5
Recalculate d02, a with new axial module
* d02 = z2*ms = 75mm, a = (d02+d01)/2 = 47.25mm
* Axial pitch: ts = π*ms = 7.854mm
* Reference lead angle: γ0 = atan(d02/(i12*d01)) = 7.3 deg
* Worm tip diameter: dk1 = d01 + 2*hk = 24.5mm
** Worm teeth reference addendum in axial section: hk = hk* *ms = 2.5mm
** Worm tooth reference addendum coefficient: hk* = 1
* Worm root diameter: df1 = d01 - 2*hf = 13.5mm
** Worm tooth reference dedendum: hf = hf* _ms = 1.2_ms = 3mm
** Dedendum coefficient: hf* = 1.2
* Worm length: L = 2.5_ms_sqrt(z2+2) = 35.36mm
* Worm tooth thickness: smx1 = smx1* * ts = 3.927mm
** Tooth thickness coefficient: smx1* = 0.5
* Normal pressure angle: aon = 20 deg
* Worm wheel throat diameter: dk2 = d02+2*hk = 80mm
* Worm wheel root diameter: df2 = d02 - 2*hf = 69mm
* Worm wheel outside diameter: de2 = dk2 + 2*mx = 83.5mm
** Worm wheel tooth external addendum: mx = n*ms, 0.4<=n<=1.5
* Effective worm wheel face width: b2H,max = sqrt((2_a - df2)^2 - (2_a - de2)^2) = 23mm

== Test Sequence ==

Test sequence needed

== Documentation ==

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

[[Category:Rotator]]

Main Page

2018-05-28T02:38:33Z

SaintAardvark: Minor cleanup

__NOTOC__
SatNOGS is an integral part of the [https://libre.space Libre Space Foundation]. The project aims to build a global network of satellite ground stations. Designed as an open source participatory project, the hardware is straightforward to build using commonly available parts and some 3D printed elements. A ground station is built to interact with a website that holds key satellite information. The web interface allows a user to schedule a satellite observation of any of the networked ground stations.
Here you can find more information on how to get started with SatNOGS, building and operating a satellite ground station and joining the SatNOGS Network.
A SatNOGS ground station can be made in a variety of ways. The reference design uses a Raspberry Pi and RTL-SDR dongle with either stationary antennas, or a rotator (either a SatNOGS rotator or a commercial amateur radio rotator). It is also possible to use amateur radio transceivers or alternative SDR technology.

The image below illustrates the system:
[[File:Satnogs_imagemap.png|center]]
<div style="border-radius: 3px; width: 16%; height: 300px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
__NOTOC__
<h2>What is SatNOGS</h2>
[[Intro|Intro to SatNOGS]]
[[Ground Stations|Intro to ground stations]]
[[Glossary]]
</div>
<div style="border-radius: 3px; width: 16%; height: 300px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Build</h2>
[[Get_Started|Learn how to get started]]
[[Build|Build a ground station]]
[[Rotators|Rotators]]
[[Antennas|Antennas]]
[[Radio|Signal Reception]]
</div>
<div style="border-radius: 3px; width: 16%; height: 300px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Operate</h2>
[[Network|SatNOGS Network]]
[[Operation|Scheduling your first observation and operating your station]]
[[Adjusting the SatNOGS Client|Tuning and adjusting your station]]
[[Satnogs DB]]
 
</div>
<div style="border-radius: 3px; width: 16%; height: 300px; background-color: #f6f6f6; float: left; display: block; margin: 1.5%; border: 1px solid #A7D7F9; text-align: center; padding: 2.5%; padding-top: 0px;">
<h2>Contribute</h2>
[[Software contribution]]
[[Provide documentation]]
[[Satnogs DB]]
[[Troubleshooting|Troubleshooting]]
[[Get_In_Touch|Get in touch and ask for help]]
 
</div>

SatNOGS Network

2018-03-13T04:05:52Z

SaintAardvark: Add link to setup instructions

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

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

==Getting started==

* Head to 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:
[[File:Dev_ground_station.PNG|center|800px]]

===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 production environment needs reliable ground stations that perform within the constraints that would be expected. A ground station should perform in a way that is comparable to its peers and 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. If your ground station fits within these guidelines then it is good to have a conversation about if it is ready for the production environment.

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

Raspberry Pi

2018-03-13T04:03:41Z

SaintAardvark: Minor typo

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

= Intro =

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

= Raspbian =

== Download ==

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

=== Artifacts list ===

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

== Data integrity verification ==

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

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

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

== Networking ==

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

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

You will want to be sure to do the following:

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

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

== Setup ==

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

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

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

=== Basic setup ===

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

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

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

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

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

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

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

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

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

=== Advanced Setup ===

* '''SATNOGS_CLIENT_URL''': If you to try a development version of satnogs-client, you can change the URL here. The URL needs to be in [https://pip.pypa.io/en/stable/reference/pip_install PIP format]. Here are some examples:
** git+https://gitlab.com/librespacefoundation/satnogs/satnogs-client.git@0 -- the '0' branch (the current development version) of satnogs-client
** git+https://gitlab.com/jdoe/satnogs-client.git@new-feature -- the 'new-feature' branch of jdoe's fork of satnogs-client
* '''SATNOGS_RADIO_GR_SATNOGS_PACKAGE''': This options allows you to change the installed package of gr-satnogs. For example, to install nightly development builds use:
** https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package/-/jobs/artifacts/master/raw/build/debian/output/armhf/gr-satnogs_armhf.deb?job=nightly
* '''RF_GAIN''': RF Gain value for your SDR hardware. Defaults can be found [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/blob/master/python/hw_settings.py here].
** For rtl-sdr possible values are the following: 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6

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

== Updating ==

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

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

WARNING: An update can potentially interrupt a running observation!

== Testing ==

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

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

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

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

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

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

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

= Fedora =

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

SatNOGS Network

2018-03-13T04:02:59Z

SaintAardvark: Migrate some content from dev page, including details needed to create ground station

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

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

==Getting started==

* Head to 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 complete the setup of it 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:
[[File:Dev_ground_station.PNG|center|800px]]

===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 production environment needs reliable ground stations that perform within the constraints that would be expected. A ground station should perform in a way that is comparable to its peers and 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. If your ground station fits within these guidelines then it is good to have a conversation about if it is ready for the production environment.

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

File:Network satnog main page.png

2018-03-13T03:56:19Z

SaintAardvark: front page of network.satnogs.org, with "Sign up" circled

front page of network.satnogs.org, with "Sign up" circled

Server Development Environment

2018-03-13T03:47:28Z

SaintAardvark: Fix typo

==What is the purpose of the development environment?==

Like many innovative projects, there needs to be a bit of testing. The development environment is a place to iron out all the wrinkles in your system before it is moved to the [[Production Environment|Production Environment]]. The production environment is essentially fully developed ground stations that only require deploying; access to it is limited. This is not the case with the development environment.

==How do I get access and create a ground station?==

The [https://network-dev.satnogs.org/ Development Network] has the usual sign up buttons. Create your account there and await confirmation.
[[File:Development network.png|center|800px]]

===Creating a ground station===

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.

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

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

SatNOGS Network

2018-03-13T03:39:32Z

SaintAardvark: /* Development */ Fix/add links

SatNOGS Network

2018-03-13T03:35:15Z

SaintAardvark: /* Getting started */ Add URL for network.satnogs.org

Rotators

2018-03-11T15:25:26Z

SaintAardvark: Add link to Rotator Controller page

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

===SatNOGS Rotator v2===

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

===SatNOGS Rotator v3===

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

==Commercial rotators==

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

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

===SPID X-Y===

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

* [[SatNOGS Rotator Controller|Wiki page]]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-controller Design files]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator-firmware Firmware]

Main Page

2018-01-25T14:58:11Z

SaintAardvark: Add link to operation and adustments pages to "Operation" column

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

Adjusting the SatNOGS Client

2018-01-25T14:52:51Z

SaintAardvark: MInor fixes

(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 [[Development Environment]]
* 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:

[[File:SatNOGS_local_network_mode.png|center|600px]]

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

[[File:SatNOGS_local_standalone_mode.png|center|600px]]

{{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...
</pre>

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.

{{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:

[[File:Startup_gqrx.png|center|600px]]

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"

[[File:Gqrx_io_configuration.png|center]]

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

[[File:Gqrx_running.png|center|600px]]

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:

[[File:Gqrx_ppm-error_offset.png|center|600px]]

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.

[[File:Gqrx_ppm-error_corrected.png|center]]

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.

[[File:Fcecd26ca08cf3d23dffce719ef1dd13a4f7109d.png|center]]

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.

Adjusting the SatNOGS Client

2018-01-24T15:19:58Z

SaintAardvark:

(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'v read all the [[Get Started|Getting Started]] page, as well as the pages linked under "Build" and "Operate" on the [[Main Page]]
* you have already done your [[Operation|first observations]] and you already have some waterfalls in the [[Development Environment]]
* 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:

[[File:SatNOGS_local_network_mode.png|center|600px]]

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

[[File:SatNOGS_local_standalone_mode.png|center|600px]]

{{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, 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

You will get an output like this, if everything is fine:

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

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

[[File:Startup_gqrx.png|center|600px]]

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"

[[File:Gqrx_io_configuration.png|center]]

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

[[File:Gqrx_running.png|center|600px]]

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:

[[File:Gqrx_ppm-error_offset.png|center|600px]]

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.

[[File:Gqrx_ppm-error_corrected.png|center]]

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.

[[File:Fcecd26ca08cf3d23dffce719ef1dd13a4f7109d.png|center]]

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.

Adjusting the SatNOGS Client

2018-01-24T15:08:19Z

SaintAardvark: Add screenshots from original post

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

== Prerequisites / dependencies ==

This page assumes you read all the available "getting started" pages linked to under "Build" and "Operate", and you have already done your first observations and you already have some waterfalls in the staging environment. Now you come to a point where you want to know how well your station is performing.

{{Message| If you haven't already, this is the perfect time to [http://gqrx.dk/download install gqrx] on your local computer.}}

== SatNOGS station adjustments ==

To start some kind of "adjustment" and "calibration", please connect to your
RasPi's local web interface. By default the URL is something like "http://192.168.0.5:5000". 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:

[[File:SatNOGS_local_network_mode.png|center|600px]]

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

[[File:SatNOGS_local_standalone_mode.png|center|600px]]

{{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, please SSH to your SatNOGS RasPi with your well
known user account.
After successful authorization you will be prompted 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

You will get an output like this, if everything is fine:

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

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

[[File:Startup_gqrx.png|center|600px]]

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"

[[File:Gqrx_io_configuration.png|center]]

Click on "Device" and chose "RTL-SDR Spectrum Server"
Edit "Device string" to match your RasPi's IP address, Port defaults to 1234,
which is the same as the default setting for your server you just started on
the RasPi.
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
"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 RasPi 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.

[[File:Gqrx_running.png|center|600px]]

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:

[[File:Gqrx_ppm-error_offset.png|center|600px]]

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.

[[File:Gqrx_ppm-error_corrected.png|center]]

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.

[[File:Fcecd26ca08cf3d23dffce719ef1dd13a4f7109d.png|center]]

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

You are done with frequency offset correction.

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

File:Fcecd26ca08cf3d23dffce719ef1dd13a4f7109d.png

2018-01-24T14:50:36Z

SaintAardvark: Screenshot of satnogs-setup PPM configuration screen

Screenshot of satnogs-setup PPM configuration screen

File:Gqrx ppm-error corrected.png

2018-01-24T14:49:31Z

SaintAardvark: Screenshot of gqrx with offset corrected

Screenshot of gqrx with offset corrected

File:Gqrx ppm-error offset.png

2018-01-24T14:48:49Z

SaintAardvark: Screenshot of gqrx with uncorrected offset

Screenshot of gqrx with uncorrected offset

File:Gqrx running.png

2018-01-24T14:47:25Z

SaintAardvark: Screenshot of gqrx running

Screenshot of gqrx running

File:Gqrx io configuration.png

2018-01-24T14:46:54Z

SaintAardvark: Screenshot of gqrx I/O configuration screen

Screenshot of gqrx I/O configuration screen

File:Startup gqrx.png

2018-01-24T14:46:01Z

SaintAardvark: Screnshot of gqrx at startup

Screnshot of gqrx at startup

File:SatNOGS local standalone mode.png

2018-01-24T14:45:24Z

SaintAardvark: Screenshot of SatNOGS client running in standalone mode

Screenshot of SatNOGS client running in standalone mode

File:SatNOGS local network mode.png

2018-01-24T14:44:45Z

SaintAardvark: Screenshot of SatNOGS client running in network mode

Screenshot of SatNOGS client running in network mode

Adjusting the SatNOGS Client

2018-01-23T04:42:33Z

SaintAardvark: Port DL4PD's excellent post (https://community.libre.space/t/how-to-do-some-client-adjustments/1604/1) to the wiki

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

== Prerequisites / dependencies ==

This page assumes you read all the available "getting started" pages linked to under "Build" and "Operate", and you have already done your first observations and you already have some waterfalls in the staging environment. Now you come to a point where you want to know how well your station is performing.

{{Message| If you haven't already, this is the perfect time to [http://gqrx.dk/download install gqrx] on your local computer.}}

== SatNOGS station adjustments ==

To start some kind of "adjustment" and "calibration", please connect to your
RasPi's local web interface. By default the URL is something like "http://192.168.0.5:5000". In the upper right corner there is a big green button where you can set your ground station in standalone mode.

Network mode:

Standalone mode

{{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, please SSH to your SatNOGS RasPi with your well
known user account.
After successful authorization you will be prompted 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

You will get an output like this, if everything is fine:

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

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

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"

Click on "Device" and chose "RTL-SDR Spectrum Server"
Edit "Device string" to match your RasPi's IP address, Port defaults to 1234,
which is the same as the default setting for your server you just started on
the RasPi
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
"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 RasPi 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.

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:

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.

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.

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

You are done with frequency offset correction.

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

2017-12-28T00:35:04Z

SaintAardvark: Add info about failed observations

__TOC__

== Scheduling your first test observation ==

'''Assumptions:'''

* You've set up your [[Raspberry Pi 3|SatNOGS client successfully]]
* You've created an account on the [https://network-dev.satnogs.org/ Stage Environment], created a ground station, and it's showing up as "online"

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

'''SatNOGS Network:'''

* Navigate your ground station page in the Stage Environment (user name -> "My Profile" -> click on the name of your ground station).
* Select the "Upcoming passes" tab.
* Look for a pass with a "schedule" button that isn't greyed out, and click it.
* In the "New Observation" page that comes up, click the "Calculate" button, then click "Schedule".
* You should now see a page for that observation; in the "Waterfall" tab, you should see "Waiting for waterfall".

'''Ground Station'''

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

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

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

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

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

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

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

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

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

== Rating observations ==

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

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

Categories of observations:

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

Below is a collection of waterfalls with possible results of observations:
<gallery heights=400px widths=200px>
File:Waterfall_20657_2017-10-15T10-07-51.png|'''Good''': Satellite is visible (bars-bursts of data in the middle). ''Note that the tangent-shaped lines are local noise''
File:Waterfall_20534_2017-10-15T07-21-24.png|'''Bad''': Typical empty waterfall with no visible signals.
File:Waterfall 20499 2017-10-15T07-17-32.png|'''Good''': Although drifting, satellite is clearly visible around the center.
File:Waterfall 20506 2017-10-15T06-47-36.png|'''Good''': Faint CW signal around center-left. ''Note you might have to expand image to notice it''
File:Waterfall_20571_2017-10-15T05-25-56.png|'''Good''': Clearly visible FM transmission. ''Note that the swinging lines are terrestrial noise''
File:Waterfall 20483 2017-10-15T05-12-49.png|'''Good''': Straight line in the center bottom is a satellite. ''Note transmission on left bottom is the same satellite on a different frequency''
</gallery>

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

=== Discuss ===
If you're still unsure about an observation, click the "Discuss" button, near the top right of the observation's page; that will post a link to it on [https://community.libre.space/c/observations the Observations forum], where you can ask for feedback.
{{Message|Discuss button is only shown in the production instance of the SatNOGS network. If you have an observation in the dev instance you want help with, you can still post it manually to [https://community.libre.space/c/observations the Observations forum], and we'll be happy to help.}}

== Scheduling observations in standalone mode ==

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

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

== Network permissions matrix ==

{| class="wikitable" style="text-align:center"
|-
! scope="col"| Group
! scope="col"| Schedule observation
! scope="col"| Delete observation
! scope="col"| Vet observation
! scope="col"| Discuss observation
|-
| Auth users
| No
| No
| No
| Any
|-
| Station owners
| Any (on online stations) & Own stations (on test stations)
| Own (stations or observations)
| Own (stations or observations)
| Any
|-
| Moderators
| Any (on online stations)& Own stations (on test stations)
| Any
| Any
| Any
|-
| Admins
| Any
| Any
| Any
| Any
|}

Server Development Environment

2017-12-28T00:31:59Z

SaintAardvark: Minor tidying and rephrasing

==What is the purpose of the development environment?==

Like many innovative projects, there needs to be a bit of testing. The development environment is a place to iron out all the wrinkles in your system before it is moved to the [[Production Environment|Production Environment]]. The production environment is essentially fully developed ground stations that only require deploying; access to it is limited. This is not the case with the development environment.

==How do I get access and create a ground station?==

The [https://network-dev.satnogs.org/ Development Network] has the usual sign up buttons. Create your account there and await confirmation.
[[File:Development network.png|center|800px]]

===Creating a ground station===

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.

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

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

Antennas

2017-11-20T01:52:48Z

SaintAardvark: Update names/design file/assembly instruction links for helical antenna to reflect new URLs

Antennas developed and used by SatNOGS rotators

==SatNOGS antennas==

To cover the needs of the SatNOGS community the SatNOGS team has developed a number of antennas.

===Yagi===

A Yagi antenna is the simplest antenna for the novice maker.

===Cross Yagi UHF v1===

A cross Yagi UHF antenna.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Yagi/Cross-Yagi-UHF-v1 v1 Design files]

===Helical v1===

The first iteration of our helical UHF antenna allows users to create their own helical antenna design using only 3D printed parts. It is tuned for 437 MHz.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical/UHF%20lhcp-version_1 Design files]

* [https://ohai.satnogs.org/workflow/helical-antenna-v1/hardware/ Assembly instructions]

===Helical v4===

This iteration is more rigid, but you need to have access to CNCed parts.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical/UHF-434-8-version_4 Design files]

* [https://satnogs.dozuki.com/Guide/Helical+Antenna+v4/11 Assembly instructions]

===Helical v5===

This iteration is our latest version of the Helical antenna design; it comes in RHCP configuration. The supports are made from aluminum, and will require a drill press.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical/UHF-435-8-version_5 Design files]

* [https://ohai.satnogs.org/project/helical-antenna-v5/hardware/ Assembly instructions]

==Commercial Antennas==

===[http://www.arrowantennas.com/arrowii/146-437.html Arrow II Satellite Antenna]===

==DIY Antenna designs==

Introduction

2017-11-17T04:53:07Z

SaintAardvark: Add link to Pierros' talk

==SatNOGS==
SatNOGS (Satellite Networked Open Ground Station) project is a free software and open source hardware platform aimed at creating a satellite ground station network. The scope of the project is to create a full stack of open technologies based on open standards, and the construction of a full ground station as a showcase of the stack.

In order to implement such a stack, the four following different sub-projects are being developed.

===Network===

SatNOGS Network is a web application for scheduling observations across the network of ground stations. It facilitates the coordination of satellite signal observations, and scheduling such observations among the satellite ground-stations connected on the network.

===Database===

SatNOGS Database is a crowd-sourced application allowing its users to suggest satellite transmitter information for currently active satellites. Its data are available via an API or via a web application interface, allowing other project to use its satellite transmitter information.

===Client===

SatNOGS Client is the software to run on ground stations, usually on embedded systems, that receives the scheduled observations from the Network, receives the satellite transmission and sends it back to the Network web app.

===Ground Station===

SatNOGS Ground Station is an open source hardware ground station instrumentation with a rotator, antennas, electronics and connected to the Client. It is based on 3D printed components and readily available materials.

==Presentations on SatNOGS==

* Pierros Pappadeas presented [https://www.youtube.com/watch?v=JGv-S1F-hQo "Going to space the Libre way"] at the AmSAT UK RSGB 2017 convention.
* Scott Bragg presented [https://www.youtube.com/watch?v=BKULw0NXhyI "Decoding Satellites with SatNOGS"] at linux.conf.au in 2017.
* Manolis Surligas presented [https://www.youtube.com/watch?v=zs_J1wlIpMs "SatNOGS: An SDR-based Satellite Networked Open Ground Station"] at FOSDEM 2017.
* Dan White presented ["SatNOGS: Satelllite Networked Ground Stations"] at the Digital Communications Conference in 2015.

==Academic papers on SatNOGS==

* [[Academic Papers]]

SatNOGS Rotator Controller

2017-11-17T04:46:50Z

SaintAardvark: Add links to a couple of PCB fabricators

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

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

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

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

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

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

==== Micro controller ====
[[File:Uc.png|thumb|320x240px|Microcontroller]]
[[File:Uc_orientation.png|thumb|320x240px|Microcontroller Orientation]]
[[File:I2c_pullup.png|thumb|320x240px|I2C pull-up resistors]]

 

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

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

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

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

===== DC motor driver =====
WIP

 

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

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

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

 

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

 

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

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

 

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

WIP

 

==== Wiring ====

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

 

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

WIP

 

=== Firmware and Pin Assignments ===

 

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

 

== Rotator Controller v1 ==

Build

2017-11-13T05:15:55Z

SaintAardvark: Re-do antenna section

== Intro ==

Thanks for your interest on building a satellite ground station!

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

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

[[File:Satnogs_imagemap.png|center]]

Here are some links explaining the different options:

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

{{Message|Use the above table to select your setup. E.g. SatNOGS Network > SatNOGS Client > RaspberryPi > Yaesu G550 > Kenwood TS2000 > UHF helical & VHF Cross Yagi}}

== How do I pick? ==

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

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

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

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

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

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

== Next steps ==

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

Build

2017-11-13T04:54:04Z

SaintAardvark: Add outline of options, and why/how to pick

== Intro ==

Thanks for your interest on building a satellite ground station!

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

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

[[File:Satnogs_imagemap.png|center]]

Here are some links explaining the different options:

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

{{Message|Use the above table to select your setup. E.g. SatNOGS Network > SatNOGS Client > RaspberryPi > Yaesu G550 > Kenwood TS2000 > UHF helical & VHF Cross Yagi}}

== How do I pick? ==

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

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

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

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

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

'''Antenna''': When choosing an antenna, you need to take into account:

* How much space you have: How much outside space do you have for an antenna? Do you only have space on the roof for a simple turnstile, or do you have room in the backyard for a rotator as well?
* What you want to hear: A simple turnstile antenna will let you pick up NOAA weather satellites and ISS broadcasts; to pick up low-power cubesats or ham radio satellites, you'll almost certainly need a helical or Yagi antenna plus a rotator.
* How comfortable you are with DIY: Antennas can be simple to build (turnstile, Yagi) or more complicated (helical).

== Next steps ==

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

Operation

2017-11-13T04:13:59Z

SaintAardvark: Add link to NOAA APT decoder walkthrough

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

Raspberry Pi

2017-11-13T04:11:00Z

SaintAardvark: Show how to install satnogs-client from fork for testing

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

= Fedora =

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

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

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

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

You will want to be sure to do the following:

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

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

== 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"
# Select "Update" to update the configuration tool
# Set basic configuration
# Select "Apply" and the Raspberry Pi will configure itself; this may take some time
# Select "Back" to exit

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

=== Basic setup ===

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

* '''SATNOGS_NETWORK_API_URL''': The API for the SatNOGS network site. If you're working on the stage environment, this is 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. For a yaesu rotator, use <code>-m 601 -r /dev/ttyACM0 -s 9600 -T 0.0.0.0</code>

=== Advanced Setup ===

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

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

== Updating ==

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

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

WARNING: An update can potentially interrupt a running observation!

== Testing ==

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

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

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

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

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

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

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

Troubleshooting Legacy

2017-11-13T03:43:16Z

SaintAardvark: Add troubleshooting steps from https://community.libre.space/t/new-ground-station-problems/1197/4

== Client troubleshooting ==

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

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

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

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

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

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

== Signal troubleshooting ==

=== Not receiving anything? ===

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

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

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

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

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

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

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

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

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

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

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

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

=== Observations seem off-frequency? ===

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

Software contribution

2017-11-03T13:13:34Z

SaintAardvark: Add note about "0" branch for satnogs-client, fix formatting

If you are skilled in Python, Web Development (CSS/JS), or gnuradio we need your help! To find out how to help see each module below. You can also find us on our [[forum|https://community.libre.space]] or on irc/matrix in #satnogs

__TOC__

=== SatNOGS Client ===

'''Skills required: Python'''

The SatNOGS client is written in Python, targeting raspberry pi 3 as the reference architecture. It interfaces with the following applications:

* rotctld (Rotator control, part of hamlib)
* rigctld (Rig frequency control, part of hamlib)
* gr-satnogs (custom SatNOGS gnuradio scripts)

Architecture documentation: https://docs.satnogs.org/en/stable/satnogs-client/doc/architecture.html

Code repository: https://gitlab.com/librespacefoundation/satnogs/satnogs-client

Note that development happens on the "0" branch, with periodic merges to master for release; PRs should be submitted against the "0" branch.

=== SatNOGS Client image / setup script ===

'''Skills required: Linux administration, .deb packaging, Ansible'''

We provide a custom raspbian image for Raspberry Pi 3 using ''pi-gen'' and a satnogs-setup script that configures the client via Ansible. In addition we package gr-satnogs as a .deb through GitLab CI. If you would like to help out check out our repositories below:

* pi-gen repository: https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen
* gr-satnogs .deb repository: https://gitlab.com/librespacefoundation/satnogs/gr-satnogs-package
* satnogs-setup ansible repository: https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible

=== gr-satnogs ===

'''Skills required: gnuradio companion, C/C++, SDR'''

If you are skilled in writing custom gnuradio modules/blocks or piecing together gnuradio scripts in gnuradio-companion then gr-satnogs can use your help!

Code repository: https://gitlab.com/librespacefoundation/satnogs/gr-satnogs

=== SatNOGS DB ===

'''Skills required: Python / Django / CSS'''

The SatNOGS DB is written in Django (a Python web framework).

Installation documentation: https://docs.satnogs.org/en/stable/satnogs-db/docs/installation.html

Contribute documentation: https://docs.satnogs.org/en/stable/satnogs-db/docs/contribute.html

API documentation: https://docs.satnogs.org/en/stable/satnogs-db/docs/api.html

Code repository: https://gitlab.com/librespacefoundation/satnogs/satnogs-db

=== SatNOGS Network ===

'''Skills required: Python / Django / CSS / JS'''

The SatNOGS Network is written in Django (a Python web framework), and makes heavier use of javascript and d3.js for scheduling and visualizations.

Installation documentation: https://docs.satnogs.org/en/stable/satnogs-network/docs/installation.html

Contribute documentation: https://docs.satnogs.org/en/stable/satnogs-network/docs/contribute.html

Code repository: https://gitlab.com/librespacefoundation/satnogs/satnogs-network

Academic Papers

2017-11-03T04:27:12Z

SaintAardvark:

This is a non-exhaustive list of research papers that cite the SatNOGS projects. Some papers are describing the project and its subprojects in-depth; others mention SatNOGS in passing. If you are familiar with any other research paper that mentions SatNOGS, don't hesitate to add it to the list!

== 2014 ==
'''[http://telsoc.org/sites/default/files/tja/pdf/ajtde_v2n4a73_telecoms_and_disaster_management.pdf Telecommunications and Disaster management:Participatory approaches and climate change adaptation]'''
Marta Poblet, Hartmut Fünfgeld, Ian McShane ''(RMIT University)''

== 2015 ==
'''[http://ieeexplore.ieee.org/abstract/document/7386227/ Identification, Location, and Reception of Low Earth Orbit Satellites (LEO) Signals]'''
Jose Eduardo Oros, Javier Trejo, Ante Salcedo ''(Digital Systems Department, Instituto Tecnologico Autonomo de Mexico)''

'''[http://digitalcommons.usu.edu/smallsat/2015/all2015/38/ Software Defined Radio (SDR) for Parallel Satellite Reception in Mobile/Deployable Ground Segments]'''
Mamatha R. Maheshwarappa, Christopher P. Bridges ''(University of Surrey)'' Mark Bowyer ''(Airbus Defence and Space Ltd)''

'''[https://www.tapr.org/pdf/DCC2015-SatNOGS-AD0CQ.pdf SatNOGS:Satellite Networked Open Ground Station]'''
Daniel J. White, Ph.D., AD/0CQ ''(Valparaiso University)'' Ioannis Giannelos, Agisilaos Zissimatos, Eleftherios Kosmas,
Dimitrios Papadeas, Pierros Papadeas, Matthaios Papamathaiou, Nikolaos Roussos, Vasileios Tsiligiannis, Ioannis Charitopoulos ''(Libre Space Foundation)''

'''[http://theses.lib.vt.edu/theses/available/etd-10192015-163016/ A Distributed Software Framework for the Virginia Tech Ground Station]'''
Paul U. David ''(Virginia Polytechnic Institute and State University)''

'''[https://arxiv.org/abs/1507.08565 Collaborative peer production as an alternative to hierarchical internet based business systems]'''
Ganesh G., Debanjum Singh Solanky, Govindaraj R ''(Central Electronics Engineering Research Institute (CEERI), Chennai
Centre, CSIR Madras Complex)''

'''[http://scholar.valpo.edu/cus/454/?utm_source=scholar.valpo.edu%2Fcus%2F454&utm_medium=PDF&utm_campaign=PDFCoverPages Valparaiso University College of Engineering SatNOGS Open-Sourced Satellite Ground Station:UHF and VHF Antenna Theory and Construction]''' Thomas M. Biedron, Jonathon Clabuesch ''(Valparaiso University)''

== 2016 ==

'''[http://ieeexplore.ieee.org/document/7500529/ Implementation of an Actor Framework for a Ground Station]''' Paul David, Seth Hitefield, Zach Leffke, William C. Headley, Robert W. McGwier ''(Virginia Polytechnic Institute and State University)''

'''[http://scholar.valpo.edu/cus/503/ SatNOGS Website Project]]''' Dylan Snyder, Adya Pandey, Caitlyn Marko, John Eric Tiessen, Dr. Nicholas Rosasco ''(Valparaiso University)''

'''[https://link.springer.com/chapter/10.1007/978-3-319-47289-8_15 Connecting the Dots: Informing Location-Based Services of Space Usage Rules]''' Pavel Andreevich Samsonov ''(Expertise Center for Digital MediaHasselt University - tUL – iMinds)''

'''[http://scholar.valpo.edu/cus/498/ SatNOGS Project]''' Ashley LeBlanc, John White, Chris Paradiso, Grace Freigang, Paul Flaten, Dan White, PhD ''(Valparaiso University)''

== 2017 ==

'''[http://ieeexplore.ieee.org/document/7500716/ System overview of the Virginia Tech Ground Station]''' Seth Hitefield, Zach Leffke, Michael Fowler, Robert W. McGwier ''(Virginia Polytechnic Institute and State University)''

'''[http://epubs.surrey.ac.uk/813388/ Software defined radio (SDR) architecture for concurrent multi-satellite communications.]''' Maheshwarappa Mamatha ''(University of Surrey)''

'''[https://halshs.archives-ouvertes.fr/halshs-01615472/ Les développeurs, une nouvelle classe sociale?]''' Paris Chrysos ''(Institut supérieur du commerce de Paris)''

'''[http://epubs.surrey.ac.uk/812783/ Improvements in CPU & FPGA Performance for Small Satellite SDR Applications]''' Mamatha R. Maheshwarappa, Christopher P. Bridges ''(University of Surrey)'' Mark Bowyer ''(Airbus Defence and Space Ltd)''

'''[http://nemertes.lis.upatras.gr/jspui/handle/10889/10553 Design, analysis and optimization of a micro-satellite for the study of lower thermosphere and re-entry conditions]''' Andreas G. Ampatzoglou ''(University of Patras)''

'''[http://www.sciencedirect.com/science/article/pii/S1877050917315338?via%3Dihub A Prototype of an Integrated Telemetry Receiving System with Volunteers: Designs of a Simple Receiver, a Protocol, and an Intelligent Information Processing]''' Masahiro Tokumitsu, Masaki Kusakabe, Souta Ogura ''(Department of Electrical and Control Engineering, National Institute of Technology, Yonago College,)'' Fumio Asai, Satoshi Aoki ''(Department of Computer Engineering, National Institute of Technology, Nara College)'' TakuTakada ''(Department of Social Design Engineering, National Institute of Technology, Kochi College)'' Makoto Wakabayashi ''(Department of Electrical and Computer Engineering, National Institute of Technology, Niihama College,)'' Yoshiteru Ishida ''(Department of Computer Science and Engineering, Toyohashi University of Technology)''

'''[http://hdl.handle.net/11250/2462967 Ground station considerations for the AMOS satellite programme]''' Øyvind Karlsen ''Norwegian University of Science and Technology'' (Masters Thesis)

== 2018 (pre-published) ==

'''[https://link.springer.com/chapter/10.1007/978-3-319-56218-6_16 Doing Science with Nano-satellites]''' Gregorio A., Cuttin A., Fragiacomo M., Messerotti M. ''(Department of PhysicsUniversity of Trieste, PicoSaTs SRL, INAF, Osservatorio Astronomico di Trieste, Department of Engineering and ArchitectureUniversity of Trieste)''

Introduction

2017-10-24T04:37:24Z

SaintAardvark:

==SatNOGS==
SatNOGS (Satellite Networked Open Ground Station) project is a free software and open source hardware platform aimed at creating a satellite ground station network. The scope of the project is to create a full stack of open technologies based on open standards, and the construction of a full ground station as a showcase of the stack.

In order to implement such a stack, the four following different sub-projects are being developed.

===Network===

SatNOGS Network is a web application for scheduling observations across the network of ground stations. It facilitates the coordination of satellite signal observations, and scheduling such observations among the satellite ground-stations connected on the network.

===Database===

SatNOGS Database is a crowd-sourced application allowing its users to suggest satellite transmitter information for currently active satellites. Its data are available via an API or via a web application interface, allowing other project to use its satellite transmitter information.

===Client===

SatNOGS Client is the software to run on ground stations, usually on embedded systems, that receives the scheduled observations from the Network, receives the satellite transmission and sends it back to the Network web app.

===Ground Station===

SatNOGS Ground Station is an open source hardware ground station instrumentation with a rotator, antennas, electronics and connected to the Client. It is based on 3D printed components and readily available materials.

==Presentations on SatNOGS==

* Scott Bragg presented [https://www.youtube.com/watch?v=BKULw0NXhyI "Decoding Satellites with SatNOGS"] at linux.conf.au in 2017.
* Manolis Surligas presented [https://www.youtube.com/watch?v=zs_J1wlIpMs "SatNOGS: An SDR-based Satellite Networked Open Ground Station"] at FOSDEM 2017.
* Dan White presented ["SatNOGS: Satelllite Networked Ground Stations"] at the Digital Communications Conference in 2015.

==Academic papers on SatNOGS==

* [[Academic Papers]]

Get In Touch

2017-10-18T14:23:42Z

SaintAardvark:

Having problems operating your ground station? Need advice on how to get started? Got a bug that needs fixing, or a feature that needs adding? We'd love to hear from you!

=Ask questions on the forum=

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

=Chat with us on our Matrix room=

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

=File an issue on our Gitlab repositories=

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

=Check our status page=

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

Operation

2017-10-15T23:06:13Z

SaintAardvark: Add screenshot of "Discuss" button in Observation page

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

* Note: 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. This may change in the future, but for now even a faint sign on the waterfall is enough to make it valid.

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

Categories of observations:

* '''Good'''
** You should mark observations as "Good" when it is clear from the waterfall and/or audio recording that a satellite is present.
* '''Bad'''
** You should mark observations as "Bad" when by examining the waterfall and/or audio it is obvious that there was no satellite detected in this observation.

Below is a collection of waterfalls with possible results of observations:
<gallery heights=400px widths=200px>
File:Waterfall_20657_2017-10-15T10-07-51.png|'''Good''': Satellite is visible (bars-bursts of data in the middle). ''Note that the hyperbola lines are local noise''
File:Waterfall_20534_2017-10-15T07-21-24.png|'''Bad''': Typical empty waterfall with no visible signals.
File:Waterfall 20499 2017-10-15T07-17-32.png|'''Good''': Although drifting, satellite is clearly visible around the center.
File:Waterfall 20506 2017-10-15T06-47-36.png|'''Good''': Faint CW signal around center-left. ''Note you might have to expand image to notice it''
File:Waterfall_20571_2017-10-15T05-25-56.png|'''Good''': Clearly visible FM transmission. ''Note that the swinging lines are terrestrial noise''
File:Waterfall 20483 2017-10-15T05-12-49.png|'''Good''': Straight line in the center bottom is a satellite. ''Note transmission on left bottom is the same satellite on a different frequency''
</gallery>

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

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. (Note: this 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.)

File:Observation with discuss button highlighted.png

2017-10-15T23:00:42Z

SaintAardvark: Screenshot of observation page with "Discuss" button highlighted.

Screenshot of observation page with "Discuss" button highlighted.

Operation

2017-10-15T20:00:11Z

SaintAardvark:

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

* Note: 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. This may change in the future, but for now even a faint sign on the waterfall is enough to make it valid.

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

Categories of observations:

* '''Good'''
** You should mark observations as "Good" when it is clear from the waterfall and/or audio recording that a satellite is present.
* '''Bad'''
** You should mark observations as "Bad" when by examining the waterfall and/or audio it is obvious that there was no satellite detected in this observation.

Below is a collection of waterfalls with possible results of observations:
<gallery heights=400px widths=200px>
File:Waterfall_20657_2017-10-15T10-07-51.png|'''Good''': Satellite is visible (bars-bursts of data in the middle). ''Note that the hyperbola lines are local noise''
File:Waterfall_20534_2017-10-15T07-21-24.png|'''Bad''': Typical empty waterfall with no visible signals.
File:Waterfall 20499 2017-10-15T07-17-32.png|'''Good''': Although drifting, satellite is clearly visible around the center.
File:Waterfall 20506 2017-10-15T06-47-36.png|'''Good''': Faint CW signal around center-left. ''Note you might have to expand image to notice it''
File:Waterfall_20571_2017-10-15T05-25-56.png|'''Good''': Clearly visible FM transmission. ''Note that the swinging lines are terrestrial noise''
File:Waterfall 20483 2017-10-15T05-12-49.png|'''Good''': Straight line in the center bottom is a satellite. ''Note transmission on left bottom is the same satellite on a different frequency''
</gallery>

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

Operation

2017-10-15T19:41:34Z

SaintAardvark: Add link to feedback; earlier edit was to add info about criteria for marking observations good/bad

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

* Note: 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. This may change in the future, but for now even a faint sign on the waterfall is enough to make it valid.

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

Categories of observations:

* '''Good'''
** You should mark observations as "Good" when it is clear from the waterfall and/or audio recording that a satellite is present.
* '''Bad'''
** You should mark observations as "Bad" when by examining the waterfall and/or audio it is obvious that there was no satellite detected in this observation.

Below is a collection of waterfalls with possible results of observations:
<gallery heights=400px widths=200px>
File:Waterfall_20657_2017-10-15T10-07-51.png|'''Good''': Satellite is visible (bars-bursts of data in the middle). ''Note that the hyperbola lines are local noise''
File:Waterfall_20534_2017-10-15T07-21-24.png|'''Bad''': Typical empty waterfall with no visible signals.
File:Waterfall 20499 2017-10-15T07-17-32.png|'''Good''': Although drifting, satellite is clearly visible around the center.
File:Waterfall 20506 2017-10-15T06-47-36.png|'''Good''': Faint CW signal around center-left. ''Note you might have to expand image to notice it''
File:Waterfall_20571_2017-10-15T05-25-56.png|'''Good''': Clearly visible FM transmission. ''Note that the swinging lines are terrestrial noise''
File:Waterfall 20483 2017-10-15T05-12-49.png|'''Good''': Straight line in the center bottom is a satellite. ''Note transmission on left bottom is the same satellite on a different frequency''
</gallery>

If you're still unsure about an observation, post a link to it on [https://community.libre.space/c/observations the Observations forum] and ask for feedback.

Operation

2017-10-15T19:34:58Z

SaintAardvark:

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

* Note: 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. This may change in the future, but for now even a faint sign on the waterfall is enough to make it valid.

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

Categories of observations:

* '''Good'''
** You should mark observations as "Good" when it is clear from the waterfall and/or audio recording that a satellite is present.
* '''Bad'''
** You should mark observations as "Bad" when by examining the waterfall and/or audio it is obvious that there was no satellite detected in this observation.

Below is a collection of waterfalls with possible results of observations:
<gallery heights=400px widths=200px>
File:Waterfall_20657_2017-10-15T10-07-51.png|'''Good''': Satellite is visible (bars-bursts of data in the middle). ''Note that the hyperbola lines are local noise''
File:Waterfall_20534_2017-10-15T07-21-24.png|'''Bad''': Typical empty waterfall with no visible signals.
File:Waterfall 20499 2017-10-15T07-17-32.png|'''Good''': Although drifting, satellite is clearly visible around the center.
File:Waterfall 20506 2017-10-15T06-47-36.png|'''Good''': Faint CW signal around center-left. ''Note you might have to expand image to notice it''
File:Waterfall_20571_2017-10-15T05-25-56.png|'''Good''': Clearly visible FM transmission. ''Note that the swinging lines are terrestrial noise''
File:Waterfall 20483 2017-10-15T05-12-49.png|'''Good''': Straight line in the center bottom is a satellite. ''Note transmission on left bottom is the same satellite on a different frequency''
</gallery>

Troubleshooting Legacy

2017-10-15T19:26:49Z

SaintAardvark: Add rotctld error and fixes

== Client troubleshooting ==

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

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

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

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

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

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

== Signal troubleshooting ==

=== Not receiving anything? ===

Make sure the satellite you are testing observations against is active and recently received by others on [https://network.satnogs.org our production network site]. If you click on a satellite name, a popup will appear and give you the option to click on "Past Observations". If everything in the past shows red, then the problem is likely with that satellite.
* SO-50 is a good satellite to use for testing as it is a strong FM voice signal assuming you have UHF capabilities. Schedule using "PE0SAT - Mode V/U FM Voice - 436.794 MHz". Here is an example to compare against: https://network.satnogs.org/observations/3334/
* ISS is a good test for VHF as the APRS digipeater is alive again (as of this writing; check [https://www.issfanclub.com/ issfanclub.com] for up-to-date information). When you schedule it, be sure to select the APRS downlink.

=== Observations seem off-frequency? ===

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

Software contribution

2017-10-15T19:16:06Z

SaintAardvark: Correct links to repos

If you are skilled in Python, Web Development (CSS/JS), or gnuradio we need your help! To find out how to help see each module below. You can also find us on our [[forum|https://community.libre.space]] or on irc/matrix in #satnogs

__TOC__

=== SatNOGS Client ===

'''Skills required: Python'''

The SatNOGS client is written in Python, targeting raspberry pi 3 as the reference architecture. It interfaces with the following applications:

* rotctld (Rotator control, part of hamlib)
* rigctld (Rig frequency control, part of hamlib)
* gr-satnogs (custom SatNOGS gnuradio scripts)

Architecture documentation: https://docs.satnogs.org/en/stable/satnogs-client/doc/architecture.html

Code repository: https://gitlab.com/librespacefoundation/satnogs/satnogs-client

=== gr-satnogs ===

'''Skills required: gnuradio companion, C/C++, SDR'''

If you are skilled in writing custom gnuradio modules/blocks or piecing together gnuradio scripts in gnuradio-companion then gr-satnogs can use your help!

Code repository: https://gitlab.com/librespacefoundation/satnogs/gr-satnogs

=== SatNOGS DB ===

'''Skills required: Python / Django / CSS'''

The SatNOGS DB is written in Django (a Python web framework).

Installation documentation: https://docs.satnogs.org/en/stable/satnogs-db/docs/installation.html

Contribute documentation: https://docs.satnogs.org/en/stable/satnogs-db/docs/contribute.html

API documentation: https://docs.satnogs.org/en/stable/satnogs-db/docs/api.html

Code repository: https://gitlab.com/librespacefoundation/satnogs/satnogs-db

=== SatNOGS Network ===

'''Skills required: Python / Django / CSS / JS'''

The SatNOGS Network is written in Django (a Python web framework), and makes heavier use of javascript and d3.js for scheduling and visualizations.

Installation documentation: https://docs.satnogs.org/en/stable/satnogs-network/docs/installation.html

Contribute documentation: https://docs.satnogs.org/en/stable/satnogs-network/docs/contribute.html

Code repository: https://gitlab.com/librespacefoundation/satnogs/satnogs-network

Antennas

2017-10-15T15:03:35Z

SaintAardvark: Fix links to v4 and latest Helical instructions and design files

Antennas developed and used by SatNOGS rotators

==SatNOGS antennas==

To cover the needs of the SatNOGS community the SatNOGS team has developed a number of antennas.

===Yagi===

A Yagi antenna is the simplest antenna for the novice maker.

===Cross Yagi UHF v1===

A cross Yagi UHF antenna.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Yagi/Cross-Yagi-UHF-v1 v1 Design files]

===Helical v1===

The first iteration of our helical UHF antenna allows users to create their own helical antenna design using only 3D printed parts.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical/UHF%20lhcp Design files]

* [https://ohai.satnogs.org/workflow/helical-antenna-v1/hardware/ Assembly instructions]

===Helical v4===

This iteration is more rigid, but you need to have access to CNCed parts.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical/UHF-434-8 Design files]

* [https://satnogs.dozuki.com/Guide/Helical+Antenna+v4/11 Assembly instructions]

===Helical 435-8===

This iteration is our latest version of the Helical antenna design; it comes in RHCP configuration. The supports are made from aluminum, and will require a drill press.

* [https://gitlab.com/librespacefoundation/satnogs/satnogs-antennas/tree/master/Helical/UHF-435-8 Design files]

* [https://ohai.satnogs.org/project/UHF_Helical_8/hardware/ Assembly instructions]

==Commercial Antennas==

===[http://www.arrowantennas.com/arrowii/146-437.html Arrow II Satellite Antenna]===

==DIY Antenna designs==

Get In Touch

2017-10-15T14:20:16Z

SaintAardvark: Add "How to get in touch" page