Display Gimbal Actions contained in Markers on the Mission Preview

Scott W

Please display Gimbal actions (gimbal heading and orientation) that occur in a Marker on the Mission Preview's timeline. 

Background...  When a Destination component has a Gimbal Orientation or Gimbal Heading specified, the Gimbal action is displayed on the "Timeline" at the bottom of the web app's Mission Preview.  But the same Gimbal action occurring from inside a Marker (on a Path) does not appear on the mission preview timeline.

0

Comments

4 comments

  • Comment author
    Jim McAndrew Dronelink Staff
    • Edited

    Those aren't discrete commands, which is what those areas in the timeline represent. If you have interpolation enabled, it is a continuous change over time, so not even really sure what would show in the command area even if we did.

    0
  • Comment author
    Scott W

    I understand the problem of just "what" to put in the timeline, due to the interpolation... 

    But I think there should be SOME indication that the gimbal position is being altered during that part of the timeline.   Even if it's a solid bar from one marker to the next (on the Gimbal line), with hover text showing start/end values?   Just disconcerting to see the discrete commands show up in other spots, but then show nothing during a Path -- even though the gimbal is changing between (some) markers.

    0
  • Comment author
    Jim McAndrew Dronelink Staff

    Technically you can just play the timeline and see the gimbal pitch / drone yaw in the 3D preview (both visually, and as text at the bottom of it). Having said that, it seems like these would both make more sense as graphs, and the yaw one would probably have to be -180 to +180. The markers could show up in a separate row and be long if interpolated, and short if not.

    0
  • Comment author
    Scott W

    Graphs would be a great way to show this.  Markers contain so much functionality, having them on the line to easily correlate with the other rows of the timeline would be great, too.

    0

Please sign in to leave a comment.