Gimbal fails to respond to gimbal pitch changes issued by markers
DJI Air 2s
dronelink Android 3.3.0 (185) kernel 3.3.1
OTC cable connected to RC
I've created several missions with waypoints and even POI with various changes to gimbal pitch. All have worked flawlessly and matched preview.
I created a new mission and this time it seems that the gimbal pitch changes with markers are ignored. The flight preview works fine with multiple pitch changes--just like previous missions.
This time is different. I start with approach gimbal pitch at -81; that works and the gimbal stays at that pitch ignoring marker changes. I think this is the first time I started an approach with gimbal pitch as low as -81. I didn't try with a different gimbal pitch. Also, during the flight I can change the gimbal pitch with the gimbal wheel and also when using the DJI Fly app.
Is there a way to check gimbal control without actually flying?
The drone heading, altitude, and speed changes all worked.
Comments
27 comments
It sounds like you are running into the 2nd issue described here. You are saying you ran missions with velocity based gimbal movements on the Air 2S before? That has never been possible.
I don't have any velocity statements for gimbal pitch. After the initial pitch down to -81 there no gimbal movements. I had a similar type of mission on 14 Feb where the gimbal pitch slowly or rapidly moved as the done passed through waypoints and markers. It was just as on the preview for that mission. Gimbal movements on previous missions were also flawless. I can't find anything different.
Gimbal pitch changes are also curved--always.
As for the off course, I looked through the AirData records and also Dronlink preview and both off courses happened at +13 f/s vertical, so I know the cause of that and know in future the drone can handle high speed climbs it causes issues with Dronlink. That I can fix.
As there a change in the Android app version or a change with the web app?
Can you post a link to a mission that worked and one that didn’t?
Is it possible that gimbal change speed set with the DJI Fly app limits the dronelink gimbal pitch changes? Could the entire string of gimbal pitch commands fail if the first one from -81 to -75 as the -75 never happened.
I might have updated the DJI Fly app recently, like before this mission. I updated something. The app is 1.5.10 and the Air 2s firmware is 02.04.2130..
Firmware is up to date.
How do I post a link?
Do I need to make it public?
OK. see if this works for the link. This is one which works:
https://app.dronelink.com/david-e-ritter/ritter-public/plan/TtlmhgznRQZKRBB6Yh1x/PH3pmgmccuQUMmL9zUo4
This is the one which failed to move the gimbal
https://app.dronelink.com/david-e-ritter/ritter-public/plan/ttAfWqeSCTF86fQsrYNE/gYKPSAJxPizhqy7ByaG8
Do you have the video from the one that is working? Supposedly DJI is going to fix the gimbal telemetry issue in the next firmware update. Did you somehow manage to get the beta firmware?
Here is the marina one--the good one. It's been edited with removal of approach and ending. The rest is uncut as it was so perfect.
https://youtu.be/0k8Rl6MU4C4
I added the music and text. My other YouTube videos with Dronelink, except the first 2 I think.
I didn't get any notice of any beta firmware; I just downloaded what
DJI Fly said was an update.
The gimbal pitch is not changing in that video.
It does change with the point of interest at the kayaks and up around the marina patio. There were constant slow gimbal pitch changes thorough.
In planning that mission I did a lot of gimbal pitch changes with markers with curved interpolation and they all executed well. I set a different pitch for the dragon boat POI.. When I found it didn't match up the preceding interpolate degrees I adjusted a marker pitch until the transition was smooth on preview. It all executed flawlessly for the flight.
With the start of the video as the drone descends towards the marina the gimbal gradually pitches up. Across the bridge the gimbal pitch is up a little more for a down close view.
Just check DJI Assistant: Firmware V02.04.2130 from 28 January 2022. Release notes: fixed some bugs. No option to roll back and no notes about beta.
I'm not exactly sure which part of the video you are talking about, but I don't see it changing. The bug is that the DJI SDK does not report the gimbal telemetry right now, so Dronelink has no way of issuing velocity based gimbal commands (the type of commands that are sent when smoothly rolling the gimbal). Dronelink is able to snap the gimbal to specific pitches (such as at the start of Paths or Maps), but that is it. We have never been able to get it to work with the current firmware and DJI says they will be fixing it in the next update.
When I do a mission preview it shows constantly changing gimbal pitches, I assume calculated by Dronlink for smooth movements. I would assume dronelink to just sent constant numbers to the drone, like "snap to" numbers every second so the movement appears smooth.
I purchased my Air 2s 12 January; it would have had the previous firmware. I'm not sure when I Updated the firmware but it's possible that it was after my 14 February good flights. This would mean the previous firmware was good and the bug fixes messed with the gimbal issue to make it not work.
I guess I'll just wait a bit for another mission or just plan the gimbal pitches but be ready for manual control--not so smooth.
I got used to dronelink but smooth gimbal movement is essential to my film making. I just don't get why it worked before and not now. Litchi supposedly has good interpolation for gimbal pitch so that might be my next learning curve..
I don't see any gimbal changes in the video - I see the altitude changing, but not the gimbal. It's possible it's there but too subtle for me to see?
The simulator is going to do what it expects to happen - it is not going to take into account the defect in the DJI SDK as far as I know.
The changes are there. When flying a mission it's important maintain proper coordination between altitude and gimbal pitch so the viewer sees it as a pleasing smooth view. When descending your eyes have a certain focus point based on a sight distance from you eyes to that focus point. So, maintaining a constant sight distance (hypotenuse of right angle triangle) while descending the altitude (b leg of triangle) decreases so the gimbal angle down becomes smaller. It can actually be calculated with trig functions. In realty the sight distance will be adjusted by your brain and I can't figure a number for that in my functions. Keeping the gimbal action smooth and making a small movements to match altitudes casual viewers won't notice that there was really a gimbal change.
I can use a reference to flying a small. Approaching to land the pilot looks at the runway with a certain sight distance. As the plan comes closer to the runway the pilot looks further way to maintain a similar sight distance. Keeping a down view means more likely to fly into the runway. Your eyes are the gimbal and need to change pitch too keep the view (and landing) correct.
If you bring your drone down without raising the gimbal the viewer will get the feeling of flying into the ground, so keep the gimbal pitch adjusted match what you expect your viewers to see and feel.
The changes are there. When flying a mission it's important maintain proper coordination between altitude and gimbal pitch so the viewer sees it as a pleasing smooth view. When descending your eyes have a certain focus point based on a sight distance from you eyes to that focus point. So, maintaining a constant sight distance (hypotenuse of right angle triangle) while descending the altitude (b leg of triangle) decreases so the gimbal angle down becomes smaller. It can actually be calculated with trig functions. In realty the sight distance will be adjusted by your brain and I can't figure a number for that in my functions. Keeping the gimbal action smooth and making a small movements to match altitudes casual viewers won't notice that there was really a gimbal change.
I can use a reference to flying a small. Approaching to land the pilot looks at the runway with a certain sight distance. As the plan comes closer to the runway the pilot looks further way to maintain a similar sight distance. Keeping a down view means more likely to fly into the runway. Your eyes are the gimbal and need to change pitch too keep the view (and landing) correct.
If you bring your drone down without raising the gimbal the viewer will get the feeling of flying into the ground, so keep the gimbal pitch adjusted match what you expect your viewers to see and feel. When flying 20-35 ft above surface I will often change gimbal in the area of -23 to -28 to match what I want for the view.
I looked at my marina video again and didn't like my initial gimbal pitch heading down in the water; it looked like I was going into the water. I should have started the upward gimbal movement sooner to match rapid descent.
Jim, I just updated my Air 2S firmware to 02.04.2150. Do you think that will take care of the gimbal pitch issues with markers? I haven't had a chance to fly a mission yet to check it out.
We tested it this morning and it does correct it. Build 190 has the fix to take advantage of it.
Thanks, Jim.
My dronelink app shows 3.3.0 (185). I assume I need to update to (190) but the app doesn't seem to have an update option and Google Play doesn't either. What am I missing?
Still waiting for TestFlight approval.
i have a complex mission ready to go for a test--8 minutes with orbit, altitude changes, heading changes, speed changes, and gimbal pitch changers. This is my first mission with a list of several components, including 2 paths.
Jim,
Any idea when the new app build will be available? When is will it just be a new install from Play Store (Android)?
I finally figured out how to get the beta update which is 3.3.1(191).
I did a short test today with varying gimbal pitch changes with markers and it works. Nice.
Now I can do my larger planned missions.
Please sign in to leave a comment.