Latest version of "serial monitoring mod" BLHeli firmware - RC Groups
Thread Tools
This thread is privately moderated by sachiho, who may elect to delete unwanted replies.
Jun 15, 2013, 02:05 PM
Registered User

Latest version of "serial monitoring mod" BLHeli firmware

This is the latest version of "serial monitoring mod" BLHeli firmware.
This is experimental mod. and I have tested only for XP7A-Main and Oversky double ESC-Main.

  • Switched to RKit-51. There is no need to modify notation.
  • 1200bps achieved by using "averaged divider" 6.5
  • Deleted monitor of governor errors.
  • Added monitor of ADCvalue, flags1.
  • Added checksum.

Many BT modules do not support lower than 1200 bps.
Therefore, the support of 1200 bps was important.
In order to obtain 1200 bps from (1/128us = ) 7815 cycle, you have to carry out dividing by 6.5.
I realized this by changing 6 dividing and 7 dividing for every bit.

But, code size have become too large. It can not be linked for some BESC.

Now, 10 bytes of packet is transfered.
Their contents are blow.
  • 0: Character 'U'
  • 1: Requested_Pwm (for throttle?)
  • 2: Governor_Req_Pwm
  • 3: flags1
  • 4-5: ADCvalue (for batt. voltage. seems to not working for some BESC)
  • 6-7: Comm_Period4x (for motor speed)
  • 8: reserved
  • 9: checksum (simple sum of byte0-8)

I think that we should determine the contents of the packet in the near future.

Is it good to see which information otherwise?
And Requested_Pwm does not seem to be a throttle surely.
Is there any better variable?
Last edited by sachiho; Jun 16, 2013 at 09:15 AM.
Sign up now
to remove ads between posts
Jun 22, 2013, 06:10 AM
Registered User
Great work! It's a pity that code becomes too large, there is surely not much room left before the 8k limit is reached.

When it comes to variables, I think your choice is mostly good.
Requested_Pwm is the throttle input value and is important.
Governor_Req_Pwm is basically the same value, except that it's change rate is limited so that governed headspeed changes become smooth. Probably not so interesting.
I think Current_Pwm_Limited is an important variable. This is the actual power that is applied to the motor.
And battery voltage and motor rpm are important variables.

Jun 23, 2013, 05:11 PM
Registered User
Thank you for the advice.
It is the perfect information for me!

I will monitor "Current_Pwm_Limited" instead of "Governor_Req_Pwm".

And next, I try to make code size smaller.
However, the again same problem will arise by a future function addition, even if code size is settled in 8kB at present.

Thread Tools

Similar Threads
Category Thread Thread Starter Forum Replies Last Post
Discussion Charge Monitor lost serial Thermal Hobby Hitec/Multiplex USA 1 May 05, 2013 09:59 AM
For Sale NIP Turnigy AE-30A ESCs flashed with BLHeli Firmware ross_badger Aircraft - Electric - Multirotor (FS/W) 0 Apr 02, 2013 05:54 AM
Discussion what is the latest firmware version for Eagles eyes FPV station? WBFlyer Eagle Tree Systems 1 Mar 26, 2013 12:54 PM
Sold Dragonlink rx latest version firmware Kloner FPV Equipment (FS/W) 5 Jul 18, 2012 09:34 AM