etracer65
commented
5 years ago Well, I wouldn't exactly call this a bug as it is working the way it's designed and has been this way for quite a while. But it is true that it can be improved. I'll look at changing the calculation to be based on the setpoint throttle which is the final modified value (after applying throttle limit and other modifiers) used in the mixer rather than input throttle percentage. But as an improvement it will be part of 4.2 as changing the behavior in the middle of a release could catch people out as they might experience different results for the virtual current sensor.
JustAskDave
mikeller
Describe the bug The virtual Current Sensor uses the throttle position to calculate the approximate current draw. This does not seem to take into account if the throttle is scaled in the PID Rate Profile.
I am using little 3in drones in Schools to teach build/program/fly and I have the throttle setup on a 3pos switch via "Adjustments" for the Rate Profile Selection. I have the throttle down to 45% on Pos1, 55% for Pos 2 and unrestricted on Pos 3. This is to give the brand new students stick time with very little sensitivity at first. The Xrotor Nano doesn't have a current sensor so I set up the Virtual Current Sensor which worked great until I introduced the throttle scaling.
To Reproduce Steps to reproduce the behavior: Setting the scale for the virtual current sensor to get an accurate reading with throttle scale at 100% works great. Change PID Rate Profile Throttle Limit to Scale 50% to reduce max available power, the current meter is still reading the actual throttle position and not he scaled throttle position. This causes the virtual current sensor to read much higher than it should.
Expected behavior A clear and concise description of what you expected to happen. Throttle position for the Virtual Current sensor needs to refer to the throttle position applied to the motors using the scaled throttle output and not throttle stick position.
Flight controller configuration Create a
diffand post it here in a code block. Put`` (three backticks) at the start and end of thediff` block (instructions on how to do a diff: https://oscarliang.com/use-diff-not-dump-betaflight/)Use
resource show allto create a resource allocation list and post it here in a code block. Put ``` (three backticks) at the start and end of the output block.Setup / Versions
Flight Controller is a HobbyWing XRotor Nano F4 (OMNIBUSF4SD) ESC is HobbyWing XRotor Nano 20 amp 4 in 1 Receiver is FlySky FS-A8S micro powered from FC 5v VTX is Turbowing TX1769 powered from VBAT
Additional context Add any other context about the problem here. I that covers it all!