Home        Store        Docs        Blog

BLHeliSuite32 and suggested firmware parameters new bidirection options etc

Hello All, I am close to finishing my custom ROV build, and decided to utilize BLHeli32 35A 2-6S ESCs for now, I am running the latest 32.7.0.0 BLHeliSuite and 32.6.4 firmware (due to limited funding was not able to afford to use BlueESCs for now). My question is with the 32 firmware the bidirectional options are now ‘bidirectional 3D | bidirectional 3D rev | bidirectional soft | bidirectional soft rev’, which option do you feel would best be suited. For now I choose bidirectional soft, thoughts?
Additionally any suggestions for any other parameters? This is what I just configured them with:

[ESC0]
Eep_Name=BR Basic ESC
Eep_ESC_Layout=iFlight-35A-BLHeli_32
Eep_ESC_Mode=2
Eep_FW_Main_Revision=32
Eep_FW_Sub_Revision=60
Eep_Layout_Revision=42
Eep_Pgm_Direction=5
Eep_Pgm_Rampup_Pwr=50
Eep_Pgm_Pwm_Freq=24
Eep_Pgm_Comm_Timing=3
Eep_Pgm_Demag_Comp=1
Eep_Pgm_Ppm_Min_Throttle=1040
Eep_Pgm_Ppm_Center_Throttle=1500
Eep_Pgm_Ppm_Max_Throttle=1960
Eep_Pgm_Enable_Throttle_Cal=1
Eep_Pgm_Temp_Prot_Enable=7
Eep_Pgm_Volt_Prot=0
Eep_Pgm_Enable_Power_Prot=0
Eep_Pgm_Brake_On_Stop=0
Eep_Pgm_Beep_Strength=152
Eep_Pgm_Beacon_Strength=80
Eep_Pgm_Beacon_Delay=300
Eep_Pgm_LED_Control=12
Eep_Pgm_Max_Acceleration=0
Eep_Pgm_Nondamped_Mode=0
Eep_Note_Config=255
Eep_Pgm_Sine_Mode=0
Eep_Pgm_Auto_Tlm_Mode=0
Eep_Hw_Voltage_Sense_Capable=0
Eep_Hw_Current_Sense_Capable=255
Eep_Hw_LED_Capable_0=1
Eep_Hw_LED_Capable_1=2
Eep_Hw_LED_Capable_2=3
Eep_Hw_LED_Capable_3=0
Eep_Nondamped_Capable=1
Eep_Note_Array=

Maybe compare to the BR config file?

http://cad.bluerobotics.com/BLHeli_BRBasicESC-R_H_15-Rev.16.6-Multi_170921.ini

Unfortunately I believe the latest BR config was parameters prior to the recent BLHeli additions of the 4 bidirectional options, and haven’t gotten it into the water yet so was curious about which maybe the best option to start out trying.

Bidirectional soft seems cool…motors pull the most amps on startup, usually double the amps than with normal load, props moving water worst of all. So a soft start in reverse and forward would pull the least amps.

I would still try and connect the ESC’s heatsinks to the outside water somehow, for the best cooling. I have bigger ESC’s with custom curved heatsinks that are pressed against the inner curve of my aluminum WTC.

1 Like

Thanks Darrell, I appreciate the input. Running an acrylic enclosure to start with, so hopefully they won’t run to hot, definitely will have to keep an eye them now. Great idea on utilizing the aluminum as heatsink cooling, is an idea worth looking into for sure.

Back a few years…when i saw the OpenROV acrylic enclosure imploded on one of thier early tests, i knew i needed to go with an aluminum enclosure on my design.

I bought 8" ID aluminum pipe (cheaper than tubing) with 3/8" wall from onlinemetals.com and had a company in California make me custom (blow-molded) 8" acrylic hemispheres with a minimum wall thickness of 1/2" at the apex. https://plastic-domes-spheres.com/

When i told them what i was using it for they quoted me a price of $140ea., which i thought was Very fair for custom work.

8" might seem huge, but i wanted (2) 7-dof manipulators and active bouyancy control, and i always tend to build bigger rather than smaller anyway. My ESC’s are in 2 seperate 4"dia WTC’s either side of my main 8" WTC. That way if an ESC gets hot or burns up it doesn’t affect the much more delicate electronics in the main WTC.

1 Like

Wow Darrell, you already making my mind take off with the next evolution I can take this. Moving the ESC’s into side piping, which frees space in the main, and if i went aluminum I could even move power in line with the main. This is what I enjoy so much with making connections, getting inspired and the fun of seeing what can be accomplished. Myself I build robotics for cave exploration and extreme environments where no human has been or can reach, I can’t wait to be able to see my latest ROV hit the water and already mentally building out the next.