<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://ssi-wiki.stanford.edu/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thomas</id>
	<title>Stanford SSI Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://ssi-wiki.stanford.edu/w/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Thomas"/>
	<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/Special:Contributions/Thomas"/>
	<updated>2026-05-11T03:08:32Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.45.1</generator>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=Vector_Graphics_in_Altium&amp;diff=2419</id>
		<title>Vector Graphics in Altium</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=Vector_Graphics_in_Altium&amp;diff=2419"/>
		<updated>2017-02-08T22:03:27Z</updated>

		<summary type="html">&lt;p&gt;Thomas: /* Using an existing logo */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Altium currently lacks well-integrated support for putting vector graphics onto the silkscreen. There are a couple of workarounds for this. SSI&#039;s preferred option for vector graphics that will be re-used is to add them to the SSI font.&lt;br /&gt;
&lt;br /&gt;
For one-off&#039;s, there is the PCB Logo Importer Script provided by Altium and documented [http://wiki.altium.com/pages/viewpage.action?pageId=6848718 here] or in [http://letanphuc.net/2016/05/put-logo-pcb-altium/ more detail here].&lt;br /&gt;
&lt;br /&gt;
== Using an existing logo ==&lt;br /&gt;
&lt;br /&gt;
The SSI Altium libraries SVN includes an &amp;quot;SSI Logos&amp;quot; font that already contains most of the logos you might need (including SSI logos, team logos, and sponsor logos). You can find the font here:&lt;br /&gt;
&lt;br /&gt;
https://subversion.assembla.com/svn/stanfordspaceinitiative/libraries/logos/SSI&lt;br /&gt;
&lt;br /&gt;
Install the font by double-clicking and pressing Add or Install.&lt;br /&gt;
&lt;br /&gt;
Then launch Altium and insert a String on the Top or Bottom Overlay layer. Select TrueType font and choose &amp;quot;SSI Logos&amp;quot; as the font.&lt;br /&gt;
&lt;br /&gt;
Each logo corresponds to a particular character. For example, typing &#039;A&#039; will insert the SSI Logo. You can find a full list of available graphics here:&lt;br /&gt;
&lt;br /&gt;
https://stanfordssi.assembla.com/spaces/stanfordspaceinitiative/subversion/source/HEAD/libraries/logos/SSI/SSI_LogosKey.txt&lt;br /&gt;
&lt;br /&gt;
== Adding a new SVG ==&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=Vector_Graphics_in_Altium&amp;diff=2418</id>
		<title>Vector Graphics in Altium</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=Vector_Graphics_in_Altium&amp;diff=2418"/>
		<updated>2017-02-08T01:36:36Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Altium currently lacks well-integrated support for putting vector graphics onto the silkscreen. There are a couple of workarounds for this. SSI&#039;s preferred option for vector graphics that will be re-used is to add them to the SSI font.&lt;br /&gt;
&lt;br /&gt;
For one-off&#039;s, there is the PCB Logo Importer Script provided by Altium and documented [http://wiki.altium.com/pages/viewpage.action?pageId=6848718 here] or in [http://letanphuc.net/2016/05/put-logo-pcb-altium/ more detail here].&lt;br /&gt;
&lt;br /&gt;
== Using an existing logo ==&lt;br /&gt;
&lt;br /&gt;
== Adding a new SVG ==&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=Vector_Graphics_in_Altium&amp;diff=2417</id>
		<title>Vector Graphics in Altium</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=Vector_Graphics_in_Altium&amp;diff=2417"/>
		<updated>2017-02-08T01:36:11Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;Altium currently lacks well-integrated support for putting vector graphics onto the silkscreen. There are a couple of workarounds for this. SSI&amp;#039;s preferred option for vector g...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Altium currently lacks well-integrated support for putting vector graphics onto the silkscreen. There are a couple of workarounds for this. SSI&#039;s preferred option for vector graphics that will be re-used is to add them to the SSI font.&lt;br /&gt;
&lt;br /&gt;
For one-off&#039;s, there is the PCB Logo Importer Script provided by Altium and documented [http://wiki.altium.com/pages/viewpage.action?pageId=6848718 here] or in [http://letanphuc.net/2016/05/put-logo-pcb-altium/ more detail here].&lt;br /&gt;
&lt;br /&gt;
## Using an existing logo ##&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=File:Altimeter.jpg&amp;diff=1531</id>
		<title>File:Altimeter.jpg</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=File:Altimeter.jpg&amp;diff=1531"/>
		<updated>2016-02-20T08:05:52Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1530</id>
		<title>SSI Altimeter</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1530"/>
		<updated>2016-02-20T08:04:52Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The SSI Altimeter (also known as the &amp;quot;Dual Deploy Altimeter&amp;quot; or &amp;quot;Althometer&amp;quot;) is an ongoing project to develop a low-cost, customization, and easily programmable altimeter for SSI-run rocketry certifications.&lt;br /&gt;
&lt;br /&gt;
[[Category:Rockets]]&lt;br /&gt;
&lt;br /&gt;
{{rocket-project&lt;br /&gt;
| header = SSI Altimeter&lt;br /&gt;
| img link = File:altimeter.jpg}}&lt;br /&gt;
&lt;br /&gt;
== Project Status ==&lt;br /&gt;
&lt;br /&gt;
The altimeter is currently under development. An revision 1 has been produced and is currently undergoing testing.&lt;br /&gt;
&lt;br /&gt;
== Using the Altimeter ==&lt;br /&gt;
&lt;br /&gt;
=== First Steps ===&lt;br /&gt;
&lt;br /&gt;
Mount the Altimeter and a single-cell LiPo battery however you like in the rocket. Note that there must be a vent hole to the altimeter or else it cannot detect changes in pressure. (At this point, it is not orientation dependent, however this will eventually change.)&lt;br /&gt;
&lt;br /&gt;
Before connecting the battery to the altimeter, go ahead and connect the deployment charges to the green terminal blocks. They are labelled on the bottom of the board. For the vast majority of applications, the polarity does not matter.&lt;br /&gt;
&lt;br /&gt;
=== Power On ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;The altimeter is very sensitive to wind. It works fine when inside of a rocket body, but it gets very confused when its sensor is directly exposed to the wind.&#039;&#039; For this reason, there is a delay before the altimeter starts doing anything. It&#039;s important that you get the altimeter installed in the body tube (or nose cose) before this delay expires.&lt;br /&gt;
&lt;br /&gt;
When the altimeter powers up, you will see:&lt;br /&gt;
1. White LED blink&lt;br /&gt;
2. Program code blink (in this case: green / red)&lt;br /&gt;
3. White LED blink&lt;br /&gt;
4. Green LED - This green LED stays on during the startup delay.&lt;br /&gt;
&lt;br /&gt;
By the time the green LED goes off, the altimeter should be in the body tube or otherwise shielded from the wind. The altimeter will also take this as its zero altitude reading, so you should be fairly close to the launch site elevation by now.&lt;br /&gt;
&lt;br /&gt;
Miss it? No problem. Press the little button in the top left to reset to the beginning. As long as no charges fired, there&#039;s no problem with just resetting.&lt;br /&gt;
&lt;br /&gt;
=== In Flight ===&lt;br /&gt;
&lt;br /&gt;
For this launch, the altimeter is programmed to:&lt;br /&gt;
1. Wait until the rocket reaches at least 900 meters.&lt;br /&gt;
2. Keep waiting until the rocket has fallen at least 100 meters.&lt;br /&gt;
3. Deploy charge 1 after the rocket passes 700 meters.&lt;br /&gt;
4. Deploy charge 2 after the rocket passes 600 meters.&lt;br /&gt;
&lt;br /&gt;
=== Recovery and Post-Flight ===&lt;br /&gt;
&lt;br /&gt;
When you get the altimeter back, it should have a solid blue LED. If it doesn&#039;t, disconnect the (potentially undeployed) charges and note the color of the LED (and tell Thomas).&lt;br /&gt;
&lt;br /&gt;
The (limited, in this case) data from the flight is only stored as long as the altimeter is on. So don&#039;t pull the battery yet!&lt;br /&gt;
&lt;br /&gt;
Using an FTDI chip, connect GND on the FTDI to the debug pin nearest the LED (green lead in the photo below) and the RX pin on the FTDI to the debug pin nearest the logo (blue lead in the photo below). Open a serial terminal (screen /dev/ttyUSB0 on Linux - you can probably use Arduino if you&#039;re running an inferior OS). You should see a bunch of text output. It&#039;s just a repeating message, so you only need one copy of it.&lt;br /&gt;
&lt;br /&gt;
[[File:altimeterserial.jpg|400px]]&lt;br /&gt;
&lt;br /&gt;
== Random things ==&lt;br /&gt;
&lt;br /&gt;
=== Programming Configuration ===&lt;br /&gt;
&lt;br /&gt;
[[File:altimeterprog.jpg|400px]]&lt;br /&gt;
&lt;br /&gt;
=== How to disconnect the LiPo ===&lt;br /&gt;
&lt;br /&gt;
Hint: Don&#039;t pull on the wires!&lt;br /&gt;
&lt;br /&gt;
[https://www.sparkfun.com/tutorials/241]&lt;br /&gt;
&lt;br /&gt;
== Accessing Source Files ==&lt;br /&gt;
&lt;br /&gt;
Source files for the altimeter are in SSI&#039;s Subversion repository (where all Altium files are hosted). If you are an SSI member, talk with Logan Herrera or Thomas Teisberg about getting access.&lt;br /&gt;
&lt;br /&gt;
The intent is to make all of the hardware open source. This will likely be done after the project has reached a stable point.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1529</id>
		<title>SSI Altimeter</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1529"/>
		<updated>2016-02-20T08:02:03Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The SSI Altimeter (also known as the &amp;quot;Dual Deploy Altimeter&amp;quot; or &amp;quot;Althometer&amp;quot;) is an ongoing project to develop a low-cost, customization, and easily programmable altimeter for SSI-run rocketry certifications.&lt;br /&gt;
&lt;br /&gt;
[[Category:Rockets]]&lt;br /&gt;
&lt;br /&gt;
{{rocket-project&lt;br /&gt;
| header = SSI Altimeter&lt;br /&gt;
| img link = altimeter.jpg}}&lt;br /&gt;
&lt;br /&gt;
== Project Status ==&lt;br /&gt;
&lt;br /&gt;
The altimeter is currently under development. An revision 1 has been produced and is currently undergoing testing.&lt;br /&gt;
&lt;br /&gt;
== Using the Altimeter ==&lt;br /&gt;
&lt;br /&gt;
=== First Steps ===&lt;br /&gt;
&lt;br /&gt;
Mount the Altimeter and a single-cell LiPo battery however you like in the rocket. Note that there must be a vent hole to the altimeter or else it cannot detect changes in pressure. (At this point, it is not orientation dependent, however this will eventually change.)&lt;br /&gt;
&lt;br /&gt;
Before connecting the battery to the altimeter, go ahead and connect the deployment charges to the green terminal blocks. They are labelled on the bottom of the board. For the vast majority of applications, the polarity does not matter.&lt;br /&gt;
&lt;br /&gt;
=== Power On ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;The altimeter is very sensitive to wind. It works fine when inside of a rocket body, but it gets very confused when its sensor is directly exposed to the wind.&#039;&#039; For this reason, there is a delay before the altimeter starts doing anything. It&#039;s important that you get the altimeter installed in the body tube (or nose cose) before this delay expires.&lt;br /&gt;
&lt;br /&gt;
When the altimeter powers up, you will see:&lt;br /&gt;
1. White LED blink&lt;br /&gt;
2. Program code blink (in this case: green / red)&lt;br /&gt;
3. White LED blink&lt;br /&gt;
4. Green LED - This green LED stays on during the startup delay.&lt;br /&gt;
&lt;br /&gt;
By the time the green LED goes off, the altimeter should be in the body tube or otherwise shielded from the wind. The altimeter will also take this as its zero altitude reading, so you should be fairly close to the launch site elevation by now.&lt;br /&gt;
&lt;br /&gt;
Miss it? No problem. Press the little button in the top left to reset to the beginning. As long as no charges fired, there&#039;s no problem with just resetting.&lt;br /&gt;
&lt;br /&gt;
=== In Flight ===&lt;br /&gt;
&lt;br /&gt;
For this launch, the altimeter is programmed to:&lt;br /&gt;
1. Wait until the rocket reaches at least 900 meters.&lt;br /&gt;
2. Keep waiting until the rocket has fallen at least 100 meters.&lt;br /&gt;
3. Deploy charge 1 after the rocket passes 700 meters.&lt;br /&gt;
4. Deploy charge 2 after the rocket passes 600 meters.&lt;br /&gt;
&lt;br /&gt;
=== Recovery and Post-Flight ===&lt;br /&gt;
&lt;br /&gt;
When you get the altimeter back, it should have a solid blue LED. If it doesn&#039;t, disconnect the (potentially undeployed) charges and note the color of the LED (and tell Thomas).&lt;br /&gt;
&lt;br /&gt;
The (limited, in this case) data from the flight is only stored as long as the altimeter is on. So don&#039;t pull the battery yet!&lt;br /&gt;
&lt;br /&gt;
Using an FTDI chip, connect GND on the FTDI to the debug pin nearest the LED (green lead in the photo below) and the RX pin on the FTDI to the debug pin nearest the logo (blue lead in the photo below). Open a serial terminal (screen /dev/ttyUSB0 on Linux - you can probably use Arduino if you&#039;re running an inferior OS). You should see a bunch of text output. It&#039;s just a repeating message, so you only need one copy of it.&lt;br /&gt;
&lt;br /&gt;
[[File:altimeterserial.jpg|400px]]&lt;br /&gt;
&lt;br /&gt;
== Random things ==&lt;br /&gt;
&lt;br /&gt;
=== Programming Configuration ===&lt;br /&gt;
&lt;br /&gt;
[[File:altimeterprog.jpg|400px]]&lt;br /&gt;
&lt;br /&gt;
=== How to disconnect the LiPo ===&lt;br /&gt;
&lt;br /&gt;
Hint: Don&#039;t pull on the wires!&lt;br /&gt;
&lt;br /&gt;
[https://www.sparkfun.com/tutorials/241]&lt;br /&gt;
&lt;br /&gt;
== Accessing Source Files ==&lt;br /&gt;
&lt;br /&gt;
Source files for the altimeter are in SSI&#039;s Subversion repository (where all Altium files are hosted). If you are an SSI member, talk with Logan Herrera or Thomas Teisberg about getting access.&lt;br /&gt;
&lt;br /&gt;
The intent is to make all of the hardware open source. This will likely be done after the project has reached a stable point.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1528</id>
		<title>SSI Altimeter</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1528"/>
		<updated>2016-02-20T08:01:35Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The SSI Altimeter (also known as the &amp;quot;Dual Deploy Altimeter&amp;quot; or &amp;quot;Althometer&amp;quot;) is an ongoing project to develop a low-cost, customization, and easily programmable altimeter for SSI-run rocketry certifications.&lt;br /&gt;
&lt;br /&gt;
[[Category:Rockets]]&lt;br /&gt;
&lt;br /&gt;
{{rocket-project&lt;br /&gt;
| header = SSI Altimeter&lt;br /&gt;
| img link = altimeter.jpg}}&lt;br /&gt;
&lt;br /&gt;
== Project Status ==&lt;br /&gt;
&lt;br /&gt;
The altimeter is currently under development. An revision 1 has been produced and is currently undergoing testing.&lt;br /&gt;
&lt;br /&gt;
== Using the Altimeter ==&lt;br /&gt;
&lt;br /&gt;
=== First Steps ===&lt;br /&gt;
&lt;br /&gt;
Mount the Altimeter and a single-cell LiPo battery however you like in the rocket. Note that there must be a vent hole to the altimeter or else it cannot detect changes in pressure. (At this point, it is not orientation dependent, however this will eventually change.)&lt;br /&gt;
&lt;br /&gt;
Before connecting the battery to the altimeter, go ahead and connect the deployment charges to the green terminal blocks. They are labelled on the bottom of the board. For the vast majority of applications, the polarity does not matter.&lt;br /&gt;
&lt;br /&gt;
=== Power On ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;The altimeter is very sensitive to wind. It works fine when inside of a rocket body, but it gets very confused when its sensor is directly exposed to the wind.&#039;&#039; For this reason, there is a delay before the altimeter starts doing anything. It&#039;s important that you get the altimeter installed in the body tube (or nose cose) before this delay expires.&lt;br /&gt;
&lt;br /&gt;
When the altimeter powers up, you will see:&lt;br /&gt;
1. White LED blink&lt;br /&gt;
2. Program code blink (in this case: green / red)&lt;br /&gt;
3. White LED blink&lt;br /&gt;
4. Green LED - This green LED stays on during the startup delay.&lt;br /&gt;
&lt;br /&gt;
By the time the green LED goes off, the altimeter should be in the body tube or otherwise shielded from the wind. The altimeter will also take this as its zero altitude reading, so you should be fairly close to the launch site elevation by now.&lt;br /&gt;
&lt;br /&gt;
Miss it? No problem. Press the little button in the top left to reset to the beginning. As long as no charges fired, there&#039;s no problem with just resetting.&lt;br /&gt;
&lt;br /&gt;
=== In Flight ===&lt;br /&gt;
&lt;br /&gt;
For this launch, the altimeter is programmed to:&lt;br /&gt;
1. Wait until the rocket reaches at least 900 meters.&lt;br /&gt;
2. Keep waiting until the rocket has fallen at least 100 meters.&lt;br /&gt;
3. Deploy charge 1 after the rocket passes 700 meters.&lt;br /&gt;
4. Deploy charge 2 after the rocket passes 600 meters.&lt;br /&gt;
&lt;br /&gt;
=== Recovery and Post-Flight ===&lt;br /&gt;
&lt;br /&gt;
When you get the altimeter back, it should have a solid blue LED. If it doesn&#039;t, disconnect the (potentially undeployed) charges and note the color of the LED (and tell Thomas).&lt;br /&gt;
&lt;br /&gt;
The (limited, in this case) data from the flight is only stored as long as the altimeter is on. So don&#039;t pull the battery yet!&lt;br /&gt;
&lt;br /&gt;
Using an FTDI chip, connect GND on the FTDI to the debug pin nearest the LED (green lead in the photo below) and the RX pin on the FTDI to the debug pin nearest the logo (blue lead in the photo below). Open a serial terminal (screen /dev/ttyUSB0 on Linux - you can probably use Arduino if you&#039;re running an inferior OS). You should see a bunch of text output. It&#039;s just a repeating message, so you only need one copy of it.&lt;br /&gt;
&lt;br /&gt;
[[File:altimeterserial.jpg|400px|thumb]]&lt;br /&gt;
&lt;br /&gt;
== Random things ==&lt;br /&gt;
&lt;br /&gt;
=== Programming Configuration ===&lt;br /&gt;
&lt;br /&gt;
[[File:altimeterprog.jpg|400px|thumb]]&lt;br /&gt;
&lt;br /&gt;
=== How to disconnect the LiPo ===&lt;br /&gt;
&lt;br /&gt;
Hint: Don&#039;t pull on the wires!&lt;br /&gt;
&lt;br /&gt;
[https://www.sparkfun.com/tutorials/241]&lt;br /&gt;
&lt;br /&gt;
== Accessing Source Files ==&lt;br /&gt;
&lt;br /&gt;
Source files for the altimeter are in SSI&#039;s Subversion repository (where all Altium files are hosted). If you are an SSI member, talk with Logan Herrera or Thomas Teisberg about getting access.&lt;br /&gt;
&lt;br /&gt;
The intent is to make all of the hardware open source. This will likely be done after the project has reached a stable point.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=File:Altimeterprog.jpg&amp;diff=1527</id>
		<title>File:Altimeterprog.jpg</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=File:Altimeterprog.jpg&amp;diff=1527"/>
		<updated>2016-02-20T08:01:09Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1526</id>
		<title>SSI Altimeter</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1526"/>
		<updated>2016-02-20T08:00:26Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The SSI Altimeter (also known as the &amp;quot;Dual Deploy Altimeter&amp;quot; or &amp;quot;Althometer&amp;quot;) is an ongoing project to develop a low-cost, customization, and easily programmable altimeter for SSI-run rocketry certifications.&lt;br /&gt;
&lt;br /&gt;
[[Category:Rockets]]&lt;br /&gt;
&lt;br /&gt;
{{rocket-project&lt;br /&gt;
| header = SSI Altimeter&lt;br /&gt;
| img link = altimeter.jpg}}&lt;br /&gt;
&lt;br /&gt;
== Project Status ==&lt;br /&gt;
&lt;br /&gt;
The altimeter is currently under development. An revision 1 has been produced and is currently undergoing testing.&lt;br /&gt;
&lt;br /&gt;
== Using the Altimeter ==&lt;br /&gt;
&lt;br /&gt;
=== First Steps ===&lt;br /&gt;
&lt;br /&gt;
Mount the Altimeter and a single-cell LiPo battery however you like in the rocket. Note that there must be a vent hole to the altimeter or else it cannot detect changes in pressure. (At this point, it is not orientation dependent, however this will eventually change.)&lt;br /&gt;
&lt;br /&gt;
Before connecting the battery to the altimeter, go ahead and connect the deployment charges to the green terminal blocks. They are labelled on the bottom of the board. For the vast majority of applications, the polarity does not matter.&lt;br /&gt;
&lt;br /&gt;
=== Power On ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;The altimeter is very sensitive to wind. It works fine when inside of a rocket body, but it gets very confused when its sensor is directly exposed to the wind.&#039;&#039; For this reason, there is a delay before the altimeter starts doing anything. It&#039;s important that you get the altimeter installed in the body tube (or nose cose) before this delay expires.&lt;br /&gt;
&lt;br /&gt;
When the altimeter powers up, you will see:&lt;br /&gt;
1. White LED blink&lt;br /&gt;
2. Program code blink (in this case: green / red)&lt;br /&gt;
3. White LED blink&lt;br /&gt;
4. Green LED - This green LED stays on during the startup delay.&lt;br /&gt;
&lt;br /&gt;
By the time the green LED goes off, the altimeter should be in the body tube or otherwise shielded from the wind. The altimeter will also take this as its zero altitude reading, so you should be fairly close to the launch site elevation by now.&lt;br /&gt;
&lt;br /&gt;
Miss it? No problem. Press the little button in the top left to reset to the beginning. As long as no charges fired, there&#039;s no problem with just resetting.&lt;br /&gt;
&lt;br /&gt;
=== In Flight ===&lt;br /&gt;
&lt;br /&gt;
For this launch, the altimeter is programmed to:&lt;br /&gt;
1. Wait until the rocket reaches at least 900 meters.&lt;br /&gt;
2. Keep waiting until the rocket has fallen at least 100 meters.&lt;br /&gt;
3. Deploy charge 1 after the rocket passes 700 meters.&lt;br /&gt;
4. Deploy charge 2 after the rocket passes 600 meters.&lt;br /&gt;
&lt;br /&gt;
=== Recovery and Post-Flight ===&lt;br /&gt;
&lt;br /&gt;
When you get the altimeter back, it should have a solid blue LED. If it doesn&#039;t, disconnect the (potentially undeployed) charges and note the color of the LED (and tell Thomas).&lt;br /&gt;
&lt;br /&gt;
The (limited, in this case) data from the flight is only stored as long as the altimeter is on. So don&#039;t pull the battery yet!&lt;br /&gt;
&lt;br /&gt;
Using an FTDI chip, connect GND on the FTDI to the debug pin nearest the LED (green lead in the photo below) and the RX pin on the FTDI to the debug pin nearest the logo (blue lead in the photo below). Open a serial terminal (screen /dev/ttyUSB0 on Linux - you can probably use Arduino if you&#039;re running an inferior OS). You should see a bunch of text output. It&#039;s just a repeating message, so you only need one copy of it.&lt;br /&gt;
&lt;br /&gt;
[[File:altimeterserial.jpg|400px|right|thumb]]&lt;br /&gt;
&lt;br /&gt;
== Random things ==&lt;br /&gt;
&lt;br /&gt;
=== Programming Configuration ===&lt;br /&gt;
&lt;br /&gt;
[[File:altimeterprog.jpg|400px|right|thumb]]&lt;br /&gt;
&lt;br /&gt;
=== How to disconnect the LiPo ===&lt;br /&gt;
&lt;br /&gt;
Hint: Don&#039;t pull on the wires!&lt;br /&gt;
&lt;br /&gt;
[https://www.sparkfun.com/tutorials/241]&lt;br /&gt;
&lt;br /&gt;
== Accessing Source Files ==&lt;br /&gt;
&lt;br /&gt;
Source files for the altimeter are in SSI&#039;s Subversion repository (where all Altium files are hosted). If you are an SSI member, talk with Logan Herrera or Thomas Teisberg about getting access.&lt;br /&gt;
&lt;br /&gt;
The intent is to make all of the hardware open source. This will likely be done after the project has reached a stable point.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=File:Altimeterserial.jpg&amp;diff=1525</id>
		<title>File:Altimeterserial.jpg</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=File:Altimeterserial.jpg&amp;diff=1525"/>
		<updated>2016-02-20T07:57:47Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1524</id>
		<title>SSI Altimeter</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1524"/>
		<updated>2016-02-20T07:54:50Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The SSI Altimeter (also known as the &amp;quot;Dual Deploy Altimeter&amp;quot; or &amp;quot;Althometer&amp;quot;) is an ongoing project to develop a low-cost, customization, and easily programmable altimeter for SSI-run rocketry certifications.&lt;br /&gt;
&lt;br /&gt;
[[Category:Rockets]]&lt;br /&gt;
&lt;br /&gt;
{{rocket-project&lt;br /&gt;
| header = SSI Altimeter&lt;br /&gt;
| img link = altimeter.jpg}}&lt;br /&gt;
&lt;br /&gt;
== Project Status ==&lt;br /&gt;
&lt;br /&gt;
The altimeter is currently under development. An revision 1 has been produced and is currently undergoing testing.&lt;br /&gt;
&lt;br /&gt;
== Using the Altimeter ==&lt;br /&gt;
&lt;br /&gt;
=== First Steps ===&lt;br /&gt;
&lt;br /&gt;
Mount the Altimeter and a single-cell LiPo battery however you like in the rocket. Note that there must be a vent hole to the altimeter or else it cannot detect changes in pressure. (At this point, it is not orientation dependent, however this will eventually change.)&lt;br /&gt;
&lt;br /&gt;
Before connecting the battery to the altimeter, go ahead and connect the deployment charges to the green terminal blocks. They are labelled on the bottom of the board. For the vast majority of applications, the polarity does not matter.&lt;br /&gt;
&lt;br /&gt;
=== Power On ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;The altimeter is very sensitive to wind. It works fine when inside of a rocket body, but it gets very confused when its sensor is directly exposed to the wind.&#039;&#039; For this reason, there is a delay before the altimeter starts doing anything. It&#039;s important that you get the altimeter installed in the body tube (or nose cose) before this delay expires.&lt;br /&gt;
&lt;br /&gt;
When the altimeter powers up, you will see:&lt;br /&gt;
1. White LED blink&lt;br /&gt;
2. Program code blink (in this case: green / red)&lt;br /&gt;
3. White LED blink&lt;br /&gt;
4. Green LED - This green LED stays on during the startup delay.&lt;br /&gt;
&lt;br /&gt;
By the time the green LED goes off, the altimeter should be in the body tube or otherwise shielded from the wind. The altimeter will also take this as its zero altitude reading, so you should be fairly close to the launch site elevation by now.&lt;br /&gt;
&lt;br /&gt;
Miss it? No problem. Press the little button in the top left to reset to the beginning. As long as no charges fired, there&#039;s no problem with just resetting.&lt;br /&gt;
&lt;br /&gt;
=== In Flight ===&lt;br /&gt;
&lt;br /&gt;
For this launch, the altimeter is programmed to:&lt;br /&gt;
1. Wait until the rocket reaches at least 900 meters.&lt;br /&gt;
2. Keep waiting until the rocket has fallen at least 100 meters.&lt;br /&gt;
3. Deploy charge 1 after the rocket passes 700 meters.&lt;br /&gt;
4. Deploy charge 2 after the rocket passes 600 meters.&lt;br /&gt;
&lt;br /&gt;
=== Recovery and Post-Flight ===&lt;br /&gt;
&lt;br /&gt;
When you get the altimeter back, it should have a solid blue LED. If it doesn&#039;t, disconnect the (potentially undeployed) charges and note the color of the LED (and tell Thomas).&lt;br /&gt;
&lt;br /&gt;
The (limited, in this case) data from the flight is only stored as long as the altimeter is on. So don&#039;t pull the battery yet!&lt;br /&gt;
&lt;br /&gt;
Using an FTDI chip, connect GND on the FTDI to the debug pin nearest the LED (green lead in the photo below) and the RX pin on the FTDI to the debug pin nearest the logo (blue lead in the photo below). Open a serial terminal (screen /dev/ttyUSB0 on Linux - you can probably use Arduino if you&#039;re running an inferior OS). You should see a bunch of text output. It&#039;s just a repeating message, so you only need one copy of it.&lt;br /&gt;
&lt;br /&gt;
[[File:altimeterserial.jpg]]&lt;br /&gt;
&lt;br /&gt;
== Random things ==&lt;br /&gt;
&lt;br /&gt;
=== Programming Configuration ===&lt;br /&gt;
&lt;br /&gt;
[[File:altimeterprog.jpg]]&lt;br /&gt;
&lt;br /&gt;
=== How to disconnect the LiPo ===&lt;br /&gt;
&lt;br /&gt;
Hint: Don&#039;t pull on the wires!&lt;br /&gt;
&lt;br /&gt;
[https://www.sparkfun.com/tutorials/241]&lt;br /&gt;
&lt;br /&gt;
== Accessing Source Files ==&lt;br /&gt;
&lt;br /&gt;
Source files for the altimeter are in SSI&#039;s Subversion repository (where all Altium files are hosted). If you are an SSI member, talk with Logan Herrera or Thomas Teisberg about getting access.&lt;br /&gt;
&lt;br /&gt;
The intent is to make all of the hardware open source. This will likely be done after the project has reached a stable point.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1523</id>
		<title>SSI Altimeter</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1523"/>
		<updated>2016-02-20T07:50:25Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The SSI Altimeter (also known as the &amp;quot;Dual Deploy Altimeter&amp;quot; or &amp;quot;Althometer&amp;quot;) is an ongoing project to develop a low-cost, customization, and easily programmable altimeter for SSI-run rocketry certifications.&lt;br /&gt;
&lt;br /&gt;
[[Category:Rockets]]&lt;br /&gt;
&lt;br /&gt;
{{rocket-project&lt;br /&gt;
| header = SSI Altimeter&lt;br /&gt;
| img link =&lt;br /&gt;
| launch details = }}&lt;br /&gt;
&lt;br /&gt;
== Project Status ==&lt;br /&gt;
&lt;br /&gt;
The altimeter is currently under development. An revision 1 has been produced and is currently undergoing testing.&lt;br /&gt;
&lt;br /&gt;
== Using the Altimeter ==&lt;br /&gt;
&lt;br /&gt;
=== First Steps ===&lt;br /&gt;
&lt;br /&gt;
Mount the Altimeter and a single-cell LiPo battery however you like in the rocket. Note that there must be a vent hole to the altimeter or else it cannot detect changes in pressure. (At this point, it is not orientation dependent, however this will eventually change.)&lt;br /&gt;
&lt;br /&gt;
Before connecting the battery to the altimeter, go ahead and connect the deployment charges to the green terminal blocks. They are labelled on the bottom of the board. For the vast majority of applications, the polarity does not matter.&lt;br /&gt;
&lt;br /&gt;
=== Power On ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;The altimeter is very sensitive to wind. It works fine when inside of a rocket body, but it gets very confused when its sensor is directly exposed to the wind.&#039;&#039; For this reason, there is a delay before the altimeter starts doing anything. It&#039;s important that you get the altimeter installed in the body tube (or nose cose) before this delay expires.&lt;br /&gt;
&lt;br /&gt;
When the altimeter powers up, you will see:&lt;br /&gt;
1. White LED blink&lt;br /&gt;
2. Program code blink (in this case: green / red)&lt;br /&gt;
3. White LED blink&lt;br /&gt;
4. Green LED - This green LED stays on during the startup delay.&lt;br /&gt;
&lt;br /&gt;
By the time the green LED goes off, the altimeter should be in the body tube or otherwise shielded from the wind. The altimeter will also take this as its zero altitude reading, so you should be fairly close to the launch site elevation by now.&lt;br /&gt;
&lt;br /&gt;
Miss it? No problem. Press the little button in the top left to reset to the beginning. As long as no charges fired, there&#039;s no problem with just resetting.&lt;br /&gt;
&lt;br /&gt;
=== In Flight ===&lt;br /&gt;
&lt;br /&gt;
For this launch, the altimeter is programmed to:&lt;br /&gt;
1. Wait until the rocket reaches at least 900 meters.&lt;br /&gt;
2. Keep waiting until the rocket has fallen at least 100 meters.&lt;br /&gt;
3. Deploy charge 1 after the rocket passes 700 meters.&lt;br /&gt;
4. Deploy charge 2 after the rocket passes 600 meters.&lt;br /&gt;
&lt;br /&gt;
=== Recovery and Post-Flight ===&lt;br /&gt;
&lt;br /&gt;
When you get the altimeter back, it should have a solid blue LED. If it doesn&#039;t, disconnect the (potentially undeployed) charges and note the color of the LED (and tell Thomas).&lt;br /&gt;
&lt;br /&gt;
The (limited, in this case) data from the flight is only stored as long as the altimeter is on. So don&#039;t pull the battery yet!&lt;br /&gt;
&lt;br /&gt;
Using an FTDI chip, connect GND on the FTDI to the debug pin nearest the LED (green lead in the photo below) and the RX pin on the FTDI to the debug pin nearest the logo (blue lead in the photo below). Open a serial terminal (screen /dev/ttyUSB0 on Linux - you can probably use Arduino if you&#039;re running an inferior OS). You should see a bunch of text output. It&#039;s just a repeating message, so you only need one copy of it.&lt;br /&gt;
&lt;br /&gt;
[[File:Example.jpg]]&lt;br /&gt;
&lt;br /&gt;
== Random things ==&lt;br /&gt;
&lt;br /&gt;
== Accessing Source Files ==&lt;br /&gt;
&lt;br /&gt;
Source files for the altimeter are in SSI&#039;s Subversion repository (where all Altium files are hosted). If you are an SSI member, talk with Logan Herrera or Thomas Teisberg about getting access.&lt;br /&gt;
&lt;br /&gt;
The intent is to make all of the hardware open source. This will likely be done after the project has reached a stable point.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1522</id>
		<title>SSI Altimeter</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1522"/>
		<updated>2016-02-20T07:49:42Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The SSI Altimeter (also known as the &amp;quot;Dual Deploy Altimeter&amp;quot; or &amp;quot;Althometer&amp;quot;) is an ongoing project to develop a low-cost, customization, and easily programmable altimeter for SSI-run rocketry certifications.&lt;br /&gt;
&lt;br /&gt;
[[Category:Rockets]]&lt;br /&gt;
&lt;br /&gt;
{{rocket-project&lt;br /&gt;
| header = SSI Altimeter&lt;br /&gt;
| img link =&lt;br /&gt;
| launch details = &lt;br /&gt;
&lt;br /&gt;
== Project Status ==&lt;br /&gt;
&lt;br /&gt;
The altimeter is currently under development. An revision 1 has been produced and is currently undergoing testing.&lt;br /&gt;
&lt;br /&gt;
== Using the Altimeter ==&lt;br /&gt;
&lt;br /&gt;
=== First Steps ===&lt;br /&gt;
&lt;br /&gt;
Mount the Altimeter and a single-cell LiPo battery however you like in the rocket. Note that there must be a vent hole to the altimeter or else it cannot detect changes in pressure. (At this point, it is not orientation dependent, however this will eventually change.)&lt;br /&gt;
&lt;br /&gt;
Before connecting the battery to the altimeter, go ahead and connect the deployment charges to the green terminal blocks. They are labelled on the bottom of the board. For the vast majority of applications, the polarity does not matter.&lt;br /&gt;
&lt;br /&gt;
=== Power On ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;The altimeter is very sensitive to wind. It works fine when inside of a rocket body, but it gets very confused when its sensor is directly exposed to the wind.&#039;&#039; For this reason, there is a delay before the altimeter starts doing anything. It&#039;s important that you get the altimeter installed in the body tube (or nose cose) before this delay expires.&lt;br /&gt;
&lt;br /&gt;
When the altimeter powers up, you will see:&lt;br /&gt;
1. White LED blink&lt;br /&gt;
2. Program code blink (in this case: green / red)&lt;br /&gt;
3. White LED blink&lt;br /&gt;
4. Green LED - This green LED stays on during the startup delay.&lt;br /&gt;
&lt;br /&gt;
By the time the green LED goes off, the altimeter should be in the body tube or otherwise shielded from the wind. The altimeter will also take this as its zero altitude reading, so you should be fairly close to the launch site elevation by now.&lt;br /&gt;
&lt;br /&gt;
Miss it? No problem. Press the little button in the top left to reset to the beginning. As long as no charges fired, there&#039;s no problem with just resetting.&lt;br /&gt;
&lt;br /&gt;
=== In Flight ===&lt;br /&gt;
&lt;br /&gt;
For this launch, the altimeter is programmed to:&lt;br /&gt;
1. Wait until the rocket reaches at least 900 meters.&lt;br /&gt;
2. Keep waiting until the rocket has fallen at least 100 meters.&lt;br /&gt;
3. Deploy charge 1 after the rocket passes 700 meters.&lt;br /&gt;
4. Deploy charge 2 after the rocket passes 600 meters.&lt;br /&gt;
&lt;br /&gt;
=== Recovery and Post-Flight ===&lt;br /&gt;
&lt;br /&gt;
When you get the altimeter back, it should have a solid blue LED. If it doesn&#039;t, disconnect the (potentially undeployed) charges and note the color of the LED (and tell Thomas).&lt;br /&gt;
&lt;br /&gt;
The (limited, in this case) data from the flight is only stored as long as the altimeter is on. So don&#039;t pull the battery yet!&lt;br /&gt;
&lt;br /&gt;
Using an FTDI chip, connect GND on the FTDI to the debug pin nearest the LED (green lead in the photo below) and the RX pin on the FTDI to the debug pin nearest the logo (blue lead in the photo below). Open a serial terminal (screen /dev/ttyUSB0 on Linux - you can probably use Arduino if you&#039;re running an inferior OS). You should see a bunch of text output. It&#039;s just a repeating message, so you only need one copy of it.&lt;br /&gt;
&lt;br /&gt;
PHOTO&lt;br /&gt;
&lt;br /&gt;
== Random things ==&lt;br /&gt;
&lt;br /&gt;
== Accessing Source Files ==&lt;br /&gt;
&lt;br /&gt;
Source files for the altimeter are in SSI&#039;s Subversion repository (where all Altium files are hosted). If you are an SSI member, talk with Logan Herrera or Thomas Teisberg about getting access.&lt;br /&gt;
&lt;br /&gt;
The intent is to make all of the hardware open source. This will likely be done after the project has reached a stable point.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1403</id>
		<title>SSI Altimeter</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1403"/>
		<updated>2016-02-11T05:20:03Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The SSI Altimeter (also known as the &amp;quot;Dual Deploy Altimeter&amp;quot; or &amp;quot;Althometer&amp;quot;) is an ongoing project to develop a low-cost, customization, and easily programmable altimeter for SSI-run rocketry certifications.&lt;br /&gt;
&lt;br /&gt;
[[Category:Rockets]]&lt;br /&gt;
&lt;br /&gt;
{{rocket-project&lt;br /&gt;
| header = SSI Altimeter&lt;br /&gt;
| img link =&lt;br /&gt;
| launch details = &lt;br /&gt;
&lt;br /&gt;
== Project Status ==&lt;br /&gt;
&lt;br /&gt;
The altimeter is currently under development. An revision 1 has been produced and is currently undergoing testing.&lt;br /&gt;
&lt;br /&gt;
== Accessing Source Files ==&lt;br /&gt;
&lt;br /&gt;
Source files for the altimeter are in SSI&#039;s Subversion repository (where all Altium files are hosted). If you are an SSI member, talk with Logan Herrera or Thomas Teisberg about getting access.&lt;br /&gt;
&lt;br /&gt;
The intent is to make all of the hardware open source. This will likely be done after the project has reached a stable point.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1402</id>
		<title>SSI Altimeter</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=SSI_Altimeter&amp;diff=1402"/>
		<updated>2016-02-11T05:18:24Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;The SSI Altimeter (also known as the &amp;quot;Dual Deploy Altimeter&amp;quot; or &amp;quot;Althometer&amp;quot;) is an ongoing project to develop a low-cost, customization, and easily programmable altimeter for...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The SSI Altimeter (also known as the &amp;quot;Dual Deploy Altimeter&amp;quot; or &amp;quot;Althometer&amp;quot;) is an ongoing project to develop a low-cost, customization, and easily programmable altimeter for SSI-run rocketry certifications.&lt;br /&gt;
&lt;br /&gt;
== Project Status ==&lt;br /&gt;
&lt;br /&gt;
The altimeter is currently under development. An revision 1 has been produced and is currently undergoing testing.&lt;br /&gt;
&lt;br /&gt;
== Accessing Source Files ==&lt;br /&gt;
&lt;br /&gt;
Source files for the altimeter are in SSI&#039;s Subversion repository (where all Altium files are hosted). If you are an SSI member, talk with Logan Herrera or Thomas Teisberg about getting access.&lt;br /&gt;
&lt;br /&gt;
The intent is to make all of the hardware open source. This will likely be done after the project has reached a stable point.&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=Pulse_Position_Modulation&amp;diff=518</id>
		<title>Pulse Position Modulation</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=Pulse_Position_Modulation&amp;diff=518"/>
		<updated>2015-11-06T07:35:53Z</updated>

		<summary type="html">&lt;p&gt;Thomas: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;This article is currently just a list of resources for now. It will be (eventually) expanded to explain more concepts.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Understanding PPM ==&lt;br /&gt;
&lt;br /&gt;
This is a good resource for understanding how PPM works:&lt;br /&gt;
&lt;br /&gt;
http://www.pcbheaven.com/wikipages/Pulse_Position_Modulation/&lt;br /&gt;
&lt;br /&gt;
The part we&#039;re most interested in is actually Differential Pulse Position Modulation (DPPM) because it is both more efficient and easier to implement.&lt;br /&gt;
&lt;br /&gt;
== Digging a little deeper ==&lt;br /&gt;
&lt;br /&gt;
Stanford happens to have one of the world&#039;s experts on optical encoding on the faculty. One of Professor Kahn&#039;s more accessible papers is available here:&lt;br /&gt;
&lt;br /&gt;
http://ee.stanford.edu/~jmk/pubs/dppm.pdf&lt;br /&gt;
&lt;br /&gt;
This is a good introduction to why DPPM is one of the most efficient optical encoding techniques.&lt;br /&gt;
&lt;br /&gt;
== What to play with ==&lt;br /&gt;
&lt;br /&gt;
For those of you working on transmitting data across your 3 CM board, I&#039;d suggest the following development process:&lt;br /&gt;
&lt;br /&gt;
1. Get 4-DPPM working. In other words, output a constant length pulse followed by four possible delay times representing binary values 00, 01, 10, and 11. Write corresponding code to decode this and output the result over serial.&lt;br /&gt;
2. Experiment with what the minimum pulse timings you can use are. There will be some point at which you reach the limit of how fast you can detect the pulses.&lt;br /&gt;
3. Try to generalize your code to work for 4-DPPM, 8-DPPM, 16-DPPM, etc.&lt;br /&gt;
4. Add some form of automatic error detection ([checksums http://computer.howstuffworks.com/encryption7.htm]) and try to get your receive microcontroller to quantify the percent of successful transmissions.&lt;br /&gt;
&lt;br /&gt;
== Random notes on the board ==&lt;br /&gt;
&lt;br /&gt;
* The transimpedance amplifier doesn&#039;t get the signal up to logic level, so we&#039;re using an analog input to read the signal. That&#039;s not as fast as amplifying the signal in hardware (which is what the new amplifier board does) and then reading it with a digital input. This will likely be your limiting factor.&lt;br /&gt;
* There&#039;s a potentiometer near the big chip next to the LED. Turning that to the right increases the brightness of the LED. If you turn it too far to the right, the LED will give you a bright flash and permanently die. Keep it to a half turn or less.&lt;br /&gt;
&lt;br /&gt;
== PPM Code Repositories ==&lt;br /&gt;
&lt;br /&gt;
https://developer.mbed.org/users/tteisberg/code/Optical3cmRX/&lt;br /&gt;
https://developer.mbed.org/users/tteisberg/code/Optical3cmTXnucleo/&lt;br /&gt;
&lt;br /&gt;
Ask Thomas for access.&lt;br /&gt;
&lt;br /&gt;
[[Category:Optical Communications]]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
	<entry>
		<id>https://ssi-wiki.stanford.edu/w/index.php?title=Pulse_Position_Modulation&amp;diff=517</id>
		<title>Pulse Position Modulation</title>
		<link rel="alternate" type="text/html" href="https://ssi-wiki.stanford.edu/w/index.php?title=Pulse_Position_Modulation&amp;diff=517"/>
		<updated>2015-11-06T07:31:23Z</updated>

		<summary type="html">&lt;p&gt;Thomas: Created page with &amp;quot;&amp;#039;&amp;#039;This article is currently just a list of resources for now. It will be (eventually) expanded to explain more concepts.&amp;#039;&amp;#039;  == Understanding PPM ==  This is a good resource fo...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&#039;&#039;This article is currently just a list of resources for now. It will be (eventually) expanded to explain more concepts.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
== Understanding PPM ==&lt;br /&gt;
&lt;br /&gt;
This is a good resource for understanding how PPM works:&lt;br /&gt;
&lt;br /&gt;
http://www.pcbheaven.com/wikipages/Pulse_Position_Modulation/&lt;br /&gt;
&lt;br /&gt;
The part we&#039;re most interested in is actually Differential Pulse Position Modulation (DPPM) because it is both more efficient and easier to implement.&lt;br /&gt;
&lt;br /&gt;
== Digging a little deeper ==&lt;br /&gt;
&lt;br /&gt;
Stanford happens to have one of the world&#039;s experts on optical encoding on the faculty. One of Professor Kahn&#039;s more accessible papers is available here:&lt;br /&gt;
&lt;br /&gt;
http://ee.stanford.edu/~jmk/pubs/dppm.pdf&lt;br /&gt;
&lt;br /&gt;
This is a good introduction to why DPPM is one of the most efficient optical encoding techniques.&lt;br /&gt;
&lt;br /&gt;
== What to play with ==&lt;br /&gt;
&lt;br /&gt;
For those of you working on transmitting data across your 3 CM board, I&#039;d suggest the following development process:&lt;br /&gt;
&lt;br /&gt;
1. Get 4-DPPM working. In other words, output a constant length pulse followed by four possible delay times representing binary values 00, 01, 10, and 11. Write corresponding code to decode this and output the result over serial.&lt;br /&gt;
2. Experiment with what the minimum pulse timings you can use are. There will be some point at which you reach the limit of how fast you can detect the pulses.&lt;br /&gt;
3. Try to generalize your code to work for 4-DPPM, 8-DPPM, 16-DPPM, etc.&lt;br /&gt;
4. Add some form of automatic error detection ([checksums http://computer.howstuffworks.com/encryption7.htm]) and try to get your receive microcontroller to quantify the percent of successful transmissions.&lt;br /&gt;
&lt;br /&gt;
== Random notes on the board ==&lt;br /&gt;
&lt;br /&gt;
* The transimpedance amplifier doesn&#039;t get the signal up to logic level, so we&#039;re using an analog input to read the signal. That&#039;s not as fast as amplifying the signal in hardware (which is what the new amplifier board does) and then reading it with a digital input. This will likely be your limiting factor.&lt;br /&gt;
* There&#039;s a potentiometer near the big chip next to the LED. Turning that to the right increases the brightness of the LED. If you turn it too far to the right, the LED will give you a bright flash and permanently die. Keep it to a half turn or less.&lt;br /&gt;
&lt;br /&gt;
[[Category:Optical Communications]]&lt;/div&gt;</summary>
		<author><name>Thomas</name></author>
	</entry>
</feed>