summaryrefslogtreecommitdiff
authorJamey Sharp <jamey@minilop.net>2007-08-09 20:17:07 (GMT)
committer Jamey Sharp <jamey@minilop.net>2007-08-09 20:22:02 (GMT)
commit53c3c66fd05f2cfd9c399ff347b8815f231998a1 (patch) (side-by-side diff)
tree1c2f8f485c4e9eb58aa5126a0653e46bd1b28e19
parentc631956fabb8f3e1376c81a3a005d31165deef54 (diff)
downloadwiki-53c3c66fd05f2cfd9c399ff347b8815f231998a1.zip
wiki-53c3c66fd05f2cfd9c399ff347b8815f231998a1.tar.gz
Replace relative links with Ikiwiki links.
Eliminates 119 "orphan" warnings on AdminHome/issues and fixes the conversion problems with CapstoneLV2bProjectReport. Links to images are not replaced, because that would change the generated HTML--it would generate <img> tags instead of <a> links. Handled with an enhanced version of my previous wikilink script. find -name '*.mdwn' | xargs ../wikilink wikilink: #!/usr/bin/perl -pi use warnings; use strict; BEGIN { $::pat = qr{\Qhttp://psas.pdx.edu/\E(?!albums/|cgi-bin/|viewfile/|attach/)(?:PSAS/)?|(?!https?://|ftp://|mailto:|#)}; $::img = qr{<img ([^>]*src="(?:$::pat)[^"]*"[^>]*)>}; $::uri = qr{="(?:$::pat)([^"]*)(?<!png|gif|jpg)(?<!jpeg)"}; } sub mdwn { my ($target, $alt) = @_; if($alt) { $alt =~ s/^\s*(.*?)\s*$/$1/; (my $realalt = $alt) =~ s/\\//g; $alt = '' if $target =~ m{/\Q$realalt\E$}; } $alt = $alt ? $alt . '|' : ''; $target =~ s/\.html$//; return '[[' . $alt . $target . ']]'; } sub img { my @attrs = split(' ', $_[0]); my ($src, $alt); foreach(@attrs) { /^(.*?)=["']?(.*?)["']?$/; $src = $2 if $1 eq "src"; $alt = $2 if $1 eq "alt"; } $src =~ s/^(?:$::pat)//o; return mdwn($src, $alt); } s!$::img!img($1)!iego; s!<a href(?:$::uri)[^>]*>\s*(.*?)\s*</a>!mdwn($1, $2)!iego; s!\!\[\s*([^]]*)\s*\]\((?:$::pat)([^)]*\.(?:png|gif|jpg|jpeg))\)!mdwn($2, $1)!iego; s{\[\s*([^]]*)\s*\]\((?:$::pat)([^)]*)(?<!png|gif|jpg)(?<!jpeg)\)}{mdwn($2, $1)}iego;
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--AdminHome/issues.mdwn13
-rw-r--r--AirframeTeamHome.mdwn4
-rw-r--r--AntennaDesignLV2.mdwn2
-rw-r--r--AntennaLetter.mdwn8
-rw-r--r--BatteryPack.mdwn2
-rw-r--r--CADDrawings.mdwn2
-rw-r--r--CapstoneLV2b/ProjectProposalCoverSheet.mdwn2
-rw-r--r--CapstoneLV2bProjectReport.mdwn4
-rw-r--r--CapstoneLV2bProjectReport/ComponentSpec/Glue.mdwn16
-rw-r--r--CapstoneLV2bProjectReport/ComponentSpec/SPS.mdwn2
-rw-r--r--CapstoneLV2bProjectReport/DetailedDesign/BoardLayout.mdwn6
-rw-r--r--CapstoneLV2bProjectReport/SystemBlockDiagram.mdwn2
-rw-r--r--CapstoneLV2bProjectReport/SystemBlockDiagram/Glue.mdwn2
-rw-r--r--CapstoneLV2bProjectReport/SystemBlockDiagram/SPS.mdwn2
-rw-r--r--CoordinateSystem.mdwn6
-rw-r--r--DirectionsToGordonsShop.mdwn2
-rw-r--r--FABDirections.mdwn2
-rw-r--r--FlowMeter.mdwn2
-rw-r--r--HybridDataSheets.mdwn12
-rw-r--r--HybridFireControl.mdwn2
-rw-r--r--HybridNozzle.mdwn2
-rw-r--r--HybridPlaces.mdwn2
-rw-r--r--HybridSolenoids.mdwn6
-rw-r--r--IgnitionRing.mdwn4
-rw-r--r--Introduction.mdwn2
-rw-r--r--LV2AirframeArchive.mdwn4
-rw-r--r--LV2b_Conceptual_Design.mdwn6
-rw-r--r--LV2cFinClamps.mdwn2
-rw-r--r--LV2cModule.mdwn2
-rw-r--r--LV2cMotorCasing.mdwn2
-rw-r--r--LV2cNosecone.mdwn4
-rw-r--r--LvTwoCompactFlash.mdwn4
-rw-r--r--MeteringOrifice.mdwn2
-rw-r--r--NodeMicrocontrollerSearch/STMDiscussion.mdwn4
-rw-r--r--ProjectLV2AirframeJigs.mdwn10
-rw-r--r--ProjectLV2FinDesignReferences.mdwn4
-rw-r--r--ProjectLV2MotorCoupler.mdwn2
-rw-r--r--PrototypeMotorParameters.mdwn2
-rw-r--r--PsasLogo.mdwn12
-rw-r--r--Q2IgniterEvaluation.mdwn12
-rw-r--r--RotaryReturn.mdwn4
-rw-r--r--SmartBatteriesLv2.mdwn2
-rw-r--r--TheoryOfOperation.mdwn2
-rw-r--r--UplinkLv1.mdwn2
-rw-r--r--logo.mdwn2
-rw-r--r--news/2002-02-27.mdwn2
-rw-r--r--news/2002-04-07.mdwn8
-rw-r--r--news/2003-09-21.mdwn2
-rw-r--r--news/2003-12-21.mdwn2
-rw-r--r--news/2003-12-31.mdwn4
-rw-r--r--news/2004-04-17.mdwn2
-rw-r--r--news/2004-05-15.mdwn6
-rw-r--r--news/2004-06-26.mdwn6
-rw-r--r--news/2005-10-25.mdwn2
-rw-r--r--news/2005-11-30.mdwn4
-rw-r--r--news/2006-02-06.mdwn6
-rw-r--r--news/2006-08-02/logo.mdwn38
-rw-r--r--news/2007-03-14.mdwn4
-rw-r--r--psas/Current_project/Parafoil/Parafoil.mdwn2
-rw-r--r--psas/Resources.mdwn2
-rw-r--r--psas/Resources/CAD.mdwn2
-rw-r--r--psas/Resources/Links.mdwn2
-rw-r--r--psas/intro.mdwn2
63 files changed, 141 insertions, 148 deletions
diff --git a/AdminHome/issues.mdwn b/AdminHome/issues.mdwn
index 6a45093..aefa120 100644
--- a/AdminHome/issues.mdwn
+++ b/AdminHome/issues.mdwn
@@ -20,16 +20,9 @@ Pages with the idiom of a table containing "Up" and "Xref" links lost
the link text in those links--the target page name is the link text
instead. See [[LaunchControl]], for example.
-Pages inlined into the CapstoneLV2bProjectReport have incorrect links to
-certain attachments, even though these links are correct if you view the
-inlined page by itself. For example, the Board Layout section should
-have some images, which are visible in
-[[CapstoneLV2bProjectReport/DetailedDesign/BoardLayout]] but are not
-visible in [[CapstoneLV2bProjectReport]].
-
-A probably related but opposite problem is visible at
-[[FlightComputer]]. Some links to images got converted into inlined
-copies of the images, which really screws with the look of the page.
+At pages like [[FlightComputer]], some links to images got converted
+into inlined copies of the images, which really screws with the look of
+the page.
Blockquoted text got paragraph-breaks inserted around inline markup like
bold and links, because TWiki generated illegal HTML that Perl's
diff --git a/AirframeTeamHome.mdwn b/AirframeTeamHome.mdwn
index 0531be3..5ad951c 100644
--- a/AirframeTeamHome.mdwn
+++ b/AirframeTeamHome.mdwn
@@ -1,6 +1,6 @@
-![](airframe_title.jpg)
+[[airframe_title.jpg]]
-![](airframe_model_8-06.jpg)
+[[airframe_model_8-06.jpg]]
## LV2c Conceptual Design
diff --git a/AntennaDesignLV2.mdwn b/AntennaDesignLV2.mdwn
index 7605646..7908a59 100644
--- a/AntennaDesignLV2.mdwn
+++ b/AntennaDesignLV2.mdwn
@@ -415,7 +415,7 @@ We also have some older [[software|Minutiae/MiscAntennaSoftware]] which we can u
<cite>Antenna Engineering Handbook</cite>
-Tektronix <cite>Analog Design System (ADS) User Manual</cite> T0-6360-00<br />[ads2.pdf](/AntennaDesignLV2/ads2.pdf) (3.1M)<br />Contains several microstrip design equations in the chapter on application models.
+Tektronix <cite>Analog Design System (ADS) User Manual</cite> T0-6360-00<br />[[/AntennaDesignLV2/ads2.pdf]] (3.1M)<br />Contains several microstrip design equations in the chapter on application models.
Guillermo Gonzalez, <cite>Microwave Transistor Amplifiers</cite>, 2nd ed. 1997
diff --git a/AntennaLetter.mdwn b/AntennaLetter.mdwn
index abb899f..f765c7f 100644
--- a/AntennaLetter.mdwn
+++ b/AntennaLetter.mdwn
@@ -1,7 +1,7 @@
<center>
<h1>PSAS Request for Antenna Design Assistance <table border=1 cellpadding=0 cellspacing=0>
<tr>
- <td><img alt="Avionics_Module_08-14-01_mod_small.jpg" src="/AntennaLetter/Avionics_Module_08-14-01_mod_small.jpg"></td>
+ <td>[[/AntennaLetter/Avionics_Module_08-14-01_mod_small.jpg]]</td>
</tr>
</table>
</h1>
@@ -9,7 +9,7 @@
## <a name="Introduction"></a> Introduction
-The Portland State Aerospace Society (PSAS) is a university-based non-profit group located at Portland State University in Portland, Oregon. We're currently working on our third generation sounding rocket called Launch Vehicle No. 2 - or LV2. LV2 is 3.5m tall (11.4ft), 13.6cm (5.37") in diameter, and should obtain a maximum velocity of Mach 3.5 on it's way to an apogee of 20km (65,600ft). Here's the [ PDF file of the simulated flight profile ](/AntennaLetter/LV2_Flight_Profile_8-2001.pdf).
+The Portland State Aerospace Society (PSAS) is a university-based non-profit group located at Portland State University in Portland, Oregon. We're currently working on our third generation sounding rocket called Launch Vehicle No. 2 - or LV2. LV2 is 3.5m tall (11.4ft), 13.6cm (5.37") in diameter, and should obtain a maximum velocity of Mach 3.5 on it's way to an apogee of 20km (65,600ft). Here's the [[PDF file of the simulated flight profile|/AntennaLetter/LV2_Flight_Profile_8-2001.pdf]].
We're scheduled to launch a low altitude airframe test on September 29th, and possibly a half height flight the day after. Our next launch will be sometime in Spring 2002.
@@ -56,8 +56,8 @@ Here's a [diagram](/AntennasForLV2/Avionics_Module_08-14-01.jpg) of exactly what
</td>
</tr>
<tr>
- <td><img alt="Avionics_Module_08-14-01_dims_small.jpg" src="/AntennaLetter/Avionics_Module_08-14-01_dims_small.jpg"></td>
- <td><img alt="Avionics_Module_08-14-01_pict.jpg" src="/AntennaLetter/Avionics_Module_08-14-01_pict.jpg"></td>
+ <td>[[/AntennaLetter/Avionics_Module_08-14-01_dims_small.jpg]]</td>
+ <td>[[/AntennaLetter/Avionics_Module_08-14-01_pict.jpg]]</td>
</tr>
</table>
</center>
diff --git a/BatteryPack.mdwn b/BatteryPack.mdwn
index b4ee5b7..6e5bf23 100644
--- a/BatteryPack.mdwn
+++ b/BatteryPack.mdwn
@@ -12,7 +12,7 @@ Some documents:
- [[PrimaryVsSecondaryDiscussion]] (which is better?)
-- See the [Battery Chemistry Comparison and Selection Document](/BatteryPack/LV2_Batteries.doc) for our decisions on the battery pack.
+- See the [[Battery Chemistry Comparison and Selection Document|/BatteryPack/LV2_Batteries.doc]] for our decisions on the battery pack.
- We'll use a [[CAN node|CanNodeSectionAppPower]] to to communicate battery state of charge to the FC as well as hold the battery charging IC.
diff --git a/CADDrawings.mdwn b/CADDrawings.mdwn
index d1221ff..51335c9 100644
--- a/CADDrawings.mdwn
+++ b/CADDrawings.mdwn
@@ -4,7 +4,7 @@
<table border=1 cellpadding=0 cellspacing=0>
<tr>
- <td><a href="/CADDrawings/GOX-Paraffinv01.3.dxf" target="_top">GOX/Paraffin v3.0.dxf</a></td>
+ <td>[[GOX/Paraffin v3.0.dxf|/CADDrawings/GOX-Paraffinv01.3.dxf]]</td>
<td> Preliminary GOX/Paraffin Prototype Hybrid Motorin .dxf format </td>
</tr>
<tr>
diff --git a/CapstoneLV2b/ProjectProposalCoverSheet.mdwn b/CapstoneLV2b/ProjectProposalCoverSheet.mdwn
index fa95cc1..e8eb9ed 100644
--- a/CapstoneLV2b/ProjectProposalCoverSheet.mdwn
+++ b/CapstoneLV2b/ProjectProposalCoverSheet.mdwn
@@ -1,4 +1,4 @@
-![](PSASJupiterRingLogo640.png)
+[[PSASJupiterRingLogo640.png]]
# 2005/06 PSU Capstone: Portland State Aerospace Society (PSAS) Avionics Team Project Proposal
diff --git a/CapstoneLV2bProjectReport.mdwn b/CapstoneLV2bProjectReport.mdwn
index 958bba2..fdbf9b0 100644
--- a/CapstoneLV2bProjectReport.mdwn
+++ b/CapstoneLV2bProjectReport.mdwn
@@ -1,4 +1,4 @@
-![](logo.jpg)
+[[logo.jpg]]
**PSAS Avionics Node Front End for LV2b Rocket**
@@ -56,7 +56,7 @@ These engineering notebooks should cover the three major areas of design: the Sw
Here is the new avionics system design:
-![](lv2_avionics_diagram_2006-06-01_sized.png)
+[[lv2_avionics_diagram_2006-06-01_sized.png]]
[[inline pages="CapstoneLV2bProjectReport/SystemBlockDiagram" raw="yes"]]
diff --git a/CapstoneLV2bProjectReport/ComponentSpec/Glue.mdwn b/CapstoneLV2bProjectReport/ComponentSpec/Glue.mdwn
index 780362c..a85e341 100644
--- a/CapstoneLV2bProjectReport/ComponentSpec/Glue.mdwn
+++ b/CapstoneLV2bProjectReport/ComponentSpec/Glue.mdwn
@@ -41,7 +41,7 @@ _Specifications/ Calculations:_
The following figure illustrates the USB filtering block.
-![](gnl_schem_usb.png)
+[[gnl_schem_usb.png]]
**Fig. Glue.1**
@@ -105,11 +105,11 @@ _Specifications/ Calculations:_
- This component provides 15 kV of ESD capability to the D+ and D- USB signals. The part adds 35 pF of capacitance on each signal circuit to ground. This values is still within the USB 2.0 edge capacitance spec of 75 pF. Figure Glue.2 illustrates the parts internal circuit. Figure Glue.3 illustrates the relationship between circuit voltage, and the suppressing current capability.
-![](sn65220_1.png) _Image from TI SN65220 datasheet_
+[[sn65220_1.png]] _Image from TI SN65220 datasheet_
**Fig. Glue.2**
-![](sn65220_2.png) _Image from TI SN65220 datasheet_
+[[sn65220_2.png]] _Image from TI SN65220 datasheet_
**Fig. Glue.3**
@@ -129,7 +129,7 @@ _Specifications/ Calculations:_
- This component provides RF attenuation on the USB circuit as shown in Figure Glue.4. The baseband USB signal is 12 Mb/sec, giving a worst case frequency (alternating 1010... pattern) of 6 MHz. In order to to attenuate this signal, the device number 471 in Figur Glue.4 should be chosen. This gives a maximum attenuation of about 38 dB at approximately 150 MHz. This maximum attenuation frequency is useful in another respect since we use 146 MHz VHF communications for another avionics subsystem. Note 6 in the data sheet mentions the device deteriorates when subjected to surges or abnormal voltages, therefore it should be placed behind the USB TVSS. The circuit is effectively a Tee fiter, with the shunting member connected to IO ground.
Interesting note: The USB 2.0 spec on the bottom of page 142 states that the use of _ferrite beads_ on a full speed USB device is discouraged.
-![](exccet.png) _Image from Panasonic EXCCET data sheet_
+[[exccet.png]] _Image from Panasonic EXCCET data sheet_
**Fig. Glue.4**
@@ -160,11 +160,11 @@ _Specifications/ Calculations:_
Another constraint to choosing the MCP130 threshold voltage is to allow normal SPS load regulation to offur, and not cause an unwanted reset. Jacob assures in the SPS design that V<sub>DD</sub> should never go below 3.0 volts under normal output ripple conditions. Infact he indicates that is V<sub>DD</sub> does go below 3.0 volts this is a fault condition and something is wrong, and a reset would be appropriate.
Figure Glue.5 shows the allowed duration of a voltage drop-out transient allowed before a reset is generated by the MCP130. Normal operation of the SPS is around V<sub>Trip</sub> - V<sub>DD</sub> = 0.3 volts, which allows a drop-out transient of about 3 us. This is well within the SPS spec according to Jacob. A final constraint is the length of time reset is asserted after power-up. Figure Glue.6 illustrates this relationship, with t<sub>RPU</sub> being approximately 275 ms for the MCP130 variant chosen. The LPC User Manual section 3.10 indicates this needs to be at least 10 ms for the first reset as power is first applied, and can be as little as 300 ns for subsequent resets after to chips oscillator is up and running.
-![](mcp130_2_2.png) _Image from Microchip MCP130 datasheet_
+[[mcp130_2_2.png]] _Image from Microchip MCP130 datasheet_
**Fig. Glue.5**
-![](mcp130_1_1.png) _Image from Microchip MCP130 datasheet_
+[[mcp130_1_1.png]] _Image from Microchip MCP130 datasheet_
**Fig. Glue.6**
@@ -174,7 +174,7 @@ _Specifications/ Calculations:_
- The crystal based system oscillator is described in the Philips User Manual in chapter 3. This oscillator and divider block provides two functions to the node. First it is the primary system clock for the LPC2148 microcontroller, and second it is a synchronizing oscillator for the SPS. The oscillator amplifier is internal to the LPC2148 with output appearing on X2 (pin 61), and input on X1 (pin 62). The microcontroller internally uses the output of the amplifier to operate it's logic clock circuits. Fig. Glue.7 shows the schematic of this functioal block
-![](gnl_schem_osc.png)
+[[gnl_schem_osc.png]]
**Fig. Glue.7**
@@ -307,7 +307,7 @@ _Specifications/ Calculations:_
- 8 = 2<sup>3</sup>, so pick off signal at Q3. This divider is also useful for other application specific functions to be identified later since it is simultaneously creating all versions of the system clock divided by 2<sup>1</sup> through 2<sup>7</sup> inclusively. For convenience I have placed below a diagram which shows the internal configuration of this divider.
-![](cd4024.png) _Image from TI CD4024 datasheet_
+[[cd4024.png]] _Image from TI CD4024 datasheet_
**Fig. Glue.8**
diff --git a/CapstoneLV2bProjectReport/ComponentSpec/SPS.mdwn b/CapstoneLV2bProjectReport/ComponentSpec/SPS.mdwn
index eb6695a..2489b37 100644
--- a/CapstoneLV2bProjectReport/ComponentSpec/SPS.mdwn
+++ b/CapstoneLV2bProjectReport/ComponentSpec/SPS.mdwn
@@ -1,4 +1,4 @@
-![](SPS_Design_Schematic_rev2_2.png)
+[[SPS_Design_Schematic_rev2_2.png]]
[[SPS_Design_Schematic_rev2_2.pdf]]
diff --git a/CapstoneLV2bProjectReport/DetailedDesign/BoardLayout.mdwn b/CapstoneLV2bProjectReport/DetailedDesign/BoardLayout.mdwn
index 1938cc7..b3e390b 100644
--- a/CapstoneLV2bProjectReport/DetailedDesign/BoardLayout.mdwn
+++ b/CapstoneLV2bProjectReport/DetailedDesign/BoardLayout.mdwn
@@ -2,14 +2,14 @@ This is the preliminary board layout; it is not complete. The board dimensions a
On the left top side of the board is the USB/Power connector. The Debug port will be placed on the left bottom side.
-![](gnl_board.png)
+[[gnl_board.png]]
Both top and bottom of board shown with component placemets
-![](gnl_board_top.png)
+[[gnl_board_top.png]]
Top side only of board
-![](gnl_board_bot.png)
+[[gnl_board_bot.png]]
Bottom side only of board
diff --git a/CapstoneLV2bProjectReport/SystemBlockDiagram.mdwn b/CapstoneLV2bProjectReport/SystemBlockDiagram.mdwn
index b346548..256106b 100644
--- a/CapstoneLV2bProjectReport/SystemBlockDiagram.mdwn
+++ b/CapstoneLV2bProjectReport/SystemBlockDiagram.mdwn
@@ -2,6 +2,6 @@
The scope of this project is within the dashed line.
-![](sys_block.png)
+[[sys_block.png]]
Each generic node front-end contains a switching power supply (SPS), some "glue circuitry", and an ARM microcontroller running a real-time operating system (RTOS).
diff --git a/CapstoneLV2bProjectReport/SystemBlockDiagram/Glue.mdwn b/CapstoneLV2bProjectReport/SystemBlockDiagram/Glue.mdwn
index a7bad8f..7d2fee9 100644
--- a/CapstoneLV2bProjectReport/SystemBlockDiagram/Glue.mdwn
+++ b/CapstoneLV2bProjectReport/SystemBlockDiagram/Glue.mdwn
@@ -1,6 +1,6 @@
The underlying goal of the Glue subsystem is to satisfy the interconnection needs of the microcontroller, and to provide any forseen resources to the application specific area for future users.
-![](glue_block.png)
+[[glue_block.png]]
_**System Block Diagram - Glue**_
diff --git a/CapstoneLV2bProjectReport/SystemBlockDiagram/SPS.mdwn b/CapstoneLV2bProjectReport/SystemBlockDiagram/SPS.mdwn
index 792e856..a86752c 100644
--- a/CapstoneLV2bProjectReport/SystemBlockDiagram/SPS.mdwn
+++ b/CapstoneLV2bProjectReport/SystemBlockDiagram/SPS.mdwn
@@ -1,4 +1,4 @@
-![](SPS_Block_Diagram.png)
+[[SPS_Block_Diagram.png]]
**Power Bus**
diff --git a/CoordinateSystem.mdwn b/CoordinateSystem.mdwn
index 52ba173..15823e0 100644
--- a/CoordinateSystem.mdwn
+++ b/CoordinateSystem.mdwn
@@ -8,7 +8,7 @@
Fig. 1 shows the coordinate convention used for our rocket.
-![](Body-Coordinates.png)
+[[Body-Coordinates.png]]
We tried, but nobody would use anything but theta(θ) to indicate roll, so we went with that. The &lt;xyz&gt; axes form a right handed coordinate system where roll is measured on the z axis parallel to the body axis. We arbitrarily assign the x axis to be pitch with angle phi(φ), and the y axis to be yaw with angle psi(ψ). The intention is to assign the axis of the horizon camera as the x axis, though we don't expect perfect alignment so probably whichever IMU axis is nearly parallel to the horizon camera will be the "real" x axis.
@@ -26,7 +26,7 @@ The only modification to this document (so far) is that we've switched the names
Since for now we're doing only relatively low altitude sounding rocket flights, we like to define our local coordinate system assuming a flat Earth. That is, we define a rectangular coordinate system centered on our launch site with "up" defined by the gravity-plumb line. To keep this system easy to use we align the (x) axis with true East and the (y) axis to true North. The resulting East-North-Up &lt;enu&gt; system is a right handed rectangular coordinate system as shown in the next figure.
-![](enu.png)
+[[enu.png]]
For more information including the formula for transforming from ECEF-g (Earth Centered Earth Fixed Geodetic) to &lt;enu&gt; please see the attached document: [[Latitude_to_LocalTangent.pdf]]
@@ -161,4 +161,4 @@ Each position reference frame defines a right-handed coordinate system.
Lift and drag are not typically aligned with the body frame axes. The next figure indicates the relationship and suggests some conventions for labeling lift, drag, and some other body forces.
-![](Lift-etc.png)<br /> Lift and Drag in body coordinates
+[[Lift-etc.png]]<br /> Lift and Drag in body coordinates
diff --git a/DirectionsToGordonsShop.mdwn b/DirectionsToGordonsShop.mdwn
index 326074c..8d4c22c 100644
--- a/DirectionsToGordonsShop.mdwn
+++ b/DirectionsToGordonsShop.mdwn
@@ -16,6 +16,6 @@ Luckily, Gordon's shop is on the first floor and is pretty close to the west gar
And here's an image to show you where to park and which entrance to come in:
-![](cathedral_park.jpg)
+[[cathedral_park.jpg]]
If no one's around, you may have to call someone's cell phone to have us come out and let you in.
diff --git a/FABDirections.mdwn b/FABDirections.mdwn
index 6cc87cc..175eb58 100644
--- a/FABDirections.mdwn
+++ b/FABDirections.mdwn
@@ -13,7 +13,7 @@ Here's a [Google map](http://maps.google.com/maps?f=q&hl=en&q=1900+sw+4th+avenue
Here's an annotated google map of the FAB:
-![](FAB-EB-Parking-Map.png)
+[[FAB-EB-Parking-Map.png]]
If you walked or took the bus, use the main FAB entrance on the southwest corner of the building off of SW 4th Avenue.
diff --git a/FlowMeter.mdwn b/FlowMeter.mdwn
index 5c103cb..ff425a0 100644
--- a/FlowMeter.mdwn
+++ b/FlowMeter.mdwn
@@ -1,6 +1,6 @@
page is under construction
-[Working copy of automated oxygen metering system document](/FlowMeter/AutomatedOxygenMeteringSystem.doc)
+[[Working copy of automated oxygen metering system document|/FlowMeter/AutomatedOxygenMeteringSystem.doc]]
Misc Parts info:
diff --git a/HybridDataSheets.mdwn b/HybridDataSheets.mdwn
index 58c1f6b..8ee0c41 100644
--- a/HybridDataSheets.mdwn
+++ b/HybridDataSheets.mdwn
@@ -4,27 +4,27 @@
<table border=1 cellpadding=0 cellspacing=0>
<tr>
- <td><a href="/HybridDataSheets/0600P-42LP.pdf" target="_top">Parker Solenoid</a></td>
+ <td>[[Parker Solenoid|/HybridDataSheets/0600P-42LP.pdf]]</td>
<td> Nitrogen purge selonoid. Parker &#39;42 series&#39; valve. Ours has 110v selonoid coil (not hand lever) </td>
</tr>
<tr>
- <td><a href="/HybridDataSheets/ser-3823.pdf" target="_top">Spartan Scientific Solenoid</a></td>
+ <td>[[Spartan Scientific Solenoid|/HybridDataSheets/ser-3823.pdf]]</td>
<td> Pneumatic valve actuator selonoid. Spartan &#39;3823 series&#39; valve. 12 volt </td>
</tr>
<tr>
- <td><a href="/HybridDataSheets/Tescom44-1100s.pdf" target="_top">Tescom Regulator</a></td>
+ <td>[[Tescom Regulator|/HybridDataSheets/Tescom44-1100s.pdf]]</td>
<td> High pressure regulator for oxygen bottle </td>
</tr>
<tr>
- <td><a href="/HybridDataSheets/WattsPneumaticActuator.pdf" target="_top">Watts Pnuematic Actuator</a></td>
+ <td>[[Watts Pnuematic Actuator|/HybridDataSheets/WattsPneumaticActuator.pdf]]</td>
<td> Pnuematically controlled ball valve to control oxygen flow </td>
</tr>
<tr>
- <td><a href="/HybridDataSheets/ss-4p4t2valve.pdf" target="_top">Swagelok purge valve</a></td>
+ <td>[[Swagelok purge valve|/HybridDataSheets/ss-4p4t2valve.pdf]]</td>
<td> Manual line purge valve </td>
</tr>
<tr>
- <td><a href="/HybridDataSheets/Barksdale405.pdf" target="_top">Barksdale 405</a></td>
+ <td>[[Barksdale 405|/HybridDataSheets/Barksdale405.pdf]]</td>
<td colspan=2> 0-2000 psi 4-20mA pressure transducer </td>
</tr>
</table>
diff --git a/HybridFireControl.mdwn b/HybridFireControl.mdwn
index 47c12ee..99a22a3 100644
--- a/HybridFireControl.mdwn
+++ b/HybridFireControl.mdwn
@@ -17,4 +17,4 @@ Upcoming version changes
- Logging. Sequence configuration, motor details, data aquisition.
- Bug fixes. Sequences over 30 seconds
-**NEW** [LabJack DAQ system](/LabJack)
+**NEW** [[LabJack DAQ system|/LabJack]]
diff --git a/HybridNozzle.mdwn b/HybridNozzle.mdwn
index a378dd1..2646de1 100644
--- a/HybridNozzle.mdwn
+++ b/HybridNozzle.mdwn
@@ -14,7 +14,7 @@ The attached document details the calculations used to design the nozzle.
<table border=1 cellpadding=0 cellspacing=0>
<tr>
- <td><a href="/HybridNozzle/Hybridnozzledesign.pdf" target="_top">GOX HybridNozzle v1.0</a></td>
+ <td>[[GOX HybridNozzle v1.0|/HybridNozzle/Hybridnozzledesign.pdf]]</td>
<td> Preliminary nozzle design </td>
</tr>
</table>
diff --git a/HybridPlaces.mdwn b/HybridPlaces.mdwn
index 52c253a..0f0af55 100644
--- a/HybridPlaces.mdwn
+++ b/HybridPlaces.mdwn
@@ -1 +1 @@
-[Static test site Rendezvous](/BartonDirections)
+[[Static test site Rendezvous|/BartonDirections]]
diff --git a/HybridSolenoids.mdwn b/HybridSolenoids.mdwn
index d8fde69..5d6afcc 100644
--- a/HybridSolenoids.mdwn
+++ b/HybridSolenoids.mdwn
@@ -10,11 +10,11 @@ Currently we are using two solenoids and one pneumatic actuator to control the m
- One for switching on and off the nitrogen to operate the pneumatic actuator for the oxygen supply
- One actuator for turning on the oxygen supply ball valve
-The nitrogen purge solenoid is a [Spartan Scientific 3823 Series](/HybridDataSheets/ser-3823.pdf)
+The nitrogen purge solenoid is a [[Spartan Scientific 3823 Series|/HybridDataSheets/ser-3823.pdf]]
The acuator solenoid is a [Predyne 12vdc solenoid ](http://www.predyne.com/series/d.asp)
-The pneumatic actuator is a [Watts PA180 Actuator](/HybridDataSheets/WattsPneumaticActuator.pdf)
+The pneumatic actuator is a [[Watts PA180 Actuator|/HybridDataSheets/WattsPneumaticActuator.pdf]]
[[solenoids3.jpg]]
@@ -22,4 +22,4 @@ The pneumatic actuator is a [Watts PA180 Actuator](/HybridDataSheets/WattsPneuma
[[Solenoid Switching Diagram |HybridSolenoidSwitch]]( not used due to high oxygen pressures needed)
-The main GOX feed solenoid is a [Parker '42 series' solenoid](/HybridDataSheets/0600P-42LP.pdf)( not used due to high oxygen pressures needed)
+The main GOX feed solenoid is a [[Parker '42 series' solenoid|/HybridDataSheets/0600P-42LP.pdf]]( not used due to high oxygen pressures needed)
diff --git a/IgnitionRing.mdwn b/IgnitionRing.mdwn
index 1d2bf5f..cea003e 100644
--- a/IgnitionRing.mdwn
+++ b/IgnitionRing.mdwn
@@ -3,7 +3,7 @@
----
<div>
- <center><img alt="ignitionringtest.jpg" height=199 src="/news/2003-12-21/ignitionringtest.jpg" width=640></center>
+ <center>[[/news/2003-12-21/ignitionringtest.jpg]]</center>
</div>
To insure that the motor starts under the high velocity flow of oxygen at Tminus 0 seconds, a solid propellant ring is lit 2 seconds prior to the initiation of oxygen flow.
@@ -12,6 +12,6 @@ The solid propellant ignition ring is made from a commercially available solid p
The fuel grain is cut into 0.25" disks and then embedded into the paraffin fuel grain at the oxygen injector side.
-[View movie of ignition ring test](/news/2003-12-21/ignitionring.mpg)
+[[View movie of ignition ring test|/news/2003-12-21/ignitionring.mpg]]
**Additional Information**
diff --git a/Introduction.mdwn b/Introduction.mdwn
index 761718a..07ac58a 100644
--- a/Introduction.mdwn
+++ b/Introduction.mdwn
@@ -41,7 +41,7 @@
</tr>
<tr>
<td>[[AvionicsTeamHome]]: Avionics are the computer &quot;brains&quot; of the rocket. We&#39;re trying to be one of the first amateur groups in the world to make an actively guided rocket &ndash; i.e., a rocket that is autonomously guided by an onboard computer. Technically speaking, we&#39;re hoping to build an amateur DGPS-aided inertial navigation system. </td>
- <td><img align="center" height=319 src="/psas/Current_project/LV-1/Payload/Resources/FC_Intro.jpg" width=320></td>
+ <td>[[/psas/Current_project/LV-1/Payload/Resources/FC_Intro.jpg]]</td>
</tr>
<tr>
<td>
diff --git a/LV2AirframeArchive.mdwn b/LV2AirframeArchive.mdwn
index f297fb8..4ac4fc2 100644
--- a/LV2AirframeArchive.mdwn
+++ b/LV2AirframeArchive.mdwn
@@ -8,7 +8,7 @@
<tr>
<td colspan=3>
<div>
- <center><img border=0 height=65 src="/AirframeTeamHome/airframe.gif" width=300></center>
+ <center>[[/AirframeTeamHome/airframe.gif]]</center>
</div>
</td>
</tr>
@@ -41,7 +41,7 @@
</td>
<td width=200>
<ul>
- <li style="letter-spacing: 0.1pc"><font size="1.2pc"><font face="Garamond"><font color="#2a5c12" face="Arial,Helvetica,Geneva,Swiss,SunSans-Regular" size=2> <a href="AirframeWorkProgress">Work Progress</a></font></font></font></li>
+ <li style="letter-spacing: 0.1pc"><font size="1.2pc"><font face="Garamond"><font color="#2a5c12" face="Arial,Helvetica,Geneva,Swiss,SunSans-Regular" size=2> [[Work Progress|AirframeWorkProgress]]</font></font></font></li>
</ul>
<p style="letter-spacing: 0.1pc"><font size="1.2pc"><font face="Garamond"><font size=2></font></font></font></p>
<ul>
diff --git a/LV2b_Conceptual_Design.mdwn b/LV2b_Conceptual_Design.mdwn
index 89e789c..1993b0a 100644
--- a/LV2b_Conceptual_Design.mdwn
+++ b/LV2b_Conceptual_Design.mdwn
@@ -2,19 +2,19 @@
The current nosecone separation system design will consist of a gas-tight parachute container and a conventionally sleeved nosecone. A cold gas generator could be located below the parachutes, which simplifies the wiring, plumbing, and nosecone interface considerably. A cold gas generator could be purchased from a third party such as Aerocon. <http://www.aeroconsystems.com/RTM/index.htm> A sample model drawn in solidworks is shown below.
-![](separation_design.jpg)
+[[separation_design.jpg]]
**Fin Design**
The current fin design involves clamping four fins equally spaced at the bottom of the propulsion module. By tightening the fasteners on each fin, a compression fit is obtained.A sample model drawn in solidworks is shown below.
-![](fin_design.jpg)
+[[fin_design.jpg]]
**Module Coupling Design**
The module coupling design consists of a coupler, roughly 2 inches in length, tightly fitting within the ends of the modules. A series of fasteners will sufficiently attach the coupler to the module. A sample model drawn in solidworks is shown below.
-![](coupler_design.jpg)
+[[coupler_design.jpg]]
**Materials**
diff --git a/LV2cFinClamps.mdwn b/LV2cFinClamps.mdwn
index e54a225..bfa1961 100644
--- a/LV2cFinClamps.mdwn
+++ b/LV2cFinClamps.mdwn
@@ -4,6 +4,6 @@ Fin clamps allow us to use simple flat fins and attach them securely to any roun
The drawing here shows the old fin shape from LV2b. The next generation fin shape will no doubt be slightly different. The drawing also shows internal fin clamps. We considered these because they are aerodynamically cleaner and pick up some flutter resistance by passing through the outer fairing. Currently exterior fin clamps seem like a better idea because they are much easier to take on and off, align, etc. The aerodynamic drawbacks of external clamps are not too severe.
-![](LV2c-Fin-preliminary.png)
+[[LV2c-Fin-preliminary.png]]
The drawing shown is available in [[PDF|/LV2cFinClamps/LV2c-Fin-preliminary.pdf]] format as well in [[source|/LV2cFinClamps/LV2c-Fin-preliminary.dxf]] (DXF) format.
diff --git a/LV2cModule.mdwn b/LV2cModule.mdwn
index 2f237e5..5af51db 100644
--- a/LV2cModule.mdwn
+++ b/LV2cModule.mdwn
@@ -2,6 +2,6 @@
The backbone of the airframe consists of modular aluminum sections screwed together. Each module is tubular with 0, 2, or 4 oval cutouts that serve to lighten the structure and provide access to the module's interior.
-![](Module-LV2c-1.2.png)
+[[Module-LV2c-1.2.png]]
The drawing shown is available in [[PDF|/LV2cModule/Module-LV2c-1.2.pdf]] format as well in [[source|/LV2cModule/Module-LV2c-1.2.dxf]] (DXF) format.
diff --git a/LV2cMotorCasing.mdwn b/LV2cMotorCasing.mdwn
index 74706a9..0fd78a9 100644
--- a/LV2cMotorCasing.mdwn
+++ b/LV2cMotorCasing.mdwn
@@ -6,6 +6,6 @@ Our motor casing is made by Sublight Aerospace LLC, a company co-founded by one
Total casing weight empty 7.25 +/- 0.1 pounds.
-![](LV2c-MotorCasing.png)
+[[LV2c-MotorCasing.png]]
The drawing shown is available in [[PDF|/LV2cMotorCasing/LV2c-MotorCasing.pdf]] format as well in [[source|/LV2cMotorCasing/LV2c-MotorCasing.dxf]] (DXF) format.
diff --git a/LV2cNosecone.mdwn b/LV2cNosecone.mdwn
index f221de8..cd5e928 100644
--- a/LV2cNosecone.mdwn
+++ b/LV2cNosecone.mdwn
@@ -4,10 +4,10 @@ The nosecone for LV2c, is an optimal design based on the Parker profile. Our par
The plug designs for the nosecone are shown below.
-![](nosecone-LV2c-M3-7:1.v2-Cone.png)
+[[nosecone-LV2c-M3-7:1.v2-Cone.png]]
The apex of the nosecone on LV2c is removable and interchangeable. It threads into the nosecone base via standard c-mount thread. The apex uses a straight taper with a rounded tip rather than following the optimal profile. The drag difference is negligible because the of the small radius.
-![](nosecone-LV2c-M3-7:1.v2-Tip.png)
+[[nosecone-LV2c-M3-7:1.v2-Tip.png]]
The source drawing for the images shown above is available in [[PDF|/LV2cNosecone/nosecone-LV2c-M3-7:1.v2.pdf]] format as well in [[source|/LV2cNosecone/nosecone-LV2c-M3-7:1.v2.dxf]] (DXF) format.
diff --git a/LvTwoCompactFlash.mdwn b/LvTwoCompactFlash.mdwn
index d51a7c7..5929738 100644
--- a/LvTwoCompactFlash.mdwn
+++ b/LvTwoCompactFlash.mdwn
@@ -10,7 +10,7 @@ We used [Tucson Area Packet Radio's](http://www.tapr.org/) [CompactFlash Type II
To mount it to the FC's PC104 stack, we used PCB material (FR-4 sandwiched by copper) and drilled 8 holes (4 for the PC104 stack, 4 for the CF adapter). We aligned the CF card such that during launch the CF card would be pushed down into it's socket. Here's a drawing of the adapter board, although note there's a [PDF file available](/LvTwoCompactFlash/SmallAdapterDrawing.png):
-<center><img alt="LvTwoCompactFlash?rev=1.1&amp;filename=SmallAdapterDrawing.png" src="/LvTwoCompactFlash/SmallAdapterDrawing.png"></center>
+<center>[[LvTwoCompactFlash?rev=1.1&amp;filename=SmallAdapterDrawing.png|/LvTwoCompactFlash/SmallAdapterDrawing.png]]</center>
Since the FC board has a 2mm 44pin connector (the kind used for 2.5" drives on laptops) which includes power, we modified the CF adapter board by:
@@ -19,6 +19,6 @@ Since the FC board has a 2mm 44pin connector (the kind used for 2.5" drives on l
- Replacing the Master Select 0.1" jumper with a hardwired (soldered) jumper,
- Replacing the electrolytic power supply filter cap with a smaller Tantalum one.
-<center><img alt="LvTwoCompactFlash?rev=1.2&amp;filename=UnmodifiedCFA.jpg" src="/LvTwoCompactFlash/UnmodifiedCFA.jpg"> <img alt="LvTwoCompactFlash?rev=1.2&amp;filename=ModifiedCFA.jpg" src="/LvTwoCompactFlash/ModifiedCFA.jpg"></center>
+<center>[[LvTwoCompactFlash?rev=1.2&amp;filename=UnmodifiedCFA.jpg|/LvTwoCompactFlash/UnmodifiedCFA.jpg]] [[LvTwoCompactFlash?rev=1.2&amp;filename=ModifiedCFA.jpg|/LvTwoCompactFlash/ModifiedCFA.jpg]]</center>
Although this is a workable solution, we'll probably want to roll our own CompactFlash carrier to PC104 adapter in the future: we could use a locking CF connector, save weight in fasteners and PCB material, and possibly mount the 2mm cable directly to the PCB (thus removing one connector, which seems to be a good thing for aerospace applications).
diff --git a/MeteringOrifice.mdwn b/MeteringOrifice.mdwn
index ae90781..1efa383 100644
--- a/MeteringOrifice.mdwn
+++ b/MeteringOrifice.mdwn
@@ -10,6 +10,6 @@ The attached document shows compressible flow calculations used to find orifice
The flat plate orifice was made from a 0.125" aluminum disk and was placed in line with the oxygen feed system immediately after the check valve.
-[Calculations for metering orifice](/WaxPlumbing/2003test-orifice.pdf)<br />[[Metering orifice validation|MeteringOrificeBarrelTest]] (The barrel test)<br />[[Motor performance projections for .089" orifice|MeteringOrifice/meteringtestl012605.pdf]]
+[[Calculations for metering orifice|/WaxPlumbing/2003test-orifice.pdf]]<br />[[Metering orifice validation|MeteringOrificeBarrelTest]] (The barrel test)<br />[[Motor performance projections for .089" orifice|MeteringOrifice/meteringtestl012605.pdf]]
<br />[[orifices.jpg]]
diff --git a/NodeMicrocontrollerSearch/STMDiscussion.mdwn b/NodeMicrocontrollerSearch/STMDiscussion.mdwn
index 2c908a4..1d36e3a 100644
--- a/NodeMicrocontrollerSearch/STMDiscussion.mdwn
+++ b/NodeMicrocontrollerSearch/STMDiscussion.mdwn
@@ -14,7 +14,7 @@ The chip requires a precise 48MHz clock. There's basically two choices for gener
Now, onto PLL1, which controls the main core frequency. It can multiply by 12, 16, 20, or 24. It can also divide by any number from 1 to 7. The input to PLL1, CLK, can be divided by one or two before it even reaches PLL1. The output from PLL1 can be divided by 1, 2, 4, or 8 before it gets to the core, memories, and peripherals. We want to get the max frequency we can get out of the chip (66MHz). There might be some wait state issues with memory, but we'll ignore that for now.
-![](NodeMicrocontrollerSearch/STMDiscussion/clocks.png)
+[[NodeMicrocontrollerSearch/STMDiscussion/clocks.png]]
Core frequency equation:
@@ -38,7 +38,7 @@ To generate the two required clocks, we end up using both PLLs. It would be grea
Tim thinks the internal voltage regulator isn't going to be as efficient as our external switching power supply. The datasheet states you can turn off the internal voltage regulator, but it's not as simple as it seems.
-![](NodeMicrocontrollerSearch/STMDiscussion/power.png)
+[[NodeMicrocontrollerSearch/STMDiscussion/power.png]]
V18BKP is where we would attach our 1.8V external power supply. V18 is supposed to be an external 1.8V reference, and it's "not supported" to hook the external power supply to it. Looking at the diagram, it appears that when the chip enters standby mode, V18BKP is disconnected from the core and the Low Power Voltage Regulator takes over. We really don't want that behavior.
diff --git a/ProjectLV2AirframeJigs.mdwn b/ProjectLV2AirframeJigs.mdwn
index c475336..a763f6f 100644
--- a/ProjectLV2AirframeJigs.mdwn
+++ b/ProjectLV2AirframeJigs.mdwn
@@ -19,14 +19,14 @@ Slip fit (Type-SF) drill bushings can be changed quickly, allowing operations us
The drill jig is also designed to hold and align the outer skin while the holes for the skin-attaching screws are drilled.
- Jig-Clamp drawings
- - [JigClamps-1.3.dxf](/ProjectLV2AirframeJigs/JigClamps-1.3.dxf) (43k) or [JigClamps-1.3.pdf](/ProjectLV2AirframeJigs/JigClamps-1.3.pdf) (246k)
+ - [[/ProjectLV2AirframeJigs/JigClamps-1.3.dxf]] (43k) or [[/ProjectLV2AirframeJigs/JigClamps-1.3.pdf]] (246k)
- Jig-Plate drawings
- - [JigPlate-1.3.dxf](/ProjectLV2AirframeJigs/JigPlate-1.3.dxf) (13k) or [JigPlate-1.3.pdf](/ProjectLV2AirframeJigs/JigPlate-1.3.pdf) (200k)
+ - [[/ProjectLV2AirframeJigs/JigPlate-1.3.dxf]] (13k) or [[/ProjectLV2AirframeJigs/JigPlate-1.3.pdf]] (200k)
Because commercial clamps that could easily hold the modules in the jigs have been hard to get, we could make our own hold-down clamps. These would attach to the jigs using a single 1/4-20 thumb screw.
- Jig-HoldDown drawings
- - [JigHoldDowns-1.4.dxf](/ProjectLV2AirframeJigs/JigHoldDowns-1.4.dxf) (11k) or [JigHoldDowns-1.4.pdf](/ProjectLV2AirframeJigs/JigHoldDowns-1.4.pdf) (84k)
+ - [[/ProjectLV2AirframeJigs/JigHoldDowns-1.4.dxf]] (11k) or [[/ProjectLV2AirframeJigs/JigHoldDowns-1.4.pdf]] (84k)
**Fin Jig for LV2 Fin Canister**
@@ -37,8 +37,8 @@ The propose design is very similar to the drill jig above. Instead of a module,
The holding mechanism for the fin can is sectioned into two parts. This supposedly means it's easier to make, but the piece could certainly be made as a single unit. The two pieces are the tube clamp, which holds the actual fin can, and the bracket that connects the tube clamp to the fin jig plate.
- Fin Tube Clamp drawings
- - [FinTubeClamp-1.1.dxf](/ProjectLV2AirframeJigs/FinTubeClamp-1.1.dxf) (27k) or [FinTubeClamp-1.1.pdf](/ProjectLV2AirframeJigs/FinTubeClamp-1.1.pdf) (210k)
+ - [[/ProjectLV2AirframeJigs/FinTubeClamp-1.1.dxf]] (27k) or [[/ProjectLV2AirframeJigs/FinTubeClamp-1.1.pdf]] (210k)
- Fin Jig Bracket drawings
- - [FinBracket-1.0.dxf](/ProjectLV2AirframeJigs/FinBracket-1.0.dxf) (9k) or [FinBracket-1.0.pdf](/ProjectLV2AirframeJigs/FinBracket-1.0.pdf) (89k)
+ - [[/ProjectLV2AirframeJigs/FinBracket-1.0.dxf]] (9k) or [[/ProjectLV2AirframeJigs/FinBracket-1.0.pdf]] (89k)
Some of these drawings are in DXF format. Many CAD programs can read DXF files. One open source CAD program that can is available at <http://www.qcad.org>
diff --git a/ProjectLV2FinDesignReferences.mdwn b/ProjectLV2FinDesignReferences.mdwn
index f8ba3f6..37f95a3 100644
--- a/ProjectLV2FinDesignReferences.mdwn
+++ b/ProjectLV2FinDesignReferences.mdwn
@@ -4,7 +4,7 @@
- James S. Barrowman &amp; Judith A. Barrowman,<br />"THE THEORETICAL PREDICTION OF THE CENTER OF PRESSURE"<br />NARAM-8 R&amp;D Project, August 18, 1966<br />Available here: [http://www.apogeerockets.com/education/downloads/Barrowman\_report.pdf](http://www.apogeerockets.com/education/downloads/Barrowman_report.pdf)<br />This is the seminal paper on model rocket stability. The derivation is fairly clear. The methods presented are based on linearized subsonic flow theory.
-- James S. Barrowman<br />CALCULATING THE CENTER OF PRESSURE OF A MODEL ROCKET<br />Centuri Engineering Company, TECHNICAL INFORMATION REPORT 33 (TIR-33)<br />Available from several sources on the web. Here as a pdf file: [tir-33.zip](/ProjectLV2FinDesignReferences/tir-33.zip) (4.3M)<br />Contains worked numerical examples of the Barrowman equations.
+- James S. Barrowman<br />CALCULATING THE CENTER OF PRESSURE OF A MODEL ROCKET<br />Centuri Engineering Company, TECHNICAL INFORMATION REPORT 33 (TIR-33)<br />Available from several sources on the web. Here as a pdf file: [[/ProjectLV2FinDesignReferences/tir-33.zip]] (4.3M)<br />Contains worked numerical examples of the Barrowman equations.
Fin rigidity is also important:
@@ -16,7 +16,7 @@ Here are a few papers commenting on the original Barrowman theory:
- Robert Galejs<br />"Wind Instability, WHAT BARROWMAN LEFT OUT"<br />Sentinel 39<br /><http://www.argoshpr.ch/PDF/sentinel39-galejs.pdf><br />Adds terms to the Barrowman equations to account for body lift.
-- Max Feil<br />"Center of Gravity &amp; Pitch Stability"<br />"From The Aeronautics File" Topic #2<br /><http://www.mat.uc.pt/~pedro/ncientificos/artigos/aeronauticsfile2.ps><br /> Also available as a pdf: [aeronauticsfile2.pdf](/ProjectLV2FinDesignReferences/aeronauticsfile2.pdf) (22k)<br />Presents a few basics. Gives a fairly good explanation of the "Center of Pressure" concept.
+- Max Feil<br />"Center of Gravity &amp; Pitch Stability"<br />"From The Aeronautics File" Topic #2<br /><http://www.mat.uc.pt/~pedro/ncientificos/artigos/aeronauticsfile2.ps><br /> Also available as a pdf: [[/ProjectLV2FinDesignReferences/aeronauticsfile2.pdf]] (22k)<br />Presents a few basics. Gives a fairly good explanation of the "Center of Pressure" concept.
The Barrowman equations start to break down around Mach 0.7 . To accurately model higher speeds requires a more laborious approach. Here is a starting point:
diff --git a/ProjectLV2MotorCoupler.mdwn b/ProjectLV2MotorCoupler.mdwn
index 7d5c1c5..0abaa2f 100644
--- a/ProjectLV2MotorCoupler.mdwn
+++ b/ProjectLV2MotorCoupler.mdwn
@@ -4,7 +4,7 @@ In LV2 we have adopted a modular approach to the upper sections of the vehicle,
This page documents the interfacing unit that connects the motor casing to the furthest aft modular unit, which is by design the avionics module. We call the interface the "Motor to Avionics Coupler" or simply the "Motor Coupler". The particular piece of hardware described here is specific to \*N\* size and smaller motors. We anticipate the need for a different interface when we move to \*P\* and larger motors.
-![](Motor_Avionics_Coupler.png)
+[[Motor_Avionics_Coupler.png]]
The coupler is a simple series of concentric rings machined from a solid disk of ordinary 6061-T6 aluminum alloy.
diff --git a/PrototypeMotorParameters.mdwn b/PrototypeMotorParameters.mdwn
index 7e81714..dccbe4e 100644
--- a/PrototypeMotorParameters.mdwn
+++ b/PrototypeMotorParameters.mdwn
@@ -8,7 +8,7 @@ The following design parameters where selected to begin the process of evaluatin
<table border=1 cellpadding=0 cellspacing=0>
<tr>
- <td><a href="/PrototypeMotorParameters/gox_paraffin.xls" target="_top">GOX/Paraffin Spreat Sheet</a></td>
+ <td>[[GOX/Paraffin Spreat Sheet|/PrototypeMotorParameters/gox_paraffin.xls]]</td>
<td> Initial Excel spread sheet used to calculate fuel grain dimensions </td>
</tr>
</table>
diff --git a/PsasLogo.mdwn b/PsasLogo.mdwn
index eb83d04..9413be0 100644
--- a/PsasLogo.mdwn
+++ b/PsasLogo.mdwn
@@ -4,26 +4,26 @@ As of August 2, 2006, PSAS has a new official logo. [[FrankMatthews]] is still t
## Banner
-![](Logo04BCombo_banner.jpg)
+[[Logo04BCombo_banner.jpg]]
## Business Cards
-![](Logo04BCombo_business-card.jpg)
+[[Logo04BCombo_business-card.jpg]]
## Letter head
-![](Logo04BCombo_letterhead.jpg)
+[[Logo04BCombo_letterhead.jpg]]
## T-shirts
-![](Logo04BCombo_tshirt.jpg)
+[[Logo04BCombo_tshirt.jpg]]
## Simple Logos
-Monochrome and flattened-color logos. ![](Logo04BCombo_monocrome-flattened.jpg)
+Monochrome and flattened-color logos. [[Logo04BCombo_monocrome-flattened.jpg]]
# Old PSAS Logo
Here's a PDF (vector drawing) of the old PSAS logo done in black and white with text outlines (no font): [[psas_logo_vector_bw_outlines.pdf]]
-Here's a PNG (giant, ~ 3300 x 800) of the old PSAS logo: ![](psas_logo_vector_bw_outlines_2.PNG)
+Here's a PNG (giant, ~ 3300 x 800) of the old PSAS logo: [[psas_logo_vector_bw_outlines_2.PNG]]
diff --git a/Q2IgniterEvaluation.mdwn b/Q2IgniterEvaluation.mdwn
index 89076c9..fdd5161 100644
--- a/Q2IgniterEvaluation.mdwn
+++ b/Q2IgniterEvaluation.mdwn
@@ -10,7 +10,7 @@ The firing energy and fusing energy of the "Quest Q2 Model Rocket Igniter" elect
## Preliminaries
-![](Quest_small.jpg)
+[[Quest_small.jpg]]
Fig.1
@@ -117,7 +117,7 @@ Table 1
There is a surprisingly large variation in resistance. Furthermore, some igniters (such as #4) displayed a resistance that seemed to vary if the igniter was flexed slightly. Despite this, all the igniters tested (including #4) fired at approximately the same energy. For applications where reliability is important, Q2 igniters need to be pre-screened for DC resistance. Only igniters in the 1-3 Ω range whose resistance is insensitive to mechanical agitation should be used.
-The test firing circuit we used is shown in figure 2. ![](TestCircuit.png)
+The test firing circuit we used is shown in figure 2. [[TestCircuit.png]]
Fig. 2
@@ -135,7 +135,7 @@ To verify the circuit was operating correctly, the first test used a 1 Ω resist
For test 2 (the first firing test) the power supply was adjusted to 6V and the pulse generator set for 250 ms. The match fired, but the bridge wire was left apparently intact. The image captured from the scope is shown in figure 3.
-![](Test2.jpg)
+[[Test2.jpg]]
Fig. 3
@@ -328,7 +328,7 @@ To demonstrate that this theory is useful for the Q2's we increased the supply v
To verify proper circuit operation at 70 V another run was made with the 1 Ω resistor as a dummy igniter. The captured waveforms from this test are shown below
-![](Test6.jpg)
+[[Test6.jpg]]
Fig. 4
@@ -342,7 +342,7 @@ For this test we used igniter #10. The pulse duration was 1 ms. The igniter fire
To measure the minimum firing energy at 70 V we loaded igniter #11 and tried successively longer pulses starting from 50 μs. At 250 μs we saw a puff of smoke. At 500 μs the igniter fired. The sparkler pattern of the ignition was visually similar to the low voltage tests. The bridge wire remained un-fused.
-![](Test8.jpg)
+[[Test8.jpg]]
Fig. 5
@@ -358,7 +358,7 @@ Igniter #8 was fired with a 5 ms pulse. The bridge wire did fuse, but no capture
Finally, igniter #9 was fired and a capture made, see below
-![](Test11.jpg)
+[[Test11.jpg]]
Fig. 6
diff --git a/RotaryReturn.mdwn b/RotaryReturn.mdwn
index 94a6d27..409abdd 100644
--- a/RotaryReturn.mdwn
+++ b/RotaryReturn.mdwn
@@ -1,6 +1,6 @@
-The issue of the [watt rotary actuator](/HybridDataSheets/WattsPneumaticActuator.pdf) not closing under the 1000 psi oxygen stream due to insufficient return spring strength was corrected by adding an 80psi nitrogen line to the outlet port on the return side of the spring/piston assembly. This would essentially assist the spring in closing the ball valve.
+The issue of the [[watt rotary actuator|/HybridDataSheets/WattsPneumaticActuator.pdf]] not closing under the 1000 psi oxygen stream due to insufficient return spring strength was corrected by adding an 80psi nitrogen line to the outlet port on the return side of the spring/piston assembly. This would essentially assist the spring in closing the ball valve.
-Originally only one N2 line, controlled by a single solenoid, was used to open the rotary actuator which opened the ball valve. Now that we have two N2 lines but have not increased the digital output lines on our controller (or changed the software) we needed to implemented a [4-way solenoid valve](/HybridDataSheets/0600P-42LP.pdf). This valve will either supply N2 to open or N2 to close side of the ball valve depending on if the solenoid is energized or not.
+Originally only one N2 line, controlled by a single solenoid, was used to open the rotary actuator which opened the ball valve. Now that we have two N2 lines but have not increased the digital output lines on our controller (or changed the software) we needed to implemented a [[4-way solenoid valve|/HybridDataSheets/0600P-42LP.pdf]]. This valve will either supply N2 to open or N2 to close side of the ball valve depending on if the solenoid is energized or not.
This fix unfortunately is not all that pretty. We only had a 110VAC 4 way solenoid where as the rest of our system is 12VDC. To get around this issue we will use a [12VDC to 110VAC inverter](http://www.linksys.com/products/product.asp?prid=95&scid=46) to power the solenoid. The inverter will get its 12VDC from the control/driver board line that we previously used to drive the 12VDC solenoid that opened the ball valve.
diff --git a/SmartBatteriesLv2.mdwn b/SmartBatteriesLv2.mdwn
index 96bf0d4..39aabf1 100644
--- a/SmartBatteriesLv2.mdwn
+++ b/SmartBatteriesLv2.mdwn
@@ -23,4 +23,4 @@ Here's what we imagine it to be:
Here's the block diagram:
-<center><img alt="CanNodeSectionAppPower?rev=1.1&amp;filename=PowerNodeBlockDiagram20020310.jpg" src="/CanNodeSectionAppPower/PowerNodeBlockDiagram20020310.jpg"></center>
+<center>[[CanNodeSectionAppPower?rev=1.1&amp;filename=PowerNodeBlockDiagram20020310.jpg|/CanNodeSectionAppPower/PowerNodeBlockDiagram20020310.jpg]]</center>
diff --git a/TheoryOfOperation.mdwn b/TheoryOfOperation.mdwn
index 9b18a26..687ff97 100644
--- a/TheoryOfOperation.mdwn
+++ b/TheoryOfOperation.mdwn
@@ -6,7 +6,7 @@
**Theory of Operation:**
-The gaseous oxygen/paraffin hybrid is fairly simple. The [control](/HybridFireControl) of the static firing sequence will be done with a laptop computer running a small script that will communicate out a serial port to a ‘Flextek’ I/O board. This board is capable of data collection through several 10-bit A/D channels and the board is also capable of triggering single events through several digital output channels.
+The gaseous oxygen/paraffin hybrid is fairly simple. The [[control|/HybridFireControl]] of the static firing sequence will be done with a laptop computer running a small script that will communicate out a serial port to a ‘Flextek’ I/O board. This board is capable of data collection through several 10-bit A/D channels and the board is also capable of triggering single events through several digital output channels.
At T-2 seconds the control board will signal the igniter to start. This signal will switch an IPS5451 intelligent power switch, which will dump a larger voltage and current to the igniter from a 12v battery.
diff --git a/UplinkLv1.mdwn b/UplinkLv1.mdwn
index 6cb0ad6..7454a1e 100644
--- a/UplinkLv1.mdwn
+++ b/UplinkLv1.mdwn
@@ -4,7 +4,7 @@
The uplink system was flown on both the LV1 and LV1b flights. It is the only method of communicating up to the avionics from the ground, which is why we called it the "uplink". Originally it was intended as a way to remotely fire the pyrotechnic recovery charge from the ground (it's original name was the "Backup Separation System"); later, we added many more features and made it an integral part of the flight sequencing. For example, the Uplink now commands the Flight Computer (FC) to do self tests, arm for launch, etc.
-<center><img alt="UplinkLv1?rev=1.1&amp;filename=UplinkBlockDiagram.png" src="/UplinkLv1/UplinkBlockDiagram.png"><br> Figure 1: Block Digram of the Uplink System </center>
+<center>[[UplinkLv1?rev=1.1&amp;filename=UplinkBlockDiagram.png|/UplinkLv1/UplinkBlockDiagram.png]]<br> Figure 1: Block Digram of the Uplink System </center>
**Ground Station**
diff --git a/logo.mdwn b/logo.mdwn
index 0547a41..79af47e 100644
--- a/logo.mdwn
+++ b/logo.mdwn
@@ -1,3 +1,3 @@
New logo design.
-There are [0 attachment(s)](./logo?action=AttachFile) stored for this page.
+There are [[0 attachment(s)|./logo?action=AttachFile]] stored for this page.
diff --git a/news/2002-02-27.mdwn b/news/2002-02-27.mdwn
index 8857122..c4ce4fb 100644
--- a/news/2002-02-27.mdwn
+++ b/news/2002-02-27.mdwn
@@ -26,6 +26,6 @@
- Here's a vaguely detailed timeline of from now until launch:
-![news/2002-02-27?rev=1.2&filename=2-2002\_timeline.png](/news/2002-02-27/2-2002_timeline.png)
+[[news/2002-02-27?rev=1.2&filename=2-2002\_timeline.png|/news/2002-02-27/2-2002_timeline.png]]
[[tag admin avionics]]
diff --git a/news/2002-04-07.mdwn b/news/2002-04-07.mdwn
index ca92c04..a159646 100644
--- a/news/2002-04-07.mdwn
+++ b/news/2002-04-07.mdwn
@@ -22,7 +22,7 @@ Although it's better to sync everything together (see below), tuning the PIC's m
One solution is to replace the mechanical variable cap with the equivalent electrical version - the varicap. The varicap is a reversed biased diode whose PN junction acts like a capacitor whose capacitance is proportional to the voltage across it. So now we can tune the oscillator with a voltage, measure the DC voltage, and replace it with a few fixed resistors. Nice, but more components than the mechanical variable cap and another circuit to design.
-<center><img alt="news/2002-04-07?rev=1.1&amp;filename=CrystalCircuitAndVCXO.jpg" src="/news/2002-04-07/CrystalCircuitAndVCXO.jpg"></center>
+<center>[[news/2002-04-07?rev=1.1&amp;filename=CrystalCircuitAndVCXO.jpg|/news/2002-04-07/CrystalCircuitAndVCXO.jpg]]</center>
**Synchronizing all of the Switching Regulators:**
@@ -32,13 +32,13 @@ Note that since the buck converter chips are relaxation oscillators, you can syn
So we discussed many ways of syncing up all of the local oscillators on the board. We talked about threading a 10KHz line from the GPS to all of the CAN nodes, using a PLL and VCXO (voltage controlled crystal oscillator) to sync the 10MHz to the 10KHz, and then dividing that 10MHz down by 6 to get 1.667 MHz for the buck converter.
-<center><img alt="news/2002-04-07?rev=1.1&amp;filename=LOSyncBlockDiagram.jpg" src="/news/2002-04-07/LOSyncBlockDiagram.jpg"></center>
+<center>[[news/2002-04-07?rev=1.1&amp;filename=LOSyncBlockDiagram.jpg|/news/2002-04-07/LOSyncBlockDiagram.jpg]]</center>
This would be a GREAT solution - we'd have all the converters and processors synched to UTC (what more could you want?). However, we don't have time for anything like this - designing a circuit like this could be weeks to months if it turned out to be harder than we imagined.
So we decided on a compromise - we'd run the buck converter off of the PIC's 10MHz crystal and get a switching speed of 1.667MHz with +/- 50ppm over temperature. With this solution, we sync the buck frequency to above all of the close IF's we know about, it only requires a divide by 6 chip (probably an SO8 PIC) and we can be pretty sure that all of the converters will be running at within a few kHz of each other.
-<center><img alt="news/2002-04-07?rev=1.1&amp;filename=LOtoBuckConverter.jpg" src="/news/2002-04-07/LOtoBuckConverter.jpg"></center>
+<center>[[news/2002-04-07?rev=1.1&amp;filename=LOtoBuckConverter.jpg|/news/2002-04-07/LOtoBuckConverter.jpg]]</center>
**System Power States:**
@@ -62,7 +62,7 @@ In this mode, the power is on but everything is in low power mode. The CAN nodes
Obviously, everything is running as necessary. We can be charging the battery as we run the avionics from ground power.
-<center><img alt="news/2002-04-07?rev=1.1&amp;filename=SBSAndPowerModes.jpg" src="/news/2002-04-07/SBSAndPowerModes.jpg"></center>
+<center>[[news/2002-04-07?rev=1.1&amp;filename=SBSAndPowerModes.jpg|/news/2002-04-07/SBSAndPowerModes.jpg]]</center>
**Future Avionics Meetings:**
diff --git a/news/2003-09-21.mdwn b/news/2003-09-21.mdwn
index bc5d795..3b4bf29 100644
--- a/news/2003-09-21.mdwn
+++ b/news/2003-09-21.mdwn
@@ -134,6 +134,6 @@ Misc Links:
- [[Tee Shirt Info|TeeShirts2003]]
- [[Black Rock 2003 Logistics Page|BlackRockLogistics2003]]
-- [September 2003 BRD Range Fees](/RangeFee)
+- [[September 2003 BRD Range Fees|/RangeFee]]
[[tag event]]
diff --git a/news/2003-12-21.mdwn b/news/2003-12-21.mdwn
index b80de15..e4aaaa3 100644
--- a/news/2003-12-21.mdwn
+++ b/news/2003-12-21.mdwn
@@ -22,7 +22,7 @@ Tim B and Brian O. worked on testing the pneumatic actuator. We were able to use
**Still to do:**
-Tim committed to also (along with Evan) doing the metering orifice calculations for choked flow and will have them completed in a day or so. (Calculations are finished AFAIK: [Oxygen metering orifice design](/WaxPlumbing/2003test-orifice.pdf))
+Tim committed to also (along with Evan) doing the metering orifice calculations for choked flow and will have them completed in a day or so. (Calculations are finished AFAIK: [[Oxygen metering orifice design|/WaxPlumbing/2003test-orifice.pdf]])
Jim will work on the control script for the Flextek controller.
diff --git a/news/2003-12-31.mdwn b/news/2003-12-31.mdwn
index 79a393d..22e3062 100644
--- a/news/2003-12-31.mdwn
+++ b/news/2003-12-31.mdwn
@@ -18,9 +18,9 @@ Two tests were conducted and they both were successful in meeting our goals.
#### <a name="Movies"></a> Movies
-[Test Fire #1 (Camera 2)](/news/2003-12-31/firsthybridB.mpg)<br />[Test Fire #1 (Camera 1)](/news/2003-12-31/firsthybrid.mpg)<br />
+[[Test Fire #1 (Camera 2)|/news/2003-12-31/firsthybridB.mpg]]<br />[[Test Fire #1 (Camera 1)|/news/2003-12-31/firsthybrid.mpg]]<br />
-[Test Fire #2 (Camera 1)](/news/2003-12-31/secondhybrid.mpg)<br />[Test Fire #2 (Camera 2)](/news/2003-12-31/secondhybridB.mpg)<br />
+[[Test Fire #2 (Camera 1)|/news/2003-12-31/secondhybrid.mpg]]<br />[[Test Fire #2 (Camera 2)|/news/2003-12-31/secondhybridB.mpg]]<br />
**The Tests:**
diff --git a/news/2004-04-17.mdwn b/news/2004-04-17.mdwn
index 004abc9..144d958 100644
--- a/news/2004-04-17.mdwn
+++ b/news/2004-04-17.mdwn
@@ -15,7 +15,7 @@
We discussed sensing and data acquisition on the new motor test stand. It was decided to do the following items to start:
- Measure two pressures one immediately upstream and one immediately downstream of the metering orifice.
-- Use a matched set of [0-2000 psi transducers](/HybridDataSheets/Barksdale405.pdf) with 12VDC excitation voltage and 4-20 mA output.
+- Use a matched set of [[0-2000 psi transducers|/HybridDataSheets/Barksdale405.pdf]] with 12VDC excitation voltage and 4-20 mA output.
- If successful and pressures are in the expected range we will later switch the downstream sensor to a 0-500 psi transducer, to get better resolution.
- Measure force generated by motor with commercially available load cell.
diff --git a/news/2004-05-15.mdwn b/news/2004-05-15.mdwn
index 3ed5389..8c2a537 100644
--- a/news/2004-05-15.mdwn
+++ b/news/2004-05-15.mdwn
@@ -10,9 +10,9 @@
**What we did today:**
-We got the dead weight tester running and were able to get [calibration curves](/news/2004-05-15/Barksdale051504.xls) for both of the [Barksdale 4-20 mA](/HybridDataSheets/Barksdale405.pdf) output pressure transducers. Both sensors behave linearly and have good repeatability. We were unable to test for hysteresis due to the nature of how the dead weight tester operates.
+We got the dead weight tester running and were able to get [[calibration curves|/news/2004-05-15/Barksdale051504.xls]] for both of the [[Barksdale 4-20 mA|/HybridDataSheets/Barksdale405.pdf]] output pressure transducers. Both sensors behave linearly and have good repeatability. We were unable to test for hysteresis due to the nature of how the dead weight tester operates.
-A schematic of the signal conditioning can be found [here](/news/2004-05-15/transducerwiring.jpg). The code we used to capture the data can be found [here](/news/2004-05-15/PressureTransducerCapture.vi).
+A schematic of the signal conditioning can be found [here](/news/2004-05-15/transducerwiring.jpg). The code we used to capture the data can be found [[here|/news/2004-05-15/PressureTransducerCapture.vi]].
With this information we will now be able to write a program in Labview that will allow us to monitor the upstream pressure relative the metering orifice and also the downstream pressure. Knowing these two values we will be able to verify that we are maintaining choked flow at the metering orifice thereby insuring a known volumetric flow rate into the combustion chamber.
@@ -80,6 +80,6 @@ We will meet again in two weeks and pour a new batch of paraffin fuel grain. And
**Of Interest:**
-[Paraffin article from "Graduating Engineer &amp; Computer Careers"](/news/2004-05-15/paraffin.pdf)
+[[Paraffin article from "Graduating Engineer &amp; Computer Careers"|/news/2004-05-15/paraffin.pdf]]
[[tag propulsion]]
diff --git a/news/2004-06-26.mdwn b/news/2004-06-26.mdwn
index fe7b6a6..bc5d792 100644
--- a/news/2004-06-26.mdwn
+++ b/news/2004-06-26.mdwn
@@ -12,9 +12,9 @@
The goal for the meeting today was to pour the paraffin fuel grains with the regression rate sensors embedded in them for the next static test fire.
-There are two proposed types of [regression rate sensors](/HybridRegressionRate) that we have come up with. Since we had a head start on the construction of one of the types and since it has been tested with the DAQ system we have chosen to implement the discrete resistor based sensor for the upcoming firing and then wait till the next firing to try the carbon/lace sensor. That way both will be evaluated in a fairly large batch of motor firings.
+There are two proposed types of [[regression rate sensors|/HybridRegressionRate]] that we have come up with. Since we had a head start on the construction of one of the types and since it has been tested with the DAQ system we have chosen to implement the discrete resistor based sensor for the upcoming firing and then wait till the next firing to try the carbon/lace sensor. That way both will be evaluated in a fairly large batch of motor firings.
-Eric and Michael worked on building up the 15 discrete resistor sensors (3 per motor, forward, mid and aft, for a total of 5 motors). Eric also collected all the necessary components (minus the Bendix connector) for the [load cell amplifier](/LoadCellAmp) circuit that Tim designed.
+Eric and Michael worked on building up the 15 discrete resistor sensors (3 per motor, forward, mid and aft, for a total of 5 motors). Eric also collected all the necessary components (minus the Bendix connector) for the [[load cell amplifier|/LoadCellAmp]] circuit that Tim designed.
Tim built up 10 carbon/lace sensors for testing and implementation on the next round of firings, which will hopefully happen soon after the upcoming batch.
@@ -67,7 +67,7 @@ Tentatively planning next static test fire for July 10th.
</div>
<div>
- <center><strong>Carbon/Lace Regression Rate Sensor</strong><p><a alt="ProtoLaceRegressionSensorsmall.jpg" href="/HybridRegressionRate/ProtoLaceRegressionSensor.jpg"> <img alt="ProtoLaceRegressionSensorsmall.jpg" height=234 src="/HybridRegressionRate/ProtoLaceRegressionSensor.jpg" width=352> </a></p>
+ <center><strong>Carbon/Lace Regression Rate Sensor</strong><p><a alt="ProtoLaceRegressionSensorsmall.jpg" href="/HybridRegressionRate/ProtoLaceRegressionSensor.jpg"> [[ProtoLaceRegressionSensorsmall.jpg|/HybridRegressionRate/ProtoLaceRegressionSensor.jpg]] </a></p>
</center>
</div>
diff --git a/news/2005-10-25.mdwn b/news/2005-10-25.mdwn
index 62f0395..1c9dcec 100644
--- a/news/2005-10-25.mdwn
+++ b/news/2005-10-25.mdwn
@@ -2,6 +2,6 @@ Attending: [[JameySharp]], [[SarahBailey]], [[AndrewGreenberg]], ??
Lots of pictures! Someone annotate these.
-![](PPC.jpg) ![](avionics.jpg) ![](avionics_more.jpg)
+[[PPC.jpg]] [[avionics.jpg]] [[avionics_more.jpg]]
[[tag avionics]]
diff --git a/news/2005-11-30.mdwn b/news/2005-11-30.mdwn
index 4bbbbdd..996571a 100644
--- a/news/2005-11-30.mdwn
+++ b/news/2005-11-30.mdwn
@@ -2,8 +2,8 @@ Attending: [[JameySharp]], [[SarahBailey]], [[AndrewGreenberg]], ??
Lots of pictures! Someone annotate these.
-![](avionics_abstraction_layers.jpg)
+[[avionics_abstraction_layers.jpg]]
-![](avionics_more2.jpg)
+[[avionics_more2.jpg]]
[[tag avionics]]
diff --git a/news/2006-02-06.mdwn b/news/2006-02-06.mdwn
index f0c7a10..bf9ba8e 100644
--- a/news/2006-02-06.mdwn
+++ b/news/2006-02-06.mdwn
@@ -15,18 +15,18 @@ Present: Andrew, Tim, Sarah, Jacob, Glenn
Here's a blurry picture of the power block diagram of LV2a's power system. Note the Avionics Power System (APS) with the Lithium Ion battery pack and power switches. Then notice the DC-DC converters scattered around - big ones for the RF power amplifiers, small ones on the nodes' front end.
-![](lv2a_power_block_diagram.jpg)
+[[lv2a_power_block_diagram.jpg]]
### Discussed CAN/Power connector used in LV2a and things we don't like about it
Here's a picture of the notes. The drawing is mostly of the old connector. Here's a link to the old connector: <http://www.jst-mfg.com/pdfE/eJED.pdf/>
-![](connector_requirements_and_sketch.jpg)
+[[connector_requirements_and_sketch.jpg]]
### Tim presented the SPS used on LV2a nodes
Here's the sketch of the new SPS block diagram (t's a composite of three shots). Note the repeat of the switching circuit, and the three outputs based on using a split inductor.
-![](new_fe_sps_block_diagram.jpg)
+[[new_fe_sps_block_diagram.jpg]]
[[tag capstonelv2b]]
diff --git a/news/2006-08-02/logo.mdwn b/news/2006-08-02/logo.mdwn
index 0b9e9c2..aab6eca 100644
--- a/news/2006-08-02/logo.mdwn
+++ b/news/2006-08-02/logo.mdwn
@@ -68,7 +68,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<p>2, 2, 1, 1</p>
</td>
<td>
- <p><img src="Logo01.jpg"></p>
+ <p>[[Logo01.jpg]]</p>
</td>
</tr>
<tr>
@@ -79,7 +79,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<p>1, 1, 1</p>
</td>
<td>
- <p><img src="retread.jpg"></p>
+ <p>[[retread.jpg]]</p>
</td>
</tr>
<tr>
@@ -89,7 +89,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<td>
</td>
<td>
- <p><img src="Logo1a.jpg"></p>
+ <p>[[Logo1a.jpg]]</p>
</td>
</tr>
<tr>
@@ -100,7 +100,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<p>3, 3, 3, 3, 2, 2, 2</p>
</td>
<td>
- <p><img src="Logo02.jpg"></p>
+ <p>[[Logo02.jpg]]</p>
</td>
</tr>
<tr>
@@ -111,7 +111,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<p>1, 2, 2, 1</p>
</td>
<td>
- <p><img src="Logo03.jpg"></p>
+ <p>[[Logo03.jpg]]</p>
</td>
</tr>
<tr>
@@ -122,7 +122,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<p>2, 1, 1, 3, 2, 3, 3</p>
</td>
<td>
- <p><img src="Logo04.jpg"></p>
+ <p>[[Logo04.jpg]]</p>
</td>
</tr>
<tr>
@@ -132,7 +132,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<td>
</td>
<td>
- <p><img src="Logo05.jpg"></p>
+ <p>[[Logo05.jpg]]</p>
</td>
</tr>
<tr>
@@ -142,7 +142,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<td>
</td>
<td>
- <p><img src="Logo06.jpg"></p>
+ <p>[[Logo06.jpg]]</p>
</td>
</tr>
<tr>
@@ -152,7 +152,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<td>
</td>
<td>
- <p><img src="Logo07.jpg"></p>
+ <p>[[Logo07.jpg]]</p>
</td>
</tr>
<tr>
@@ -163,7 +163,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<p>3</p>
</td>
<td>
- <p><img src="Logo08.jpg"></p>
+ <p>[[Logo08.jpg]]</p>
</td>
</tr>
<tr>
@@ -174,7 +174,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<p>3, 967.78</p>
</td>
<td>
- <p><img src="Logo09.jpg"></p>
+ <p>[[Logo09.jpg]]</p>
</td>
</tr>
<tr>
@@ -184,7 +184,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<td>
</td>
<td>
- <p><img src="Logo10.jpg"></p>
+ <p>[[Logo10.jpg]]</p>
</td>
</tr>
<tr>
@@ -194,7 +194,7 @@ Here's how to vote: Put the numbers 1,2,3 in the ones you like the most. The one
<td>
</td>
<td>
- <p><img src="Logo11.jpg"></p>
+ <p>[[Logo11.jpg]]</p>
</td>
</tr>
</tbody>
@@ -207,7 +207,7 @@ Using Condorcet method, logo #04 was the most popular. The top five logos are th
# Ben's Logo
-![](BenPSASLogo.gif)
+[[BenPSASLogo.gif]]
# Frank's "Full Treatment" for Logo #04
@@ -233,23 +233,23 @@ The original (really big attachment) is Logo04BCombo.jpg. Here's smaller version
## Banner
-![](Logo04BCombo_banner.jpg)
+[[Logo04BCombo_banner.jpg]]
## Business Cards
-![](Logo04BCombo_business-card.jpg)
+[[Logo04BCombo_business-card.jpg]]
## Letter head
-![](Logo04BCombo_letterhead.jpg)
+[[Logo04BCombo_letterhead.jpg]]
## T-shirts
-![](Logo04BCombo_tshirt.jpg)
+[[Logo04BCombo_tshirt.jpg]]
## Simple Logos
-Monochrome and flattened-color logos. ![](Logo04BCombo_monocrome-flattened.jpg)
+Monochrome and flattened-color logos. [[Logo04BCombo_monocrome-flattened.jpg]]
# Logo Decision
diff --git a/news/2007-03-14.mdwn b/news/2007-03-14.mdwn
index a491581..1f7c0b6 100644
--- a/news/2007-03-14.mdwn
+++ b/news/2007-03-14.mdwn
@@ -4,13 +4,13 @@
- detect apogee
- has a timer in case everything else fails
-![](rocket_states.jpg)
+[[rocket_states.jpg]]
# Recovery Node Hardware
It needs an accelerometer for launch detect. We may also want it for apogee detect.
-![](recovery_block_diagram.jpg)
+[[recovery_block_diagram.jpg]]
## Accelerometer Debate
diff --git a/psas/Current_project/Parafoil/Parafoil.mdwn b/psas/Current_project/Parafoil/Parafoil.mdwn
index 0412a5c..29df8f7 100644
--- a/psas/Current_project/Parafoil/Parafoil.mdwn
+++ b/psas/Current_project/Parafoil/Parafoil.mdwn
@@ -7,7 +7,7 @@
<p><b><i>PSAS Autonomous Recovery System</i></b></p>
<p>PSAS plans to utilize an autonomous recovery system for its future launch vehicles. It will consist of a parafoil and controller which will steer booster stages and payloads back to a pre-determined point for safety and easy recovery. The controller will monitor various environmental and dynamic variables, as well as an electronic compass and a GPS module.</p>
<p>The initial phase of the project involves the design and construction of a prototype referred to as ARS1, for Autonomous Recovery System No. 1. ARS1 will serve as a development system to test various sensor and controller schemes. It will be fully operational under manual remote control only, and the constraints on the controller of size, shape, and weight will be minimized to allow the testing of different servo devices, and the prototyping of different electronic components. ARS1 will be designed with the framework in place to gradually add complexity to hardware and firmware until the point is reached where it is under complete autonomous control. At that time we will focus our efforts on a redesign to package the electronics and mechanical components to be smaller, lighter, and appropriate for deploying from LV2.</p>
- <p>The ARS project is currently on hold - we simply don&#39;t have the people or resources to pursue this project. If you&#39;re interested in collaborating with us on this project, please <a href="/Contacts">let us know</a>!</p>
+ <p>The ARS project is currently on hold - we simply don&#39;t have the people or resources to pursue this project. If you&#39;re interested in collaborating with us on this project, please [[let us know|/Contacts]]!</p>
</td>
</tr>
</table>
diff --git a/psas/Resources.mdwn b/psas/Resources.mdwn
index 68415b1..f3f81e4 100644
--- a/psas/Resources.mdwn
+++ b/psas/Resources.mdwn
@@ -16,7 +16,7 @@
<tr>
<td width="41%">
</td>
- <td bgcolor="#FFFFFF" width="59%"><a href="Resources/datasheets.html">Data Sheets</a></td>
+ <td bgcolor="#FFFFFF" width="59%">[[Data Sheets|Resources/datasheets]]</td>
</tr>
<tr>
<td width="41%">
diff --git a/psas/Resources/CAD.mdwn b/psas/Resources/CAD.mdwn
index d0fbe41..f9a17e1 100644
--- a/psas/Resources/CAD.mdwn
+++ b/psas/Resources/CAD.mdwn
@@ -1,3 +1,3 @@
-[ [[Veiw Online with Browser - Java CAD viewer|psas/Resources/CAD/cad]] ] [ [CAD files](CAD/CADfiles.html) ]
+[ [[Veiw Online with Browser - Java CAD viewer|psas/Resources/CAD/cad]] ] [ [[CAD files|CAD/CADfiles]] ]
[[psas/Resources/graphics/LV2exp.gif]]
diff --git a/psas/Resources/Links.mdwn b/psas/Resources/Links.mdwn
index 27a5a00..440bbbf 100644
--- a/psas/Resources/Links.mdwn
+++ b/psas/Resources/Links.mdwn
@@ -26,7 +26,7 @@
<td bgcolor="#EEE8D5" height=61 width="69%">Produces fantastic RISC microcontrollers with FREE development system. These guys have more bang for the buck, and a better development environment, than we&#39;ve seen as of yet. We used the PIC 16C73A and 17C756.</td>
</tr>
<tr>
- <td bgcolor="#FFFFFF" height=42 width="31%"><a href="http:/www.amd.com/" target="_blank">Advanced Micro Devices, Inc.</a></td>
+ <td bgcolor="#FFFFFF" height=42 width="31%">[[Advanced Micro Devices, Inc.|http:/www.amd.com/]]</td>
<td bgcolor="#EEE8D5" height=42 width="69%">Produces the fastest FLASH RAMs available - that are affordable and large enough for scientific data logging applications (4M x 8 - the AM29F032B).</td>
</tr>
<tr>
diff --git a/psas/intro.mdwn b/psas/intro.mdwn
index f06eaff..0bf5bee 100644
--- a/psas/intro.mdwn
+++ b/psas/intro.mdwn
@@ -31,7 +31,7 @@
<p>1. [[psas/Current_project/LV-0/Project_Navigation_LV-0]] (LV0) was our first launch in June of 1998 to 366m (1,200ft). It was our first rocket and a proof of concept for some of our radio systems, including real-time broadcast video. It was a great introduction to amateur rocketry for many of us [[news/1998-06-07]].</p>
<p>2. [[psas/Current_project/LV-1/Lv1menu]] (LV1) was our next rocket that flew in April of 1999 to 3.6km (12,000ft). It was our proof of concept for several new systems, including a manual control system, inertial sensors, and a more advanced telemetry system [[news/1999-04-11]].</p>
<p>[[psas/Resources/graphics/tower.JPG]]3. Launch Vehicle No. 1b (LV1b) was the same rocket as LV1, but with improved avionics (electronics) which flew in October of 2000 to 3.53km (11,600ft). We added a GPS, upgraded the flight computer and improved the inertial sensors. This was our first real stab at the computing power and sensors necessary to do computer guidance; we&#39;re right in the middle of processing the data from this launch and are excited about its implications [[news/2000-10-07]].</p>
- <p>We&#39;ve also developed &quot;M&quot;-class solid motors, test stand equipment for motor testing, and the beginning of a mobile infrastructure including a <a href="Schedule/Tower/Launch_tower.html">launch tower</a>, a launch control module, and the various logistical equipment and skills a group needs to do successful field operations.</p>
+ <p>We&#39;ve also developed &quot;M&quot;-class solid motors, test stand equipment for motor testing, and the beginning of a mobile infrastructure including a [[launch tower|LaunchTower]], a launch control module, and the various logistical equipment and skills a group needs to do successful field operations.</p>
<p>We also try and reach out to the community as much as possible. We&#39;re a regular attendee at [[news/1999-07-18]], we&#39;ve done many educational presentations and we&#39;re an advocate of cross-discipline engineering projects at Portland State.</p>
<p><b><i>What are your current projects?</i></b></p>
<p>We&#39;re currently working on the next generation vehicle, called [[psas/Current_project/LV-2/LV2menu]] (LV2) which should be ready to launch in fall of 2001. It has a projected altitude of 16km (55,000ft), has an advanced avionics system which we hope to use for real computer guidance, a modular air frame system, and most of all it&#39;ll build on everything we&#39;ve learned from the last three rockets. LV2 is currently funded through a $10,000 grant from the NASA Space Grant Program.</p>