-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Description
Have you checked the latest release for fixes?
- Yes, I’ve tested on the latest release
Description
Expected Behavior
Unable to use Steamdeck with QGC to control ArduRover (4.6.2) with its 2 Joysticks on QGC 5.0.5 (or earlier)
Have simulated it with QGC connecting to SITL instance, so not hardware related.
when using ArduRover allows only two Joystick Axis CH1(yaw) CH3(throttle) and no other RC_channels available
when using ArduCopter will allow CH1-4 so its ArduRover specific.
This is a showstopper for using QGC at least with Steamdeck Joystick for Rovers as more channels are needed.
Have worked around the problem by sticking with mission planner (requiring windows) on steamdeck.
QGC is excellent - except for this showstopper.
Current Behavior
Describe what actually happened here.
Steps To Reproduce
- install QGC on Steamdeck via flatpak install
- run QGroundControl.exe
- calibrate and configure joystick
- connect to model via TCP 192.168.1.123 port 5760
- only forwards/backwards left/right ch1 & ch3 are available for mapping/usage - others not available
- Lawnmower functionality not possible, as i need to control more channels (deck up/down) gimbal etc
- Mapping buttons and Mavlink custom actions is possible, but only 1 time actions, not AXIS type levels.
Additional Details
QGC is a good fit for ArduRover mowers - but not with such RC_channel limitations. Hoping to revisit it.
Note - mission planner allows all channels, Cockpit has same restrictions as QGC, not sure where the restriction is
System Information
QGC 5.0.5 (and i believe 4.x before it)
OS SteamOS on steamdeck - current version (not sure)
Flight Controller Qiotek Zealot H743 - working fine with Mission planner on Steamdeck/Joystick
Ardurover 4.6.1 and 4.6.2
Log Files and Screenshots
No response