Outsourced engines for POGO and Spike? If possible I would like to see the
drawings for the POGO engine, I might be able to give some ideas on
producabilty (unless you have already sent them out to the shop). Last drawing
I saw of Spike was concept only.
IIRC Spike was to initially use the KISS airframe to prove concept, is
this so? Is there more than one current KISS airframe? Were more test flights
planned for KISS regular?
POGO will use all new airframe and tankage correct? Engines aside is there
high confidence in the design? Will it share KISS components (tested
components) or will everythying be new? Tanks will be OTS or scratch built?
Is the compter hardware known, is it the same unit as in Gizmocopter? The
first flight for POGO would have to have the flight controls installed, right?
That is there won't be any ballistic flight possibility to test the hardware
without some computer control. So to allow for a little test time what is the
latest that the computer could at least provide minimum control for flight and
still make the deadline? I think mid July or a little over 7 months. Final
code installed later of course. Is this doable? Seems like a lot of man hours
to me.
Perhaps a deadline for a timetable would be approriate and answer the
question of possibility.
David Masten wrote:
> On Fri, 2002-12-20 at 14:11, Alex Fraser wrote:
>
> > I don't think you can do POGO and Spike at the same time with a end
> > of next year deadline. I think you would be hard pressed to build POGO
> > in that time, but it is a possibility.
>
> There is something *very* wrong if we can't work two projects
> simultaneously. We have plenty of people to work both projects.
>
> We have already outsourced the engine manufacture, the remainder of the
> work is composites and pipe fitting. (and flight controls.)
>
> --
> David Masten <[EMAIL PROTECTED]>
>
> ------------------------------------------------------------------------
> Name: signature.asc
> signature.asc Type: application/pgp-signature
> Description: This is a digitally signed message part
--
>>>>>>>>>>>>>>>>----<<<<<<<<<<<<<<<<<
........ Alex Fraser N3DER .........
......... [EMAIL PROTECTED] .......
[~]_>^</\-[~]_>^</\-[~]_>^</\-[~]_>^<
_______________________________________________
ERPS-list mailing list
[EMAIL PROTECTED]
http://lists.erps.org/mailman/listinfo/erps-list
