Hey @Eric-Katzfey @James-Strawson ,

Thanks a lot for helping me with the integration of my VOXL2 with Cube Orange. It is working well. I am also using it with the ToF, HighRes, and tracking camera from ModalAI.
Position hold using VIO and Semi-Autonomous (VOA) are also working well.

Now, I am facing an issue with the offboard mode. The moment I switch to offboard, the drone aggressively moves and crashes. (in both "figure_eight and "trajectory"). [In the offboard mode = "off", I am not able to switch to offboard. ]

There are no error messages in QGC or otherwise. Except offboard everything else works.
Could please help with this issue?
I'm working on this as a priority, so any suggestion will be quickly tested. I hope to hear from you.

Thank you

We have been looking out for VOXL Time of Flight (TOF) Depth Sensor from ModalAI products page to integrate with our VOXL2 board. But the sensor is currently unavailable for the critical time period.

The sensor provided is ToF Depth sensor from PMD. Could the same sensor module provided by PMD(ie. PMD Flexx2 3D Camera Sensor module) be directly integrated with VOXL2?

@Eric-Katzfey Thank you for reverting back, The options only show one option button 1. I tested with button one but the drone was not taking in the command for enabling the turtle mode.
I want to know whether the code was tested out, so that I can be sure about not missing out on any parameter or setup

@Eric-Katzfey Hey hope you are doing fine, I checked the code and various branches of PX4, I noticed I was able to see the parameter VOXL_ESC_T_ON but the option only showcased button 1 for assignment . what to do if I want to assign another button.

Hi @Vinny, @Alex-Kushleyev,

Thank you once again for your valuable feedback on the schematics, and apologies for the delayed response.

I’ve now completed the PCB layout based on the updated schematics and newly selected components, as per your suggestions. I would greatly appreciate it if you could take a moment to review the layout and share your feedback—particularly on whether it meets the required configuration or if any modifications are recommended.

The following have been included in the shared Drive link:

Screenshots of all four layers

3D views of both the top and bottom sides of the board

Drive link: https://drive.google.com/file/d/1czCx-N8ws3CelpKTV1VRBTzFZLcd-odx/view?usp=drive_link

Looking forward to your insights.

Thank you again for your continued support and guidance.

@KLindgren thank you for reverting back. From which port are you taking the 3.3 V also how did you complete the circuit, the image you provide is confusing with respect to the connections, it would be great if you would provide further details.

@KLindgren I am also using the same board but my video stream is with high disturbances, i have posted a image above in the chat. could you please share the image from your camera so that i could figure out what is wrong with my setup. Also the details of your setup, it would be of great help.

@Eric-Katzfey COM_RC_IN_MODE is set to joystick only

@Alex-Kushleyev , I will backtrack the steps and try re-configuring the setup.

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

@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

@Alex-Kushleyev I have already tried it, It was working fine earlier. since past 2 days the behaviour has changed, I have verified everything else and nothing else could be a reason for such behaviour , I even played around with delay to verify it, still the same issue.
please excuse me for repeating the questions but is there any other reason that can cause this issue.