360 photos with mavic mini error
hi!
i have made a couple of 360 photos with my mavic mini with no problems, but yesterday when i wanted to make a new 360 photo i just used an old plan which i know works and i changed nothing. but it gives me this error when the automation starts
Required Component Failed: Remove this component, make it not required, or try again.
You may need to restart your drone before trying again.
Gimbal Orientation | Pitch 12° | The parameters are invalid.
Please review and submit the request.(code:-1005)
i tried to make a new plan but it also gave me the same error. But when i use the offical DJI app the gimball works perfectly fine.
Does anyone know this error and how to fix it?
Comments
27 comments
I have the same problem with my mavic mini.
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
We will need to test this to confirm if there has been a change. Thanks for the report.
Yes, I also have the same issue on mavic mini. 360 photo does not work in any positive angle
I have the same issue. And this issue also happens with Path mode.
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.
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?
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.
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 ...
If you want to key off the drone model, you can access it like this:
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
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
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.
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
}
...
It should work now.
Hi Jim,
Great, it works again. Thank you very much!
What has been changed? I do not see a difference in the function.
Yes, now I see it.
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..
You need to copy the 360 photo component into your own account and modify the gimbal angle.
Hello, are there any updates on this issue?
From the thread I understand that there are some work-arounds to the problem, but being able to run the OTF 360 Photo function without positive pitch is not completely satisfactory as part of the sky will be missing from the whole composition, and this is troublesome not only for the composition itself but to being able to publish it in Street View (the aspect ratio of the composition is not met with such a narrow vertical angle).
On the other hand, I could find the custom function that Michael F. designed, but I'm not sure of how to load and run it OTF, is it possible? I'm a Premiun (2020) user.
The absolute best solution would be for a DJI SDK fix, any news on that front?
DJI claims to have fixed this in SDK 4.15 (which currently only supports Android only), but we have not confirmed this.
Hi Alvaro,
yes, the custom function can run OTF. It might be needed to copy the complete repository. The simulation mode in the web-app will show a different start point, but I guess this is normal behavior.
In case DJI SDK fix still takes long time, my suggestion would be to adjust the original Dronelink on-the-fly 360 Photo function in a way that it starts with dynamic input like this:
DYNAMICINPUT.JS
if (variables["StartGimbalPitch"] === undefined) {
const input = new Dronelink.FuncInput()
input.descriptors.name = "Start with current gimbal pitch (move manually upwards to -20 beforehand) or start with horizontal gimbal pitch?"
input.enumValues = ["current", "horizontal"]
input.variable.descriptors.name = "StartGimbalPitch"
input.variable.valueType = Dronelink.VariableValueType.String
input.variable.value = input.enumValues[0]
return input
}
Depending on the input value, the gimbal command for the first (topmost) row could be skipped or set to 0 degree.
Unfortunately I do not know yet, how to handover the input variable to a component, nor how to chose a component depending on an input variable. So I did not manage to create a function for both options. But I am quite happy with the 2 existing functions.
Hello Michael and Jim, thank you both for your responses to my inquiry. Please excuse my delay in answering, I have been off the igrid for a few months.
A few weeks ago I updated my IOS Dronelink App to 2.6.1, which now gives support to DJI SDK 4.15.1.
I've run a few tests, and as far as I can gather, the issue with positive pitch 360 Photo has been solved for Mavic Mini (partially). I run 360 Photo both as: i.) a component in a pre-designed mission, ii.) and as an OTF function. While running it as i.) the Mini took positive pitch photos (12°) without error messages, and completed the mission as expected. While running it as ii.) the Mini finished the OTF function taking all the pictures, but didn't take positive pitch photos, they were limited to 0°.
I figure that the OTF 360 Photo function is still limited to 0° pitch on Mavic Mini as a workaround for the issue encountered before the latest App update, but given that that issue seems to be solved, could it be possible to update this OTF function to be able to take positive pitch 360 photos with Mavic Mini?
Thank you in advance for your guidance.
BTW: Michael, thank you for your suggestion to adjust the script on the original Dronelink on-the-fly 360 Photo function. I tried, but as far as I can tell my current Dronelink plan does not allow it (Premium 2020).
Hi Alvaro,
not sure about the requirements for beeing able to copy and adjust OTF functions. I just have hobbiyst (basic) plan, but I joined in August 2020, so I think I have been "grandfathered".
And yes, I also think it would makes sense to remove the 0° pitch limit from the official Dronelink OTF 360 photo. It would be great, if the upward pitch could be set to 20°, which is the limit for Mavic Mini, but I don't know if this would also work for other drones.
btw: here is my latest 360 photo from a small village in France called Eguisheim, which somehow has a good round shape for a 360 photo ...
https://www.skypixel.com/photo360s/pano-eguisheim-small?utm_source=copied&utm_medium=PCWeb&utm_campaign=share&sp=0
Done
Looks great Michael. 👍🏼
Hello Michael, great picture, thank you for sharing! Eguisheim looks like a lovely village to visit sometime.
Hello Jim, thank you for the update. Already checked the functionality on my Mavic Mini and OTF 360 Photo(s) is back in business!
Please sign in to leave a comment.