SatNOGS Wiki - User contributions [en]

SatNOGS Optical

2022-08-27T20:53:03Z

Jebba: Initial page for SatNOGS Optical

==Introduction==
SatNOGS Optical is a project by the Libre Space Foundation to add optical observations to the distributed network. It is under early development.

== Software ==
See:

* stvid
https://github.com/cbassa/stvid

* satpredict
https://github.com/cbassa/satpredict

* sattools
https://github.com/cbassa/sattools

== Hardware ==

* Sony IMX174 based cameras have worked well.
* A 50mm lens, the faster the better, in the F1.2 - F1.8 range.
* A Raspberry Pi 4 or faster embedded computer.
* A mount, doesn't need to be tracking.

== Further Info ==

* Optical Communications and Photonics MakerSpace
https://libre.space/projects/optical-communications-and-photonics-makerspace/

* SIDLOC
https://libre.space/projects/sidloc/

== Development ==
Discussion in #satnogs-optical:matrix.org.

[[Category:Hardware]]
[[Category:Software]]
[[Category:Develop]]

User:Jebba

2022-08-27T20:44:10Z

Jebba: spacecruft

I'm Jeff Moe.

* https://spacecruft.org

Ground stations:

* [https://network.satnogs.org/stations/2733/ spacecruft]

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

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

Decode Telemetry and Packets

2022-07-29T01:51:47Z

Jebba: add gr-satellites

== Introduction ==

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

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

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

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

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

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

SoX supports demodulating the following modes:

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

===References===

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

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

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

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

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

===References===

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

==multimon-ng==

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

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

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

===How to AFSK===

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

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

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

===References===

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

==Direwolf==

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

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

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

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

==gr-satellites==
GNU Radio decoder for Amateur satellites.

https://github.com/daniestevez/gr-satellites

SatNOGS gr_satellites combines gr-satellites with the satnogs-client and satnogs-flowgraphs.

https://github.com/kng/satnogs_gr-satellites

Discussion:

https://community.libre.space/t/install-the-satnogs-gr-satellites-addon-and-use-your-station-more/8027

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

===Usage===

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

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

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

 

==WXtoImg==

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

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

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

===Usage===

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

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

*Then invoke command line interface of WXtoIMG with:

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

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

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

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

__NOEDITSECTION__

Qubik

2020-03-03T01:29:30Z

Jebba: Qubik stub

== Introduction ==
Libre Space Foundation is currently developing and integrating 2 pocketqube satellites (QUBIK-1 & QUBIK-2) and supplying a pocketqube deployer (PICOBUS) to be flown as part of the DREAM payloads program on the inaugural Firefly Alpha launch from Firefly Aerospace. The satellites are expected to be short-lived with only ~3 weeks of predicted orbit lifespan. This short timeframe will be enough though for the communications experiment they are tasked to perform. Specifically, the satellites will be conducting a series of telecommunication related experiments, while at the same time, ground station analysis of the received signals will try to exploit doppler variations in order to perform orbit determination and satellite identification from ground stations around the world though the SatNOGS Network.

== See also ==
* [https://libre.space/projects/qubik/ Qubik Project]
* [https://gitlab.com/librespacefoundation/qubik Qubik source code repositories]
* [[SatNOGS Network]]
* [https://firefly.com/firefly-aerospace-announces-dream-payload-participants/ DREAM payloads program]
* [[Space Situational Awareness]]

[[Category:Satellite]]
[[Category:Infrastructure]]

SatNOGS Assembly Instructions

2020-03-03T01:24:45Z

Jebba: Jebba moved page OHAI to SatNOGS Assembly Instructions: Clarity

== Introduction ==
SatNOGS Assembly Instructions are available here:

* [https://ohai.satnogs.org/ SatNOGS OHAI]

[[File:Satnogs-ohai-cap.png|800px|SatNOGS OHAI Screen capture]]

== See also ==
* [[Build]]

[[Category:Build]]
[[Category:Hardware]]
[[Category:Develop]]
[[Category:Infrastructure]]

OHAI

2020-03-03T01:24:45Z

Jebba: Jebba moved page OHAI to SatNOGS Assembly Instructions: Clarity

#REDIRECT [[SatNOGS Assembly Instructions]]

SatNOGS DB

2020-03-03T00:57:35Z

Jebba: * [https://libre.space/2020/03/02/space-situational-awareness/ Space Situational Awareness – The story so far and an open way forward]

__NOTOC__

== Introduction ==

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

[[File:Satnogs-db-cap.png|800px|SatNOGS DB Screen capture]]

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

==Contribute==

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

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

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

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

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

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

#Log in to db.satnogs.org
#Navigate to https://db.satnogs.org/admin (if you are seeing a login screen, you are either not logged in to db.satnogs.org, or don't have moderator permissions)
#Click on Base::Suggestions
#Click on the suggestion you want to review and carefully check the data, especially the citation URL
#When you are ready to approve or reject 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....

==Documentation & Installation==

You can find documentation and installation instructions about the project in our [https://docs.satnogs.org/projects/satnogs-db/en/stable/ Read the Docs instance].

== See also ==
* [[SatNOGS Network]]
* [https://libre.space/2020/03/02/space-situational-awareness/ Space Situational Awareness – The story so far and an open way forward]

[[Category:Infrastructure]]
[[Category:Operate]]
[[Category:Satellite]]
[[Category:RF Modes]]

SSA

2020-03-03T00:53:03Z

Jebba: #REDIRECT Space_Situational_Awareness

#REDIRECT [[Space_Situational_Awareness]]

Space Situational Awareness

2020-03-03T00:52:10Z

Jebba: Space Situational Awareness stub

== Introduction ==
We in Libre Space Foundation believe that all people shall have access to outer space, space technologies, and space data. Space Situational Awareness data are critical for our understanding, peaceful coexistence, and exploration of space. We believe that to achieve that, all SSA data should be gathered, processed, licensed, and disseminated as Open Data.

== See also ==
* [https://libre.space/2020/03/02/space-situational-awareness/ Space Situational Awareness – The story so far and an open way forward]

[[Category:Infrastructure]]
[[Category:Satellite]]

SatNOGS Setup Legacy

2020-02-26T15:41:45Z

Jebba: rm wrong

==Introduction==
<code>satnogs-setup</code> provides a set of scripts for configuring a '''SatNOGS Client''' system. <code>satnogs-setup</code> main function is to bring up a menu-driven console configuration utility and provision the system using [[SatNOGS Client Ansible|Ansible]].

==Initial Setup==
Right after the first boot of the system, packages and the configuration tool itself '''must be updated'''. Follow the [[SatNOGS Client Setup#Updating SatNOGS Client Software|Updating]] instruction found below.

To configure a '''SatNOGS Client''' system:

#SSH into the system and run <code>sudo satnogs-setup</code>; this will bring up the configuration menu
#Set '''all''' options in '''Basic Configuration''' (see below)
#Select <code>Apply</code> and the Raspberry Pi will configure itself; this may take some time
#Select <code>Back</code> to exit
{{Message|You can always reconfigure the software by running <code>sudo satnogs-setup</code> again.}}
===Basic Configuration===
{| class="wikitable"
!Setting
!Description
|-
|<code>SATNOGS_API_TOKEN</code>
|The API token assigned to your ground station on the SatNOGS Network website, please don’t share your api key as this can give access to anyone to upload and change things in network related to your station and its observations.
|-
|<code>SATNOGS_RX_DEVICE</code>
|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/airspymini</code>, <code>lime</code>, or <code>hackrf</code>.
|-
|<code>SATNOGS_STATION_ELEV</code>
|The height of your ground station above sea level in metres.
|-
|<code>SATNOGS_STATION_ID</code>
|The '''numeric ID''' assigned to your station in the SatNOGS Network site when the groundstation was created.
|-
|<code>SATNOGS_STATION_LAT</code>
|The latitude of your station. North is positive, south is negative.
|-
|<code>SATNOGS_STATION_LON</code>
|The longitude of your station. East is positive, west is negative.
|-
|<code>HAMLIB_UTILS_ROT_ENABLED</code>
|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 [[No rotator|No rotator setup]]), enter <code>NO</code>.
|-
|<code>HAMLIB_UTILS_ROT_OPTS</code>
|Options for rotcld:
For a yaesu rotator, use <code>-m 601 -r /dev/ttyACM0 -s 9600 -T 0.0.0.0</code>

For a SatNOGS rotator <code>-m 204 -s 19200 -r /dev/ttyACM0 -C timeout=200</code> or <code>-m 204 -s 19200 -r /dev/ttyUSB0 -C timeout=200</code>
|}

==Advanced Setup==
{{Warning|Changing these settings is ''not'' recommended unless you're developing SatNOGS.}}A more detailed description on setting up a development environment using the SatNOGS reference setup is given in [[SatNOGS_Client_Development]].

NOTE: To get your station online, you need to set SATNOGS_NETWORK_API_URL to https://network.satnogs.org/api/
{| class="wikitable"
!Setting
!Description
|-
|<code>EXPERIMENTAL</code>
|Install latest (experimental) versions of all software
|-
|<code>APT_REPOSITORY</code>
|This options allows you to change the SatNOGS packages repository. For example, to install unstable package builds use:
<code>deb <nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10</nowiki> ./</code>
|-
|<code>APT_KEY_URL</code>
|This options allows you to change the SatNOGS packages repository key URL. For example, to install unstable package builds use:
<code><nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key</nowiki></code>
|-
|<code>APT_KEY_ID</code>
|This options allows you to specify an alternative SatNOGS packages repository key ID.
|-
|<code>SATNOGS_CLIENT_URL</code>
|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:

*<code>git+<nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client.git@master</nowiki></code> -- the 'master' branch (the current development version) of satnogs-client
*<code><nowiki>git+https://gitlab.com/jdoe/satnogs-client.git@new-feature</nowiki></code> -- the 'new-feature' branch of jdoe's fork of satnogs-client
|-
|<code>SATNOGS_RADIO_GR_SATNOGS_VERSION</code>
|This options allows you to change the version of gr-satnogs package to be installed. For example:
<code>1.5.1-1</code>
|-
|<code>RF_GAIN</code>
|RF Gain value for your SDR hardware. Defaults can be found [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/-/blob/v1.5.1/python/hw_settings.py here].

*For rtl-sdr possible values are the following: <code>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</code>
|-
|<code>SATNOGS_SOAPY_RX_DEVICE</code>
|(only applicable if '''EXPERIMENTAL=True''') Required. If you are using an RTL-SDR, this is <code>driver=rtlsdr</code> (TODO:confirm!). See [https://github.com/pothosware/SoapyRTLSDR/wiki#modules pothosware/SoapyRTLSDR/wiki#modules] for other SDR modules (linked in the navigation bar at the right side of the page).

If multiple devices are attached to your station you should also specify the serial of the desired device here, e.g. <code>driver=uhd,serial=3164495</code>.
|-
|<code>SATNOGS_RX_SAMP_RATE</code>
|(only applicable if '''EXPERIMENTAL=True''') Required. Specify the receiver sampling rate. Example value: <code>2.048e6</code> (for 2MHz) (TODO:confirm!).
|-
|<code>SATNOGS_RF_GAIN</code>
|(only applicable if '''EXPERIMENTAL=True''') RF Gain value for your SDR hardware. Run <code>SoapySDRUtil --probe</code> to see all possible gain values for your hardware.
|-
|<code>SATNOGS_RX_BANDWIDTH</code>
|(only applicable if '''EXPERIMENTAL=True''') TODO.
|-
|<code>SATNOGS_ANTENNA</code>
|(only applicable if '''EXPERIMENTAL=True''') TODO.
|}
==Updating SatNOGS Client Software==
To update SatNOGS software, including the configuration tool itself:

#SSH into the system and (re-)run <code>sudo satnogs-setup</code>; this will bring up the configuration menu
#Select <code>Update</code> to update the configuration tool and all distribution packages to the latest
#If you are prompt for a reboot during the upgrade, once the upgrade is finished, select <code>Reboot</code>, SSH back into the system and re-run <code>satnogs-config</code> to continue to the next step
#Select <code>Apply</code> and the Raspberry Pi will update itself; this may take some time
#Before exit, check at the top that you have the latest satnogs-client and gr-satnogs versions
#Select <code>Back</code> to exit

'''WARNING: An update can potentially interrupt a running observation!'''
===Upgrading from Debian 'stretch' to 'buster'===
Debian <code>stretch</code> is no longer supported. If you have already installed an older version of Debian or Raspbian SatNOGS image based on <code>stretch</code> (releases <= [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/tags/2018080300 2018080300]), you must upgrade to <code>buster</code> otherwise it will be impossible to receive updates or upgrades in the future.
====Method 1: Reflashing and reinstalling (recommended)====
The recommended method to upgrade to <code>buster</code> is reflashing the latest Raspbian SatNOGS image (or reinstalling latest Debian). Follow [[Raspberry Pi|Raspberry Pi]] installation instructions and reinstall from scratch.
====Method 2: Release upgrade using the configuration tool (advanced)====
{{Warning|Make sure you have a stable connection to the internet and your SatNOGS client during this process. Release upgrades can consume a lot of time, data and storage.}}To upgrade from stretch to buster using the configuration tool:

#SSH into the system
#Make sure you have enough free space on your SD card (>2GiB) by running <code>df -h /</code> on the console
#Run <code>sudo satnogs-setup</code> to bring up the configuration menu
#Select <code>Update</code> to update the configuration tool and all distribution packages to the latest; this will also prompt you for a distribution upgrade, if it detects that one is needed
#Keep an eye on the upgrade progress; <code>dpkg</code> may prompt for changes
#Once the upgrade is completed select <code>Reboot</code>
#After the reboot, SSH back into the system and make sure you are on the correct release by running <code>lsb_release -a</code>
#Re-run <code>sudo satnogs-setup</code> and select <code>Update</code> and then <code>Apply</code>; this may take some time
#Before exit, check at the top that you have the latest satnogs-client and gr-satnogs versions
#Select <code>Back</code> to exit

==Verification of correct installation==
To see if satnogs-client has started successfully, check the logs with journalctl:<pre>
$ journalctl -u satnogs-client.service
</pre>You should see entries running approximately once per minute that look like this:<pre>
Oct 01 23:02:13 raspberrypi satnogs-client[6695]: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
Oct 01 23:02:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:02:14,466 - satnogsclient - INFO - [LD] Downlink thread waiting for first downlink packet
Oct 01 23:03:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:14,450 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:03:14 UTC)" (scheduled at 2017-10-01 23:03:14.423393+00:00)
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,324 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,325 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,327 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,453 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.423393+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,484 - apscheduler.executors.default - INFO - Running job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.436367+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,489 - apscheduler.executors.default - INFO - Job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,627 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,628 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,629 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:05:14 UTC)" executed successfully
</pre>If you see that, great -- you're ready to [[Operation|schedule your first observation]]! If not, check out the [[Troubleshooting]] page.

==See also==

*[[SatNOGS Client Ansible]]

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

SatNOGS Setup Legacy

2020-02-26T07:19:34Z

Jebba: /* Initial Setup */

==Introduction==
<code>satnogs-setup</code> provides a set of scripts for configuring a '''SatNOGS Client''' system. <code>satnogs-setup</code> main function is to bring up a menu-driven console configuration utility and provision the system using [[SatNOGS Client Ansible|Ansible]].

==Initial Setup==
Right after the first boot of the system, packages and the configuration tool itself '''must be updated'''. Follow the [[SatNOGS Client Setup#Updating SatNOGS Client Software|Updating]] instruction found below.

To configure a '''SatNOGS Client''' system:

#SSH into the system and run <code>sudo satnogs-setup</code>; this will bring up the configuration menu
#Set '''all''' options in '''Basic Configuration''' (see below)
#Select <code>Apply</code> and the Raspberry Pi will configure itself; this may take some time
#Select <code>Back</code> to exit
{{Message|You can always reconfigure the software by running <code>sudo satnogs-setup</code> again.}}
===Basic Configuration===
{| class="wikitable"
!Setting
!Description
|-
|<code>SATNOGS_API_TOKEN</code>
|The API token assigned to your ground station on the SatNOGS Network website, please don’t share your api key as this can give access to anyone to upload and change things in network related to your station and its observations.
|-
|<code>SATNOGS_RX_DEVICE</code>
|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/airspymini</code>, <code>lime</code>, or <code>hackrf</code>; a complete list can be found by running: <code>SoapySDRUtil --info</code>
|-
|<code>SATNOGS_STATION_ELEV</code>
|The height of your ground station above sea level in metres.
|-
|<code>SATNOGS_STATION_ID</code>
|The '''numeric ID''' assigned to your station in the SatNOGS Network site when the groundstation was created.
|-
|<code>SATNOGS_STATION_LAT</code>
|The latitude of your station. North is positive, south is negative.
|-
|<code>SATNOGS_STATION_LON</code>
|The longitude of your station. East is positive, west is negative.
|-
|<code>HAMLIB_UTILS_ROT_ENABLED</code>
|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 [[No rotator|No rotator setup]]), enter <code>NO</code>.
|-
|<code>HAMLIB_UTILS_ROT_OPTS</code>
|Options for rotcld:
For a yaesu rotator, use <code>-m 601 -r /dev/ttyACM0 -s 9600 -T 0.0.0.0</code>

For a SatNOGS rotator <code>-m 204 -s 19200 -r /dev/ttyACM0 -C timeout=200</code> or <code>-m 204 -s 19200 -r /dev/ttyUSB0 -C timeout=200</code>
|}

==Advanced Setup==
{{Warning|Changing these settings is ''not'' recommended unless you're developing SatNOGS.}}A more detailed description on setting up a development environment using the SatNOGS reference setup is given in [[SatNOGS_Client_Development]].

NOTE: To get your station online, you need to set SATNOGS_NETWORK_API_URL to https://network.satnogs.org/api/
{| class="wikitable"
!Setting
!Description
|-
|<code>EXPERIMENTAL</code>
|Install latest (experimental) versions of all software
|-
|<code>APT_REPOSITORY</code>
|This options allows you to change the SatNOGS packages repository. For example, to install unstable package builds use:
<code>deb <nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10</nowiki> ./</code>
|-
|<code>APT_KEY_URL</code>
|This options allows you to change the SatNOGS packages repository key URL. For example, to install unstable package builds use:
<code><nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key</nowiki></code>
|-
|<code>APT_KEY_ID</code>
|This options allows you to specify an alternative SatNOGS packages repository key ID.
|-
|<code>SATNOGS_CLIENT_URL</code>
|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:

*<code>git+<nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client.git@master</nowiki></code> -- the 'master' branch (the current development version) of satnogs-client
*<code><nowiki>git+https://gitlab.com/jdoe/satnogs-client.git@new-feature</nowiki></code> -- the 'new-feature' branch of jdoe's fork of satnogs-client
|-
|<code>SATNOGS_RADIO_GR_SATNOGS_VERSION</code>
|This options allows you to change the version of gr-satnogs package to be installed. For example:
<code>1.5.1-1</code>
|-
|<code>RF_GAIN</code>
|RF Gain value for your SDR hardware. Defaults can be found [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/-/blob/v1.5.1/python/hw_settings.py here].

*For rtl-sdr possible values are the following: <code>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</code>
|-
|<code>SATNOGS_SOAPY_RX_DEVICE</code>
|(only applicable if '''EXPERIMENTAL=True''') Required. If you are using an RTL-SDR, this is <code>driver=rtlsdr</code> (TODO:confirm!). See [https://github.com/pothosware/SoapyRTLSDR/wiki#modules pothosware/SoapyRTLSDR/wiki#modules] for other SDR modules (linked in the navigation bar at the right side of the page).

If multiple devices are attached to your station you should also specify the serial of the desired device here, e.g. <code>driver=uhd,serial=3164495</code>.
|-
|<code>SATNOGS_RX_SAMP_RATE</code>
|(only applicable if '''EXPERIMENTAL=True''') Required. Specify the receiver sampling rate. Example value: <code>2.048e6</code> (for 2MHz) (TODO:confirm!).
|-
|<code>SATNOGS_RF_GAIN</code>
|(only applicable if '''EXPERIMENTAL=True''') RF Gain value for your SDR hardware. Run <code>SoapySDRUtil --probe</code> to see all possible gain values for your hardware.
|-
|<code>SATNOGS_RX_BANDWIDTH</code>
|(only applicable if '''EXPERIMENTAL=True''') TODO.
|-
|<code>SATNOGS_ANTENNA</code>
|(only applicable if '''EXPERIMENTAL=True''') TODO.
|}
==Updating SatNOGS Client Software==
To update SatNOGS software, including the configuration tool itself:

#SSH into the system and (re-)run <code>sudo satnogs-setup</code>; this will bring up the configuration menu
#Select <code>Update</code> to update the configuration tool and all distribution packages to the latest
#If you are prompt for a reboot during the upgrade, once the upgrade is finished, select <code>Reboot</code>, SSH back into the system and re-run <code>satnogs-config</code> to continue to the next step
#Select <code>Apply</code> and the Raspberry Pi will update itself; this may take some time
#Before exit, check at the top that you have the latest satnogs-client and gr-satnogs versions
#Select <code>Back</code> to exit

'''WARNING: An update can potentially interrupt a running observation!'''
===Upgrading from Debian 'stretch' to 'buster'===
Debian <code>stretch</code> is no longer supported. If you have already installed an older version of Debian or Raspbian SatNOGS image based on <code>stretch</code> (releases <= [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/tags/2018080300 2018080300]), you must upgrade to <code>buster</code> otherwise it will be impossible to receive updates or upgrades in the future.
====Method 1: Reflashing and reinstalling (recommended)====
The recommended method to upgrade to <code>buster</code> is reflashing the latest Raspbian SatNOGS image (or reinstalling latest Debian). Follow [[Raspberry Pi|Raspberry Pi]] installation instructions and reinstall from scratch.
====Method 2: Release upgrade using the configuration tool (advanced)====
{{Warning|Make sure you have a stable connection to the internet and your SatNOGS client during this process. Release upgrades can consume a lot of time, data and storage.}}To upgrade from stretch to buster using the configuration tool:

#SSH into the system
#Make sure you have enough free space on your SD card (>2GiB) by running <code>df -h /</code> on the console
#Run <code>sudo satnogs-setup</code> to bring up the configuration menu
#Select <code>Update</code> to update the configuration tool and all distribution packages to the latest; this will also prompt you for a distribution upgrade, if it detects that one is needed
#Keep an eye on the upgrade progress; <code>dpkg</code> may prompt for changes
#Once the upgrade is completed select <code>Reboot</code>
#After the reboot, SSH back into the system and make sure you are on the correct release by running <code>lsb_release -a</code>
#Re-run <code>sudo satnogs-setup</code> and select <code>Update</code> and then <code>Apply</code>; this may take some time
#Before exit, check at the top that you have the latest satnogs-client and gr-satnogs versions
#Select <code>Back</code> to exit

==Verification of correct installation==
To see if satnogs-client has started successfully, check the logs with journalctl:<pre>
$ journalctl -u satnogs-client.service
</pre>You should see entries running approximately once per minute that look like this:<pre>
Oct 01 23:02:13 raspberrypi satnogs-client[6695]: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
Oct 01 23:02:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:02:14,466 - satnogsclient - INFO - [LD] Downlink thread waiting for first downlink packet
Oct 01 23:03:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:14,450 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:03:14 UTC)" (scheduled at 2017-10-01 23:03:14.423393+00:00)
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,324 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,325 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,327 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,453 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.423393+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,484 - apscheduler.executors.default - INFO - Running job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.436367+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,489 - apscheduler.executors.default - INFO - Job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,627 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,628 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,629 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:05:14 UTC)" executed successfully
</pre>If you see that, great -- you're ready to [[Operation|schedule your first observation]]! If not, check out the [[Troubleshooting]] page.

==See also==

*[[SatNOGS Client Ansible]]

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

SatNOGS Setup Legacy

2020-02-26T07:16:36Z

Jebba: /* Basic Configuration */ SoapySDRUtil --info + lime

==Introduction==
<code>satnogs-setup</code> provides a set of scripts for configuring a '''SatNOGS Client''' system. <code>satnogs-setup</code> main function is to bring up a menu-driven console configuration utility and provision the system using [[SatNOGS Client Ansible|Ansible]].

==Initial Setup==
Right after the first boot of the system, packages and the configuration tool itself '''must be updated'''. Follow the [[SatNOGS Client Setup#Updating SatNOGS Client Software|Updating]] instruction found below.

To configure a '''SatNOGS Client''' system:

#SSH into the system and run <code>sudo satnogs-setup</code>; this will bring up the configuration menu
#Set '''all''' options in '''Basic Configuration''' (see below)
#Select <code>Apply</code> and the Raspberry Pi will configure itself; this may take some time
#Select <code>Back</code> to exit
{{Message|You can always reconfigure the software by running <code>sudo satnogs-setup</code> again.}}
===Basic Configuration===
{| class="wikitable"
!Setting
!Description
|-
|<code>SATNOGS_API_TOKEN</code>
|The API token assigned to your ground station on the SatNOGS Network website, please don’t share your api key as this can give access to anyone to upload and change things in network related to your station and its observations.
|-
|<code>SATNOGS_RX_DEVICE</code>
|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/airspymini</code>, <code>lime</code>, or <code>hackrf</code>; a complete list can be found by running:
<code>SoapySDRUtil --info</code>
|-
|<code>SATNOGS_STATION_ELEV</code>
|The height of your ground station above sea level in metres.
|-
|<code>SATNOGS_STATION_ID</code>
|The '''numeric ID''' assigned to your station in the SatNOGS Network site when the groundstation was created.
|-
|<code>SATNOGS_STATION_LAT</code>
|The latitude of your station. North is positive, south is negative.
|-
|<code>SATNOGS_STATION_LON</code>
|The longitude of your station. East is positive, west is negative.
|-
|<code>HAMLIB_UTILS_ROT_ENABLED</code>
|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 [[No rotator|No rotator setup]]), enter <code>NO</code>.
|-
|<code>HAMLIB_UTILS_ROT_OPTS</code>
|Options for rotcld:
For a yaesu rotator, use <code>-m 601 -r /dev/ttyACM0 -s 9600 -T 0.0.0.0</code>

For a SatNOGS rotator <code>-m 204 -s 19200 -r /dev/ttyACM0 -C timeout=200</code> or <code>-m 204 -s 19200 -r /dev/ttyUSB0 -C timeout=200</code>
|}

==Advanced Setup==
{{Warning|Changing these settings is ''not'' recommended unless you're developing SatNOGS.}}A more detailed description on setting up a development environment using the SatNOGS reference setup is given in [[SatNOGS_Client_Development]].

NOTE: To get your station online, you need to set SATNOGS_NETWORK_API_URL to https://network.satnogs.org/api/
{| class="wikitable"
!Setting
!Description
|-
|<code>EXPERIMENTAL</code>
|Install latest (experimental) versions of all software
|-
|<code>APT_REPOSITORY</code>
|This options allows you to change the SatNOGS packages repository. For example, to install unstable package builds use:
<code>deb <nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10</nowiki> ./</code>
|-
|<code>APT_KEY_URL</code>
|This options allows you to change the SatNOGS packages repository key URL. For example, to install unstable package builds use:
<code><nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs-unstable/Raspbian_10/Release.key</nowiki></code>
|-
|<code>APT_KEY_ID</code>
|This options allows you to specify an alternative SatNOGS packages repository key ID.
|-
|<code>SATNOGS_CLIENT_URL</code>
|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:

*<code>git+<nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client.git@master</nowiki></code> -- the 'master' branch (the current development version) of satnogs-client
*<code><nowiki>git+https://gitlab.com/jdoe/satnogs-client.git@new-feature</nowiki></code> -- the 'new-feature' branch of jdoe's fork of satnogs-client
|-
|<code>SATNOGS_RADIO_GR_SATNOGS_VERSION</code>
|This options allows you to change the version of gr-satnogs package to be installed. For example:
<code>1.5.1-1</code>
|-
|<code>RF_GAIN</code>
|RF Gain value for your SDR hardware. Defaults can be found [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/-/blob/v1.5.1/python/hw_settings.py here].

*For rtl-sdr possible values are the following: <code>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</code>
|-
|<code>SATNOGS_SOAPY_RX_DEVICE</code>
|(only applicable if '''EXPERIMENTAL=True''') Required. If you are using an RTL-SDR, this is <code>driver=rtlsdr</code> (TODO:confirm!). See [https://github.com/pothosware/SoapyRTLSDR/wiki#modules pothosware/SoapyRTLSDR/wiki#modules] for other SDR modules (linked in the navigation bar at the right side of the page).

If multiple devices are attached to your station you should also specify the serial of the desired device here, e.g. <code>driver=uhd,serial=3164495</code>.
|-
|<code>SATNOGS_RX_SAMP_RATE</code>
|(only applicable if '''EXPERIMENTAL=True''') Required. Specify the receiver sampling rate. Example value: <code>2.048e6</code> (for 2MHz) (TODO:confirm!).
|-
|<code>SATNOGS_RF_GAIN</code>
|(only applicable if '''EXPERIMENTAL=True''') RF Gain value for your SDR hardware. Run <code>SoapySDRUtil --probe</code> to see all possible gain values for your hardware.
|-
|<code>SATNOGS_RX_BANDWIDTH</code>
|(only applicable if '''EXPERIMENTAL=True''') TODO.
|-
|<code>SATNOGS_ANTENNA</code>
|(only applicable if '''EXPERIMENTAL=True''') TODO.
|}
==Updating SatNOGS Client Software==
To update SatNOGS software, including the configuration tool itself:

#SSH into the system and (re-)run <code>sudo satnogs-setup</code>; this will bring up the configuration menu
#Select <code>Update</code> to update the configuration tool and all distribution packages to the latest
#If you are prompt for a reboot during the upgrade, once the upgrade is finished, select <code>Reboot</code>, SSH back into the system and re-run <code>satnogs-config</code> to continue to the next step
#Select <code>Apply</code> and the Raspberry Pi will update itself; this may take some time
#Before exit, check at the top that you have the latest satnogs-client and gr-satnogs versions
#Select <code>Back</code> to exit

'''WARNING: An update can potentially interrupt a running observation!'''
===Upgrading from Debian 'stretch' to 'buster'===
Debian <code>stretch</code> is no longer supported. If you have already installed an older version of Debian or Raspbian SatNOGS image based on <code>stretch</code> (releases <= [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/tags/2018080300 2018080300]), you must upgrade to <code>buster</code> otherwise it will be impossible to receive updates or upgrades in the future.
====Method 1: Reflashing and reinstalling (recommended)====
The recommended method to upgrade to <code>buster</code> is reflashing the latest Raspbian SatNOGS image (or reinstalling latest Debian). Follow [[Raspberry Pi|Raspberry Pi]] installation instructions and reinstall from scratch.
====Method 2: Release upgrade using the configuration tool (advanced)====
{{Warning|Make sure you have a stable connection to the internet and your SatNOGS client during this process. Release upgrades can consume a lot of time, data and storage.}}To upgrade from stretch to buster using the configuration tool:

#SSH into the system
#Make sure you have enough free space on your SD card (>2GiB) by running <code>df -h /</code> on the console
#Run <code>sudo satnogs-setup</code> to bring up the configuration menu
#Select <code>Update</code> to update the configuration tool and all distribution packages to the latest; this will also prompt you for a distribution upgrade, if it detects that one is needed
#Keep an eye on the upgrade progress; <code>dpkg</code> may prompt for changes
#Once the upgrade is completed select <code>Reboot</code>
#After the reboot, SSH back into the system and make sure you are on the correct release by running <code>lsb_release -a</code>
#Re-run <code>sudo satnogs-setup</code> and select <code>Update</code> and then <code>Apply</code>; this may take some time
#Before exit, check at the top that you have the latest satnogs-client and gr-satnogs versions
#Select <code>Back</code> to exit

==Verification of correct installation==
To see if satnogs-client has started successfully, check the logs with journalctl:<pre>
$ journalctl -u satnogs-client.service
</pre>You should see entries running approximately once per minute that look like this:<pre>
Oct 01 23:02:13 raspberrypi satnogs-client[6695]: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
Oct 01 23:02:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:02:14,466 - satnogsclient - INFO - [LD] Downlink thread waiting for first downlink packet
Oct 01 23:03:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:14,450 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:03:14 UTC)" (scheduled at 2017-10-01 23:03:14.423393+00:00)
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,324 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,325 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,327 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,453 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.423393+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,484 - apscheduler.executors.default - INFO - Running job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.436367+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,489 - apscheduler.executors.default - INFO - Job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,627 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,628 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,629 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:05:14 UTC)" executed successfully
</pre>If you see that, great -- you're ready to [[Operation|schedule your first observation]]! If not, check out the [[Troubleshooting]] page.

==See also==

*[[SatNOGS Client Ansible]]

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

SatNOGS Ansible

2020-02-21T16:38:27Z

Jebba: /* Installation */ git checkout stable

==Introduction==

'''SatNOGS Client Ansible''' makes the actual provisioning of the '''SatNOGS Client''' system. It is called, under the hood, when applying the configuration using [[SatNOGS Client Setup|SatNOGS Client Setup utility]]. It currently supports Raspbian and Debian (stretch and buster).

==Raspbian==

For Raspberry Pi, which is the reference platform for SatNOGS, a [[Raspberry Pi|Raspbian image]] with '''SatNOGS Client Ansible''' pre-installed is available.

==Debian==

{{Warning|Follow these instructions only if you are provisioning SatNOGS to Debian from another host or are installing on the same host. If you are using [[Raspberry_Pi|SatNOGS Raspbian]] image, follow [[SatNOGS_Client_Setup|SatNOGS Client Setup]] to set up your system. }}These sections contain generic instructions for installing SatNOGS Client on a Debian system.

===Prerequisites===

*A target Debian system. To install Debian please follow the [https://www.debian.org/releases/stretch/installmanual Debian Installation Guide] and chose the net installer if you want to run a headless server. The target system can be the host itself.
*A user (referenced later as ''youruser'') which is member of 'sudo' group exists on the target system.
*An SSH server running on the target system.
*A host system with Git and latest version of Ansible installed. To install Ansible on Debian, follow the [https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#latest-releases-via-apt-debian Ansible Installation Guide].

===Installation===

On the host system run the following commands:
$ git clone <nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible.git</nowiki> # Clone SatNOGS Client Ansible repository
$ cd satnogs-client-ansible # Change to cloned repository directory
$ git checkout stable # Optionally, check out stable (Debian Buster 10) branch
$ cp -r production.dist production # Copy dist configuration
$ vi production/inventory/hosts # Update file with your own target host e.g. 127.0.0.1, user and SSH password
$ ssh youruser@yourtargetsystem true # Test SSH connection to target system
$ ansible-playbook -i production/inventory -K site.yml # Run Ansible playbook
$ ssh -t youruser@yourtargetsystem sudo satnogs-setup # Setup SatNOGS client (see below)

 

== See also ==
* [[SatNOGS Client Setup]]

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

Talk:Observations

2020-02-18T19:12:01Z

Jebba: HOWTO Get List/Count of Modes

Observations

2020-02-18T19:08:49Z

Jebba: current modes list, five new modes

== Introduction ==
Satellites use a variety of transmitters, frequencies, and modes (encodings). Similar equipment will produce similar observations. Satellites can have, and often do have, multiple transmitters and modes. Below are various categories of observations.

== Transmitters ==
The SatNOGS DB API can generate the [https://db.satnogs.org/api/transmitters/ current list of transmitters].

== Modes ==
The SatNOGS DB API can generate the [https://db.satnogs.org/api/modes/ current list of modes].

At the time of writing, there are 70 modes, listed below:



<div style="column-count:6;-moz-column-count:6;-webkit-column-count:6">
* [[AFSK1k2]]
* [[AFSK9k6]]
* [[AFSK_SALSA]]
* [[AFSK_S-Net]]
* [[AFSK]]
* [[AHRPT]]
* [[AM]]
* [[APT]]
* [[BPSK1k2]]
* [[BPSK2k4]]
* [[BPSK4k8]]
* [[BPSK9k6]]
* [[BPSK12k5]]
* [[BPSK14k4]]
* [[BPSK115k2]]
* [[BPSK400]]
* [[BPSK]]
* [[CERTO]]
* [[CW]]
* [[DQPSK]]
* [[DSTAR]]
* [[DUV]]
* [[FFSK1k2]]
* [[FFSK]]
* [[FMN]]
* [[FM]]
* [[FSK1k2]]
* [[FSK2k4]]
* [[FSK4k8]]
* [[FSK9k6]]
* [[FSK19k2]]
* [[FSK40k]]
* [[FSK]]
* [[GFSK1k2]]
* [[GFSK2k4]]
* [[GFSK4k8]]
* [[GFSK9k6]]
* [[GFSK19k2]]
* [[GFSK_Rktr]]
* [[GFSK]]
* [[GMSK1k2]]
* [[GMSK2k4]]
* [[GMSK4k8]]
* [[GMSK9k6]]
* [[GMSK19k2]]
* [[GMSK]]
* [[HRPT]]
* [[LRPT]]
* [[LSB]]
* [[MFSK]]
* [[MSK1k2]]
* [[MSK2k4]]
* [[MSK4k8]]
* [[MSK9k6]]
* [[MSK19k2]]
* [[MSK38k4]]
* [[MSK]]
* [[OFDM]]
* [[OQPSK]]
* [[PSK4k8]]
* [[PSK31]]
* [[PSK63]]
* [[PSK]]
* [[QPSK31]]
* [[QPSK38k4]]
* [[QPSK63]]
* [[QPSK]]
* [[SSTV]]
* [[USB]]
* [[WSJT]]
</div>

=== Example Waterfalls ===
Below are waterfalls depicting various modes.

<gallery mode="packed" widths=310px heights=400px>
File:Waterfall_1439401_2019-12-26T17-19-27.png|[[AFSK1k2]]
File:Waterfall_1522395_2020-01-11T00-21-25.png|[[BPSK400]]
File:Waterfall_1521561_2020-01-10T20-57-09.png|[[BPSK1k2]]
File:Waterfall_1521031_2020-01-10T17-49-23.png|[[BPSK1k2]]
File:Waterfall 1521001 2020-01-10T17-13-53.png|[[BPSK1k2]]
File:Waterfall 1521004 2020-01-10T17-34-10.png|[[BPSK1k2]]
File:Waterfall 1521077 2020-01-10T18-07-02.png|[[BPSK12k5]]
File:Waterfall_1509702_2020-01-08T08-28-22.png|[[CERTO]]
File:Waterfall_1523025_2020-01-11T03-34-59.png|[[CW]]
File:Waterfall_1522483_2020-01-11T00-53-53.png|[[CW]]
File:Waterfall 1521149 2020-01-10T19-06-44.png|[[DUV]]
File:Waterfall_1521555_2020-01-10T20-20-54.png|[[FM]]
File:Waterfall 1524296 2020-01-11T10-01-27.png|[[FM]]
File:Waterfall_1521311_2020-01-10T19-19-45.png|[[FM]]
File:Waterfall 1521115 2020-01-10T18-42-03.png|[[FSK9k6]]
File:Waterfall 1521309 2020-01-10T19-06-56.png|[[FSK9k6]]
File:Waterfall 1524914 2020-01-11T14-27-01.png|[[FSK19k2]]
File:Waterfall_1290522_2019-11-30T17-45-27.png|[[GFSK Rktr]]
File:Waterfall_1232286_2019-11-21T16-57-56.png|[[GFSK9k6]]
File:Waterfall_1522671_2020-01-11T01-06-44.png|[[GFSK19k2]]
File:Waterfall 1524946 2020-01-11T14-57-12.png|[[GMSK]]
File:Waterfall_1493960_2020-01-05T04-44-29.png|[[GMSK1k2]]
File:Waterfall_1505060_2020-01-07T10-17-10.png|[[GMSK1k2]]
File:Waterfall_1521477_2020-01-10T19-31-32.png|[[GMSK2k4]]
File:Waterfall 1521029 2020-01-10T17-38-40.png|[[GMSK4k8]]
File:Waterfall 1521032 2020-01-10T17-55-29.png|[[GMSK4k8]]
File:Waterfall 1521108 2020-01-10T18-22-34.png|[[GMSK9k6]]
File:Waterfall_1531688_2020-01-13T10-08-44.png|[[LRPT]]
File:Waterfall_1520385_2020-01-10T13-55-32.png|[[MSK1k2]]
File:Waterfall_1295041_2019-12-01T10-41-10.png|[[PSK31]]
File:Waterfall_1456893_2019-12-30T10-35-46.png|[[SSTV]]
File:Waterfall_1538438_2020-01-14T11-41-28.png|[[USB]]
File:Waterfall_1475593_2020-01-01T23-14-41.png|[[USB]]
</gallery>

== See also ==

* [[Observe]]
* [[Operation]]
* [[Decode Telemetry and Packets]]
* [[:Category:RF_Modes]]
* [https://en.wikipedia.org/wiki/List_of_amateur_radio_modes List of amateur radio modes].
* [https://db.satnogs.org/stats/ SatNOGS DB stats on transmitters, modes, and bands].
* [[Adding a new data decoder]] to SatNOGS.

Note, for some modes there are a variety of baud rates and other factors that make it so two identical modes might not necessarily look similar. For further comments on the variety of modes, see:

* https://destevez.net/2020/01/extracting-ax-25-satellites-from-satnogs-db/
* https://github.com/daniestevez/jupyter_notebooks/blob/master/SatNOGS%20transmitters.ipynb

[[Category:Operate]]
[[Category:RF Modes]]

Observe

2020-02-09T17:58:29Z

Jebba: categorize good/bad possible observations.

== Introduction ==

Below are examples of SatNOGS observations that can be used to help rating new observations as "Good", "Bad", or "Failed".

Click right and left arrows at top of image to view next image.

== Good Observations ==

These waterfalls are good observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1509702_2020-01-08T08-28-22.png|Observation 1509702
File:Waterfall_1456893_2019-12-30T10-35-46.png|Observation 1456893
File:Waterfall_1538438_2020-01-14T11-41-28.png|Observation 1538438
File:Waterfall_1475593_2020-01-01T23-14-41.png|Observation 1475593
File:Waterfall_1520385_2020-01-10T13-55-32.png|Observation 1520385
File:Waterfall_1531688_2020-01-13T10-08-44.png|Observation 1531688
File:Waterfall_1295041_2019-12-01T10-41-10.png|Observation 1295041
File:Waterfall_1521477_2020-01-10T19-31-32.png|Observation 1521477
File:Waterfall_1493960_2020-01-05T04-44-29.png|Observation 1493960
File:Waterfall_1505060_2020-01-07T10-17-10.png|Observation 1505060
File:Waterfall_1522671_2020-01-11T01-06-44.png|Observation 1522671
File:Waterfall_1232286_2019-11-21T16-57-56.png|Observation 1232286
File:Waterfall_1290522_2019-11-30T17-45-27.png|Observation 1290522
File:Waterfall_1522940_2020-01-11T02-48-24.png|Observation 1522940
File:Waterfall_1523025_2020-01-11T03-34-59.png|Observation 1523025
File:Waterfall_1522483_2020-01-11T00-53-53.png|Observation 1522483
File:Waterfall_1521561_2020-01-10T20-57-09.png|Observation 1521561
File:Waterfall_1522395_2020-01-11T00-21-25.png|Observation 1522395
File:Waterfall_1439401_2019-12-26T17-19-27.png|Observation 1439401
File:Waterfall_1521555_2020-01-10T20-20-54.png|Observation 1521555
File:Waterfall_1521311_2020-01-10T19-19-45.png|Observation 1521311
File:Waterfall_1521149_2020-01-10T19-06-44.png|Observation 1521149
File:Waterfall_1520938_2020-01-10T16-58-00.png|Observation 1520938
File:Waterfall_1521001_2020-01-10T17-13-53.png|Observation 1521001
File:Waterfall_1521004_2020-01-10T17-34-10.png|Observation 1521004
File:Waterfall_1521029_2020-01-10T17-38-40.png|Observation 1521029
File:Waterfall_1521031_2020-01-10T17-49-23.png|Observation 1521031
File:Waterfall_1521032_2020-01-10T17-55-29.png|Observation 1521032
File:Waterfall_1521077_2020-01-10T18-07-02.png|Observation 1521077
File:Waterfall_1521107_2020-01-10T18-17-01.png|Observation 1521107
File:Waterfall_1521108_2020-01-10T18-22-34.png|Observation 1521108
File:Waterfall_1521115_2020-01-10T18-42-03.png|Observation 1521115
File:Waterfall_1521309_2020-01-10T19-06-56.png|Observation 1521309
File:Waterfall_1524946_2020-01-11T14-57-12.png|Observation 1524946
File:Waterfall_1524914_2020-01-11T14-27-01.png|Observation 1524914
File:Waterfall_1524296_2020-01-11T10-01-27.png|Observation 1524296
File:Waterfall_1525024_2020-01-11T15-28-52.png|Observation 1525024
File:Waterfall_1524945_2020-01-11T14-37-30.png|Observation 1524945
File:Waterfall_1524776_2020-01-11T13-35-22.png|Observation 1524776
File:Waterfall_1524775_2020-01-11T13-25-20.png|Observation 1524775
File:Waterfall_1524577_2020-01-11T12-23-50.png|Observation 1524577
File:Waterfall_1524438_2020-01-11T10-34-55.png|Observation 1524438
File:Waterfall_1524358_2020-01-11T10-24-33.png|Observation 1524358
File:Waterfall_1524071_2020-01-11T09-27-29.png|Observation 1524071
File:Waterfall_1524066_2020-01-11T08-59-57.png|Observation 1524066
File:Waterfall_1525136_2020-01-11T15-58-19.png|Observation 1525136, with noise

</gallery>

== Bad Observations ==

These waterfalls show bad observations.

<gallery mode="slideshow" showthumbnails>
File:waterfall_1520894_2020-01-10T16-39-45.png|Observation 1520894
File:Waterfall_1484539_2020-01-03T13-22-00.png|Signal is interference from terrestrial APRS station.
File:Waterfall_1520897_2020-01-10T16-54-13.png|Observation 1520897
File:Waterfall_1521028_2020-01-10T17-33-03.png|Observation 1521028
File:Waterfall_1521105_2020-01-10T18-00-39.png|Observation 1521105
File:Waterfall_1524511_2020-01-11T11-10-24.png|Observation 1524511
File:Waterfall_1524165_2020-01-11T09-50-17.png|Observation 1524165
File:Waterfall_1524092_2020-01-11T09-38-26.png|Observation 1524092
File:Waterfall_1523930_2020-01-11T08-12-36.png|Observation 1523930
File:Waterfall_1523768_2020-01-11T07-42-00.png|Observation 1523768
File:Waterfall_1523488_2020-01-11T06-41-14.png|Observation 1523488
File:Waterfall_1524535_2020-01-11T11-13-50.png|Observation 1524535
File:Waterfall_1525047_2020-01-11T15-32-14.png|Observation 1525047
File:Waterfall_1524932_2020-01-11T14-12-57.png|Observation 1524932
File:Waterfall_1524740_2020-01-11T13-23-43.png|Observation 1524740
File:Waterfall_1524578_2020-01-11T12-31-46.png|Observation 1524578
File:Waterfall_1524579_2020-01-11T12-28-56.png|Observation 1524579
File:Waterfall_1524573_2020-01-11T12-02-50.png|Observation 1524573
File:Waterfall_1524510_2020-01-11T10-49-25.png|Observation 1524510
File:Waterfall_1524299_2020-01-11T10-21-03.png|Observation 1524299
File:Waterfall_1524166_2020-01-11T10-06-33.png|Observation 1524166
File:Waterfall_1524119_2020-01-11T09-47-27.png|Observation 1524119
File:Waterfall_1524091_2020-01-11T09-27-29.png|Observation 1524091
File:Waterfall_1524019_2020-01-11T08-25-42.png|Observation 1524019
File:Waterfall_1523690_2020-01-11T07-08-44.png|Observation 1523690
File:Waterfall_1523562_2020-01-11T07-10-27.png|Observation 1523562
</gallery>

== Failed Observations ==

These waterfalls show failed observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1365407_2019-12-13T02-15-35.png|SatNOGS Client uploaded an image, but it is a solid color.
</gallery>

== See also ==
* [[Operation]].
* [[Observations]].
* [[Intro|Introduction]] to SatNOGS.

[[Category:Operate]]

Observe

2020-02-09T17:45:42Z

Jebba: re-categorize good/bad unknowns

== Introduction ==

Below are examples of SatNOGS observations that can be used to help rating new observations as "Good", "Bad", or "Failed".

Click right and left arrows at top of image to view next image.

== Good Observations ==

These waterfalls are good observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1509702_2020-01-08T08-28-22.png|Observation 1509702
File:Waterfall_1456893_2019-12-30T10-35-46.png|Observation 1456893
File:Waterfall_1538438_2020-01-14T11-41-28.png|Observation 1538438
File:Waterfall_1475593_2020-01-01T23-14-41.png|Observation 1475593
File:Waterfall_1520385_2020-01-10T13-55-32.png|Observation 1520385
File:Waterfall_1531688_2020-01-13T10-08-44.png|Observation 1531688
File:Waterfall_1295041_2019-12-01T10-41-10.png|Observation 1295041
File:Waterfall_1521477_2020-01-10T19-31-32.png|Observation 1521477
File:Waterfall_1493960_2020-01-05T04-44-29.png|Observation 1493960
File:Waterfall_1505060_2020-01-07T10-17-10.png|Observation 1505060
File:Waterfall_1522671_2020-01-11T01-06-44.png|Observation 1522671
File:Waterfall_1232286_2019-11-21T16-57-56.png|Observation 1232286
File:Waterfall_1290522_2019-11-30T17-45-27.png|Observation 1290522
File:Waterfall_1522940_2020-01-11T02-48-24.png|Observation 1522940
File:Waterfall_1523025_2020-01-11T03-34-59.png|Observation 1523025
File:Waterfall_1522483_2020-01-11T00-53-53.png|Observation 1522483
File:Waterfall_1521561_2020-01-10T20-57-09.png|Observation 1521561
File:Waterfall_1522395_2020-01-11T00-21-25.png|Observation 1522395
File:Waterfall_1439401_2019-12-26T17-19-27.png|Observation 1439401
File:Waterfall_1521555_2020-01-10T20-20-54.png|Observation 1521555
File:Waterfall_1521311_2020-01-10T19-19-45.png|Observation 1521311
File:Waterfall_1521149_2020-01-10T19-06-44.png|Observation 1521149
File:Waterfall_1520938_2020-01-10T16-58-00.png|Observation 1520938
File:Waterfall_1521001_2020-01-10T17-13-53.png|Observation 1521001
File:Waterfall_1521004_2020-01-10T17-34-10.png|Observation 1521004
File:Waterfall_1521029_2020-01-10T17-38-40.png|Observation 1521029
File:Waterfall_1521031_2020-01-10T17-49-23.png|Observation 1521031
File:Waterfall_1521032_2020-01-10T17-55-29.png|Observation 1521032
File:Waterfall_1521077_2020-01-10T18-07-02.png|Observation 1521077
File:Waterfall_1521107_2020-01-10T18-17-01.png|Observation 1521107
File:Waterfall_1521108_2020-01-10T18-22-34.png|Observation 1521108
File:Waterfall_1521115_2020-01-10T18-42-03.png|Observation 1521115
File:Waterfall_1521309_2020-01-10T19-06-56.png|Observation 1521309
File:Waterfall_1524946_2020-01-11T14-57-12.png|Observation 1524946
File:Waterfall_1524914_2020-01-11T14-27-01.png|Observation 1524914
File:Waterfall_1524296_2020-01-11T10-01-27.png|Observation 1524296
File:Waterfall_1525024_2020-01-11T15-28-52.png|Observation 1525024
File:Waterfall_1524945_2020-01-11T14-37-30.png|Observation 1524945
File:Waterfall_1524776_2020-01-11T13-35-22.png|Observation 1524776
File:Waterfall_1524775_2020-01-11T13-25-20.png|Observation 1524775
File:Waterfall_1524577_2020-01-11T12-23-50.png|Observation 1524577
File:Waterfall_1524438_2020-01-11T10-34-55.png|Observation 1524438
File:Waterfall_1524358_2020-01-11T10-24-33.png|Observation 1524358
File:Waterfall_1524071_2020-01-11T09-27-29.png|Observation 1524071
File:Waterfall_1524066_2020-01-11T08-59-57.png|Observation 1524066
</gallery>

== Bad Observations ==

These waterfalls show bad observations.

<gallery mode="slideshow" showthumbnails>
File:waterfall_1520894_2020-01-10T16-39-45.png|Observation 1520894
File:Waterfall_1484539_2020-01-03T13-22-00.png|Signal is interference from terrestrial APRS station.
File:Waterfall_1520897_2020-01-10T16-54-13.png|Observation 1520897
File:Waterfall_1521028_2020-01-10T17-33-03.png|Observation 1521028
File:Waterfall_1521105_2020-01-10T18-00-39.png|Observation 1521105
File:Waterfall_1524511_2020-01-11T11-10-24.png|Observation 1524511
File:Waterfall_1524165_2020-01-11T09-50-17.png|Observation 1524165
File:Waterfall_1524092_2020-01-11T09-38-26.png|Observation 1524092
File:Waterfall_1523930_2020-01-11T08-12-36.png|Observation 1523930
File:Waterfall_1523768_2020-01-11T07-42-00.png|Observation 1523768
File:Waterfall_1523488_2020-01-11T06-41-14.png|Observation 1523488
</gallery>

== Failed Observations ==

These waterfalls show failed observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1365407_2019-12-13T02-15-35.png|SatNOGS Client uploaded an image, but it is a solid color.
</gallery>

== Observations to Confirm ==
The below observations are corner cases or more difficult to discern than the above examples. As the below examples are confirmed by more experienced members of the community, they can be moved to their appropriate classification above.

=== Possibly Bad Observations ===
The below observations are potentially "bad" observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1524535_2020-01-11T11-13-50.png|Observation 1524535
File:Waterfall_1525047_2020-01-11T15-32-14.png|Observation 1525047
File:Waterfall_1524932_2020-01-11T14-12-57.png|Observation 1524932
File:Waterfall_1524740_2020-01-11T13-23-43.png|Observation 1524740
File:Waterfall_1524578_2020-01-11T12-31-46.png|Observation 1524578
File:Waterfall_1524579_2020-01-11T12-28-56.png|Observation 1524579
File:Waterfall_1524573_2020-01-11T12-02-50.png|Observation 1524573
File:Waterfall_1524510_2020-01-11T10-49-25.png|Observation 1524510
File:Waterfall_1524299_2020-01-11T10-21-03.png|Observation 1524299
File:Waterfall_1524166_2020-01-11T10-06-33.png|Observation 1524166
File:Waterfall_1524119_2020-01-11T09-47-27.png|Observation 1524119
File:Waterfall_1524091_2020-01-11T09-27-29.png|Observation 1524091
File:Waterfall_1524019_2020-01-11T08-25-42.png|Observation 1524019
File:Waterfall_1523690_2020-01-11T07-08-44.png|Observation 1523690
File:Waterfall_1523562_2020-01-11T07-10-27.png|Observation 1523562
</gallery>

=== Possibly Failed Observations ===
The below observations are potentially "failed" observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1525136_2020-01-11T15-58-19.png|Observation 1525136
</gallery>

== See also ==
* [[Operation]].
* [[Observations]].
* [[Intro|Introduction]] to SatNOGS.

[[Category:Operate]]

Satellite Mission Guide

2020-02-04T20:23:14Z

Jebba: /* See also */ * Satellite operator manual

{{Warning|WIP - Work in Progress}}

This page intents to provide information for Satellite Missions (under development, or operational) on why and how to join SatNOGS.

===Reasons to Join===

You have recently discovered SatNOGS and you are involved in a mission. Here are the top 10 reasons why your mission should join SatNOGS:

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

===Add a new Mission===

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

#SatNOGS DB
#*Suggest to add your satellite to satnogs-db by creating an issue in [https://gitlab.com/librespacefoundation/satnogs-ops/issues satnogs-ops] providing the following information:
#** Name
#** NORAD catalog number (if already assigned)
#** Amateur Radio call sign (if Amateur service)
#** Description
#** Project Website
#** Image of the satellite
#*Once the new satellite was added to satnogs-db by one of the satnogs-ops team members, find your satellite in [https://db.satnogs.org/ db.satnogs.org] and add a transmitter suggestion for each transmitter of your satellite
#GR SatNOGS
#*Choose one of the existing flowgraphs in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs] or provide a new one
#SatNOGS Client
#*If you added a new flowgraph under the previous point, make sure to add support for it in [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client]
#*Wait for the next release of [https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible/ satnogs-client-ansible], then let the station owners know that your satellite is supported now and ask them to update their stations.
#SatNOGS Decoders
#*Add a decoder written in [https://kaitai.io/ Kaitai] to [https://gitlab.com/librespacefoundation/satnogs/satnogs-decoders satnogs-decoders]

We kindly ask you to also provide a station to increase the network (maybe you can spare some time of your existing ground station to SatNOGS).

== See also ==
* [[SatNOGS DB]]
* [[SatNOGS Network]]
* [[Satellite operator manual]]

[[Category:Satellite]]

Satellite Mission Guide

2020-02-04T20:21:46Z

Jebba: Category:Satellite * See also

User:Jebba

2020-01-26T02:18:37Z

Jebba: username fixed!

I'm Jeff Moe.

Ground stations:

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

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

Troubleshooting Legacy

2020-01-21T18:57:53Z

Jebba: usb reset

==Client troubleshooting==

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

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

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

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

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

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

 

===Some uploads missing & Doppler-correction not working properly===
The station/client might have a clock offset. This causes a Doppler shift on the waterfall and some observations don't start because of a conflict between the time on the PC of the station and the time of the SatNOGS Network.

=== Uploads (waterfall or audio) are missing for a past observation ===
When using <code>satnogs-setup</code> for editing/updating the configuration of the station, the satnogs-client gets restarted. When this happens during an observation the observation will be aborted and no waterfall/audio/data files will be uploaded. Such observations should be voted as ''failed''.

The partial data from such observations is stored in <code>/tmp/.satnogs/data/</code>, look for files like <code>receiving_{satnogs|waterfall}_123456_2019-01-01T12-23-42.{out|dat}</code>. They can be manually removed.

==Signal troubleshooting==

===Blank or solid purple waterfall?===
At the first sign of trouble, put your station into testing mode. This way bad waterfalls do not get uploaded to the database.

*Make sure the RTLSDR gain is set correctly. If set too high, a blank waterfall can result. If set to low, same. Test a value between 7 and 15. Check your gain value is valid. Wrong values can result in blank waterfalls. For for example '7.7.' will result in errors (and a blank waterfall - there is an extra '.' at the end). <code>journalctl -u satnogs-client.service</code> It might be a big file, but work through it and look for errors. <code>df -h</code> Ensure there is sufficient hard drive space. If temp files can not be created, the waterfall might be blank. Run <code>rtl_test</code> for about 30 seconds and make sure you can connect with the dongle and that there are no errors.

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

=== USB ===
You can reset USB without having to reboot the system by running these commands:

echo “usb1” > /sys/bus/usb/drivers/usb/unbind
echo “usb1” > /sys/bus/usb/drivers/usb/bind

This can be placed in the satnogs_post_observation_script for automation.

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

*Twist each pair or the motor wire
*Add proper grounding
*Add capacitor to the DC input of drivers
*wrap the motors wire with adhesite aluminum and then connect it to GND on driver side
*add ferites to motors wires

[[File:Rf noise.png|alt=RF Noise|left|thumb|400x400px|Too much RF Noise]]

[[Category:Operate]]
[[Category:Hardware]]
[[Category:Software]]

Satellite Catalog Number

2020-01-20T23:19:09Z

Jebba: /* Introduction */ , split

== Introduction ==
The Satellite Catalog Number is a sequential five-digit number assigned by USSTRATCOM (United States Strategic Command) in order of discovery to all man-made objects in Earth orbit.
It includes rocket bodies, debris, and space probes launched from Earth.
It is also known as NORAD (North American Aerospace Defense) Catalog Number, NORAD ID, NASA catalog number, USSPACECOM object number or simply catalog number and similar variants.

== See also ==
* [[SatNOGS DB]]
* [[SatNOGS Network]]
* [https://en.wikipedia.org/wiki/Satellite_Catalog_Number Wikipedia Satellite Catalog Number]

[[Category:Satellite]]

Satellite Catalog Number

2020-01-20T23:16:36Z

Jebba: /* See also */ * SatNOGS DB * SatNOGS Network

== Introduction ==
The Satellite Catalog Number (also known as NORAD (North American Aerospace Defense) Catalog Number, NORAD ID, NASA catalog number, USSPACECOM object number or simply catalog number and similar variants) is a sequential five-digit number assigned by USSTRATCOM (United States Strategic Command) in order of discovery to all man-made objects in Earth orbit (including rocket bodies and debris) and space probes launched from Earth.

== See also ==
* [[SatNOGS DB]]
* [[SatNOGS Network]]
* [https://en.wikipedia.org/wiki/Satellite_Catalog_Number Wikipedia Satellite Catalog Number]

[[Category:Satellite]]

SatNOGS Network

2020-01-20T23:11:51Z

Jebba: Librespace1 moved page Network to SatNOGS Network: Actually, full name is better for main websites...

== Introduction ==

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]

[[File:Satnogs-network-cap.png|800px|SatNOGS Network Screen capture]]

==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#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 Network needs reliable ground stations that perform within the constraints that would be expected. A ground station should perform in a way that is comparable to its peers and in line with the constraints of the geography, antenna type, location and the other aspects which will make a ground station different to another.

Once you feel that your station has been performing well for a period of time under the "Testing" flag then remove the flag. Select the ground station press edit and remove the testing flag under settings. Then announce the availability of a new station in our community channels!

The ground station should also be reliable. This does not mean that it should be available 24 hours a day, 7 days a week. Downtime is expected, it should however, not be unduly off line or unreliable.

==What's next?==

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

==Development==

The SatNOGS Network application is a project by itself with constant development. We test the Network application in our [[Development Environment|development environment]], and [[Software contribution|always welcome python/javascript developers to help us]]!

[[Category:Infrastructure]]
[[Category:Hardware]]
[[Category:Software]]
[[Category:Build]]
[[Category:Operate]]
[[Category:Develop]]

Network

2020-01-20T23:11:51Z

Jebba: Librespace1 moved page Network to SatNOGS Network: Actually, full name is better for main websites...

#REDIRECT [[SatNOGS Network]]

SatNOGS DB

2020-01-20T23:11:22Z

Jebba: Librespace1 moved page DB to SatNOGS DB: Actually, full name is better for main websites...

__NOTOC__

== Introduction ==

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

[[File:Satnogs-db-cap.png|800px|SatNOGS DB Screen capture]]

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

==Contribute==

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

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

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

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

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

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

#Log in to db.satnogs.org
#Navigate to https://db.satnogs.org/admin (if you are seeing a login screen, you are either not logged in to db.satnogs.org, or don't have moderator permissions)
#Click on Base::Suggestions
#Click on the suggestion you want to review and carefully check the data, especially the citation URL
#When you are ready to approve or reject 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....

==Documentation & Installation==

You can find documentation and installation instructions about the project in our [https://docs.satnogs.org/projects/satnogs-db/en/stable/ Read the Docs instance].

[[Category:Infrastructure]]
[[Category:Operate]]
[[Category:Satellite]]
[[Category:RF Modes]]

DB

2020-01-20T23:11:22Z

Jebba: Librespace1 moved page DB to SatNOGS DB: Actually, full name is better for main websites...

#REDIRECT [[SatNOGS DB]]

Software

2020-01-20T23:07:08Z

Jebba: /* Unofficial SatNOGS Software */ moar

== Introduction ==
There is a variety of free software (open source) you can use with SatNOGS. The Libre Space Foundation maintains the official SatNOGS software. There are many groups and individuals that also write software that can be used with the SatNOGS system.

== Official SatNOGS Software ==
The main software archive is available here:

* [https://gitlab.com/librespacefoundation All Libre Space Foundation software at GitLab]
* [https://gitlab.com/librespacefoundation/satnogs SatNOGS]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-auto-scheduler SatNOGS Auto-scheduler]
* [https://gitlab.com/librespacefoundation/satnogs/satnogs-client SatNOGS Client]
* [[Telemetry Dashboards]] at [https://dashboard.satnogs.org/ SatNOGS Dashboards]

...and much more is available in the repos.

== More SatNOGS Software ==
Below is a list of free software that works with SatNOGS, but is not maintained by the project.

* [https://github.com/deckbsd/glouton-satnogs-data-downloader glouton-satnogs-data-downloader] --- This cli app is a downloader for the data provided by the satnogs network and the satnogs db APIs.

* [http://gpredict.oz9aec.net/ Gpredict] --- Satellite tracking program.

* [https://github.com/wose/satnogs-monitor SatNOGS Monitor] --- Terminal UI monitor for your SatNOGS ground station. [[SatNOGS Monitor]] page in this wiki.

* [https://gitlab.com/chibill/satnogsmap/ SatNOGS Map] --- Displays SatNOGS ground stations on a map with live updates of passing satellites' observations.

* [https://gitlab.com/chibill/satnogsglobalnetworkmonitor SatNOGS Global Network Monitor]

<gallery mode="packed" widths=310px heights=200px>
File:Satnogs-monitor.png|[[SatNOGS Monitor]]
File:Satnogsmap.png|[https://gitlab.com/chibill/satnogsmap/ SatNOGS Map]
</gallery>

== See also ==
* [[Software contribution]]
* [[SatNOGS Client Development]]
* [[Audio Editing Tools]]
* [[Decode Telemetry and Packets]]

[[Category:Software]]

Decode Telemetry and Packets

2020-01-20T23:05:44Z

Jebba: * Software

== Introduction ==

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

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

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

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

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

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

SoX supports demodulating the following modes:

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

===References===

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

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

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

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

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

===References===

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

==multimon-ng==

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

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

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

===How to AFSK===

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

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

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

===References===

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

==Direwolf==

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

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

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

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

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

===Usage===

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

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

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

 

==WXtoImg==

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

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

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

===Usage===

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

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

*Then invoke command line interface of WXtoIMG with:

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

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

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

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

__NOEDITSECTION__

NORADID

2020-01-20T23:03:20Z

Jebba: #REDIRECT Satellite Catalog Number

#REDIRECT [[Satellite Catalog Number]]

NORAD

2020-01-20T23:03:07Z

Jebba: #REDIRECT Satellite Catalog Number

#REDIRECT [[Satellite Catalog Number]]

NORAD ID

2020-01-20T23:02:47Z

Jebba: #REDIRECT Satellite Catalog Number

#REDIRECT [[Satellite Catalog Number]]

Satellite Catalog Number

2020-01-20T23:02:28Z

Jebba: Satellite Catalog Number stub

== Introduction ==
The Satellite Catalog Number (also known as NORAD (North American Aerospace Defense) Catalog Number, NORAD ID, NASA catalog number, USSPACECOM object number or simply catalog number and similar variants) is a sequential five-digit number assigned by USSTRATCOM (United States Strategic Command) in order of discovery to all man-made objects in Earth orbit (including rocket bodies and debris) and space probes launched from Earth.

== See also ==
* [https://en.wikipedia.org/wiki/Satellite_Catalog_Number Wikipedia Satellite Catalog Number]

[[Category:Satellite]]

Observe

2020-01-20T22:49:42Z

Jebba: /* Rating Observations */ Introduction

== Introduction ==

Below are examples of SatNOGS observations that can be used to help rating new observations as "Good", "Bad", or "Failed".

Click right and left arrows at top of image to view next image.

== Good Observations ==

These waterfalls are good observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1509702_2020-01-08T08-28-22.png|Observation 1509702
File:Waterfall_1456893_2019-12-30T10-35-46.png|Observation 1456893
File:Waterfall_1538438_2020-01-14T11-41-28.png|Observation 1538438
File:Waterfall_1475593_2020-01-01T23-14-41.png|Observation 1475593
File:Waterfall_1520385_2020-01-10T13-55-32.png|Observation 1520385
File:Waterfall_1531688_2020-01-13T10-08-44.png|Observation 1531688
File:Waterfall_1295041_2019-12-01T10-41-10.png|Observation 1295041
File:Waterfall_1521477_2020-01-10T19-31-32.png|Observation 1521477
File:Waterfall_1493960_2020-01-05T04-44-29.png|Observation 1493960
File:Waterfall_1505060_2020-01-07T10-17-10.png|Observation 1505060
File:Waterfall_1522671_2020-01-11T01-06-44.png|Observation 1522671
File:Waterfall_1232286_2019-11-21T16-57-56.png|Observation 1232286
File:Waterfall_1290522_2019-11-30T17-45-27.png|Observation 1290522
File:Waterfall_1522940_2020-01-11T02-48-24.png|Observation 1522940
File:Waterfall_1523025_2020-01-11T03-34-59.png|Observation 1523025
File:Waterfall_1522483_2020-01-11T00-53-53.png|Observation 1522483
File:Waterfall_1521561_2020-01-10T20-57-09.png|Observation 1521561
File:Waterfall_1522395_2020-01-11T00-21-25.png|Observation 1522395
File:Waterfall_1439401_2019-12-26T17-19-27.png|Observation 1439401
File:Waterfall_1521555_2020-01-10T20-20-54.png|Observation 1521555
File:Waterfall_1521311_2020-01-10T19-19-45.png|Observation 1521311
File:Waterfall_1521149_2020-01-10T19-06-44.png|Observation 1521149
File:Waterfall_1520938_2020-01-10T16-58-00.png|Observation 1520938
File:Waterfall_1521001_2020-01-10T17-13-53.png|Observation 1521001
File:Waterfall_1521004_2020-01-10T17-34-10.png|Observation 1521004
File:Waterfall_1521029_2020-01-10T17-38-40.png|Observation 1521029
File:Waterfall_1521031_2020-01-10T17-49-23.png|Observation 1521031
File:Waterfall_1521032_2020-01-10T17-55-29.png|Observation 1521032
File:Waterfall_1521077_2020-01-10T18-07-02.png|Observation 1521077
File:Waterfall_1521107_2020-01-10T18-17-01.png|Observation 1521107
File:Waterfall_1521108_2020-01-10T18-22-34.png|Observation 1521108
File:Waterfall_1521115_2020-01-10T18-42-03.png|Observation 1521115
File:Waterfall_1521309_2020-01-10T19-06-56.png|Observation 1521309
File:Waterfall_1524946_2020-01-11T14-57-12.png|Observation 1524946
File:Waterfall_1524914_2020-01-11T14-27-01.png|Observation 1524914
File:Waterfall_1524296_2020-01-11T10-01-27.png|Observation 1524296
</gallery>

== Bad Observations ==

These waterfalls show bad observations.

<gallery mode="slideshow" showthumbnails>
File:waterfall_1520894_2020-01-10T16-39-45.png|Observation 1520894
File:Waterfall_1484539_2020-01-03T13-22-00.png|Signal is interference from terrestrial APRS station.
File:Waterfall_1520897_2020-01-10T16-54-13.png|Observation 1520897
File:Waterfall_1521028_2020-01-10T17-33-03.png|Observation 1521028
File:Waterfall_1521105_2020-01-10T18-00-39.png|Observation 1521105
</gallery>

== Failed Observations ==

These waterfalls show failed observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1365407_2019-12-13T02-15-35.png|SatNOGS Client uploaded an image, but it is a solid color.
</gallery>

== Observations to Confirm ==
The below observations are corner cases or more difficult to discern than the above examples. As the below examples are confirmed by more experienced members of the community, they can be moved to their appropriate classification above.

=== Possibly Good Observations ===
The below observations are potentially "good" observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1525024_2020-01-11T15-28-52.png|Observation 1525024
File:Waterfall_1524945_2020-01-11T14-37-30.png|Observation 1524945
File:Waterfall_1524776_2020-01-11T13-35-22.png|Observation 1524776
File:Waterfall_1524775_2020-01-11T13-25-20.png|Observation 1524775
File:Waterfall_1524577_2020-01-11T12-23-50.png|Observation 1524577
File:Waterfall_1524511_2020-01-11T11-10-24.png|Observation 1524511
File:Waterfall_1524438_2020-01-11T10-34-55.png|Observation 1524438
File:Waterfall_1524358_2020-01-11T10-24-33.png|Observation 1524358
File:Waterfall_1524165_2020-01-11T09-50-17.png|Observation 1524165
File:Waterfall_1524092_2020-01-11T09-38-26.png|Observation 1524092
File:Waterfall_1524071_2020-01-11T09-27-29.png|Observation 1524071
File:Waterfall_1524066_2020-01-11T08-59-57.png|Observation 1524066
File:Waterfall_1523930_2020-01-11T08-12-36.png|Observation 1523930
File:Waterfall_1523768_2020-01-11T07-42-00.png|Observation 1523768
File:Waterfall_1523488_2020-01-11T06-41-14.png|Observation 1523488
</gallery>

=== Possibly Bad Observations ===
The below observations are potentially "bad" observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1524535_2020-01-11T11-13-50.png|Observation 1524535
File:Waterfall_1525047_2020-01-11T15-32-14.png|Observation 1525047
File:Waterfall_1524932_2020-01-11T14-12-57.png|Observation 1524932
File:Waterfall_1524740_2020-01-11T13-23-43.png|Observation 1524740
File:Waterfall_1524578_2020-01-11T12-31-46.png|Observation 1524578
File:Waterfall_1524579_2020-01-11T12-28-56.png|Observation 1524579
File:Waterfall_1524573_2020-01-11T12-02-50.png|Observation 1524573
File:Waterfall_1524510_2020-01-11T10-49-25.png|Observation 1524510
File:Waterfall_1524299_2020-01-11T10-21-03.png|Observation 1524299
File:Waterfall_1524166_2020-01-11T10-06-33.png|Observation 1524166
File:Waterfall_1524119_2020-01-11T09-47-27.png|Observation 1524119
File:Waterfall_1524091_2020-01-11T09-27-29.png|Observation 1524091
File:Waterfall_1524019_2020-01-11T08-25-42.png|Observation 1524019
File:Waterfall_1523690_2020-01-11T07-08-44.png|Observation 1523690
File:Waterfall_1523562_2020-01-11T07-10-27.png|Observation 1523562
</gallery>

=== Possibly Failed Observations ===
The below observations are potentially "failed" observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1525136_2020-01-11T15-58-19.png|Observation 1525136
</gallery>

== See also ==
* [[Operation]].
* [[Observations]].
* [[Intro|Introduction]] to SatNOGS.

[[Category:Operate]]

Observations

2020-01-20T22:48:26Z

Jebba: /* See also */ * Observe

== Introduction ==
Satellites use a variety of transmitters, frequencies, and modes (encodings). Similar equipment will produce similar observations. Satellites can have, and often do have, multiple transmitters and modes. Below are various categories of observations.

== Transmitters ==
The SatNOGS DB API can generate the [https://db.satnogs.org/api/transmitters/ current list of transmitters].

== Modes ==
The SatNOGS DB API can generate the [https://db.satnogs.org/api/modes/ current list of modes].

At the time of writing, there are 65 modes, listed below:



<div style="column-count:6;-moz-column-count:6;-webkit-column-count:6">
* [[AFSK1k2]]
* [[AFSK9k6]]
* [[AFSK]]
* [[AHRPT]]
* [[AM]]
* [[APT]]
* [[BPSK1k2]]
* [[BPSK2k4]]
* [[BPSK4k8]]
* [[BPSK9k6]]
* [[BPSK12k5]]
* [[BPSK14k4]]
* [[BPSK115k2]]
* [[BPSK400]]
* [[BPSK]]
* [[CERTO]]
* [[CW]]
* [[DQPSK]]
* [[DSTAR]]
* [[DUV]]
* [[FFSK1k2]]
* [[FMN]]
* [[FM]]
* [[FSK1k2]]
* [[FSK2k4]]
* [[FSK4k8]]
* [[FSK9k6]]
* [[FSK19k2]]
* [[FSK]]
* [[GFSK1k2]]
* [[GFSK2k4]]
* [[GFSK4k8]]
* [[GFSK9k6]]
* [[GFSK19k2]]
* [[GFSK_Rktr]]
* [[GFSK]]
* [[GMSK1k2]]
* [[GMSK2k4]]
* [[GMSK4k8]]
* [[GMSK9k6]]
* [[GMSK19k2]]
* [[GMSK]]
* [[HRPT]]
* [[LRPT]]
* [[LSB]]
* [[MFSK]]
* [[MSK1k2]]
* [[MSK2k4]]
* [[MSK4k8]]
* [[MSK9k6]]
* [[MSK19k2]]
* [[MSK38k4]]
* [[OFDM]]
* [[OQPSK]]
* [[PSK4k8]]
* [[PSK31]]
* [[PSK63]]
* [[PSK]]
* [[QPSK31]]
* [[QPSK38k4]]
* [[QPSK63]]
* [[QPSK]]
* [[SSTV]]
* [[USB]]
* [[WSJT]]
</div>

=== Example Waterfalls ===
Below are waterfalls depicting various modes.

<gallery mode="packed" widths=310px heights=400px>
File:Waterfall_1439401_2019-12-26T17-19-27.png|[[AFSK1k2]]
File:Waterfall_1522395_2020-01-11T00-21-25.png|[[BPSK400]]
File:Waterfall_1521561_2020-01-10T20-57-09.png|[[BPSK1k2]]
File:Waterfall_1521031_2020-01-10T17-49-23.png|[[BPSK1k2]]
File:Waterfall 1521001 2020-01-10T17-13-53.png|[[BPSK1k2]]
File:Waterfall 1521004 2020-01-10T17-34-10.png|[[BPSK1k2]]
File:Waterfall 1521077 2020-01-10T18-07-02.png|[[BPSK12k5]]
File:Waterfall_1509702_2020-01-08T08-28-22.png|[[CERTO]]
File:Waterfall_1523025_2020-01-11T03-34-59.png|[[CW]]
File:Waterfall_1522483_2020-01-11T00-53-53.png|[[CW]]
File:Waterfall 1521149 2020-01-10T19-06-44.png|[[DUV]]
File:Waterfall_1521555_2020-01-10T20-20-54.png|[[FM]]
File:Waterfall 1524296 2020-01-11T10-01-27.png|[[FM]]
File:Waterfall_1521311_2020-01-10T19-19-45.png|[[FM]]
File:Waterfall 1521115 2020-01-10T18-42-03.png|[[FSK9k6]]
File:Waterfall 1521309 2020-01-10T19-06-56.png|[[FSK9k6]]
File:Waterfall 1524914 2020-01-11T14-27-01.png|[[FSK19k2]]
File:Waterfall_1290522_2019-11-30T17-45-27.png|[[GFSK Rktr]]
File:Waterfall_1232286_2019-11-21T16-57-56.png|[[GFSK9k6]]
File:Waterfall_1522671_2020-01-11T01-06-44.png|[[GFSK19k2]]
File:Waterfall 1524946 2020-01-11T14-57-12.png|[[GMSK]]
File:Waterfall_1493960_2020-01-05T04-44-29.png|[[GMSK1k2]]
File:Waterfall_1505060_2020-01-07T10-17-10.png|[[GMSK1k2]]
File:Waterfall_1521477_2020-01-10T19-31-32.png|[[GMSK2k4]]
File:Waterfall 1521029 2020-01-10T17-38-40.png|[[GMSK4k8]]
File:Waterfall 1521032 2020-01-10T17-55-29.png|[[GMSK4k8]]
File:Waterfall 1521108 2020-01-10T18-22-34.png|[[GMSK9k6]]
File:Waterfall_1531688_2020-01-13T10-08-44.png|[[LRPT]]
File:Waterfall_1520385_2020-01-10T13-55-32.png|[[MSK1k2]]
File:Waterfall_1295041_2019-12-01T10-41-10.png|[[PSK31]]
File:Waterfall_1456893_2019-12-30T10-35-46.png|[[SSTV]]
File:Waterfall_1538438_2020-01-14T11-41-28.png|[[USB]]
File:Waterfall_1475593_2020-01-01T23-14-41.png|[[USB]]
</gallery>

== See also ==

* [[Observe]]
* [[Operation]]
* [[Decode Telemetry and Packets]]
* [[:Category:RF_Modes]]
* [https://en.wikipedia.org/wiki/List_of_amateur_radio_modes List of amateur radio modes].
* [https://db.satnogs.org/stats/ SatNOGS DB stats on transmitters, modes, and bands].
* [[Adding a new data decoder]] to SatNOGS.

Note, for some modes there are a variety of baud rates and other factors that make it so two identical modes might not necessarily look similar. For further comments on the variety of modes, see:

* https://destevez.net/2020/01/extracting-ax-25-satellites-from-satnogs-db/
* https://github.com/daniestevez/jupyter_notebooks/blob/master/SatNOGS%20transmitters.ipynb

[[Category:Operate]]
[[Category:RF Modes]]

Observe

2020-01-20T22:47:41Z

Jebba: Librespace1 moved page Rating Observations to Observe: Shorten name

== Rating Observations ==

Below are examples of SatNOGS observations that can be used to help rating new observations as "Good", "Bad", or "Failed".

Click right and left arrows at top of image to view next image.

== Good Observations ==

These waterfalls are good observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1509702_2020-01-08T08-28-22.png|Observation 1509702
File:Waterfall_1456893_2019-12-30T10-35-46.png|Observation 1456893
File:Waterfall_1538438_2020-01-14T11-41-28.png|Observation 1538438
File:Waterfall_1475593_2020-01-01T23-14-41.png|Observation 1475593
File:Waterfall_1520385_2020-01-10T13-55-32.png|Observation 1520385
File:Waterfall_1531688_2020-01-13T10-08-44.png|Observation 1531688
File:Waterfall_1295041_2019-12-01T10-41-10.png|Observation 1295041
File:Waterfall_1521477_2020-01-10T19-31-32.png|Observation 1521477
File:Waterfall_1493960_2020-01-05T04-44-29.png|Observation 1493960
File:Waterfall_1505060_2020-01-07T10-17-10.png|Observation 1505060
File:Waterfall_1522671_2020-01-11T01-06-44.png|Observation 1522671
File:Waterfall_1232286_2019-11-21T16-57-56.png|Observation 1232286
File:Waterfall_1290522_2019-11-30T17-45-27.png|Observation 1290522
File:Waterfall_1522940_2020-01-11T02-48-24.png|Observation 1522940
File:Waterfall_1523025_2020-01-11T03-34-59.png|Observation 1523025
File:Waterfall_1522483_2020-01-11T00-53-53.png|Observation 1522483
File:Waterfall_1521561_2020-01-10T20-57-09.png|Observation 1521561
File:Waterfall_1522395_2020-01-11T00-21-25.png|Observation 1522395
File:Waterfall_1439401_2019-12-26T17-19-27.png|Observation 1439401
File:Waterfall_1521555_2020-01-10T20-20-54.png|Observation 1521555
File:Waterfall_1521311_2020-01-10T19-19-45.png|Observation 1521311
File:Waterfall_1521149_2020-01-10T19-06-44.png|Observation 1521149
File:Waterfall_1520938_2020-01-10T16-58-00.png|Observation 1520938
File:Waterfall_1521001_2020-01-10T17-13-53.png|Observation 1521001
File:Waterfall_1521004_2020-01-10T17-34-10.png|Observation 1521004
File:Waterfall_1521029_2020-01-10T17-38-40.png|Observation 1521029
File:Waterfall_1521031_2020-01-10T17-49-23.png|Observation 1521031
File:Waterfall_1521032_2020-01-10T17-55-29.png|Observation 1521032
File:Waterfall_1521077_2020-01-10T18-07-02.png|Observation 1521077
File:Waterfall_1521107_2020-01-10T18-17-01.png|Observation 1521107
File:Waterfall_1521108_2020-01-10T18-22-34.png|Observation 1521108
File:Waterfall_1521115_2020-01-10T18-42-03.png|Observation 1521115
File:Waterfall_1521309_2020-01-10T19-06-56.png|Observation 1521309
File:Waterfall_1524946_2020-01-11T14-57-12.png|Observation 1524946
File:Waterfall_1524914_2020-01-11T14-27-01.png|Observation 1524914
File:Waterfall_1524296_2020-01-11T10-01-27.png|Observation 1524296
</gallery>

== Bad Observations ==

These waterfalls show bad observations.

<gallery mode="slideshow" showthumbnails>
File:waterfall_1520894_2020-01-10T16-39-45.png|Observation 1520894
File:Waterfall_1484539_2020-01-03T13-22-00.png|Signal is interference from terrestrial APRS station.
File:Waterfall_1520897_2020-01-10T16-54-13.png|Observation 1520897
File:Waterfall_1521028_2020-01-10T17-33-03.png|Observation 1521028
File:Waterfall_1521105_2020-01-10T18-00-39.png|Observation 1521105
</gallery>

== Failed Observations ==

These waterfalls show failed observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1365407_2019-12-13T02-15-35.png|SatNOGS Client uploaded an image, but it is a solid color.
</gallery>

== Observations to Confirm ==
The below observations are corner cases or more difficult to discern than the above examples. As the below examples are confirmed by more experienced members of the community, they can be moved to their appropriate classification above.

=== Possibly Good Observations ===
The below observations are potentially "good" observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1525024_2020-01-11T15-28-52.png|Observation 1525024
File:Waterfall_1524945_2020-01-11T14-37-30.png|Observation 1524945
File:Waterfall_1524776_2020-01-11T13-35-22.png|Observation 1524776
File:Waterfall_1524775_2020-01-11T13-25-20.png|Observation 1524775
File:Waterfall_1524577_2020-01-11T12-23-50.png|Observation 1524577
File:Waterfall_1524511_2020-01-11T11-10-24.png|Observation 1524511
File:Waterfall_1524438_2020-01-11T10-34-55.png|Observation 1524438
File:Waterfall_1524358_2020-01-11T10-24-33.png|Observation 1524358
File:Waterfall_1524165_2020-01-11T09-50-17.png|Observation 1524165
File:Waterfall_1524092_2020-01-11T09-38-26.png|Observation 1524092
File:Waterfall_1524071_2020-01-11T09-27-29.png|Observation 1524071
File:Waterfall_1524066_2020-01-11T08-59-57.png|Observation 1524066
File:Waterfall_1523930_2020-01-11T08-12-36.png|Observation 1523930
File:Waterfall_1523768_2020-01-11T07-42-00.png|Observation 1523768
File:Waterfall_1523488_2020-01-11T06-41-14.png|Observation 1523488
</gallery>

=== Possibly Bad Observations ===
The below observations are potentially "bad" observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1524535_2020-01-11T11-13-50.png|Observation 1524535
File:Waterfall_1525047_2020-01-11T15-32-14.png|Observation 1525047
File:Waterfall_1524932_2020-01-11T14-12-57.png|Observation 1524932
File:Waterfall_1524740_2020-01-11T13-23-43.png|Observation 1524740
File:Waterfall_1524578_2020-01-11T12-31-46.png|Observation 1524578
File:Waterfall_1524579_2020-01-11T12-28-56.png|Observation 1524579
File:Waterfall_1524573_2020-01-11T12-02-50.png|Observation 1524573
File:Waterfall_1524510_2020-01-11T10-49-25.png|Observation 1524510
File:Waterfall_1524299_2020-01-11T10-21-03.png|Observation 1524299
File:Waterfall_1524166_2020-01-11T10-06-33.png|Observation 1524166
File:Waterfall_1524119_2020-01-11T09-47-27.png|Observation 1524119
File:Waterfall_1524091_2020-01-11T09-27-29.png|Observation 1524091
File:Waterfall_1524019_2020-01-11T08-25-42.png|Observation 1524019
File:Waterfall_1523690_2020-01-11T07-08-44.png|Observation 1523690
File:Waterfall_1523562_2020-01-11T07-10-27.png|Observation 1523562
</gallery>

=== Possibly Failed Observations ===
The below observations are potentially "failed" observations.

<gallery mode="slideshow" showthumbnails>
File:Waterfall_1525136_2020-01-11T15-58-19.png|Observation 1525136
</gallery>

== See also ==
* [[Operation]].
* [[Observations]].
* [[Intro|Introduction]] to SatNOGS.

[[Category:Operate]]

Rating Observations

2020-01-20T22:47:41Z

Jebba: Librespace1 moved page Rating Observations to Observe: Shorten name

#REDIRECT [[Observe]]

Observe

2020-01-20T22:47:07Z

Jebba: /* See also */ * Observations.

Observations

2020-01-20T22:45:32Z

Jebba: Librespace1 moved page Taxonomy of Observations to Observations: Shorten name

== Introduction ==
Satellites use a variety of transmitters, frequencies, and modes (encodings). Similar equipment will produce similar observations. Satellites can have, and often do have, multiple transmitters and modes. Below are various categories of observations.

== Transmitters ==
The SatNOGS DB API can generate the [https://db.satnogs.org/api/transmitters/ current list of transmitters].

== Modes ==
The SatNOGS DB API can generate the [https://db.satnogs.org/api/modes/ current list of modes].

At the time of writing, there are 65 modes, listed below:



<div style="column-count:6;-moz-column-count:6;-webkit-column-count:6">
* [[AFSK1k2]]
* [[AFSK9k6]]
* [[AFSK]]
* [[AHRPT]]
* [[AM]]
* [[APT]]
* [[BPSK1k2]]
* [[BPSK2k4]]
* [[BPSK4k8]]
* [[BPSK9k6]]
* [[BPSK12k5]]
* [[BPSK14k4]]
* [[BPSK115k2]]
* [[BPSK400]]
* [[BPSK]]
* [[CERTO]]
* [[CW]]
* [[DQPSK]]
* [[DSTAR]]
* [[DUV]]
* [[FFSK1k2]]
* [[FMN]]
* [[FM]]
* [[FSK1k2]]
* [[FSK2k4]]
* [[FSK4k8]]
* [[FSK9k6]]
* [[FSK19k2]]
* [[FSK]]
* [[GFSK1k2]]
* [[GFSK2k4]]
* [[GFSK4k8]]
* [[GFSK9k6]]
* [[GFSK19k2]]
* [[GFSK_Rktr]]
* [[GFSK]]
* [[GMSK1k2]]
* [[GMSK2k4]]
* [[GMSK4k8]]
* [[GMSK9k6]]
* [[GMSK19k2]]
* [[GMSK]]
* [[HRPT]]
* [[LRPT]]
* [[LSB]]
* [[MFSK]]
* [[MSK1k2]]
* [[MSK2k4]]
* [[MSK4k8]]
* [[MSK9k6]]
* [[MSK19k2]]
* [[MSK38k4]]
* [[OFDM]]
* [[OQPSK]]
* [[PSK4k8]]
* [[PSK31]]
* [[PSK63]]
* [[PSK]]
* [[QPSK31]]
* [[QPSK38k4]]
* [[QPSK63]]
* [[QPSK]]
* [[SSTV]]
* [[USB]]
* [[WSJT]]
</div>

=== Example Waterfalls ===
Below are waterfalls depicting various modes.

<gallery mode="packed" widths=310px heights=400px>
File:Waterfall_1439401_2019-12-26T17-19-27.png|[[AFSK1k2]]
File:Waterfall_1522395_2020-01-11T00-21-25.png|[[BPSK400]]
File:Waterfall_1521561_2020-01-10T20-57-09.png|[[BPSK1k2]]
File:Waterfall_1521031_2020-01-10T17-49-23.png|[[BPSK1k2]]
File:Waterfall 1521001 2020-01-10T17-13-53.png|[[BPSK1k2]]
File:Waterfall 1521004 2020-01-10T17-34-10.png|[[BPSK1k2]]
File:Waterfall 1521077 2020-01-10T18-07-02.png|[[BPSK12k5]]
File:Waterfall_1509702_2020-01-08T08-28-22.png|[[CERTO]]
File:Waterfall_1523025_2020-01-11T03-34-59.png|[[CW]]
File:Waterfall_1522483_2020-01-11T00-53-53.png|[[CW]]
File:Waterfall 1521149 2020-01-10T19-06-44.png|[[DUV]]
File:Waterfall_1521555_2020-01-10T20-20-54.png|[[FM]]
File:Waterfall 1524296 2020-01-11T10-01-27.png|[[FM]]
File:Waterfall_1521311_2020-01-10T19-19-45.png|[[FM]]
File:Waterfall 1521115 2020-01-10T18-42-03.png|[[FSK9k6]]
File:Waterfall 1521309 2020-01-10T19-06-56.png|[[FSK9k6]]
File:Waterfall 1524914 2020-01-11T14-27-01.png|[[FSK19k2]]
File:Waterfall_1290522_2019-11-30T17-45-27.png|[[GFSK Rktr]]
File:Waterfall_1232286_2019-11-21T16-57-56.png|[[GFSK9k6]]
File:Waterfall_1522671_2020-01-11T01-06-44.png|[[GFSK19k2]]
File:Waterfall 1524946 2020-01-11T14-57-12.png|[[GMSK]]
File:Waterfall_1493960_2020-01-05T04-44-29.png|[[GMSK1k2]]
File:Waterfall_1505060_2020-01-07T10-17-10.png|[[GMSK1k2]]
File:Waterfall_1521477_2020-01-10T19-31-32.png|[[GMSK2k4]]
File:Waterfall 1521029 2020-01-10T17-38-40.png|[[GMSK4k8]]
File:Waterfall 1521032 2020-01-10T17-55-29.png|[[GMSK4k8]]
File:Waterfall 1521108 2020-01-10T18-22-34.png|[[GMSK9k6]]
File:Waterfall_1531688_2020-01-13T10-08-44.png|[[LRPT]]
File:Waterfall_1520385_2020-01-10T13-55-32.png|[[MSK1k2]]
File:Waterfall_1295041_2019-12-01T10-41-10.png|[[PSK31]]
File:Waterfall_1456893_2019-12-30T10-35-46.png|[[SSTV]]
File:Waterfall_1538438_2020-01-14T11-41-28.png|[[USB]]
File:Waterfall_1475593_2020-01-01T23-14-41.png|[[USB]]
</gallery>

== See also ==

* [[Operation]]
* [[Rating_Observations]]
* [[Decode Telemetry and Packets]]
* [[:Category:RF_Modes]]
* [https://en.wikipedia.org/wiki/List_of_amateur_radio_modes List of amateur radio modes].
* [https://db.satnogs.org/stats/ SatNOGS DB stats on transmitters, modes, and bands].
* [[Adding a new data decoder]] to SatNOGS.

Note, for some modes there are a variety of baud rates and other factors that make it so two identical modes might not necessarily look similar. For further comments on the variety of modes, see:

* https://destevez.net/2020/01/extracting-ax-25-satellites-from-satnogs-db/
* https://github.com/daniestevez/jupyter_notebooks/blob/master/SatNOGS%20transmitters.ipynb

[[Category:Operate]]
[[Category:RF Modes]]

Taxonomy of Observations

2020-01-20T22:45:32Z

Jebba: Librespace1 moved page Taxonomy of Observations to Observations: Shorten name

#REDIRECT [[Observations]]

AX.25

2020-01-20T22:44:34Z

Jebba: /* See also */ Category:Operate no

== Introduction ==
AX.25 (Amateur X.25) is a data link layer protocol originally derived from layer 2 of the X.25 protocol suite and designed for use by amateur radio operators. It is used extensively on amateur packet radio networks.

== See also ==
* [[Decode Telemetry and Packets]]
* [https://en.wikipedia.org/wiki/AX.25 Wikipedia AX.25]

[[Category:RF Modes]]

AX.25

2020-01-20T22:43:21Z

Jebba: intro stub

AX 25

2020-01-20T22:41:50Z

Jebba: #REDIRECT AX.25

#REDIRECT [[AX.25]]

AX25

2020-01-20T22:41:27Z

Jebba: #REDIRECT AX.25

#REDIRECT [[AX.25]]

AX.25

2020-01-20T22:41:00Z

Jebba: AX.25 stub

== Introduction ==
AX.25 stub.

== See also ==
* [[Decode Telemetry and Packets]]

[[Category:RF Modes]]
[[Category:Operate]]

Decode Telemetry and Packets

2020-01-20T22:38:49Z

Jebba: * [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs#adding-a-new-satellite-demodulator gr-satnogs Adding a New Satellite]

== Introduction ==

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

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

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

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

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

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

SoX supports demodulating the following modes:

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

===References===

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

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

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

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

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

===References===

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

==multimon-ng==

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

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

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

===How to AFSK===

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

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

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

===References===

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

==Direwolf==

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

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

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

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

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

===Usage===

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

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

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

 

==WXtoImg==

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

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

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

===Usage===

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

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

*Then invoke command line interface of WXtoIMG with:

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

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

== See also ==
* [http://www.dk3wn.info/software.shtml Satellite specific telemetry decoders] (German)
* [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs#adding-a-new-satellite-demodulator gr-satnogs Adding a New Satellite]

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

__NOEDITSECTION__

Decode

2020-01-20T22:32:50Z

Jebba: #REDIRECT Decode_Telemetry_and_Packets

#REDIRECT [[Decode_Telemetry_and_Packets]]

Demodulator

2020-01-20T22:32:17Z

Jebba: #REDIRECT Decode_Telemetry_and_Packets

#REDIRECT [[Decode_Telemetry_and_Packets]]

SatNOGS Setup Legacy

2020-01-20T22:14:41Z

Jebba: * SatNOGS Client Ansible

==Introduction==
<code>satnogs-setup</code> provides a set of scripts for configuring a '''SatNOGS Client''' system. <code>satnogs-setup</code> main function is to bring up a menu-driven console configuration utility and provision the system using [[SatNOGS Client Ansible|Ansible]].

==Initial Setup==
Right after the first boot of the system, packages and the configuration tool itself '''must be updated'''. Follow the [[SatNOGS Client Setup#Updating SatNOGS Client Software|Updating]] instruction found below.

To configure a '''SatNOGS Client''' system:

#SSH into the system and run <code>sudo satnogs-setup</code>; this will bring up the configuration menu
#Set '''all''' options in '''Basic Configuration''' (see below)
#Select <code>Apply</code> and the Raspberry Pi will configure itself; this may take some time
#Select <code>Back</code> to exit
{{Message|You can always reconfigure the software by running <code>sudo satnogs-setup</code> again.}}
===Basic Configuration===
{| class="wikitable"
!Setting
!Description
|-
|<code>SATNOGS_API_TOKEN</code>
|The API token assigned to your ground station on the SatNOGS Network website, please don’t share your api key as this can give access to anyone to upload and change things in network related to your station and its observations.
|-
|<code>SATNOGS_RX_DEVICE</code>
|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/airspymini</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].
|-
|<code>SATNOGS_STATION_ELEV</code>
|The height of your ground station above sea level in metres.
|-
|<code>SATNOGS_STATION_ID</code>
|The '''numeric ID''' assigned to your station in the SatNOGS Network site when the groundstation was created.
|-
|<code>SATNOGS_STATION_LAT</code>
|The latitude of your station. North is positive, south is negative.
|-
|<code>SATNOGS_STATION_LON</code>
|The longitude of your station. East is positive, west is negative.
|-
|<code>HAMLIB_UTILS_ROT_ENABLED</code>
|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 [[No rotator|No rotator setup]]), enter <code>NO</code>.
|-
|<code>HAMLIB_UTILS_ROT_OPTS</code>
|Options for rotcld:
For a yaesu rotator, use <code>-m 601 -r /dev/ttyACM0 -s 9600 -T 0.0.0.0</code>

For a SatNOGS rotator <code>-m 204 -s 19200 -r /dev/ttyACM0 -C timeout=200</code> or <code>-m 204 -s 19200 -r /dev/ttyUSB0 -C timeout=200</code>
|}
==Advanced Setup==
{{Warning|Changing these settings is ''not'' recommended unless you're developing SatNOGS.}}A more detailed description on setting up a development environment using the SatNOGS reference setup is given in [[SatNOGS_Client_Development]].

NOTE: To get your station online, you need to set SATNOGS_NETWORK_API_URL to https://network.satnogs.org/api/
{| class="wikitable"
!Setting
!Description
|-
|<code>APT_REPOSITORY</code>
|This options allows you to change the SatNOGS packages repository. For example, to install unstable package builds use:
<code>deb <nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs_unstable/Raspbian_10</nowiki> ./</code>
|-
|<code>APT_KEY_URL</code>
|This options allows you to change the SatNOGS packages repository key URL. For example, to install unstable package builds use:
<code><nowiki>http://download.opensuse.org/repositories/home:/librespace:/satnogs_unstable/Raspbian_10/Release.key</nowiki></code>
|-
|<code>APT_KEY_ID</code>
|This options allows you to specify an alternative SatNOGS packages repository key ID.
|-
|<code>SATNOGS_CLIENT_URL</code>
|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:

*<code>git+https://gitlab.com/librespacefoundation/satnogs/satnogs-client.git@master</code> -- the 'master' branch (the current development version) of satnogs-client
*<code><nowiki>git+https://gitlab.com/jdoe/satnogs-client.git@new-feature</nowiki></code> -- the 'new-feature' branch of jdoe's fork of satnogs-client
|-
|<code>SATNOGS_RADIO_GR_SATNOGS_VERSION</code>
|This options allows you to change the version of gr-satnogs package to be installed. For example:
<code>1.5.1-1</code>
|-
|<code>RF_GAIN</code>
|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: <code>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</code>
|}
==Updating SatNOGS Client Software==
To update SatNOGS software, including the configuration tool itself:

#SSH into the system and (re-)run <code>sudo satnogs-setup</code>; this will bring up the configuration menu
#Select <code>Upgrade</code> to upgrade all distribution packages to the latest; this may require a reboot. If this option is not available, running an <code>Update</code> will make it show up
#Select <code>Update</code> to update the configuration tool
#Select <code>Apply</code> and the Raspberry Pi will update itself; this may take some time
#Before exit, check at the top that you have the latest satnogs-client and gr-satnogs versions
#Select <code>Back</code> to exit

'''WARNING: An update can potentially interrupt a running observation!'''
===Upgrading from Debian 'stretch' to 'buster'===
If you have already installed an older version of Debian or Raspbian SatNOGS image based on <code>stretch</code> (releases <= [https://gitlab.com/librespacefoundation/satnogs/satnogs-pi-gen/-/tags/2018080300 2018080300]), it is recommended to upgrade to <code>buster</code>. Support for <code>stretch</code> will be dropped with the next release of <code>gr-satnogs</code>.
====Method 1: Reflashing and reinstalling (recommended)====
The recommended method to upgrade to <code>buster</code> is reflashing the latest Raspbian SatNOGS image (or reinstalling latest Debian). Follow [[Raspberry Pi|Raspberry Pi]] installation instructions and reinstall from scratch.
====Method 2: Release upgrade using the configuration tool (advanced)====
{{Warning|Make sure you have a stable connection to the internet and your SatNOGS client during this process. Release upgrades can consume a lot of time, data and storage.}}To upgrade from stretch to buster using the configuration tool:

#SSH into the system
#Make sure you have enough free space on your SD card (>2GiB) by running <code>df -h /</code> on the console
#Run <code>sudo satnogs-setup</code> to bring up the configuration menu
#On the Advanced menu, enable <code>SATNOGS_SETUP_RELEASE_UPGRADE_ENABLED</code> option, in case there isn't an option like that available run first <code>Update</code> and then try again to enable it.
#On the Main menu, select <code>Apply</code> and let Ansible apply the configuration
#On the Main menu, select <code>Upgrade</code>. The script will check if there is a new release upgrade and ask you to proceed
#Keep an eye on the upgrade progress; <code>dpkg</code> may prompt for changes
#Once the upgrade is completed, <code>satnogs-setup</code> will ask for a reboot
#After the reboot, make sure you are on the correct release by running <code>lsb_release -a</code>
#Re-run <code>sudo satnogs-setup</code> and select <code>Update</code> and then <code>Apply</code>

==Verification of correct installation==
To see if satnogs-client has started successfully, check the logs with journalctl:<pre>
$ journalctl -u satnogs-client.service
</pre>You should see entries running approximately once per minute that look like this:<pre>
Oct 01 23:02:13 raspberrypi satnogs-client[6695]: * Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)
Oct 01 23:02:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:02:14,466 - satnogsclient - INFO - [LD] Downlink thread waiting for first downlink packet
Oct 01 23:03:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:14,450 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:03:14 UTC)" (scheduled at 2017-10-01 23:03:14.423393+00:00)
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,324 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,325 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:03:47 raspberrypi satnogs-client[6695]: 2017-10-01 23:03:47,327 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,453 - apscheduler.executors.default - INFO - Running job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.423393+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,484 - apscheduler.executors.default - INFO - Running job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" (scheduled at 2017-10-01 23:04:14.436367+00:00)
Oct 01 23:04:14 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:14,489 - apscheduler.executors.default - INFO - Job "post_data (trigger: interval[0:02:00], next run at: 2017-10-01 23:04:14 UTC)" executed successfully
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,627 - satnogsclient - DEBUG - Opening TCP socket: 127.0.0.1:5011
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,628 - satnogsclient - DEBUG - Sending message: []
Oct 01 23:04:15 raspberrypi satnogs-client[6695]: 2017-10-01 23:04:15,629 - apscheduler.executors.default - INFO - Job "get_jobs (trigger: interval[0:01:00], next run at: 2017-10-01 23:05:14 UTC)" executed successfully
</pre>If you see that, great -- you're ready to [[Operation|schedule your first observation]]! If not, check out the [[Troubleshooting]] page.

== See also ==
* [[SatNOGS Client Ansible]]

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

SatNOGS Ansible

2020-01-20T22:14:05Z

Jebba: /* See also */ meh

==Introduction==

'''SatNOGS Client Ansible''' makes the actual provisioning of the '''SatNOGS Client''' system. It is called, under the hood, when applying the configuration using [[SatNOGS Client Setup|SatNOGS Client Setup utility]]. It currently supports Raspbian and Debian (stretch and buster).

==Raspbian==

For Raspberry Pi, which is the reference platform for SatNOGS, a [[Raspberry Pi|Raspbian image]] with '''SatNOGS Client Ansible''' pre-installed is available.

==Debian==

{{Warning|Follow these instructions only if you are provisioning SatNOGS to Debian from another host or are installing on the same host. If you are using [[Raspberry_Pi|SatNOGS Raspbian]] image, follow [[SatNOGS_Client_Setup|SatNOGS Client Setup]] to set up your system. }}These sections contain generic instructions for installing SatNOGS Client on a Debian system.

===Prerequisites===

*A target Debian system. To install Debian please follow the [https://www.debian.org/releases/stretch/installmanual Debian Installation Guide] and chose the net installer if you want to run a headless server. The target system can be the host itself.
*A user (referenced later as ''youruser'') which is member of 'sudo' group exists on the target system.
*An SSH server running on the target system.
*A host system with Git and latest version of Ansible installed. To install Ansible on Debian, follow the [https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html#latest-releases-via-apt-debian Ansible Installation Guide].

===Installation===

On the host system run the following commands:
$ git clone <nowiki>https://gitlab.com/librespacefoundation/satnogs/satnogs-client-ansible.git</nowiki> # Clone SatNOGS Client Ansible repository
$ cd satnogs-client-ansible # Change to cloned repository directory
$ cp -r production.dist production # Copy dist configuration
$ vi production/inventory/hosts # Update file with your own target host e.g. 127.0.0.1, user and SSH password
$ ssh youruser@yourtargetsystem true # Test SSH connection to target system
$ ansible-playbook -i production/inventory -K site.yml # Run Ansible playbook
$ ssh -t youruser@yourtargetsystem sudo satnogs-setup # Setup SatNOGS client (see below)

 

== See also ==
* [[SatNOGS Client Setup]]

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