https://ssi-wiki.stanford.edu/w/api.php?action=feedcontributions&feedformat=atom&user=Amilich 2026-04-29T07:48:02Z User contributions MediaWiki 1.45.1 https://ssi-wiki.stanford.edu/w/index.php?title=SNAPS&diff=1971 2016-04-19T03:12:11Z

<p>Amilich: </p> <hr /> <div>SNAPS is patiently awaiting deployment on the ISS. <br /> <br /> {{satellites-stub}}<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=COTS_CubeSat_Radio&diff=1970 2016-04-19T03:10:46Z

<p>Amilich: </p> <hr /> <div>Radio is currently the standard mode of CubeSat telecommunication. Hence, there are a variety of COTS CubeSat radio options available. <br /> <br /> '''Here's a list of COTS CubeSat radio system suppliers:'''<br /> *AstroDev<br /> *Stensat<br /> *ISIS (good luck googling that one)<br /> <br /> '''Here's a preliminary list of commercial CubeSat transmitters useful for a one-way downlink:'''<br /> *'''Stensat Radio Beacon'''<br /> **Cost: $750<br /> **Downlink rate: AX.25 Unnumbered Information (UI) packets at 1200 bps AFSK and 9600 bps FSK<br /> **Transmitter Frequency range: 420-450 MHz or 144-148 MHz (depending on model)<br /> **Mass: 50g<br /> **Dimensions: 44.45 x 78.74 (mm) (PCB layout)<br /> **Power Consumption: &lt;3W<br /> **More details on the product page: [http://www.stensat.org/products.html#]<br /> *'''ISIS TXS S-Band Transmitter'''<br /> **Cost: $9600<br /> **Downlink rate: up to 100 kbps<br /> **Transmitter Frequency range: 2100 MHz - 2500 MHz<br /> **Mass: 62g<br /> **Dimensions: 90 x 96 x 15 (mm)<br /> **Power Consumption: &lt;3.5W<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=9&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> *'''Integrated S-Band Transmitter'''<br /> **Cost: $7300<br /> **Downlink rate: 1.06 Mbs (max)<br /> **Transmitter Frequency range: 2200-2300 MHz, adjustable in steps of 100 kHz<br /> **Mass: 75g<br /> **Dimensions: 95 x 46 x 15 (mm)<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=84&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> <br /> '''Here's a preliminary list of commercial CubeSat transceivers useful for bi-directional communication:'''<br /> <br /> *'''ISIS VHF down UHF up Duplex Transceiver'''<br /> **Cost: $9600<br /> **Downlink rate: 1200, 2400, 4800 or 9600 bps<br /> **Uplink rate: 300 or 1200 bps<br /> **Transmitter Frequency range: 130 - 160 MHz (VHF)<br /> **Receiver Frequency range: 400 - 450 Mhz (UHF)<br /> **Mass: 85g<br /> **Dimensions: 96 x 90 x 15 (mm)<br /> **Power Consumption: &lt;1.7W (transmitter on), &lt;0.2W (receiver only)<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=73&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> *'''ISIS UHF down VHF up Duplex Transceiver'''<br /> **Cost: $9600<br /> **Downlink rate: 1200, 2400, 4800 or 9600 bps<br /> **Uplink rate: 1200 bps<br /> **Transmitter Frequency range: 420-450 MHz (UHF)<br /> **Receiver Frequency range: 140-150 MHz (VHF)<br /> **Mass: 75g<br /> **Dimensions: 96 x 90 x 15 (mm)<br /> **Power Consumption: &lt;4.0W (transmitter on), &lt;0.480W (receiver only)<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=11&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> * '''Astrodev Lithium'''<br /> ** Cost: ~$5000<br /> ** Downlink rate: Max 77 kbps <br /> ** Power Consumption: &lt; 10.0W; 4.0W transmitter power <br /> ** Efficiency: 40%<br /> **More details on the product page: [http://www.astrodev.com/public_html2/downloads/datasheet/LithiumUserManual.pdf]<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=Attitude_Determination_and_Control_(ADCS)&diff=1969 2016-04-19T03:08:20Z

<p>Amilich: </p> <hr /> <div>An Attitude Determination and Control (ADCS) provides measurements regarding a satellite's orbit and allows the satellite to change its inertial position. <br /> <br /> [[File:Cubesat_adcs.png|frame|none|alt=Alt text|CubeSpace ADCS]]<br /> <br /> == Examples of ADCS Hardware ==<br /> * Most ADCS hardware relies on an ability to change the satellite's position relative to the Earth. <br /> ** Reaction wheels: Using small, spinning wheels, reaction wheels allow satellite positioning using the principle of conservation of momentum. <br /> *** CubeADCS: CubeSpace's CubeADCS utilizes a variety of sensors (including magnetometers and sun sensors) to accurately determine the satellite's precision. It can use either magnetic torquers (see below) or reaction wheels for attitude determination. <br /> ** Magnetorquer: By creating a magnetic field that interact's with the Earth's own magnetic field, a magnetic torquer produces a force that can rotate a satellite. <br /> ** Control Moment Gyros: Similar to Reaction Wheels, Control Moment Gyros use a gimbal to change the rotation of a spinning flywheel. See https://www.youtube.com/watch?v=JTWA6tUREi8 for an excellent visual demonstration of CMG technology. <br /> ** Thrusters: Though far more uncommon on small satellites, thrusters remain a dependable and conceptually straightforward method of attitude determination. <br /> <br /> == ADCS Specifications ==<br /> * ADCS Pointing Accuracy<br /> ** ADCS accuracy varies depending on the type and quality of mechanisms and control systems. The popular CubeSpace hardware used on 2U QB50 satellites has an accuracy of 0.2º to 0.6º (keep in mind, however, that the QB50 missions requirements regarding ADCS precision are fairly lax). The BlueCanyon XB1 high precision ADCS suggests an accuracy of 0.002º. <br /> * ADCS Maneuvering Rates<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=File:Cubesat_adcs.png&diff=1966 2016-04-19T03:07:43Z

<p>Amilich: </p> <hr /> <div></div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=CubeSat_Component_Manufacturers&diff=1964 2016-04-19T03:06:19Z

<p>Amilich: </p> <hr /> <div>Here's a general listing of CubeSat component manufacturers and the components each manufacture. <br /> <br /> ==Pumpkin==<br /> Founded by Stanford Professor Andrew Kalman, Pumpkin provides cubesat kits, components, and software. <br /> * Specialties: <br /> ** Salvo Real Time Operating System <br /> ** CubeSatKit and development hardware for a variety of microcontrollers <br /> ** Software for interfacing with a variety of other relevant components, such as radios and EPS systems <br /> &lt;br&gt;<br /> [[File: Cubesatkit_logo.jpg |80px]] <br /> ==ClydeSpace==<br /> Particularly in the field of power consumption and generation, ClydeSpace provides a wide array of COTS CubeSat components. This includes premade solar panels, EPS systems, batteries, and deployable solar panels. <br /> ClydeSpace also provides a CubeSat onboard computer module, though the flexibility and applications of this system seemed somewhat unclear. <br /> &lt;br&gt;<br /> [[File: Clydespace_batt.jpg |80px]] <br /> ==AstroDev==<br /> Astronautical Development manufactures and sells CubeSat radio hardware. This includes the Helium and Lithium radios, which have been used on past satellites built by the Stanford Space Systems Development Laboratory.<br /> &lt;br&gt;<br /> [[File: Astrodev_lithium.jpg |80px]] <br /> ==CubeSpace==<br /> CubeSpace manufactures components and actuators designed for CubeSat ADC systems. In addition to their all-in-one CubeADCS (which includes sunsensors, magnetorquers, magnetometers, and a reaction wheel), individual components (such as a sun sensor board) are also provided. <br /> ==Blue Canyon==<br /> Blue Canyon provides &quot;spacecraft bus platforms&quot; with modular systems configurable for CubeSat missions. This includes extremely high precision ADCS components (0.002º pointing accuracy), radios (up to 15 Mbps downlink), telecommand processing, and other software components.<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=CubeSat_Component_Manufacturers&diff=1963 2016-04-19T03:05:55Z

<p>Amilich: </p> <hr /> <div>Here's a general listing of CubeSat component manufacturers and the components each manufacture. <br /> <br /> ==Pumpkin==<br /> Founded by Stanford Professor Andrew Kalman, Pumpkin aims to provide cubesat kits, components, and software. <br /> * Specialties: <br /> ** Salvo Real Time Operating System <br /> ** CubeSatKit and development hardware for a variety of microcontrollers <br /> ** Software for interfacing with a variety of other relevant components, such as radios and EPS systems <br /> &lt;br&gt;<br /> [[File: Cubesatkit_logo.jpg |80px]] <br /> ==ClydeSpace==<br /> Particularly in the field of power consumption and generation, ClydeSpace provides a wide array of COTS CubeSat components. This includes premade solar panels, EPS systems, batteries, and deployable solar panels. <br /> ClydeSpace also provides a CubeSat onboard computer module, though the flexibility and applications of this system seemed somewhat unclear. <br /> &lt;br&gt;<br /> [[File: Clydespace_batt.jpg |80px]] <br /> ==AstroDev==<br /> Astronautical Development manufactures and sells CubeSat radio hardware. This includes the Helium and Lithium radios, which have been used on past satellites built by the Stanford Space Systems Development Laboratory.<br /> &lt;br&gt;<br /> [[File: Astrodev_lithium.jpg |80px]] <br /> ==CubeSpace==<br /> CubeSpace manufactures components and actuators designed for CubeSat ADC systems. In addition to their all-in-one CubeADCS (which includes sunsensors, magnetorquers, magnetometers, and a reaction wheel), individual components (such as a sun sensor board) are also provided. <br /> ==Blue Canyon==<br /> Blue Canyon provides &quot;spacecraft bus platforms&quot; with modular systems configurable for CubeSat missions. This includes extremely high precision ADCS components (0.002º pointing accuracy), radios (up to 15 Mbps downlink), telecommand processing, and other software components.<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=CubeSat_Component_Manufacturers&diff=1962 2016-04-19T03:05:33Z

<p>Amilich: </p> <hr /> <div>Here's a general listing of CubeSat component manufacturers and the components each manufacture. <br /> <br /> ==Pumpkin==<br /> Founded by Stanford Professor Andrew Kalman, Pumpkin aims to provide cubesat kits, components, and software. <br /> * Specialties: <br /> ** Salvo Real Time Operating System <br /> ** CubeSatKit and development hardware for a variety of microcontrollers <br /> ** Software for interfacing with a variety of other relevant components, such as radios and EPS systems <br /> &lt;br&gt;<br /> [[File: Cubesatkit_logo.jpg |80px]] <br /> ==ClydeSpace==<br /> Particularly in the field of power consumption and generation, ClydeSpace provides a wide array of COTS CubeSat components. This includes premade solar panels, EPS systems, batteries, and deployable solar panels. <br /> ClydeSpace also provides a CubeSat onboard computer module, though the flexibility and applications of this system seemed somewhat unclear. <br /> &lt;br&gt;<br /> [[File: Clydespace_batt.jpg |80px]] <br /> ==AstroDev===<br /> Astronautical Development manufactures and sells CubeSat radio hardware. This includes the Helium and Lithium radios, which have been used on past satellites built by the Stanford Space Systems Development Laboratory.<br /> &lt;br&gt;<br /> [[File: Astrodev_lithium.jpg |80px]] <br /> ==CubeSpace==<br /> CubeSpace manufactures components and actuators designed for CubeSat ADC systems. In addition to their all-in-one CubeADCS (which includes sunsensors, magnetorquers, magnetometers, and a reaction wheel), individual components (such as a sun sensor board) are also provided. <br /> ==Blue Canyon==<br /> Blue Canyon provides &quot;spacecraft bus platforms&quot; with modular systems configurable for CubeSat missions. This includes extremely high precision ADCS components (0.002º pointing accuracy), radios (up to 15 Mbps downlink), telecommand processing, and other software components.<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=CubeSat_Component_Manufacturers&diff=1961 2016-04-19T03:04:53Z

<p>Amilich: </p> <hr /> <div>Here's a general listing of CubeSat component manufacturers and the components each manufacture. <br /> <br /> ==Pumpkin==<br /> Founded by Stanford Professor Andrew Kalman, Pumpkin aims to provide cubesat kits, components, and software. <br /> * Specialties: <br /> ** Salvo Real Time Operating System <br /> ** CubeSatKit and development hardware for a variety of microcontrollers <br /> ** Software for interfacing with a variety of other relevant components, such as radios and EPS systems <br /> [[File: Cubesatkit_logo.jpg |80px]] <br /> ==ClydeSpace==<br /> Particularly in the field of power consumption and generation, ClydeSpace provides a wide array of COTS CubeSat components. This includes premade solar panels, EPS systems, batteries, and deployable solar panels. <br /> ClydeSpace also provides a CubeSat onboard computer module, though the flexibility and applications of this system seemed somewhat unclear. <br /> [[File: Clydespace_batt.jpg |80px]] <br /> ==AstroDev===<br /> Astronautical Development manufactures and sells CubeSat radio hardware. This includes the Helium and Lithium radios, which have been used on past satellites built by the Stanford Space Systems Development Laboratory.<br /> [[File: Astrodev_lithium.jpg |80px]] <br /> ==CubeSpace==<br /> CubeSpace manufactures components and actuators designed for CubeSat ADC systems. In addition to their all-in-one CubeADCS (which includes sunsensors, magnetorquers, magnetometers, and a reaction wheel), individual components (such as a sun sensor board) are also provided. <br /> ==Blue Canyon==<br /> Blue Canyon provides &quot;spacecraft bus platforms&quot; with modular systems configurable for CubeSat missions. This includes extremely high precision ADCS components (0.002º pointing accuracy), radios (up to 15 Mbps downlink), telecommand processing, and other software components.<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=CubeSat_Component_Manufacturers&diff=1960 2016-04-19T03:03:32Z

<p>Amilich: </p> <hr /> <div>Here's a general listing of CubeSat component manufacturers and the components each manufacture. <br /> <br /> *'''Pumpkin'''<br /> ** Founded by Stanford Professor Andrew Kalman, Pumpkin aims to provide cubesat kits, components, and software. <br /> ** Specialties: <br /> *** Salvo Real Time Operating System <br /> *** CubeSatKit and development hardware for a variety of microcontrollers <br /> *** Software for interfacing with a variety of other relevant components, such as radios and EPS systems <br /> [[File: Cubesatkit_logo.jpg |80px]] <br /> *'''ClydeSpace''' <br /> ** Particularly in the field of power consumption and generation, ClydeSpace provides a wide array of COTS CubeSat components. This includes premade solar panels, EPS systems, batteries, and deployable solar panels. <br /> *** ClydeSpace also provides a CubeSat onboard computer module, though the flexibility and applications of this system seemed somewhat unclear. <br /> [[File: Clydespace_batt.jpg |80px]] <br /> *'''AstroDev''' <br /> ** Astronautical Development manufactures and sells CubeSat radio hardware. This includes the Helium and Lithium radios, which have been used on past satellites built by the Stanford Space Systems Development Laboratory.<br /> [[File: Astrodev_lithium.jpg |80px]] <br /> *'''CubeSpace'''<br /> ** CubeSpace manufactures components and actuators designed for CubeSat ADC systems. In addition to their all-in-one CubeADCS (which includes sunsensors, magnetorquers, magnetometers, and a reaction wheel), individual components (such as a sun sensor board) are also provided. <br /> *'''Blue Canyon''' <br /> ** Blue Canyon provides &quot;spacecraft bus platforms&quot; with modular systems configurable for CubeSat missions. This includes extremely high precision ADCS components (0.002º pointing accuracy), radios (up to 15 Mbps downlink), telecommand processing, and other software components.<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=File:Astrodev_lithium.jpg&diff=1959 2016-04-19T03:03:16Z

<p>Amilich: </p> <hr /> <div></div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=CubeSat_Component_Manufacturers&diff=1958 2016-04-19T03:02:39Z

<p>Amilich: </p> <hr /> <div>Here's a general listing of CubeSat component manufacturers and the components each manufacture. <br /> <br /> *'''Pumpkin'''<br /> ** Founded by Stanford Professor Andrew Kalman, Pumpkin aims to provide cubesat kits, components, and software. <br /> ** Specialties: <br /> *** Salvo Real Time Operating System <br /> *** CubeSatKit and development hardware for a variety of microcontrollers <br /> *** Software for interfacing with a variety of other relevant components, such as radios and EPS systems <br /> [[File: Cubesatkit_logo.jpg |80px]] <br /> *'''ClydeSpace''' <br /> ** Particularly in the field of power consumption and generation, ClydeSpace provides a wide array of COTS CubeSat components. This includes premade solar panels, EPS systems, batteries, and deployable solar panels. <br /> *** ClydeSpace also provides a CubeSat onboard computer module, though the flexibility and applications of this system seemed somewhat unclear. <br /> [[File: Clydespace_batt.jpg |80px]] <br /> *'''AstroDev''' <br /> ** Astronautical Development manufactures and sells CubeSat radio hardware. This includes the Helium and Lithium radios, which have been used on past satellites built by the Stanford Space Systems Development Laboratory.<br /> *'''CubeSpace'''<br /> ** CubeSpace manufactures components and actuators designed for CubeSat ADC systems. In addition to their all-in-one CubeADCS (which includes sunsensors, magnetorquers, magnetometers, and a reaction wheel), individual components (such as a sun sensor board) are also provided. <br /> *'''Blue Canyon''' <br /> ** Blue Canyon provides &quot;spacecraft bus platforms&quot; with modular systems configurable for CubeSat missions. This includes extremely high precision ADCS components (0.002º pointing accuracy), radios (up to 15 Mbps downlink), telecommand processing, and other software components.<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=File:Clydespace_batt.jpg&diff=1956 2016-04-19T02:58:38Z

<p>Amilich: </p> <hr /> <div></div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=CubeSat_Component_Manufacturers&diff=1955 2016-04-19T02:57:45Z

<p>Amilich: </p> <hr /> <div>Here's a general listing of CubeSat component manufacturers and the components each manufacture. <br /> <br /> *'''Pumpkin'''<br /> ** Founded by Stanford Professor Andrew Kalman, Pumpkin aims to provide cubesat kits, components, and software. <br /> ** Specialties: <br /> *** Salvo Real Time Operating System <br /> *** CubeSatKit and development hardware for a variety of microcontrollers <br /> *** Software for interfacing with a variety of other relevant components, such as radios and EPS systems <br /> [[File: Cubesatkit_logo.jpg |80px]]<br /> *'''ClydeSpace''' <br /> ** Particularly in the field of power consumption and generation, ClydeSpace provides a wide array of COTS CubeSat components. This includes premade solar panels, EPS systems, batteries, and deployable solar panels. <br /> *** ClydeSpace also provides a CubeSat onboard computer module, though the flexibility and applications of this system seemed somewhat unclear. <br /> *'''AstroDev''' <br /> ** Astronautical Development manufactures and sells CubeSat radio hardware. This includes the Helium and Lithium radios, which have been used on past satellites built by the Stanford Space Systems Development Laboratory.<br /> *'''CubeSpace'''<br /> ** CubeSpace manufactures components and actuators designed for CubeSat ADC systems. In addition to their all-in-one CubeADCS (which includes sunsensors, magnetorquers, magnetometers, and a reaction wheel), individual components (such as a sun sensor board) are also provided. <br /> *'''Blue Canyon''' <br /> ** Blue Canyon provides &quot;spacecraft bus platforms&quot; with modular systems configurable for CubeSat missions. This includes extremely high precision ADCS components (0.002º pointing accuracy), radios (up to 15 Mbps downlink), telecommand processing, and other software components.<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=CubeSat_Component_Manufacturers&diff=1950 2016-04-19T02:54:39Z

<p>Amilich: </p> <hr /> <div>Here's a general listing of CubeSat component manufacturers and the components each manufacture. <br /> <br /> [[File: Cubesatkit_logo.jpg |80px]]<br /> <br /> *'''Pumpkin'''<br /> ** Founded by Stanford Professor Andrew Kalman, Pumpkin aims to provide cubesat kits, components, and software. <br /> ** Specialties: <br /> *** Salvo Real Time Operating System <br /> *** CubeSatKit and development hardware for a variety of microcontrollers <br /> *** Software for interfacing with a variety of other relevant components, such as radios and EPS systems <br /> *'''ClydeSpace''' <br /> ** Particularly in the field of power consumption and generation, ClydeSpace provides a wide array of COTS CubeSat components. This includes premade solar panels, EPS systems, batteries, and deployable solar panels. <br /> *** ClydeSpace also provides a CubeSat onboard computer module, though the flexibility and applications of this system seemed somewhat unclear. <br /> *'''AstroDev''' <br /> ** Astronautical Development manufactures and sells CubeSat radio hardware. This includes the Helium and Lithium radios, which have been used on past satellites built by the Stanford Space Systems Development Laboratory.<br /> *'''CubeSpace'''<br /> ** CubeSpace manufactures components and actuators designed for CubeSat ADC systems. In addition to their all-in-one CubeADCS (which includes sunsensors, magnetorquers, magnetometers, and a reaction wheel), individual components (such as a sun sensor board) are also provided. <br /> *'''Blue Canyon''' <br /> ** Blue Canyon provides &quot;spacecraft bus platforms&quot; with modular systems configurable for CubeSat missions. This includes extremely high precision ADCS components (0.002º pointing accuracy), radios (up to 15 Mbps downlink), telecommand processing, and other software components.<br /> <br /> [[Category: Satellites]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=File:Cubesatkit_logo.jpg&diff=1949 2016-04-19T02:52:43Z

<p>Amilich: </p> <hr /> <div></div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=CubeSat_Component_Manufacturers&diff=1910 2016-04-18T06:24:31Z

<p>Amilich: </p> <hr /> <div>Here's a general listing of CubeSat component manufacturers and the components each manufacture. <br /> <br /> *'''Pumpkin'''<br /> ** Founded by Stanford Professor Andrew Kalman, Pumpkin aims to provide cubesat kits, components, and software. <br /> ** Specialties: <br /> *** Salvo Real Time Operating System <br /> *** CubeSatKit and development hardware for a variety of microcontrollers <br /> *** Software for interfacing with a variety of other relevant components, such as radios and EPS systems <br /> *'''ClydeSpace''' <br /> ** Particularly in the field of power consumption and generation, ClydeSpace provides a wide array of COTS CubeSat components. This includes premade solar panels, EPS systems, batteries, and deployable solar panels. <br /> *** ClydeSpace also provides a CubeSat onboard computer module, though the flexibility and applications of this system seemed somewhat unclear. <br /> *'''AstroDev''' <br /> ** Astronautical Development manufactures and sells CubeSat radio hardware. This includes the Helium and Lithium radios, which have been used on past satellites built by the Stanford Space Systems Development Laboratory.<br /> *'''CubeSpace'''<br /> ** CubeSpace manufactures components and actuators designed for CubeSat ADC systems. In addition to their all-in-one CubeADCS (which includes sunsensors, magnetorquers, magnetometers, and a reaction wheel), individual components (such as a sun sensor board) are also provided. <br /> *'''Blue Canyon''' <br /> ** Blue Canyon provides &quot;spacecraft bus platforms&quot; with modular systems configurable for CubeSat missions. This includes extremely high precision ADCS components (0.002º pointing accuracy), radios (up to 15 Mbps downlink), telecommand processing, and other software components.</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=CubeSat_Component_Manufacturers&diff=1909 2016-04-18T06:18:59Z

<p>Amilich: Created page with &quot;Here&#039;s a general listing of CubeSat component manufacturers and the components each manufacture. *&#039;&#039;&#039;Pumpkin&#039;&#039;&#039; ** Founded by Stanford Professor Andrew Kalman, Pumpkin aims...&quot;</p> <hr /> <div>Here's a general listing of CubeSat component manufacturers and the components each manufacture. <br /> <br /> *'''Pumpkin'''<br /> ** Founded by Stanford Professor Andrew Kalman, Pumpkin aims to provide cubesat kits, components, and software. <br /> ** Specialties: <br /> *** Salvo Real Time Operating System <br /> *** CubeSatKit and development hardware for a variety of microcontrollers <br /> *** Software for interfacing with a variety of other relevant components, such as radios and EPS systems <br /> *'''ClydeSpace''' <br /> ** Particularly in the field of power consumption and generation, ClydeSpace provides a wide array of COTS CubeSat components. This includes premade solar panels, EPS systems, batteries, and deployable solar panels. <br /> *** ClydeSpace also provides a CubeSat onboard computer module, though the flexibility and applications of this system seemed somewhat unclear. <br /> *'''AstroDev''' <br /> ** Astronautical Development manufactures and sells CubeSat radio hardware. This includes the Helium and Lithium radios, which have been used on past satellites built by the Stanford Space Systems Development Laboratory.</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=COTS_CubeSat_Radio&diff=1908 2016-04-18T06:10:51Z

<p>Amilich: </p> <hr /> <div>Radio is currently the standard mode of CubeSat telecommunication. Hence, there are a variety of COTS CubeSat radio options available. <br /> <br /> '''Here's a list of COTS CubeSat radio system suppliers:'''<br /> *AstroDev<br /> *Stensat<br /> *ISIS (good luck googling that one)<br /> <br /> '''Here's a preliminary list of commercial CubeSat transmitters useful for a one-way downlink:'''<br /> *'''Stensat Radio Beacon'''<br /> **Cost: $750<br /> **Downlink rate: AX.25 Unnumbered Information (UI) packets at 1200 bps AFSK and 9600 bps FSK<br /> **Transmitter Frequency range: 420-450 MHz or 144-148 MHz (depending on model)<br /> **Mass: 50g<br /> **Dimensions: 44.45 x 78.74 (mm) (PCB layout)<br /> **Power Consumption: &lt;3W<br /> **More details on the product page: [http://www.stensat.org/products.html#]<br /> *'''ISIS TXS S-Band Transmitter'''<br /> **Cost: $9600<br /> **Downlink rate: up to 100 kbps<br /> **Transmitter Frequency range: 2100 MHz - 2500 MHz<br /> **Mass: 62g<br /> **Dimensions: 90 x 96 x 15 (mm)<br /> **Power Consumption: &lt;3.5W<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=9&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> *'''Integrated S-Band Transmitter'''<br /> **Cost: $7300<br /> **Downlink rate: 1.06 Mbs (max)<br /> **Transmitter Frequency range: 2200-2300 MHz, adjustable in steps of 100 kHz<br /> **Mass: 75g<br /> **Dimensions: 95 x 46 x 15 (mm)<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=84&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> <br /> '''Here's a preliminary list of commercial CubeSat transceivers useful for bi-directional communication:'''<br /> <br /> *'''ISIS VHF down UHF up Duplex Transceiver'''<br /> **Cost: $9600<br /> **Downlink rate: 1200, 2400, 4800 or 9600 bps<br /> **Uplink rate: 300 or 1200 bps<br /> **Transmitter Frequency range: 130 - 160 MHz (VHF)<br /> **Receiver Frequency range: 400 - 450 Mhz (UHF)<br /> **Mass: 85g<br /> **Dimensions: 96 x 90 x 15 (mm)<br /> **Power Consumption: &lt;1.7W (transmitter on), &lt;0.2W (receiver only)<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=73&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> *'''ISIS UHF down VHF up Duplex Transceiver'''<br /> **Cost: $9600<br /> **Downlink rate: 1200, 2400, 4800 or 9600 bps<br /> **Uplink rate: 1200 bps<br /> **Transmitter Frequency range: 420-450 MHz (UHF)<br /> **Receiver Frequency range: 140-150 MHz (VHF)<br /> **Mass: 75g<br /> **Dimensions: 96 x 90 x 15 (mm)<br /> **Power Consumption: &lt;4.0W (transmitter on), &lt;0.480W (receiver only)<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=11&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> * '''Astrodev Lithium'''<br /> ** Cost: ~$5000<br /> ** Downlink rate: Max 77 kbps <br /> ** Power Consumption: &lt; 10.0W; 4.0W transmitter power <br /> ** Efficiency: 40%<br /> <br /> [[Category: Satellites]] [[Category:Optical Communications]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=COTS_CubeSat_Radio&diff=1907 2016-04-18T06:10:41Z

<p>Amilich: </p> <hr /> <div>Radio is currently the standard mode of CubeSat telecommunication. Hence, there are a variety of COTS CubeSat radio options available. <br /> <br /> '''Here's a list of COTS CubeSat radio system suppliers:'''<br /> *AstroDev<br /> *Stensat<br /> *ISIS (good luck googling that one)<br /> <br /> '''Here's a preliminary list of commercial CubeSat transmitters useful for a one-way downlink:'''<br /> *'''Stensat Radio Beacon'''<br /> **Cost: $750<br /> **Downlink rate: AX.25 Unnumbered Information (UI) packets at 1200 bps AFSK and 9600 bps FSK<br /> **Transmitter Frequency range: 420-450 MHz or 144-148 MHz (depending on model)<br /> **Mass: 50g<br /> **Dimensions: 44.45 x 78.74 (mm) (PCB layout)<br /> **Power Consumption: &lt;3W<br /> **More details on the product page: [http://www.stensat.org/products.html#]<br /> *'''ISIS TXS S-Band Transmitter'''<br /> **Cost: $9600<br /> **Downlink rate: up to 100 kbps<br /> **Transmitter Frequency range: 2100 MHz - 2500 MHz<br /> **Mass: 62g<br /> **Dimensions: 90 x 96 x 15 (mm)<br /> **Power Consumption: &lt;3.5W<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=9&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> *'''Integrated S-Band Transmitter'''<br /> **Cost: $7300<br /> **Downlink rate: 1.06 Mbs (max)<br /> **Transmitter Frequency range: 2200-2300 MHz, adjustable in steps of 100 kHz<br /> **Mass: 75g<br /> **Dimensions: 95 x 46 x 15 (mm)<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=84&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> <br /> '''Here's a preliminary list of commercial CubeSat transceivers useful for bi-directional communication:'''<br /> <br /> *'''ISIS VHF down UHF up Duplex Transceiver'''<br /> **Cost: $9600<br /> **Downlink rate: 1200, 2400, 4800 or 9600 bps<br /> **Uplink rate: 300 or 1200 bps<br /> **Transmitter Frequency range: 130 - 160 MHz (VHF)<br /> **Receiver Frequency range: 400 - 450 Mhz (UHF)<br /> **Mass: 85g<br /> **Dimensions: 96 x 90 x 15 (mm)<br /> **Power Consumption: &lt;1.7W (transmitter on), &lt;0.2W (receiver only)<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=73&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> *'''ISIS UHF down VHF up Duplex Transceiver'''<br /> **Cost: $9600<br /> **Downlink rate: 1200, 2400, 4800 or 9600 bps<br /> **Uplink rate: 1200 bps<br /> **Transmitter Frequency range: 420-450 MHz (UHF)<br /> **Receiver Frequency range: 140-150 MHz (VHF)<br /> **Mass: 75g<br /> **Dimensions: 96 x 90 x 15 (mm)<br /> **Power Consumption: &lt;4.0W (transmitter on), &lt;0.480W (receiver only)<br /> **More details on the product page: [http://www.cubesatshop.com/index.php?page=shop.product_details&amp;flypage=flypage.tpl&amp;product_id=11&amp;category_id=5&amp;option=com_virtuemart&amp;Itemid=67]<br /> * &quot;Astrodev Lithium&quot; <br /> ** Cost: ~$5000<br /> ** Downlink rate: Max 77 kbps <br /> ** Power Consumption: &lt; 10.0W; 4.0W transmitter power <br /> ** Efficiency: 40%<br /> <br /> [[Category: Satellites]] [[Category:Optical Communications]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=Attitude_Determination_and_Control_(ADCS)&diff=1906 2016-04-18T06:04:32Z

<p>Amilich: </p> <hr /> <div>{{opcomms-sidebar}}<br /> <br /> An Attitude Determination and Control (ADCS) provides measurements regarding a satellite's orbit and allows the satellite to change its inertial position. <br /> <br /> == Examples of ADCS Hardware ==<br /> * Most ADCS hardware relies on an ability to change the satellite's position relative to the Earth. <br /> ** Reaction wheels: Using small, spinning wheels, reaction wheels allow satellite positioning using the principle of conservation of momentum. <br /> *** CubeADCS: CubeSpace's CubeADCS utilizes a variety of sensors (including magnetometers and sun sensors) to accurately determine the satellite's precision. It can use either magnetic torquers (see below) or reaction wheels for attitude determination. <br /> ** Magnetorquer: By creating a magnetic field that interact's with the Earth's own magnetic field, a magnetic torquer produces a force that can rotate a satellite. <br /> ** Control Moment Gyros: Similar to Reaction Wheels, Control Moment Gyros use a gimbal to change the rotation of a spinning flywheel. See https://www.youtube.com/watch?v=JTWA6tUREi8 for an excellent visual demonstration of CMG technology. <br /> ** Thrusters: Though far more uncommon on small satellites, thrusters remain a dependable and conceptually straightforward method of attitude determination. <br /> <br /> == ADCS Specifications ==<br /> * ADCS Pointing Accuracy<br /> ** ADCS accuracy varies depending on the type and quality of mechanisms and control systems. The popular CubeSpace hardware used on 2U QB50 satellites has an accuracy of 0.2º to 0.6º (keep in mind, however, that the QB50 missions requirements regarding ADCS precision are fairly lax). The BlueCanyon XB1 high precision ADCS suggests an accuracy of 0.002º. <br /> * ADCS Maneuvering Rates</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=Attitude_Determination_and_Control_(ADCS)&diff=1905 2016-04-18T05:59:10Z

<p>Amilich: </p> <hr /> <div>{{opcomms-sidebar}}<br /> <br /> An Attitude Determination and Control (ADCS) provides measurements regarding a satellite's orbit and allows the satellite to change its inertial position. <br /> <br /> == Examples of ADCS Hardware ==<br /> * Most ADCS hardware relies on an ability to change the satellite's position relative to the Earth. <br /> ** Reaction wheels: Using small, spinning wheels, reaction wheels allow satellite positioning using the principle of conservation of momentum. <br /> ** Magnetorquer: By creating a magnetic field that interact's with the Earth's own magnetic field, a magnetic torquer produces a force that can rotate a satellite. <br /> ** Control Moment Gyros: Similar to Reaction Wheels, Control Moment Gyros use a gimbal to change the rotation of a spinning flywheel. See https://www.youtube.com/watch?v=JTWA6tUREi8 for an excellent visual demonstration of CMG technology. <br /> ** Thrusters: Though far more uncommon on small satellites, thrusters remain a dependable and conceptually straightforward method of attitude determination. <br /> <br /> == ADCS Specifications ==<br /> * ADCS Pointing Accuracy<br /> ** ADCS accuracy varies depending on the type and quality of mechanisms and control systems. The CubeSpace hardware popular for use on 2U QB50 satellites has an accuracy of 0.2º to 0.6º. The BlueCanyon XB1 high precision ADCS suggests an accuracy of 0.002º. <br /> * ADCS Maneuvering Rates</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=Attitude_Determination_and_Control_(ADCS)&diff=1903 2016-04-18T03:43:23Z

<p>Amilich: </p> <hr /> <div>{{opcomms-sidebar}}<br /> <br /> An Attitude Determination and Control (ADCS)<br /> <br /> == Examples of ADCS Hardware ==<br /> <br /> <br /> == ADCS Pointing Accuracy ==</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=Attitude_Determination_and_Control_(ADCS)&diff=1902 2016-04-18T03:20:10Z

<p>Amilich: ADCS System on Satellites</p> <hr /> <div>{{opcomms-sidebar}}</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=HPR_Background_Information&diff=1552 2016-03-05T01:01:26Z

<p>Amilich: Spellcheck</p> <hr /> <div>NASA's online [https://spaceflightsystems.grc.nasa.gov/education/rocket/shortr.html Beginner's Guide To Rockets] will get you started on many of the basic principles governing rocketry. If you manage to make your way through all of these, you will understand the vernacular often used in rocketry.<br /> <br /> == Jargon ==<br /> <br /> === Impulse and its Specificity ===<br /> <br /> Impulse (or total impulse) is defined as equal to force multiplied by time - it is a measure of how powerful motors are, and can easily give you your change in velocity, Impulse / Mass, assuming no drag or gravity losses. (There will always be drag and gravity losses.) Total impulse can be thought of as the area under the thrust curve.<br /> <br /> [[File:L1_Guide_Thrust_Curve.png|400px|thumb|frame|center|Thrust curves of motors with the same total impulse]]<br /> <br /> In the above graph, each of those three motors have the same total impulse (area under the curve), but with very different thrust profiles. The letter designation for each motor (e.g. in E15, H125, or M1250) are a measure of total impulse and each successive letter represents double the total impulse.<br /> <br /> It turns out that impulse alone is not a gooad measure for rocket fuel performance; it is technically possible to use wood and air as rocket fuels, and to get an insanely large impulse by making the engine really big. That will never get you to space. Instead, rockets really care about a number called the specific impulse, defined as impulse divided by the mass of the propellant and the gravitational constant. This gives a far better picture of what constitutes a good rocket fuel, although there are definitely other considerations.<br /> <br /> === Motor Systems (DMS and RMS) ===<br /> [[File:DMSMotor.jpg|thumb|200px|right|A DMS with its packaging]]<br /> <br /> DMS stands for Disposable Motor System. These motors are one time use only, and are very easy to work with. <br /> <br /> RMS stands for Reloadable Motor System. These types of motors are harder to work with, since they require the maintenance of a motor casing and proficiency in loading, cleaning, and reloading the casing. After purchasing the relatively expensive casing, one must learn how to assemble it with motor reloads. If not assembled properly, your rocket will most likely not make it through the flight. However, once you become good at assembling and using RMS, it is cheaper to merely have to purchase propellant each time you launch instead of an entirely new DMS motor.<br /> <br /> === Motor Retention (Positive or Otherwise) and Adaptors ===<br /> <br /> There is one direction we care about when discussing motor retention, the y direction (axially). Simply put, the job of a motor retainer is to keep your motor from falling out of your rocket or allowing it to shoot through the nosecone upon ignition, resulting in a cato. Depending on the company, motor retainers have a couple different ways they work. For the slimline retainers used in the SSI Firestorm kit, the motor retainers use retaining rings. These rings are removable and are located on the lip of the the retainer. The purpose of the rings are to keep the motor from sliding out of the bottom while a lip on the body of the retainer prevents the motor from launching through the rocket's nosecone. For any 38mm motor being used in the 58mm Firestorm airframe, a motor adaptor is going to be used which has identical retaining rings, except smaller in diameter, to the motor retainer.<br /> <br /> <br /> <br /> You can purchase/make motor adaptors which allow you to have a motor of a diameter that is smaller than the diameter of your rocket. For example: If one wanted to launch an L1 with a 54mm H motor but his or her rocket had an ID of 98mm, that person would purchase/make a motor adapter to keep the motor stable and restrained. Motor adapters consist of a tube that has the same ID as the motor's OD and uses centering rings to keep the motor centered between the airframe walls. If you are planning on using various diameter motors for the same airframe it might be a wise choice to invest in a motor retention system that allows the user to buy various components designed to work with different sized motors.<br /> <br /> '''Some Quick Terminology'''<br /> Positive = not falling out the bottom.<br /> <br /> == Stability ==<br /> <br /> [[File:L1_Guide_Stability.png|thumb|200px|right|CG and CP for stable flight]]<br /> <br /> === Center of Gravity ===<br /> <br /> An objects center of gravity is its (rigorously and mathematically defined) middle point. The force of gravity can be simulated to act here, and the object will tend to rotate about this point, making it crucial to finding rocket stability.<br /> <br /> The relation of CG to your L1 rocket is its relation to the center of pressure (CP). For stable flight your CG needs to be towards the nosecone of your CP. If you determine that your CG is too close to your CP and need to move it forward because you can't change the position of your CP, a common method is to add some mass weight to your nosecone.<br /> <br /> === Center of Pressure ===<br /> The center of pressure is the location at which we can model the aerodynamic effects as acting. In other words, the drag on the rocket acts at this point. If the center of pressure is below the center of gravity, then the downwards force of drag will keep the rocket upright, while a center of pressure above the center of gravity will flip the rocket. A CP and CG at the same point will create a neutrally stable rocket, meaning that any incidental forces could theoretically spin it. This makes the distance between the CP and CG critically important for determining whether flight will be safe and successful.<br /> <br /> The main tool we have to change the center of pressure is the size of the rocket's fins - larger fins will bring the center of pressure lower down on the rocket, increasing its stability.<br /> <br /> To calculate center of pressure, you can use the Barrowman equations ([http://www.scalerocketry.com/equations/barrowman.htm link to a slighty confusing example]) or the [https://www.apogeerockets.com/education/downloads/Newsletter18.pdf cardboard cutout method].<br /> <br /> Another way to determine the CP of your rocket is to use a program like OpenRocket or RockSim. Both of these programs take all the information you input about your rocket and input into the Barrowman equations for you.<br /> <br /> === Calibers ===<br /> <br /> A caliber is a unit of measurement defined as the diameter of the airframe. Calibers are used to measure the distance between the CP and CG - it doesn't make sense to solely measure based on distance, as a 3&quot; difference on a 2&quot; OD, 24&quot; long rocket is very different from a 2&quot; difference on a 10' long, 6&quot; OD one.<br /> <br /> Calibers measure the length between CP and CG allowing for a much more fair comparison between different rocket sizes. It would be correct to say, the CG is 2 calibers away from the CP. <br /> <br /> As a rule of thumb, having your CP 1.5-2 calibers in front of your CG is considered good, while numbers outside of that range tend to be either under-or-over-stable.<br /> <br /> == Motor Specs ==<br /> <br /> Solid rocket motors have a fairly standardized labeling system. On the casing (or reload) itself there is a three-part code which denotes what the total impulse range is, the average thrust, and the delay grain length. All these numbers are in standard metric units.<br /> <br /> The letter designation represents the total impulse. Each letter category represents double the total impulse of the previous letter category.<br /> <br /> [[File:L1_Guide_Motor_Classification.png|300px|thumb|frame|center|Letter designations increase total impulse exponentially]]<br /> <br /> Motor classification table:<br /> <br /> [[File:MotorClassification.png|300px|thumb|center|Motor Classification]]<br /> <br /> <br /> <br /> ===Motor Designation Breakdown===<br /> To better understand how to read a motor label lets take an example:<br /> <br /> '''Aerotech H550ST-14A'''<br /> <br /> Here is the spec sheet for this motor[http://www.aerotech-rocketry.com/uploads/4e952284-bb4b-4943-8904-9a0719e8ee3a_AT%20H550ST%20SU%20jun%2019.pdf]. This is the motor that SSI uses for its L1 certification launches.<br /> <br /> *'''H''': the letter designating the impulse range. For an H this is from 160 Ns - 320 Ns.<br /> *'''550''': denotes that the motor's average thrust is 550 N.<br /> *'''ST''': denotes what type of propellant is in the casing. In this case, ST stands for &quot;Super Thunder&quot;. Aerotech has various names for their different types of propellants, however, often these names are only denoting the color of the flame rather than the chemical compounds that it is made of. <br /> *'''14''': denotes that the motor will fire its ejection charge 14 s after burnout unless it is adjusted, as indicated by the A. Motor delay times can be adjusted with a motor delay tool (otherwise known as a proprietary screwdriver, here is a link to buy one[http://www.buyrocketmotors.com/aerotech-universal-delay-drilling-tool-for-dms-motors/]).<br /> <br /> == Recovery ==<br /> <br /> [[File:L1_Guide_Delay_Charge.png|thumb|165px|right|Motor delay charge]]<br /> Recovery is the second stage of a simple non-complex rocket, aka basic L1. Although it would seem like the largest percentage of failure would happen during ascent, 75% of failed rockets are a result of a faulty recovery system. Common points of failure for an L1 are: the parachute did not deploy out of the airframe, the parachute deployed too soon before or too far after apogee, line tangling, and too quick of a descent. All of these aspects are things that you should consider when compiling your recovery system.<br /> <br /> For L1 all a rocketeer needs is single stage deployment. Simply put, only a main parachute is required to bring the rocket safely back to the ground. Because it is single stage, the parachute should be ejected as close to apogee as possible to prevent unnecessary damage to the rocket. Apogee is the highest point of a rocket trajectory, where the vertical velocity is momentarily zero and the rocket transitions from ascent to descent. This is the point at which the rocket is moving slowest and thus is the most ideal for deployment of a parachute.<br /> <br /> For typical L1 rockets, after the motor burns through its main propellant, it burns through a delay grain. This is a slow-burning section at the end of the motor which acts as a timer. Once it has burned through the delay grain, the flame front ignites an ejection charge loaded in the charge well at the front of the motor. This ejection charge, typically black powder, pressurizes the body tube of the rocket and forces the nose cone out, along with the parachute. To test whether your nose cone has the proper fit (tight enough to stay on during flight but loose enough to eject for recovery), hold the back end of your completed, and unloaded, rocket to your mouth and blow hard with a good seal. The nose cone and parachute should both pop out. If you are incapable of doing this, another test can be done by vigorously shaking the rocket by holding the nosecone. The nosecone should separate from the rocket by doing this.<br /> <br /> == Simulations ==<br /> <br /> [[File:exampleOpenRocket.jpg|thumb|right|300px|Example of the OpenRocket interface]]<br /> <br /> It is always important to know what your rocket will do (assuming that things go according to plan), and we use a program called OpenRocket to find the flight profile of our rockets. The program is free, and can be found here[http://openrocket.sourceforge.net/]<br /> <br /> OpenRocket is quite easy to learn, and is quite accurate for sub-Mach rockets (those that fly faster should use RasAero to model drag forces.) OpenRocket includes ascent, including a massive database of thrust curves, as well as a simulated descent using the parachutes included in the rocket. If used properly, it can output data from height of apogee to time of flight to drift distance, all of which are incredibly useful while designing your rocket. (Hint: the center of pressure calculation is extremely important.)<br /> <br /> One other program of note is called FinSim, which can model possible vibrations within fins. If unchecked, these vibrations can grow and shear the fins off, likely dooming the rocket. The program is required for transonic and supersonic flights, and can be found here[http://www.aerorocket.com/finsim.html]<br /> <br /> [[Category: Rockets]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=Project_Sol&diff=1332 2016-02-08T07:36:45Z

<p>Amilich: </p> <hr /> <div>{{balloon-stub}}<br /> <br /> Project Sol is the 2015-2016 Balloons Team project to develop effective solar tracking algorithms, high efficiency solar panels, and ultimately equip the Valve-Ballast System with sufficient power for long range flights. <br /> <br /> Our mission is to create a UV-tracking solar cell power system. The solar panels must be pointed at the sun at an optimal angle of 28 degrees from vertical (see calculation here). They will be controlled by a mini motor low-speed gearbox that rotates the panels to point towards the sun. The panels are installed on a laser-cut rotating duron base that sits below the styrofoam box housing the motor and electronics. The insulated central box will house a Teensy, Arduino, GPS, and AdafruIt 10 degrees of freedom board. Optimal light will be calculated using six photovoltaic cells around the base of the solar panel rotator and two located on the top of the panels themselves. The cells will be wired into the central box. For this launch, we are using six panels wired in series. The expected voltage in full sunlight is 7 volts open-circuit voltage maximum, with 1.25 amps of short-circuit current. The voltage is approximately .833 volts per solar cell.<br /> <br /> {{balloon-footer}}<br /> <br /> [[Category: High Altitude Balloons]][[Category: Projects]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=Project_Sol&diff=1331 2016-02-08T07:36:35Z

<p>Amilich: </p> <hr /> <div>{{balloon-stub}}<br /> <br /> Project Sol is the 2015-2016 Balloons Team project to develop effective solar tracking algorithms, high efficiency solar panels, and ultimately equip the Valve-Ballast System with sufficient power for long range flights. <br /> <br /> Our mission is to create a UV-tracking solar cell power system. The solar panels must be pointed at the sun at an optimal angle of 28 degrees from vertical (see calculation here). They will be controlled by a mini motor low-speed gearbox that rotates the panels to point towards the sun. The panels are installed on a laser-cut rotating duron base that sits below the styrofoam box housing the motor and electronics. The insulated central box will house a Tnsy, Arduino, GPS, and AdafruIt 10 degrees of freedom board. Optimal light will be calculated using six photovoltaic cells around the base of the solar panel rotator and two located on the top of the panels themselves. The cells will be wired into the central box. For this launch, we are using six panels wired in series. The expected voltage in full sunlight is 7 volts open-circuit voltage maximum, with 1.25 amps of short-circuit current. The voltage is approximately .833 volts per solar cell.<br /> <br /> {{balloon-footer}}<br /> <br /> [[Category: High Altitude Balloons]][[Category: Projects]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=Project_Sol&diff=984 2016-01-26T07:17:05Z

<p>Amilich: </p> <hr /> <div>{{balloon-stub}}<br /> <br /> Project Sol is the 2015-2016 Balloons Team project to develop effective solar tracking algorithms, high efficiency solar panels, and ultimately equip the Valve-Ballast System with sufficient power for long range flights. <br /> <br /> {{balloon-footer}}<br /> <br /> [[Category: High Altitude Balloons]][[Category: Projects]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=QB50_Discovery&diff=982 2016-01-26T07:14:29Z

<p>Amilich: </p> <hr /> <div>{{satellites-stub}}<br /> <br /> [[Category: Satellites]]<br /> <br /> The satellite QB50 Discovery is currently under construction by Professor Kalman's SSDL laboratory. A number of SSI members have contributed to the project, including Jan Kolmas, Rishi Bedi, Thomas Teisberg, Iskender Kushan, and Andrew Milich. It will be launched in the multinational QB50 constellation of cubesats.</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=QB50_Discovery&diff=975 2016-01-26T07:03:20Z

<p>Amilich: </p> <hr /> <div>{{satellites-stub}}<br /> <br /> [[Category: Satellites]]<br /> <br /> The satellite QB50 Discovery is currently under construction by Professor Kalman's SSDL laboratory. A number of SSI members have contributed to the project, including Rishi Bedi, Thomas Teisberg, Iskender Kushan, and Andrew Milich. It will be launched in the multinational QB50 constellation of cubesats.</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=Pegasus&diff=974 2016-01-26T06:59:55Z

<p>Amilich: </p> <hr /> <div>The Pegasus team is designing a rocket with the goal of demonstrating the feasibility of controlled recovery from high-powered flight from over 10,000 ft through the use of a parafoil. The team is currently working on the design of an L3 rocket to be launched on March 19, 2016 as well as an L1 to be launched on February 6, 2016, the purpose of which is to test the ejection of the parafoil from the airframe. <br /> {{rocket-project<br /> | header = Pegasus (ARES-2)<br /> | img link = File:Pegasus_Flag.png<br /> | launch date 1 = February 6, 2016<br /> | launch class 1 = L1<br /> | launch site 1 = LUNAR<br /> | launch date 2 = Pending<br /> | launch class 2 = L2<br /> | launch site 2 = Pending<br /> | launch date 3 = Pending<br /> | launch class 3 = L3<br /> | launch site 3 = Pending<br /> | program = Project Daedalus<br /> | last = Talos<br /> | next = Charybdis<br /> }}<br /> <br /> = Team Summary =<br /> <br /> Ian Gomez (Project Manager), Marie Johnson (Team lead), Austin Pineault (Structural Development and Mechanical Systems Integration), Andrew Milich (Avionics, Deployment, and Programming), John Dean (Avionics, Deployment, and Programming), Hannah Williams (Structural Development and Parafoil), Sruti Arulmani, Nate Simon (Parafoil and Aerodynamics). &lt;br /&gt;<br /> <br /> = Launch Vehicle and Payload Summary =<br /> <br /> The purpose of the Pegasus rocket is to demonstrate the feasibility of using a parafoil recovery system to create a controlled, directed recovery for a high-powered rocket from over 10,000 ft.<br /> <br /> The payload of this rocket is the active recovery system and its backup. The payload will be a parafoil deployed at apogee and controlled by two servos throughout descent.<br /> <br /> = Vehicle Criteria =<br /> <br /> == Mission Statement ==<br /> <br /> The Pegasus Rocket team is seeking to develop an efficient and reliable recovery system for high-powered rockets that utilizes a parafoil instead of a parachute.<br /> <br /> == Mission Success Criteria ==<br /> <br /> The mission will be considered successful if the recovered rocket would be able to pass a L3 certification inspection. This means that if the rocket experiences excessive damage to the point that it could not be re-flown that day with a reloaded motor, then the recovery system will have failed. Another criteria is that the rocket will have landed within a 300ft radius of its original target landing space.<br /> <br /> == Constraints ==<br /> <br /> # Tripoli height ceiling of 16,800 ft<br /> # Rocket construction to be made using a “minimum of metallic parts” excepting those necessary for airframe integrity<br /> # Motor impulse to not exceed 10,240 N-s<br /> # Redundant avionics, wiring, and safe arm systems<br /> # Automated program for descent path<br /> # Manual back up control system for descent path<br /> # Back up recovery system consisting of main parachute<br /> # Vertical descent speed of 20 ft/s maximum upon landing<br /> # Budget<br /> <br /> == System Overview ==<br /> <br /> Moments after reaching apogee, a parafoil will deployed from the nosecone of the Firestorm rocket. Structural and control lines of the parafoil will be secured on the exterior of the rocket. Using stepper motors and an XBee, the rocket will be monitored and controlled during descent. This includes real-time data monitoring of position, velocity, vertical speed, and system status as well as options to steer or flare the system. Initially, this will be limited to simple guidance motions such as left or right turns, or flare using both control surfaces simultaneously.<br /> <br /> == Propulsion System ==<br /> <br /> The Cesaroni M1450 was chosen because it is commercially available, reloadable, complies with the Tripoli and California restrictions, keeps our rocket sub Mach-1, and should achieve a maximum height to a safe margin below the maximum ceiling. Thus even if our mass budget increases, there will still be ample altitude to test the parafoil system.<br /> <br /> The M1450 has an average thrust of 1500 N, a total impulse of 10000 N-s, a specific impulse of 210 s, and a burn time of 6.9 s.<br /> <br /> === Flight Characteristics ===<br /> <br /> With current mass budget considerations, the M1450 motor is projected to boost the rocket to a peak of roughly Mach 0.78 and an apogee of roughly 11000 ft after 27 s.<br /> <br /> [[File:Pegasus_Performance_Altitude_Speed.png|thumb|frame|center|1000px|Altitude and Mach variation throughout the flight]]<br /> <br /> On liftoff, the acceleration of the rocket is projected to be roughly 10 g, increasing to a sustained 11.5 g. A maximum drag force of roughly 85 N is expected. Max-Q is expected to occur roughly 4 s into the flight.<br /> <br /> [[File:Pegasus_Performance_Acceleration_Drag.png|thumb|frame|center|1000px|Acceleration and drag forces on the rocket during the motor firing]]<br /> <br /> A nominal static stability ranging between 1.5 and 2.3 calibers is expected in the current configuration.<br /> <br /> [[File:Pegasus_Performance_Mass_Stability.png|thumb|frame|center|1000px|Mass decrease and change in static stability during the motor firing]]<br /> <br /> == Structural Design ==<br /> <br /> The complete launch vehicle can be broken-down into three primary sections: nose cone, forward airframe, and aft airframe.<br /> <br /> === Nose Cone ===<br /> <br /> A fiberglass nose cone will be used. A custom lay-up of fiberglass will be used to control the exact aerodynamic profile and meet the diameter requirements of the rocket.<br /> <br /> === Forward Airframe ===<br /> <br /> The forward airframe will be 6“ in diameter and 44” in length. It will house, from front to rear, the primary recovery system (parafoil), backup recovery system (parachute payload), and avionics bay.<br /> <br /> [[File:Pegasus_Parafoil_Structural_Overview.png|thumb|frame|center|600px|Structural overview for parafoil storage in forward airframe]]<br /> <br /> Each of these components will be separated by bulkheads; the foreward bulkhead is designed to protect the backup recovery system from the parafoil’s expulsion and will be mobile (supported on the aft side by blocks along the inner wall of the airframe) to allow backup system to exit the rocket, while the aft bulkhead is designed to protect the avionics and therefore will be stationary.<br /> <br /> === Aft Airframe ===<br /> <br /> The aft airframe will be 6“ in diameter and 48” in length, and will house the motor retainer and fins, as well as have aft attachment points for the coupler.<br /> <br /> === Fins ===<br /> <br /> There are going to be three fins for this rocket. We are going to be using a trapezoidal design with a root length of 12“ and a tip of 6”. They are to have a span of roughly 12“, a leading sweep of 60, and a trailing sweep of 20. This design choice was made to keep the CP within the ”rule of thumb&amp;quot; 1-2 diameter distance between the CP and CG that generates correct stability. However, there is a concern with how the trailing ends of the fins, which extend beyond the aft end of the rocket, will incur damage upon landing.<br /> <br /> This possibility of damage is to be mitigated by the material choice for the fins. Aluminum is currently the best choice, for resistance to deformation upon landing, malleability and ease of machining, as well as being relatively lightweight.<br /> <br /> === Materials ===<br /> <br /> There will be a variety of materials used for the Pegasus rocket. For the airframes we are currently considering to either use polycarbonate due to its structural qualities. However, we are also considering phenolic for the airframes. The nosecone will be made of fiberglass because it is lightweight and strong as well as relatively easy to shape into smooth and specific designs, such as an ogive nosecone. The fins are currently going to be made from aluminum unless a structural equivalent can be found from a non-metal material. Inner support and structures to hold the motors and avionics will be made from a mixture of wood and aluminum bulkheads, as well as some structural support from aluminum struts.<br /> <br /> == Avionics and Telemetry ==<br /> <br /> Telemetry is accomplished using two XBee 9B 900MHZ 250MW long range radio transmitters. Under line of sight conditions, these are expected to achieve a maximum range of 28 miles. We equipped both with 900 MHZ, low impedance, RP-SMA duck antennas.<br /> <br /> [[File:Pegasus_Avionics_Block_Diagram.png|thumb|300px|right|Avionics block diagram]]<br /> <br /> === Avionics Teensy Pinout ===<br /> <br /> A Teensy 3.2 microncontroller served as the principal brains of the rocket due to considerable size and performance advantages compared to Arduino based platforms. Through software serial, it communicated directly with the XBee (and thus the ground station) while reading from the GPS and 10DOF sensors as well.<br /> <br /> === In-Flight Tracking ===<br /> <br /> The in-flight tracking will use a XBee Pro module and an Adafruit GPS receiver with a ceramic antena.<br /> <br /> [[File:Pegasus_Avionics_XBee.png|80px]]<br /> <br /> For the in-flight communication and redundant tracking, the rocket will rely on live communication via XBee transmitters and the use of a small SPOT GPS for precise location of the rocket.<br /> <br /> === Power Sources and Budget ===<br /> <br /> Due to high power density and low weight, we chose to use a Lithium Polymer battery. As stepper motors require relatively high amounts of voltage and current, we chose a two cell, 7.4 V LiPo. As the motor’s burn time is relatively short, a battery with low mAh was suitable for these applications. This battery is required to power the Teensy, XBee, stepper motors, and sensors used for guidance.<br /> <br /> == Parafoil System ==<br /> <br /> === Storage and Attachment ===<br /> <br /> The parafoil is going to be stored directly behind the nosecone within the forward airframe. The majority of the attachment and support lines are going to be folded in with the parafoil with the four main lines leading out of the nosecone and down the outside of the airframe. These four lines are the two control and two load bearing lines respectively. Each of these four lines is to be inserted through its own slot in the foreward/aft airframes where it is attached to the inside of the rocket near the CG.<br /> <br /> [[File:Pegasus_Parafoil_Storage.png|thumb|frame|center|400px|Bulkhead and backup separation design]]<br /> <br /> === Deployment ===<br /> <br /> Deployment is going to be the result of a pyrodex ejection charge that pushes off the nosecone and a drogue chute. This drogue chute then pulls out the parafoil, allowing it to open in a more controlled manner which should reduce the possibility of lines getting tangled. This should also minimize the possibility of the parafoil becoming wrapped around the airframe due to axial spin.<br /> <br /> === Guidance ===<br /> <br /> We developed a series of in-flight maneuvers used for our initial L1 launch. These can be selected at any time during descent in the Python or Processing ground stations. All allow the selection of a specific period of time and were tested during initial systems experiments.<br /> <br /> * Turn Left: Turning left requires opposite directional movement of the two stepper motors for a period of time. During this time, the steppers are first rotated in opposite directions an equal number of steps. For the remainder of the time, the stepper motors maintain position in the turning state. A short period before the time expires, they are returned to the initial state by rotating back the same number of steps.<br /> * Turn right: This is accomplished in the same manner as above.<br /> * Flare: Flaring requires a fairly similar maneuver. Instead of rotating opposite directions, the two stepper motors are both rotated in the same direction to increase lift and drag. This causes the parafoil to slow down and momentarily reduce the rate of descent.<br /> <br /> === Ground Station ===<br /> <br /> The ARES-2 Ground Station will include two equivalently functional pieces of software for GUI or text based monitoring and control of the rocket. This includes, but is not limited to:<br /> <br /> * A Processing GUI with in-flight instruments, real-time mapping, and graphical renderings of system status (such as velocity, vertical speed, or heading).<br /> * A simple Python text-based monitoring application to continually log data and send basic commands (for example, ’turn right for 15 seconds’) to the rocket.<br /> * Other simple applications to monitor range or other basic parameters.<br /> <br /> [[File:Pegasus_Avionics_Ground_Station.png|800px|center]]<br /> <br /> === Landing ===<br /> <br /> There are two landing procedures possible with this rocket. The first is by flaring the parafoil upon the approach of the ground, similar to how airplanes and skydivers land. This would be performed by using the “flaring” procedure described in the Guidance section. The second is by deploying the backup parachute. This option would be used if the ability to flare the parafoil is deemed ineffective by prior testing. The backup parachute would then be deployed at around 600ft. This height would give the parachute enough time to decrease the speed of the rocket to an acceptable landing speed of 20 ft/s.<br /> <br /> == Backup Recovery System ==<br /> <br /> === Backup Recovery Purpose ===<br /> <br /> The backup Recovery system for the Pegasus rocket is also its payload. This system has a dual purpose: to become the main source of safe recovery upon a possible failure of the parafoil due to twisting, wrapping, and breakage, or as the second, and final, stage of recovery to drop the rocket down to its predesignated landing site. This last purpose may, or may not, become used as it is pending upon how well we are able to flare the ends of the parafoil in order to slow down the rocket and have a controlled touchdown.<br /> <br /> === Backup Recovery System Design ===<br /> <br /> The backup recovery system is to consist of a main parachute and a shockcord attached to a hardpoint within the rocket airframes. The parachute is going to be located inside of the inner tube that provides the resting point for the movable bulkhead.<br /> <br /> Upon the need for the backup recovery system, a pyrodex ejection charge located behind the parachute will be ignited from a command given by the altimeter. This charge will force out the parachute, pushing the movable bulkhead out of the forward airframe with it. Since the shockcord is going to be traveling a large distance within the rocket, the shockcord will have a tennis ball around it to mitigate possible zippering of the rocket.<br /> <br /> [[File:Pegasus_Design_Bulkheads.png|thumb|frame|center|600px|Bulkhead and backup separation design]]<br /> <br /> = Manufacturing and Assembly =<br /> <br /> For all of the testing, kits and other pre-made parts are going to be bought and modified in house. For the final L3, CAD will be sent out to make parts, such as the fiberglass nosecone that we are unable to make in house. The airframe tubes are going to be purchased, however modifications to them, such as cutting and reinforcement, will be done in house. The fins may also be made in house pending time. The parafoil and other recovery parts are going to be purchased through reliable vendors.<br /> <br /> = Systems Integration and Testing =<br /> <br /> == Major Vehicle Launch Dates ==<br /> <br /> ; February 6th:<br /> : Launch test for parafoil deployment at 2,000ft using scale version of L3 rocket<br /> ; February 20th:<br /> : 2nd Major Launch test for avionics system and refining of parafoil deployment<br /> ; March 19th:<br /> : L3 Launch<br /> <br /> = Risk Management =<br /> <br /> == Safety Hazards ==<br /> <br /> For this rocket using a parafoil recovery system creates most of the possible risks of having an unsuccessful flight. Our first risk is the parafoil not deploying properly. This could mean not emerging from the rocket, becoming tangled upon exit of the airframe, and becoming tangled in mid-air while opening. To mitigate the first issue, non-emergence, we are performing pre-launch date small scale tests to practice our system and amount of propellant needed to fully expel the parafoil. The second issue of becoming tangled upon exit we will also be performing small scale tests on prior to the full L3 rocket. This test will be performed again using a static run on the L3 to make sure we scaled it up properly. The final issue of becoming tangled while opening will also be examined through the small scale L1-L2 tests and should be mitigated depending on how the parafoil is folded and fit into the rocket airframe. The parafoil is also going to be contained in a freebag that will be pulled out by the drogue chute. This combination should also help prevent the other issues upon exit. In the event that all of this fails, the payload for the rocket is a parachute that is rigged to an altimeter. Upon too quick of a descent (aka parafoil mal-deployment) the parachute will deploy prematurely to slow the descent of the rocket to a safe speed of 20 m/s.<br /> <br /> The second point of risk is when the rocket is descending while being controlled by the parafoil and the step motors. There is always a possibility of having strong winds above 10,000ft and gusts could cause major control issues for both the stepper motors and for the coded flight plan. Some fail-safes are put into place such as having overly robust stepper motors so that under larger-than-predicted forces the stepper motors will not fail. Another safe-guard are pre-written statements that are associated with the parachute. These safe-guards include too quick of a descent rate (parafoil failure), prolonged ascension after the rocket has reached apogee (in case of thermals or wind gusts forcing the parafoil upwards).<br /> <br /> Further safe-guards are the pre-launch weather requirements. Due to the nature of the recovery system and understanding that parafoils can become rather difficult to control above certain windspeeds, the Pegasus will not plan to launch when the ground windspeed exceeds 15mph. Under these types of conditions it is not unreasonable to assume that the windspeed above 10,000ft could be close to, if not greater than, 40mph; which is too high for the recovery system to be able to be properly controlled in a successful and reliable manner by the step motors.<br /> <br /> == Budget Risks ==<br /> <br /> Our current total budget for Pegasus is $4000. Most of this will be going towards the purchases of our L3 components. Currently, our projected expenditures are below that budget limit. The largest budget “risk” would be testing expenses. It is easier to predict how much the L3 components are going to cost rather than the testing because extra tests might need to be run if we come upon unexpected problems, or are simply desirous of more testing before launching the L3. For this reason, we have allocated $690 as an overhead for testing costs and unforseen, but necessary, purchases. Due to the scale of the rocket and the cost of materials we are using, it is highly unlikely that the team will burn through the entire reserve fund.<br /> <br /> = Activity Plan =<br /> <br /> == Timeline ==<br /> <br /> ; January 23rd:<br /> : Small scale ground ejection tests completed.<br /> ; January 30th:<br /> : Small scale rocket fully assembled<br /> ; February 6th:<br /> : Launch test for parafoil deployment at 2,000ft using scale version of L3 rocket<br /> ; February 13th:<br /> : APRS transmitter, GPS ground station and XBee controller built<br /> ; February 20th:<br /> : 2nd Major Launch test for avionics system and refining of parafoil deployment<br /> ; March 5th:<br /> : Optional extra launch test if necessary to continue refining systems<br /> ; March 12th:<br /> : Finish assembly of L3 rocket<br /> ; March 19th:<br /> : L3 Launch<br /> <br /> == Budget ==<br /> <br /> The overall Budget that the Pegasus team has is $4000. Currently our expenditure for our L3 rocket specifically, as predicted and as already purchased, stands at $3310. An extra $400 is expected to be spent on L1-L2 testing. The current budget break-down is as follows:<br /> <br /> {|<br /> | '''Motor'''<br /> |align=&quot;right&quot;| $710<br /> |-<br /> | '''Structural Components'''<br /> |align=&quot;right&quot;|<br /> <br /> |-<br /> | Airframe<br /> |align=&quot;right&quot;| $200<br /> |-<br /> | Nosecone<br /> |align=&quot;right&quot;| $120<br /> |-<br /> | Fins<br /> |align=&quot;right&quot;| $80<br /> |-<br /> | '''Recovery System'''<br /> |align=&quot;right&quot;|<br /> <br /> |-<br /> | Parafoil<br /> |align=&quot;right&quot;| $1200<br /> |-<br /> | Drogue<br /> |align=&quot;right&quot;| $66<br /> |-<br /> | '''Backup Recovery System'''<br /> |align=&quot;right&quot;|<br /> <br /> |-<br /> | Parachute<br /> |align=&quot;right&quot;| $324<br /> |-<br /> | Recovery Accessories<br /> |align=&quot;right&quot;| $120<br /> |-<br /> | '''Avionics'''<br /> |align=&quot;right&quot;| $490<br /> |-<br /> | '''Reserve + Testing Expenses'''<br /> |align=&quot;right&quot;| $690<br /> |-<br /> |<br /> |}<br /> <br /> <br /> [[Category:Rockets]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=L1_Certification&diff=973 2016-01-26T06:54:53Z

<p>Amilich: </p> <hr /> <div>In order to understand high power rocketry enough to launch and successfully recover an L1 rocket, you must read, live, and understand the following information.<br /> <br /> L1 rocket certification allows individuals to launch rockets with an impulse up to 640 Ns. The requirements include: <br /> <br /> * The airframe must be built by the user with external markings for the centers of gravity and pressure. Rocket kits may be used. <br /> * A standard parachute must be used for recovery, even if a dual-deployment method is used. <br /> * An H or I motor may be used (with impulse &lt; 640 Ns). <br /> * No electronics or altimeter is required. <br /> <br /> Following the launch, the rocket will be inspected; should the airframe be deemed suitable for flight given a new motor, it will have passed L1 certification. Failed deployment, motor cato, drifting beyond a particular range (see launch officer), or the violation of other safety codes will result in a failure. L1 certification, however, is an excellent introduction to the basic operations of rockets and recovery! See [[Pegasus|Pegasus]] for a description of an L1 rocket used as a testbed for an L3 concept.</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=L1_Certification&diff=972 2016-01-26T06:54:37Z

<p>Amilich: </p> <hr /> <div>In order to understand high power rocketry enough to launch and successfully recover an L1 rocket, you must read, live, and understand the following information.<br /> <br /> L1 rocket certification allows individuals to launch rockets with an impulse up to 640 Ns. The requirements include: <br /> <br /> * The airframe must be built by the user with external markings for the centers of gravity and pressure. Rocket kits may be used. <br /> * A standard parachute must be used for recovery, even if a dual-deployment method is used. <br /> * An H or I motor may be used (with impulse &lt; 640 Ns). <br /> * No electronics or altimeter is required. <br /> <br /> Following the launch, the rocket will be inspected; should the airframe be deemed suitable for flight given a new motor, it will have passed L1 certification. Failed deployment, motor cato, drifting beyond a particular range (see launch officer), or the violation of other safety codes will result in a failure. L1 certification, however, is an excellent introduction to the basic operations of rockets and recovery! See [[http://wiki.stanfordssi.org/Pegasus|Pegasus]] for a description of an L1 rocket used as a testbed for an L3 concept. [[Pegasus|Pegasus]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=L1_Certification&diff=971 2016-01-26T06:54:26Z

<p>Amilich: </p> <hr /> <div>In order to understand high power rocketry enough to launch and successfully recover an L1 rocket, you must read, live, and understand the following information.<br /> <br /> L1 rocket certification allows individuals to launch rockets with an impulse up to 640 Ns. The requirements include: <br /> <br /> * The airframe must be built by the user with external markings for the centers of gravity and pressure. Rocket kits may be used. <br /> * A standard parachute must be used for recovery, even if a dual-deployment method is used. <br /> * An H or I motor may be used (with impulse &lt; 640 Ns). <br /> * No electronics or altimeter is required. <br /> <br /> Following the launch, the rocket will be inspected; should the airframe be deemed suitable for flight given a new motor, it will have passed L1 certification. Failed deployment, motor cato, drifting beyond a particular range (see launch officer), or the violation of other safety codes will result in a failure. L1 certification, however, is an excellent introduction to the basic operations of rockets and recovery! See [[http://wiki.stanfordssi.org/Pegasus|Pegasus]] for a description of an L1 rocket used as a testbed for an L3 concept. [[a|b]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=L1_Certification&diff=970 2016-01-26T06:54:03Z

<p>Amilich: </p> <hr /> <div>In order to understand high power rocketry enough to launch and successfully recover an L1 rocket, you must read, live, and understand the following information.<br /> <br /> L1 rocket certification allows individuals to launch rockets with an impulse up to 640 Ns. The requirements include: <br /> <br /> * The airframe must be built by the user with external markings for the centers of gravity and pressure. Rocket kits may be used. <br /> * A standard parachute must be used for recovery, even if a dual-deployment method is used. <br /> * An H or I motor may be used (with impulse &lt; 640 Ns). <br /> * No electronics or altimeter is required. <br /> <br /> Following the launch, the rocket will be inspected; should the airframe be deemed suitable for flight given a new motor, it will have passed L1 certification. Failed deployment, motor cato, drifting beyond a particular range (see launch officer), or the violation of other safety codes will result in a failure. L1 certification, however, is an excellent introduction to the basic operations of rockets and recovery! See [[http://wiki.stanfordssi.org/Pegasus|Pegasus]] for a description of an L1 rocket used as a testbed for an L3 concept.</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=L1_Certification&diff=969 2016-01-26T06:53:50Z

<p>Amilich: </p> <hr /> <div>In order to understand high power rocketry enough to launch and successfully recover an L1 rocket, you must read, live, and understand the following information.<br /> <br /> L1 rocket certification allows individuals to launch rockets with an impulse up to 640 Ns. The requirements include: <br /> <br /> * The airframe must be built by the user with external markings for the centers of gravity and pressure. Rocket kits may be used. <br /> * A standard parachute must be used for recovery, even if a dual-deployment method is used. <br /> * An H or I motor may be used (with impulse &lt; 640 Ns). <br /> * No electronics or altimeter is required. <br /> <br /> Following the launch, the rocket will be inspected; should the airframe be deemed suitable for flight given a new motor, it will have passed L1 certification. Failed deployment, motor cato, drifting beyond a particular range (see launch officer), or the violation of other safety codes will result in a failure. L1 certification, however, is an excellent introduction to the basic operations of rockets and recovery! See [[Pegasus|http://wiki.stanfordssi.org/Pegasus]] for a description of an L1 rocket used as a testbed for an L3 concept. a</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=Pegasus&diff=870 2016-01-23T07:54:16Z

<p>Amilich: </p> <hr /> <div>{{problems}}<br /> <br /> [[File:peg-logo.png|image]]&lt;br /&gt;<br /> = Team Summary =<br /> <br /> Stanford SSI Rockets Team - Pegasus,&lt;br /&gt;<br /> Leland Stanford Junior University&lt;br /&gt;<br /> Stanford, CA&lt;br /&gt;<br /> Ian Gomez&lt;br /&gt;<br /> Project Manager&lt;br /&gt;<br /> iangomez@stanford.edu&lt;br /&gt;<br /> Marie Johnson&lt;br /&gt;<br /> Team lead&lt;br /&gt;<br /> mj6@stanford.edu&lt;br /&gt;<br /> Austin Pineault&lt;br /&gt;<br /> Structural Development and Mechanical Systems Integration&lt;br /&gt;<br /> austin.pineault@stanford.edu&lt;br /&gt;<br /> Andrew Milich&lt;br /&gt;<br /> Avionics, Deployment, and Programming&lt;br /&gt;<br /> amilich@stanford.edu&lt;br /&gt;<br /> John Dean&lt;br /&gt;<br /> Avionics, Deployment, and Programming&lt;br /&gt;<br /> deanjl@stanford.edu&lt;br /&gt;<br /> Hannah Williams&lt;br /&gt;<br /> Structural Development and Parafoil&lt;br /&gt;<br /> hhwilliams@stanford.edu&lt;br /&gt;<br /> Sruti Arulmani&lt;br /&gt;<br /> srutira@stanford.edu&lt;br /&gt;<br /> Nate Simon&lt;br /&gt;<br /> Parafoil and Aerodynamics&lt;br /&gt;<br /> simonnj@stanford.edu&lt;br /&gt;<br /> <br /> <br /> = Launch Vehicle Summary =<br /> <br /> The purpose of the Pegasus rocket is to demonstrate the feasibility of using a parafoil recovery system to create a controlled, directed recovery for a high-powered rocket from over 10,000 ft.<br /> <br /> = Payload Summary =<br /> <br /> The payload of this rocket is the active recovery system and its backup. The payload will be a parafoil deployed at apogee and controlled by two servos throughout descent.<br /> <br /> = Vehicle Criteria =<br /> <br /> == Mission Statement ==<br /> <br /> The Pegasus Rocket team is seeking to develop an efficient and reliable recovery system for high-powered rockets that utilizes a parafoil instead of a parachute.<br /> <br /> == Mission Success Criteria ==<br /> <br /> The mission will be considered successful if the recovered rocket would be able to pass a L3 certification inspection. This means that if the rocket experiences excessive damage to the point that it could not be re-flown that day with a reloaded motor, then the recovery system will have failed. Another criteria is that the rocket will have landed within a 300ft radius of its original target landing space.<br /> <br /> == Constraints ==<br /> <br /> # Tripoli height ceiling of 16,800 ft<br /> # Rocket construction to be made using a “minimum of metallic parts” excepting those necessary for airframe integrity<br /> # Motor impulse to not exceed 10,240 N-s<br /> # Redundant avionics, wiring, and safe arm systems<br /> # Automated program for descent path<br /> # Manual back up control system for descent path<br /> # Back up recovery system consisting of main parachute<br /> # Vertical descent speed of 20 ft/s maximum upon landing<br /> # Budget<br /> <br /> == System Overview ==<br /> <br /> Moments after reaching apogee, a parafoil will deployed from the nosecone of the Firestorm rocket. Structural and control lines of the parafoil will be secured on the exterior of the rocket. Using stepper motors and an XBee, the rocket will be monitored and controlled during descent. This includes real-time data monitoring of position, velocity, vertical speed, and system status as well as options to steer or break the system. Initially, this will be limited to simple guidance motions such as left or right turns, or breaks using both airfoils.<br /> <br /> == Propulsion System ==<br /> <br /> The Cesaroni M1450 was chosen because it is commercially available, reloadable, complies with the Tripoli and California restrictions, keeps our rocket sub Mach-1, and should achieve a maximum height of 16,300 ft with the current mass estimates. Thus even if our mass budget increases, there will still be ample altitude to test the parafoil system.<br /> <br /> The M1450 has an average thrust of 1500 N, a total impulse of 10000 N-s, a specific impulse of 210 s, a burn time of 6.9 s, and a maximum velocity of 300 m/s (Mach 0.9).<br /> <br /> === Motor Performance ===<br /> <br /> [[File:CM1450_Thrust.png|image]]&lt;br /&gt;<br /> <br /> <br /> [[File:CM1450_Altitude.png|image]]&lt;br /&gt;<br /> <br /> <br /> [[File:CM1450_V.png|image]]&lt;br /&gt;<br /> <br /> <br /> [[File:CM1450_Mass.png|image]]<br /> <br /> === Flight Characteristics ===<br /> <br /> [[File:CM1450_Drag_Force.png|image]]&lt;br /&gt;<br /> <br /> <br /> [[File:CM1450_S_Stabil.png|image]]<br /> <br /> == Structural Design ==<br /> <br /> The complete launch vehicle can be broken-down into three primary sections: nose cone, forward airframe, and aft airframe.<br /> <br /> === Nose Cone ===<br /> <br /> A fiberglass nose cone will be used. A custom lay-up of fiberglass will be used to control the exact aerodynamic profile and meet the diameter requirements of the rocket.<br /> <br /> === Forward Airframe ===<br /> <br /> The forward airframe will be 6“ in diameter and 44” in length. It will house, from front to rear, the primary recovery system (parafoil), backup recovery system (parachute payload), and avionics bay.<br /> <br /> [[File:f_airframe.png|image]]&lt;br /&gt;<br /> <br /> <br /> Each of these components will be separated by bulkheads; the foreward bulkhead is designed to protect the backup recovery system from the parafoil’s expulsion and will be mobile (supported on the aft side by blocks along the inner wall of the airframe) to allow backup system to exit the rocket, while the aft bulkhead is designed to protect the avionics and therefore will be stationary.<br /> <br /> === Aft Airframe ===<br /> <br /> The aft airframe will be 6“ in diameter and 48” in length, and will house the motor retainer and fins, as well as have aft attachment points for the coupler.<br /> <br /> === Fins ===<br /> <br /> There are going to be three fins for this rocket. We are going to be using a trapezoidal design with a root length of 12“ and a tip of 6”. They are to have a span of roughly 12“, a leading sweep of 60, and a trailing sweep of 20. This design choice was made to keep the CP within the ”rule of thumb&amp;quot; 1-2 diameter distance between the CP and CG that generates correct stability. However, there is a concern with how the trailing ends of the fins, which extend beyond the aft end of the rocket, will incur damage upon landing.<br /> <br /> This possibility of damage is to be mitigated by the material choice for the fins. Aluminum is currently the best choice, for resistance to deformation upon landing, malleability and ease of machining, as well as being relatively lightweight.<br /> <br /> === Materials ===<br /> <br /> There will be a variety of materials used for the Pegasus rocket. For the airframes we are currently considering to either use polycarbonate due to its structural qualities. However, we are also considering phenolic for the airframes. The nosecone will be made of fiberglass because it is lightweight and strong as well as relatively easy to shape into smooth and specific designs, such as an ogive nosecone. The fins are currently going to be made from aluminum unless a structural equivalent can be found from a non-metal material. Inner support and structures to hold the motors and avionics will be made from a mixture of wood and aluminum bulkheads, as well as some structural support from aluminum struts.<br /> <br /> == Avionics and Telemetry ==<br /> <br /> Telemetry is accomplished using two XBee 9B 900MHZ 250MW long range radio transmitters. Under line of sight conditions, these are expected to achieve a maximum range of 28 miles. We equipped both with 900 MHZ, low impedance, RP-SMA duck antennas.<br /> <br /> === Avionics Teensy Pinout ===<br /> <br /> A Teensy 3.2 microncontroller served as the principal brains of the rocket due to considerable size and performance advantages compared to Arduino based platforms. Through software serial, it communicated directly with the XBee (and thus the ground station) while reading from the GPS and 10DOF sensors as well.<br /> <br /> === In-Flight Tracking ===<br /> <br /> The in-flight tracking will use a XBee Pro module and an Adafruit GPS receiver with a ceramic antena.<br /> <br /> For the in-flight communication and redundant tracking, the rocket will rely on live communication via XBee transmitters and the use of a small SPOT GPS for precise location of the rocket.<br /> <br /> === Power Sources and Budget ===<br /> <br /> Due to high power density and low weight, we chose to use a Lithium Polymer battery. As stepper motors require relatively high amounts of voltage and current, we chose a two cell, 7.4 V LiPo. As the motor’s burn time is relatively short, a battery with low mAh was suitable for these applications. This battery is required to power the Teensy, XBee, stepper motors, and sensors used for guidance.<br /> <br /> == Parafoil System ==<br /> <br /> === Storage and Attachment ===<br /> <br /> The parafoil is going to be stored directly behind the nosecone within the forward airframe. The majority of the attachment and support lines are going to be folded in with the parafoil with the four main lines leading out of the nosecone and down the outside of the airframe. These four lines are the two control and two load bearing lines respectively. Each of these four lines is to be inserted through its own slot in the foreward/aft airframes where it is attached to the inside of the rocket near the CG.<br /> <br /> === Deployment ===<br /> <br /> Deployment is going to be the result of a pyrodex ejection charge that pushes off the nosecone and a drogue chute. This drogue chute then pulls out the parafoil, allowing it to open in a more controlled manner which should reduce the possibility of lines getting tangled. This should also minimize the possibility of the parafoil becoming wrapped around the airframe due to axial spin.<br /> <br /> === Guidance ===<br /> <br /> We developed a series of in-flight maneuvers used for our initial L1 launch. These can be selected at any time during descent in the Python or Processing ground stations. All allow the selection of a specific period of time and were tested during initial systems experiments.<br /> <br /> * Turn Left: Turning left requires opposite directional movement of the two stepper motors for a period of time. During this time, the steppers are first rotated in opposite directions an equal number of steps. For the remainder of the time, the stepper motors maintain position in the turning state. A short period before the time expires, they are returned to the initial state by rotating back the same number of steps.<br /> * Turn right: This is accomplished in the same manner as above.<br /> * Break: Breaking requires a fairly similar maneuver. Instead of rotating opposite directions, however, the two stepper motors are both rotated in the same direction to increase drag.<br /> <br /> === Ground Station ===<br /> <br /> The ARES-2 Ground Station will include two equivalently functional pieces of software for GUI or text based monitoring and control of the rocket. This includes, but is not limited to:<br /> <br /> * A Processing GUI with in-flight instruments, real-time mapping, and graphical renderings of system status (such as velocity, vertical speed, or heading).<br /> * A simple Python text-based monitoring application to continually log data and send basic commands (for example, ’turn right for 15 seconds’) to the rocket.<br /> * Other simple applications to monitor range or other basic parameters.<br /> <br /> [[File:groundstation.png|frame|none|alt=|caption A working demo of the GUI ground station.]]<br /> <br /> === Landing ===<br /> <br /> There are two landing procedures possible with this rocket. The first is by flaring the parafoil upon the approach of the ground, similar to how airplanes and skydivers land. This would be performed by using the “breaking” procedure described in the Guidance section. The second is by deploying the backup parachute. This option would be used if the ability to flare the parafoil is deemed ineffective by prior testing. The backup parachute would then be deployed at around 600ft. This height would give the parachute enough time to decrease the speed of the rocket to an acceptable landing speed of 20 &lt;math&gt;ft/s&lt;/math&gt;.<br /> <br /> == Backup Recovery System ==<br /> <br /> === Backup Recovery Purpose ===<br /> <br /> The backup Recovery system for the Pegasus rocket is also its payload. This system has a dual purpose: to become the main source of safe recovery upon a possible failure of the parafoil due to twisting, wrapping, and breakage, or as the second, and final, stage of recovery to drop the rocket down to its predesignated landing site. This last purpose may, or may not, become used as it is pending upon how well we are able to flare the ends of the parafoil in order to slow down the rocket and have a controlled touchdown.<br /> <br /> === Backup Recovery System Design ===<br /> <br /> The backup recovery system is to consist of a main parachute and a shockcord attached to a hardpoint within the rocket airframes. The parachute is going to be located inside of the inner tube that provides the resting point for the movable bulkhead.<br /> <br /> Upon the need for the backup recovery system, a pyrodex ejection charge located behind the parachute will be ignited from a command given by the altimeter. This charge will force out the parachute, pushing the movable bulkhead out of the forward airframe with it. Since the shockcord is going to be traveling a large distance within the rocket, the shockcord will have a tennis ball around it to mitigate possible zippering of the rocket.<br /> <br /> = Manufacturing and Assembly =<br /> <br /> For all of the testing, kits and other pre-made parts are going to be bought and modified in house. For the final L3, CAD will be sent out to make parts, such as the fiberglass nosecone that we are unable to make in house. The airframe tubes are going to be purchased, however modifications to them, such as cutting and reinforcement, will be done in house. The fins may also be made in house pending time. The parafoil and other recovery parts are going to be purchased through reliable vendors.<br /> <br /> = Systems Integration and Testing =<br /> <br /> == Major Vehicle Launch Dates ==<br /> <br /> ; February 6th:<br /> : Launch test for parafoil deployment at 2,000ft using scale version of L3 rocket<br /> ; February 20th:<br /> : 2nd Major Launch test for avionics system and refining of parafoil deployment<br /> ; March 19th:<br /> : L3 Launch<br /> <br /> = Risk Management =<br /> <br /> == Safety Hazards ==<br /> <br /> For this rocket using a parafoil recovery system creates most of the possible risks of having an unsuccessful flight. Our first risk is the parafoil not deploying properly. This could mean not emerging from the rocket, becoming tangled upon exit of the airframe, and becoming tangled in mid-air while opening. To mitigate the first issue, non-emergence, we are performing pre-launch date small scale tests to practice our system and amount of propellant needed to fully expel the parafoil. The second issue of becoming tangled upon exit we will also be performing small scale tests on prior to the full L3 rocket. This test will be performed again using a static run on the L3 to make sure we scaled it up properly. The final issue of becoming tangled while opening will also be examined through the small scale L1-L2 tests and should be mitigated depending on how the parafoil is folded and fit into the rocket airframe. The parafoil is also going to be contained in a freebag that will be pulled out by the drogue chute. This combination should also help prevent the other issues upon exit. In the event that all of this fails, the payload for the rocket is a parachute that is rigged to an altimeter. Upon too quick of a descent (aka parafoil mal-deployment) the parachute will deploy prematurely to slow the descent of the rocket to a safe speed of 20 &lt;math&gt;m/s&lt;/math&gt;.<br /> <br /> The second point of risk is when the rocket is descending while being controlled by the parafoil and the step motors. There is always a possibility of having strong winds above 10,000ft and gusts could cause major control issues for both the stepper motors and for the coded flight plan. Some fail-safes are put into place such as having overly robust stepper motors so that under larger-than-predicted forces the stepper motors will not fail. Another safe-guard are pre-written statements that are associated with the parachute. These safe-guards include too quick of a descent rate (parafoil failure), prolonged ascension after the rocket has reached apogee (in case of thermals or wind gusts forcing the parafoil upwards).<br /> <br /> Further safe-guards are the pre-launch weather requirements. Due to the nature of the recovery system and understanding that parafoils can become rather difficult to control above certain windspeeds, the Pegasus will not plan to launch when the ground windspeed exceeds 15mph. Under these types of conditions it is not unreasonable to assume that the windspeed above 10,000ft could be close to, if not greater than, 40mph; which is too high for the recovery system to be able to be properly controlled in a successful and reliable manner by the step motors.<br /> <br /> == Budget Risks ==<br /> <br /> Our current total budget for Pegasus is $4000. Most of this will be going towards the purchases of our L3 components. Currently, our projected expenditures are below that budget limit. The largest budget “risk” would be testing expenses. It is easier to predict how much the L3 components are going to cost rather than the testing because extra tests might need to be run if we come upon unexpected problems, or are simply desirous of more testing before launching the L3. For this reason, we have allocated $690 as an overhead for testing costs and unforseen, but necessary, purchases. Due to the scale of the rocket and the cost of materials we are using, it is highly unlikely that the team will burn through the entire reserve fund.<br /> <br /> = Activity Plan =<br /> <br /> == Timeline ==<br /> <br /> ; January 23rd:<br /> : Small scale ground ejection tests completed.<br /> ; January 30th:<br /> : Small scale rocket fully assembled<br /> ; February 6th:<br /> : Launch test for parafoil deployment at 2,000ft using scale version of L3 rocket<br /> ; February 13th:<br /> : APRS transmitter, GPS ground station and XBee controller built<br /> ; February 20th:<br /> : 2nd Major Launch test for avionics system and refining of parafoil deployment<br /> ; March 5th:<br /> : Optional extra launch test if necessary to continue refining systems<br /> ; March 12th:<br /> : Finish assembly of L3 rocket<br /> ; March 19th:<br /> : L3 Launch<br /> <br /> == Budget ==<br /> <br /> The overall Budget that the Pegasus team has is $4000. Currently our expenditure for our L3 rocket specifically, as predicted and as already purchased, stands at $3310. An extra $400 is expected to be spent on L1-L2 testing. The current budget break-down is as follows:<br /> <br /> {|<br /> | '''Motor'''<br /> |align=&quot;right&quot;| $710<br /> |-<br /> | '''Structural Components'''<br /> |align=&quot;right&quot;|<br /> <br /> |-<br /> | Airframe<br /> |align=&quot;right&quot;| $200<br /> |-<br /> | Nosecone<br /> |align=&quot;right&quot;| $120<br /> |-<br /> | Fins<br /> |align=&quot;right&quot;| $80<br /> |-<br /> | '''Recovery System'''<br /> |align=&quot;right&quot;|<br /> <br /> |-<br /> | Parafoil<br /> |align=&quot;right&quot;| $1200<br /> |-<br /> | Drogue<br /> |align=&quot;right&quot;| $66<br /> |-<br /> | '''Backup Recovery System'''<br /> |align=&quot;right&quot;|<br /> <br /> |-<br /> | Parachute<br /> |align=&quot;right&quot;| $324<br /> |-<br /> | Recovery Accessories<br /> |align=&quot;right&quot;| $120<br /> |-<br /> | '''Avionics'''<br /> |align=&quot;right&quot;| $490<br /> |-<br /> | '''Reserve + Testing Expenses'''<br /> |align=&quot;right&quot;| $690<br /> |-<br /> |<br /> <br /> |align=&quot;right&quot;| $4000<br /> |}<br /> <br /> <br /> [[Category:Rockets]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=File:Peg-logo.png&diff=869 2016-01-23T07:53:11Z

<p>Amilich: </p> <hr /> <div></div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-Guy&diff=471 2015-10-27T19:11:03Z

<p>Amilich: </p> <hr /> <div>{{balloon-launch<br /> | header = SSI Guy<br /> | img link = File:ssi24v2.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> }}<br /> <br /> The SSI-Guy was launched on SSI-24. <br /> <br /> [[Category: Satire]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-Guy&diff=470 2015-10-27T19:10:51Z

<p>Amilich: Created page with &quot;{{balloon-launch | header = SSI-24 (Orion) | img link = File:ssi24v2.png | launch date = October 24th, 2015, 11:39AM PDT | launch site = 2093 San Juan Drive, Hollister, CA }}...&quot;</p> <hr /> <div>{{balloon-launch<br /> | header = SSI-24 (Orion)<br /> | img link = File:ssi24v2.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> }}<br /> <br /> The SSI-Guy was launched on SSI-24. <br /> <br /> [[Category: Satire]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-24&diff=469 2015-10-27T19:09:49Z

<p>Amilich: </p> <hr /> <div>{{balloon-launch<br /> | header = SSI-24 (Orion)<br /> | img link = File:ssi24v2.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> | launch coordinates = 36.84842,-121.43236<br /> | flight duration = 3 hours, 44 minutes, 11.1 seconds<br /> | landing date = October 24th, 2015, 3:23:11 PM PDT<br /> | last = 23<br /> | next = 25<br /> }}<br /> <br /> SSI-24 Orion was one of three balloons launched during fall quarter, 2015. It consisted of an almost all-freshman team dedicated to creating a scientifically power yet aesthetically beautiful payload. Ultimately, Orion represented a resounding success in its use of sensors, logging of data, power management, use of solar energy to charge its batteries, demonstration of wifi transmissions, and creation of a visually refined payload. The total ground track was 121.21 miles, and the top speed reached was 92.44 miles per hour. <br /> <br /> SSI-24 also launched the infamous [[SSI-Guy | SSGuy]] or [[SSI-Guy]]. <br /> <br /> == Pre-Launch == <br /> <br /> The Pre-Launch proceeded fairly well with few hiccups. After fixing minor problems with the solar panel wiring, the team prepared the gimbal and finished visual preparation of the payload. Unfortunately, the team experienced extreme difficulties setting up the keychain camera (which did not function during flight). The payload, which consisted of two styrofoam boxes and a selfie stick, was attached to a single 1500g balloon. <br /> <br /> == Flight == <br /> <br /> [[File:SSI24 map.png | thumb | &lt;center&gt;SSI 24 ground track. The GPS was likely deactivated above 60,000 feet due to poor firmware implementation.&lt;/center&gt;]]<br /> <br /> SSI-24 used the SPOT Nebula for tracking and recovery. See http://habmc.stanfordssi.org/#/app/spot_four. A Phantom 2 UAV was used by members of Orion to video the launch of SSI-23a, 23, 24, and 25. <br /> <br /> <br /> [[File:Drone.jpg | thumb | &lt;center&gt; Phantom 2 &lt;/center&gt;]]<br /> <br /> == Experimental Payload == <br /> <br /> [[File:SSI24-perspective.jpg | thumb | &lt;center&gt; Perspective view of the Orion sensor payload. &lt;/center&gt;]]<br /> <br /> SSI-24 included both a Raspberry Pi 2B and two Arduino Uno boards. The Raspberry Pi was initially intended to be used to stream live video from the balloon, however, due to issues with the camera board, it was simply used as a wifi access point. The two Arduino boards regulated the sensors onboard the balloon, including a temperature sensor, two heating pads, an SD reader, a GPS, a solar panel, and an accelerometer. Though the group initially intended to use a PIXY camera as well, the PIXY's requirement to be updated with signatures made it difficult to use aboard the balloon. <br /> <br /> The second board served a single purpose: dropping three Hershey's chocolate bars at a specified altitude. This was accomplished using the GPS altitude from the first Arduino, which would set a single digital pin to high. This would trigger the second Arduino to swing a servo and release the bars. <br /> <br /> [[File:OrionWifi.jpg | thumb | &lt;center&gt; Wifi Antenna &lt;/center&gt;]]<br /> <br /> == Landing Drama == <br /> <br /> Upon landing, SSI-24 was discovered by two passers-by. They kindly brought it to their home and phoned the balloons team, who recovered it soon after. <br /> <br /> == Milestones == <br /> <br /> * First use of wifi antennas and Raspberry Pi on an SSI high altitude balloon<br /> * Successful implementation of a gimbal for the SPOT GPS<br /> <br /> {{balloon-footer}}<br /> [[Category: High Altitude Balloons]][[Category: Balloon Launches]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-24&diff=468 2015-10-27T19:09:35Z

<p>Amilich: </p> <hr /> <div>{{balloon-launch<br /> | header = SSI-24 (Orion)<br /> | img link = File:ssi24v2.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> | launch coordinates = 36.84842,-121.43236<br /> | flight duration = 3 hours, 44 minutes, 11.1 seconds<br /> | landing date = October 24th, 2015, 3:23:11 PM PDT<br /> | last = 23<br /> | next = 25<br /> }}<br /> <br /> SSI-24 Orion was one of three balloons launched during fall quarter, 2015. It consisted of an almost all-freshman team dedicated to creating a scientifically power yet aesthetically beautiful payload. Ultimately, Orion represented a resounding success in its use of sensors, logging of data, power management, use of solar energy to charge its batteries, demonstration of wifi transmissions, and creation of a visually refined payload. The total ground track was 121.21 miles, and the top speed reached was 92.44 miles per hour. <br /> <br /> SSI-24 also launched the infamous [[SSGuy | SSI-Guy]] or [[SSI-Guy]]. <br /> <br /> == Pre-Launch == <br /> <br /> The Pre-Launch proceeded fairly well with few hiccups. After fixing minor problems with the solar panel wiring, the team prepared the gimbal and finished visual preparation of the payload. Unfortunately, the team experienced extreme difficulties setting up the keychain camera (which did not function during flight). The payload, which consisted of two styrofoam boxes and a selfie stick, was attached to a single 1500g balloon. <br /> <br /> == Flight == <br /> <br /> [[File:SSI24 map.png | thumb | &lt;center&gt;SSI 24 ground track. The GPS was likely deactivated above 60,000 feet due to poor firmware implementation.&lt;/center&gt;]]<br /> <br /> SSI-24 used the SPOT Nebula for tracking and recovery. See http://habmc.stanfordssi.org/#/app/spot_four. A Phantom 2 UAV was used by members of Orion to video the launch of SSI-23a, 23, 24, and 25. <br /> <br /> <br /> [[File:Drone.jpg | thumb | &lt;center&gt; Phantom 2 &lt;/center&gt;]]<br /> <br /> == Experimental Payload == <br /> <br /> [[File:SSI24-perspective.jpg | thumb | &lt;center&gt; Perspective view of the Orion sensor payload. &lt;/center&gt;]]<br /> <br /> SSI-24 included both a Raspberry Pi 2B and two Arduino Uno boards. The Raspberry Pi was initially intended to be used to stream live video from the balloon, however, due to issues with the camera board, it was simply used as a wifi access point. The two Arduino boards regulated the sensors onboard the balloon, including a temperature sensor, two heating pads, an SD reader, a GPS, a solar panel, and an accelerometer. Though the group initially intended to use a PIXY camera as well, the PIXY's requirement to be updated with signatures made it difficult to use aboard the balloon. <br /> <br /> The second board served a single purpose: dropping three Hershey's chocolate bars at a specified altitude. This was accomplished using the GPS altitude from the first Arduino, which would set a single digital pin to high. This would trigger the second Arduino to swing a servo and release the bars. <br /> <br /> [[File:OrionWifi.jpg | thumb | &lt;center&gt; Wifi Antenna &lt;/center&gt;]]<br /> <br /> == Landing Drama == <br /> <br /> Upon landing, SSI-24 was discovered by two passers-by. They kindly brought it to their home and phoned the balloons team, who recovered it soon after. <br /> <br /> == Milestones == <br /> <br /> * First use of wifi antennas and Raspberry Pi on an SSI high altitude balloon<br /> * Successful implementation of a gimbal for the SPOT GPS<br /> <br /> {{balloon-footer}}<br /> [[Category: High Altitude Balloons]][[Category: Balloon Launches]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-24&diff=467 2015-10-27T19:09:18Z

<p>Amilich: </p> <hr /> <div>{{balloon-launch<br /> | header = SSI-24 (Orion)<br /> | img link = File:ssi24v2.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> | launch coordinates = 36.84842,-121.43236<br /> | flight duration = 3 hours, 44 minutes, 11.1 seconds<br /> | landing date = October 24th, 2015, 3:23:11 PM PDT<br /> | last = 23<br /> | next = 25<br /> }}<br /> <br /> SSI-24 Orion was one of three balloons launched during fall quarter, 2015. It consisted of an almost all-freshman team dedicated to creating a scientifically power yet aesthetically beautiful payload. Ultimately, Orion represented a resounding success in its use of sensors, logging of data, power management, use of solar energy to charge its batteries, demonstration of wifi transmissions, and creation of a visually refined payload. The total ground track was 121.21 miles, and the top speed reached was 92.44 miles per hour. <br /> <br /> SSI-24 also launched the infamous [[SSGuy || SSI-Guy]] or [[SSI-Guy]]. <br /> <br /> == Pre-Launch == <br /> <br /> The Pre-Launch proceeded fairly well with few hiccups. After fixing minor problems with the solar panel wiring, the team prepared the gimbal and finished visual preparation of the payload. Unfortunately, the team experienced extreme difficulties setting up the keychain camera (which did not function during flight). The payload, which consisted of two styrofoam boxes and a selfie stick, was attached to a single 1500g balloon. <br /> <br /> == Flight == <br /> <br /> [[File:SSI24 map.png | thumb | &lt;center&gt;SSI 24 ground track. The GPS was likely deactivated above 60,000 feet due to poor firmware implementation.&lt;/center&gt;]]<br /> <br /> SSI-24 used the SPOT Nebula for tracking and recovery. See http://habmc.stanfordssi.org/#/app/spot_four. A Phantom 2 UAV was used by members of Orion to video the launch of SSI-23a, 23, 24, and 25. <br /> <br /> <br /> [[File:Drone.jpg | thumb | &lt;center&gt; Phantom 2 &lt;/center&gt;]]<br /> <br /> == Experimental Payload == <br /> <br /> [[File:SSI24-perspective.jpg | thumb | &lt;center&gt; Perspective view of the Orion sensor payload. &lt;/center&gt;]]<br /> <br /> SSI-24 included both a Raspberry Pi 2B and two Arduino Uno boards. The Raspberry Pi was initially intended to be used to stream live video from the balloon, however, due to issues with the camera board, it was simply used as a wifi access point. The two Arduino boards regulated the sensors onboard the balloon, including a temperature sensor, two heating pads, an SD reader, a GPS, a solar panel, and an accelerometer. Though the group initially intended to use a PIXY camera as well, the PIXY's requirement to be updated with signatures made it difficult to use aboard the balloon. <br /> <br /> The second board served a single purpose: dropping three Hershey's chocolate bars at a specified altitude. This was accomplished using the GPS altitude from the first Arduino, which would set a single digital pin to high. This would trigger the second Arduino to swing a servo and release the bars. <br /> <br /> [[File:OrionWifi.jpg | thumb | &lt;center&gt; Wifi Antenna &lt;/center&gt;]]<br /> <br /> == Landing Drama == <br /> <br /> Upon landing, SSI-24 was discovered by two passers-by. They kindly brought it to their home and phoned the balloons team, who recovered it soon after. <br /> <br /> == Milestones == <br /> <br /> * First use of wifi antennas and Raspberry Pi on an SSI high altitude balloon<br /> * Successful implementation of a gimbal for the SPOT GPS<br /> <br /> {{balloon-footer}}<br /> [[Category: High Altitude Balloons]][[Category: Balloon Launches]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-24&diff=466 2015-10-27T19:09:09Z

<p>Amilich: </p> <hr /> <div>{{balloon-launch<br /> | header = SSI-24 (Orion)<br /> | img link = File:ssi24v2.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> | launch coordinates = 36.84842,-121.43236<br /> | flight duration = 3 hours, 44 minutes, 11.1 seconds<br /> | landing date = October 24th, 2015, 3:23:11 PM PDT<br /> | last = 23<br /> | next = 25<br /> }}<br /> <br /> SSI-24 Orion was one of three balloons launched during fall quarter, 2015. It consisted of an almost all-freshman team dedicated to creating a scientifically power yet aesthetically beautiful payload. Ultimately, Orion represented a resounding success in its use of sensors, logging of data, power management, use of solar energy to charge its batteries, demonstration of wifi transmissions, and creation of a visually refined payload. The total ground track was 121.21 miles, and the top speed reached was 92.44 miles per hour. <br /> <br /> SSI-24 also launched the infamous [[SSGuy || SSI-Guy]] or [[SSI-Guy]. <br /> <br /> == Pre-Launch == <br /> <br /> The Pre-Launch proceeded fairly well with few hiccups. After fixing minor problems with the solar panel wiring, the team prepared the gimbal and finished visual preparation of the payload. Unfortunately, the team experienced extreme difficulties setting up the keychain camera (which did not function during flight). The payload, which consisted of two styrofoam boxes and a selfie stick, was attached to a single 1500g balloon. <br /> <br /> == Flight == <br /> <br /> [[File:SSI24 map.png | thumb | &lt;center&gt;SSI 24 ground track. The GPS was likely deactivated above 60,000 feet due to poor firmware implementation.&lt;/center&gt;]]<br /> <br /> SSI-24 used the SPOT Nebula for tracking and recovery. See http://habmc.stanfordssi.org/#/app/spot_four. A Phantom 2 UAV was used by members of Orion to video the launch of SSI-23a, 23, 24, and 25. <br /> <br /> <br /> [[File:Drone.jpg | thumb | &lt;center&gt; Phantom 2 &lt;/center&gt;]]<br /> <br /> == Experimental Payload == <br /> <br /> [[File:SSI24-perspective.jpg | thumb | &lt;center&gt; Perspective view of the Orion sensor payload. &lt;/center&gt;]]<br /> <br /> SSI-24 included both a Raspberry Pi 2B and two Arduino Uno boards. The Raspberry Pi was initially intended to be used to stream live video from the balloon, however, due to issues with the camera board, it was simply used as a wifi access point. The two Arduino boards regulated the sensors onboard the balloon, including a temperature sensor, two heating pads, an SD reader, a GPS, a solar panel, and an accelerometer. Though the group initially intended to use a PIXY camera as well, the PIXY's requirement to be updated with signatures made it difficult to use aboard the balloon. <br /> <br /> The second board served a single purpose: dropping three Hershey's chocolate bars at a specified altitude. This was accomplished using the GPS altitude from the first Arduino, which would set a single digital pin to high. This would trigger the second Arduino to swing a servo and release the bars. <br /> <br /> [[File:OrionWifi.jpg | thumb | &lt;center&gt; Wifi Antenna &lt;/center&gt;]]<br /> <br /> == Landing Drama == <br /> <br /> Upon landing, SSI-24 was discovered by two passers-by. They kindly brought it to their home and phoned the balloons team, who recovered it soon after. <br /> <br /> == Milestones == <br /> <br /> * First use of wifi antennas and Raspberry Pi on an SSI high altitude balloon<br /> * Successful implementation of a gimbal for the SPOT GPS<br /> <br /> {{balloon-footer}}<br /> [[Category: High Altitude Balloons]][[Category: Balloon Launches]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-24&diff=465 2015-10-27T19:08:38Z

<p>Amilich: </p> <hr /> <div>{{balloon-launch<br /> | header = SSI-24 (Orion)<br /> | img link = File:ssi24v2.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> | launch coordinates = 36.84842,-121.43236<br /> | flight duration = 3 hours, 44 minutes, 11.1 seconds<br /> | landing date = October 24th, 2015, 3:23:11 PM PDT<br /> | last = 23<br /> | next = 25<br /> }}<br /> <br /> SSI-24 Orion was one of three balloons launched during fall quarter, 2015. It consisted of an almost all-freshman team dedicated to creating a scientifically power yet aesthetically beautiful payload. Ultimately, Orion represented a resounding success in its use of sensors, logging of data, power management, use of solar energy to charge its batteries, demonstration of wifi transmissions, and creation of a visually refined payload. The total ground track was 121.21 miles, and the top speed reached was 92.44 miles per hour. <br /> <br /> SSI-24 also launched the infamous [[SSGuy]] or 'SSI-Guy'. <br /> <br /> == Pre-Launch == <br /> <br /> The Pre-Launch proceeded fairly well with few hiccups. After fixing minor problems with the solar panel wiring, the team prepared the gimbal and finished visual preparation of the payload. Unfortunately, the team experienced extreme difficulties setting up the keychain camera (which did not function during flight). The payload, which consisted of two styrofoam boxes and a selfie stick, was attached to a single 1500g balloon. <br /> <br /> == Flight == <br /> <br /> [[File:SSI24 map.png | thumb | &lt;center&gt;SSI 24 ground track. The GPS was likely deactivated above 60,000 feet due to poor firmware implementation.&lt;/center&gt;]]<br /> <br /> SSI-24 used the SPOT Nebula for tracking and recovery. See http://habmc.stanfordssi.org/#/app/spot_four. A Phantom 2 UAV was used by members of Orion to video the launch of SSI-23a, 23, 24, and 25. <br /> <br /> <br /> [[File:Drone.jpg | thumb | &lt;center&gt; Phantom 2 &lt;/center&gt;]]<br /> <br /> == Experimental Payload == <br /> <br /> [[File:SSI24-perspective.jpg | thumb | &lt;center&gt; Perspective view of the Orion sensor payload. &lt;/center&gt;]]<br /> <br /> SSI-24 included both a Raspberry Pi 2B and two Arduino Uno boards. The Raspberry Pi was initially intended to be used to stream live video from the balloon, however, due to issues with the camera board, it was simply used as a wifi access point. The two Arduino boards regulated the sensors onboard the balloon, including a temperature sensor, two heating pads, an SD reader, a GPS, a solar panel, and an accelerometer. Though the group initially intended to use a PIXY camera as well, the PIXY's requirement to be updated with signatures made it difficult to use aboard the balloon. <br /> <br /> The second board served a single purpose: dropping three Hershey's chocolate bars at a specified altitude. This was accomplished using the GPS altitude from the first Arduino, which would set a single digital pin to high. This would trigger the second Arduino to swing a servo and release the bars. <br /> <br /> [[File:OrionWifi.jpg | thumb | &lt;center&gt; Wifi Antenna &lt;/center&gt;]]<br /> <br /> == Landing Drama == <br /> <br /> Upon landing, SSI-24 was discovered by two passers-by. They kindly brought it to their home and phoned the balloons team, who recovered it soon after. <br /> <br /> == Milestones == <br /> <br /> * First use of wifi antennas and Raspberry Pi on an SSI high altitude balloon<br /> * Successful implementation of a gimbal for the SPOT GPS<br /> <br /> {{balloon-footer}}<br /> [[Category: High Altitude Balloons]][[Category: Balloon Launches]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=User:Amilich&diff=464 2015-10-27T19:07:11Z

<p>Amilich: Created page with &quot;Hi! I am Andrew.&quot;</p> <hr /> <div>Hi! I am Andrew.</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-24&diff=463 2015-10-27T19:04:45Z

<p>Amilich: </p> <hr /> <div>{{balloon-launch<br /> | header = SSI-24 (Orion)<br /> | img link = File:ssi24v2.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> | launch coordinates = 36.84842,-121.43236<br /> | flight duration = 3 hours, 44 minutes, 11.1 seconds<br /> | landing date = October 24th, 2015, 3:23:11 PM PDT<br /> | last = 23<br /> | next = 25<br /> }}<br /> <br /> SSI-24 Orion was one of three balloons launched during fall quarter, 2015. It consisted of an almost all-freshman team dedicated to creating a scientifically power yet aesthetically beautiful payload. Ultimately, Orion represented a resounding success in its use of sensors, logging of data, power management, use of solar energy to charge its batteries, demonstration of wifi transmissions, and creation of a visually refined payload. The total ground track was 121.21 miles, and the top speed reached was 92.44 miles per hour. <br /> <br /> == Pre-Launch == <br /> <br /> The Pre-Launch proceeded fairly well with few hiccups. After fixing minor problems with the solar panel wiring, the team prepared the gimbal and finished visual preparation of the payload. Unfortunately, the team experienced extreme difficulties setting up the keychain camera (which did not function during flight). The payload, which consisted of two styrofoam boxes and a selfie stick, was attached to a single 1500g balloon. <br /> <br /> == Flight == <br /> <br /> [[File:SSI24 map.png | thumb | &lt;center&gt;SSI 24 ground track. The GPS was likely deactivated above 60,000 feet due to poor firmware implementation.&lt;/center&gt;]]<br /> <br /> SSI-24 used the SPOT Nebula for tracking and recovery. See http://habmc.stanfordssi.org/#/app/spot_four. A Phantom 2 UAV was used by members of Orion to video the launch of SSI-23a, 23, 24, and 25. <br /> <br /> <br /> [[File:Drone.jpg | thumb | &lt;center&gt; Phantom 2 &lt;/center&gt;]]<br /> <br /> == Experimental Payload == <br /> <br /> [[File:SSI24-perspective.jpg | thumb | &lt;center&gt; Perspective view of the Orion sensor payload. &lt;/center&gt;]]<br /> <br /> SSI-24 included both a Raspberry Pi 2B and two Arduino Uno boards. The Raspberry Pi was initially intended to be used to stream live video from the balloon, however, due to issues with the camera board, it was simply used as a wifi access point. The two Arduino boards regulated the sensors onboard the balloon, including a temperature sensor, two heating pads, an SD reader, a GPS, a solar panel, and an accelerometer. Though the group initially intended to use a PIXY camera as well, the PIXY's requirement to be updated with signatures made it difficult to use aboard the balloon. <br /> <br /> The second board served a single purpose: dropping three Hershey's chocolate bars at a specified altitude. This was accomplished using the GPS altitude from the first Arduino, which would set a single digital pin to high. This would trigger the second Arduino to swing a servo and release the bars. <br /> <br /> [[File:OrionWifi.jpg | thumb | &lt;center&gt; Wifi Antenna &lt;/center&gt;]]<br /> <br /> == Landing Drama == <br /> <br /> Upon landing, SSI-24 was discovered by two passers-by. They kindly brought it to their home and phoned the balloons team, who recovered it soon after. <br /> <br /> == Milestones == <br /> <br /> * First use of wifi antennas and Raspberry Pi on an SSI high altitude balloon<br /> * Successful implementation of a gimbal for the SPOT GPS<br /> <br /> {{balloon-footer}}<br /> [[Category: High Altitude Balloons]][[Category: Balloon Launches]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=File:Ssi24v2.png&diff=462 2015-10-27T19:04:23Z

<p>Amilich: </p> <hr /> <div></div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-24&diff=461 2015-10-27T19:01:55Z

<p>Amilich: </p> <hr /> <div>{{balloon-launch<br /> | header = SSI-24 (Orion)<br /> | img link = File:ssi_24.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> | launch coordinates = 36.84842,-121.43236<br /> | flight duration = 3 hours, 44 minutes, 11.1 seconds<br /> | landing date = October 24th, 2015, 3:23:11 PM PDT<br /> | last = 23<br /> | next = 25<br /> }}<br /> <br /> SSI-24 Orion was one of three balloons launched during fall quarter, 2015. It consisted of an almost all-freshman team dedicated to creating a scientifically power yet aesthetically beautiful payload. Ultimately, Orion represented a resounding success in its use of sensors, logging of data, power management, use of solar energy to charge its batteries, demonstration of wifi transmissions, and creation of a visually refined payload. The total ground track was 121.21 miles, and the top speed reached was 92.44 miles per hour. <br /> <br /> == Pre-Launch == <br /> <br /> The Pre-Launch proceeded fairly well with few hiccups. After fixing minor problems with the solar panel wiring, the team prepared the gimbal and finished visual preparation of the payload. Unfortunately, the team experienced extreme difficulties setting up the keychain camera (which did not function during flight). The payload, which consisted of two styrofoam boxes and a selfie stick, was attached to a single 1500g balloon. <br /> <br /> == Flight == <br /> <br /> [[File:SSI24 map.png | thumb | &lt;center&gt;SSI 24 ground track. The GPS was likely deactivated above 60,000 feet due to poor firmware implementation.&lt;/center&gt;]]<br /> <br /> SSI-24 used the SPOT Nebula for tracking and recovery. See http://habmc.stanfordssi.org/#/app/spot_four. A Phantom 2 UAV was used by members of Orion to video the launch of SSI-23a, 23, 24, and 25. <br /> <br /> <br /> [[File:Drone.jpg | thumb | &lt;center&gt; Phantom 2 &lt;/center&gt;]]<br /> <br /> == Experimental Payload == <br /> <br /> [[File:SSI24-perspective.jpg | thumb | &lt;center&gt; Perspective view of the Orion sensor payload. &lt;/center&gt;]]<br /> <br /> SSI-24 included both a Raspberry Pi 2B and two Arduino Uno boards. The Raspberry Pi was initially intended to be used to stream live video from the balloon, however, due to issues with the camera board, it was simply used as a wifi access point. The two Arduino boards regulated the sensors onboard the balloon, including a temperature sensor, two heating pads, an SD reader, a GPS, a solar panel, and an accelerometer. Though the group initially intended to use a PIXY camera as well, the PIXY's requirement to be updated with signatures made it difficult to use aboard the balloon. <br /> <br /> The second board served a single purpose: dropping three Hershey's chocolate bars at a specified altitude. This was accomplished using the GPS altitude from the first Arduino, which would set a single digital pin to high. This would trigger the second Arduino to swing a servo and release the bars. <br /> <br /> [[File:OrionWifi.jpg | thumb | &lt;center&gt; Wifi Antenna &lt;/center&gt;]]<br /> <br /> == Landing Drama == <br /> <br /> Upon landing, SSI-24 was discovered by two passers-by. They kindly brought it to their home and phoned the balloons team, who recovered it soon after. <br /> <br /> == Milestones == <br /> <br /> * First use of wifi antennas and Raspberry Pi on an SSI high altitude balloon<br /> * Successful implementation of a gimbal for the SPOT GPS<br /> <br /> {{balloon-footer}}<br /> [[Category: High Altitude Balloons]][[Category: Balloon Launches]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-24&diff=460 2015-10-27T19:01:42Z

<p>Amilich: </p> <hr /> <div>{{balloon-launch<br /> | header = SSI-24 (Orion)<br /> | img link = File:ssi_24.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> | launch coordinates = 36.84842,-121.43236<br /> | flight duration = 3 hours, 44 minutes, 11.1 seconds<br /> | landing date = October 24th, 2015, 3:23:11PM PDT<br /> | last = 23<br /> | next = 25<br /> }}<br /> <br /> SSI-24 Orion was one of three balloons launched during fall quarter, 2015. It consisted of an almost all-freshman team dedicated to creating a scientifically power yet aesthetically beautiful payload. Ultimately, Orion represented a resounding success in its use of sensors, logging of data, power management, use of solar energy to charge its batteries, demonstration of wifi transmissions, and creation of a visually refined payload. The total ground track was 121.21 miles, and the top speed reached was 92.44 miles per hour. <br /> <br /> == Pre-Launch == <br /> <br /> The Pre-Launch proceeded fairly well with few hiccups. After fixing minor problems with the solar panel wiring, the team prepared the gimbal and finished visual preparation of the payload. Unfortunately, the team experienced extreme difficulties setting up the keychain camera (which did not function during flight). The payload, which consisted of two styrofoam boxes and a selfie stick, was attached to a single 1500g balloon. <br /> <br /> == Flight == <br /> <br /> [[File:SSI24 map.png | thumb | &lt;center&gt;SSI 24 ground track. The GPS was likely deactivated above 60,000 feet due to poor firmware implementation.&lt;/center&gt;]]<br /> <br /> SSI-24 used the SPOT Nebula for tracking and recovery. See http://habmc.stanfordssi.org/#/app/spot_four. A Phantom 2 UAV was used by members of Orion to video the launch of SSI-23a, 23, 24, and 25. <br /> <br /> <br /> [[File:Drone.jpg | thumb | &lt;center&gt; Phantom 2 &lt;/center&gt;]]<br /> <br /> == Experimental Payload == <br /> <br /> [[File:SSI24-perspective.jpg | thumb | &lt;center&gt; Perspective view of the Orion sensor payload. &lt;/center&gt;]]<br /> <br /> SSI-24 included both a Raspberry Pi 2B and two Arduino Uno boards. The Raspberry Pi was initially intended to be used to stream live video from the balloon, however, due to issues with the camera board, it was simply used as a wifi access point. The two Arduino boards regulated the sensors onboard the balloon, including a temperature sensor, two heating pads, an SD reader, a GPS, a solar panel, and an accelerometer. Though the group initially intended to use a PIXY camera as well, the PIXY's requirement to be updated with signatures made it difficult to use aboard the balloon. <br /> <br /> The second board served a single purpose: dropping three Hershey's chocolate bars at a specified altitude. This was accomplished using the GPS altitude from the first Arduino, which would set a single digital pin to high. This would trigger the second Arduino to swing a servo and release the bars. <br /> <br /> [[File:OrionWifi.jpg | thumb | &lt;center&gt; Wifi Antenna &lt;/center&gt;]]<br /> <br /> == Landing Drama == <br /> <br /> Upon landing, SSI-24 was discovered by two passers-by. They kindly brought it to their home and phoned the balloons team, who recovered it soon after. <br /> <br /> == Milestones == <br /> <br /> * First use of wifi antennas and Raspberry Pi on an SSI high altitude balloon<br /> * Successful implementation of a gimbal for the SPOT GPS<br /> <br /> {{balloon-footer}}<br /> [[Category: High Altitude Balloons]][[Category: Balloon Launches]]</div>

Amilich https://ssi-wiki.stanford.edu/w/index.php?title=SSI-24&diff=459 2015-10-27T18:55:30Z

<p>Amilich: </p> <hr /> <div>{{balloon-launch<br /> | header = SSI-24 (Orion)<br /> | img link = File:ssi_24.png<br /> | launch date = October 24th, 2015, 11:39AM PDT<br /> | launch site = 2093 San Juan Drive, Hollister, CA<br /> | launch coordinates = 36.84842,-121.43236<br /> | flight duration = 3 hours, 44 minutes, 11.1 seconds<br /> | top speed = 92.44 MPH<br /> | ground track = 121.21 miles<br /> | last = 23<br /> | next = 25<br /> }}<br /> <br /> SSI-24 Orion was one of three balloons launched during fall quarter, 2015. It consisted of an almost all-freshman team dedicated to creating a scientifically power yet aesthetically beautiful payload. Ultimately, Orion represented a resounding success in its use of sensors, logging of data, power management, use of solar energy to charge its batteries, demonstration of wifi transmissions, and creation of a visually refined payload. The total ground track was 121.21 miles, and the top speed reached was 92.44 miles per hour. <br /> <br /> == Pre-Launch == <br /> <br /> The Pre-Launch proceeded fairly well with few hiccups. After fixing minor problems with the solar panel wiring, the team prepared the gimbal and finished visual preparation of the payload. Unfortunately, the team experienced extreme difficulties setting up the keychain camera (which did not function during flight). The payload, which consisted of two styrofoam boxes and a selfie stick, was attached to a single 1500g balloon. <br /> <br /> == Flight == <br /> <br /> [[File:SSI24 map.png | thumb | &lt;center&gt;SSI 24 ground track. The GPS was likely deactivated above 60,000 feet due to poor firmware implementation.&lt;/center&gt;]]<br /> <br /> SSI-24 used the SPOT Nebula for tracking and recovery. See http://habmc.stanfordssi.org/#/app/spot_four. A Phantom 2 UAV was used by members of Orion to video the launch of SSI-23a, 23, 24, and 25. <br /> <br /> <br /> [[File:Drone.jpg | thumb | &lt;center&gt; Phantom 2 &lt;/center&gt;]]<br /> <br /> == Experimental Payload == <br /> <br /> [[File:SSI24-perspective.jpg | thumb | &lt;center&gt; Perspective view of the Orion sensor payload. &lt;/center&gt;]]<br /> <br /> SSI-24 included both a Raspberry Pi 2B and two Arduino Uno boards. The Raspberry Pi was initially intended to be used to stream live video from the balloon, however, due to issues with the camera board, it was simply used as a wifi access point. The two Arduino boards regulated the sensors onboard the balloon, including a temperature sensor, two heating pads, an SD reader, a GPS, a solar panel, and an accelerometer. Though the group initially intended to use a PIXY camera as well, the PIXY's requirement to be updated with signatures made it difficult to use aboard the balloon. <br /> <br /> The second board served a single purpose: dropping three Hershey's chocolate bars at a specified altitude. This was accomplished using the GPS altitude from the first Arduino, which would set a single digital pin to high. This would trigger the second Arduino to swing a servo and release the bars. <br /> <br /> [[File:OrionWifi.jpg | thumb | &lt;center&gt; Wifi Antenna &lt;/center&gt;]]<br /> <br /> == Landing Drama == <br /> <br /> Upon landing, SSI-24 was discovered by two passers-by. They kindly brought it to their home and phoned the balloons team, who recovered it soon after. <br /> <br /> == Milestones == <br /> <br /> * First use of wifi antennas and Raspberry Pi on an SSI high altitude balloon<br /> * Successful implementation of a gimbal for the SPOT GPS<br /> <br /> {{balloon-footer}}<br /> [[Category: High Altitude Balloons]][[Category: Balloon Launches]]</div>

Amilich