Hi, A friend and I are undertaking a university project using a pixhawk in a bixler 2 airframe. We have modified Arduplane version 3.03 and are attempting to upload it via mission planner using the px4 toolchain build method - http://dev.ardupilot.com/wiki/building-px4-with-make/.
We are able to upload standard code using this method but when uploading the .px4 file through mission planner which contains our modified code a couple of things happen:
1. The board makes the start up sound after upload, not the successful upload sound it should.
2. The main led is a mixing of blue and red - solid pinkish colour.
3. And we are unable to connect to the pixhawk using mission planner - telemetry or usb.
It seems to us like it is hanging in the final stages of uploading.
We have added three new navigational controllers to the code as library .cpp files - as children of the navigation class based on the existing L1 control library. We've also added a library to achieve uart data transfer to a Raspberry Pi over serial port 4, which we believe to be unused as UartE in the code.
This uart connection worked great on a APM 2.5 board where we utilised UartC for communication. Unfortunately that board stopped working, hence the upgrade to the pixhawk.
Thanks in advance if you can shed any light on our issue.
Replies
Have since solved the problem. We had defined group info objects within the different controller classes but had given each the same idx number rather giving them consecutive numbers.