Changes

Jump to navigation Jump to search
m
Remove time for Systems since it will consistently change
Line 22: Line 22:     
== Satsurdays and Team Meetings ==
 
== Satsurdays and Team Meetings ==
We have team-wide meetings '''every Saturday at noon in [https://maps.app.goo.gl/hj8P2qSLKHK18MRk6 ES3]'''! Satsurdays is a great opportunity to come together as a group and get everyone on the same page, and it's also where we most often make big announcements. In addition to Satsurdays, each of our subteams have weekly meetings which you can find in the Satellites Events Calendar.  
+
We have team-wide meetings '''every Saturday at 11am in [https://maps.app.goo.gl/hj8P2qSLKHK18MRk6 ES3]'''! Before each meeting we'll also have '''brunch at 10am at Lakeside''' before walking over to ES3. Satsurdays is a great opportunity to come together as a group and get everyone on the same page, and it's also where we most often make big announcements. In addition to Satsurdays, each of our subteams have weekly meetings which you can find in the Satellites Events Calendar.  
    
== What is a CubeSat? ==
 
== What is a CubeSat? ==
Line 34: Line 34:     
=== Attitude Determination and Control (ADCS) ===
 
=== Attitude Determination and Control (ADCS) ===
[[File:Magnetorquer.jpg|thumb|A magnetorquer board from Sapling-2; those tiny lines are the coils of wire that generate a magnetic field!]]
+
[[File:Magnetorquer.jpg|thumb|A magnetorquer board from Sapling-2; those lines are the coils of wire that generate a magnetic field!]]
 
Slack Channel: [https://ssi-teams.slack.com/messages/satellites-adcs satellites-adcs]
 
Slack Channel: [https://ssi-teams.slack.com/messages/satellites-adcs satellites-adcs]
    
Subteam Lead: Grant Regen
 
Subteam Lead: Grant Regen
   −
Welcome! As it says in the name, the ADCS subteam is focused on two major parts of our on-orbit operations: figuring out the orientation of the satellite, and controlling this orientation. This is a super important part of any satellite, especially ones that takes pictures like ours. For our past missions we've used sun sensors for our attitude determination and magnetorquer boards for control. The sun sensors measure how much light is hitting each of the six sides of the satellite; by combining information from all six sides, we can roughly determine where the sun is in relation to the satellite, and thus which direction we're pointing. Magnetorquer boards spin the satellite by creating a magnetic field that interacts with the Earth's magnetic field. This interaction creates a force on the satellite, spinning it around an axis.
+
Meetings: Thursday evenings in ES3 (with Avionics)
   −
We have a BUNCH of projects for this subteam for the upcoming SAMWISE mission! In addition to creating new magnetorquer boards for a 2U, we're also developing reaction wheels for more precise pointing ability. Reaction wheels are small spinning disks attached to electric motors that rotate the satellite due to the conservation of angular momentum. Since the angular momentum of the satellite stays the same, when you spin the disk in one direction the satellite spins in the opposite direction! This allows us to control which way the satellite points with a lot more precision than just with magnetorquers. We're also developing a star tracker for our attitude determination, which takes pictures of the stars and figures out where the satellite is pointing. There's tons of super cool stuff happening with this subteam, so definitely join the slack to get started!
+
Welcome! As it says in the name, the ADCS subteam is focused on two major parts of our on-orbit operations: figuring out the orientation of the satellite, and controlling this orientation. This is a super important part of any satellite, especially ones that takes pictures like ours. For our past missions we've used sun sensors for our attitude determination and magnetorquer boards for control. The sun sensors measure how much light is hitting each of the six sides of the satellite and combine this information to roughly determine where the sun is in relation to the satellite. Magnetorquer boards spin the satellite by creating a magnetic field that interacts with the Earth's magnetic field. This interaction creates a torque on the satellite, spinning it around an axis.
 +
 
 +
We have a BUNCH of projects for this subteam for the upcoming SAMWISE mission! In addition to creating new magnetorquer boards, '''we're developing reaction wheels and thrusters (!!!)''' for more precise pointing ability. Reaction wheels are small spinning disks attached to electric motors that rotate the satellite very precisely. The thrusters we're working on are vacuum arc thrusters, which work by ionizing a solid metal propellant and then accelerating those ions with a magnetic field. We're also developing a star tracker for our attitude determination, which takes pictures of the stars and figures out where the satellite is pointing. There's tons of super cool stuff happening with this subteam, so definitely join the slack to get started!
    
=== Avionics ===
 
=== Avionics ===
Line 47: Line 49:     
Subteam Lead: Hunter Liu
 
Subteam Lead: Hunter Liu
 +
 +
Meetings: Thursday evenings in ES3 (with ADCS)
    
The avionics subteam focuses on all of the hardware on the satellite that makes the electronics system work! This "bus" hardware includes power, compute, and sensing systems. Our current flight computer, the central computer of the satellite that handles all information coming in and out and executes commands, is a modified PyCubed microcontroller that runs our CircuitPython flight code. The satellite is powered by a solar power system based off of the LT3652 chip and some NCR18650B batteries, and it also includes a sensing system with sun sensors, an inertial measurement unit (IMU), and thermistors to measure temperature.
 
The avionics subteam focuses on all of the hardware on the satellite that makes the electronics system work! This "bus" hardware includes power, compute, and sensing systems. Our current flight computer, the central computer of the satellite that handles all information coming in and out and executes commands, is a modified PyCubed microcontroller that runs our CircuitPython flight code. The satellite is powered by a solar power system based off of the LT3652 chip and some NCR18650B batteries, and it also includes a sensing system with sun sensors, an inertial measurement unit (IMU), and thermistors to measure temperature.
Line 57: Line 61:     
Subteam Lead: Niklas Vainio
 
Subteam Lead: Niklas Vainio
 +
 +
Meetings: Tuesday evenings after systems meeting (with Structures)
    
Welcome to the payload subteam! The payload often defines the mission of the satellite, so it's basically the most important part :) These payloads can be anything from telescopes like Hubble to communication systems like Starlink. Our recent satellites have largely focused on low-cost camera systems and radio modules. This subteam covers a huge variety of topics, so no matter your interests definitely join the Slack and reach out!  
 
Welcome to the payload subteam! The payload often defines the mission of the satellite, so it's basically the most important part :) These payloads can be anything from telescopes like Hubble to communication systems like Starlink. Our recent satellites have largely focused on low-cost camera systems and radio modules. This subteam covers a huge variety of topics, so no matter your interests definitely join the Slack and reach out!  
Line 72: Line 78:     
Subteam Leads: Jacob Mukobi, Siolé Mayeski, and Jeremy Merritt
 
Subteam Leads: Jacob Mukobi, Siolé Mayeski, and Jeremy Merritt
 +
 +
Meetings: Tuesday evenings after systems meeting (with Payload)
    
Hi! This is the structures subteam, where we design and build the core mechanical components of the satellite. The structure holds everything together and allows for the satellite to fit into CubeSat standard deployers, which push the satellite out of the spacecraft in orbit. If you're interested in mechanical engineering this is definitely the subteam for you, but of course everyone is welcome!
 
Hi! This is the structures subteam, where we design and build the core mechanical components of the satellite. The structure holds everything together and allows for the satellite to fit into CubeSat standard deployers, which push the satellite out of the spacecraft in orbit. If you're interested in mechanical engineering this is definitely the subteam for you, but of course everyone is welcome!
Line 82: Line 90:  
Subteam Lead: kinda everyone!
 
Subteam Lead: kinda everyone!
   −
The systems subteam is the subteam for everyone! We focus on making sure all the different pieces of the satellite work together and juggle the demands of various other subsystems. For example, our payload needs a certain amount of power but so does our ADCS system; the systems subteam is where these two groups can come together and work out who gets the available resources. In addition to these kinds of engineering discussions, we also work on administrative and operational topics.
+
The systems subteam is the subteam for everyone! We focus on making sure all the different pieces of the satellite work together and juggle the demands of various other subsystems. For example, our payload needs a certain amount of power but so does our ADCS system; the systems subteam is where these two groups can come together and work out who gets the available resources. In addition to these kinds of engineering discussions, we also work on administrative and operational topics.  
 
= Missions =
 
= Missions =
 
== Current Mission: SAMWISE ==
 
== Current Mission: SAMWISE ==
Our current mission is SAMWISE, a 2U CubeSat (10cm x 10cm x 20cm rectangle) with a bunch of super cool technologies. Stay tuned.
+
Our current mission is SAMWISE, a 2U CubeSat (10cm x 10cm x 20cm rectangle) with a bunch of super cool technologies. Stay tuned for more info, but here's some big ticket items:
 +
 
 +
* Thrusters 🚀
 +
* Selfie stick 🤳 with 12MP cameras
 +
* Deployable structures (solar panels that fold out!)
 +
* High power radio
 +
* It's literally twice as big as our last satellites so it must be twice as good right?
 
== Past Missions ==
 
== Past Missions ==
   Line 109: Line 123:     
The avionics on Sapling-1 include a PyCubed V4 main flight computer, NCR18650B batteries, and solar power based off of the LT3652 chip.  
 
The avionics on Sapling-1 include a PyCubed V4 main flight computer, NCR18650B batteries, and solar power based off of the LT3652 chip.  
  −
Paragraph on the software
      
The payload of Sapling-1 consisted of a [https://coral.ai/products/dev-board-mini Google Coral Dev Board Mini] computer and a [https://coral.ai/products/camera/ Google Coral Camera]. This payload was selected to demonstrate on-orbit image processing and selection using an AI filter. The Coral would use this processing to select a single "best" image out of a series of images taken, reducing the amount of data needed to be transmitted down to Earth. The camera was mounted on the Z- face of the satellite opposite the antennas (towards the table in the photo on the right).
 
The payload of Sapling-1 consisted of a [https://coral.ai/products/dev-board-mini Google Coral Dev Board Mini] computer and a [https://coral.ai/products/camera/ Google Coral Camera]. This payload was selected to demonstrate on-orbit image processing and selection using an AI filter. The Coral would use this processing to select a single "best" image out of a series of images taken, reducing the amount of data needed to be transmitted down to Earth. The camera was mounted on the Z- face of the satellite opposite the antennas (towards the table in the photo on the right).
Line 116: Line 128:  
Sapling-1's structure comprised four anodized aluminum rails with slots on the interior that support the avionics. The rails were held together by the side panels, which contained the solar panels and GPS modules. The Z+ side panel (pointing upwards in the photo on the right) contained the tape spring radio antennas tuned for the 433 MHz radio.
 
Sapling-1's structure comprised four anodized aluminum rails with slots on the interior that support the avionics. The rails were held together by the side panels, which contained the solar panels and GPS modules. The Z+ side panel (pointing upwards in the photo on the right) contained the tape spring radio antennas tuned for the 433 MHz radio.
   −
=== Sequoia: 2019–2020 ===
+
=== Sequoia: 2018–2020 ===
 
Sequoia was a planned 3U CubeSat that would demonstrate on-board image classification and processing with updateable machine learning models. The goal of the project was to obtain a high volume of scientifically important imagery for ecological and climatology research. Researchers many times have no need of images saturated with clouds or uninteresting areas—so why not filter them out with a convolutional neural network? Sequoia’s deep learning with images taken by the satellite would be retained, with improvements implemented on-orbit. SSI worked on developing deep learning models for forest fire risk assessment and detection and a number of other applications. The mission architecture was user definable with the operator specifying desirable image locations or types and resolutions, and the satellite planned to maximize delivery of fully open-source images.  
 
Sequoia was a planned 3U CubeSat that would demonstrate on-board image classification and processing with updateable machine learning models. The goal of the project was to obtain a high volume of scientifically important imagery for ecological and climatology research. Researchers many times have no need of images saturated with clouds or uninteresting areas—so why not filter them out with a convolutional neural network? Sequoia’s deep learning with images taken by the satellite would be retained, with improvements implemented on-orbit. SSI worked on developing deep learning models for forest fire risk assessment and detection and a number of other applications. The mission architecture was user definable with the operator specifying desirable image locations or types and resolutions, and the satellite planned to maximize delivery of fully open-source images.  
    
Project materials can be found in the [https://github.com/stanford-ssi/Sequoia Sequoia GitHub].
 
Project materials can be found in the [https://github.com/stanford-ssi/Sequoia Sequoia GitHub].
   −
=== POINTR: [year]–2018 ===
+
=== POINTR: 2016–2018 ===
 
The Satellites team developed various [[Optical Communications]] technologies, culminating in the launch of [[POINTR]]. This was a 1U segment of a 3U CubeSat launched in 2018, but it unfortunately never connected with ground control due to improper orbital insertion from the launch provider.  
 
The Satellites team developed various [[Optical Communications]] technologies, culminating in the launch of [[POINTR]]. This was a 1U segment of a 3U CubeSat launched in 2018, but it unfortunately never connected with ground control due to improper orbital insertion from the launch provider.  
  
2

edits

Navigation menu