summaryrefslogtreecommitdiff
path: root/SystemTest09Jul2005.mdwn
blob: 42434b2937b03a61389ccacc71cc5516936b0ee0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
# <a name="Yet Another LV2 System Test Day:"></a> Yet Another LV2 System Test Day: July 9th, 2005

**Goal:** Successful "pre-launch" test of the complete LV2 system

## <a name="Who"></a> Who

Who: Tim, Holly, Jamey, Sarah, Andrew, Glenn, Frank, Jay

## <a name="When"></a> When

Previous evening prep:

- Prep the two "ground tables" (launch control and launch tower) to slide into the back of a van/truck
- Get: batteries from Glenn, power system setup

Here's the schedule for the test day:

<table border=1 cellpadding=0 cellspacing=0>
  <tr>
    <td> 10:00 - 11:00 </td>
    <td> Meet at 10:00am sharp at Andrew&#39;s workshop, and load up the hardware according to the [[CurrentBringList]]. </td>
  </tr>
  <tr>
    <td> 11:00 - 12:00 </td>
    <td> Set up the launch tower and launch control at Gabriel Park. </td>
  </tr>
  <tr>
    <td> 12:00 - 16:00 </td>
    <td> System test and picnic. </td>
  </tr>
  <tr>
    <td> 16:00 - 17:00 </td>
    <td> Quick teardown and drop off at Andrew&#39;s workshop. </td>
  </tr>
</table>

Mostly went as planned, for suitable definitions of time.

## <a name="Where"></a> Where

Once again, we started at [Andrew's workshop](http://psas.pdx.edu/Minutiae/DirectionsToAndrewsCabin) and then went off to Gabriel Park, in SW Portland near Multnomah located at the intersection of SW Vermont and SW 45th. The launch tower was on SW 37th avenue just south of SW Vermont on the east side of the park, and launch control was in the middle of the park in a parking lot off of SW 42nd, near the park's maintenance buildings (or whatever they are).

Launch tower: N 45 deg 28.510', W 122 deg 42.938', 480 ft <br /> Launch control: N 45 deg 28.514', W 122 deg 43.137', 410 ft <br /> Pressure that day: 999.6 mb <br /> Temperature: ? <br />

## <a name="Agenda"></a> Agenda

- Set up LV2 airframe/avionics "ready for launch" on the rail on the launch tower
  - Went well, boards worked well as levelers. Forgot to get the right rail-bolt.
- Set up the complete ground station (_except_ for the 2m antenna)
  - Check
- Test the heck out of the field server: is netforward keeping up? does it powerup correctly? What is the powerup sequence? Should we kill X?
  - Who is X? Test did not go perfectly, see **Results** below
- Range check on the new/old 2m receiver using a handheld
  - 2m may be jammed by HV pyro supply, need further test.
- Do 3 complete scripted launch sequences without simulator (get to FC's Boost detect using accelerometer test pin and umbilical cord)
  - Problems here too, see **Results**
- Do 3 complete scripted launch sequences using simulator to go past Boost
  - Problems, see below.

- End of Day Debrief: Did everything work? What could have gone better? What should we focus on during the next month?

## <a name="Results"></a> Results

Added several ToDo's to various lists

- Ignition relay appears dead!
- LTC igniter enable rocker switch (red) seems flaky but working, OK?
- DC to DC converter (black box) jams the ATV, but only when shore power is engaged and the battery is _NOT_ being charged. The off-line power supply (blue box) from the same manufacturer does not have this problem.
- Field server jams the orinoco at least some of the time. Possibly disconnect the right rather than the left diversity antenna? Or is it possible that this was a channel issue?
- Get proper bolt for launch rail pivot (assigned)
- Launch tower rail bracket detached during test, the fasteners are inadequate, inform Jimmy &amp; Brian
- Solar panel power cord is badly frayed, repair and prevent recurrence

Lots of stuff added to [[SoftwareToDo]].

## <a name="Chronicle"></a> Chronicle

We were late getting setup. The setup went ok. Next time we think we can strap the rocket to the tent pole if we're too lazy to bring the tower. Good news is that there is no evidence of interference from the tower. (Though it's hard to completely rule this out until 100% of our interference problems are solved.) Also good, it looks like the trackmaster is preforming ok and that the 2m has decent range, at least when the pyros aren't charging ;) . Once we got setup and the birthday festivities had wound down a bit we proceeded to discover that things keep jamming other things.

<div>
  <center><a href="http://psas.pdx.edu/gallery/view_photo.php?set_albumName=psas_system_tests_2005&amp;id=fm_real_soon_now"> <img alt="fm_real_soon_now.thumb.jpg" src="http://psas.pdx.edu/albums/psas_system_tests_2005/fm_real_soon_now.thumb.jpg"> </a> <a href="http://psas.pdx.edu/gallery/view_photo.php?set_albumName=psas_system_tests_2005&amp;id=fm_overrun_with_kids"> <img alt="fm_overrun_with_kids.thumb.jpg" src="http://psas.pdx.edu/albums/psas_system_tests_2005/fm_overrun_with_kids.thumb.jpg"> </a></center>
</div>

The GPS and pressure altitude disagree to a larger than expected factor. Initially the pressure altitude wasn't being initialized, but once we caught that, the pressure altitude was initialized to 480 feet [146m] based on Andrew's pressure aided GPS. The on-board GPS varied but favored 130m, this is probably a bit further off than they should be with seven satellites. We should try to get the map-altitude of future test sites beforehand.

Right away we saw packet loss even with 40dB S/N: (-50/-90)dBm.

The black box still jams the ATV in ARMED mode. The blue box works fine.

Since Jamey's laptop was reading packets with just the PCMCIA patch antenna we put the ad-hoc card in his laptop and used the field server only for the PSAS net. This resulted in high packet loss when Jamey's laptop was resting on top of the field server. Also the loss was worse with the field server lid closed, which we explain by the proximity of the diversity antenna to the other RF junk when the lid is closed.

After figuring much of this out and checking cables until we (Glenn) was convinced they were ok, we noticed two other WiFi nets in range. By the time we got our data rates reasonable one net had gone down. This may or may not have been a factor.

Also, the HostAP access point running on the field server was set to channel 3, which we think was jamming the channel 1 ad-hoc network. We changed it to channel 11, just like old Linsys WAP we had.

Once the packet loss subsided we ran a few tests of the launch sequence. That's when we noticed the ATV display was working in real-time while rocketview was lagging badly. (About 6min in one test.) We attribute this to a slow link and buffering in the network (we have a 32MB buffer).

In the first complete test the sequencing looked good including the recovery node. In subsequent tests even though the igniter relay clicked we noted that we could never confirm continuity in the ignition circuit. Also the recovery node failed to reset properly resulting in "\*\*\*\*" for the drogue timers. Further the recovery node failed to respond to, and probably to hear, our disarm commands from the 2m until the pyros actually fired. This may be due to yet another RFI problem, this time from the HV pyro switcher.

By that time it was pretty late (past 6) and just starting to rain, so we packed and headed out. Break down was pretty efficient. It was a nice day in the park.