New feature: battery profiles

[shellixyz]

Feature request #2673

Summary

• 3 battery profiles supported by default
• Profiles can be switched by stick commands: THR-UP+YAW-LEFT + PIT-CENTER+ROLL-LEFT(1)/PIT-UP+ROLL-CENTER(2)/PIT-CENTER+ROLL-RIGHT(3)
• Profiles can be switched and configured through CMS
• Profiles can be switched automatically on power-up based on battery voltage
• If a profile bat_cells is 0 the cell count is calculated based on vbat_max_cell_voltage
• With default config it is working just as before

Profile autoswitch

Automatic profile switching can be enabled with the bat_profile_autoswitch setting. The profile is chosen among profiles with number of cells bat_cells set to a value > 0. The automatically selected profile can be overridden if necessary with a stick command or through the CMS.

Example config

set bat_profile_autoswitch = ON

# battery_profile
battery_profile 1

set bat_cells = 3
set vbat_max_cell_voltage = 421
set vbat_warning_cell_voltage = 350
set vbat_min_cell_voltage = 330

# battery_profile
battery_profile 2

set bat_cells = 3
set vbat_max_cell_voltage = 411
set vbat_warning_cell_voltage = 300
set vbat_min_cell_voltage = 280

# battery_profile
battery_profile 3

set bat_cells = 4
set vbat_max_cell_voltage = 421
set vbat_warning_cell_voltage = 350
set vbat_min_cell_voltage = 330

Profile 1 is for a 3S Li-Po pack, profile 2 for a 3S Li-Ion pack and profile 3 for a 4S Li-Po pack.
With this configuration if the battery plugged in is less than 12.33V the profile 2 will be automatically selected else if the battery voltage is less than 12.63V the profile 1 will be automatically selected else if the battery voltage is less 16.84V the profile 3 will be automatically selected. If a matching profile can't be found the last manually selected profile is used.

[shellixyz]

I don't know why the checks failed the OMNIBUS target compiles fine on my machine. Well... I know why. GCC 7.1.0 seems better at optimizing the RAM usage. Are we already at the F3's limits !?

Using built-in specs.
COLLECT_GCC=arm-none-eabi-g++
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/arm-none-eabi/7.1.0/lto-wrapper
Target: arm-none-eabi
Configured with: ../gcc-7.1.0/configure --prefix=/usr --mandir=/usr/share/man --with-pkgversion='Fedora 7.1.0-2.fc26' --with-bugurl=https://bugzilla.redhat.com/ --infodir=/usr/share/info --target=arm-none-eabi --enable-interwork --enable-multilib --with-python-dir=share/arm-none-eabi/gcc-7.1.0/python --with-multilib-list=rmprofile --enable-plugins --disable-decimal-float --disable-libffi --disable-libgomp --disable-libmudflap --disable-libquadmath --disable-libssp --disable-libstdcxx-pch --disable-nls --disable-shared --disable-threads --disable-tls --enable-languages=c,c++ --with-newlib --disable-nls --disable-shared --disable-threads --with-gnu-as --with-gnu-ld --with-gmp --with-mpfr --with-mpc --with-headers=yes --with-system-zlib --with-sysroot=/usr/arm-none-eabi
Thread model: single
gcc version 7.1.0 (Fedora 7.1.0-2.fc26)

[shellixyz]

I disabled the external barometer support for OMNIBUS for the checks to pass. It is not necessary with the GCC version 7.1.0 but the OMNIBUS board has an on-board barometer so it is not needed anyway.

[giacomo892]

Neat feature!
I came up with something you can add if bat_profile_autoswitch is enabled:
A series of long beeps after gyro calibration beeps reporting the profile number so the pilot can have an immediate feedback on the profile detection.

Could be very nice to report, optionally, the current profile on the OSD via the system messages function before arming.

[shellixyz]

@giacomo892 Good ideas. I thought about beeping the profile number it but I'm not familiar with how the beeper code is working yet I'll take a look at it.

[shellixyz]

Would this be merged in 2.0 if I rebase this PR ?

[digitalentity]

Why not?

…

On Fri, Jun 8, 2018, 15:17 Michel Pastor ***@***.***> wrote: Would this be merged in 2.0 if I rebase this PR ? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2749 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKi_m9QrTKjIaSd10ReVTAZ8OscyM4lZks5t6nlLgaJpZM4SBuFQ> .

[shellixyz]

I'm asking because it was ready long before 1.9.1 so I was not sure why it was not merged earlier. I will rebase it.

[shellixyz]

Rebased and bench tested again. Ready to merge

[digitalentity]

It would be nice to have a possibility to entirely disable the possibility to switch battery profiles via sticks (as we do to PID profiles) -to prevent accidental switching.

[shellixyz]

Good idea. Battery profile selection is now only possible when the TX_PROF_SEL feature is enabled. I also updated the documentation.

[CpeDratDoPC]

It would be a good idea to have a Scale and Offset current sensor set in each profile.
I have a KakuteF7 and my voltage offset changes, 3S-6S.

[teckel12]

@CpeDratDoPC I believe it's a voltage divider, it shouldn't change for hight voltages (maybe just be more precise).