QGC 4.4 Issues List

[rmackay9]

This is a consolidated list of issues related to the 4.4 beta release.

• AP community beta announcement is here.

Reports requiring investigation:

• [ ] Camera and Video controls are not working with AP
• [ ] "Point Home" appears not to use the correct altitude (camera points up) -- reported by Randy

Confirmed issues:

• None

Enhancements or Issues that may not be resolved before the stable release:

• [ ] Sluggish movement when both PC & Herelink controlling gimbal -- likely inputs from two ground stations
• [ ] Herelink click-and-drag not working -- reported by HenryW -- likely inputs from two ground stations
• [ ] ROI should support inputting an altitude -- reported by Randy
• [ ] With multiple gimbals, "Select Gimbal" should also change the video stream shown

Resolved issues:

• [x] "Point Home" ROI can't be cancelled, remains on map -- reported by Randy -- can be done, click on label
• [x] Cannot trigger recording video from the camera controls when using Siyi A8 --- reported by Randy, HenryW. Fixed for -rc4
• [x] Herelink HDMI1 / HDMI2 selector not working -- reported by Randy, HenryW -- cannot reproduce
• [x] Herelink video not working -- reported by Randy and JulianO
• [x] ROI controls are not clear -- reported by Randy -- requires vehicle to be armed and flying

[timtuxworth]

I've noticed hangs and crashes on both Mac OSX and Windows 11 when connected to a vehicle (real and SITL) via UDP

[vacoff]

I came across some other issues. The gimbal icon is missing in all of the v4.4 release candidates. I am using gremsy gimbal with cube orange px4 v1.14

[julianoes]

@vacoff can you post a screenshot?

@timtuxworth any chance you can give tips how to reproduce the crashes, or get crash reports?

[timtuxworth]

@vacoff can you post a screenshot?

@timtuxworth any chance you can give tips how to reproduce the crashes, or get crash reports?

The only thing special I do is I usually use UDP to connect to my vehicles - this is usually SITL but I also do this with real planes.

It's pretty easy. Just start QGC and use it for a bit. I run SITL for a while doing some testing. It will hang after a while and then you are forced to close it. I make sure to press the "report to Microsoft" button. You should be able to go to your Microsoft dev account and review the crash logs.

Actually the same thing happens on my Mac too. It's very unstable it shouldn't be hard to reproduce.

[julianoes]

You should be able to go to your Microsoft dev account and review the crash logs.

No idea how this would all connect. I rarely use Windows.

That being said, I assume QGC v4.3.0 works nicely and doesn't have the stalls and crashes?

[timtuxworth]

I have no idea. I usually use the daily build which has always worked for me on both windows and Mac.

[rmackay9]

@timtuxworth @julianoes,

I have not seen QGC 4.4 lockup or crash. This includes running it on Windows 11 using UDP or USB to real vehicles.

@timtuxworth, could you just confirm that you're using QGC 4.4-rc3? If the crashing issue involves another version (like 4.5) I'd like it if we could move the discussion to another thread or issue so that we don't muddy the waters of the 4.4 beta testing.

[julianoes]

@rmackay9 I had a look through the issues you mentioned:

Sluggish movement when both PC & Herelink controlling gimbal

This one is tricky. I think it comes down to several points:

• Are both QGC sending with the same sysid/compid? If so, that's not a valid use case, in my opinion.
• If not, how are both sending signals? Commands, or using the wheel/buttons? Basically, the gimbal protocol has the notion of "in control", so in theory it shouldn't really be possible to have two ground stations both controlling the gimbal, unless one is primary and one is in secondary control. The exact behaviour in that case is then implementation specific.
• In the current ArduPilot case, I believe "in control" is not implemented yet, right? If so, that would potentially explain conflicting/sluggish behaviour.
• When I tried this with PX4 (using different sysids for the two QGC instances). I had to manually "release control" in order for the other QGC to "acquire control". Otherwise, it would not work. (A user warning for this case would be a nice to have in the future.) Mixing RC and MAVLink gimbal input did not work, presumably that's a PX4 issue.

Herelink click-and-drag not working -- reported by HenryW

This would depend on the setup. It worked for me, although very slowly. And I'm not sure if it's the right way around. Could it be inverted? Maybe @Davidsastresas you can clarify: is it supposed to move with my finger? E.g. I point and move my finger the right and expect the camera to pan left?

"Point Home" ROI can't be cancelled, remains on map -- reported by Randy

I can confirm that. I'm not sure how to fix that one. @Davidsastresas hints would be appreciated.

"Point Home" appears not to use the correct altitude (camera points up) -- reported by Randy

This seemed correct with my testing with PX4. I'd check what's going on in: https://github.com/mavlink/qgroundcontrol/blob/Stable_V4.4/src/Vehicle/Vehicle.cc#L2869-L2912

[vacoff]

@vacoff can you post a screenshot?

@timtuxworth any chance you can give tips how to reproduce the crashes, or get crash reports?

this screenshots are from release candidate 4.5 but the issue is still ongoing, even though the gimbal control works ok from both console and the rc input

[Davidsastresas]

• About cancel ROI when "ROI home" action, it can be done. The area clickable is not only the "waypoint icon", but also the label. If you click the label that popup to cancel ROI will appear:

• About click and drag, I am thinking on disabling it for the moment. In android it is not working as it is supposed to, and I think it is prone to missunderstand how it works. It is basically a virtual joystick occupying the whole screen. I played around with inverting the direction as some comments suggested, but it wasn't natural, it wasn't feeling like when you pan a map, because the camera isn't tracking the position really, is being controlled by speed on that command.

So I think it is better to disable it for now, and come back to it in the future with more time to test it maybe. Any thought on this?

• About the crashes, I can't comment about Macos, but me and my team use this regularly in Linux and Windows 10 and 11, and we haven't seen any crash lately. A few months ago, a crash bug was discovered related to joystick, it would only make QGC crash if a joystick was present and connected, but all these 4.4 release candidates have the patch, as well as master. So we really need more information about exact versions, etc to try to reproduce.

[julianoes]

@vacoff ah, so the gimbal doesn't get detected in your case. Now I understand. What is the MNT_MODE_IN param set to?

[rmackay9]

Hi @Davidsastresas,

I think we should leave the click-and-drag in. I think it works unless there are two ground stations connected at which point they interfere with each other. I think it does no harm to leave it in.

I vaguely remember (I think) that you said it was implemented using angle control, I think we should change that to use rate-control (which DO_GIMBAL_MANAGER_PITCHYAW supports) but I think we could do that for QGC-4.5.

[julianoes]

@vacoff I think I have found an edge case in PX4 that causes GIMBAL_MANAGER_INFORMATION not to be sent out and hence QGC not detecting the gimbal. I'll have a fix soon.

[julianoes]

@vacoff can you test with this PX4 branch: https://github.com/PX4/PX4-Autopilot/pull/23236

[vacoff]

@vacoff ah, so the gimbal doesn't get detected in your case. Now I understand. What is the MNT_MODE_IN param set to?

it is set to mavlink v2

[vacoff]

@julianoes just tested with the pr you said. GImbal icon is now appearing on the QGC but when I try to command it the error on the second picture is appearing. it is v4.4 rc5. It seems like it is stuck on the yaw follow mode and doesn't accept commands to change its mode also the on screen control doesn't work. it reacts to the "gimbal test" commands.

btw I have changed hardware from cube orange to cuav nora as wouldn't like to fly with un-official firmware just to be safe. But I am not sure if this would make any difference.

[vacoff]

After rebooting the autopilot the gimbal manager command rejection error disappeared, but the whole logic of the commands on QGC is working kinda weird. For gimbal is on yaw follow mode in default. After pressing yaw lock it locks it in place until another command is activated such as center or tilt 90 degrees then it reverts to the yaw follow mode. And the yaw lock mode makes gimbal twitch in the yaw axis, it doesn't lock stable

[julianoes]

@vacoff I'm glad you got it to work (somewhat).

And the yaw lock mode makes gimbal twitch in the yaw axis,

I think that's a gimbal issue. I'm assuming this is using the SIYI A8 mini? If so, I see the same.

After pressing yaw lock it locks it in place until another command is activated such as center or tilt 90 degrees then it reverts to the yaw follow mode.

That's by design. I don't think locking at 90 degrees down would make sense. And when you click center you want to have it look forward, so it shouldn't be locked anymore either.

[vacoff]

I think that's a gimbal issue. I'm assuming this is using the SIYI A8 mini? If so, I see the same.

I am using Gremsy Mio. It seems like gimbal is switching between yaw lock and yaw follow modes fast, so it causes twitching.

[julianoes]

@vacoff that's interesting. Do you know what's sending it follow commands?

[julianoes]

@vacoff I verified this and I can't see the effect, at least when using PX4. It either sends with or without yaw lock. There is no switching between the two modes in my testing.

Let me know if there is specific way to reproduce it .