@Jetson-Nano If all that seems to be working then press the turtle button and arm (with drone right side up, not upside down) and verify that with turtle mode enabled the propellers are spinning in the opposite direction and the drone won't lift off. Of course, you must be extremely careful when running this test!!! Make sure that the drone is in a location where it cannot cause damage or injure someone if it goes out of control. It would be best to completely remove the propellers and just verify that the motors are spinning in the opposite direction of normal flight.

@Jetson-Nano Let's try to walk through this and see where it is going wrong. Please provide answers to all of the following questions. Go to the joystick tab in QGC and press the button on the joystick that you want to use for turtle mode. Which number lights up when you press the button? Next, go to the MAVLink console and provide the output of these commands: ver all, listener manual_control_setpoint, param show VOXL_ESC_MODE, param show VOXL_ESC_T_ON, and param show COM_RC_IN_MODE. If VOXL_ESC_T_ON is not set to the number of the button you just discovered on the joystick tab then change it to the value you want. For example, by default VOXL_ESC_T_ON is set to 9. If you want to use button 10 instead then do param set VOXL_ESC_T_ON 10. If you had to change that parameter then reboot and verify that it is now set correctly. You should see the aux1 value in manual_control_setpoint change from 0.0 to 1.0 when you press the button that you have chosen. Can you verify that you are seeing that?

Hi @hula
YOU ARE CORRECT!
I found a whole bag of mis-wired MCBL-00010's in our inventory.
I'll work with our @Moderator to figure out a plan.
We will likely need to setup an email where any customer can let us know if they have offending cables and we will send replacements promptly.

@ashwin Can you differentiate each drone based on the drone's IP address? Those will be unique.

@Ansel-Misfeldt Please take a look at this post: https://forum.modalai.com/topic/4653/uavcan-error-while-building-px4-firmware/2?_=1755096615166

Hi @hula
Interesting. I will investigate. The cable appears as it should according to our tech docs and every batch is sample tested but I will inspect further and respond tomorrow.
https://docs.modalai.com/cable-datasheets/#mcbl-00010
Thanks
Vinny

HI @Jetson-Nano
Your welcome. Apologies I cannot find anything blatantly wrong with your design at the document and layout level.
If your PCB still does not work after all these reviews and positive affirmations, then you may very well have a fabrication issue with your PCB.
The only way to verify that is to try your own net-by-net buzz-out using a DMM to ensure your netlist matches the expected schematic. If that all matches up, then you may be suffering from poor assembly/soldering. The socket for the lepton does require a reflow oven/line and cannot be hand soldered, unless you have an IR tray/heater and a way to deposit solder paste on the pads.

Any further debugging I could offer would require physical samples of the hardware to validate everything.

Hope that info helps!

Hi @Jetson-Nano I have reviewed your schematic again and your layout files.
I cannot see any reason why your design will not work.
The only suggestion I have is to increase your capacitors here to 1uF:

But, otherwise, your layout is OK (some improvements can be made, but nothing is detrimental):

• Pin 1 correct on connector, socket, LDO, other ICs
• Vias are picking up planes correctly
• Voids where expected
• Generous copper trace thickness

The one issue I think I might have found is your reference designators do not match the schematic between the layout. So, I'm wondering if you are installing parts from the BOM in incorrect locations...
For example, the cap on the output of the LDO is "C6" in the layout, but "C7" in your schematic:

And, your resistors are also not in sync. R1 and R2 in the layout are for the Ic2 expander, but in the SCH, it is for your FLIR module and not R5/R6 as in the SCH:

and there are a few other examples. So, I just think perhaps your layout reference designators are not synced to your design.

J1 should be J2, and R3/R4 on the layout does not exist on the SCH.

So, maybe this is where your issue is. I'd recheck the annotation between SCH and Layout, and be sure you are installing all the correct parts in the correct places.

Hope this helped!
Keep us posted.
Thanks!

Hi @Jetson-Nano
I received your data package and will review it this evening.
Thanks!
Vinny

Hi @Michael-Mortensen
Please see the post to Victor about using the power module instead of just USB.
Let us know if that helps.
Thanks!