Skip to main content

360 photos with mavic mini error

Comments

19 comments

  • Sven

    I have the same problem with my mavic mini.

    0
  • Michael F.

    Yes, I also have the same issue on mavic mini, now. It used to work fine, but the new version from march 24, 2021 seems to have issues.

    Is there any option to get the previous version of the 360 On-the-Fly function?

    Or is the error with gimbal orientation 12 related to some updates in DJI software or firmware?

    Best Regards

    Michael

     

    0
  • Jim McAndrew

    We will need to test this to confirm if there has been a change. Thanks for the report.

    -1
  • Ted Hillhead

    Yes, I also have the same issue on mavic mini. 360 photo does not work in any positive angle

    0
  • Xavier Font Bruch

    I have the same issue. And this issue also happens with Path mode.

    0
  • Jim McAndrew

    There appears to be a bug in the latest DJI SDK (iOS + Mavic Mini only) for gimbal pitches above 0, even if pitch range extension is enabled. We have reported it to DJI. In the meantime, you will need to make sure you don't issue gimbal orientation commands that go above 0 degrees, or if you do, mark them as not required.

    0
  • Michael F.

    Thank you Jim for reporting this issue to DJI.

    They seem to have similar issues within their built in 360 function, e.g. on Mavic Air 2.
    At least this is how I understand the following thread in DJI forum:

    Home / Products / Mavic / Mavic Air 2
    "Gimbal upward move limited for pano"
    https://forum.dji.com/thread-239203-1-1.html

    But I assume it will take a long time until DJI would solve it, if they do at all.

    So, I wonder if the Dronelink on-the-fly function could be changed to have the maximum upward pitch of the gimbal as user parameter, or if it would be possible to get a new on-the-fly function which starts at zero gimbal pitch?

    Or maybe someone has already created this 360 function, tested it for Mavic Mini and would like to share it?

    0
  • Jim McAndrew
    if the Dronelink on-the-fly function could be changed

    Will add it to the list but not sure when it will actually happen. If you get impatient, the code is open source and you can do it yourself with an Elite account or higher.

    0
  • Michael F.

    Okay. So I copied the Dronelink on-the-fly 360 Photo function to a new repository ("mf_otf_360") and started to create 2 new functions:

    360 Photo2 (start with gimbal pitch zero-hoizontal)
    360 Photo3 (start with current gimbal pitch)

    I made a short test today, and both flew on Mavic Mini without issue. I did not check and stitch the pictures, yet, but looks promising.

    Setting the gimbal pitch to the maximum upper limit before start also works fine for the 2nd function.

    Next step could be to introduce a user parameter and ask if it should start with zero (horizontal) gimbal pitch or with the current one. But I have to learn some more things before I would be able to do this.

    Feel free to test or add ideas ...

    0
  • Jim McAndrew

    If you want to key off the drone model, you can access it like this:

    context.drone.model
    0
  • Justin Manning

    I am in the same boat, pitch 12 error.  This is with the On-The-Fly 360 Photo. I have attached a screenshot in case it helps.

    ~Justin

    0
  • Michael F.

    Not sure how to share my repository "mf_otf_360". Maybe via this linK?

    https://app.dronelink.com/michael-franz/mf_otf_360/function/SQiFHvi03Cb7akn6DgIa 

    On-the-fly function: "360 Photo3 (start with current gimbal pitch)"

    Here is the first 360 test result done on Mavic Mini. The 23 pictures have been stiched with Hugin.

    https://www.skypixel.com/photo360s/mf-otf-360-test1?utm_source=copied&utm_medium=PCWeb&utm_campaign=share&sp=0 

    1
  • Michael F.

    Hi Jim,

    there is a new version of  OTF '360 Photo' in public Dronelink repository 'On the Fly'.

    Thank you adjusting it. I tried it out, but unfortunately the error still occurred.

    Gimbal Orientation | Pitch 12° | The parameters are invalid.

    Is there a possibility to use different components, based on type of drone or based on user parameter within the function?

     

    code snippet from new version of OTF '360 Photo':

    ...

    //limit the top row to zero on the mini and spark
    switch (context.drone.camera().specification.id) {
    case "spark":
    case "mavicMini":
    plan.node().descendants.forEach((node) => {
    if (
    node.component &&
    node.component instanceof Dronelink.CommandComponent &&
    node.component.command instanceof Dronelink.OrientationGimbalCommand &&
    node.component.command.orientation.x > 0
    ) {
    node.component.command.orientation.x = 0
    }
    })
    break

    default:
    break
    }

    ...

    0
  • Jim McAndrew

    It should work now.

    0
  • Michael F.

    Hi Jim,

    Great, it works again. Thank you very much!

    What has been changed? I do not see a difference in the function.

    0
  • Jim McAndrew

    0
  • Michael F.

    Yes, now I see it.

    0
  • Jo Koman

    https://support.dronelink.com/hc/en-us/community/posts/1500000664542/comments/1500000630962

    i have the same error message when i try to run a planned 360 mission component.

    on the fly component works just fine..

    0
  • Jim McAndrew

    You need to copy the 360 photo component into your own account and modify the gimbal angle.

    0

Please sign in to leave a comment.