Why doesn’t my custom .apj firmware connect to Mission Planner after flashing on CubeOrange+?

ArduCopter Copter 4.6
1

I have built a custom ArduCopter firmware for the CubeOrange+ and successfully generated the .apj file. The firmware uploads without any issues, and the board reboots as expected. However, it does not connect to Mission Planner afterward.

For reference, when I flash the official .apj firmware, everything works normally, and the board connects without any problem.

In my custom build, I have only added a new parameter. Could this be causing the issue?

I would appreciate any guidance or suggestions to help me understand why my custom firmware fails to connect after flashing.

image
image1897×631 29 KB

image
image456×244 13.4 KB

2

Your firmware isn’t sending heartbeat in a way that is compatible with what Mission Planner or inline hardware is expecting.

1 Like
3

Yes, if it is the only change to the original firmware, but without knowing any details all is only guesswork

1 Like
4

Thank you for the support. I found the issue my GitHub working tree wasn’t clean when I built the firmware. :sweat_smile: