Log review for big hex

ArduCopter Copter 4.1
1

Alright!!!

So, we finally were able to successfully perform a hover with this big hex being built after working through some ESC/pixhawk issues.
Here are the previous threads posted to refer to those issues: ESC not connecting to Pixhawk Cube - #14 by geofrancis
and
MASSIVE 200 LB Drone ESC issue

I wanted to see if it would be possible to have someone look over this log to see if there is anything out of the norm. Please let me know if this is the right file type.
https://drive.google.com/file/d/1ilpUHyaSv75QHqBywa1IdJL8ZQw0WPEX/view?usp=sharing

2

It’s not, useless. The .bin flight log from the Flight Controller.

3

https://drive.google.com/file/d/1xrL2URMbZesGIOufq9Ic124NAyVNyHB-/view?usp=sharing

My bad here is the bin file
Thanks

4

Not much is revealed here. You should have battery logging and configure the Dynamic Notch filter. Start by setting INS_LOG_BAT_MASK to 1 and make another short hover flight.

5

Ive been trying to figure out how we could do battery logging because we are using 88v.

6

Battery voltage is the most important so you can use the thrust linearization features. A simple voltage divider is better than nothing. The Cube Orange has a 3.3V full scale input for battery monitoring.

7

Ok i will have to look into that because we are running the pixhawk off a separate lipo. Gonna have to do some research into the 3.3v input you refered to.

8

https://drive.google.com/file/d/1yLN8OKm8zu-zZfKmO1c77Ar0Ug4_V74H/view?usp=sharing here is a log with INS_LOG_BAT_MASK set to 1. We are still working on the battery logging.

9

Try checking this @MindProbe