Battery voltage calibration

I am using 2S Lipo and the battery display is 0.8 less than actual value. Any chance to calibrate it?

Or which .c file should I look into and modify?

Thanks

You can modify the target/[your tx model]/target_defs.h file. At the end you will see the formula and the parameters.

Hi rbe, could you please advise more detail on how to calibrate the voltage display ? Like how to access to (target/[your tx model]/target_defs.h file)

thanks

Hi,
You will have to download the source code from the BitBucket PB repository and
setup the programming environment to build (compile) the firmware yourself after changing the parameters in the file
src/target/[your tx model]/target_defs.h

where [your tx model] is your TX model (devo10 for ex.)

domcars0 wrote: Hi,
You will have to download the source code from the BitBucket PB repository and
setup the programming environment to build (compile) the firmware yourself after changing the parameters in the file
src/target/[your tx model]/target_defs.h

where [your tx model] is your TX model (devo10 for ex.)

That might be true, but it's a major hurdle for most Deviation users.
On top of that, you have to go through that process after every firmware update.

My tx displays fairly accurate supply voltage, but it seems that the variation is quite large between different transmitters, even when comparing the same model.

A solution to this might be to have a calibration value in the tx.ini file for easy editing, eliminating the need of a complete developer toolchain and the steep learning curve associated with it.

You are right.

I have the same problem with à Turnigy 9xr 3s lipo. Is there something new about that ?

Thx

Hello Everybody,

I found that maybe the RPM value also not accurate (I think, about 10%).

I've checked the RPM sensor with a signal generator and an oscilloscope,
and its output signal seemed good for me (1 edge/Hz (only even numbers are possible, so 120 1/min resolution) ).
I guess, the telemetry module can cause the difference or the TX with the Deviation 4.0.1.

Have anybody else experienced similar?

Best regards!