Hello all, thank you for your support. Sorry for the delay in getting back to you all, I have been quite busy at work. Also I have to crash land the quad on Monday the 02 Dec 2019, and counting the cost of damage.
Dave I am running the same firmware version 1.9.2 on the flight controller. My PC’s both run Win7, and I am running QGround Control V3.5.5 on both. My R/C is Version: Development master f25149835 2019-04-26 18:59:47 +0530. R/C Make is Herelink Beta 1, yes it runs QGround Control as well.
Hardware is Holybro Pixhawk 4 mini with Holybro Pixhawk 4 M8N GPS Module from getfpv.com.
What I have noticed so far on Monday the 02 Dec 2019:
I get the this error (Critical Reject position Control) when I arm the quad on my test bench, and I do not get this error if I place the quad on the ground in front of my house.
When this error is triggered I am unable to enter into Position Mode which I like to fly my quad with.
I was able to select Position by placing the Quad outside the home on the ground see the log stamped with 11:00 AM.
So I decided to take the quad to the field and test it after doing all the checks and putting the props at 2:00 PM the same day. On the field on initial boot-up, the same error prevented me flying. So I decided to move my position in the field and re-booted the flight controller. This time the error did not come up and I wanted arm the quad and arming was denied due to compass inconsistence. So I calibrated the compass in the field and re-booted the flight controller.
I was able to arm and choose Position Mode without any errors. So I used the auto take-off and the quad reached about 2m height, but it did yaw clock wise once and struggling to hold position.
I decided to bring the quad back and selected the RTL button and the quad rose to set 20m height and was struggling to land. So next I selected the Land button and the quad rose even further, and I tried to bring it down by lowering the throttle and I had no response.
The quad gained more height and was drifting away from me, so I had no option but to apply the Emergency stop, crashing the quad to the ground from around 40m high.
During the flight I also observed effects of vibration on the flight controller. I have had this vibration effect during my initial testing at home, as recommended I was using the vibration isolation pads provided with the kit during my initial test at home and the pads made the vibration effects worse and the motors were cutting out. So I placed the flight controller on double sided tape, and mounted it to the frame, and this stopped the vibration effects on my initial try at home. Is there a better way to isolate this vibration problem?
I am rebuilding the quad, I made the frame and it will take time to make the broken pieces and to replace the broken components. But my biggest concern is reliability of Pixhawk 4. I was using Cube Black and Here 2 by ProfiCNC, and encountered reliability issues with the cube black flight controller. But it did fly and held it course but temperamental at times, and also heavy for my application, hence I chose this current setup.
You guys are the experts so please analyse the logs I have provided and please assist me to fix the problem.
Sorry unable to upload the log’s, because when I down load the log from flight controller is in ULG extension, and I cannot upload this extension. So how to change to a format which can be up loaded to this post?