Hello, I am currently trying to use a ps5 controller to control the ROV, but I can’t find a way to make my own custom preset. For example, I can’t use the shoulder triggers to throttle and reverse, and I can’t change the joystick to pitch and yaw like I wanted to. I am currently using a navigator board and Q ground Control for 6 DOF because I can’t get cockpit to work either. Can someone help me PLZ?
Thank you!
Hi @Abner -
Welcome to the forums!
QGC isn’t going to work for what you’re trying to accomplish, as far as I know.
The control scheme you describe is definitely unusual, but should be possible to achieve in Cockpit. By “throttle” I assume you mean forwards and backwards movement?
The right joystick by default controls depth and heading. If you wanted to leave the default “strafe” sideways movement on the left/right axis of the left joystick, you could map the forward/backwards axis to pitch (the s axis), and the triggers to forward/reverse.
Some joysticks may not have the triggers appear as axis, but only buttons… if this is the case for the p25 controller, you may not be able to get things working as you desire!
Hi @tony-white Cockpit recognizes the shoulder triggers as a button instead of a axis or potentiometer. and yes by saying throttle I meant to say moving forward. Is there any chance that I can change that to a axis kind of thing?
and isn’t it suppost to be Z axis? for thrust? or thats for motor power?
Hi @Abner
If the shoulder buttons aren’t recognized as Axis, then you won’t be able to use them to control the vehicle motion. Sorry for the news!
The z axis is vertical - x and y are position (fwd/side to side) and r is the heading/yaw. S and T are roll / pitch, as described in the link provided.
I think you’ll find that the normal control scheme, using both joysticks, is much easier than trying to use the triggers would be!
Ok cool! Thanks a lot!
Hi @Abner, welcome to the forum 
I remember having internal discussions about this kind of idea a while ago, but I couldn’t find a place where it was nicely written down so I’ve included it in this Issue, which can be tracked / referred to by anyone interested in this functionality
