Hey Folks,
As many of you recommend, I used a paid Ecalc to order the parts for my new drone.
Unfortunately the motors do not spin fast enough to take off.
Stupid ECalc!!
Any advice on new motors.
6S, 15", 4500 gr weight.
See pics. =(
The Motors I have can do 8S batteries, but seems to me new motors might be cheaper than new batteries and ESCs?
Thanks!
Oh, and I’d really like this kind of prop interface.
330kv motors should be fine with 15inch props and 6S.
What ESCs do you have?
Provide a .bin log of an attempted take off.
EDIT: throwing some numbers into ecalc I get a similar result to your screenshot, so that’s at least consistent.
This is W/O props on the bench. Threw a message about power loss.
THANKS Xfacta.
Xaidin
Oh the escs are 32a.
Bench testing always provides limited/skewed results - about all you can check is that all the motors spin in the correct order and direction.
You really should be using DSHOT (or bid-directional DSHOT) with those ESCs, the operation is more reliable and the data is extremely useful. (I see you tried)
There are some BLHELI_32 settings you need to do, after you set up DSHOT you can do them via the flight controller (passthrough).
The important setting you probably need the most is the first one of these:
For now, set these in the flight controller:
ATC_THR_MIX_MAX,0.5
INS_HNTCH_ENABLE,0 // you dont have ESC RPM data yet
INS_LOG_BAT_MASK,1
INS_LOG_BAT_OPT,4
LOG_BITMASK,180222
MOT_PWM_TYPE,0 // unless you set up DHSOT, then use 6
SERVO_BLH_MASK,0 // not needed
SERVO_BLH_OTYPE,0 // not needed
So at this point you can leave things as they are with the adjustments I’ve specified, and do the semi-automatic ESC calibration procedure (linked below) - OR set up DHSOT properly and get all that sweet ESC data! You should do all the settings I specified in either case.
Either way you really need to get that “Low RPM Protect” setting changed in all the ESCs.
Let us know if you can use some guidance on the DSHOT setup. Your flight controller can do it easy enough. Do you have all those ESC Telem wires joined into one and connected to anything?
https://ardupilot.org/copter/docs/esc-calibration.html#semi-automatic-esc-by-esc-calibration
To get DSHOT working you need to move the ESC signal wires to the FMU/PWM 1,2,3,4,5,6 output pins and in MissionPlanner / Mandatory / Servo you logically move the motor functions
from Servo 1,2,3,4,5,6
to Servo 9,10,11,12,13,14
You’ll probably have to shift your neopixels or anything else that’s connect to those servo outputs.
And set these:
INS_HNTCH_ENABLE,1
INS_HNTCH_FREQ,40
INS_HNTCH_BW,10
MOT_PWM_TYPE,6
SERVO_BLH_BDMASK,0
SERVO_BLH_MASK,0
SERVO_BLH_OTYPE,0
SERVO_BLH_POLES,14
Also set all the other parameters I mentioned before (except any I’ve specified here)
Reboot the flight controller and observe the Messages tab, there should be something like:
RCOut: PWM:1-8 DS600:9-14 NeoP:15-16
Now use MissionPlanner motor test to set:
MOT_SPIN_ARM as low as you can get it and motors still start up reliably.MOT_SPIN_MIN,0.10 usually, but at least MOT_SPIN_ARM + 0.03That should do for now - let us know how you go before running out to do a test flight.
And what are all those ESC telem wires connected to?
For 100% 330kV + 15" are fine.
I assembled quad - tarrot 5008 340kV + 15x5.5 props running on 6S.
Total weight about 5kg and files fine, hover at about 40% throttle, so with 6 props should have even more power.
I think that is misdirected…
It will come down to one setting that @xfacta supplied in Blheli32.
Of course all else should be configured also.
Thank you so much Xfacta!
I’d actually had it setup like that before. The Pixhawk 6x supports 16 PWM outputs, all but 2 Dshot compatible.
Using your setting it just beeps and chirps the motors incessantly until I either arm it or unplug.
I think you’re right about the ESC programming issue though.
For the life of me I can not get the BLHeli/betaflight passthrough to work.
I have the same issue as this post:
Passthrough Post.
I’ve gone though this doc several times:
ESC Setup
Oh, and the telemetry wires aren’t connect to anything. Should they go to the first 6 IO/PWM Out ports? Or…?
I figured I didn’t need them.
Thank you!
Xaidin
Your configuration is all wrong and you have the wrong firmware for what you are trying to do. Consider changing the Title of your post to something relevant to the issues. You are doing a disservice to Mr. Mueller.
Suggest you reset all to default and start over with the Methodic Configurator with your level of knowledge.
Fixed that, since you are correct, and it does no good to lambast a software tool that is not at fault.
The constant beeping means there’s no valid signal to the ESCs, so lets work through that rather than just go back to a second-rate config. The BLEHLI passthrough wont work in that state either.
What do you get in Messages about the RCout ?
Supply a .param file (in MissionPlanner go to full parameter list, “save as file”)
Without the Telem wires connected, you should
or, what I would do
SERIALx_OPTIONS,16
SERIALx_PROTOCOL,16
Firmware is here. Download the .apj and flash it.
Pixhawk 6X-bdshot
Thanks for the info.
I did the firmware per dkemxr.
Worked.
Never could get passthrough to work, so I checked the ESCs using a separate betaflight FC.
Apparently have some of the new “prototype” ECSs that can’t be programmed.
As per this vid: PSA on prototype ECSs Mine show up the same.
Thinking of sending them back.
Anyway, all the settings were okay on them except: Low RPM Power protect, that’s “on” and can’t be changed.
RCOut: PWM:1-8 DS600:9-14 PWM:15-16
Motors are on 9-14, and motor test works, no extra beeping, but they only run at one slow speed. Regardless of throttle %. About where you’d want “arm” speed to be.
Thank you so much!
Try the new AM32 firmware config tool - if those ESCs do have AM32 on them that is the preferred outcome.
This is web-based and needs Chrome to work
https://am32.ca/configurator
What ESC’s are they?`
And this is misconfigured:
SERVO_BLH_3DMASK,3968 Of course you don’t want dynamically reversible motors, set it back to default. This won’t fix your problem.
Low RPM Power Protect won’t work with the kV of those motors.
It’s these sir:
I’ll try, but they say “blheli32” right one them and did connect to the software, just yelled these errors:
That is AM32 firmware using a BlHeli boot loader. You need to use the AM32 configurator.
Then I think you were right when stating you cannot disable the feature causing the issue. At least by the product description “no configuration changes can be made”.
And this comment “ However, stock ESC settings work great for almost all applications”. Almost all application with motor kV>1200 maybe…,
Worth s try with the AM32 configurator anyway but I guess you are stuck.
Okay I replaced all the ESCs with different ones. These.
I got the right BLHELI settings into them.
After some tweaks it almost works now.
I rolled firmware back to regular: ArduPilot firmware : /Copter/beta/Pixhawk6X
Instead of BDSHOT, as new ESCs don’t do bdshot, only regular.
Motor test works except they all run at what seems 100% no matter throttle setting.
Can one of you give me the correct configs for regular 600 Dshot?
I have these: (from post before)
MOT_PWM_TYPE,6
SERVO_BLH_BDMASK,0
SERVO_BLH_MASK,0
SERVO_BLH_OTYPE,0
SERVO_BLH_POLES,14
THANKS! Getting close!
