Stanford SSI Wiki - User contributions [en]

History of End Station III

2025-06-19T07:11:08Z

Lskaling: Updated with more info

This page documents the history of ES3, as found during research by curious SSI members.

=== Founding and Construction ===
ES3 was constructed as part of the HEPL physics lab in the 1960s, and believed to be operational by 1972 [https://web.archive.org/web/20080221175405/www.stanford.edu/group/hepl/HEPL_History_opt.pdf (source)]. At the time, HEPL had buildings across modern day e-quad, as shown in [https://purl.stanford.edu/mx948nt2935 this image]. The only buildings that remain today are ES3 (ES2 appears to be a later addition), and Varian buildings (which have received major renovations).
[[File:Screenshot 2025-06-18 at 10.24.57 PM.png|thumb|Side profile of the expanded tunnel]]
The reason for HEPL construction coinciding with SLAC construction is unclear. SLAC was built in

=== Accelerators ===
The accelerators in ES3 are unclear. There was a series of linear accelerators developed starting in the 1940s. It's unclear where these were developed ([https://web.archive.org/web/20150622184228/http://web.stanford.edu/group/hepl/documents/HEPL_History_opt.pdf the first in the basement of main quad]), however they predate ES3 and later were installed at SLAC's, which has [https://www6.slac.stanford.edu/about/our-story/history completed before 1693], before ES3 was finished.

=== Gravity Probe B ===
Gravity Probe B was a satellite designed in collaboration between Stanford, NASA, and Lockheed Martin to test theories of General Relativity [https://en.wikipedia.org/wiki/Gravity_Probe_B (source)]. It was first proposed in the 60s and didn't launch until 2004, and is believed to be housed in ES3 through development in the 1980s as a facility with vibration and temperature control sufficient for calibrating the spacecraft. A marker in ES3 marked the location of the accelerometer calibration, precisely determining the gravity at a point in ES3.

=== Dark Matter Research ===
[[File:Screenshot 2025-06-18 at 9.39.09 AM.png|thumb|Tunnel schematic on south side of ES3, including tunnel A expansion]]
In the 1990s, ES3 became the home of dark matter research. In particular, the researchers expanded Tunnel A to be larger and more cavernous, allowing detection of cosmic rays with shielding provided by the Earth. Reports here suggest that the tunnels were 10m before expansion, and expanded to 30m. Details of the experiement are in [https://lss.fnal.gov/archive/thesis/1900/fermilab-thesis-1996-60.pdf#:~:text=Tunnels%20Band%20C%20are%20roughly,entrances%20of%20all%20of%20the this paper].

=== SSI Moves In ===
SSI was originally working out of the room in Durand, which suited the club as it originally was a space enthusiast club than a project based engineering club. However, as the club began pursuing engineering projects, the space quickly became a limiting factor.

In 2017, SSI moved into ES3. Unsubstantiated lore in the club suggests this was due to an incident where a high schooler hurt their hand while drilling, which eventually caused the university to realize the space was not suited for engineering work. SSI was given the M300 suite [https://hepl.stanford.edu/news/stanfords-student-space-initiative-group-sets-shop-hepl-southend-station-iii#:~:text=An%20energetic%20group%20of%20Stanford,of%20HEPL%20South%2FEnd%20Station%20III <nowiki>[source]</nowiki>].
[[File:August 2022 Basement.png|thumb|East side of SSI's Dragon workspace, 2022]]
As the club grew, SSI expanded slowly into the basement. It's suspected this was in 2018 or 2019, and there was never a formal agreement to use the downstairs space but the building manager graciously let us as it was underutilized. This downstairs space was named Dragon, and the upstairs space ISS.

=== Solar Instillation ===
[[File:Rooftop Solar.png|thumb|Aerial view of solar on ES3 roof]]
ES3 was chosen as one of 15 buildings on campus to have solar installed on the roof. Installation occurred in 2016, and is now among the largest rooftop solar arrays on campus. [https://news.stanford.edu/stories/2017/04/sun-rooftop-photovoltaic-panels-electricity-stanford (Source)]

=== Construction ===
SSI's involvement in construction began in 2023. Initial plans involved moving SSI either to a basement room under M300 or the M200 suite, the latter of which the construction crews eventually selected. Due to the demolition of Flight Club's Cedar Hall at the same time, at one point the Stanford administration also tried to add Flight Club to M200, but pushback from both clubs eventually prompted the administration to give Flight Club a room in Durand instead.

The first phase of the construction involved the refurbishment of M200, where walls were removed and new appliances installed. Partway through this phase, SSI's downstairs lab was briefly relocated to the south side of the basement, while construction began on the north side to demolish the restrooms and closets,and refurbish the north tunnel for the [TODO] lab.
[[File:ES3 Basement September 2024.jpg|thumb|ES3 Basement September 2024. SSI has now moved to the South East corner shown on the left covered by tarps]]
[[File:November 2024 M200.png|thumb|M200 after refurbishment before SSI moved in, November 2024]]
In phase two of construction, SSI moved from the basement into M200, which would be the new second home from the club. M300 was unchanged through it all. SSI was also given a shipping container outside ES3 for long-term storage.

File:November 2024 M200.png

2025-06-19T07:10:25Z

Lskaling:

November 2024 M200

File:ES3 Basement September 2024.jpg

2025-06-19T07:08:48Z

Lskaling:

ES3 Basement September 2024

File:Rooftop Solar.png

2025-06-19T07:05:18Z

Lskaling:

Photo of solar on ES3 roof

File:August 2022 Basement.png

2025-06-19T07:00:01Z

Lskaling:

East side of SSI's Dragon workspace, 2022

File:Screenshot 2025-06-18 at 10.24.57 PM.png

2025-06-19T06:25:22Z

Lskaling:

From https://farm4.static.flickr.com/3173/2561293811_f1542a9f77_o.png

History of End Station III

2025-06-19T06:21:35Z

Lskaling:

This page documents the history of ES3, as found during research by curious SSI members.

=== Founding and Construction ===
ES3 was constructed as part of the HEPL physics lab in the 1960s. At the type HEPL had buildings across modern day e-quad, ES3 and ES2 being the only two remaining.

The reason for HEPL construction coinciding with SLAC construction is unclear. SLAC was built in [[File:thumbnail.jpg|thumb|Link to full viewer|link=https://purl.stanford.edu/mx948nt2935]]
=== Mark Accelerators ===

=== Dark Matter Reearch ===
[[File:Mx948nt2935 00 0001-2.jpg|thumb|Tunnel schematic on south side of ES3, including tunnel A expansion]]
In the 1990s, ES3 became the home of dark matter research. In particular, the researchers expanded Tunnel A to be larger and more cavernous, allowing detection of cosmic rays with shielding provided by the Earth. Reports here suggest that the tunnels were 10m before expansion [TODO find schematics of that]

=== SSI Moves In ===
SSI was originally working out of the room in Durand, which suited the club as it originally was a space enthusiast club than a project based engineering club. However as the club began pursuing enineering projects, the space quickly became a limiting factor.

In 2017, SSI moved into ES3. Unsubstantiated lore in the club suggests this was due to an incident where a high schooler hurt their hand while drilling, which eventually caused the university to realize the space was not suited for engineering work. SSI was given the M300 suite [https://hepl.stanford.edu/news/stanfords-student-space-initiative-group-sets-shop-hepl-southend-station-iii#:~:text=An%20energetic%20group%20of%20Stanford,of%20HEPL%20South%2FEnd%20Station%20III <nowiki>[source]</nowiki>].

As the club grew, SSI expanded slowly into the basement. It's suspected this was in 2018 or 2019, and there was never a formal agreement to use the downstairs space but the building manager graciously let us as it was underutilized. This downstairs space was named Dragon, and the upstairs space ISS.

=== Construction ===
SSI's involvement in construction began in 2023. Lawton Skaling, Matthew Nguyen, and Amy Huang met with the construction planners and coordinated SSI's continued presence during the move. Initial plans involved moving SSI either to a basement room under M300 or the M200 suite, the latter of which the construction crews eventually selected. Due to demolition of Flight Club's Cedar Hall at the same time, at one point the Stanford administration also tried to add Flight Club to M200, but pushback from both clubs eventually prompted the administration to give Flight Club a room in Durand instead.

The first phase of the construction involved the refurbishment of M200, where walls were removed and new appliances installed. Partway through this phase, SSI's downstairs lab was briefly relocated to the south side of the basement, while construction began on the north side to demolish the restrooms and closets,and refurbish the north tunnel for the [TODO] lab.

In phase two of construction, SSI moved from the basement into M200, which would be the new second home from the club. M300 was unchanged through it all. SSI was also given a shipping container outside ES3 for long-term storage.

File:Mx948nt2935 00 0001-2.jpg

2025-06-19T06:20:50Z

Lskaling:

From https://purl.stanford.edu/mx948nt2935

History of End Station III

2025-06-19T06:16:29Z

Lskaling:

This page documents the history of ES3, as found during research by curious SSI members.

=== Founding and Construction ===
ES3 was constructed as part of the HEPL physics lab in the 1960s. At the type HEPL had buildings across modern day e-quad, ES3 and ES2 being the only two remaining.

The reason for HEPL construction coinciding with SLAC construction is unclear. SLAC was built in

[https://purl.stanford.edu/mx948nt2935 View the image at Stanford Digital Repository]

=== Mark Accelerators ===

=== Dark Matter Reearch ===
[[File:Screenshot 2025-06-18 at 9.39.09 AM.png|thumb|Tunnel schematic on south side of ES3, including tunnel A expansion]]
In the 1990s, ES3 became the home of dark matter research. In particular, the researchers expanded Tunnel A to be larger and more cavernous, allowing detection of cosmic rays with shielding provided by the Earth. Reports here suggest that the tunnels were 10m before expansion [TODO find schematics of that]

=== SSI Moves In ===
SSI was originally working out of the room in Durand, which suited the club as it originally was a space enthusiast club than a project based engineering club. However as the club began pursuing enineering projects, the space quickly became a limiting factor.

In 2017, SSI moved into ES3. Unsubstantiated lore in the club suggests this was due to an incident where a high schooler hurt their hand while drilling, which eventually caused the university to realize the space was not suited for engineering work. SSI was given the M300 suite [https://hepl.stanford.edu/news/stanfords-student-space-initiative-group-sets-shop-hepl-southend-station-iii#:~:text=An%20energetic%20group%20of%20Stanford,of%20HEPL%20South%2FEnd%20Station%20III <nowiki>[source]</nowiki>].

As the club grew, SSI expanded slowly into the basement. It's suspected this was in 2018 or 2019, and there was never a formal agreement to use the downstairs space but the building manager graciously let us as it was underutilized. This downstairs space was named Dragon, and the upstairs space ISS.

=== Construction ===
SSI's involvement in construction began in 2023. Lawton Skaling, Matthew Nguyen, and Amy Huang met with the construction planners and coordinated SSI's continued presence during the move. Initial plans involved moving SSI either to a basement room under M300 or the M200 suite, the latter of which the construction crews eventually selected. Due to demolition of Flight Club's Cedar Hall at the same time, at one point the Stanford administration also tried to add Flight Club to M200, but pushback from both clubs eventually prompted the administration to give Flight Club a room in Durand instead.

The first phase of the construction involved the refurbishment of M200, where walls were removed and new appliances installed. Partway through this phase, SSI's downstairs lab was briefly relocated to the south side of the basement, while construction began on the north side to demolish the restrooms and closets,and refurbish the north tunnel for the [TODO] lab.

In phase two of construction, SSI moved from the basement into M200, which would be the new second home from the club. M300 was unchanged through it all. SSI was also given a shipping container outside ES3 for long-term storage.

History of End Station III

2025-06-19T06:11:20Z

Lskaling: Initial release

This page documents the history of ES3, as found during research by curious SSI members.

=== Founding and Construction ===
ES3 was constructed as part of the HEPL physics lab in the 1960s. At the type HEPL had buildings across modern day e-quad, ES3 and ES2 being the only two remaining.

The reason for HEPL construction coinciding with SLAC construction is unclear. SLAC was built in

=== Mark Accelerators ===

=== Dark Matter Reearch ===
[[File:Screenshot 2025-06-18 at 9.39.09 AM.png|thumb|Tunnel schematic on south side of ES3, including tunnel A expansion]]
In the 1990s, ES3 became the home of dark matter research. In particular, the researchers expanded Tunnel A to be larger and more cavernous, allowing detection of cosmic rays with shielding provided by the Earth. Reports here suggest that the tunnels were 10m before expansion [TODO find schematics of that]

=== SSI Moves In ===
SSI was originally working out of the room in Durand, which suited the club as it originally was a space enthusiast club than a project based engineering club. However as the club began pursuing enineering projects, the space quickly became a limiting factor.

In 2017, SSI moved into ES3. Unsubstantiated lore in the club suggests this was due to an incident where a high schooler hurt their hand while drilling, which eventually caused the university to realize the space was not suited for engineering work. SSI was given the M300 suite [https://hepl.stanford.edu/news/stanfords-student-space-initiative-group-sets-shop-hepl-southend-station-iii#:~:text=An%20energetic%20group%20of%20Stanford,of%20HEPL%20South%2FEnd%20Station%20III <nowiki>[source]</nowiki>].

As the club grew, SSI expanded slowly into the basement. It's suspected this was in 2018 or 2019, and there was never a formal agreement to use the downstairs space but the building manager graciously let us as it was underutilized. This downstairs space was named Dragon, and the upstairs space ISS.

=== Construction ===
SSI's involvement in construction began in 2023. Lawton Skaling, Matthew Nguyen, and Amy Huang met with the construction planners and coordinated SSI's continued presence during the move. Initial plans involved moving SSI either to a basement room under M300 or the M200 suite, the latter of which the construction crews eventually selected. Due to demolition of Flight Club's Cedar Hall at the same time, at one point the Stanford administration also tried to add Flight Club to M200, but pushback from both clubs eventually prompted the administration to give Flight Club a room in Durand instead.

The first phase of the construction involved the refurbishment of M200, where walls were removed and new appliances installed. Partway through this phase, SSI's downstairs lab was briefly relocated to the south side of the basement, while construction began on the north side to demolish the restrooms and closets,and refurbish the north tunnel for the [TODO] lab.

In phase two of construction, SSI moved from the basement into M200, which would be the new second home from the club. M300 was unchanged through it all. SSI was also given a shipping container outside ES3 for long-term storage.

File:Screenshot 2025-06-18 at 9.39.09 AM.png

2025-06-18T16:40:26Z

Lskaling:

Image of the end of ES3 from research paper https://lss.fnal.gov/archive/thesis/1900/fermilab-thesis-1996-60.pdf#:~:text=Tunnels%20Band%20C%20are%20roughly,entrances%20of%20all%20of%20the

How to Join SSI

2024-06-19T04:42:47Z

Lskaling: removed slack join link

Hello! There are a few things you need to do if you'd like to have full access to SSI's resources as a member. :-)

=Becoming an official member=


# Join the SSI Slack [https://sites.google.com/d/1jYHC2-QvA_n4n-FCrT6HhYskoRkJzElO/p/1FHpUBgY0GufAMKVPiomVJ09WBQvxRyPp/edit here].
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].
# Apply for access to ESIII. This includes completing safety training and paperwork. Find the instructions for that [https://sites.google.com/stanford.edu/ssi/end-station-iii/keycard-access-for-es3?authuser=1 here]

# Take a look at [https://s3-us-west-1.amazonaws.com/habmc/assets/assi.pdf Approaching SSI], a handbook for new (and prospective) members!

=Resources=

== [https://sites.google.com/d/1jYHC2-QvA_n4n-FCrT6HhYskoRkJzElO/p/1FHpUBgY0GufAMKVPiomVJ09WBQvxRyPp/edit Slack] ==

{{nowrap|Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like {{slack-channel|rockets}}), which allow us to push out general updates to everyone interested in the rockets team and direct messages which allows one to one or smaller group communication. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time! Have any questions? Feel free to ask the Co-Presidents! {{Leadership
| Presidents = true
}}}}

We highly recommend joining the channels of whichever teams you are interested in! To see what a list of what channels there are to join, check out the [[Slack Directory]].

'''[https://sites.google.com/d/1jYHC2-QvA_n4n-FCrT6HhYskoRkJzElO/p/1FHpUBgY0GufAMKVPiomVJ09WBQvxRyPp/edit Join the SSI Slack here.]'''

==[https://stanfordssi.org/ Calendar]==
Home to all of our events across all our teams.

== [https://stanfordssi.org/leadership SSI Leadership] ==
Find out who's in charge of things you're interested in and contact them! You can find all of us on Slack as well.

==The Wiki==

This wiki is a great place to find guides, overviews, and generally useful documentation on SSI projects. Many of the most current plans and docs are in the drive though.

==[https://drive.google.com/drive/u/0/folders/0AOLUM8S1U9vqUk9PVA SSI Drive]==

The drive contains a lot of important documentation for each team. We are trying to put more emphasis on using the wiki as a place for longer-term knowledge storage. If you don't have access, ask in {{slack-channel|SSIT}}

== [https://stanfordssi.org/mailing-list The Mailing List] ==
We use SSI General for organization-wide announcements, and it's a good way to hear about events that get lost in the depths of slack (Slack is still by and large the primary mode of communication for most of us though).

== [https://sites.google.com/d/1jYHC2-QvA_n4n-FCrT6HhYskoRkJzElO/p/1QCURHVQATK6OsdyFKMwCyDortR7lk95l/edit?authuser=1 End Station III] ==

End Station III (also known as ES3) can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. End Station III houses work sessions, team meetings, and project storage. Keycard access is required to access the building.

[[File:whereisesiii.png|thumb|left]]

== [[Find a Project]] ==

If you're ever feeling overwhelmed or lost about all the things going on in SSI, use this page to see what's what! Reach out to someone working on a project you're interested in and they'll help you get started. If you have questions or just want to chat, poke any leadership member.

[[Category:Getting started]]

Flying Phoque 6

2024-06-06T04:44:32Z

Lskaling: /* Pre-Flight Checklist */

[[File:Flying Phoque 6.png|thumb|PCB Layout]]
[[File:Flying Phoque 6 Labels.png|thumb|External interfaces]]

== Software ==
The software repo is [https://github.com/LSkaling/Flying-Phoque-6.0/tree/main here]. The board is programmed using Platform IO in VS code.

== Setup ==
Setup instructions assume board is just being used for data logging (TODO: add instructions to use as flight computer)

# Ensure the board is not contacting any metal surfaces
# Check that the internal power header pins aren't connected (see photo)
# Insert SD card into Teensy
# Connect the Teensy to a computer via USB
# Upload firmware using Platform IO
# Data should be logging, and serial data being sent to the computer. Open the Serial monitor to check that everything is working.
# Unplug the teensy from the computer. Verify the SD card has data written to it by plugging it into a computer and opening the file.
# Put the SD card back into the Teensy (it's okay to leave the program, a new program file is created every time it is turned on)
# Insert the internal power header jumper cap to have the Teensy powered by the battery
# Screw a connector into the power in port
# Verify polarity! Red on top, GND on bottom
# (Optionally) add any arming circuitry to the power port connector, such as a magswitch or toggle switch
# Plug the battery in and turn on. Unplug immediately if the light does not turn on and buzzer doesn't beep
# Teensy should be in fully operational data logging state. It will have slow chirps indicating that it's logging data, and a green flashing LED. Fast beeps and a red LED indicate an error. If that happens, unplug, remove the internal power header jumper cap, and plug in with USB to view serial data.

== Pre-Flight Checklist ==
Packing list:

* Board
* JST Connector
* Batteries
* Battery charger
* Arming switch
* Jumper Caps
* Micro USB cable + adapters for computer
* MicroSD card
* MicroSD card adapter for computer
* Electrical tape
* Multimeter
* Avionics mount for board

Integration:

* Battery fully charged (around 8.4v)
* SD card has sufficient capacity (Data logs generate about 10 megabytes per hour)
* SD installed into the slot
* Internal power jumper installed (top right)
* Board powered on, displays green LED and correct chips, and then powered off again
* SD card checked to verify data is being logged properly. Re-inserted into SD card slot, and retained with electrical tape.

Pre-launch:

# Arm the switch
# Correct beeping pattern (slow chirps spaced a few seconds apart, with a green LED)
#

Flying Phoque 6

2024-06-06T04:40:13Z

Lskaling:

[[File:Flying Phoque 6.png|thumb|PCB Layout]]
[[File:Flying Phoque 6 Labels.png|thumb|External interfaces]]

== Software ==
The software repo is [https://github.com/LSkaling/Flying-Phoque-6.0/tree/main here]. The board is programmed using Platform IO in VS code.

== Setup ==
Setup instructions assume board is just being used for data logging (TODO: add instructions to use as flight computer)

# Ensure the board is not contacting any metal surfaces
# Check that the internal power header pins aren't connected (see photo)
# Insert SD card into Teensy
# Connect the Teensy to a computer via USB
# Upload firmware using Platform IO
# Data should be logging, and serial data being sent to the computer. Open the Serial monitor to check that everything is working.
# Unplug the teensy from the computer. Verify the SD card has data written to it by plugging it into a computer and opening the file.
# Put the SD card back into the Teensy (it's okay to leave the program, a new program file is created every time it is turned on)
# Insert the internal power header jumper cap to have the Teensy powered by the battery
# Screw a connector into the power in port
# Verify polarity! Red on top, GND on bottom
# (Optionally) add any arming circuitry to the power port connector, such as a magswitch or toggle switch
# Plug the battery in and turn on. Unplug immediately if the light does not turn on and buzzer doesn't beep
# Teensy should be in fully operational data logging state. It will have slow chirps indicating that it's logging data, and a green flashing LED. Fast beeps and a red LED indicate an error. If that happens, unplug, remove the internal power header jumper cap, and plug in with USB to view serial data.

== Pre-Flight Checklist ==
Packing list:

* Board
* JST Connector
* Batteries
* Battery charger
* Arming switch
* Jumper Caps
* Micro USB cable + adapters for computer
* MicroSD card
* MicroSD card adapter for computer
* Electrical tape
* Multimeter
* Avionics mount for board

Integration:

* Battery fully charged (around 8.4v)
* SD card has sufficient capacity (Data logs generate about 10 megabytes per hour)
* SD installed into the slot and retained with tape
* Internal power jumper installed (top right)
* Board powered on, displays green LED and correct chips, and then powered off again

Pre-launch:

# Arm the switch
# Correct beeping pattern (slow chirps spaced a few seconds apart, with a green LED)
#

Flying Phoque 6

2024-06-04T06:13:37Z

Lskaling: grammar

[[File:Flying Phoque 6.png|thumb|PCB Layout]]
[[File:Flying Phoque 6 Labels.png|thumb|External interfaces]]

== Software ==
The software repo is [https://github.com/LSkaling/Flying-Phoque-6.0/tree/main here]. The board is programmed using Platform IO in VS code.

== Setup ==
Setup instructions assume board is just being used for data logging (TODO: add instructions to use as flight computer)

# Ensure the board is not contacting any metal surfaces
# Check that the internal power header pins aren't connected (see photo)
# Insert SD card into Teensy
# Connect the Teensy to a computer via USB
# Upload firmware using Platform IO
# Data should be logging, and serial data being sent to the computer. Open the Serial monitor to check that everything is working.
# Unplug the teensy from the computer. Verify the SD card has data written to it by plugging it into a computer and opening the file.
# Put the SD card back into the Teensy (it's okay to leave the program, a new program file is created every time it is turned on)
# Insert the internal power header jumper cap to have the Teensy powered by the battery
# Screw a connector into the power in port
# Verify polarity! Red on top, GND on bottom
# (Optionally) add any arming circuitry to the power port connector, such as a magswitch or toggle switch
# Plug the battery in and turn on. Unplug immediately if the light does not turn on and buzzer doesn't beep
# Teensy should be in fully operational data logging state. It will have slow chirps indicating that it's logging data, and a green flashing LED. Fast beeps and a red LED indicate an error. If that happens, unplug, remove the internal power header jumper cap, and plug in with USB to view serial data.

== Pre-Flight Checklist ==
Packing list:

* Board
* JST Connector
* Batteries
* Battery charger
* Arming switch
* Jumper Caps
* Micro USB cable + adapters for computer
* MicroSD card
* MicroSD card adapter for computer
* Electrical tape
* Multimeter
* Avionics mount for board

Integration:

* Battery fully charged (around 8.4v)
* SD card has sufficient capacity (Data logs generate about 10 megabytes per hour)
* SD installed into the slot and retained with tape
* Internal power jumper installed (top right)
* Board powered on, displays green LED and correct chips, and then powered off again

Pre-launch:

# Arm the switch
# Correct beeping pattern (slow chirps spaced a few seconds apart)
#

Flying Phoque 6

2024-06-04T05:33:45Z

Lskaling: /* Software */ Added link

[[File:Flying Phoque 6.png|thumb|PCB Layout]]
[[File:Flying Phoque 6 Labels.png|thumb|External interfaces]]

== Software ==
The software repo is [https://github.com/LSkaling/Flying-Phoque-6.0/tree/main here]. The board is programmed using Platform IO in VS code.

== Setup ==
Setup instructions assume board is just being used for data logging (TODO: add instructions to use as flight computer)

# Ensure the board is not contact any metal surfaces
# Check that the internal power header pins aren't connected (see photo)
# Insert SD card into Teensy
# Connect the Teensy to a computer via USB
# Upload firmware using Platform IO
# Data should be logging, and serial data being sent to the computer. Open the Serial monitor to check that everything is working.
# Unplug the teensy from the computer. Verify the SD card has data written to it by plugging it into a computer and opening the file.
# Put the SD card back into the Teensy (it's okay to leave the program, a new program file is created every time it is turned on)
# Insert the internal power header jumper cap to have the Teensy powered by the battery
# Screw a connector into the power in port
# Verify polarity! Red on top, GND on bottom
# (Optionally) add any arming circuitry to the power port connector, such as a magswitch or toggle switch
# Plug the battery in and turn on. Unplug immediately if the light does not turn on and buzzer doesn't beep
# Teensy should be in fully operational data logging state. It will have slow chirps indicating that it's logging data, and a green flashing LED. Fast beeps and a red LED indicate an error. If that happens, unplug, remove the internal power header jumper cap, and plug in with USB to view serial data.

== Pre-Flight Checklist ==
Packing list:

* Board
* JST Connector
* Batteries
* Battery charger
* Arming switch
* Jumper Caps
* Micro USB cable + adapters for computer
* MicroSD card
* MicroSD card adapter for computer
* Electrical tape
* Multimeter
* Avionics mount for board

Integration:

* Battery fully charged (around 8.4v)
* SD card has sufficient capacity (Data logs generate about 10 megabytes per hour)
* SD installed into the slot and retained with tape
* Internal power jumper installed (top right)
* Board powered on, displays green LED and correct chips, and then powered off again

Pre-launch:

# Arm the switch
# Correct beeping pattern (slow chirps spaced a few seconds apart)
#

Flying Phoque 6

2024-06-04T05:32:48Z

Lskaling: Initial Commit

[[File:Flying Phoque 6.png|thumb|PCB Layout]]
[[File:Flying Phoque 6 Labels.png|thumb|External interfaces]]

== Software ==
The software repo is here. The board is programmed using Platform IO in VS code.

== Setup ==
Setup instructions assume board is just being used for data logging (TODO: add instructions to use as flight computer)

# Ensure the board is not contact any metal surfaces
# Check that the internal power header pins aren't connected (see photo)
# Insert SD card into Teensy
# Connect the Teensy to a computer via USB
# Upload firmware using Platform IO
# Data should be logging, and serial data being sent to the computer. Open the Serial monitor to check that everything is working.
# Unplug the teensy from the computer. Verify the SD card has data written to it by plugging it into a computer and opening the file.
# Put the SD card back into the Teensy (it's okay to leave the program, a new program file is created every time it is turned on)
# Insert the internal power header jumper cap to have the Teensy powered by the battery
# Screw a connector into the power in port
# Verify polarity! Red on top, GND on bottom
# (Optionally) add any arming circuitry to the power port connector, such as a magswitch or toggle switch
# Plug the battery in and turn on. Unplug immediately if the light does not turn on and buzzer doesn't beep
# Teensy should be in fully operational data logging state. It will have slow chirps indicating that it's logging data, and a green flashing LED. Fast beeps and a red LED indicate an error. If that happens, unplug, remove the internal power header jumper cap, and plug in with USB to view serial data.

== Pre-Flight Checklist ==
Packing list:

* Board
* JST Connector
* Batteries
* Battery charger
* Arming switch
* Jumper Caps
* Micro USB cable + adapters for computer
* MicroSD card
* MicroSD card adapter for computer
* Electrical tape
* Multimeter
* Avionics mount for board

Integration:

* Battery fully charged (around 8.4v)
* SD card has sufficient capacity (Data logs generate about 10 megabytes per hour)
* SD installed into the slot and retained with tape
* Internal power jumper installed (top right)
* Board powered on, displays green LED and correct chips, and then powered off again

Pre-launch:

# Arm the switch
# Correct beeping pattern (slow chirps spaced a few seconds apart)
#

File:Flying Phoque 6 Labels.png

2024-06-04T00:45:37Z

Lskaling:

External interfaces on FP6

File:Flying Phoque 6.png

2024-06-04T00:36:41Z

Lskaling:

FP6 schematic

Making a Purchase

2024-01-23T03:09:24Z

Lskaling: Updated with the latest workflow

Are you planning on spending money on something SSI-related? If so, you're in the right place! This page will go over both how to get reimbursed and how to use the credit card form.

= Step 1: Make the purchase and keep the receipt =

We care about making SSI financially accessible, and that includes you never having to make a purchase you are unable to or uncomfortable making. Choose one of the two options based on what works best for you and your situation:

A) If you are comfortable fronting the money yourself and being reimbursed later, go ahead and make the purchase and keep the receipt. The importance of the receipt cannot be overstated - without a receipt, it's very difficult to reimburse. If you're buying things at home, save your receipt and try to submit it as soon as you can; if you're traveling with SSI, take a picture of your receipt in case you forget it or accidentally lose it. And when you get your receipt, check two things:
* Is it an invoice? If so, it's not quite enough - you also need to attach a bank statement.
* Is it itemized? Restaurants are especially notorious for this, but if a place doesn't list a breakdown of what you spent, it doesn't count. If you get one of these, go back and ask for an itemized one. If you can't get an itemized one, we can try to work something out.

B) If you are not comfortable fronting the money yourself, submit a request to the FOs to purchase it on the SSI credit card here: https://bit.ly/2OOdr4B

= Step 2: Request a reimbursement on GrantEd =
Visit granted.stanford.edu, create a new request, and upload all required documentation. Please double check all fields before submitting!

= Step 3: Complete the internal reimbursement tracking =
Visit the [https://docs.google.com/forms/d/e/1FAIpQLSfcNRzuvxVPPdBL8-8ik50IJDehC-TPBmIiBscqL6045vHNEA/viewform internal google form] and complete the fields. This will notify the team leads of the expense and allow us to track it internally. Team leads will approve it, then the FOs will process it through GrantEd. This process can take a few weeks.

= What You Can and Can't Buy=

As a general rule, it’s best to clear a purchase with your immediate supervisor (project lead, team lead, etc) at least verbally beforehand, just in case it’s something we already own, something it’s more cost-effective to machine ourselves, or something that’s just a no-go. But whether you’re on a launch or just need a new part ASAP, sometimes you gotta make a purchase fast. To prevent an event where you make a purchase you later find out you can’t get reimbursed for, here is an non exhaustive list of generally approved items:

*Gas for SSI-related transportation, e.g. launches
*Small general parts, e.g. screws, brackets
* Non-power tools we don't already own or need more of, e.g. screwdrivers, taps
*3-D printing filament, when we run out
* PPE we don’t have or we anticipate needing
* Specialized safety equipment (ex. working with dry ice? Get a pair of thick gloves)
*Team-specific parts (e.g. ejection mechanism for parachutes, camera for satellite, rocket airframes)
*Non-chemical adhesives (tacky tape, regular glue/tape, duct tape)
*Office supplies

Here are a list of items you should be more careful about purchasing:
*Food. The food policy is dictated on high from the ASSU--make sure you clear it with your project team leads before hosting an event with food. The current policy is one event per team, per quarter. Food on launches is also discretionary.
*Really expensive things. Whether this is a motel stay on a launch or an expensive hunk of metal for a project, if something costs upward of >$100, it would be unwise not to discuss it first. Plus, who wants to front that much money without a guarantee of return, anyway?
*Things that are questionable for safety reasons. New power tools, anything chemical (yes, epoxy counts), and anything else that could result in unsafe practices you should clear with your team lead and possibly discuss with the safety leads. This may happen even when you don’t expect it to--for example, planning on cutting through carbon fiber? You’ll need goggles and an N95 mask to avoid inhaling microscopic fragments that could harm your lungs.

Here are some items you should never be purchasing:
*Alcohol
*Dangerous explosives

Happy purchasing!

[[Category:Operations]]

Snack Bot

2024-01-05T19:46:41Z

Lskaling: /* Technical */

Snack Bot is a Slack Bot that incentives workspace cleaning by giving snacks to those who share proof of cleaning. You'll need to spend a few minutes tidying the workspace, then you can redeem a snack. Here are possible ways to fulfill the requirement:

=== Cleaning Ideas ===

* Put away tools left out on a table
* Repair a broken 3D printer
* Sweep floor
* Organize a bin
* Remove scraps from around 3D printers
* Clean the whiteboard
* Clean the break room
* Organize cable storage rack
* Replenish low workspace consumables (solder, wire, fasteners, etc)
* Tidy downstairs

== Usage ==
To check your balance, type `/snack`. Everyone is given credits at the start of the quarter, so you may already have some.

If you have a credit, you can also use `/snack` to redeem. Select the cabinet corresponding to the snack you'd like and it will unlock. All cabinets use 1 credit to unlock.

To get a credit, spend a few minutes cleaning, then send a photo of what you cleaned to Snack Bot on slack. This image will be sent to a public channel to ensure accountability, however the credit will be available immediately. You can then choose to redeem it to unlock the cabinet or save it for later.

== Expectations ==
The expectation is that cleaning lasts at least 2 minutes, and makes a noticeable change to the workspace. Cleaning a mess you made does not count, and should benefit others in the club (i.e. not a box that only you use).

For accountability, when you send a photo it gets uploaded to #snackbot-pics. Anyone is allowed to join this channel and see what others have cleaned. If someone believes a photo was taken without cleaning, it can be flagged with the :not-clean: emoji, and it will be sent to the workspace managers for review.

== Workspace Managers ==
Additional functionality is available to those in the #workspace-core private channel:

=== <code>/workspace-add-snack-credits</code> ===
Adds snack credits to the users tagged in the slash command. Multiple users can be added with any or no delimiter. Add a number, 1-9, at the beginning or end of the command to specify the number of snack credits; it otherwise defaults to one.

=== <code>/workspace-unlock-snack-cabinet</code> ===
Unlock the snack cabinet for 5 minutes. Intended to be used to restock the snack cabinet.

=== <code>/workspace-refresh-snack-credits</code> ===
Resets all free snack credits to 2. Intended to be used at the start of the quarter. Snack credits granted through photo upload or /workspace-add-snack-credits are not affected by this. Free snack credits do not roll over if unused, though.

== Technical ==
The slack bot is run locally on a Raspberry Pi, using a Python script. Lawton maintains the Slack API access. When the button is pressed, a solenoid is actuated on the corresponding cabinet.

An SQL database stores the snack credits. They are differentiated into two segments: free credits and earned credits. Free credits are used before earned credits, as free credits do not roll over. This is abstracted to the user with a single credit number. When a user invokes any command for the first time, they are added to the database with the free snacks.

Because of confusion with the package manager, there are two virtual environments. Venv was used on my mac for testing, snackbotvenv is used on the Raspberry Pi. The latter is excluded from github.

Snack-bot is located in the home directory of the Pi. Do not move, as the directory is hard coded in the startup execution.

The Raspberry Pi is set up to run the script upon booting, so it is resilient against power outages.

The password to SSH into the raspberry pi is stored in Dashlane.

Snack Bot

2024-01-05T19:35:35Z

Lskaling:

Snack Bot is a Slack Bot that incentives workspace cleaning by giving snacks to those who share proof of cleaning. You'll need to spend a few minutes tidying the workspace, then you can redeem a snack. Here are possible ways to fulfill the requirement:

=== Cleaning Ideas ===

* Put away tools left out on a table
* Repair a broken 3D printer
* Sweep floor
* Organize a bin
* Remove scraps from around 3D printers
* Clean the whiteboard
* Clean the break room
* Organize cable storage rack
* Replenish low workspace consumables (solder, wire, fasteners, etc)
* Tidy downstairs

== Usage ==
To check your balance, type `/snack`. Everyone is given credits at the start of the quarter, so you may already have some.

If you have a credit, you can also use `/snack` to redeem. Select the cabinet corresponding to the snack you'd like and it will unlock. All cabinets use 1 credit to unlock.

To get a credit, spend a few minutes cleaning, then send a photo of what you cleaned to Snack Bot on slack. This image will be sent to a public channel to ensure accountability, however the credit will be available immediately. You can then choose to redeem it to unlock the cabinet or save it for later.

== Expectations ==
The expectation is that cleaning lasts at least 2 minutes, and makes a noticeable change to the workspace. Cleaning a mess you made does not count, and should benefit others in the club (i.e. not a box that only you use).

For accountability, when you send a photo it gets uploaded to #snackbot-pics. Anyone is allowed to join this channel and see what others have cleaned. If someone believes a photo was taken without cleaning, it can be flagged with the :not-clean: emoji, and it will be sent to the workspace managers for review.

== Workspace Managers ==
Additional functionality is available to those in the #workspace-core private channel:

=== <code>/workspace-add-snack-credits</code> ===
Adds snack credits to the users tagged in the slash command. Multiple users can be added with any or no delimiter. Add a number, 1-9, at the beginning or end of the command to specify the number of snack credits; it otherwise defaults to one.

=== <code>/workspace-unlock-snack-cabinet</code> ===
Unlock the snack cabinet for 5 minutes. Intended to be used to restock the snack cabinet.

=== <code>/workspace-refresh-snack-credits</code> ===
Resets all free snack credits to 2. Intended to be used at the start of the quarter. Snack credits granted through photo upload or /workspace-add-snack-credits are not affected by this. Free snack credits do not roll over if unused, though.

== Technical ==
The slack bot is run locally on a Raspberry Pi, using a Python script. Lawton maintains the Slack API access. When the button is pressed, a solenoid is actuated on the corresponding cabinet.

An SQL database stores the snack credits. They are differentiated into two segments: free credits and earned credits. Free credits are used before earned credits, as free credits do not roll over. This is abstracted to the user with a single credit number. When a user invokes any command for the first time, they are added to the database with the free snacks.

The Raspberry Pi is set up to run the script upon booting, so it is resilient against power outages.

The password to SSH into the raspberry pi is stored in Dashlane.

Snack Bot

2024-01-01T07:06:43Z

Lskaling:

Snack Bot is a Slack Bot that incentives workspace cleaning by giving snacks to those who share proof of cleaning. You'll need to spend a few minutes tidying the workspace, then you can redeem a snack. Here are possible ways to fulfill the requirement:

=== Cleaning Ideas ===

* Put away tools left out on a table
* Repair a broken 3D printer
* Sweep floor
* Organize a bin
* Remove scraps from around 3D printers
* Clean the whiteboard
* Clean the break room
* Organize cable storage rack
* Replenish low workspace consumables (solder, wire, fasteners, etc)
* Tidy downstairs

== Usage ==
To check your balance, type `/snack`. Everyone is given credits at the start of the quarter, so you may already have some.

If you have a credit, you can also use `/snack` to redeem. Select the cabinet corresponding to the snack you'd like and it will unlock. All cabinets use 1 credit to unlock.

To get a credit, spend a few minutes cleaning, then send a photo of what you cleaned to Snack Bot on slack. This image will be sent to a public channel to ensure accountability, however the credit will be available immediately. You can then choose to redeem it to unlock the cabinet or save it for later.

== Expectations ==
The expectation is that cleaning lasts at least 2 minutes, and makes a noticeable change to the workspace. Cleaning a mess you made does not count, and should benefit others in the club (i.e. not a box that only you use).

For accountability, when you send a photo it gets uploaded to #snackbot-pics. Anyone is allowed to join this channel and see what others have cleaned. If someone believes a photo was taken without cleaning, it can be flagged with the :not-clean: emoji, and it will be sent to the workspace managers for review.

== Workspace Managers ==
Additional functionality is available to those in the #workspace-core private channel:

=== <code>/workspace-add-snack-credits</code> ===
Adds snack credits to the users tagged in the slash command. Multiple users can be added with any or no delimiter. Add a number, 1-9, at the beginning or end of the command to specify the number of snack credits; it otherwise defaults to one.

=== <code>/workspace-unlock-snack-cabinet</code> ===
Unlock the snack cabinet for 5 minutes. Intended to be used to restock the snack cabinet.

=== <code>/workspace-refresh-snack-credits</code> ===
Resets all free snack credits to 2. Intended to be used at the start of the quarter. Snack credits granted through photo upload or /workspace-add-snack-credits are not affected by this. Free snack credits do not roll over if unused, though.

== Technical ==
The slack bot is run locally on a Raspberry Pi, using a Python script. Lawton maintains the Slack API access. When the button is pressed, a solenoid is actuated on the corresponding cabinet.

An SQL database stores the snack credits. They are differentiated into two segments: free credits and earned credits. Free credits are used before earned credits, as free credits do not roll over. This is abstracted to the user with a single credit number. When a user invokes any command for the first time, they are added to the database with the free snacks.

The Raspberry Pi is set up to run the script upon booting, so it is resilient against power outages.

Snack Bot

2023-12-31T20:25:37Z

Lskaling:

Snack Bot

2023-12-31T19:56:29Z

Lskaling: Created page with "Snack Bot is a Slack Bot that incentives workspace cleaning by giving snacks to those who share proof of cleaning. You are expected to spend a few minutes tidying the workspac..."

Snack Bot is a Slack Bot that incentives workspace cleaning by giving snacks to those who share proof of cleaning. You are expected to spend a few minutes tidying the workspace, then can redeem a snack. Here are possible ways to fulfil the requirement:

=== Cleaning options ===

* Put away tools left out on a table
* Repair a broken 3D printer
* Sweep floor
* Organize a bin
* Remove scraps from around 3D printers
* Clean the whiteboard
* Clean the break room
* Organize cable storage rack
* Replenish low workspace consumables (solder, wire, fasteners, etc)
* Tidy downstairs

== Usage ==

Find SSI Friends

2023-09-23T23:04:04Z

Lskaling: formatting

=== Use ===

# Type <code>/find-ssi-friends</code> into any Slack channel (nothing gets posted publicly to the channel).
# Navigate to the people tab of the canvas class you want to find friends for
# Copy the entire page, navigate to the slack modal, and paste it into the box. It will likely be very messy, and that is fine
# You'll receive a DM with the members that are in the SSI slack channel
# Search for the slack channel for the class (the convention is #ssi-takes-[class-code]) and join it or create it if it doesn't exist already
# Paste the names of others to add them to the channel. In SSI adding others to channels is common and encouraged, people can leave at any time without notifying others that they left.

=== Software ===
Find the GitHub repo here. The software is written in JavaScript using Slack's Bolt SDK. It's hosted on Heroku. The string of names is cleaned and each space delimiter is treated as a separate name. If anyone matches two names, it is considered successful. For example, "Alan" "Shepard" matches Slack's "Alan Shepard". "Alan" "Shepard" "he/him" also matches "Alan Shepard". Obviously, it's not a perfect system, but captures the vast majority of cases. The slack roster is saved as a CSV file, and must be updated for new members to be included.

=== History ===
Find SSI Friends was written over an evening of homework procrastination when Lawton wanted others to work with on his ME 30 pset. He wrote a python script that would take people from other classes, slack channels, and dorm chats. Proving useful, he made it into a slack bot the following weekend for others to use. Tracking suggests it gets used ~20 times per quarter.

=== Example submission ===
<blockquote>

Skip To Content

Dashboard

Lawton Michael Skaling

Account

Dashboard

 
Profile Picture Name Section Role Administrative Links

Alex Agris

Alex Agris (She/her)

F23-CME-102-01

Student

Carlos Emmanuelle Ayala Bellido

Carlos Emmanuelle Ayala Bellido

F23-CME-102-01

F23-ENGR-155A-01

TA

TA

Analiese Marie Bancroft

Analiese Marie Bancroft</blockquote>

Find SSI Friends

2023-09-23T23:03:25Z

Lskaling: Changed formatting

=== Use ===

# Type <code>/find-ssi-friends</code> into any Slack channel (nothing gets posted publicly to the channel).
# Navigate to the people tab of the canvas class you want to find friends for
# Copy the entire page, navigate to the slack modal, and paste it into the box. It will likely be very messy, and that is fine
# You'll receive a DM with the members that are in the SSI slack channel
# Search for the slack channel for the class (the convention is #ssi-takes-[class-code]) and join it or create it if it doesn't exist already
# Paste the names of others to add them to the channel. In SSI adding others to channels is common and encouraged, people can leave at any time without notifying others that they left.

=== Software ===
Find the GitHub repo here. The software is written in JavaScript using Slack's Bolt SDK. It's hosted on Heroku. The string of names is cleaned and each space delimiter is treated as a separate name. If anyone matches two names, it is considered successful. For example, "Alan" "Shepard" matches Slack's "Alan Shepard". "Alan" "Shepard" "he/him" also matches "Alan Shepard". Obviously, it's not a perfect system, but captures the vast majority of cases. The slack roster is saved as a CSV file, and must be updated for new members to be included.

=== History ===
Find SSI Friends was written over an evening of homework procrastination when Lawton wanted others to work with on his ME 30 pset. He wrote a python script that would take people from other classes, slack channels, and dorm chats. Proving useful, he made it into a slack bot the following weekend for others to use. Tracking suggests it gets used ~20 times per quarter.

=== Example submission ===

Skip To Content

Dashboard

Lawton Michael Skaling

Account

Dashboard

Profile Picture Name Section Role Administrative Links

Alex Agris

Alex Agris (She/her)

F23-CME-102-01

Student

Carlos Emmanuelle Ayala Bellido

Carlos Emmanuelle Ayala Bellido

F23-CME-102-01

F23-ENGR-155A-01

TA

TA

Analiese Marie Bancroft

Analiese Marie Bancroft

Find SSI Friends

2023-09-23T23:03:00Z

Lskaling: Initial commit

=== Use ===

# Type `/find-ssi-friends` into any Slack channel (nothing gets posted publicly to the channel).
# Navigate to the people tab of the canvas class you want to find friends for
# Copy the entire page, navigate to the slack modal, and paste it into the box. It will likely be very messy, and that is fine
# You'll receive a DM with the members that are in the SSI slack channel
# Search for the slack channel for the class (the convention is #ssi-takes-[class-code]) and join it or create it if it doesn't exist already
# Paste the names of others to add them to the channel. In SSI adding others to channels is common and encouraged, people can leave at any time without notifying others that they left.

=== Software ===
Find the GitHub repo here. The software is written in JavaScript using Slack's Bolt SDK. It's hosted on Heroku. The string of names is cleaned and each space delimiter is treated as a separate name. If anyone matches two names, it is considered successful. For example, "Alan" "Shepard" matches Slack's "Alan Shepard". "Alan" "Shepard" "he/him" also matches "Alan Shepard". Obviously, it's not a perfect system, but captures the vast majority of cases. The slack roster is saved as a CSV file, and must be updated for new members to be included.

=== History ===
Find SSI Friends was written over an evening of homework procrastination when Lawton wanted others to work with on his ME 30 pset. He wrote a python script that would take people from other classes, slack channels, and dorm chats. Proving useful, he made it into a slack bot the following weekend for others to use. Tracking suggests it gets used ~20 times per quarter.

=== Example submission ===

Skip To Content

Dashboard

Lawton Michael Skaling

Account

Dashboard

Profile Picture Name Section Role Administrative Links

Alex Agris

Alex Agris (She/her)

F23-CME-102-01

Student

Carlos Emmanuelle Ayala Bellido

Carlos Emmanuelle Ayala Bellido

F23-CME-102-01

F23-ENGR-155A-01

TA

TA

Analiese Marie Bancroft

Analiese Marie Bancroft

Operations Team

2023-09-02T02:59:42Z

Lskaling: Updated Operations

Operations is the place in SSI to learn professional skills and connect to the wider aerospace community. The skills you’ll learn are so diverse -- from graphic design to how to get a sponsorship -- that they’re near impossible to summarize. Space is so much more than just the technology, and Operations where it all happens. If you want to know how to manage a group of 200 members with a six figure budget, make space art to decorate our workspace, or get connected to the top of the space industry, Operations is the place for you.

{{Nowrap|Space would hardly be possible without the people behind the hardware, getting sponsorships, building community, and talking to CEOs and Venture Capitalists across the industry. We’ve brought in speakers like Charlie Bolden, the then-administrator of NASA, and Gwynne Shotwell, the President of SpaceX. We have a half dozen different efforts that form the backbone of SSI. Feel free to reach out if you want to get involved! The current team lead is {{Leadership|Operations=true}}}}

= Public Relations =
Public relations connects SSI to the space community, Stanford campus, and people around the world! They manage our social media presence, keep connected with alumni, and help create content to share across the university.

= Sponsor Relations =
Sponsor relations keeps connected to our partners and sponsors, including Boeing, Autodesk, and Stanford. They also seek out new sponsors, and are the point of contact for companies looking to support our club.

= Diversity, Equity, and Inclusion (DEI) =
We want space to be the most welcoming community possible, and that starts with SSI. The DEI team runs a quarterly leadership workshop, hosts talks, connects with engineering diversity organizations, and works to make SSI a space for everyone. Look out for self-care and movie nights and exciting speakers discussing equity and representation in aerospace.

= Onboarding =
Onboarding focuses on us that, bringing in the future leaders in space! They organize events at the start of each quarter, create and distribute posters talking about our club, and are a point of contact for people interested in getting involved.

= Financial Officers =
The FOs should really be called the wolves of wall-ssi, because they focus on managing the six-figure budget, handling reimbursements, and interfacing with Stanford administrators.

= Workspace =
Workspace manages the 60-foot-tall underground bunker we call home. That means running a machine shop, planting herbs, and painting space-themed murals across our cavernous space.

= Events =
At the core of any team is the people, and in the events group you’ll help welcome and foster connections between people from all walks of life. By organizing events like special dinners, watergun fights, and spring retreat, you will help make SSI more than just a group of talented engineers, but rather (in the words of one of our members) “the best family one could ask for.”

= Safety =
Space can be dangerous! Whether it’s working with dry ice, using power tools, keeping our workspace compliant, or standing far, far, away from rockets at launches, Safety comes up with procedures that keep us from getting injured doing what we love.

= Technology =
If you want to explore the bowels of SSI on a deep, deep level, then SSIT is for you. Keeping our Wiki and website running and managing all of SSI’s technology is no easy task, but it’s critical for helping the club function.

----

<noinclude>
[[Category:Operations]]
</noinclude>

Operations Team

2023-03-31T01:32:15Z

Lskaling: Updated positions this year

Operations is the place in SSI to learn professional skills and connect to the wider aerospace community. The skills you’ll learn are so diverse -- from graphic design to how to get a sponsorship -- that they’re near impossible to summarize. Space is so much more than just the technology, and Operations where it all happens. Operations is split into a number of subgroups with various responsibilities, from organizing members to teach classes at [https://www.stanfordesp.org Stanford Splash] and uploading workshops to YouTube, to planning special dinners for all members. If you want to know how to manage a group of 200 members with a six figure budget, make space art to decorate our workspace, or get connected to the top of the space industry, Operations is the place for you.

{{Nowrap|Space would hardly be possible without the people behind the hardware, getting sponsorships, building community, and talking to CEOs and Venture Capitalists across the industry. We’ve brought in speakers like Charlie Bolden, the then-administrator of NASA, and Gwynne Shotwell, the President of SpaceX. We have a half dozen different efforts that form the backbone of SSI. Feel free to reach out if you want to get involved! The current team lead is {{Leadership|Operations=true}}}}

= Public Relations =
Public relations connects SSI to the space community, Stanford campus, and people around the world! They manage our social media presence, keep connected with alumni, and help create content to share across the university.

= Sponsor Relations =
Sponsor relations keeps connected to our partners and sponsors, including Boeing, Autodesk, and Stanford. They also seek out new sponsors, and are the point of contact for companies looking to support our club.

= Diversity, Equity, and Inclusion (DEI) =
We want space to be the most welcoming community possible, and that starts with SSI. The DEI team runs a quarterly leadership workshop, hosts talks, connects with engineering diversity organizations, and works to make SSI a space for everyone. Look out for self-care and movie nights and exciting speakers discussing equity and representation in aerospace.

= Onboarding =
Onboarding focuses on us that, bringing in the future leaders in space! They organize events at the start of each quarter, create and distribute posters talking about our club, and are a point of contact for people interested in getting involved.

= Financial Officers =
The FOs should really be called the wolves of wall-ssi, because they focus on managing the six-figure budget, handling reimbursements, and interfacing with Stanford administrators.

= Workspace =
Workspace manages the 60-foot-tall underground bunker we call home. That means running a machine shop, planting herbs, and painting space-themed murals across our cavernous space.

= Events =
At the core of any team is the people, and in the events group you’ll help welcome and foster connections between people from all walks of life. By organizing events like special dinners, watergun fights, and spring retreat, you will help make SSI more than just a group of talented engineers, but rather (in the words of one of our members) “the best family one could ask for.”

= Safety =
Space can be dangerous! Whether it’s working with dry ice, using power tools, keeping our workspace compliant, or standing far, far, away from rockets at launches, Safety comes up with procedures that keep us from getting injured doing what we love.

= Technology =
If you want to explore the bowels of SSI on a deep, deep level, then SSIT is for you. Keeping our Wiki and website running and managing all of SSI’s technology is no easy task, but it’s critical for helping the club function.

----

<noinclude>
[[Category:Operations]]
</noinclude>

End station III

2022-10-20T15:59:35Z

Lskaling: Changed esiii access link

End Station III is our home base. It's where we do almost all of our project work, and where we keep our stuff. It's also an active laboratory doing some pretty cool work. Here are some thoughts, tips and tricks about using it!

[[File:whereisesiii.png|thumb|right]]

=Where is ESIII=

See the picture above! Or you can type "where pizza" to any slack channel to get an address.

=How Can I Get Access to ESIII=

Follow the instructions on the [https://sites.google.com/d/1jYHC2-QvA_n4n-FCrT6HhYskoRkJzElO/p/1QCURHVQATK6OsdyFKMwCyDortR7lk95l/edit?authuser=1 ESIII Access Guide]! If you have any problems, please feel free to message the Workspace Managers (@Lawton Skaling and @Madeleine Butterfly).

=What are the rules in ESIII=

There are a couple things to keep in mind while you're in ESIII.

# Please swipe in when you enter, even if someone else is holding the door for you. We're required to get a sense of who's in the building in case of emergency!
# *Do not enter ESIII alone.* It's an active laboratory. If you need a buddy, hit up #random in the slack - people are always willing to head over!
# Don't park bikes inside, please; it blocks stuff.
# You can open the loading dock door - but don't open it for long (it messes up sensitive experiments), and don't leave it open (so people don't steal our stuff).
# Don't use the door near Green Earth Sciences - use the one on South Service Road instead.
# Although it's tempting, please don't actually sleep in ESIII.

=Tips and Tricks=
# Check out the #doorbell channel to see if people are in ESIII if you're unsure!
# There are some cool easter eggs and historical moments hidden all around - check things out while you're there!
# We have access to the break room - it's a lovely spot to do PSETs with people.
# ISS stands for Industrial Subterranean Space, but it's the closest we have (so far!) to our own International Space Station. Each room is named after a capsule of the ISS - Unity (Mechanical Engineering), Harmony (Electrical Engineering), Tranquility (Meeting Room), Destiny (Storage), and Zarya (General Use, 3D Printers and Desktop). The two storage spaces on the floor are named after capsules that meet the ISS - Dragon and Cygnus.

How to Join SSI

2022-10-01T00:07:04Z

Lskaling: Changed ESIII to point to internal site

Hello! There are a few things you need to do if you'd like to have full access to SSI's resources as a member. :-)

=Becoming an official member=


# Join the SSI Slack [https://join.slack.com/t/ssi-teams/shared_invite/zt-gahlixrm-DyAtkyxTrUkt7K6HvPsxIA here].
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].
# Apply for access to ESIII. This includes completing safety training and paperwork. Find the instructions for that [https://sites.google.com/stanford.edu/ssi/end-station-iii/keycard-access-for-es3?authuser=1 here]

# Take a look at [https://s3-us-west-1.amazonaws.com/habmc/assets/assi.pdf Approaching SSI], a handbook for new (and prospective) members!

=Resources=

== [https://ssi-teams.slack.com/ Slack] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like {{slack-channel|rockets}}), which allow us to push out general updates to everyone interested in the rockets team and direct messages which allows one to one or smaller group communication. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

To see what a list of what channels there are to join, check out the [[Slack Directory]].

[https://ssi-teams.slack.com/signup '''Join the SSI Slack here.''']

==[https://stanfordssi.org/events Calendar]==
Home to all of our events across all our teams.

== [https://stanfordssi.org/leadership SSI Leadership] ==
Find out who's in charge of things you're interested in and contact them! You can find all of us on Slack as well.

==The Wiki==

This wiki is a great place to find guides, overviews, and generally useful documentation on SSI projects. Many of the most current plans and docs are in the drive though.

==[https://drive.google.com/drive/u/0/folders/0AOLUM8S1U9vqUk9PVA SSI Drive]==

The drive contains a lot of important documentation for each team. We are trying to put more emphasis on using the wiki as a place for longer-term knowledge storage. If you don't have access, ask in {{slack-channel|SSIT}}

== [https://stanfordssi.org/mailing-list The Mailing List] ==
We use SSI General for organization-wide announcements, and it's a good way to hear about events that get lost in the depths of slack (Slack is still by and large the primary mode of communication for most of us though).

== [https://sites.google.com/d/1jYHC2-QvA_n4n-FCrT6HhYskoRkJzElO/p/1QCURHVQATK6OsdyFKMwCyDortR7lk95l/edit?authuser=1 End Station III] ==

End Station III (also known as ES3) can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. End Station III houses work sessions, team meetings, and project storage. Keycard access is required to access the building.

[[File:whereisesiii.png|thumb|left]]

== [[Find a Project]] ==

If you're ever feeling overwhelmed or lost about all the things going on in SSI, use this page to see what's what! Reach out to someone working on a project you're interested in and they'll help you get started. If you have questions or just want to chat, poke any leadership member.

[[Category:Getting started]]

How to Join SSI

2022-09-30T23:55:05Z

Lskaling: deleted esiii access stuff to instead direct to internal site

Hello! There are a few things you need to do if you'd like to have full access to SSI's resources as a member. :-)

=Becoming an official member=


# Join the SSI Slack [https://join.slack.com/t/ssi-teams/shared_invite/zt-gahlixrm-DyAtkyxTrUkt7K6HvPsxIA here].
# Join the SSI mailing list [https://mailman.stanford.edu/mailman/listinfo/ssi_general here].
# Apply for access to ESIII. This includes completing safety training and paperwork. Find the instructions for that [https://sites.google.com/stanford.edu/ssi/end-station-iii/keycard-access-for-es3?authuser=1 here]

# Take a look at [https://s3-us-west-1.amazonaws.com/habmc/assets/assi.pdf Approaching SSI], a handbook for new (and prospective) members!

=Resources=

== [https://ssi-teams.slack.com/ Slack] ==

Slack is the lifeblood of SSI. It is a messaging client that allows everyone within SSI to communicate. There are general channels (like {{slack-channel|rockets}}), which allow us to push out general updates to everyone interested in the rockets team and direct messages which allows one to one or smaller group communication. Notifications are pushed directly to your phone/computer/anything that has internet so that way we can infringe on all of your free time!

To see what a list of what channels there are to join, check out the [[Slack Directory]].

[https://ssi-teams.slack.com/signup '''Join the SSI Slack here.''']

==[https://stanfordssi.org/events Calendar]==
Home to all of our events across all our teams.

== [https://stanfordssi.org/leadership SSI Leadership] ==
Find out who's in charge of things you're interested in and contact them! You can find all of us on Slack as well.

==The Wiki==

This wiki is a great place to find guides, overviews, and generally useful documentation on SSI projects. Many of the most current plans and docs are in the drive though.

==[https://drive.google.com/drive/u/0/folders/0AOLUM8S1U9vqUk9PVA SSI Drive]==

The drive contains a lot of important documentation for each team. We are trying to put more emphasis on using the wiki as a place for longer-term knowledge storage. If you don't have access, ask in {{slack-channel|SSIT}}

== [https://stanfordssi.org/mailing-list The Mailing List] ==
We use SSI General for organization-wide announcements, and it's a good way to hear about events that get lost in the depths of slack (Slack is still by and large the primary mode of communication for most of us though).

== [[End Station III]] ==

End Station III (also known as ES3) can be considered the temple to SSI’s religion, the hub, nerve center, or kernel of all project activity. End Station III houses work sessions, team meetings, and project storage. Keycard access is required to access the building.

[[File:whereisesiii.png|thumb|left]]

== [[Find a Project]] ==

If you're ever feeling overwhelmed or lost about all the things going on in SSI, use this page to see what's what! Reach out to someone working on a project you're interested in and they'll help you get started. If you have questions or just want to chat, poke any leadership member.

[[Category:Getting started]]

Metric Fasteners

2022-04-30T04:58:15Z

Lskaling: New metric fasteners added

ESIII has an assortment of metric fasteners useful for many projects, and free for any team to use.

== Types of fasteners ==

=== M3 ===
M3 indicates a screw is 3mm diameter, as measured by the outside of the threads. These are common in electronics and good for small prototypes.

=== M4 ===
M4 indicates a screw is 4mm diameter, as measured by the outside of the threads. These are common for hardware such as medium size motors, and good for larger assemblies.

=== Cap-Head ===
Cap head screws have a cylindrical head. They are the go to fastener in most situations. They are easier to model in assemblies and have a stronger socket than button-head screws.

=== Button-Head ===
Button head screws have an arced head. They are primarily used in situations which require a small head size, such as constrained space or exterior of a rocket.

=== Counter-Sunk ===
Countersunk screws have a circular head with a chamfer into the screw. These are good for situations which the top of the head must be flush with the surface. A countersink bit can be used to create a slot for the head in the material.

=== Standard Nut ===
Standard are have a hexagonal exterior and threaded inside to hold a screw in place. They must be held in place when screwing, either with your fingers (in applications which doesn't require a tight screw), with a wrench, or with a nut driver.

=== Square Nut ===
Square nuts are similar to standard nuts, but with a square exterior. These are mostly used for inserting in 3D printed pieces, as they create a stronger attachment and easier to install compared to standard nuts.

=== Nylock Nut ===
Nylock nuts have a small rubber contact on the head of the nut. This prevents the nut from coming undone with vibrations. These nuts should be installed with the rubber portion facing away from the screw head.

=== Heat-Set Inserts ===
Heat set inserts are used to create stronger threads in plastic components. They are installed by heating the insert (with a soldering iron), and pressing it into a hole in the plastic.

=== Self-threading screws ===
Self threading screws are used to fasten materials which don't have any threads. They can simplify components by not requiring nuts or heat-set inserts. They have larger threads compared with standard screws, and as the fastener is drilled, cuts into the material to create a thread and hold the screw in place.

== Dimensions ==

=== Screw Dimensions ===
{| class="wikitable"
|+Screw Dimensions
!Measurement
!M3
!M4
|-
|Thread diameter
|3mm
|4mm
|-
|Cap-Head diameter
|
|
|-
|Cap-Head length
|
|
|-
|Button-Head diameter
|
|
|-
|Button-Head length
|
|
|}

=== Nut Dimensions ===
{| class="wikitable"
|+Nut Dimensions
!Measurement
!Standard M3
!Square M3
!Nylock M3
!Standard M4
!Square M4
!Nylock M4
|-
|Edge to Edge
|
|
|
|
|
|
|-
|Thickness
|
|
|
|
|
|
|-
|Circumscribed Diameter
|
|
|
|
|
|
|}

=== Hole Dimensions ===
Note that with soft materials such as plastic, standard screws can also be self tapping. These can easily be stripped by over-tightening however.
{| class="wikitable"
|+Hole sizes
!Measurement
!M3
!Self-Tapping M3
!M4
!Self-Tapping M4
|-
|Clearance Hole
|3mm (1/8 in)
|3mm (1/8 in)
|4mm (11/64 in)
|4mm (11/64 in)
|-
|Tapping Hole
|2.5mm (3/32 in)
|2.2mm (3/32 in)
|3.5mm (9/64 in)
|3.2 (1/8 in)
|-
|Heat-Set Inserts
|5mm (3/16 in)
| -
|5.5mm (7/32 in)
| -
|}

== Common Fabrication Dimensions ==
Because 3D printers produce undersized holes, tolerances must be adjusted from the actual values. These numbers are optimized for Prusa printers.
{| class="wikitable"
|+3D printing dimensions
!
!M3
!M4
|-
|Clearance Hole
|3.2mm
|4.2mm
|-
|Tapping Hole (standard screw)
|2.6mm
|3.6mm
|-
|Tapping Hole (self-threading screw)
|
|
|-
|Hex Nut Width
|
|
|-
|Square Nut Width
|
|
|-
|Heat-Set Inserts
|5mm
|5.5mm
|-
|Cap-Head Clearance
|
|
|}
Because laser cutters produce oversized holes, tolerances must be adjusted from the actual values. This can vary with material size, focus, material and laser type.
{| class="wikitable"
|+Lasercutting dimensions
!
!M3
!M4
|-
|Clearance Hole
|2.8mm
|3.8mm
|-
|Tapping Hole (standard screw)
|2.4mm
|3.4mm
|-
|Tapping Hole (self-threading screw)
|
|
|-
|Hex Nut Width
|
|
|-
|Square Nut Width
|
|
|-
|Heat-Set Inserts
|4.8mm
|5.3mm
|}

== Re-order Links ==
Note: If a part is out of stock or requiring shipping from a different location, the "corrosion resistance" equivalent can be substituted, however slightly more expensive.
{| class="wikitable"
|+
!Part
!McMaster SKU
!Link
|-
|M2 Socket Head, 4mm
|91292A004
|https://www.mcmaster.com/catalog/91292A004
|-
|M2 Socket Head, 6mm
|91292A831
|https://www.mcmaster.com/catalog/91292A831
|-
|M2 Socket Head, 8mm
|91292A832
|https://www.mcmaster.com/catalog/91292A832
|-
|M2 Socket head, 12mm
|91292A834
|https://www.mcmaster.com/catalog/91292A834
|-
|M2 Nut
|91828A111
|https://www.mcmaster.com/catalog/91828A111
|}
{| class="wikitable"
|+M3
!Part
!McMaster SKU
!Link
|-
|M3 Socket Head, 4mm
|91292A109
|https://www.mcmaster.com/91292A109/
|-
|M3 Socket Head, 6mm
|91292A111
|https://www.mcmaster.com/catalog/91292A111
|-
|M3 Socket head, 8mm
|91292A112
|[https://www.mcmaster.com/91292A112 https://www.mcmaster.com/catalog/91292A112]
|-
|M3 Socket Head, 12mm
|91292A114
|https://www.mcmaster.com/catalog/91292A114
|-
|M3 Socket Head, 16mm
|91292A115
|https://www.mcmaster.com/catalog/91292A115
|-
|M3 Socket Head, 20mm
|91292A123
|https://www.mcmaster.com/catalog/91292A123
|-
|M3 Socket Head, 25mm
|91292A020
|https://www.mcmaster.com/catalog/91292A020
|-
|M3 Socket Head, 30mm
|91292A022
|https://www.mcmaster.com/catalog/91292A022
|-
|M3 Socket Head, 40mm
|91292A024
|https://www.mcmaster.com/catalog/91292A024
|-
|M3 Hex Nut
|91828A211
|https://www.mcmaster.com/catalog/91828A211
|-
|M3 Nylock Nut
|93625A100
|https://www.mcmaster.com/catalog/93625A100
|-
|M3 Square Nut
|97258A101
|https://www.mcmaster.com/catalog/97258A101
|-
|M3 Washer
|98689A112
|https://www.mcmaster.com/catalog/98689A112
|-
|M3 Oversize Washer
|91116A120
|https://www.mcmaster.com/catalog/91116A120
|-
|M3 Heat-Set Inserts
|94180A331
|https://www.mcmaster.com/catalog/94180A331
|}
{| class="wikitable"
|+M4
!Part
!McMaster SKU
!Link
|-
|M4 Socket Head, 6mm
|91292A107
|https://www.mcmaster.com/91292A107
|-
|M4 Socket head, 8mm
|91292A108
|https://www.mcmaster.com/91292A108
|-
|M4 Socket Head, 12mm
|91292A117
|https://www.mcmaster.com/91292A117
|-
|M4 Socket Head, 16mm
|91292A118
|https://www.mcmaster.com/91292A118
|-
|M4 Socket Head, 20mm
|91292A121
|https://www.mcmaster.com/91292A121
|-
|M4 Socket Head, 25mm
|91292A122
|https://www.mcmaster.com/91292A122
|-
|M4 Socket Head, 30mm
|91292A130
|https://www.mcmaster.com/91292A130
|-
|M4 Socket Head, 40mm
|91292A132
|https://www.mcmaster.com/91292A132
|-
|M4 Socket Head, 50mm
|91292A140
|https://www.mcmaster.com/91292A140
|-
|M4 Socket Head, 60mm
|91292A048
|https://www.mcmaster.com/91292A048
|-
|M4 Cap Head, 8mm
|[[/www.mcmaster.com/94500A226|94500A226]]
|https://www.mcmaster.com/94500A226
|-
|M4 Cap Head, 12mm
|94500A228
|https://www.mcmaster.com/94500A228/
|-
|M4 Cap Head, 16mm
|[[/www.mcmaster.com/94500A282|94500A282]]
|https://www.mcmaster.com/94500A282
|-
|M4 Thread Forming, 8mm
|2815-0004-0008*
|https://www.servocity.com/zinc-plated-steel-thread-forming-socket-head-screw-m4-x-8mm-length-25-pack/
|-
|M4 Thread Forming, 12mm
|2815-0004-0012*
|https://www.servocity.com/zinc-plated-steel-thread-forming-socket-head-screw-m4-x-12mm-length-25-pack/
|-
|M4 Thread Forming, 16mm
|2815-0004-0016*
|https://www.servocity.com/zinc-plated-steel-thread-forming-socket-head-screw-m4-x-16mm-length-25-pack/
|-
|M4 Hex Nut
|91828A231
|https://www.mcmaster.com/91828A231
|-
|M4 Nylock Nut
|93625A150
|https://www.mcmaster.com/93625A150
|-
|M4 Square Nut
|96887A329
|https://www.mcmaster.com/96887A329
|-
|M4 Washer
|93475A230
|https://www.mcmaster.com/93475A230
|-
|M4 Oversize Washer
|91116A130
|https://www.mcmaster.com/91116A130
|-
|M4 Heat-Set Inserts
|94180A351
|https://www.mcmaster.com/94180A351
|}
<nowiki>*</nowiki>Unavailable from McMaster, order from Servocity instead

Label Maker

2022-04-23T15:48:09Z

Lskaling: Initial commit

Large labels can be printed with SSI's QL-800 label maker located in Harmony. It is capable of printing 2.4" width and any length label in red and black.

== Software ==
To print, download the [https://support.brother.com/g/b/downloadtop.aspx?c=ca&lang=en&prod=lpql800eus Brother P-touch Editor]. [https://help.brother-usa.com/app/answers/detail/a_id/78738/~/how-to-download-and-install-the-ptouch-editor-from-the-brother-website-for This guide] gives a step by step setup. Once it's set up, press the power button on the printer and plug the USB cable into your laptop, and "QL-800 (USB)" should appear as a printer option.
[[File:QL800.webp|thumb]]

== Restocking ==
Extra label rolls are located in the label maker box, stored in harmony. If you use the last roll, please notify {{slack-channel|operations-esiii}} or purchase more [https://www.amazon.com/dp/B08CPZS731?ref=ppx_yo2ov_dt_b_product_details&th=1 here]. Lift the top cover, and insert the new roll through the feed, then select the scissors button to cut it to length.

== Templates ==
The following are templates that may be useful for printing labels in the future. If you create a template worthy label, please add it to the google drive folder.

[https://drive.google.com/drive/u/0/folders/11vr03lAqRSASvWQI1kh9OQFAFOQbowoN Templates]

== Spreadsheets ==
A useful features of the P-touch editor software is being able to import spreadsheets for printing multiple things quickly, such as labeling a drawer of fasteners. Drag an excel file into the bottom center region labeled "Drop database file here", and select the rows or columns you wish to print.

== Smaller Labels ==
The QL-800 is constrained to the large tape width, so not ideal for smaller labels. For those, handheld label makers are available in the label maker box in harmony. Additionally, Lab 64 has a higher quality small label maker that can be operated by the same Brother P-touch Editor software.

== Other resources ==
[https://www.brother-usa.com/products/ql800?ef_id=CjwKCAjwx46TBhBhEiwArA_DjCa4xcdXmNWQfUtffsaNadQciYrjLsOf0cxZdz8u-QOVtelrPXUHzhoCjoMQAvD_BwE:G:s&gclid=CjwKCAjwx46TBhBhEiwArA_DjCa4xcdXmNWQfUtffsaNadQciYrjLsOf0cxZdz8u-QOVtelrPXUHzhoCjoMQAvD_BwE Purchase site]

[https://www.brother-usa.com/support/ql800 Support page]

File:QL800.webp

2022-04-23T15:19:37Z

Lskaling:

Stock photo of QL800 label maker

Metric Fasteners

2022-03-08T06:06:13Z

Lskaling: Minor clarifications to screw descriptions

ESIII has an assortment of metric fasteners useful for many projects, and free for any team to use.

== Types of fasteners ==

=== M3 ===
M3 indicates a screw is 3mm diameter, as measured by the outside of the threads. These are common in electronics and good for small prototypes.

=== M4 ===
M4 indicates a screw is 4mm diameter, as measured by the outside of the threads. These are common for hardware such as medium size motors, and good for larger assemblies.

=== Cap-Head ===
Cap head screws have a cylindrical head. They are the go to fastener in most situations. They are easier to model in assemblies and have a stronger socket than button-head screws.

=== Button-Head ===
Button head screws have an arced head. They are primarily used in situations which require a small head size, such as constrained space or exterior of a rocket.

=== Counter-Sunk ===
Countersunk screws have a circular head with a chamfer into the screw. These are good for situations which the top of the head must be flush with the surface. A countersink bit can be used to create a slot for the head in the material.

=== Standard Nut ===
Standard are have a hexagonal exterior and threaded inside to hold a screw in place. They must be held in place when screwing, either with your fingers (in applications which doesn't require a tight screw), with a wrench, or with a nut driver.

=== Square Nut ===
Square nuts are similar to standard nuts, but with a square exterior. These are mostly used for inserting in 3D printed pieces, as they create a stronger attachment and easier to install compared to standard nuts.

=== Nylock Nut ===
Nylock nuts have a small rubber contact on the head of the nut. This prevents the nut from coming undone with vibrations. These nuts should be installed with the rubber portion facing away from the screw head.

=== Heat-Set Inserts ===
Heat set inserts are used to create stronger threads in plastic components. They are installed by heating the insert (with a soldering iron), and pressing it into a hole in the plastic.

=== Self-threading screws ===
Self threading screws are used to fasten materials which don't have any threads. They can simplify components by not requiring nuts or heat-set inserts. They have larger threads compared with standard screws, and as the fastener is drilled, cuts into the material to create a thread and hold the screw in place.

== Dimensions ==

=== Screw Dimensions ===
{| class="wikitable"
|+Screw Dimensions
!Measurement
!M3
!M4
|-
|Thread diameter
|3mm
|4mm
|-
|Cap-Head diameter
|
|
|-
|Cap-Head length
|
|
|-
|Button-Head diameter
|
|
|-
|Button-Head length
|
|
|}

=== Nut Dimensions ===
{| class="wikitable"
|+Nut Dimensions
!Measurement
!Standard M3
!Square M3
!Nylock M3
!Standard M4
!Square M4
!Nylock M4
|-
|Edge to Edge
|
|
|
|
|
|
|-
|Thickness
|
|
|
|
|
|
|-
|Circumscribed Diameter
|
|
|
|
|
|
|}

=== Hole Dimensions ===
Note that with soft materials such as plastic, standard screws can also be self tapping. These can easily be stripped by over-tightening however.
{| class="wikitable"
|+Hole sizes
!Measurement
!M3
!Self-Tapping M3
!M4
!Self-Tapping M4
|-
|Clearance Hole
|3mm (1/8 in)
|3mm (1/8 in)
|4mm (11/64 in)
|4mm (11/64 in)
|-
|Tapping Hole
|2.5mm (3/32 in)
|2.2mm (3/32 in)
|3.5mm (9/64 in)
|3.2 (1/8 in)
|-
|Heat-Set Inserts
|5mm (3/16 in)
| -
|5.5mm (7/32 in)
| -
|}

== Common Fabrication Dimensions ==
Because 3D printers produce undersized holes, tolerances must be adjusted from the actual values. These numbers are optimized for Prusa printers.
{| class="wikitable"
|+3D printing dimensions
!
!M3
!M4
|-
|Clearance Hole
|3.2mm
|4.2mm
|-
|Tapping Hole (standard screw)
|2.6mm
|3.6mm
|-
|Tapping Hole (self-threading screw)
|
|
|-
|Hex Nut Width
|
|
|-
|Square Nut Width
|
|
|-
|Heat-Set Inserts
|5mm
|5.5mm
|-
|Cap-Head Clearance
|
|
|}
Because laser cutters produce oversized holes, tolerances must be adjusted from the actual values. This can vary with material size, focus, material and laser type.
{| class="wikitable"
|+Lasercutting dimensions
!
!M3
!M4
|-
|Clearance Hole
|2.8mm
|3.8mm
|-
|Tapping Hole (standard screw)
|2.4mm
|3.4mm
|-
|Tapping Hole (self-threading screw)
|
|
|-
|Hex Nut Width
|
|
|-
|Square Nut Width
|
|
|-
|Heat-Set Inserts
|4.8mm
|5.3mm
|}

== Re-order Links ==
Note: If a part is out of stock or requiring shipping from a different location, the "corrosion resistance" equivalent can be substituted, however slightly more expensive.
{| class="wikitable"
|+M3
!Part
!McMaster SKU
!Link
|-
|M3 Socket Head, 6mm
|91292A111
|https://www.mcmaster.com/catalog/91292A111
|-
|M3 Socket head, 8mm
|91292A112
|[https://www.mcmaster.com/91292A112 https://www.mcmaster.com/catalog/91292A112]
|-
|M3 Socket Head, 12mm
|91292A114
|https://www.mcmaster.com/catalog/91292A114
|-
|M3 Socket Head, 16mm
|91292A115
|https://www.mcmaster.com/catalog/91292A115
|-
|M3 Socket Head, 20mm
|91292A123
|https://www.mcmaster.com/catalog/91292A123
|-
|M3 Socket Head, 25mm
|91292A020
|https://www.mcmaster.com/catalog/91292A020
|-
|M3 Socket Head, 30mm
|91292A022
|https://www.mcmaster.com/catalog/91292A022
|-
|M3 Socket Head, 40mm
|91292A024
|https://www.mcmaster.com/catalog/91292A024
|-
|M3 Hex Nut
|91828A211
|https://www.mcmaster.com/catalog/91828A211
|-
|M3 Nylock Nut
|93625A100
|https://www.mcmaster.com/catalog/93625A100
|-
|M3 Square Nut
|97258A101
|https://www.mcmaster.com/catalog/97258A101
|-
|M3 Washer
|98689A112
|https://www.mcmaster.com/catalog/98689A112
|-
|M3 Oversize Washer
|91116A120
|https://www.mcmaster.com/catalog/91116A120
|-
|M3 Heat-Set Inserts
|94180A331
|https://www.mcmaster.com/catalog/94180A331
|}
{| class="wikitable"
|+M4
!Part
!McMaster SKU
!Link
|-
|M4 Socket Head, 6mm
|91292A107
|https://www.mcmaster.com/91292A107
|-
|M4 Socket head, 8mm
|91292A108
|https://www.mcmaster.com/91292A108
|-
|M4 Socket Head, 12mm
|91292A117
|https://www.mcmaster.com/91292A117
|-
|M4 Socket Head, 16mm
|91292A118
|https://www.mcmaster.com/91292A118
|-
|M4 Socket Head, 20mm
|91292A121
|https://www.mcmaster.com/91292A121
|-
|M4 Socket Head, 25mm
|91292A122
|https://www.mcmaster.com/91292A122
|-
|M4 Socket Head, 30mm
|91292A130
|https://www.mcmaster.com/91292A130
|-
|M4 Socket Head, 40mm
|91292A132
|https://www.mcmaster.com/91292A132
|-
|M4 Socket Head, 50mm
|91292A140
|https://www.mcmaster.com/91292A140
|-
|M4 Socket Head, 60mm
|91292A048
|https://www.mcmaster.com/91292A048
|-
|M4 Thread Forming, 8mm
|2815-0004-0008*
|https://www.servocity.com/zinc-plated-steel-thread-forming-socket-head-screw-m4-x-8mm-length-25-pack/
|-
|M4 Thread Forming, 12mm
|2815-0004-0012*
|https://www.servocity.com/zinc-plated-steel-thread-forming-socket-head-screw-m4-x-12mm-length-25-pack/
|-
|M4 Thread Forming, 16mm
|2815-0004-0016*
|https://www.servocity.com/zinc-plated-steel-thread-forming-socket-head-screw-m4-x-16mm-length-25-pack/
|-
|M4 Hex Nut
|91828A231
|https://www.mcmaster.com/91828A231
|-
|M4 Nylock Nut
|93625A150
|https://www.mcmaster.com/93625A150
|-
|M4 Square Nut
|96887A329
|https://www.mcmaster.com/96887A329
|-
|M4 Washer
|93475A230
|https://www.mcmaster.com/93475A230
|-
|M4 Oversize Washer
|91116A130
|https://www.mcmaster.com/91116A130
|-
|M4 Heat-Set Inserts
|94180A351
|https://www.mcmaster.com/94180A351
|}
<nowiki>*</nowiki>Unavailable from McMaster, order from Servocity instead

Metric Fasteners

2022-03-03T20:47:18Z

Lskaling: Added M4 Reorder Table

ESIII has an assortment of metric fasteners useful for many projects, and free for any team to use.

== Types of fasteners ==

=== M3 ===
M3 indicates a screw is 3mm diameter, as measured by the outside of the threads. These are common in electronics and good for small prototypes.

=== M4 ===
M4 indicates a screw is 4mm diameter, as measured by the outside of the threads. These are common for hardware such as medium size motors, and good for larger assemblies.

=== Cap-Head ===
Cap head screws have a cylindrical head. They are most common, and useful in applications which don't require a button head geometry. They are easier to model in assemblies and have a stronger head than button-head screws.

=== Button-Head ===
Button head screws have an arced head. They are primarily used in situations which require a small head size, such as constrained space or exterior of a rocket.

=== Counter-Sunk ===
Countersunk screws have a circular head with a chamfer into the screw. These are good for situations which the top of the head must be flush with the surface. A countersink bit can be used to create a slot for the head in the material.

=== Standard Nut ===
Standard are have a hexagonal exterior and threaded inside to hold a screw in place. They must be held in place when screwing, either with your fingers (in applications which doesn't require a tight screw), with a wrench, or with a nut driver.

=== Square Nut ===
Square nuts are similar to standard nuts, but with a square exterior. These are mostly used for inserting in 3D printed pieces, as they are stronger and easier to install compared to standard nuts.

=== Nylock Nut ===
Nylock nuts have a small rubber contact on the head of the nut. This prevents the nut from coming undone with vibrations. These nuts should be installed with the rubber portion facing away from the screw head.

=== Heat-Set Inserts ===
Heat set inserts are used to create stronger threads in plastic components. They are installed by heating the insert (with a soldering iron), and pressing it into a piece of plastic.

=== Self-threading screws ===
Self threading screws are used to fasten materials which don't have any threads. They can simplify components by not requiring nuts or heat-set inserts. They have larger threads compared with standard screws, and as the fastener is drilled, cuts into the material to create a thread and hold the screw in place.

== Dimensions ==

=== Screw Dimensions ===
{| class="wikitable"
|+Screw Dimensions
!Measurement
!M3
!M4
|-
|Thread diameter
|3mm
|4mm
|-
|Cap-Head diameter
|
|
|-
|Cap-Head length
|
|
|-
|Button-Head diameter
|
|
|-
|Button-Head length
|
|
|}

=== Nut Dimensions ===
{| class="wikitable"
|+Nut Dimensions
!Measurement
!Standard M3
!Square M3
!Nylock M3
!Standard M4
!Square M4
!Nylock M4
|-
|Edge to Edge
|
|
|
|
|
|
|-
|Thickness
|
|
|
|
|
|
|-
|Circumscribed Diameter
|
|
|
|
|
|
|}

=== Hole Dimensions ===
Note that with soft materials such as plastic, standard screws can also be self tapping. These can easily be stripped by over-tightening however.
{| class="wikitable"
|+Hole sizes
!Measurement
!M3
!Self-Tapping M3
!M4
!Self-Tapping M4
|-
|Clearance Hole
|3mm (1/8 in)
|3mm (1/8 in)
|4mm (11/64 in)
|4mm (11/64 in)
|-
|Tapping Hole
|2.5mm (3/32 in)
|2.2mm (3/32 in)
|3.5mm (9/64 in)
|3.2 (1/8 in)
|-
|Heat-Set Inserts
|5mm (3/16 in)
| -
|5.5mm (7/32 in)
| -
|}

== Common Fabrication Dimensions ==
Because 3D printers produce undersized holes, tolerances must be adjusted from the actual values. These numbers are optimized for Prusa printers.
{| class="wikitable"
|+3D printing dimensions
!
!M3
!M4
|-
|Clearance Hole
|3.2mm
|4.2mm
|-
|Tapping Hole (standard screw)
|2.6mm
|3.6mm
|-
|Tapping Hole (self-threading screw)
|
|
|-
|Hex Nut Width
|
|
|-
|Square Nut Width
|
|
|-
|Heat-Set Inserts
|5mm
|5.5mm
|-
|Cap-Head Clearance
|
|
|}
Because laser cutters produce oversized holes, tolerances must be adjusted from the actual values. This can vary with material size, focus, material and laser type.
{| class="wikitable"
|+Lasercutting dimensions
!
!M3
!M4
|-
|Clearance Hole
|2.8mm
|3.8mm
|-
|Tapping Hole (standard screw)
|2.4mm
|3.4mm
|-
|Tapping Hole (self-threading screw)
|
|
|-
|Hex Nut Width
|
|
|-
|Square Nut Width
|
|
|-
|Heat-Set Inserts
|4.8mm
|5.3mm
|}

== Re-order Links ==
Note: If a part is out of stock or requiring shipping from a different location, the "corrosion resistance" equivalent can be substituted, however slightly more expensive.
{| class="wikitable"
|+M3
!Part
!McMaster SKU
!Link
|-
|M3 Socket Head, 6mm
|91292A111
|https://www.mcmaster.com/catalog/91292A111
|-
|M3 Socket head, 8mm
|91292A112
|[https://www.mcmaster.com/91292A112 https://www.mcmaster.com/catalog/91292A112]
|-
|M3 Socket Head, 12mm
|91292A114
|https://www.mcmaster.com/catalog/91292A114
|-
|M3 Socket Head, 16mm
|91292A115
|https://www.mcmaster.com/catalog/91292A115
|-
|M3 Socket Head, 20mm
|91292A123
|https://www.mcmaster.com/catalog/91292A123
|-
|M3 Socket Head, 25mm
|91292A020
|https://www.mcmaster.com/catalog/91292A020
|-
|M3 Socket Head, 30mm
|91292A022
|https://www.mcmaster.com/catalog/91292A022
|-
|M3 Socket Head, 40mm
|91292A024
|https://www.mcmaster.com/catalog/91292A024
|-
|M3 Hex Nut
|91828A211
|https://www.mcmaster.com/catalog/91828A211
|-
|M3 Nylock Nut
|93625A100
|https://www.mcmaster.com/catalog/93625A100
|-
|M3 Square Nut
|97258A101
|https://www.mcmaster.com/catalog/97258A101
|-
|M3 Washer
|98689A112
|https://www.mcmaster.com/catalog/98689A112
|-
|M3 Oversize Washer
|91116A120
|https://www.mcmaster.com/catalog/91116A120
|-
|M3 Heat-Set Inserts
|94180A331
|https://www.mcmaster.com/catalog/94180A331
|}
{| class="wikitable"
|+M4
!Part
!McMaster SKU
!Link
|-
|M4 Socket Head, 6mm
|91292A107
|https://www.mcmaster.com/91292A107
|-
|M4 Socket head, 8mm
|91292A108
|https://www.mcmaster.com/91292A108
|-
|M4 Socket Head, 12mm
|91292A117
|https://www.mcmaster.com/91292A117
|-
|M4 Socket Head, 16mm
|91292A118
|https://www.mcmaster.com/91292A118
|-
|M4 Socket Head, 20mm
|91292A121
|https://www.mcmaster.com/91292A121
|-
|M4 Socket Head, 25mm
|91292A122
|https://www.mcmaster.com/91292A122
|-
|M4 Socket Head, 30mm
|91292A130
|https://www.mcmaster.com/91292A130
|-
|M4 Socket Head, 40mm
|91292A132
|https://www.mcmaster.com/91292A132
|-
|M4 Socket Head, 50mm
|91292A140
|https://www.mcmaster.com/91292A140
|-
|M4 Socket Head, 60mm
|91292A048
|https://www.mcmaster.com/91292A048
|-
|M4 Thread Forming, 8mm
|2815-0004-0008*
|https://www.servocity.com/zinc-plated-steel-thread-forming-socket-head-screw-m4-x-8mm-length-25-pack/
|-
|M4 Thread Forming, 12mm
|2815-0004-0012*
|https://www.servocity.com/zinc-plated-steel-thread-forming-socket-head-screw-m4-x-12mm-length-25-pack/
|-
|M4 Thread Forming, 16mm
|2815-0004-0016*
|https://www.servocity.com/zinc-plated-steel-thread-forming-socket-head-screw-m4-x-16mm-length-25-pack/
|-
|M4 Hex Nut
|91828A231
|https://www.mcmaster.com/91828A231
|-
|M4 Nylock Nut
|93625A150
|https://www.mcmaster.com/93625A150
|-
|M4 Square Nut
|96887A329
|https://www.mcmaster.com/96887A329
|-
|M4 Washer
|93475A230
|https://www.mcmaster.com/93475A230
|-
|M4 Oversize Washer
|91116A130
|https://www.mcmaster.com/91116A130
|-
|M4 Heat-Set Inserts
|94180A351
|https://www.mcmaster.com/94180A351
|}
<nowiki>*</nowiki>Unavailable from McMaster, order from Servocity instead

Metric Fasteners

2022-02-27T04:03:55Z

Lskaling: Added more metrics to measure

Metric Fasteners

2022-02-27T03:59:32Z

Lskaling: Label change

Metric Fasteners

2022-02-27T03:58:44Z

Lskaling: Initial Commit