Servers by jDrones

BLHeli, BLHeli_S and BLHeli_32 On Pixhawk and ChibiOS/stock 3.6

Hi! The last time I built a multirotor with ArduPilot was on an APM with Hobbyking Blue Series ESCs flashed with SimonK and Multistar 4208 motors. Was a successful build and used to get 15 minute flights on a 4S 4000mAh, on 14x4.7 props. After that, Ive mostly built racer quads and have used the Pixhawk on fixed wings only.

Also I’ve built and flown a few racer quads with BLHeli_S firmware. Haven’t had major issues with them so far.

Now I’m building a ZD550 frame and putting a Pixhawk on it.

I’m deciding on the motor and ESCs for this build and was wondering how easy it would be to actually setup my build with BLHel firmware. I am looking at a 4S setup with 12 inch props and maybe upgrade to a 6S setup sometime later. The main reason I’d like to go with BLHeli is the form factor and that’s what is a little more easily available where I’m at.

I have the following questions:

  1. I’ve gone through the documentation at http://ardupilot.org/copter/docs/common-dshot.html?highlight=blheli
    From what I understood, I will HAVE to use Copter 3.6 AND also the ChibiOS build?
    So it won’t work with the firmware I would usually install using Mission Planner following http://ardupilot.org/copter/docs/common-loading-firmware-onto-pixhawk.html?

  2. I have only ever installed the firmware using Mission Planner, never built it from source. How difficult would this be, provided I have a moderate competency with figuring out how to install and use software by following documentation?
    Also this is the ChibiOS build? https://github.com/ArduPilot/ChibiOS

  3. Also should I just look for regular ESCs for this build and experiment with BLHeli at a later stage?

Thank you so much!

Go straight for blheli, it’s better than most proprietary firmware anyway.

Sir, Would you suggest BLHeli-S or BLHeli 32 ?.

Blheli32, as it gives the option for esc telemetry feedback.

2 Likes

Yes, I am aware it is much superior firmware and I have had a great experience using it on my racer quads. How well does it play with the default ArduCopter firmware? Can I use it with that or do I have to compulsorily use the ChibiOS version?

Also, with the default ArduCopter firmware, would it be possible to mitigate any potential issues by setting the motor PWM outputs of the Pixhawk to 1000us(min) to 2000us(max) and at the same time calibrate the BLHeli values to 1000us (min) and 2000us (max)?

BlHeli32 , like James says, is a good choice because of telemetry.

Quadcopter you plan have less use for ESC telemetry anyway, if one fail, the outcome is given. Had it been a big , redundant RPAS with =>6 motors, it could ba a nice feature (and an fail is still easy to spot by throttle demand monitoring)

but ArduCopter does not use this telemetry (yet) for handling faults - which would be the BEST argument for blheli_32

blheli_s may have some slight efficiency advantages due to better PWM, but I can’t say whatever it is more of an theoretical advantage, or can make a typical setup save a few percent of power.

  • it’s up to you.

Personally, I don’t see any reason what so ever to use ESCs running BLHeli firmware on anything other than a racer.

I have a racer. It uses BLHeli. Its a blast to fly.

I have 3 other aircraft larger than 500mm. 2 are quads, the other is a hex. I use Hobbywing X-Rotor 40A ESCs. Work fine, last a long time. No muss, no fuss, hook 'em up, calibrate, fly.

Based on the documentation I read (See warning above this link: http://ardupilot.org/copter/docs/common-dshot.html#where-to-buy), the BLHeli with telemetry is only supported on ChibiOS, is that still the case with the latest 3.6 release? If it is still the case, is ChibiOS ready for general testing with 3.6?

Do the ESC telemetry messages get communicated over MAVLINK for Arducopter 3.6 yet?

1 Like

Yes, the BLHeli stuff is only on ChibiOS and the ESC telemetry messages are being sent to the ground station now.

We’ve also got a new guide for loading ChibiOS onto Pixhawk boards and the ChibiOS-only boards.

The Copter-3.6 on ChibiOS testing seems to be going well. I haven’t see any crashes caused by bugs in the ChibiOS port but it’s still in beta so I don’t think we can say it’s totally stable.

By the way, Copter-3.6 testing was put on hold for a few days as we test Copter-3.5.6 but it will resume today or tomorrow.

1 Like

ChibiOS also allows display of BLHeli32 telemetry values in the OSD, including ESC temperature, current flow and RPMs. IT is valuable for fixed wing and multi rotor, especially during early verification of a build and it’s power train.

Kelly

Is there any technical reason that the BLHeli is not supported for NuttX? Or, is it just a labor resource issue?

It’s a low level issue with how nuttx manages DMA to a pin, that can’t be fixed in the flight code layer. Noting the work to drop nuttx as soon as the ChibiOS port is confirmed stable, I don’t think any effort will be spent modifying nuttx.

1 Like

It’S possible to use bheli32 esc with nutts until chibios become stable release? Or they doesn’t work directly?

Sure, up to One shot125 just not Dshot.

1 Like

Dear All
Trying dozens times and cant do my BlHeli_s work with my PIXHAWK. The motors do not spins, and passtrough does not work too.
Please anybody to send a quad parameter file to help me?

Frame: QUAD
RCOut: PWM:1-12
fmuv2 00390040 31385112 38353731
ArduCopter V4.0.3 (ffd08628)
ChibiOS: d4fce84e
BhHelisuit32 vers :32.7.1.2
ESC RacerStar Dshot RS40A
Motors: Racerstar 4208

Same issue;
12/22/2020 10:00:18 PM : Frame: QUAD
12/22/2020 10:00:18 PM : RCOut: PWM:1-8 DS150:9-12 PWM:13-16
12/22/2020 10:00:18 PM : fmuv5 001D0039 34385119 39313933
12/22/2020 10:00:18 PM : ChibiOS: d4fce84e
12/22/2020 10:00:18 PM : ArduCopter V4.0.5 (3f6b43e3)

Bob, these are the settinigs that I have. I finaly got BLHeli32 to see my TEKKO32 ESCs, but it is skippiing ESC#1 for some reason. You also need to look into the Mototx/SERVOxx_" parameters settings. Let me know if you fixed the issues.

MOT_PWM_TYPE 7 0:Normal 1:OneShot 2:OneShot125 3:Brushed 4:DShot150 5:DShot300 6:DShot600 7:DShot1200
SERIAL4_BAUD 115200 1:1200 2:2400 4:4800 9:9600 19:19200 38:38400 57:57600 111:111100 115:115200 230:230400 256:256000 460:460800 500:500000 921:921600 1500:1500000
SERIAL4_OPTIONS 36
SERIAL4_PROTOCOL 16 -1:None 1:MAVLink1 2:MAVLink2 3:Frsky D 4:Frsky SPort 5:GPS 7:Alexmos Gimbal Serial 8:SToRM32 Gimbal Serial 9:Rangefinder 10:FrSky SPort Passthrough (OpenTX) 11:Lidar360 13:Beacon 14:Volz servo out 15:SBus servo out 16:ESC Telemetry 17:Devo Telemetry 18:OpticalFlow 19:RobotisServo 20:NMEA Output 21:WindVane 22:SLCAN 23:RCIN 24:MegaSquirt EFI 25:LTM 26:RunCam 27:HottTelem 28:Scripting 29:Crossfire 30:Generator 31:Winch 32:MSP 33:DJI FPV 34:Sagetech
SERVO_BLH_AUTO 1 0:Disabled 1:Enabled
SERVO_BLH_DEBUG 1 0:Disabled 1:Enabled
SERVO_BLH_MASK 1
SERVO_BLH_OTYPE 7 0:None 1:OneShot 2:OneShot125 3:Brushed 4:DShot150 5:DShot300 6:DShot600 7:DShot1200
SERVO_BLH_POLES 14 1 127
SERVO_BLH_PORT 0 0:Console 1:Serial1 2:Serial2 3:Serial3 4:Serial4 5:Serial5
SERVO_BLH_REMASK 0
SERVO_BLH_TEST 0 0:Disabled 1:TestMotor1 2:TestMotor2 3:TestMotor3 4:TestMotor4 5:TestMotor5 6:TestMotor6 7:TestMotor7 8:TestMotor8
SERVO_BLH_TMOUT 0 s 0 300
SERVO_BLH_TRATE 10 Hz 0 500

Servers by jDrones