wiki/ news/ 2005-10-06 - General Meeting: what do we do next?


After the loss of LV2 and the departure (temporarily, we all hope!) of Brian, we did some soul searching to figure out what we wanted to do next. We were looking at a range of options:

  1. Rebuild LV2 exactly as it was, with only very minor modifications (like, for example, a new recovery system!)
  2. Rebuild LV2 pretty close to how we had it, but with major upgrades.
  3. Design and build LV3.

Very few people were interested in the first option 1, although it technically might be the quickest path to another launch. Without Brian, a propulsion team, and a lot of strong student resources, we really can't do a design and build of LV3. So we chose option 2, although what "major upgrades" are must be defined along the way.

We're starting out this process by making some simple goals to be done by January, at which point we might really have an idea of exactly what we'll be doing for 2006.

Airframe Team

Most of how we proceed depends on if we build a new airframe, and what kind it is. Maggie, Tim and Peter have said that they're willing to rebuild LV2's airframe with some minor modifications. Since they might have more access to CNC tooling in the future, this might be easier than the first time around. In particular, we discussed:

Maggie and Tim felt that a new airframe was realistically about 1 to 1.5 years away. That would mean that we wouldn't be able to launch until Spring of 2007.

January Goals:

  1. Presentation to the ME department to see if we can get some more student interest
  2. Make a design and schedule document

Avionics Team

With the decision to rebuild LV2's airframe, we knew that we could now rebuild much of the avionics in the same way: the cylindrical patch antennas, the radio systems, etc., all didn't need to change. And with the new ?PowerPC from the IBM grant, we at least had a starting point. Probably the most disagreement for the evening was exactly how we rebuild the avionics. We had two realistic options:

Most folks are leaning towards the later (redo each block), but there's a lot of careful planning to do before we leap into designing and building. In terms of how soon until we have a completed system, that's just not foreseeable right now. After we have an idea of exactly what we're planning, we'll be able to look at schedules.

January Goals:

  1. Help the software team get the new PPC FC up and running - get a PCI-104 to PCMCIA/PC Card adapter, flash memory, etc.
  2. Get GPL-GPS up and running with the new FC (probably just over the UART, no need for CAN).
  3. Determine if Glenn and Sarah can do their senior capstone project on the design of new ARM7TDMI-based CAN nodes.
  4. Have a true design and schedule document for the new avionics system

Software Team

As Jamey so, uh, "nicely" pointed out, the software team didn't lose anything in the last crash :-? . But there's still a lot to do, especially with the migration to a ?PowerPC flight computer. There was a general consensus to:

January Goals:

  1. Get the PPC flight computer up and running by mid-December.
  2. Set up communication with GPL-GPS, maybe including 10 Hz position calculations from 10 Hz pseudorange data.


Jamey set up PSAS as a PSU student group. This gets us some funding, but more importantly it sets us up to have more of a presence on campus to recruit new students. We'd love to get some new students onboard, and hopefully attract people who will be self-motivated enough to really end up contributing.

We also decided to get back to monthly team meetings as we work on the new LV2: our official schedule is now the 1st Wednesday of each month in FAB155 at 7:00pm.