ghost
commented
9 years ago https://3drsolo.atlassian.net/browse/FC-145 https://3drsolo.atlassian.net/browse/FC-145
@dngrlux I don’t recognize your username. Who is this?
This issue is OK to be closed as it is tracked in Jira.
On Jun 19, 2015, at 7:25 PM, dngrlux notifications@github.com wrote:
This may be expected behavior… please close if so.
With the Solo controller defaulting to hover at 50% stick/throttle, I had a possibly-false expectation that the altitude would not deviate too much when using drift mode. In today's tests I brought the Solo to 400' AGL and tested full forward flight and banks in drift mode, and the altitude dropped over a period of 10-15 seconds to 350', then to 300'. If the FLY mode can be tuned to hover at 50% throttle, could some kind of throttle curve or barometric assist be utilized to keep the quad in drift mode at generally the same altitude without throttle input?
With the IRIS+ in drift mode, I had no expectation of holding an altitude at precisely 50% throttle, as the stick is not spring loaded and manual throttle position is required.
— Reply to this email directly or view it on GitHub https://github.com/3drobotics/ardupilot-solo/issues/103.
dngrlux
proficnc
brettdaman
This may be expected behavior… please close if so.
With the Solo controller defaulting to hover at 50% stick/throttle, I had a possibly-false expectation that the altitude would not deviate too much when using drift mode. In today's tests I brought the Solo to 400' AGL and tested full forward flight and banks in drift mode, and the altitude dropped over a period of 10-15 seconds to 350', then to 300'. If the FLY mode can be tuned to hover at 50% throttle, could some kind of throttle curve or barometric assist be utilized to keep the quad in drift mode at generally the same altitude without throttle input?
With the IRIS+ in drift mode, I had no expectation of holding an altitude at precisely 50% throttle, as the stick is not spring loaded and manual throttle positioning is required.