@Alex-Kushleyev Found the reason why it was skipping. In /px4-firmware/src/lib/parameters/CMakeLists.txt there is a line that skips all modules that match 'pwm_out'. I was able to disable that for PCA9685. Once I disabled the module.yaml file being skipped it worked. No need for the .c file (which makes sense, that is just the old way to do the .yaml)

@Alex-Kushleyev This was what I got when opening the file in SolidWorks:
a3f8d672-9ddc-465e-85c5-f40e6203ce29-image.png

I found a symlink mismatch in the file tree... pushing M073 PCB board with M0172 connector.

Anyway, it is solved now:

8f13ae56-bfcd-4829-8bd1-e238097e9bb0-image.png

Thank you.

Regards,
Jacob

@lhermosillo It was 15 with/without the GPS.

@Alex-Kushleyev
We are designing our custom adapter board which will have mating connector DF56C-26S-0.3V(51) on board to connect MSU-M0186-1-09 camera module.

And we are planning to test synchronicity with other camera. So just wanted to confirm master or slave mode is configured from firmware or is there any dependency on hardware is well for this configuration.
let me know if more details are needed.

Regards,
Richa

@tejasram The source code is here: https://gitlab.com/voxl-public/voxl-sdk/services/voxl-tag-detector. Perhaps try changing #define MAX_TAG_LOCATIONS 64 in locations.h.

@taiwohazeez This is what most people use: https://qgroundcontrol.com/

@ggangmi What was the flight mode on takeoff and what did it unexpectedly change to? There should be logs in /data/px4/log. They may be incomplete or maybe even corrupted if the drone lost power in the crash but there should be something there. The logging starts when the drone is armed.