https://wiki.satnogs.org/api.php?action=feedcontributions&user=Pierros&feedformat=atomSatNOGS Wiki - User contributions [en]2024-03-29T11:45:14ZUser contributionsMediaWiki 1.32.0https://wiki.satnogs.org/index.php?title=File:Frequency_misuse.drawio.png&diff=3826File:Frequency misuse.drawio.png2022-05-07T07:09:26Z<p>Pierros: Pierros uploaded a new version of File:Frequency misuse.drawio.png</p>
<hr />
<div>Frequency misuse</div>Pierroshttps://wiki.satnogs.org/index.php?title=File:Frequency_misuse.drawio.png&diff=3825File:Frequency misuse.drawio.png2022-05-07T07:07:35Z<p>Pierros: Pierros uploaded a new version of File:Frequency misuse.drawio.png</p>
<hr />
<div>Frequency misuse</div>Pierroshttps://wiki.satnogs.org/index.php?title=Spectrum_Management&diff=3824Spectrum Management2022-05-06T08:03:14Z<p>Pierros: </p>
<hr />
<div>===Definitions===<br />
<br />
====Frequency Coordination====<br />
Frequency coordination is, preceding its use, the technical coordination of frequencies (including geostationary orbits) conducted by the authorities who are planning the radiocommunication network, on the basis of the Radio Regulation(RR) enacted by the International Telecommunication Union (ITU), in order to prevent the frequencies radiocommunication networks from causing harmful interference to the networks of foreign counties.<br />
<br />
<br /><br />
<br />
====ITU Radiocommunication Service====<br />
A radiocommunication service is – according to Article 1.19 of the International Telecommunication Union's (ITU) Radio Regulations (RR) – defined as «A service…involving the transmission, emission and/or reception of radio waves for specific telecommunication purposes.» <br />
<br /><br />
<br /><br />
<br />
====Satellite Service====<br />
Satellite services means communications capabilities that utilize an on-orbit satellite for transmitting the signal from one location to another. Those are the services that are of interest to the SatNOGS project.<br />
<br />
<br />
The following are all the possible different satellite services:<br />
{| class="wikitable"<br />
|'''ITU RR Article'''<br />
|'''Description'''<br />
|'''Short'''<br />
|'''Links'''<br />
|'''In SatNOGS DB'''<br />
|-<br />
|1.21<br />
|Fixed-satellite service<br />
|FSS<br />
|[[wikipedia:Fixed-satellite_service|Main article: Fixed-satellite service]]<br />
|YES<br />
|-<br />
|1.22<br />
|Inter-satellite service<br />
|ISS<br />
|[[wikipedia:Inter-satellite_service|Main article: Inter-satellite service]]<br />
|YES<br />
|-<br />
|1.23<br />
|Space operation service<br />
|SOS<br />
|[[wikipedia:Space_operation_service|Main article: Space operation service]]<br />
|YES<br />
|-<br />
|1.25<br />
|Mobile-satellite service<br />
|MSS<br />
|[[wikipedia:Mobile-satellite_service|Main article: Mobile-satellite service]]<br />
|YES<br />
|-<br />
|1.29<br />
|Maritime mobile-satellite service<br />
|MMSS<br />
|[[wikipedia:Maritime_mobile-satellite_service|Main article: Maritime mobile-satellite service]]<br />
|YES<br />
|-<br />
|1.35<br />
|Aeronautical mobile-satellite service<br />
|AMSS<br />
|[[wikipedia:Aeronautical_mobile-satellite_service|Main article: Aeronautical mobile-satellite service]]<br />
|YES<br />
|-<br />
|1.39<br />
|Broadcasting-satellite service<br />
|BSS<br />
|[[wikipedia:Broadcasting-satellite_service|Main article: Broadcasting-satellite service]]<br />
|YES<br />
|-<br />
|1.43<br />
|Radionavigation-satellite service<br />
|RNSS<br />
|[[wikipedia:Radionavigation-satellite_service|Main article: Radionavigation-satellite service]]<br />
|YES<br />
|-<br />
|1.49<br />
|Radiolocation-satellite service<br />
|RLSS<br />
|[[wikipedia:Radiolocation-satellite_service|Main article: Radiolocation-satellite service]]<br />
|YES<br />
|-<br />
|1.51<br />
|Earth exploration-satellite service<br />
|EESS<br />
|[[wikipedia:Earth_exploration-satellite_service|Main article: Earth exploration-satellite service]]<br />
|YES<br />
|-<br />
|1.52<br />
|Meteorological-satellite service<br />
|<br />
|[[wikipedia:Meteorological-satellite_service|Main article: Meteorological-satellite service]]<br />
|YES<br />
|-<br />
|1.54<br />
|Standard frequency and time signal-satellite service<br />
|SFTSS<br />
|[[wikipedia:Standard_frequency_and_time_signal-satellite_service|Main article: Standard frequency and time signal-satellite service]]<br />
|YES<br />
|-<br />
|1.55<br />
|Space research service<br />
|SRS<br />
|[[wikipedia:Standard_frequency_and_time_signal-satellite_service|Main article: Space research service]]<br />
|YES<br />
|-<br />
|1.57<br />
|Amateur-satellite service<br />
|Amateur-satellite<br />
|[[wikipedia:Amateur_radio_satellite#International_regulation|Main article: Amateur-satellite service]]<br />
|YES<br />
|}<br /><br />
===SatNOGS Policy===<br />
In Libre Space Foundation we take frequency coordination, spectrum management and violations very seriously. Radio spectrum is a finite resource and we need to follow international regulations and practices to ensure fair access and usage of frequencies as services.<br />
<br />
<br />
We use the following diagram to determine if a satellite should be marked for frequency misuse:<br /><br />
[[File:Frequency misuse.drawio.png|center|frameless|646x646px]]<br />
<br /></div>Pierroshttps://wiki.satnogs.org/index.php?title=File:Frequency_misuse.drawio.png&diff=3823File:Frequency misuse.drawio.png2022-05-06T08:02:49Z<p>Pierros: </p>
<hr />
<div>Frequency misuse</div>Pierroshttps://wiki.satnogs.org/index.php?title=Spectrum_Management&diff=3822Spectrum Management2022-05-06T07:46:26Z<p>Pierros: Add service definitions</p>
<hr />
<div>=== Definitions ===<br />
<br />
====Frequency Coordination====<br />
Frequency coordination is, preceding its use, the technical coordination of frequencies (including geostationary orbits) conducted by the authorities who are planning the radiocommunication network, on the basis of the Radio Regulation(RR) enacted by the International Telecommunication Union (ITU), in order to prevent the frequencies radiocommunication networks from causing harmful interference to the networks of foreign counties.<br />
<br />
<br /><br />
<br />
==== ITU Radiocommunication Service ====<br />
A radiocommunication service is – according to Article 1.19 of the International Telecommunication Union's (ITU) Radio Regulations (RR) – defined as «A service…involving the transmission, emission and/or reception of radio waves for specific telecommunication purposes.» <br />
<br /><br />
<br />
==== Satellite Service ====<br />
Satellite services means communications capabilities that utilize an on-orbit satellite for transmitting the signal from one location to another. Those are the services that are of interest to the SatNOGS project.<br />
<br />
<br />
The following are all the possible different satellite services:<br />
{| class="wikitable"<br />
|'''ITU RR Article'''<br />
|'''Description'''<br />
|'''Short'''<br />
|'''Links'''<br />
|'''In SatNOGS DB'''<br />
|-<br />
|1.21<br />
|Fixed-satellite service<br />
|FSS<br />
|[[wikipedia:Fixed-satellite_service|Main article: Fixed-satellite service]]<br />
|YES<br />
|-<br />
|1.22<br />
|Inter-satellite service<br />
|ISS<br />
|[[wikipedia:Inter-satellite_service|Main article: Inter-satellite service]]<br />
|YES<br />
|-<br />
|1.23<br />
|Space operation service<br />
|SOS<br />
|[[wikipedia:Space_operation_service|Main article: Space operation service]]<br />
|YES<br />
|-<br />
|1.25<br />
|Mobile-satellite service<br />
|MSS<br />
|[[wikipedia:Mobile-satellite_service|Main article: Mobile-satellite service]]<br />
|YES<br />
|-<br />
|1.29<br />
|Maritime mobile-satellite service<br />
|MMSS<br />
|[[wikipedia:Maritime_mobile-satellite_service|Main article: Maritime mobile-satellite service]]<br />
|YES<br />
|-<br />
|1.35<br />
|Aeronautical mobile-satellite service<br />
|AMSS<br />
|[[wikipedia:Aeronautical_mobile-satellite_service|Main article: Aeronautical mobile-satellite service]]<br />
|YES<br />
|-<br />
|1.39<br />
|Broadcasting-satellite service<br />
|BSS<br />
|[[wikipedia:Broadcasting-satellite_service|Main article: Broadcasting-satellite service]]<br />
|YES<br />
|-<br />
|1.43<br />
|Radionavigation-satellite service<br />
|RNSS<br />
|[[wikipedia:Radionavigation-satellite_service|Main article: Radionavigation-satellite service]]<br />
|YES<br />
|-<br />
|1.49<br />
|Radiolocation-satellite service<br />
|RLSS<br />
|[[wikipedia:Radiolocation-satellite_service|Main article: Radiolocation-satellite service]]<br />
|YES<br />
|-<br />
|1.51<br />
|Earth exploration-satellite service<br />
|EESS<br />
|[[wikipedia:Earth_exploration-satellite_service|Main article: Earth exploration-satellite service]]<br />
|YES<br />
|-<br />
|1.52<br />
|Meteorological-satellite service<br />
|<br />
|[[wikipedia:Meteorological-satellite_service|Main article: Meteorological-satellite service]]<br />
|YES<br />
|-<br />
|1.54<br />
|Standard frequency and time signal-satellite service<br />
|SFTSS<br />
|[[wikipedia:Standard_frequency_and_time_signal-satellite_service|Main article: Standard frequency and time signal-satellite service]]<br />
|YES<br />
|-<br />
|1.55<br />
|Space research service<br />
|SRS<br />
|[[wikipedia:Standard_frequency_and_time_signal-satellite_service|Main article: Space research service]]<br />
|YES<br />
|-<br />
|1.57<br />
|Amateur-satellite service<br />
|Amateur-satellite<br />
|[[wikipedia:Amateur_radio_satellite#International_regulation|Main article: Amateur-satellite service]]<br />
|YES<br />
|}<br />
<br />
=== SatNOGS Policy ===<br />
In Libre Space Foundation we take frequency coordination, spectrum management and violations very seriously. Radio spectrum is a finite resource and we need to follow international regulations and practices to ensure fair access and usage of frequencies as services.<br />
<br /></div>Pierroshttps://wiki.satnogs.org/index.php?title=Spectrum_Management&diff=3771Spectrum Management2021-07-19T07:33:06Z<p>Pierros: what is frequency coordination</p>
<hr />
<div>=== Frequency Coordination ===<br />
Frequency coordination is, preceding its use, the technical coordination of frequencies (including geostationary orbits) conducted by the authorities who are planning the radiocommunication network, on the basis of the Radio Regulation(RR) enacted by the International Telecommunication Union (ITU), in order to prevent the frequencies radiocommunication networks from causing harmful interference to the networks of foreign counties.<br />
<br />
<br />
More detailed information coming soon.</div>Pierroshttps://wiki.satnogs.org/index.php?title=Spectrum_Management&diff=3694Spectrum Management2020-10-27T10:46:57Z<p>Pierros: </p>
<hr />
<div>Frequency coordination matters.<br />
<br />
<br />
More detailed information coming soon.</div>Pierroshttps://wiki.satnogs.org/index.php?title=SatNOGS_DB&diff=3659SatNOGS DB2020-08-14T11:09:50Z<p>Pierros: /* Introduction */</p>
<hr />
<div>__NOTOC__<br />
<br />
==Introduction==<br />
<br />
[https://db.satnogs.org/ SatNOGS DB] is an effort to create a holistic, unified, global transmitter database for all satellite information. You can export the data or even connect your application using our API. It's part of the SatNOGS project.<br />
[[File:SatNOGS DB front page.png|alt=|center|800x800px]]<br />
<br /><br />
<br />
==Data==<br />
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.<br />
<br />
==Contribute==<br />
<br />
===Adding Satellites===<br />
If you are a moderator you can add new satellites on the DB. For that follow the instructions:<br />
<br />
#Log in to db.satnogs.org<br />
#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)<br />
#Click on Base::Satellite [https://db.satnogs.org/admin/base/satellite/add/ Add button]<br />
#Complete the information to the best of your knowledge. NORAD ID and Name are mandatory. Add multiple names on the "Names" field.<br />
#Click Save and you are done!<br />
#You can now move on to the next steps: suggesting and approving transmitters for this satellite.<br />
<br />
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.<br />
<br />
===Suggesting transmitters===<br />
[[File:Create new transmitter.png|thumb|Menu item to add new transmitter suggestion (for logged in users)]]<br />
[[File:Transmitter suggestion.png|alt=|thumb|New transmitter suggestion (any logged in user can do it!)]]<br />
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.<br />
<br />
Navigate to the satellite you want to edit or suggest a new transmitter and click on the Edit menu while logged-in.<br /><br />
<br />
*Description: This is the name that will appear for this transmitter across DB, Network, and API users. Please use the following notations<br />
**Band, for instance VHF, or for a transceiver, MODE U/V<br />
**Baud (if applicable), in the format 9k6 for 9600<br />
**Mode, for instance FSK<br />
**Rough type description, ie TLM for "telemetry", or "FM Transponder" for repeater<br />
**Examples<br />
***UHF 9k6 FSK TLM<br />
***MODE U/V FM Transceiver<br />
***VHF CW TLM<br />
*Type<br />
**Transmitter: one-way downlink (telemetry)<br />
**Transceiver: repeats an uplinked signal intact<br />
**Transponder: interacts with an uplinked signal or downlinks after signal modification<br />
*Status<br />
**Active: alive and well<br />
**Inactive: not functional or powered down<br />
**Invalid: this is a legacy or erroneous transmitter information that should be hidden from UI<br />
*Downlink Freq: Published frequency, in Hz<br />
*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.<br />
*Downlink Mode: The modulation mode for this transmitter<br />
*Baud rate: the baud rate, if applicable. If this is a CW beacon, use WPM<br />
*Citation URL: a URL to link to in providing the details for your suggestion. Include observations from SatNOGS Network and/or frequency coordination documentation.<br />
*Service: The ITU service that the transmitter can be categorized.<br />
<br />
===Approving transmitters===<br />
[[File:Review transmitter suggestion.png|thumb|Review transmitter suggestion (for moderators only)]]<br />
If you are a moderator you can approved suggestions for transmitters. For that follow the instructions:<br />
<br />
#Log in to db.satnogs.org<br />
#Navigate to the satellite page that has pending suggestions for transmitters<br />
#Review the suggestion<br />
#Decide to accept or reject it by clicking on the transmitter menu top right.<br />
<br />
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.<br />
<br />
===Coding===<br />
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.<br />
<br />
==API==<br />
<br />
More info can be found in [[SatNOGS DB/API|API wiki page]].<br />
<br />
==Documentation & Installation==<br />
<br />
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].<br />
<br />
==See also==<br />
<br />
*[[SatNOGS Network]]<br />
*[https://libre.space/2020/03/02/space-situational-awareness/ Space Situational Awareness – The story so far and an open way forward]<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Operate]]<br />
[[Category:Satellite]]<br />
[[Category:RF Modes]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=SatNOGS_DB&diff=3658SatNOGS DB2020-08-14T11:09:08Z<p>Pierros: /* API */</p>
<hr />
<div>__NOTOC__<br />
<br />
==Introduction==<br />
<br />
[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.<br />
<br />
[[File:Satnogs-db-cap.png|800px|SatNOGS DB Screen capture]]<br />
<br />
==Data==<br />
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.<br />
<br />
==Contribute==<br />
<br />
===Adding Satellites===<br />
If you are a moderator you can add new satellites on the DB. For that follow the instructions:<br />
<br />
#Log in to db.satnogs.org<br />
#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)<br />
#Click on Base::Satellite [https://db.satnogs.org/admin/base/satellite/add/ Add button]<br />
#Complete the information to the best of your knowledge. NORAD ID and Name are mandatory. Add multiple names on the "Names" field.<br />
#Click Save and you are done!<br />
#You can now move on to the next steps: suggesting and approving transmitters for this satellite.<br />
<br />
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.<br />
<br />
===Suggesting transmitters===<br />
[[File:Create new transmitter.png|thumb|Menu item to add new transmitter suggestion (for logged in users)]]<br />
[[File:Transmitter suggestion.png|alt=|thumb|New transmitter suggestion (any logged in user can do it!)]]<br />
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.<br />
<br />
Navigate to the satellite you want to edit or suggest a new transmitter and click on the Edit menu while logged-in.<br /><br />
<br />
*Description: This is the name that will appear for this transmitter across DB, Network, and API users. Please use the following notations<br />
**Band, for instance VHF, or for a transceiver, MODE U/V<br />
**Baud (if applicable), in the format 9k6 for 9600<br />
**Mode, for instance FSK<br />
**Rough type description, ie TLM for "telemetry", or "FM Transponder" for repeater<br />
**Examples<br />
***UHF 9k6 FSK TLM<br />
***MODE U/V FM Transceiver<br />
***VHF CW TLM<br />
*Type<br />
**Transmitter: one-way downlink (telemetry)<br />
**Transceiver: repeats an uplinked signal intact<br />
**Transponder: interacts with an uplinked signal or downlinks after signal modification<br />
*Status<br />
**Active: alive and well<br />
**Inactive: not functional or powered down<br />
**Invalid: this is a legacy or erroneous transmitter information that should be hidden from UI<br />
*Downlink Freq: Published frequency, in Hz<br />
*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.<br />
*Downlink Mode: The modulation mode for this transmitter<br />
*Baud rate: the baud rate, if applicable. If this is a CW beacon, use WPM<br />
*Citation URL: a URL to link to in providing the details for your suggestion. Include observations from SatNOGS Network and/or frequency coordination documentation.<br />
*Service: The ITU service that the transmitter can be categorized.<br />
<br />
===Approving transmitters===<br />
[[File:Review transmitter suggestion.png|thumb|Review transmitter suggestion (for moderators only)]]<br />
If you are a moderator you can approved suggestions for transmitters. For that follow the instructions:<br />
<br />
#Log in to db.satnogs.org<br />
#Navigate to the satellite page that has pending suggestions for transmitters<br />
#Review the suggestion<br />
#Decide to accept or reject it by clicking on the transmitter menu top right.<br />
<br />
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.<br />
<br />
===Coding===<br />
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.<br />
<br />
==API==<br />
<br />
More info can be found in [[SatNOGS DB/API|API wiki page]].<br />
<br />
==Documentation & Installation==<br />
<br />
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].<br />
<br />
==See also==<br />
<br />
*[[SatNOGS Network]]<br />
*[https://libre.space/2020/03/02/space-situational-awareness/ Space Situational Awareness – The story so far and an open way forward]<br />
<br />
[[Category:Infrastructure]]<br />
[[Category:Operate]]<br />
[[Category:Satellite]]<br />
[[Category:RF Modes]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=File:Create_new_transmitter.png&diff=3657File:Create new transmitter.png2020-08-14T11:05:34Z<p>Pierros: </p>
<hr />
<div>Create new transmitter</div>Pierroshttps://wiki.satnogs.org/index.php?title=File:Transmitter_suggestion.png&diff=3656File:Transmitter suggestion.png2020-08-14T11:04:40Z<p>Pierros: </p>
<hr />
<div>Transmitter suggestion</div>Pierroshttps://wiki.satnogs.org/index.php?title=File:Review_transmitter_suggestion.png&diff=3655File:Review transmitter suggestion.png2020-08-14T11:03:04Z<p>Pierros: </p>
<hr />
<div>Review transmitter suggestion</div>Pierroshttps://wiki.satnogs.org/index.php?title=SatNOGS_DB/Contribute&diff=3654SatNOGS DB/Contribute2020-08-14T10:38:53Z<p>Pierros: Redirected page to SatNOGS DB#Contribute</p>
<hr />
<div>#REDIRECT [[SatNOGS DB#Contribute]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=File:SatNOGS_DB_front_page.png&diff=3653File:SatNOGS DB front page.png2020-08-14T10:37:31Z<p>Pierros: </p>
<hr />
<div>SatNOGS DB front page</div>Pierroshttps://wiki.satnogs.org/index.php?title=SatNOGS_DB/API&diff=3652SatNOGS DB/API2020-08-14T10:35:26Z<p>Pierros: Created page with "The API of SatNOGS DB is accessible under https://db.satnogs.org/api/ Settings/ API key option on profile menu For certain functions you need an..."</p>
<hr />
<div>The API of SatNOGS DB is accessible under https://db.satnogs.org/api/<br />
[[File:Db-api-key.png|thumb|Settings/ API key option on profile menu]]<br />
For certain functions you need an API key that can be obtained by:<br />
<br />
# Register an account <br />
# Login to db.satnogs.org<br />
# Click on your profile picture top right<br />
# Click on Settings/API Key<br />
# Obtain your API key <br /></div>Pierroshttps://wiki.satnogs.org/index.php?title=File:Db-api-key.png&diff=3651File:Db-api-key.png2020-08-14T10:34:21Z<p>Pierros: </p>
<hr />
<div>db-api-key</div>Pierroshttps://wiki.satnogs.org/index.php?title=Main_Page&diff=3643Main Page2020-08-06T16:03:28Z<p>Pierros: </p>
<hr />
<div><p>__NOTOC__</p><br />
[[File:SatNOGS_explanation.png|right|300x300px]][[File:Station-1000.jpg|alt=S-Band dish on AZ/EL rotator.|right|thumb|Ground Station with S-Band dish on AZ/EL rotator. [https://network.satnogs.org/stations/1000 SatNOGS Station #1000]]]<p><big>[https://satnogs.org SatNOGS]</big> is an integral part of the [https://libre.space <big>Libre Space Foundation</big>]. The project aims to build a global network of satellite ground stations. It is designed as an open source participatory project based on the users operating a ground station that is accessed via a web page for all of the network users. A basic ground station can be made up of commercial off the shelf components that are commonly available with a static [[Omnidirectional Station How To|omnidirectional antenna]], to more complex stations with multiple movable antennas.</p><br />
[[File:AZ EL Ground Station.png|alt=AZ/EL Ground Station with VHF and UHF Antennas|left|thumb|Yaesu G-5500 Az/El Rotator w/ M2 VHF/UHF Antennas. [https://network.satnogs.org/stations/2 SatNOGS Station #2]]]<br />
<p>If you would like to build your own ground station and have limited knowledge then it is recommended that you follow a [[Omnidirectional Station How To|non-rotator build]] with a simple RTL-SDR dongle and a [[Raspberry Pi]]. This will get you on to the network quickly and allow you to start scheduling observations. There are a few choices to be made but he community are available to help if you need it. More complex, movable, antenna systems can be steered with either the SatNOGS designed rotator or a commercial unit such as the Yaesu G-5500, Spid XY or similar. It is recommended that these types of builds are for more experienced operators but there is no reason why these can not be put into operation, they just require more work.</p><br />
<p>The reference design uses a Raspberry Pi + RTL-SDR dongle + either a VHF or UHF antenna. A [[Raspberry Pi]] image is available to make software installation simpler. Much of the decision making is down to personal choice but sometimes additional hardware is needed to help filter out local noise, such as strong broadcast stations. Both the community and Matrix / IRC offer support and assistance.</p><br />
<br />
[[Category:Community]]<br />
[[Category:Build]]<br />
[[Category:Hardware]]<br />
[[Category:Software]]<br />
[[Category:Operate]]<br />
[[Category:Main]]<br />
[[Category:Develop]]<br />
[[Category:Infrastructure]]<br />
[[Category:Satellite]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=Main_Page&diff=3642Main Page2020-08-06T16:03:10Z<p>Pierros: </p>
<hr />
<div><p>__NOTOC__</p><br />
[[File:SatNOGS_explanation.png|right|300x300px]]<br />
<p><big>[https://satnogs.org SatNOGS]</big> is an integral part of the [https://libre.space <big>Libre Space Foundation</big>]. The project aims to build a global network of satellite ground stations. It is designed as an open source participatory project based on the users operating a ground station that is accessed via a web page for all of the network users. A basic ground station can be made up of commercial off the shelf components that are commonly available with a static [[Omnidirectional Station How To|omnidirectional antenna]], to more complex stations with multiple movable antennas.</p><br />
[[File:AZ EL Ground Station.png|alt=AZ/EL Ground Station with VHF and UHF Antennas|left|thumb|Yaesu G-5500 Az/El Rotator w/ M2 VHF/UHF Antennas. [https://network.satnogs.org/stations/2 SatNOGS Station #2]]]<br />
<p>If you would like to build your own ground station and have limited knowledge then it is recommended that you follow a [[Omnidirectional Station How To|non-rotator build]] with a simple RTL-SDR dongle and a [[Raspberry Pi]]. This will get you on to the network quickly and allow you to start scheduling observations. There are a few choices to be made but he community are available to help if you need it. More complex, movable, antenna systems can be steered with either the SatNOGS designed rotator or a commercial unit such as the Yaesu G-5500, Spid XY or similar. It is recommended that these types of builds are for more experienced operators but there is no reason why these can not be put into operation, they just require more work.</p><br />
<p>The reference design uses a Raspberry Pi + RTL-SDR dongle + either a VHF or UHF antenna. A [[Raspberry Pi]] image is available to make software installation simpler. Much of the decision making is down to personal choice but sometimes additional hardware is needed to help filter out local noise, such as strong broadcast stations. Both the community and Matrix / IRC offer support and assistance.</p><br />
<br />
[[File:Station-1000.jpg|alt=S-Band dish on AZ/EL rotator.|right|thumb|Ground Station with S-Band dish on AZ/EL rotator. [https://network.satnogs.org/stations/1000 SatNOGS Station #1000]]]<br />
<br />
[[Category:Community]]<br />
[[Category:Build]]<br />
[[Category:Hardware]]<br />
[[Category:Software]]<br />
[[Category:Operate]]<br />
[[Category:Main]]<br />
[[Category:Develop]]<br />
[[Category:Infrastructure]]<br />
[[Category:Satellite]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=File:Station-1000.jpg&diff=3641File:Station-1000.jpg2020-08-06T16:02:33Z<p>Pierros: </p>
<hr />
<div></div>Pierroshttps://wiki.satnogs.org/index.php?title=MediaWiki:Sidebar&diff=3640MediaWiki:Sidebar2020-08-06T15:58:01Z<p>Pierros: </p>
<hr />
<div>* Build<br />
** Build|[Station] Build a Ground Station<br />
** Raspberry_Pi|[Station] Install a Raspberry Pi<br />
** SatNOGS_Client_Setup|[Station] Configure/Update your Station<br />
** Omnidirectional_Station_How_To|[Station] Omnidirectional Howto<br />
** Radio|SDR Support<br />
** Troubleshooting|Client Troubleshooting<br />
* Operate<br />
** Satellite_Operator_Guide|Add your Mission<br />
** Operation|Managing Observations<br />
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets<br />
** Telemetry_Dashboards|Telemetry Dashboards<br />
** :Category:RF Modes|RF Modes<br />
* Contribute<br />
** Get_Started|Get Started<br />
** SatNOGS_DB|Crowd-Sourced Satellite Info<br />
** Software_contribution|Software Contribution<br />
** Server_Development_Environment|Server Development Environment<br />
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module<br />
** SatNOGS_Client_Development|SatNOGS Client Development<br />
** Adding_a_new_data_decoder|Adding a new data decoder<br />
** Academic_Papers|Academic Papers citing SatNOGS<br />
** Provide_documentation|Provide Documentation<br />
** SatNOGS_Operations_Manual|SatNOGS Operations Manual<br />
* Learn<br />
** Rotators|Rotators<br />
** Antennas|Antennas<br />
** Understanding_satnogs-flowgraphs| SatNOGS Flowgraphs<br />
** SDR_Setup| SatNOGS SDR setup<br />
** Glossary|Glossary<br />
* Contact<br />
** Get_In_Touch|Get In Touch<br />
** https://community.libre.space|Forums<br />
** Press|Press<br />
* Links<br />
** https://db.satnogs.org|SatNOGS DB<br />
** https://network.satnogs.org|SatNOGS Network<br />
** https://dashboard.satnogs.org|SatNOGS Dashboard<br />
** https://community.libre.space|SatNOGS Forums<br />
** https://libre.space|Libre Space Foundation<br />
** https://status.libre.space|System Status<br />
* SEARCH</div>Pierroshttps://wiki.satnogs.org/index.php?title=MediaWiki:Sidebar&diff=3639MediaWiki:Sidebar2020-08-06T08:45:19Z<p>Pierros: </p>
<hr />
<div>* Understand<br />
** Rotators|Rotators<br />
** Antennas|Antennas<br />
** Understanding_satnogs-flowgraphs| SatNOGS Flowgraphs<br />
** SDR_Setup| SatNOGS SDR setup<br />
** Glossary|Glossary<br />
* Build<br />
** Build|[Station] Build a Ground Station<br />
** Raspberry_Pi|[Station] Install a Raspberry Pi<br />
** SatNOGS_Client_Setup|[Station] Configure/Update your Station<br />
** Omnidirectional_Station_How_To|[Station] Omnidirectional Howto<br />
** Radio|SDR Support<br />
** Troubleshooting|Client Troubleshooting<br />
* Operate<br />
** Satellite_Operator_Guide|Add your Mission<br />
** Operation|Managing Observations<br />
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets<br />
** Telemetry_Dashboards|Telemetry Dashboards<br />
** :Category:RF Modes|RF Modes<br />
* Contribute<br />
** Get_Started|Get Started<br />
** SatNOGS_DB|Crowd-Sourced Satellite Info<br />
** Software_contribution|Software Contribution<br />
** Server_Development_Environment|Server Development Environment<br />
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module<br />
** SatNOGS_Client_Development|SatNOGS Client Development<br />
** Adding_a_new_data_decoder|Adding a new data decoder<br />
** Academic_Papers|Academic Papers citing SatNOGS<br />
** Provide_documentation|Provide Documentation<br />
** SatNOGS_Operations_Manual|SatNOGS Operations Manual<br />
* Contact<br />
** Get_In_Touch|Get In Touch<br />
** https://community.libre.space|Forums<br />
** Press|Press<br />
* Links<br />
** https://db.satnogs.org|SatNOGS DB<br />
** https://network.satnogs.org|SatNOGS Network<br />
** https://dashboard.satnogs.org|SatNOGS Dashboard<br />
** https://community.libre.space|SatNOGS Forums<br />
** https://libre.space|Libre Space Foundation<br />
** https://status.libre.space|System Status<br />
* SEARCH</div>Pierroshttps://wiki.satnogs.org/index.php?title=MediaWiki:Sidebar&diff=3638MediaWiki:Sidebar2020-08-06T08:43:09Z<p>Pierros: add sdr setup</p>
<hr />
<div>* Understand<br />
** Rotators|Rotators<br />
** Antennas|Antennas<br />
** Understanding_satnogs-flowgraphs| SatNOGS Flowgraphs<br />
** SDR_Setup| SatNOGS SDR setup<br />
* Build<br />
** Build|[Station] Build a Ground Station<br />
** Raspberry_Pi|[Station] Install a Raspberry Pi<br />
** SatNOGS_Client_Setup|[Station] Configure/Update your Station<br />
** Omnidirectional_Station_How_To|[Station] Omnidirectional Howto<br />
** Radio|SDR Support<br />
** Troubleshooting|Client Troubleshooting<br />
* Operate<br />
** Satellite_Operator_Guide|Add your Mission<br />
** Operation|Managing Observations<br />
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets<br />
** Telemetry_Dashboards|Telemetry Dashboards<br />
** :Category:RF Modes|RF Modes<br />
* Contribute<br />
** Get_Started|Get Started<br />
** SatNOGS_DB|Crowd-Sourced Satellite Info<br />
** Software_contribution|Software Contribution<br />
** Server_Development_Environment|Server Development Environment<br />
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module<br />
** SatNOGS_Client_Development|SatNOGS Client Development<br />
** Adding_a_new_data_decoder|Adding a new data decoder<br />
** Academic_Papers|Academic Papers citing SatNOGS<br />
** Provide_documentation|Provide Documentation<br />
** SatNOGS_Operations_Manual|SatNOGS Operations Manual<br />
* Contact<br />
** Get_In_Touch|Get In Touch<br />
** https://community.libre.space|Forums<br />
** Press|Press<br />
* Links<br />
** https://db.satnogs.org|SatNOGS DB<br />
** https://network.satnogs.org|SatNOGS Network<br />
** https://dashboard.satnogs.org|SatNOGS Dashboard<br />
** https://community.libre.space|SatNOGS Forums<br />
** https://libre.space|Libre Space Foundation<br />
** https://status.libre.space|System Status<br />
* SEARCH</div>Pierroshttps://wiki.satnogs.org/index.php?title=Rotators&diff=3637Rotators2020-08-06T08:40:51Z<p>Pierros: </p>
<hr />
<div>__NOTOC__<br />
<br />
The SatNOGS Client uses [http://hamlib.sourceforge.net/ hamlib] to speak to a rotator. With this, we are able to support almost any commercially available rotator, and have the flexibility to support home built rotators that implement protocols like [https://www.mustbeart.com/software/easycomm.txt EasyComm] or Yaesu GS-232.<br />
<br />
In this [https://wiki.satnogs.org/Review_of_Commercial_Rotator wiki page] you could read a review about the AZ/EL rotators, which are popular in HAM community.<br />
<br />
If you would rather start with a stationary antenna setup (no rotator), see our [[Omnidirectional Station How To|omnidirectional guide]].<br />
<br />
{| class="wikitable" style="width: 100%;"<br />
! style="width: 49%" |<br />
===Commercial Rotators [[Review of Commercial Rotators|(review)]]===<br />
!<br />
! style="width: 49%" |<br />
===Homebuilt Rotators===<br />
|-<br />
|[[File:G5500.jpg|left|frameless|100x100px]]<br />
<br />
====[[G-5500|Yaesu G-5500]]====<br />
The G-5500 is a common rotator for amateur radio AZ/EL applications. The SatNOGS client interfaces with this rotator via the hamlib library. While a commercial computer interface is available from Yaesu, the SatNOGS project provides an open hardware design that is much cheaper. <br />
<br />
*[[G-5500|G-5500 SatNOGS Wiki page]]<br />
*G-5500 Arduino interface<br />
*[https://www.yaesu.com/indexVS.cfm?cmd=DisplayProducts&ProdCatID=104&encProdID=79A89CEC477AA3B819EE02831F3FD5B8 Yaesu G-5500 Product link]<br />
|<br />
|[[File:30033213301 ef78e64120 k.jpg|left|frameless|133x133px]]<br />
<br />
====[[SatNOGS Rotator v2]]====<br />
The v2 rotator is not recommended, as v3 provides much greater strength and durability. These docs remain for historical purposes.<br />
<br />
*[[SatNOGS Rotator v2|SatNOGS v2 Wiki page]]<br />
*[https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v2 SatNOGS v2 source code]<br />
|-<br />
|[[File:Portable Rotation.jpg|left|frameless|100x100px]]<br />
<br />
====Portable Rotation AZ/EL====<br />
Docs to be written, but we do have successful stations using this rotator with the SatNOGS client.<br />
<br />
*[http://portablerotation.com/shop/azel-portable-rotor-system/ Portable Rotation product link]<br />
|<br />
|[[File:V3.jpg|left|frameless|100x100px]]<br />
<br />
====[[SatNOGS Rotator v3]]====<br />
The v3 rotator is a complete overhaul on the v2 design. The 2020 slotted extrusion frame and larger gears provide for a stronger rotator with greater wind loading.<br />
<br />
*[[SatNOGS Rotator v3|SatNOGS v3 Wiki page]]<br />
*[https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v3.0 SatNOGS v3 source code]<br />
|-<br />
|[[File:Alfa Spid.jpg|left|frameless|133x133px]]<br />
<br />
====Alfa Spid X-Y====<br />
<br />
<br />
*[[SPID Big RAS|Alfa Spid SatNOGS Wiki page]]<br />
*[http://alfaradio.ca/alfaspid-azel.html Alfa Spid product link]<br />
|<br />
|<br />
==== [[Metal antenna rotator|Metal Antenna Rotator]] ====<br />
A simple metal antenna rotator by User:Jujun<br />
<br /><br />
|-<br />
|[[File:Dwingleloo.png|left|frameless|100x100px]]<br />
<br />
====Dwingeloo Radio Observatory====<br />
(okay, you're not likely to keep a deep space observatory on the network, but it has been done!)<br />
<br />
*[https://www.youtube.com/watch?v=wGJh139EDfk Video of the observatory in action on SatNOGS (YouTube)]<br />
*[https://network.satnogs.org/stations/384/ Dwingeloo on SatNOGS network]<br />
*[[wikipedia:Dwingeloo_Radio_Observatory|About the Dwingeloo Radio Observatory (wikipedia)]]<br />
|<br />
|<br />
|}<br />
<br />
[[Category:Hardware]]<br />
[[ Category:Rotator ]]<br />
__NOEDITSECTION__</div>Pierroshttps://wiki.satnogs.org/index.php?title=Build&diff=3636Build2020-08-06T08:39:23Z<p>Pierros: </p>
<hr />
<div>__NOTOC__<br />
==Introduction==<br />
<br />
Building a ground station need not be complicated. There are a few things to consider when working out what it is you are going to do. Choices such as the desire to have a fixed or steerable ground station will play a big part in the amount of equipment needed and the time taken as well as the complexity of any build. If you are new to this and a little unsure then a fixed (no rotator) option is a good choice. If you fancy a challenge and want to pick out the weakest signals then the steerable ground station might be what you are after. There is more detail in the [[Ground Stations]] page<br />
<br />
The illustration below sets out the various major components to give an idea as to what is commonly used.<br />
<br />
==Options for Ground Stations==<br />
<br />
A satellite ground station is made up from different parts. The following diagram can help you select your setup based on your needs and/or your existing setup.<br />
<br />
[[File:Satnogs_imagemap.png|center]]<br />
<br />
Here are some links explaining the different options:<br />
<br />
{| class="wikitable" style="margin: 0 auto;"<br />
!Platform<br />
!Controller<br />
!Rotator<br />
!Radio<br />
!Antenna<br />
|-<br />
|[[Raspberry_Pi|Raspberry Pi]]<br />
|[[SatNOGS Rotator Controller|SatNOGS Controller]]<br />
|[[SatNOGS_Rotator_v3|SatNOGS Rotator]]<br />
|[[Radio#SDR|SDR]]<br />
|[[Antennas|Yagi]]<br />
|-<br />
|[[SatNOGS_Client_Ansible|Debian system]]<br />
|[http://spid.net.pl/en/rot2prog-2/ Rot2Prog]<br />
|[[SPID Big RAS]]<br />
|<br />
|[[Antennas|Helical]]<br />
|-<br />
|[[Linux Desktop]]<br />
|[[G-5500|lsf-g5500]]<br />
|[[G-5500|Yaesu G5500]]<br />
|<br />
|[[Antennas|Vertical]]<br />
|-<br />
|[[Fedora Installation|Linux Fedora (old)]]<br />
|[https://wiki.satnogs.org/SatNOGS_Arduino_Uno/CNC_Shield_Based_Rotator_Controller Arduino UNO CNC Shield based controller]<br />
|[[No rotator]]<br />
|<br />
|[[Antennas|Cross-Yagi]]<br />
|-<br />
|<br />
|[https://community.libre.space/t/ramps-1-4-board-for-satnogs-rotator/3386 RAMPS 1.4 Board for SatNOGS Rotator]<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
{{Message|Use the above table to select your setup. E.g. RPi3 > Yaesu G550 > SDR > UHF helical & VHF Cross Yagi}}<br />
<br />
==How do I pick?==<br />
<br />
'''Client''': The Raspberry Pi is the reference platform for SatNOGS, and is currently the option that has the best support from the community. Certain SDRs may benefit from a more powerful CPU, like what you'd find in a desktop machine; however, currently you'll need to set that up on your own.<br />
<br />
'''Rotator''': A rotator, like the [[SatNOGS_Rotator_v3|SatNOGS Rotator v3]], will allow your antenna to follow satellites as they move across the sky, and thus pick up fainter signals. But if you want to get started quickly, or don't have the hardware skills to build your own, you can still pick up stronger signals (the ISS, NOAA and Meteor weather satellites) with a [[No_rotator|no-rotator]] setup. If you already have [https://github.com/Hamlib/Hamlib/wiki/Supported-Rotators a rotator supported by rotctl], you can use that.<br />
<br />
'''Signal Reception''': The reference radio for SatNOGS is the [https://www.rtl-sdr.com RTL-SDR v3], but other latest-generation SDRs like the [http://www.nooelec.com/store/nesdr-smart-sdr.html NooElec NESDR SMart] should work as well. Higher-end SDRs should work as well, but can get a bit expensive. Alternately, [https://sourceforge.net/p/hamlib/wiki/Supported%20Radios/ any radio supported by rigctl] should work.<br />
<br />
Amplification is generally done by a low noise amplifier, or LNA. There are multiple options:<br />
<br />
*A wide-band LNA next to your SDR (see [http://lna4all.blogspot.com/ LNA4ALL], [https://iz7boj.wordpress.com/2019/04/11/spf5189z-lna-measurements-on-vna/ SPF5189] and similar)<br />
*A band specific (or two) pre-amplifiers next to your antennas ([http://www.wimo.com/mast-preamplifier_e.html example])<br />
*No amplification at all...just pump the gain of your SDR. (This is not recommended for the rtl-sdr.)<br />
<br />
'''Antenna''': Stationary antennas (eg: [https://en.wikipedia.org/wiki/Turnstile_antenna Turnstile], [https://community.libre.space/t/parasitic-lindenblad-on-uhf/1128/2 Lindenblad]) will be easy to build and mount, as they won't require rotator hardware. They will let you receive stronger broadcasts, like NOAA weather satellites and ISS broadcasts, but may not work for receiving fainter cubesat broadcasts. Directional antennas (eg: Yagis, Helicals) can be more complicated to build, but will also require a rotator to track satellites across the sky. The advantage is that they will let you pick up fainter broadcasts from cubesats or ham radio satellites.<br />
<br />
==Next steps==<br />
<br />
Once you have a ground station ready, you should go ahead and operate it! More info can be found on the [[Operation]] wiki page.<br />
<br />
[[Category:Build]]<br />
[[Category:Hardware]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=MediaWiki:Sidebar&diff=3635MediaWiki:Sidebar2020-08-06T08:38:07Z<p>Pierros: </p>
<hr />
<div>* Understand<br />
** Rotators|Rotators<br />
** Antennas|Antennas<br />
** Understanding_satnogs-flowgraphs| SatNOGS Flowgraphs<br />
* Build<br />
** Build|[Station] Build a Ground Station<br />
** Raspberry_Pi|[Station] Install a Raspberry Pi<br />
** SatNOGS_Client_Setup|[Station] Configure/Update your Station<br />
** Omnidirectional_Station_How_To|[Station] Omnidirectional Howto<br />
** Radio|SDR Support<br />
** Troubleshooting|Client Troubleshooting<br />
* Operate<br />
** Satellite_Operator_Guide|Add your Mission<br />
** Operation|Managing Observations<br />
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets<br />
** Telemetry_Dashboards|Telemetry Dashboards<br />
** :Category:RF Modes|RF Modes<br />
* Contribute<br />
** Get_Started|Get Started<br />
** SatNOGS_DB|Crowd-Sourced Satellite Info<br />
** Software_contribution|Software Contribution<br />
** Server_Development_Environment|Server Development Environment<br />
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module<br />
** SatNOGS_Client_Development|SatNOGS Client Development<br />
** Adding_a_new_data_decoder|Adding a new data decoder<br />
** Academic_Papers|Academic Papers citing SatNOGS<br />
** Provide_documentation|Provide Documentation<br />
** SatNOGS_Operations_Manual|SatNOGS Operations Manual<br />
* Contact<br />
** Get_In_Touch|Get In Touch<br />
** https://community.libre.space|Forums<br />
** Press|Press<br />
* Links<br />
** https://db.satnogs.org|SatNOGS DB<br />
** https://network.satnogs.org|SatNOGS Network<br />
** https://dashboard.satnogs.org|SatNOGS Dashboard<br />
** https://community.libre.space|SatNOGS Forums<br />
** https://libre.space|Libre Space Foundation<br />
** https://status.libre.space|System Status<br />
* SEARCH</div>Pierroshttps://wiki.satnogs.org/index.php?title=MediaWiki:Sidebar&diff=3634MediaWiki:Sidebar2020-08-06T08:37:52Z<p>Pierros: </p>
<hr />
<div>* Understand<br />
** Rotators|Rotators<br />
** Antennas|Antennas<br />
** Understanding_satnogs-flowgraphs| SatNOGS Flowgraphs<br />
* Build<br />
** Build|[Station] Build a Ground Station<br />
** Raspberry_Pi|[Station] Install a Raspberry Pi<br />
** SatNOGS_Client_Setup|[Station] Configure/Update your Station<br />
** Omnidirectional_Station_How_To|[Station] Omnidirectional Howto<br />
** Radio|SDR Support<br />
** Troubleshooting|Client Troubleshooting<br />
* Operate<br />
** Satellite_Operator_Guide|Add your Mission<br />
** Operation|Managing Observations<br />
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets<br />
** Telemetry_Dashboards|Telemetry Dashboards<br />
** :Category:RF Modes|RF Modes<br />
* Contribute<br />
** Get_Started|Get Started<br />
** SatNOGS_DB|Crowd-Sourced Satellite Info<br />
** Software_contribution|Software Contribution<br />
** Server_Development_Environment|Server Development Environment<br />
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module<br />
** SatNOGS_Client_Development|SatNOGS Client Development<br />
** Adding_a_new_data_decoder|Adding a new data decoder<br />
** Academic_Papers|Academic Papers citing SatNOGS<br />
** Provide_documentation|Provide Documentation<br />
** SatNOGS_Operations_Manual|SatNOGS Operations Manual<br />
* Contact<br />
** Get_In_Touch|Get In Touch<br />
** https://community.libre.space|Forums<br />
** Press<br />
* Links<br />
** https://db.satnogs.org|SatNOGS DB<br />
** https://network.satnogs.org|SatNOGS Network<br />
** https://dashboard.satnogs.org|SatNOGS Dashboard<br />
** https://community.libre.space|SatNOGS Forums<br />
** https://libre.space|Libre Space Foundation<br />
** https://status.libre.space|System Status<br />
* SEARCH</div>Pierroshttps://wiki.satnogs.org/index.php?title=Press&diff=3633Press2020-08-06T08:37:25Z<p>Pierros: </p>
<hr />
<div>Please send any press inquiries to press (at) satnogs (dot) org.<br />
<br />
There is a [https://satnogs.org/wp-content/uploads/2015/01/SatNOGS-Presskit-201508.zip SatNOGS Press Kit available].<br />
<br />
====See also====<br />
<br />
*[[Get In Touch]]<br />
<br />
[[Category:Community]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=Rotators&diff=3632Rotators2020-08-06T08:36:02Z<p>Pierros: add review link</p>
<hr />
<div>__NOTOC__<br />
<br />
The SatNOGS Client uses [http://hamlib.sourceforge.net/ hamlib] to speak to a rotator. With this, we are able to support almost any commercially available rotator, and have the flexibility to support home built rotators that implement protocols like [https://www.mustbeart.com/software/easycomm.txt EasyComm] or Yaesu GS-232.<br />
<br />
In this [https://wiki.satnogs.org/Review_of_Commercial_Rotator wiki page] you could read a review about the AZ/EL rotators, which are popular in HAM community.<br />
<br />
If you would rather start with a stationary antenna setup (no rotator), see our [[Omnidirectional Station How To|omnidirectional guide]].<br />
<br />
{| class="wikitable" style="width: 100%;"<br />
! style="width: 49%" |<br />
===Commercial Rotators [[Review of Commercial Rotators|(review)]]===<br />
!<br />
! style="width: 49%" |<br />
===Homebuilt Rotators===<br />
|-<br />
|[[File:G5500.jpg|left|frameless|100x100px]]<br />
<br />
====[[G-5500|Yaesu G-5500]]====<br />
The G-5500 is a common rotator for amateur radio AZ/EL applications. The SatNOGS client interfaces with this rotator via the hamlib library. While a commercial computer interface is available from Yaesu, the SatNOGS project provides an open hardware design that is much cheaper. <br />
<br />
*[[G-5500|G-5500 SatNOGS Wiki page]]<br />
*G-5500 Arduino interface<br />
*[https://www.yaesu.com/indexVS.cfm?cmd=DisplayProducts&ProdCatID=104&encProdID=79A89CEC477AA3B819EE02831F3FD5B8 Yaesu G-5500 Product link]<br />
|<br />
|[[File:30033213301 ef78e64120 k.jpg|left|frameless|133x133px]]<br />
<br />
====[[SatNOGS Rotator v2]]====<br />
The v2 rotator is not recommended, as v3 provides much greater strength and durability. These docs remain for historical purposes.<br />
<br />
*[[SatNOGS Rotator v2|SatNOGS v2 Wiki page]]<br />
*[https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v2 SatNOGS v2 source code]<br />
|-<br />
|[[File:Portable Rotation.jpg|left|frameless|100x100px]]<br />
<br />
====Portable Rotation AZ/EL====<br />
Docs to be written, but we do have successful stations using this rotator with the SatNOGS client.<br />
<br />
*[http://portablerotation.com/shop/azel-portable-rotor-system/ Portable Rotation product link]<br />
|<br />
|[[File:V3.jpg|left|frameless|100x100px]]<br />
<br />
====[[SatNOGS Rotator v3]]====<br />
The v3 rotator is a complete overhaul on the v2 design. The 2020 slotted extrusion frame and larger gears provide for a stronger rotator with greater wind loading.<br />
<br />
*[[SatNOGS Rotator v3|SatNOGS v3 Wiki page]]<br />
*[https://gitlab.com/librespacefoundation/satnogs/satnogs-rotator/tree/v3.0 SatNOGS v3 source code]<br />
|-<br />
|[[File:Alfa Spid.jpg|left|frameless|133x133px]]<br />
<br />
====Alfa Spid X-Y====<br />
<br />
<br />
*[[SPID Big RAS|Alfa Spid SatNOGS Wiki page]]<br />
*[http://alfaradio.ca/alfaspid-azel.html Alfa Spid product link]<br />
|<br />
|<br />
|-<br />
|[[File:Dwingleloo.png|left|frameless|100x100px]]<br />
<br />
====Dwingeloo Radio Observatory====<br />
(okay, you're not likely to keep a deep space observatory on the network, but it has been done!)<br />
<br />
*[https://www.youtube.com/watch?v=wGJh139EDfk Video of the observatory in action on SatNOGS (YouTube)]<br />
*[https://network.satnogs.org/stations/384/ Dwingeloo on SatNOGS network]<br />
*[[wikipedia:Dwingeloo_Radio_Observatory|About the Dwingeloo Radio Observatory (wikipedia)]]<br />
|<br />
|<br />
|}<br />
<br />
[[Category:Hardware]]<br />
[[ Category:Rotator ]]<br />
__NOEDITSECTION__</div>Pierroshttps://wiki.satnogs.org/index.php?title=Review_of_Commercial_Rotators&diff=3630Review of Commercial Rotators2020-08-06T08:34:51Z<p>Pierros: Pierros moved page Review of Commercial Rotator to Review of Commercial Rotators</p>
<hr />
<div>{{DISPLAYTITLE:Review of Commercial Rotators}}<br />
<br />
==Introduction==<br />
<br />
The existing rotator controllers are old-fashioned and use obsolete technology, either in hardware or in software. Almost all the motor drivers are based on electromechanical switches like relays. This introduces limits to the usefulness in connection with satellite observations, and cause reduced accuracy in the movements of the rotator. In the following, we will be reviewing the three most popular commercially available rotator systems in the ham radio community:<br />
<br />
*[https://www.yaesu.com/indexVS.cfm?cmd=DisplayProducts&ProdCatID=104&encProdID=79A89CEC477AA3B819EE02831F3FD5B8 Yaesu G-5500]<br />
*[http://www.alfaradio.ca/ SPID rotators]<br />
**[https://www.rfhamdesign.com/products/spid-antenna--rotator/ras-az--el-rotator/index.php RAS]<br />
**[https://www.rfhamdesign.com/products/spid-antenna--rotator/big-ras-az--el-rotor/index.php BIG-RAS]<br />
*SPX rotators,<br />
**[http://www.rfhamdesign.com/products/spx-antenna-rotators/spx-01-az--el/index.php SPX-01]<br />
**[http://www.rfhamdesign.com/products/spx-antenna-rotators/spx-02-az--el/index.php SPX-02]<br />
**[http://www.rfhamdesign.com/products/spx-antenna-rotators/spx-03-az--el/index.php SPX-03]<br />
<br />
==Yaesu G-5500==<br />
<br />
===Electronics===<br />
<br />
[https://www.yaesu.com/indexVS.cfm?cmd=DisplayProducts&ProdCatID=104&encProdID=79A89CEC477AA3B819EE02831F3FD5B8 Yaesu G-5500] is an AZ/EL rotator. The [http://www.radiomanual.info/schemi/ACC_rotator/Yaesu_G-5500_user.pdf datasheet] states that it has AC motors (26V@2.8A, specifications of transformer for both motors), potentiometer (not multiturn) for position feedback which are operated with +6V, and the control loop is implemented with analog IC's (comparators and op-amps). Also, the system has end-stops in both axes in both directions (min-max), that immediately cut off the current to the motors. The connection to the client is implemented via a rotator interface, for example an [https://gitlab.com/librespacefoundation/satnogs/g5500-ardushield ardushield] that runs [https://github.com/ppapadeas/k3ng_rotator_controller/tree/lsf-g5500 k3ng rotator firmware]. The cost of the entire system is ~750$ including an analog controller.<br />
<br />
Useful links:<br />
<br />
*[https://kb5wia.blogspot.com/2012/03/yaesu-g5500-rotator-motor-repair.html Motor Repair]<br />
<br />
[[File:Yaesug5500-electronics-1.jpeg|thumb|center|300x300px|alt=|Yaesu G5500 - Controller]]<br />
<br />
===Mechanical===<br />
<br />
The gear box of the rotator it is a spur gear box. Almost all the gears are made from laser cut sheet metal, and the output gear is a stack of laser cut sheet metal gears. Another interesting thing is the brake system, which is a torsional spring in the motor axis, that blocks the movement from output to input. When a torque is applied from output to input, the torsional spring "opens" and blocks the rotation. A mechanical failure in of one brackets that mount the pins of the gears was observed in [https://network.satnogs.org/stations/6/ station 6] after a lot of observations (the oval hole). This problem is caused by the antennas being back-mounted without a counterbalance.<br />
<br />
<gallery widths="300" heights="300" perrow="2"><br />
File:Yaesug5500-mech-1.jpeg|Yaesu G5500, Gear box<br />
File:Yaesug5500-mech-2.jpeg|Yaesu G5500, Mechanical failure<br />
</gallery><br />
<br />
===Alternative Rotator Controllers===<br />
<br />
A list of available digital controllers:<br />
<br />
*[https://www.greenheronengineering.com/proddetail.php?prod=RT-21azel RT-21 Azimuth/Elevation, Green Heron Engineering LLC], 889$<br />
*[http://www.af6sa.com/projects/AZ_EL_Rotor.html, AZ-EL USB Rotor Controller AE-21]<br />
*[http://www.arrl.org/files/file/ETP/Satellite%20Tracker%20Interface%20ver%201_2.pdf DIY solution from ARRL]<br />
<br />
==SPID rotators==<br />
<br />
This company it has two AZ/EL models:<br />
<br />
*[https://www.rfhamdesign.com/products/spid-antenna--rotator/ras-az--el-rotator/index.php RAS]<br />
*[https://www.rfhamdesign.com/products/spid-antenna--rotator/big-ras-az--el-rotor/index.php BIG-RAS]<br />
<br />
===Electronics===<br />
<br />
Both the models are using DC motors, according to the datasheets, [https://www.rfhamdesign.com/downloads/spid-bigras-specifications.pdf BIG-RAS] and [https://www.rfhamdesign.com/downloads/spid-ras-specifications.pdf RAS]. The power consumption for both rotators is 12V@6-10A or 18V@6-11A. For the position sensor, a reed switch is used, one in each axis. This sensor is mounted in the first stage of a worm gear box (in total two worm gear boxes), with a total of 6 magnets that produce pulses with Vp-p according to the Vcc of the reed switch.<br />
<br />
<gallery widths="300" heights="300" perrow="3"><br />
File:Ras-reedswitch.jpeg| RAS, position sensor<br />
File:Ras-magnets.jpeg| RAS, magnets of position sensor<br />
File:Ras-pulses.jpeg| RAS, pulses of position sensor (reed switch)<br />
</gallery> <br />
<br />
It seems that the encoder is relative, so when the system starts, it is programmed for the zero position. When the system loses power, the rotator controller knows the last position, it stores the last position in a non-volatile memory.<br />
Also the system has two hard stops in the elevation axis, that limits the rotation between 0-180 deg. These switches immediately cut off the current to the elevation motor. There is no end stop in the azimuth axis.<br />
<br />
[[File:Ras-endstop.jpeg|thumb|center|300x300px|alt=|RAS, end-stops in elevation axis]]<br />
<br />
The default rotator controller is [https://www.rfhamdesign.com/downloads/spid-ras-specifications.pdf Rot2Prog], the motor driver consists of relays. The interface with the client is done with [Hamlib](https://hamlib.github.io/) via a USB. A note here: The cable is USB-A male to USB-A male, which is weird. Two rectifier bridges are used for protection of the board from the currents of the DC motors. The cost of Rot2Prog is ~250$.<br />
<br />
[[File:Ras-rotatorcontroller.jpeg|thumb|center|300x300px|alt=|RAS, Default rotator controller]]<br />
<br />
The [https://www.rfhamdesign.com/downloads/spid-ras-specifications.pdf datasheet of RAS] refers to a parameter called [https://en.wikipedia.org/wiki/Mean_time_between_failures MTBF] which is the mean time between failures. For the rotator controller is 15000 hours @ -5 to +40°C. For a system that is connected to the [https://network.satnogs.org/ SatNOGS network], i.e.:<br />
<br />
*in 1h, at least 2 observations of 15min each<br />
*in 15000 hours, 30000 observations<br />
*which means almost 2 years of operation<br />
<br />
But how are the relays worked?<br />
<br />
===Mechanical===<br />
Both of the rotators consist of two stages of worm gear boxes. The second stage (the output) take all the load. In this system, the brake mechanism is the two stage worm gear box (big gear ratio and also the lead angle of worm gear). The cost for RAS with Rot2Prog controller is ~1200$, for BIG-RAS with Rot2Prog controller is ~1600$.<br />
<br />
<gallery widths="300" heights="300" perrow="2"><br />
| RAS, position sensor<br />
File:Ras-magnets.jpeg| RAS, First stage of worm gear<br />
File:Ras-wormgear.jpg| RAS, Second (output) stage of worm gear<br />
</gallery> <br />
<br />
===Alternative Rotator Controllers===<br />
<br />
A list of available digital controllers:<br />
<br />
*[https://www.greenheronengineering.com/proddetail.php?prod=RT-21azel RT-21 Azimuth/Elevation, Green Heron Engineering LLC], 889$. This has a nice feature: "Allows different Azimuth and Elevation rotators from any manufacturer provided they both use either AC or DC motors. (Example: We can configure the Azimuth to use an OR-2800 and the Elevation to use a DC motor linear actuator. OR, the Azimuth to use a T2X, and the Elevation to use a Yaesu G-550)"<br />
*[http://www.rfhamdesign.com/downloads/spid-ras_hr-specifications.pdf MD-01/02 HR], which is a high resolution edition rotator controller, with resolution of 0.1875 deg. Instead of using reed switches in the first stage of the worm gear box, it uses a hall effect sensor. Again, the motor driver consist of electromechanical switches, as shown in the picture on [http://www.rfhamdesign.com/downloads/spid-ras_hr-specifications.pdf page 3 of the datasheet]. This controller also supports soft-start functionality (PWM control), but only when the power supply is higher than 20V, [https://community.libre.space/t/review-of-commercial-rotator-controllers/3428/7 according to this post].<br />
<br />
<br />
The cost of this controller (only) is calculated:<br />
<br />
*RAS/HR, RAS rotator and MD-02/HR controller is ~[1435E](http://www.rfhamdesign.com/products/spid-hr-antenna-rotators/ras-hr-az--el-rotor/index.php)<br />
*only the RAS rotator costs ~900E (an estimation)<br />
<br />
so the cost of MD-02/HR is ~500E.<br />
<br />
<gallery widths="300" heights="300" perrow="2"><br />
| RAS, position sensor<br />
File:Az-El controller front G.gif| RT-21 Azimuth/Elevation, Green Heron Engineering LLC<br />
File:Rotator-controller-md.png| Rotator Controller, MD-01/02 HR<br />
</gallery> <br />
<br />
==SPX rotators==<br />
<br />
===Electronics & Mechanical===<br />
<br />
A series of AZ/EL rotators:<br />
<br />
*[http://www.rfhamdesign.com/products/spx-antenna-rotators/spx-01-az--el/index.php SPX-01]<br />
*[http://www.rfhamdesign.com/products/spx-antenna-rotators/spx-02-az--el/index.php SPX-02]<br />
*[http://www.rfhamdesign.com/products/spx-antenna-rotators/spx-03-az--el/index.php SPX-03]<br />
<br />
All of these rotators seem to be based on the same first stage worm gear box as the RAS. The second stage looks like [https://ae01.alicdn.com/kf/HTB1uzY4PVXXXXX4XXXXq6xXFXXXE/NMRV050-Speed-Ratio-50-1-Worm-Gearbox-14mm-19mm-Input-Shaft-90-Degree-Worm-Gear-Speed.jpg_640x640.jpg this] and changed according to the maximum output load (and maximum break torque). From all the datasheets, it seems that the motor needs 12-18V@3-20A or 20-24V@3-20A (max current depends on load or rotator controller, e.g. PWM control). All of these rotators use the same controllers as RAS/BIG-RAS. The motors are DC (it seems that they are the same as RAS/BIG-RAS). For position sensor, a reed switch for the standard version and a hall effect sensor for high resolution version are used. From the number of cables and from the type of controller it seems that there are no end-stops connected to the rotator controller. [https://community.libre.space/t/review-of-commercial-rotator-controllers/3428/7 This post] confirms that the SPX-01 and SPX-02 have no end stop switches on either azimuth or elevation. Also the limits are set in the controller, based on the user's cabling setup.<br />
In this system, the brake system is the double worm gear. In the specification, the rotation range is AZ/EL:360/180deg - the same as the RAS. The available rotator controllers are the same as the SPID rotators.<br />
<br />
<gallery widths="300" heights="300" perrow="2"><br />
File:Spx-wormgear.jpeg| SPX, second stage of worm gear<br />
File:Spx-station232.jpg| SPX-02 rotator, [https://network.satnogs.org/stations/232/ station 232]<br />
</gallery><br />
<br />
[[Category:Build]]<br />
[[Category:Hardware]]<br />
[[Category:Rotator]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=Review_of_Commercial_Rotator&diff=3631Review of Commercial Rotator2020-08-06T08:34:51Z<p>Pierros: Pierros moved page Review of Commercial Rotator to Review of Commercial Rotators</p>
<hr />
<div>#REDIRECT [[Review of Commercial Rotators]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=MediaWiki:Sidebar&diff=3629MediaWiki:Sidebar2020-08-06T08:33:10Z<p>Pierros: </p>
<hr />
<div>* Understand<br />
** Rotators|Rotators<br />
** Antennas|Antennas<br />
** Understanding_satnogs-flowgraphs| SatNOGS Flowgraphs<br />
* Build<br />
** Build|[Station] Build a Ground Station<br />
** Raspberry_Pi|[Station] Install a Raspberry Pi<br />
** SatNOGS_Client_Setup|[Station] Configure/Update your Station<br />
** Omnidirectional_Station_How_To|[Station] Omnidirectional Howto<br />
** Radio|SDR Support<br />
** Troubleshooting|Client Troubleshooting<br />
* Operate<br />
** Satellite_Operator_Guide|Add your Mission<br />
** Operation|Managing Observations<br />
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets<br />
** Telemetry_Dashboards|Telemetry Dashboards<br />
** :Category:RF Modes|RF Modes<br />
* Contribute<br />
** Get_Started|Get Started<br />
** SatNOGS_DB|Crowd-Sourced Satellite Info<br />
** Software_contribution|Software Contribution<br />
** Server_Development_Environment|Server Development Environment<br />
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module<br />
** SatNOGS_Client_Development|SatNOGS Client Development<br />
** Adding_a_new_data_decoder|Adding a new data decoder<br />
** Academic_Papers|Academic Papers citing SatNOGS<br />
** Provide_documentation|Provide Documentation<br />
** SatNOGS_Operations_Manual|SatNOGS Operations Manual<br />
* Contact<br />
** Get_In_Touch|Get In Touch<br />
** https://community.libre.space|Forums<br />
* Links<br />
** https://db.satnogs.org|SatNOGS DB<br />
** https://network.satnogs.org|SatNOGS Network<br />
** https://dashboard.satnogs.org|SatNOGS Dashboard<br />
** https://community.libre.space|SatNOGS Forums<br />
** https://libre.space|Libre Space Foundation<br />
** https://status.libre.space|System Status<br />
* SEARCH</div>Pierroshttps://wiki.satnogs.org/index.php?title=Understanding_satnogs-flowgraphs&diff=3627Understanding satnogs-flowgraphs2020-08-06T08:31:52Z<p>Pierros: Pierros moved page Understanding 'satnogs-flowgraphs' to Understanding satnogs-flowgraphs</p>
<hr />
<div>''I'm not entirely sure where to put this, but perhaps someone more experienced can move and link this from a sensible location. This started as a question continuing the [https://community.libre.space/t/how-to-open-satnogs-iq-dat-files/3793 How to open satnogs iq.dat files] thread but as I worked through after picking things up after initially having a problem I realised everything I'd described now magically worked! Typical. Worth documenting.''<br />
<br />
==Setting yourself up==<br />
<br />
You need GNU Radio and satnogs-flowgraphs together with its dependencies like gr-satnogs and gr-soapy. <br />
<br />
The easiest would be to have a supported distribution and do the normal installation of the binaries from repositories like the one from satnogs. In my case, I am using a virtual Ubuntu 19.10 machine grabbed from osboxes.org. Overthere, a recent GNU Radio is available from the official repository. The gr-soapy package is available from [https://github.com/pothosware/PothosCore/wiki/Ubuntu#add-ppas-to-your-system PothosCore PPA external repository]. As there are no ubuntu packages for satnogs-flowgraphs and gr-satnogs, those need to be built from the gitlab source. The [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs/-/blob/master/.gitlab-ci.yml recipe for building the Debian packages] can be adapted for Ubuntu. For gr-satnogs, that means something like this:<br />
<pre><br />
sudo apt-get -qy install gnupg libcurl4 devscripts git-buildpackage<br />
git clone https://gitlab.com/librespacefoundation/satnogs/gr-satnogs.git<br />
cd gr-satnogs<br />
sudo mk-build-deps -i -r -t "apt-get -o Debug::pkgProblemResolver=yes --no-install-recommends -y"<br />
PACKAGE_VERSION="${PACKAGE_VERSION:-$(git describe --abbrev=8 2>/dev/null | tr '-' '+' || true)}" <br />
echo $PACKAGE_VERSION # Or set it directly if not set OK<br />
dch -b -M -v "${PACKAGE_VERSION}-1" "Bump to version '${PACKAGE_VERSION}-1'" <br />
dch -r -m "" <br />
sed -i '/0001-remove-git-maint-version.patch/ d' debian/patches/series # removes that line<br />
debuild --unsigned-source --unsigned-changes --build=binary <br />
</pre><br />
If all goes well, two debian packages, libgnuradio-satnogs and gr-satnogs, are produced in the parent directory. <br />
Install them in the your system: <br />
<pre><br />
cd .. <br />
sudo dpkg --install libgnuradio-satnogs_2.1.2-1_amd64.deb gr-satnogs_2.1.2-1_amd64.deb <br />
</pre><br />
Then, proceed similarly for satnogs-flowgraphs.<br />
<br />
==Storing an IQ recording==<br />
<br />
There are options in satnogs-setup under Advanced > Radio to store IQ files:<br />
<br />
*ENABLE_IQ_DUMP: Enable IQ dump<br />
*IQ_DUMP_FILENAME: Define IQ dump filename [/tmp/.satnogs/iq.raw]<br />
<br />
Beware, IQ files are huge (220MB for my APT pass example below). They're stored in /tmp so therefore in RAM and are overwritten with each pass. You can do [https://community.libre.space/t/uploading-compressed-iq-files-to-dropbox-or-any-other-cloud-storage-provider/5395 something clever] to upload them elsewhere, but for playing just grab a copy immediately after a pass.<br />
<br />
Don't worry about storing much else (which also vanishes quickly). You can easily grab waterfalls and OGG recording from the database via [https://github.com/deckbsd/glouton-satnogs-data-downloader Glouton].<br />
<br />
==GNU Radio Companion==<br />
<br />
Here I'm working with [https://network.satnogs.org/observations/2073316/ Observation #2073316] as an example. I've saved a copy of the IQ recording my station briefly stored at `/tmp/.satnogs/iq.raw`. This is about 220 MB. I even remembered to turn the IQ collection off afterwards or it would be storing stuff on top of each other forever.<br />
<br />
===So where did the IQ come from?===<br />
<br />
In my case, I'm playing with an APT pass. It is therefore processed by [https://gitlab.com/librespacefoundation/satnogs/satnogs-flowgraphs/-/blob/master/satellites/noaa_apt_decoder.grc satnogs-flowgraphs/satellites/noaa_apt_decoder.grc]. Other signals use other flowgraphs. The default where nothing else is suitable appears to be [https://gitlab.com/librespacefoundation/satnogs/satnogs-flowgraphs/-/blob/master/generic/fsk.grc satnogs-flowgraphs/generic/fsk.grc].<br />
<br />
[[File:flowgraph_save.png|600px]]<br />
<br />
That is, it's post Doppler correction, which includes an LO (Local Oscillator) offset; and the values are scaled to shorts, although 16768 seems an weird number as I'd have expected a power of two - 16384? I don't imagine it makes a lot of difference as it'll still fit in the short just lose a little bit of dynamic range.<br />
<br />
===Feeding your IQ in===<br />
<br />
Loading the IQ into beginning of the flowgraph in requires some GNU Radio modules chaining together. Starting with [https://community.libre.space/t/how-to-open-satnogs-iq-dat-files/3793 How to open satnogs iq.dat files] you'll end up with something beginning like the below. It takes the file source, throttles the output to real-time, then converts the short values to complex real including reversing the scaling division. This feeds then into the existing flowgraph exactly where it left off.<br />
<br />
[[File:flowgraph_open.png|800px]]<br />
<br />
===Sample rate===<br />
It took some time for me to work out the appropriate sample rate. Here's my methodology:<br />
<br />
The IQ recording is generated by the flowgraph in use. If there's no particular decoder in use then that's <code>GNURADIO_DEFAULT_SCRIPT_FILENAME</code> (see [https://gitlab.com/librespacefoundation/satnogs/satnogs-client/-/blob/master/satnogsclient/settings.py#L66 <code>settings.py</code>] as it keeps changing in HEAD - <code>satnogs_fsk_ax25.py</code>, then <code>fsk.grc</code> and now <code>fm.grc</code>). The flowgraph can vary, but it's probably fairly similar for each on the front end.<br />
<br />
From <code>fsk.grc</code>:<br />
<br />
#Soapy Source collects data at <code>samp_rate_rx</code>.<br />
#Doppler Compensation takes <code>samp_rate_rx</code> and aims for a Target Sampling Rate of <code>baudrate*decimation</code> (in <code>fsk.grc</code>) or <code>audio_samp_rate</code> (in <code>fm.grc</code>). One assumes these should normally be identical, but perhaps someone brighter can explain the difference and how Doppler Compensation converts - decimation?<br />
#IQ sink stores the data to <code>iq_file_path</code>, with a scaling factor of <code>16768</code> applied.<br />
<br />
<br />
'''Where do these parameters come from?'''<br />
<br />
All observation jobs come via [https://gitlab.com/librespacefoundation/satnogs/satnogs-client/-/blob/master/satnogsclient/scheduler/tasks.py#L47 scheduler/tasks.py]. This grabs scheduled jobs from the Satnogs network. In JSON format, the jobs look something like this:<br />
<pre><br />
[<br />
{<br />
"id": 2164959,<br />
"start": "2020-05-06T18:53:17Z",<br />
"end": "2020-05-06T19:00:30Z",<br />
"ground_station": 1450,<br />
"tle0": "0 METEOR M2",<br />
"tle1": "1 40069U 14037A 20126.65202808 -.00000042 00000-0 13670-6 0 9996",<br />
"tle2": "2 40069 98.5071 165.7965 0006707 53.4504 306.7289 14.20671999302133",<br />
"frequency": 137100000,<br />
"mode": "LRPT",<br />
"transmitter": "CojkGDaq3u42nRdLdfczng",<br />
"baud": 80000<br />
<br />
},<br />
{<br />
<br />
"id": 2164887,<br />
"start": "2020-05-06T15:51:13Z",<br />
"end": "2020-05-06T16:06:30Z",<br />
"ground_station": 1450,<br />
"tle0": "0 NOAA 19",<br />
"tle1": "1 33591U 09005A 20126.94623650 +.00000063 +00000-0 +59678-4 0 9999",<br />
"tle2": "2 33591 099.1965 131.1873 0013769 190.9197 169.1677 14.12406430579135",<br />
"frequency": 137100000,<br />
"mode": "APT",<br />
"transmitter": "kE4VaYKpnFmzEquEjKKi8D",<br />
"baud": null<br />
}<br />
]<br />
</pre><br />
<br />
Clearly, there is no sample rate in those, but there is a mode and a baudrate. So that information brings many parameters. Others come from the satnogs configuration done via sudo satnogs-setup. <br />
<br />
<br />
'''How do these parameters get to the flowgraph?'''<br />
<br />
The function <code>exec_gnuradio</code> in [https://gitlab.com/librespacefoundation/satnogs/satnogs-client/-/blob/master/satnogsclient/upsat/gnuradio_handler.py#L60 satnogsclient/upsat/gnuradio_handler.py#L60] takes all the parameters collected and passes them as command line arguments to the relevant flowgraph. It looks like the samp-rate-rx comes from SATNOGS_RX_SAMP_RATE in settings.py. <br />
<br />
<br />
'''So where does the sample rate actually come from!?'''<br />
<br />
Ah, it looks like it's actually static and stored in /etc/ansible/host_vars/localhost:<br />
<br />
<code>...</code><br />
<br />
<code>satnogs_rx_samp_rate: 2.048e6</code><br />
<br />
<code>...</code><br />
<br />
So it's a static sample rate regardless of flowgraph. Okay, that might explain why the Doppler Compensation has different output sample rate and does some kind of decimation.<br />
<br />
''Note: it looks like the new fm.grc doesn't pass a baudrate - what effect will this have on things like LPRT that don't have their own flowgraph handled at present?''<br />
<br />
'''Summary'''<br />
<br />
The key value is the Doppler Compensation ''Target Sampling Rate''.<br />
<br />
For the simple case of APT imaging through [https://gitlab.com/librespacefoundation/satnogs/satnogs-flowgraphs/-/blob/master/satellites/noaa_apt_decoder.grc noaa_apt_decoder.grc] this is pretty simple. it's a static value 4*4160*4 or 66,560.<br />
<br />
It's a more complicated case for say an LRPT signal from [https://db.satnogs.org/satellite/40069/ METEOR M2] for example. This runs through <code>satnogs_fsk_ax25.py</code> at least in my live system. One needs to look at the database page and get the Baud rate of the relevant transmitter (80,000 in this case). Then look at the Doppler Compensation ''Target Sampling Rate'' again which turns out to be <code>baudrate*decimation</code>. Argh! Decimation turns out to be <code>max(4,satnogs.find_decimation(baudrate, 2, audio_samp_rate))</code>. So what's <code>audio_samp_rate</code>? Luckily it's static and set in <code>satnogs_fsk_ax25.py</code> to <code>48e3</code>.<br />
<br />
Using gr-satnogs/python/utils.py, this is easy to calculate:<br />
<pre><br />
>>>> import utils as satnogs<br />
>>>> baudrate = 80000<br />
>>>> audio_samp_rate = 48000<br />
>>>> max(4,satnogs.find_decimation(baudrate, 2, audio_samp_rate))<br />
4<br />
</pre><br />
So, by my calculation, my IQ should be at 4 * 80,000 = 320,000. Hopefully.<br />
<br />
'''Alternative route'''<br />
<br />
After all this hassle, I think the easy fix is the put in a pre-observation script to dump to the logfile! Looks like the following will give me most of what I need, although I'll still need to do some maths.<br />
<br />
<code>echo <nowiki>{{ID}}</nowiki> <nowiki>{{BAUD}}</nowiki> <nowiki>{{SCRIPT_NAME}}</nowiki></code><br />
<br />
===Results===<br />
<br />
Initially, the waterfall may look a bit busy compared to the one from the [https://network.satnogs.org/observations/2073316/ observation]. There's obviously some gain setting within the waterfall I've not yet mastered, or the Satnogs ones does something slightly cleverer.<br />
<br />
[[File:Waterfall.png|200px]]<br />
<br />
Yep. It turns out you can set the intesity min and max to better reflect the signal and get a cleaner display. Still not as good as the observation page one, but maybe that fiddles with the FFT size too.<br />
<br />
[[File:Better.png|200px]] <br />
<br />
However, if you peer closer you can just about make out the feint telltales of an APT signal.<br />
<br />
Following the flowgraph through to output shows an identical output to that on the observation. Result!<br />
<br />
[[File:visual.png|300px]]<br />
<br />
===OGG===<br />
<br />
For completeness, you can do the same thing using the OGG file as a source. Again, you need to reverse any resampling or other changes that were done before saving to file before feeding back into the flowgraph at an appropriate point. The throttle is optional, and in the screenshot bypassed:<br />
<br />
[[File:flowgraph_all.png|800px]]<br />
<br />
[[Category:Software]]<br />
[[Category:Develop]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=Understanding_%27satnogs-flowgraphs%27&diff=3628Understanding 'satnogs-flowgraphs'2020-08-06T08:31:52Z<p>Pierros: Pierros moved page Understanding 'satnogs-flowgraphs' to Understanding satnogs-flowgraphs</p>
<hr />
<div>#REDIRECT [[Understanding satnogs-flowgraphs]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=MediaWiki:Sidebar&diff=3626MediaWiki:Sidebar2020-08-06T08:19:52Z<p>Pierros: </p>
<hr />
<div>* Understand<br />
** <br />
* Build<br />
** Build|[Station] Build a Ground Station<br />
** Raspberry_Pi|[Station] Install a Raspberry Pi<br />
** SatNOGS_Client_Setup|Configure/Update your Station<br />
** Rotators|Rotators<br />
** Antennas|Antennas<br />
** Omnidirectional_Station_How_To| Omnidirectional Station<br />
** Radio|SDR Support<br />
** Troubleshooting|Client Troubleshooting<br />
* Operate<br />
** Satellite_Operator_Guide|Add your Mission<br />
** Operation|Managing Observations<br />
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets<br />
** Telemetry_Dashboards|Telemetry Dashboards<br />
** :Category:RF Modes|RF Modes<br />
* Contribute<br />
** Get_Started|Get Started<br />
** SatNOGS_DB|Crowd-Sourced Satellite Info<br />
** Software_contribution|Software Contribution<br />
** Server_Development_Environment|Server Development Environment<br />
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module<br />
** SatNOGS_Client_Development|SatNOGS Client Development<br />
** Adding_a_new_data_decoder|Adding a new data decoder<br />
** Academic_Papers|Academic Papers citing SatNOGS<br />
** Provide_documentation|Provide Documentation<br />
** SatNOGS_Operations_Manual|SatNOGS Operations Manual<br />
* Contact<br />
** Get_In_Touch|Get In Touch<br />
** https://community.libre.space|Forums<br />
* Links<br />
** https://db.satnogs.org|SatNOGS DB<br />
** https://network.satnogs.org|SatNOGS Network<br />
** https://dashboard.satnogs.org|SatNOGS Dashboard<br />
** https://community.libre.space|SatNOGS Forums<br />
** https://libre.space|Libre Space Foundation<br />
** https://status.libre.space|System Status<br />
* SEARCH</div>Pierroshttps://wiki.satnogs.org/index.php?title=SatNOGS_Operations_Manual&diff=3620SatNOGS Operations Manual2020-06-27T12:23:01Z<p>Pierros: /* 5. Update provisional TLEs (~12 hours before launch) */</p>
<hr />
<div>{{Warning|This manual is intended for SatNOGS Moderators. For a guide on how to add your mission to SatNOGS see [[Satellite Operator Guide]]}}<br />
<br />
===Requirements===<br />
This manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!<br />
<br />
===Adding a new Satellite===<br />
<br />
====0. Should we add it?====<br />
In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible.<br />
<br />
====1. Find new satellites====<br />
Besides the missions that will actively reach out to us by filling issues in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo], we need to track launch activity to ensure we are adding new satellites in our DB. Some resources for tracking launches:<br />
<br />
*https://space.skyrocket.de/doc_chr/lau2020.htm<br />
*https://spaceflightnow.com/launch-schedule/<br />
*https://www.space.com/32286-space-calendar.html<br />
<br />
Tip: As of 2020 we are not adding any swarm satellite entries (e.g. Starlink, OneWeb etc)<br />
<br /><br />
<br />
====2. File the issues in satnogs-ops====<br />
Once you have the information it is needed then navigate to [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo] and open new issues containing all the information needed.<br />
<br />
[https://gitlab.com/librespacefoundation/satnogs-ops/-/issues/new New issue on satnogs-ops]<br />
<br />
Some websites and online resources for digging up information (if not already provided by the mission teams):<br />
<br />
*http://nanosats.eu/<br />
*http://www.amsatuk.me.uk/iaru/index.php<br />
*https://fcc.report/<br />
*https://apps.fcc.gov/oetcf/els/index.cfm<br />
*Search Google and Twitter for mission posted information!<br />
<br />
====3. Add satellite in DB====<br />
<br /><br />
<br />
====4. Add and approve transmitters in DB====<br />
<br />
==== 5. Sync SatNOGS Network ====<br />
Go to [https://network.satnogs.org/settings_site/ Network Site Settings] and click on "Sync"<br />
<br /><br />
====6. Update provisional TLEs (~12 hours before launch)====<br />
<br />
* Acquire provisional TLEs (either constructed from the community or shared by the launch provider)<br />
** You can verify the integrity of the TLE [https://www.vcalc.com/wiki/MichaelBartmess/TLE+Checksum here] and [https://oraas.orekit.space/oraas-tools-tletranslator.html here]<br />
* Go to "[https://network.satnogs.org/admin/base/tle/add/ Add new TLE]" on network.satnogs.org<br />
** Fill out the TLE (don't forget the TLE 0 line too)<br />
** Enter "manual" as source<br />
** Save the TLE<br />
* Go to "[https://network.satnogs.org/admin/base/satellite/ Satellites]" in Admin of network.satnogs.org<br />
** Find and Edit your satellite<br />
** Check "Manual TLE" field<br />
** Save the Satellite<br />
<br />
<br /><br />
====7. Schedule LEOP====<br />
<br /><br />
<br />
====8. Review results====<br />
<br />
<br />
<br />
<br /></div>Pierroshttps://wiki.satnogs.org/index.php?title=MediaWiki:Sidebar&diff=3619MediaWiki:Sidebar2020-06-20T08:30:04Z<p>Pierros: </p>
<hr />
<div>* Build<br />
** Raspberry_Pi|Install a Raspberry Pi<br />
** Build|Build a Ground Station<br />
** SatNOGS_Client_Setup|Configure your Station<br />
** Rotators|Rotators<br />
** Antennas|Antennas<br />
** Omnidirectional_Station_How_To| Omnidirectional Station<br />
** Radio|SDR Support<br />
** Troubleshooting|Client Troubleshooting<br />
** SatNOGS_Client_Setup#Updating_SatNOGS_Client_Software|Updating your Station Software<br />
* Operate<br />
** Satellite_Operator_Guide|Add your Mission<br />
** Operation|Managing Observations<br />
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets<br />
** Telemetry_Dashboards|Telemetry Dashboards<br />
** :Category:RF Modes|RF Modes<br />
* Contribute<br />
** Get_Started|Get Started<br />
** SatNOGS_DB|Crowd-Sourced Satellite Info<br />
** Software_contribution|Software Contribution<br />
** Server_Development_Environment|Server Development Environment<br />
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module<br />
** SatNOGS_Client_Development|SatNOGS Client Development<br />
** Adding_a_new_data_decoder|Adding a new data decoder<br />
** Academic_Papers|Academic Papers citing SatNOGS<br />
** Provide_documentation|Provide Documentation<br />
** SatNOGS_Operations_Manual|SatNOGS Operations Manual<br />
* Contact<br />
** Get_In_Touch|Get In Touch<br />
** https://community.libre.space|Forums<br />
* Links<br />
** https://db.satnogs.org|SatNOGS DB<br />
** https://network.satnogs.org|SatNOGS Network<br />
** https://dashboard.satnogs.org|SatNOGS Dashboard<br />
** https://community.libre.space|SatNOGS Forums<br />
** https://libre.space|Libre Space Foundation<br />
** https://status.libre.space|System Status<br />
* SEARCH</div>Pierroshttps://wiki.satnogs.org/index.php?title=SatNOGS_Operations_Manual&diff=3618SatNOGS Operations Manual2020-06-19T18:03:31Z<p>Pierros: </p>
<hr />
<div>{{Warning|This manual is intended for SatNOGS Moderators. For a guide on how to add your mission to SatNOGS see [[Satellite Operator Guide]]}}<br />
<br />
===Requirements===<br />
This manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!<br />
<br />
===Adding a new Satellite===<br />
<br />
====0. Should we add it?====<br />
In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible.<br />
<br />
====1. Find new satellites====<br />
Besides the missions that will actively reach out to us by filling issues in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo], we need to track launch activity to ensure we are adding new satellites in our DB. Some resources for tracking launches:<br />
<br />
*https://space.skyrocket.de/doc_chr/lau2020.htm<br />
*https://spaceflightnow.com/launch-schedule/<br />
*https://www.space.com/32286-space-calendar.html<br />
<br />
Tip: As of 2020 we are not adding any swarm satellite entries (e.g. Starlink, OneWeb etc)<br />
<br /><br />
<br />
====2. File the issues in satnogs-ops====<br />
Once you have the information it is needed then navigate to [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo] and open new issues containing all the information needed.<br />
<br />
[https://gitlab.com/librespacefoundation/satnogs-ops/-/issues/new New issue on satnogs-ops]<br />
<br />
Some websites and online resources for digging up information (if not already provided by the mission teams):<br />
<br />
*http://nanosats.eu/<br />
*http://www.amsatuk.me.uk/iaru/index.php<br />
*https://fcc.report/<br />
*https://apps.fcc.gov/oetcf/els/index.cfm<br />
*Search Google and Twitter for mission posted information!<br />
<br />
====3. Add satellite in DB====<br />
<br /><br />
<br />
====4. Add and approve transmitters in DB====<br />
<br /><br />
<br />
====5. Update provisional TLEs (~12 hours before launch)====<br />
<br /><br />
<br />
====6. Sync SatNOGS Network====<br />
<br /><br />
<br />
====7. Schedule LEOP====<br />
<br /><br />
<br />
====8. Review results====<br />
<br />
<br />
<br />
<br /></div>Pierroshttps://wiki.satnogs.org/index.php?title=SatNOGS_Operations_Manual&diff=3616SatNOGS Operations Manual2020-06-19T16:32:57Z<p>Pierros: </p>
<hr />
<div>{{Warning|This manual is intended for SatNOGS Moderators. For a guide on how to add your mission to SatNOGS see [[Satellite Operator Guide]]}}<br />
<br />
===Requirements===<br />
his manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!<br />
<br />
===Adding a new Satellite===<br />
<br />
====0. Should we add it?====<br />
In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible.<br />
<br />
==== 1. Find new satellites ====<br />
Besides the missions that will actively reach out to us by filling issues in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo], we need to track launch activity to ensure we are adding new satellites in our DB. Some resources for tracking launches:<br />
<br />
* https://space.skyrocket.de/doc_chr/lau2020.htm<br />
* https://spaceflightnow.com/launch-schedule/<br />
* https://www.space.com/32286-space-calendar.html<br />
<br />
Tip: As of 2020 we are not adding any swarm satellite entries (e.g. Starlink, OneWeb etc)<br />
<br /><br />
<br />
==== 2. File the issues in satnogs-ops ====<br />
Once you have the information it is needed then navigate to [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo] and open new issues containing all the information needed. Some websites and online resources for digging up information (if not already provided by the mission teams):<br />
<br />
* http://nanosats.eu/<br />
* http://www.amsatuk.me.uk/iaru/index.php<br />
* https://fcc.report/<br />
* https://apps.fcc.gov/oetcf/els/index.cfm<br />
* Search Google and Twitter for mission posted information!<br />
<br />
==== 3. Add satellite in DB ====<br />
<br /><br />
<br />
==== 4. Add and approve transmitters in DB ====<br />
<br /><br />
<br />
==== 5. Update provisional TLEs (~12 hours before launch) ====<br />
<br /><br />
<br />
==== 6. Sync SatNOGS Network ====<br />
<br /><br />
<br />
==== 7. Schedule LEOP ====<br />
<br /><br />
<br />
==== 8. Review results ====<br />
<br />
<br />
<br />
<br /></div>Pierroshttps://wiki.satnogs.org/index.php?title=MediaWiki:Sidebar&diff=3615MediaWiki:Sidebar2020-06-19T16:20:04Z<p>Pierros: </p>
<hr />
<div>* Build<br />
** Raspberry_Pi|Install a Raspberry Pi<br />
** Build|Build a Ground Station<br />
** SatNOGS_Client_Setup|Configure your Station<br />
** Rotators|Rotators<br />
** Antennas|Antennas<br />
** Omnidirectional_Station_How_To| Omnidirectional Station<br />
** Radio|SDR Support<br />
** Troubleshooting|Client Troubleshooting<br />
** SatNOGS_Client_Setup#Updating_SatNOGS_Client_Software|Updating your Station Software<br />
* Operate<br />
** Satellite_Operator_Guide|Add your Mission<br />
** Operation|Managing Observations<br />
** Decode_Telemetry_and_Packets|Decode Telemetry and Packets<br />
** Telemetry_Dashboards|Telemetry Dashboards<br />
** :Category:RF Modes|RF Modes<br />
* Contribute<br />
** Get_Started|Get Started<br />
** SatNOGS_DB|Crowd-Sourced Satellite Info<br />
** Software_contribution|Software Contribution<br />
** Server_Development_Environment|Server Development Environment<br />
** Hacking_the_GNURadio_Module_'gr-satnogs'|SatNOGS GNURadio Module<br />
** SatNOGS_Client_Development|SatNOGS Client Development<br />
** Adding_a_new_data_decoder|Adding a new data decoder<br />
** Academic_Papers|Academic Papers citing SatNOGS<br />
** Provide_documentation|Provide Documentation<br />
* Contact<br />
** Get_In_Touch|Get In Touch<br />
** https://community.libre.space|Forums<br />
* Links<br />
** https://db.satnogs.org|SatNOGS DB<br />
** https://network.satnogs.org|SatNOGS Network<br />
** https://dashboard.satnogs.org|SatNOGS Dashboard<br />
** https://community.libre.space|SatNOGS Forums<br />
** https://libre.space|Libre Space Foundation<br />
** https://status.libre.space|System Status<br />
* SEARCH</div>Pierroshttps://wiki.satnogs.org/index.php?title=SatNOGS_Operations_Manual&diff=3614SatNOGS Operations Manual2020-06-19T11:46:42Z<p>Pierros: wip</p>
<hr />
<div>{{Warning|This manual is intended for SatNOGS Moderators. For a guide on how to add your mission to SatNOGS see [[Satellite Operator Guide]]}}<br />
<br />
=== Requirements ===<br />
his manual assumes you have SatNOGS moderator access on Network and DB. If you don't please reach out to our channels for gaining access and helping with SatNOGS Operations!<br />
<br />
=== Adding a new Satellite ===<br />
<br />
==== 0. Should we add it? ====<br />
In principle SatNOGS DB aims to capture all information about satellites regardless of their origin, ownership or purpose. So the simple answer is "Yes you should add it". That said we do prioritize the satellites that can be (and will be) tracked by the SatNOGS Network and especially the ones that have been pro-active in reaching out and sharing as much information as possible.<br />
<br />
1. Find new satellites<br />
<br />
Besides the missions that will actively reach out to us by filling issues in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops repo]</div>Pierroshttps://wiki.satnogs.org/index.php?title=Satellite_Mission_Guide&diff=3613Satellite Mission Guide2020-06-19T10:24:34Z<p>Pierros: Redirected page to Satellite Operator Guide</p>
<hr />
<div>#REDIRECT [[Satellite Operator Guide]]{{Warning|WIP - Work in Progress; Should be merged into https://wiki.satnogs.org/Satellite_operator_manual}}<br />
<br />
This page intents to provide information for Satellite Missions (under development, or operational) on why and how to join SatNOGS.<br />
<br />
===Reasons to Join===<br />
<br />
You have recently discovered SatNOGS and you are involved in a mission. Here are the top 10 reasons why your mission should join SatNOGS:<br />
<br />
#SatNOGS can help streamline your mission operations (Dashboards, Monitoring, Telemetry acquisition)<br />
#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!<br />
#SatNOGS is a global community of satellite enthusiasts, radio amateurs and satellite operators! [[Get In Touch|Join our community and be part of it.]]<br />
#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.<br />
#SatNOGS is the largest global ground station network. 400 stations online with a spread around the world. No other network can beat that :)<br />
#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!<br />
#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.<br />
#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.<br />
#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/]).<br />
#SatNOGS is a project abiding to the Libre Space Manifesto [https://manifesto.libre.space/].<br />
<br />
===Add a new Mission===<br />
<br />
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:<br />
<br />
#SatNOGS DB<br />
#*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:<br />
#**Name<br />
#**NORAD catalog number (if already assigned)<br />
#**Amateur Radio call sign (if Amateur service)<br />
#**Description<br />
#**Project Website<br />
#**Image of the satellite<br />
#*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<br />
#GR SatNOGS<br />
#*Choose one of the existing flowgraphs in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs] or provide a new one<br />
#SatNOGS Client<br />
#*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]<br />
#*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.<br />
#SatNOGS Decoders<br />
#*Add a decoder written in [https://kaitai.io/ Kaitai] to [https://gitlab.com/librespacefoundation/satnogs/satnogs-decoders satnogs-decoders]<br />
<br />
<br />
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).<br />
<br />
<br />
==See also==<br />
<br />
*[[SatNOGS DB]]<br />
*[[SatNOGS Network]]<br />
*[[Satellite operator manual]]<br />
<br />
[[Category:Satellite]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=Satellite_Operator_Guide&diff=3611Satellite Operator Guide2020-06-19T10:18:37Z<p>Pierros: Pierros moved page Satellite operator manual to Satellite Operator Guide</p>
<hr />
<div>{{warning|This guide is intended for Satellite Operators. For SatNOGS Operations moderators please see [[SatNOGS Operations Manual]]}}<br />
==Introduction==<br />
You are building a satellite? Congratulations! The information below will be helpful for the Communications and Operations part of your mission. Plan early and invest time in COMMS and Ground Segment. As a community, SatNOGS is here to help you in the process!<br />
<br />
Although the information is tailored for missions that will be using Amateur Radio bands of the spectrum, some information is still relevant for other parts of the band too.<br />
<br />
==Process==<br />
===0. Early Stage===<br />
It's strongly advised to get in touch with the AMSAT of you country at the beginning of your project. It enables that the radio amateur requirements are taken in account at the early stage on your project. It avoids false expectations and miscommunications along the way. In order to use an Amateur Radio band, your mission needs to be Amateur Radio related. Broadly speaking this includes and Amateur Radio service (like a transponder) or Amateur Radio experiment (new modulations, propagation experiments etc).<br />
===1. Frequency Coordination===<br />
First you need to determine whether you'll require an amateur frequency, a non-amateur frequency, or both.<br />
<br />
Historically educational but non-Amateur Radio satellite operators (e.g. university research projects) were often improperly permitted to use amateur spectrum on a not-commercial basis. As this practice has led to serious congestion of the Amateur Radio Service, the IARU will no longer coordinate amateur frequency allocation for this purpose. Therefore:<br />
<br />
*If your satellite will be purely for Amateur Radio use (i.e. all of its major functions will be available for use by all licensed Amateur Radio operators), then you're usually able to request Amateur Radio Space Service frequency coordination from IARU. You remain free to perform limited control functions on Amateur Radio spectrum. If there is an AMSAT organization in your country, start there. If not, approach your national Amateur Radio body. They will usually help you to get a radio amateur frequency coordination from IARU your allocation. It will take time: usually between six months and a year. If you don't ask for an IARU coordination, the launcher of your satellite may not allow you to launch the satellite.<br />
*If your satellite will have substantial non-Radio Amateur use (sensor data, imagery, space-qualification of components, ...) then you will usually require a (non-amateur) Space Service license and frequency allocation. Approach your local radio communication regulator directly to start this process, which will have to finalized through ITU.<br />
*If your satellite will do both, then you'll require licenses and frequency allocation/coordination for both services. A recent example is [https://www.amsat.org/falconsat-3/ FalconSAT-3].<br />
<br />
====1.1 Publicly and openly document your Communications====<br />
If you are planning to use a Radio Amateur band you are required to publicly and openly document ever singe detail of your transmission. That includes your modulation, encoding, framing and various functions. Your uplink and TC operations might not be publicly documented if you choose so.<br />
<br />
Regardless of your band usage, we would strongly advise you to openly document your Communications since Open Data is a core pillar of sustainable and efficient Space operations. See the [https://manifesto.libre.space/ Libre Space Manifesto] for more info.<br />
<br />
===2. Integration with SatNOGS===<br />
====2.1 Reasons to Join====<br />
You have recently discovered SatNOGS and you are involved in a mission. Here are the top 10 reasons why your mission should join SatNOGS:<br />
<br />
#SatNOGS can help streamline your mission operations (Dashboards, Monitoring, Telemetry acquisition)<br />
#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!<br />
#SatNOGS is a global community of satellite enthusiasts, radio amateurs and satellite operators! [[Get In Touch|Join our community and be part of it.]]<br />
#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.<br />
#SatNOGS is the largest global ground station network. 400 stations online with a spread around the world. No other network can beat that :)<br />
#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!<br />
#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.<br />
#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.<br />
#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/]).<br />
#SatNOGS is a project abiding to the Libre Space Manifesto [https://manifesto.libre.space/].<br />
<br />
<br /><br />
<br />
==== 2.2 Add a new Mission ====<br />
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:<br />
<br />
#SatNOGS DB<br />
#*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:<br />
#**Name<br />
#**NORAD catalog number (if already assigned)<br />
#**Amateur Radio call sign (if Amateur service)<br />
#**Description<br />
#**Project Website<br />
#**Image of the satellite<br />
#*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<br />
#SatNOGS GNURadio<br />
#*Choose one of the existing flowgraphs in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs] or provide a new one<br />
#SatNOGS Client<br />
#*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]<br />
#*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.<br />
#SatNOGS Decoders<br />
#*Add a decoder written in [https://kaitai.io/ Kaitai] to [https://gitlab.com/librespacefoundation/satnogs/satnogs-decoders satnogs-decoders]<br />
#SatNOGS Dashboar d<br />
#*Create a new dashboard in [https://dashboard.satnogs.org dashboard.satnogs.org] for your satellite.<br />
{{warning|In order to have scheduling rights in SatNOGS Network, you need to own an operational Online Station in the Network. Consider building one, or donating one in the Network.}}<br />
==3. Operations==<br />
TBA<br />
<br />
==See Also==<br />
<br />
*[[DB|SatNOGS DB]]<br />
*[[Network|SatNOGS Network]]<br />
*[[Forum|Community Forum]]<br />
*[[Get In Touch]]<br />
<br />
[[Category:Satellite]]<br />
[[Category:RF Modes]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=Satellite_operator_manual&diff=3612Satellite operator manual2020-06-19T10:18:37Z<p>Pierros: Pierros moved page Satellite operator manual to Satellite Operator Guide</p>
<hr />
<div>#REDIRECT [[Satellite Operator Guide]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=Satellite_Operator_Guide&diff=3610Satellite Operator Guide2020-06-19T10:17:48Z<p>Pierros: refactor and merging info from Satellite Mission Guide</p>
<hr />
<div>{{warning|This guide is intended for Satellite Operators. For SatNOGS Operations moderators please see [[SatNOGS Operations Manual]]}}<br />
==Introduction==<br />
You are building a satellite? Congratulations! The information below will be helpful for the Communications and Operations part of your mission. Plan early and invest time in COMMS and Ground Segment. As a community, SatNOGS is here to help you in the process!<br />
<br />
Although the information is tailored for missions that will be using Amateur Radio bands of the spectrum, some information is still relevant for other parts of the band too.<br />
<br />
==Process==<br />
===0. Early Stage===<br />
It's strongly advised to get in touch with the AMSAT of you country at the beginning of your project. It enables that the radio amateur requirements are taken in account at the early stage on your project. It avoids false expectations and miscommunications along the way. In order to use an Amateur Radio band, your mission needs to be Amateur Radio related. Broadly speaking this includes and Amateur Radio service (like a transponder) or Amateur Radio experiment (new modulations, propagation experiments etc).<br />
===1. Frequency Coordination===<br />
First you need to determine whether you'll require an amateur frequency, a non-amateur frequency, or both.<br />
<br />
Historically educational but non-Amateur Radio satellite operators (e.g. university research projects) were often improperly permitted to use amateur spectrum on a not-commercial basis. As this practice has led to serious congestion of the Amateur Radio Service, the IARU will no longer coordinate amateur frequency allocation for this purpose. Therefore:<br />
<br />
*If your satellite will be purely for Amateur Radio use (i.e. all of its major functions will be available for use by all licensed Amateur Radio operators), then you're usually able to request Amateur Radio Space Service frequency coordination from IARU. You remain free to perform limited control functions on Amateur Radio spectrum. If there is an AMSAT organization in your country, start there. If not, approach your national Amateur Radio body. They will usually help you to get a radio amateur frequency coordination from IARU your allocation. It will take time: usually between six months and a year. If you don't ask for an IARU coordination, the launcher of your satellite may not allow you to launch the satellite.<br />
*If your satellite will have substantial non-Radio Amateur use (sensor data, imagery, space-qualification of components, ...) then you will usually require a (non-amateur) Space Service license and frequency allocation. Approach your local radio communication regulator directly to start this process, which will have to finalized through ITU.<br />
*If your satellite will do both, then you'll require licenses and frequency allocation/coordination for both services. A recent example is [https://www.amsat.org/falconsat-3/ FalconSAT-3].<br />
<br />
====1.1 Publicly and openly document your Communications====<br />
If you are planning to use a Radio Amateur band you are required to publicly and openly document ever singe detail of your transmission. That includes your modulation, encoding, framing and various functions. Your uplink and TC operations might not be publicly documented if you choose so.<br />
<br />
Regardless of your band usage, we would strongly advise you to openly document your Communications since Open Data is a core pillar of sustainable and efficient Space operations. See the [https://manifesto.libre.space/ Libre Space Manifesto] for more info.<br />
<br />
===2. Integration with SatNOGS===<br />
====2.1 Reasons to Join====<br />
You have recently discovered SatNOGS and you are involved in a mission. Here are the top 10 reasons why your mission should join SatNOGS:<br />
<br />
#SatNOGS can help streamline your mission operations (Dashboards, Monitoring, Telemetry acquisition)<br />
#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!<br />
#SatNOGS is a global community of satellite enthusiasts, radio amateurs and satellite operators! [[Get In Touch|Join our community and be part of it.]]<br />
#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.<br />
#SatNOGS is the largest global ground station network. 400 stations online with a spread around the world. No other network can beat that :)<br />
#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!<br />
#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.<br />
#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.<br />
#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/]).<br />
#SatNOGS is a project abiding to the Libre Space Manifesto [https://manifesto.libre.space/].<br />
<br />
<br /><br />
<br />
==== 2.2 Add a new Mission ====<br />
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:<br />
<br />
#SatNOGS DB<br />
#*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:<br />
#**Name<br />
#**NORAD catalog number (if already assigned)<br />
#**Amateur Radio call sign (if Amateur service)<br />
#**Description<br />
#**Project Website<br />
#**Image of the satellite<br />
#*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<br />
#SatNOGS GNURadio<br />
#*Choose one of the existing flowgraphs in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs] or provide a new one<br />
#SatNOGS Client<br />
#*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]<br />
#*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.<br />
#SatNOGS Decoders<br />
#*Add a decoder written in [https://kaitai.io/ Kaitai] to [https://gitlab.com/librespacefoundation/satnogs/satnogs-decoders satnogs-decoders]<br />
#SatNOGS Dashboar d<br />
#*Create a new dashboard in [https://dashboard.satnogs.org dashboard.satnogs.org] for your satellite.<br />
{{warning|In order to have scheduling rights in SatNOGS Network, you need to own an operational Online Station in the Network. Consider building one, or donating one in the Network.}}<br />
==3. Operations==<br />
TBA<br />
<br />
==See Also==<br />
<br />
*[[DB|SatNOGS DB]]<br />
*[[Network|SatNOGS Network]]<br />
*[[Forum|Community Forum]]<br />
*[[Get In Touch]]<br />
<br />
[[Category:Satellite]]<br />
[[Category:RF Modes]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=Get_Started&diff=3426Get Started2020-02-21T18:24:17Z<p>Pierros: /* STEP 3: Create an account on Network */</p>
<hr />
<div>==Introduction==<br />
<br />
Welcome to the SatNOGS community! Here you can find all the info needed to get you started. If you can't wait then why not head over to the [[Omnidirectional_Station_How_To|Quick Start]] page where you find all the information need to get a fixed antenna ground station.<br />
<br />
SatNOGS is a Hackaday Prize winning global project that consists of a network of ground stations that are used to receive voice, CW and data from satellites. As a user you can either build your own ground station and connect to the network or just simply use the existing ground stations to take what you need from the obersvation.<br />
<br />
A [[Ground_Stations|ground station]] could be a simple fixed antenna with a Raspberry Pi through to a complex multi antenna steerable ground station running a much larger server. If you're new to this then the [https://community.libre.space/ community] can support and help.<br />
<br />
The basic steps are below, beneath this is more detail on the individual aspects<br />
<br />
==Who are you?==<br />
<br />
*'''Radio Amateur''': Most members of SatNOGS community are radio amateur operators licensed in may different countries around the world.<br />
*'''Space enthusiast''': You love space and space data? SatNOGS is just the project for you! There are many learning opportunities around our community, and you can start easily with accessible projects, while you gradually become a space expert!<br />
*'''Satellite operator''': You have your own satellite project? That's awesome! Many SatNOGS ground stations are built by satellite operators to gain extended access on their satellite telemetry and use the stations for telecommand and control.<br />
<br />
==STEP 1: Join the community==<br />
[[File:Satnogs-forum-cap.png|800px|SatNOGS Forum Screen capture]]<br />
<br />
First things first: make sure to get connected with fellow SatNOG-ers!<br />
<br />
*Join the [https://community.libre.space community forums] and [https://community.libre.space/t/new-users-welcome/29 announce yourself].<br />
*Follow us on our [https://libre.space/category/updates/ Blog], via [https://twitter.com/satnogs Twitter] or [https://www.facebook.com/satnogs/ Facebook].<br />
*Join our live discussions over at IRC #satnogs on the Freenode network, or via [https://riot.im/app/#/room/#satnogs:matrix.org the Matrix #satnogs room].<br />
<br />
==STEP 2: Choose and deploy your ground station==<br />
<br />
Learn about the different options for [[Build|ground stations and software]], and create your station. This choice will determine what type of ground station you have. The reference design of a Raspberry Pi, an RTL-SDR broadband SDR receiver and single antenna is deliberatly straightforward. However, the network is not limited to simple set ups. More complex multi antenna steerable ground stations are common but will need a greater investment in time and resources. They do offer superior performance though.<br />
<br />
==STEP 3: Create an account on Network==<br />
[[File:Satnogs-network-cap.png|800px|SatNOGS Network Screen capture]]<br />
<br />
SatNOGS runs a network instance at [https://network.satnogs.org/ https://network.satnogs.org]. It's used to operate various ground stations around the world, but it's also the right place for you to test your ground station. [https://network.satnogs.org/login/auth0 Sign up for an account]. Once you've verified your email address, log in and create a ground station entry and an API key. (Save the API key -- you'll need that when you install the SatNOGS client.<br />
<br />
(And if you notice any bugs along the way -- [https://gitlab.com/librespacefoundation/satnogs/satnogs-network/issues please let us know]!)<br />
<br />
==STEP 4: Test your setup==<br />
<br />
In this step, you will install the SatNOGS client (if you haven't already), and ensure that it can connect to the Network. Once that's done, you can [[Operation|schedule your first observation]].<br />
<br />
==STEP 5: Move your station out of testing==<br />
<br />
Once you feel confident with your observations, post your successful observations to [https://community.libre.space/c/observations the community]. When you feel ready and feedback from the community is positive, edit your station in Network and remove the "Testing" flag from it! Now continue scheduling observations!<br />
<br />
==STEP +: Consider wider contributions==<br />
<br />
There are many ways to contribute to the SatNOGS project:<br />
<br />
*[[Software contribution|Contributing to the software that runs SatNOGS]]<br />
*[[Provide documentation|Improving the documentation for the project]]<br />
*[[Satnogs DB|Improving the SatNOGS database]]<br />
<br />
==See also==<br />
<br />
*[[Introduction]] to SatNOGS.<br />
<br />
[[Category:Build]]<br />
[[Category:Community]]</div>Pierroshttps://wiki.satnogs.org/index.php?title=Satellite_Mission_Guide&diff=3406Satellite Mission Guide2020-02-01T09:40:16Z<p>Pierros: </p>
<hr />
<div>{{Warning|WIP - Work in Progress}}<br />
<br />
This page intents to provide information for Satellite Missions (under development, or operational) on why and how to join SatNOGS.<br />
<br />
=== Reasons to Join ===<br />
You have recently discovered SatNOGS and you are involved in a mission. Here are the top 10 reasons why your mission should join SatNOGS:<br />
<br />
#SatNOGS can help streamline your mission operations (Dashboards, Monitoring, Telemetry acquisition)<br />
#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!<br />
#SatNOGS is a global community of satellite enthusiasts, radio amateurs and satellite operators! [[Get In Touch|Join our community and be part of it.]]<br />
#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.<br />
#SatNOGS is the largest global ground station network. 400 stations online with a spread around the world. No other network can beat that :)<br />
#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!<br />
#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.<br />
#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.<br />
#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/]).<br />
#SatNOGS is a project abiding to the Libre Space Manifesto [https://manifesto.libre.space/].<br />
<br />
<br />
Do you want to integrate your mission with SatNOGS? Cool! Here is a guide how to do this.<br />
<br />
Please also reach out to us via chat or community so that we can support you.<br />
<br />
*Suggest to add your satellite to satnogs-db by creating an issue in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops]<br />
*Once the new satellite was added to satnogs-db by one of the satnogs-ops team, find your satellite in [https://db.satnogs.org/ db.satnogs.org] and add a transmitter suggestion for each transmitter of your satellite<br />
*Choose one of the existing flowgraphs in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs] or provide a new one<br />
*If you add a new flowgraph, make sure to add support for it in [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client]<br />
*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.<br />
*Add a decoder written in [https://kaitai.io/ Kaitai] to [https://gitlab.com/librespacefoundation/satnogs/satnogs-decoders satnogs-decoders]<br />
<br />
<br />
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).</div>Pierroshttps://wiki.satnogs.org/index.php?title=Satellite_Mission_Guide&diff=3405Satellite Mission Guide2020-02-01T09:35:56Z<p>Pierros: added reasons to join</p>
<hr />
<div>-- heavily WIP - WORK IN PROGRESS --<br />
<br />
You have recently discovered SatNOGS and you are involved in a mission. Here are the top 10 reasons why your mission should join SatNOGS:<br />
<br />
# SatNOGS can help streamline your mission operations (Dashboards, Monitoring, Telemetry acquisition)<br />
# 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!<br />
# SatNOGS is a global community of satellite enthusiasts, radio amateurs and satellite operators! [[Get In Touch|Join our community and be part of it.]]<br />
# 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.<br />
# SatNOGS is the largest global ground station network. 400 stations online with a spread around the world. No other network can beat that :)<br />
# 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!<br />
# 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.<br />
# 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.<br />
# 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/]).<br />
# SatNOGS is a project abiding to the Libre Space Manifesto [https://manifesto.libre.space/].<br />
<br />
<br />
Do you want to integrate your mission with SatNOGS? Cool! Here is a guide how to do this.<br />
<br />
Please also reach out to us via chat or community so that we can support you.<br />
<br />
*Suggest to add your satellite to satnogs-db by creating an issue in [https://gitlab.com/librespacefoundation/satnogs-ops satnogs-ops]<br />
*Once the new satellite was added to satnogs-db by one of the satnogs-ops team, find your satellite in [https://db.satnogs.org/ db.satnogs.org] and add a transmitter suggestion for each transmitter of your satellite<br />
*Choose one of the existing flowgraphs in [https://gitlab.com/librespacefoundation/satnogs/gr-satnogs gr-satnogs] or provide a new one<br />
*If you add a new flowgraph, make sure to add support for it in [https://gitlab.com/librespacefoundation/satnogs/satnogs-client satnogs-client]<br />
*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.<br />
*Add a decoder written in [https://kaitai.io/ Kaitai] to [https://gitlab.com/librespacefoundation/satnogs/satnogs-decoders satnogs-decoders]<br />
<br />
<br />
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).</div>Pierros