I’m relatively new to the px4 community and have found myself with a few confusing problems. I am working with a generic “x” quad build and a px4fmu(v1.7) standalone. I have been relatively successful in the general set up of the vehicle (via micro SD card - things like the config. file, etc.) but I am having a difficult time when I go to fly the quadrotor.
The problems first start with qgroundcontrol (v 2.8.0) and flashing firmware to the fmu. When I go to flash the firmware, the bootloader recognizes the px4fmu, tells me how much “flash” is available and then proceeds to just “sit there” until I unplug the USB cable. I was able to flash firmware with an older version of qgroundcontrol, but not with this most recent update. Additionally, if I attempt to flash “custom” firmware (px4fmu-v1_default, etc.); I am not able to flash px4fmu-v2_default. Instead, the terminal begins repeatedly printing that it found device and never erases/flashes the new firmware - I am, however, successful with flashing px4fmu-v1_default - is this a problem or is this behavior correct?
Regardless of my possible firmware problem, my main issue is with attempting to fly the quadrotor. I have double (even tripple) checked the hardware, rotor configuration/numbering and rotational directions as well as ensuring that the px4fmu is calibrated and displaying the correct artificial horizon. However, when attempting to takeoff, the vehicle always flips. I am trying to fly the vehicle through a USB controller and qgroundcontrol, but with no luck. I can see that the commanded pwm outputs from the px4 (through the analyze widget in qgc) do not seem correct. The chip will often command non-symmetric pwm outputs when in manual mode and I have, overall, had more success in attempting to control the quad when enabling ACRO mode - although even this mode does not give me total control of the throttles. I have been able to “tether” the quad and see that the roll, pitch and yaw commands seem to work 100% correctly when in ACRO mode (even manual mode), but not the throttles (I cannot get them below a pulse width of 1500 micro seconds). I have looked around quite a bit for solutions to this/these problems but haven’t been too successful in finding a general solution that would work for me. Does anyone know of any possible solutions/experienced similar issues to this with a px4fmu?
Thanks in advance,