[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Paparazzi-devel] Unit Test/Start-up Procedure for Paparazzi?
|
From: |
Felix Ruess |
|
Subject: |
Re: [Paparazzi-devel] Unit Test/Start-up Procedure for Paparazzi? |
|
Date: |
Fri, 17 Feb 2012 18:26:36 +0100 |
Hi Gareth,
could you please elaborate on how you can check all this on the command line?
I mean do you start specific "test programs" and then you "just" see the output and have to verify yourself this is correct/what you expected?
If that is so, what is the difference to just checking the exactly the same things in messages? (Except that it might be guided, so walk you through the steps)
So I suspect a bit more than that is done (certainly possible)?
And I certainly agree that the basic pre-flight check should always include putting it into AUTO1 and checking the responses, pfd, etc.
I hope most people do that anyway...
Cheers, Felix
On Fri, Feb 17, 2012 at 6:04 PM, Gareth Roberts
<address@hidden> wrote:
Hi,
Another O.S autopilot has a command-line test routine you can run through.
If you have a switch on the autopilot set in a certain (no-fly) direction on boot, a serial console is opened on the device with a very basic shell.
You can check IMU directions, compass, GPS, RC inputs, telemetry etc etc and test servos.
It's fairly handy for testing & debugging, although I'm not sure whether the kb cost is worth it.
Possible as a core that could be uploaded to the autopilot (similar to 'tunnel').
That said, a basic check of putting the aircraft in MODE1 on the ground before takeoff & checking aileron/elevator responses are correct and match GCS pitch/roll doesn't take much time and should be mandatory unless there is a strong reason not to.
Potentially off-topic, some sort of vehicle incident/crash reporting database could be useful for improving the paparazzi software/hardware?
Cheers,
Gareth