I’m having some issues trying to program my pixhawk 3 pro with arducopter firmware. For verification I used QGroundcontrol (On windows) to install PX4 firmware which worked.
What i’ve tried:
Using QGroundcontrol -> install firmware -> APM Stack. The dropdown menu is empty, so I choose advanced settings, and use custom arducopter firmware downloaded from firmware.ardupilot.org (ArduCopter-v4pro.px4, last stable version, as well as the newest). It programs the board and it seemingly goes ok. When I cycle power on the autopilot, there communication possible (no telemetry data) other than reprogramming the device. The LED on the PWM output side does not light up.
I tried to install through Mission Planner as well, both with custom firmware and automatically downloaded firmware. They both go through the firmware install, and say to wait for a ‘beep’ which never occurs then press ok. If I press ok regardless, the board will not connect through the COM port (same as QGroundcontrol) but I can reprogram the device.
Any suggestion as to what might cause this? I googled abit, and I saw a thread with pixhawk 3 pro support from late 2017 so it should be in the stable version of arducopter now?
I put in an SD card while programming, now it seems to be able to program and connect. However, it seems like it’s stuck in some kind of boot loop while trying to initialize the pixhawk. The output from the console window of the pixhawk is
bps 168 loss 0 left 0 mem 28.806640625 mav2 False sign False mav1 4 mav2 0 signed 0 bps 17 loss 0 left 0 mem 29.955078125 mav2 False sign False mav1 1 mav2 0 signed 0 bps 17 loss 0 left 0 mem 30.9775390625 mav2 False sign False mav1 1 mav2 0 signed 0 INFO MissionPlanner.MAVLinkInterface - 12/04/2018 08:53:16 3 Check BRD_TYPE: Baro: unable to initialise driver bps 76 loss 0 left 0 mem 29.2548828125 mav2 False sign False mav1 2 mav2 0 signed 0 bps 17 loss 0 left 0 mem 30.1533203125 mav2 False sign False mav1 1 mav2 0 signed 0 INFO MissionPlanner.MAVLinkInterface - 12/04/2018 08:53:18 6 Initialising APM bps 76 loss 0 left 0 mem 28.5439453125 mav2 False sign False mav1 2 mav2 0 signed 0 INFO MissionPlanner.MAVLinkInterface - 12/04/2018 08:53:19 3 Check BRD_TYPE: Baro: unable to initialise driver bps 76 loss 0 left 0 mem 29.8095703125 mav2 False sign False mav1 2 mav2 0 signed 0 bps 17 loss 0 left 0 mem 31.01171875 mav2 False sign False mav1 1 mav2 0 signed 0 bps 17 loss 0 left 0 mem 29.064453125 mav2 False sign False mav1 1 mav2 0 signed 0 INFO MissionPlanner.MAVLinkInterface - 12/04/2018 08:53:22 3 Check BRD_TYPE: Baro: unable to initialise driver bps 76 loss 0 left 0 mem 30.1103515625 mav2 False sign False mav1 2 mav2 0 signed 0 INFO MissionPlanner.MAVLinkInterface - 12/04/2018 08:53:23 6 Initialising APM INFO MissionPlanner.MAVLinkInterface - doCommand cmd PREFLIGHT_STORAGE 1 0 0 0 0 0 0 bps 87 loss 0 left 0 mem 28.5205078125 mav2 False sign False mav1 3 mav2 0 signed 0 bps 17 loss 0 left 0 mem 29.5439453125 mav2 False sign False mav1 1 mav2 0 signed 0 INFO MissionPlanner.MAVLinkInterface - 12/04/2018 08:53:25 3 Check BRD_TYPE: Baro: unable to initialise driver bps 76 loss 0 left 0 mem 30.80078125 mav2 False sign False mav1 2 mav2 0 signed 0 bps 17 loss 0 left 0 mem 28.921875 mav2 False sign False mav1 1 mav2 0 signed 0