Dave Martin wrote:
Just done some more reading of your page and incident analysis; I was just
thinking that a useful tool would be a couple of camcorders. (and a friend to
operate one of them).
If you set one up on a tripod looking at the transmitter, you could at least
see what control positions you were *trying* to get at any given time.
The second camera could be kept on the aircraft itself.
Both cameras would need to be synced to keep the correct time (for comparison
with your UAV data).
We do have a camera on board looking forward and down, but our helpful
video capture application decided that there was so much "snow" and bad
signal in the video stream (primarily after the crash) that it helpfully
deleted that entire segment of video for us. Ya gotta love windows!
One thing we'd like to do that wouldn't be too technically difficult
would be to get a 2nd receiver on the same channel as the aircraft but
keep it on the ground. Pipe the servo outputs from the ground based
receiver into a little PIC board and decode the PWM signals coming in on
each channel and send them out the serial port to the ground station.
This would be a way to record pilot inputs without needing extra
equipment in the air. It doesn't tell you about loss of signal or
interference issues with the airborn system, but it does tell you what
the pilot is trying to do.
I think we'll get there ... you learn as you go with this stuff and it
takes time to assemble equipment and develop software and interfaces.
Curt.
--
Curtis Olson http://www.flightgear.org/~curt
HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
