Skip to main content

Gimbal will not point down. include link to mission?

Comments

11 comments

  • Jim McAndrew

    I think you might be trying to fit a square peg through a round hole. The "idea" behind destination components is they are intended to just get you from point a to point b with most of the rest of the behavior being automatic / determined by Dronelink. If you prefer fine-tuned control over what is happening between point a and b, you should probably just use a path with markers, or multiple paths.

    1
  • Jim McAndrew

    Share from the more menu on the plan:

    0
  • Tommy Keane

    Thank you,  I kept trying to "export" it. 

     

    0
  • Tommy Keane

    OK, I can't share the actual mission, but the plan can be shared.  the link is below..

    I want the drone to fly to a corner of the property.  point camera down. and video to the final corner.

    The issue is, the camera won't point -90 down.

    https://app.dronelink.com/tommy-keane/rep_initial/plan/VCMpab0ib3dP1eCRhD8Z/j1tLSzdi7zo1wSNedaVd

     

     

     

    0
  • Tommy Keane

    Also.  flying a mavic Mini on an iPhone 11 pro max

    0
  • Jim McAndrew

    You are attempting to issue a gimbal command during the achievement portion of your destinations, which is not what you want. If you want it to fly to a destination while pointing down, you need to click this:

    0
  • Tommy Keane

    Thank you for your prompt reply.

    OK,  instead of an Achieved List of Commands of gimbal -90; camera start capture.
    I will use  "Add Gimbal Orientation"/ -90,  Then "Add Automatic Capture" /video .

    So first see if there is a "built in button"  before creating  an Achieved list.

    Do I have this concept correct now?

     

     

    0
  • Jim McAndrew

    Yes, but you don't have to guess. Just run the mission previewer before flying to make sure you are getting the behavior you want. If not, look for a different way to do it, possibly with different component types (like Path).

    0
  • Tommy Keane

    In the previewer, I can achieve the behavior I want.  It seems in the Destination "ADD [some command]"  is what takes place on the way to that destination, not what happens when you get there.  So If  I want the camera pointed down between Dest #2 and Dest #3, I need to add "Add Gimbal Orientation"/ -90,  Then "Add Automatic Capture" /video  at Dest #3.   (it also generates, STOP CAPTURE, then mode VIDEO & START CAPTURE.

    I will test live Monday.

     

    0
  • Tommy Keane

    Conclusion:
    I often submit "issues" under "Bug Reports"  but I know the bug is usually within my program.

    The plan is :
    Fly to nearby Destination1 and perform initial setup. ( I usually do this as my practice, not sure if it is "best practice").
    Fly to Destination2 at corner of property.
    Point gimbal -90 and video to 2nd corner at Destination3.
    Then fly to 3rd corner at Destination4 with gimbal -90 and capturing video.

    How Dronelink reacts:
    When "Add Gimbal Orientation"  is used, that is what happens on the way TO the Destination.  If you want gimbal at -90 between Dest2 and Dest3, Add Gimbal Orientation at Dest3.  Then again at Dest4 to keep it down  Default is something like -12.
    If Destination option "Add Automatic Capture" is used, add this to Dest3 to capture between Dest2 and Dest3.  Again, this is the command used on the APPROACH to the Destination.  Setting this at Dest3 generates this at Dest2: Stop Capture, Camera mode/video, Start Capture. and generates at Dest3: Stop Capture.
    To capture between Dest3 and Dest4, the "Add" the same instructions at Dest4.   This will create 2 separate videos.
    To create 1 video from Dest2-Dest3-Dest4, alternatively use "Set Achieved Component/Start Capture" at Dest2 to Start Capture (after proper initializations at Dest1) instead of "Add Automatic Capture" at Dest3 and Dest4.

    I cannot seem to use "Set Achieved Component/gimbal orientation" at Dest2 to cooperate.  Gimbal moves to -90, then back to -12 when video capture starts. IS THIS AN ACTUAL BUG?  anyway, I can work around it.

    ONE NOTE: Using Mavic Mini and iPhone11.   The mini's camera is not alway displayed to the iPhone, but it does indeed capture the video.  I have not determined the cause for this intermittent issue in my programming.


     







    0
  • Tommy Keane

    OK.  I was using the wrong tool for the job.  I thought the waypoints were click and drag locations.  But now I see I can actually enter the Lat/Long from the county assessors office.  I was entering Lat/Long in the Destination to get to property corners.
    Now I see life could be simplified if I use a Path and waypoints with exact Lat/Long.

    Thanks for helping with my self-induced complexities.  :-)

     

    0

Please sign in to leave a comment.