5Cm is nothing. I have aircraft with ESC signal wires that are 6 to 7 times as long.
I’m with dkemxr. Other than telemetry (big ho hum) I don’t see any reason what so ever to use ANY form of BLHeli ESC on a large multi-rotor aircraft.
Think about the history of BlHeli. Where did it start? With racers. Small aircraft with small high KV motors swinging “small” props. At the time it was all about throttle response and with any racer from go-karts to Reno Air Racers, getting power to the props/wheels/jet exhaust throttle response is the key…
Here is another analogy. Compare a Hyabusa motor cycle to an 18 wheeled tractor-trailer. Who is quickest off the line? Who has the highest top speed? Who has the highest towing capacity? Who has the longest endurance on a tank of fuel?
The point is, each of these machines are purpose built for what they do and because they are purpose built they are the best at what they were built to do. Your aircraft is no different. It’s not going to set any speed records, so your really don’t need BLHeli ESCs.
As I have written, thatis a third version of a copter on that frame. For the first two copters the first flight became the last. I added screencap and logs to the google drive.
If I apply full throttle it will get jump up for 50 meters or so and start swinging and crash. I want to get it to fly smooth.
BlHeli is not just software, but hardware as well. Faster, smarter MCUs, faster FETs with lower internal resistence, so on. In the end, a brushless motor is a brushless motor, regardless of its size.
For instance, with BlHeli32, desynchs are a thing of the past. Consumption is a bit lower and flight times longer. Add telemetry and dynamic notch filtering based on motor rpm, and it’s a different universe altogether.
It’s not that you don’t need BlHeli ESCs. It’s more like make sure you get them with STM32F3s, not F0s.
Motors 7025 420w, the power is approximetely 2.5 kw. I use 380 props and the battery is 6s but I inntend to use 8s battery later.
The entire construction weighs 9 kg
Third or fourth time you give this advice. Reverse stick input doesn’t make the craft flip on take off, it is perfectly able to fly just has reversed command.
Wonder why you keep saying that.
You need to get your facts straight. I only said that once. The longer this saga goes on the more I tend to agree with dkemxr. By your own admission this is the 3rd iteration of this design and it still won’t fly This tells me the entire design is fundamentally flawed.
The situation might not depend on the params at all. So today I turned the controller around and now the copter tilts backwards. The problem occurs to be not in the controller, but it is still not clear. All motors and ESCs are same. I post a video of a copter in 15% throttle, it seems like motor B is doing the best job, and motor C is the worst, but I think that will be compensated by the controller.
Well, I would disagree with you. If one of the first versions was able to fly, I wouldn’t have to make new ones. Yes, something is wrong, so I am trying to figure out what is it.
Why do you have The SERVOxx_REVERSED parameters all set to Motor Output numbers? Those are not even valid values for this parameter. If you didn’t do this purposefully, for whatever reason, I would reset to default and start over.
I defenetelly didn’t change that parameter. I think it should be 1 for default. I’ll check that. I believe its a great idea to start over the entire param adjustment. I’ll refresh all params to default and keep track of what I change.
I reinstalled and updated the firmware to version 404. The only changes made are the most nessesery ones. Unfortunatelly, it didn’t help. Here are the changes I made to the default params.
Have you tried to fly with that? Include a link to the new .bin log.
Have you calibrated accels and done a perfect level horizon?
Otherwise it’s got to be motor position or direction.