doodle labs and joystick setup

Eric Katzfey

@Jetson-Nano voxl-fpv-dev is the name of the branch. The version will be a number, such as 1.14.0-8.104.3. Most of the joystick button mapping is handled by QGC directly. It maps them to commands that are sent over Mavlink. But the turtle mode is something specific built into the ESC driver. For the joystick buttons to work for turtle mode you need to set VOXL_ESC_MODE to 1. For newer versions of the voxl-fpv-dev branch you can also set VOXL_ESC_MODE to 2. The verify that the button mapping is working you can look at the manual_control_setpoint topic in px4 and see if the aux1 / aux2 fields are changing between 0.0 and 1.0. (e.g. px4-listener manual_control_setpoint)

Jetson Nano

@Eric-Katzfey Thank you for the support. I will test it out and get back to you encase of any further queries.

Jetson Nano

@Eric-Katzfey
I tested what you asked me, since i am using external Fc and doodle labs, I am not able to assign AUX to any button, is there any work around on how to assign AUX

Jetson Nano

@Eric-Katzfey @Alex-Kushleyev
hey guys, just a random thought, can I enable turtle mode through a button instead of taking AUX 1 into consideration. just a thought, any guidance and help would be greatly appreciated.

Eric Katzfey

@Jetson-Nano What do you see if you go to the MAVLink console in QGC and look at the manual_control_setpoint topic? (listener manual_control_setpoint)?

Eric Katzfey

@Eric-Katzfey Also, there is a parameter called VOXL_ESC_T_ON. How is that set? It determines which button will be used for turtle mode. The code is here: https://github.com/modalai/px4-firmware/blob/ea098200d3c09b7af548bf7be29fda245fad8f17/src/modules/mavlink/mavlink_receiver.cpp#L2083

Jetson Nano

@Eric-Katzfey
This is the output i am getting while running listener manual_control_setpoint

NuttShell (NSH) NuttX-11.0.0
nsh> listener manual_control_setpoint

TOPIC: manual_control_setpoint
 manual_control_setpoint
    timestamp: 438754659 (0.033455 seconds ago)
    timestamp_sample: 438754653 (6 us before timestamp)
    roll: 0.00000
    pitch: 0.00000
    yaw: 0.00000
    throttle: 0.00000
    flaps: 0.00000
    aux1: 0.00000
    aux2: 0.00000
    aux3: 0.00000
    aux4: 0.00000
    aux5: 0.00000
    aux6: 0.00000
    buttons: 0
    valid: True
    data_source: 2
    sticks_moving: False

nsh> listener manual_control_setpoint

TOPIC: manual_control_setpoint
 manual_control_setpoint
    timestamp: 446282690 (0.039850 seconds ago)
    timestamp_sample: 446282683 (7 us before timestamp)
    roll: 0.00000
    pitch: 0.00000
    yaw: 0.00000
    throttle: 0.00000
    flaps: 0.00000
    aux1: 0.00000
    aux2: 0.00000
    aux3: 0.00000
    aux4: 0.00000
    aux5: 0.00000
    aux6: 0.00000
    buttons: 0
    valid: True
    data_source: 2
    sticks_moving: False

Jetson Nano

@Eric-Katzfey I am not able to see the option you have mentioned VOXL_ESC_T_ON

Eric Katzfey

@Jetson-Nano said in doodle labs and joystick setup:

I am not able to see the option you have mentioned VOXL_ESC_T_ON

In the Mavlink console what do you see with "param show VOXL_ESC_*"?

And what about "ver all"?

Eric Katzfey

@Jetson-Nano said in doodle labs and joystick setup:

This is the output i am getting while running listener manual_control_setpoint

What is the parameter COM_RC_IN_MODE set to?