Closed varunagrawal closed 4 years ago
@Winter-Guerra @eatal any updates?
Hi @varunagrawal ,
Can you describe the issue you are experiencing in a bit more detail?
The commit you referenced should not affect the operation of the keyboard teleop node. Are you using the updated take-off procedure as summarized in the commit message as "the vehicle is armed by publishing a message to the topic /uav/input/arm
" (see also in the FAQ here)?
Oh I see. I was using an older version that didn't require that parameter to be set so this was unintuitive to me. Can you please add this to the "Getting Started" instructions?
On Fri, Feb 7, 2020, 13:44 eatal notifications@github.com wrote:
Hi @varunagrawal https://github.com/varunagrawal ,
Can you describe the issue you are experiencing in a bit more detail?
The commit you referenced should not affect the operation of the keyboard teleop node. Are you using the updated take-off procedure as summarized in the commit message as "the vehicle is armed by publishing a message to the topic /uav/input/arm" (see also in the FAQ here https://github.com/mit-fast/FlightGoggles/wiki/FAQ#why-is-the-vehicle-not-moving )?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mit-fast/FlightGoggles/issues/147?email_source=notifications&email_token=AAHOIXDIQLPH37L5MTSCSH3RBWTYRA5CNFSM4KRHK5NKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELEEC3Y#issuecomment-583549295, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHOIXDF735WYNV74VIACTTRBWTYRANCNFSM4KRHK5NA .
Hi,
I recently updated my local version to the latest commit and the keyboard command not longer works. The breaking change was introduced in commit ff5fca7f1f359b1f749f3c3bf9046d0bfa0e6441.
It would be great if this could be fixed.