Is there anyone who had experiences with a total communication interruption for app. 5 sec. during the deployment of a blue-rov2? When the connection established again, the video record was smashed.
Has someone ideas to avoid something like that?
Is there a possibility to deploy the trigger-buttons (LT/RT) It would be makes sense.
Most likely this is a powering issue, although it could also conceivably be a tether strain issue if the tether is pulled hard by the vehicle, or could be caused by strong electrical noise disrupting the signal through the tether.
I believe on x-box controllers these register as axes rather than buttons, and currently can’t be assigned button functionalities. The equivalent buttons on playstation (dualshock) controllers do register as buttons, and I’m not sure what happens for other controller types.
If this is an important feature for you you’re welcome to submit a GitHub issue, but there’s no guarantee of when the QGroundControl developers will have time to look into it and implement a fix.
Hi Eliot,
Where you say “I believe on x-box controllers these register as axes rather than buttons, and currently can’t be assigned button functionalities. The equivalent buttons on playstation (dualshock) controllers do register as buttons, and I’m not sure what happens for other controller types.”
I have just bought a PS DualShock controller based on this and these buttons show as axes in QGC as standard. How did you manage to configure them as buttons, please?
Xbox & PS as per type discussed above.
Neither controller working on the desktop app on windows or MacOS. Both controllers showing in the settings but not working. Both controllers work when running the BlueOS Cockpit extension. Been discussing issues with @rafael.lehmkuhl on the cockpit forum post