Close
0%
0%

SatNOGS - Global Network of Ground Stations

SatNOGS is an open source satellite ground station network, optimized for modularity, built using affordable tools and resources.

Similar projects worth following
SatNOGS project is a complete platform for an open source Satellite Ground Station Network. The scope of the project is to create a full stack of open technologies based on open standards , and the construction of a full ground station as a showcase of the stack.
SatNOGS provides the basis for:

Bulk manufacturing and deployment of affordable Satellite Ground Stations
Modular design for integration with existing and future technologies
A platform for a variety of instrumentation around Satellite Ground Station operations
A firm platform for a Ground Station collaborative network (one to one, one to many, many to many)
A community based approach on Ground Station development
A solution for massive automation of operator-less Ground Stations based on open standards

Check out our documentation on the website for detailed info.

SatNOGS is a modular and scalable stack for Satellite Ground Station implementation. Fully based on open source technologies and open standards, it provides interoperability with existing or future subsystems.

A Global Management Network is the key part of our stack, connecting multiple observers with multiple ground stations enabling tracking and monitoring of satellites from multiple locations around the world. The data gathered will be publicly accessible through the network website.

SatNOGS project is implementing the above general stack design using 4 different sub-projects.

SatNOGS Network - Our observations, scheduling and discovery server

SatNOGS DB - Our crowd-sourced suggestions transponder info website

SatNOGS Client - An embedded system that receives the scheduled operation from Network, records an observation and sends it back

SatNOGS Ground Station - The actual ground station instrumentation with tracker, antennas, LNAs and connected to Client.

You can choose the configuration you want, re-using existing hardware:

The following System Design visualization depicts all subsystems of a reference implementation of a SatNOGS Ground Station.

A rendering of the finalized ground station (with front cover open) can be seen here:

  • 2 × Stepper Motor NEMA 14 or NEMA 17
  • 2 × 3D printed Gear Assembly Check our repo for designs
  • 1 × Arduino Micro For Alt/Az commands translation and commanding the stepper drivers
  • 1 × TP-Link wr703n For WiFi connectivity and routing
  • 2 × Signal Receiver DVB-T receiver based on RTL2832U

View all 9 components

  • SatNOGS News – January 2017

    elkos01/23/2017 at 01:51 0 comments

    SatNOGS community has been busy over the last couple of months, with many exciting updates on projects to share with you!

    satnogsrot31

    Rotator v3.1

    First and foremost, the 3.1 version of the SatNOGS rotator is soon to be finalized. If you are already working with a v3 keep in mind that upgrading to 3.1 is pretty straightforward, on the meantime feel free to share your build progress or finished ground stations with our community We got have some stickers to send to SatNOGS ground station operators. We really hope that lot’s of people get to install their own v3.1 rotator and hook up to the SatNOGS network, and we are working on a way to get the v3.1 rotator design to as many people as possible.


    New UHF antenna

    We published a new UHF 8 turn helical antenna design. Documentation and step-by-step build process is now public so everyone interested can build one on their own, using readily available tools and materials.


    Updates on SatNOGS DB

    Our crowd-sourced satellite database, SatNOGS DB, is expanding and will soon be powering Csete’s gpredict through it’s API. In the meantime we deployed new functionality that allows SatNOGS DB to visualize telemetry data captured using the SatNOGS Network of ground stations.


    Events

    We really appreciate people participating in the SatNOGS project, either in our community website, our IRC/Matrix chatroom, the SatNOGS Wiki, populating the SatNOGS database and our source code repositories but we also enjoy meeting people interested in SatNOGS in person.

    linuxconfauLast week on Linux.conf.au taking place in Hobart,Australia, Scott Bragg’s gave a great talk titled “Decoding Satellites With SatNOGS“. It was a great overview of the SatNOGS project and the ways you can get involved.

    shrAijm8_400x400Since most of the core SatNOGS team lives in Europe most of us will attend FOSDEM in Brussels,Belgium this February. There Manolis Surligas is giving a talk “SDR for Space the Open Way” focusing on the Software Defined Radio RF frontend and the GNU Radio module operating it and will be introduced in the coming versions of the SatNOGS client.

    Stay tuned for more detailed updates, and as always … keep hunting satellites!

    log is copied by SatNOGS main project website

  • SatNOGS DB, the open satellite transmitter database opens for contributions

    elkos07/23/2015 at 00:55 0 comments

    Early on, while developing SatNOGS, the SatNOGS team encountered the lack of a central and editable database for active satellite transmitters. Such information would be vital not only for SatNOGS operations but also for amateur radio operators interested in satellite telecommunications.

    Over the past many years, lots of radio amateurs undertook the challenge by creating personal pages that would keep track of transmitter data, and although there are really fine examples of such efforts (props to PE0SAT, JE9PEL, OZ9AEC, AMSAT-UK and others) those are unfortunately not scalable approaches, that could easily become deprecated and are not easily exported for further usage.

    Our solution was to create SatNOGS DB an open satellite transmitter database, that allows everyone to suggest transmitter information of active satellites and collaborate in keeping the database up-to date. SatNOGS DB information is freely and openly (CC-BY-SA) accessible via an API and a web application, to facilitate the needs of satellite radio operators across the globe.

    satnogs-db

    Technically our current implementation is based on the Django Python framework. The code can be found here and we are looking for code contributors as always! Do you have any suggestions on how we can make SatNOGS DB better? File away issues here, so we can make DB better for everyone.

    If you are a satellite operator, or an amateur radio enthusiast and would like to make suggestions on populating SatNOGS DB don’t hesitate to check out our FAQ on how to do so.

    satnogs db

    The more transmitter information we have, the easier it is to communicate with many more satellites. So get those contributions started, and together let’s create the holistic, open and crowd-sourced satellite transmitter database once and for all!

    (cross posted in the SatNOGS blog)

  • Introducing the Summer Of Code In Space 2015 student working on SatNOGS

    elkos06/03/2015 at 01:52 0 comments

    42_digital_logo_dark_blue_sign_AAs posted a few months ago SatNOGS is participating as a mentor organization in European Space Agency's Summer Of Code In Space 2015, during the call for proposals we received numerous interesting proposals to work on SatNOGS during summer as part of the Summer Of Code In Space initiative, from these proposals and with the consultation of the ESA SOCIS managers we choose Emilio Martínez's proposal working on "a pre-amplifier with an integrated antenna polarization switch for cross YAGI-UDA UHF band antenna, and a U/V diplexer module for the SatNOGS ground station". Emilio provided a highly detailed proposal for his work in SatNOGS and we are really excited to work with him during summer and beyond to the development of SatNOGS.

    EmilioEmilio Martínez is a Spanish Telecommunication Engineering (MSc) student at
    University of Granada. He defines himself as an enthusiast of space-related technology and he would like to focus his professional career on the space industry when he finishes his studies.

    He is enrolled in an aerospace developing group at University of Granada called GranaSAT. This group isformed by students and professors with the goal of designing and developing a Cubesat mission. Currently, Emilio is developing his master's thesis about the Communications System of the Granasat Cubesat and the satellite-earth link: designing the Cubesat communication hardware, defining the link budget and improving their ground station capabilities in order to reach a reliable communication.

    The SatNOGS team is looking forward for the expertise and know-how Emilio brings to our project.

    We welcome all contributors that would like to be involved in the SatNOGS project and we would like to encourage all parties interested in satellite communications to join our community of developers.

  • SatNOGS rotator tracking a high attitude balloon

    elkos05/13/2015 at 02:07 0 comments

    Since the conception of the SatNOGS one of our design mantras was modularity, not only we believe that the SatNOGS stack should be able use a wide variety of components but also that components should be able to used in a wide variety of applications.

    This Sunday May 1oth 2015 the SatNOGS team had the chance to test how versatile our SatNOGS rotator and control software was by tracking the Aeolus-2way High Attitude Balloon.

    Tracking was made possible by receiving APRS data from the Aeolus-2way High Attitude Balloon and converting them using a specialized script as azimuth and elevation coordinates.

    The Aeolus-2way is a high attitude balloon build by an awesome team of radio amateur high attitude balloon enthusiasts from Greece, and the help of several groups and organizations.

    IMG_0078Aeolus team preparing the Aeolus-2way payload

    The balloon launched from the center of the Peloponisos peninsula of Greece in the city of Megalopolis at Plaka airstrip at around 11:10.

    IMG_0107Aeolus-2 way launch

    The SatNOGS team was positioned 35 km (~21.7 miles) West – NorthWest of the launch site on the Antenna park near the Ano Dolianna village of Mt Parnon. An inverter was used to power two laptops sever ham radio transceivers and our SatNOGS rotator and provide sufficient power for the team's needs

    IMG_0115SatNOGS rotator tracking Aeolus-2way IMG_0114SatNOGS running on power provided by automotive inverter

    The balloon began it's descent at 34.660 meters and it's payload was successfully retrieved.

    We would like to congratulate and thank all parties involved in this high attitude balloon launch for the great team work and cooperation and especially the Aeolus team for their commitment.

    copied from the original post in SatNOGS website.

  • SatNOGS selected to participate in European Space Agency’s 2015 Summer of Code In Space

    Pierros Papadeas03/10/2015 at 16:59 0 comments

    42_digital_logo_dark_blue_sign_A
    SatNOGS is proud to participate in ESA's Summer Of Code In Space 2015 as a mentoring organization.

    ESA's Summer Of Code In Space (also known as SOCIS) is an open source development program specifically for students run by the European Space Agency Under this program. ESA funds students to write space-related code for open source projects during the northern hemisphere's summer.

    If you are eligible to participate in SOCIS and interested in contributing code to the SatNOGS project, you may start by visiting our SOCIS project ideas page witch contains a list of suggested projects. Students are welcome to provide their own ideas for projects in collaboration with the SatNOGS developer community. The major communication and coordination systems of the SatNOGS project are its community forum and its github repositories.

    We encourage every party interested to visit the SOCIS website, and follow read the list of frequently asked questions.

  • SatNOGS in FOSDEM 2015 lightning talk video

    Pierros Papadeas03/10/2015 at 16:59 0 comments

    As promised in a previous post about our project in FOSDEM 2o15, videos from presentations and talks during FOSDEM 2015 are now available and we are happy to share the video of our lightning talk.

    So, if you are interested for an introduction of the SatNOGS project don't hesitate to check out the video from our lightning talk in FOSDEM 2015.

  • New lab equipment

    Pierros Papadeas03/10/2015 at 16:57 0 comments

    Having access to an awesome 3D printer is certainly crucial for the SatNOGS project but the SatNOGS hardware is much more than 3D printed parts. To push the development of the ground station forward the core development team decided to acquire an oscilloscope, a programmable power supply and a Vector Network Analyzer

    Following our ideal of sharing resources with the community, sharing it with the local hackerspace, we decided to install our instruments to it's lab and share them with anyone interested.

    IMG_8833
    IMG_8840
    IMG_8842
    IMG_8838
    IMG_8837
    IMG_8832
    IMG_8828
    IMG_8830

    In the future we plan to include to our instruments among other things a frequency generator and a signal analyzer.

    We consider having access to a complete electromechanical lab/workspace is crucial not only for SatNOGS but for any community driven open hardware initiative.

  • SatNOGS #1 in Athens, Greece

    Pierros Papadeas01/05/2015 at 15:47 0 comments

    10 days ago we deployed a SatNOGS v2 on top of hackerspace.gr in Athens, Greece. This is the first SatNOGS deployed on the field and we couldn't help but thinking that this is a huge milestone and brings great pride to the team!

    (obviously the front cap is closed at the finished deployment)

    The deployment was pretty straightforward, with one UHF helical antenna (our VHF is still up for matching) and no SatNOGS client controlling it (still under development for connection to Network). We simply controlled it with gPredict and Gqrx. POE for powering it up and minimal weather shielding (just some silicone on and around the bolts of the box)

    We were able to track and record many different satellite passes and we encountered some software issues with our arduino homing code (see https://community.satnogs.org/t/arduino-problem-with-gpredict-and-rotctld/101/10 for details) which we hotfixed.

    Congratulations to the whole SatNOGS team for the first deployment!

  • Observation Scheduler on Network

    Pierros Papadeas10/27/2014 at 21:57 0 comments

    After a nice code push, scheduling observation functionality is now complete in SatNOGS Network website. The website is now able to dynamically calculate and schedule observation windows given a satellite for all available Ground Stations. The functionality works like this:

    The observer enters the New Observation page. After selecting a Satellite and associated Transponder desired, the observer selects the timeframe for the observation. The timeframe selection is constrained in the future with maximum width being 8 hours (this could change as we scale the Network). After hitting 'Calculate Observation' the system returns a proposed Timeline of the observation, that includes the Ground Stations to be used and their individual observational windows. For this calculation we use PyEphem library and input the Ground Station locations, Satellite TLE, and timeframe desired.

    Once the proposed timeline is reviewed and/or modified the observer can schedule the observation by hitting 'Schedule Observation'. This creates the Observation in our database as planned, together with its associated individual observations for the Stations.

    The Stations, through the Client, query the Network API frequently for scheduled individual observations.They then execute them on time, and push back the recorded data to Network, for further analysis by the Observers (making them also publicly available!)

    Optimization of the Scheduling functionality will be further pursued. Ideas like deduplication of overlapping (more than 50%) individual observations, and accounting for horizon constrains are already in the works, and will be evaluated (in terms of their efficiency) as the Network scales up.

    Check our code here and a live dev website here.
    (requires registration for testing the New Observation functionality. Feel free to abuse!)

    You can check a sceencast of the workflow in SatNOGS Network below:


  • SatNOGS now equipped with Diplexer

    Pierros Papadeas10/27/2014 at 00:16 3 comments

    We've been thinking for some time that there is no need to install two separate RTL-SDR dongles to cover both VHF and UHF. It increases power consumption on WR703N without actually having any benefit, as using two dongles simultaneously is limited by the CPU power and network bandwidth.

    A diplexer would allow the connection of a single dongle on both antennas. After studying the theory behind filters, we decided to implement a pair of Chebyshev filters. This type of filter has very steep roll-off and the maximum ripple can be a design parameter.

    The two filters, a high-pass to attenuate the VHF band and a low-pass to attenuate the UHF band, should be crossing at exactly 288MHz@-3dB. Attenuation on each band should be at least 50dB. We calculated that a 9-pole Chabyshev filter would match these requirements and started designing a prototype on Qucs. Qucs is an open source circuit simulator which helped us verify that our calculations are correct.

    LPF

    The LPF has a maximum insertion loss of 0.4dB in VHF. The attenuation in UHF is more that 60dB. Some ripple can be observed on the chart, but it should not affect reception of narrow band signals.

    HPF

    The HPF has a maximum insertion loss of 0.2 dB in UHF. The attenuation in VHF is more that 80dB.

    Special care has been taken to ensure minimal cross-talk between the two filters. The bottom layer of the PCB is a complete ground plane and two copper shieldings have been solder on top of each filter.

    Please note, that this diplexer can be used only for receiving. For transmission, a higher grade of components (high voltage caps, high current inductors) should be used.

    All source files can be found in our github repo here.

    More pics from the diplexer can be found here.

View all 26 project logs

  • 1
    Step 1

    You can check build instructions for the SatNOGS Ground Station here: 

    http://satnogs.dozuki.com/

  • 2
    Step 2

    For all software (server, services and clients) you can check install/build instructions on their respective repositories here: 

    https://github.com/satnogs

View all instructions

Enjoy this project?

Share

Discussions

dearuserhron wrote 05/20/2021 at 11:50 point

I want to summarize what I have learned from the docs. First of all, SatNOGS is just a distributed radio telescope, capable of receiving signals from space. It can not transmit, only receive.

It is still unclear, what kind of information will I get, if I install my own antenna? Weather reports?

For me, more interesting thing will be satellite messaging. But it will require ground stations to be able to transmit.

  Are you sure? yes | no

Benjamin wrote 05/27/2019 at 18:16 point

Psychotronic warfare? Need a referral anyone in mind? Someone extremely knowledgeable.

  Are you sure? yes | no

korne#AlfonLibertad wrote 11/16/2018 at 05:20 point

Saludos ¿
Este proyecto está vivo?

  Are you sure? yes | no

elkos wrote 11/20/2018 at 03:24 point

Sure thing if you check https://network.satnogs.org over 100+ stations are setup

  Are you sure? yes | no

fabian wrote 07/25/2018 at 14:27 point

very nice,

is possible using outernet data?

  Are you sure? yes | no

elkos wrote 11/20/2018 at 03:22 point

Well the thing is that SatNOGS decodes satellite transmissions that use publicly shared characteristics. Is such info available on outernet?

  Are you sure? yes | no

EngineerAllen wrote 01/26/2017 at 12:06 point

this project is like what surrey satellites tried to do

  Are you sure? yes | no

ve7cer wrote 02/03/2015 at 02:16 point

Very nice antenna system,,am a HAM and have worked all the Russian Ham Sats when they were up,,2 meter up 10 meter down,,had a bay of 4 x 10 element 2 meter antennas trying to get in moments before and after the foot print was gone,,lots of work tracking,,LOL

Charlie ve7cer

  Are you sure? yes | no

ninerDelta wrote 12/31/2014 at 00:32 point

Has anybody in this community built a SatNOG system?

  Are you sure? yes | no

Adam Fabio wrote 02/13/2015 at 04:33 point

Not yet that I know of, but you can bet that there are a few in progress - I'll be building one of my soon !

  Are you sure? yes | no

Tyler Anderson wrote 11/13/2014 at 21:54 point
Awesome job and congratulations! Now are you going to try tracking satellites from sub-orbit?

  Are you sure? yes | no

Kojote wrote 11/13/2014 at 21:24 point
Congratulations, well earned - rock on!

  Are you sure? yes | no

nGoline wrote 11/13/2014 at 21:21 point
Congrats!

  Are you sure? yes | no

Guzzi wrote 11/13/2014 at 21:21 point
Congratulations to the winning team. Let's build a lot of base stations.

  Are you sure? yes | no

erenemre wrote 11/13/2014 at 20:06 point
Congratulations!

  Are you sure? yes | no

NIKOS GIANNAKOPOULOS wrote 11/11/2014 at 22:47 point
Awesome !

  Are you sure? yes | no

KR0SIV wrote 10/17/2014 at 18:52 point
Any update on the Satellite database sub-project site?

  Are you sure? yes | no

Pierros Papadeas wrote 10/17/2014 at 19:00 point
You can check the dev site here (with real data)
http://db.satnogs.org/

We are still working on the suggestions functionality.

  Are you sure? yes | no

n0p wrote 09/09/2014 at 06:41 point
For the new electronics shield, I think it would be a nice addition to break out the unused arduino pins. For future upgrades and prototyping of other features.

  Are you sure? yes | no

Pierros Papadeas wrote 09/09/2014 at 15:01 point
Hey n0p. Indeed a breakout for the unused arduino pins could be useful in the future. We will make sure to add this on v2. If you want you can take a pass on a v2 too :)

  Are you sure? yes | no

Fotis Georgatos wrote 08/18/2014 at 19:29 point
Hi Pierros et al,

I would like to point out, that if we are to implement a many-to-many configuration, this requires scheduling on at least two levels: A) global (=task submission) B) local (=execution site).

This is for example how the LCG (LHC Computing Grid) system has been implemented, crunching tons of data coming out of CERN, for some years already. Iff a FIFO queue at local (B) level is considered sufficient, then this has already been described how it's done in paper [1]; it is relatively trivial implementation for people experienced with the gLite middleware stack. Truth be told, that solution does not take into account celestial and orbital mechanics natively, at least not in a way that would yield near-optimal scheduling. Optimality here is a far more complex problem, which should rather be solved by the groups of users and resource owners. To do that, the concept of Virtual Organizations that grid systems provide, would become handy.

In short, there can be *some* initial solution, but for optimal utilization let's all honestly expect that this is a problem that will take some man-years of effort and tuning! If you are not sure why this would take time, try to play NetworKing [2] and you will understand ;-)

keep up,
Fotis

[1] Solomos, N. H. and Georgatos, F. (2006), System aspects of the EUDOXOS observatories network. Astronomische Nachrichten, 327: 796–799. doi: 10.1002/asna.200610673
[2] http://www.nasa.gov/multimedia/3d_resources/scan.html

  Are you sure? yes | no

ganzuul wrote 11/14/2014 at 06:25 point
Avoiding premature optimization is essential to hacking.

  Are you sure? yes | no

Jasmine Brackett wrote 08/15/2014 at 18:59 point
Hello Pierros & SatNOGS team, I hope you received your Astronaut or Not t-shirts!

Just looking at your project and wanted to remind you that by August 20th you must have the following documentation on Hackaday Projects to be considered for the next round:
- A video less than 2 minutes long describing your project.
- At least 4 Project Logs (you need at least 3 more)
- A system design document (give us a visual overview of how it all works. Highlight the design doc in the details section)
- Links to code repositories, and remember to mention any licenses or permissions needed for your project. For example, if you are using software libraries you need to document that information.

You should also try to highlight how your project is 'Connected' and 'Open' in the details and video.

Good luck!

  Are you sure? yes | no

Pierros Papadeas wrote 08/17/2014 at 13:34 point
Hey Jasmine,

The Video is linked (actually we made a second one too) and we will be publishing the rest of the logs by 20th of Aug. Also links to code repos are on the side.

Does the uploaded Design Document viz meet the requirements?

  Are you sure? yes | no

Marios Papachristou wrote 08/12/2014 at 22:04 point
A great project from ardent developers!

  Are you sure? yes | no

Fotis Georgatos wrote 08/02/2014 at 11:30 point
Hello folks,

The idea of using 100s of SatNOGS together for tracking "whatever" has been buzzing in my mind, after the recent "astroexormisi" event in Mt. Elikonas, Greece, of last week!

There are a zillion of approaches to take about how to run such a setup and I'm growingly convinced that the best way may be to allow a bouquet of technologies to co-exist together.

I started looking at SPIKE and found out it's already 25 years old technology and many more things have sprung up in the meantime, see [1] [2] [3]. Windows of Opportunity (WoP) are an objective to highlight and calculating celestial and orbital mechanics may be the holy grail of this business. Subgroups of SatNOGs may be homogeneous or heterogenous, which affects scheduling dearly [4]. Finally, efforts to integrate observations with data reductions and network transfers should be overlooked and may become relevant [5].

Let me explain:
* This is by far and large a Multi-Objective-Optimization problem
* There are multiple scheduling platforms (SPIKE, ASPEN, Raptor/TALON)
* There are plenty of planning languages that could be of interest (ANML, PDDL, NDDL, AML)
* It is not clear if a push or pull scheduling (ref. "Condor") mechanism is optimal in efficiency
So, neither would ever any single approach be optimal for everybody at the same time!

In short, let's keep the current open API (congrats for that) and, build upon it multiple implementations, perhaps even allowing different coordinated groups to tackle this!

Thanks for reading the long email, F.

Ref.
[1] http://scholar.google.gr/scholar?q=SPIKE+Intelligent+Scheduling
[2] The Deep Space Network Scheduling Problem
http://www.aaai.org/Papers/AAAI/2005/IAAI05-009.pdf
[3] http://aspen.jpl.nasa.gov/
[4] http://scholar.google.gr/scholar?q=htn+telescope+scheduling
[5] https://www.google.gr/search?q=System+aspects+of+the+EUDOXOS+observatories+network

  Are you sure? yes | no

Similar Projects

Does this project spark your interest?

Become a member to follow this project and never miss any updates