The autopilot would have been the easy part. I offered to do one having
just demonstrated--on the HiMAT vehicle---an autopilot that performed
flight test maneuver automatically. The pilot, Fitz Fulton, refused. He
believed he could fly manually from a remote location.
Curtis Olson wrote:
On
On Sun, 18 Jan 2009 21:05:56 -0500, Lee wrote in message
4973e004.7030...@rainmountainsystems.com:
I think the link I sent to the CID movie was bad. Try this:
http://www1.dfrc.nasa.gov/Gallery/Movie/CID/Medium/EM-0004-01.mpg
..they both worked ok for me, I used wget and kmplayer.
Here are
I'm excited! I just got FlightGear connected up to a Garmin 400 which
speaks the same protocol as the 430/530. I haven't looked at sending over
fuel and radio information, but all the positional / velocity stuff is
working. I'm going to do some more testing here before committing the new
Hi Curt,
Curtis Olson wrote:
I'm excited! I just got FlightGear connected up to a Garmin 400 which
speaks the same protocol as the 430/530. I haven't looked at sending over
fuel and radio information, but all the positional / velocity stuff is
working. I'm going to do some more testing
On Mon, Jan 19, 2009 at 3:06 PM, Martin Spott wrote:
Hi Curt,
Curtis Olson wrote:
I'm excited! I just got FlightGear connected up to a Garmin 400 which
speaks the same protocol as the 430/530. I haven't looked at sending
over
fuel and radio information, but all the positional /
I'm excited! I just got FlightGear connected up to a Garmin 400 which
speaks the same protocol as the 430/530. I haven't looked at sending over
fuel and radio information, but all the positional / velocity stuff is
working. I'm going to do some more testing here before committing the new
Curtis Olson wrote:
There is a set of messages that the Garmin 295/296/400/430/530/etc. emit. I
previously implmented this message set which you can activate with the
--AV400=[...] option. This works for driving a Garmin 295/296 gps.
However, the 400/430/530 gps expect a different command
On Mon, Jan 19, 2009 at 2:53 PM, Torsten Dreyer wrote:
Will you also commit the Garmin 400, so everybody can download one?
Alas, I haven't yet figured out how to commit physical hardware to CVS ...
maybe with GIT? I can commit the protocol updates soon though. :-)
Curt.
--
Curtis Olson:
Hi Csaba,
Csaba Hal??sz wrote:
On Sat, Jan 17, 2009 at 9:08 PM, Martin Spott martin.sp...@mgras.net wrote:
nevertheless I'm surprised to see a missing XML config file
segfaulting the entire simulation (current CVS, Linux AMD64).
I am not :)
The patch you're proposing indeed saves us/me
Not sure who does the patching around here but I've attached a fix for
the Instrumentation/HUD/HUD_ladder.cxx file.
The sign on the sideslip (beta) term used to drive the velocity vector
on the HUD was incorrect. The patch fixes the velocity vector so it
conforms to the positive beta = wind in
On Tue, Jan 20, 2009 at 12:56 AM, Martin Spott martin.sp...@mgras.net wrote:
Hi Csaba,
The patch you're proposing indeed saves us/me from the segfault due to
a file not being present - which is definitely a good start.
That was all I intended. If a file is missing it is a broken airplane
On Mon, Jan 19, 2009 at 3:56 PM, Martin Spott wrote:
This sounds great to me. Even though I would not count the GNS430/530
as being among my personal favourites, I know they are _very_ popular
and I've been using such thing at least in two different aircraft. If
I'm not mistaken, this would
12 matches
Mail list logo
