Hi,
The adc_set_injected_sequence function is exactly the same for F1
and F4, and the priorities are the same as before (just set by a
macro).
Maybe you can try to use the adc_generic module to figure out which
adc channel is actually used for battery monitoring.
Gautier
Le 29/01/2014 09:29, Kadir ÇİMENCİ a
écrit :
Hello everyone,
Thanks for the answers, today i had a chance to test all
possible problematic cases related with your answers:
(all of them is made with two different Lisam v2 boards
- stm32f105 to avoid the problems related with hardware)
I have directly fed the battery voltage to the V_bat
pin.
1) I have been working with a dead Lipo and changed it to
a fully charged healthy ones 3s and 4s nothing changed
still displaying 9.4 V on gcs
2) Directly fed the board with a DC power supply with
constant voltages between 5-15 V , nothing changed, still
9.4V
3) Finally decided it is a problem with software and decided
to look at to source code, luckily i have a backup of master
release on 22 January(a week ago) and turned back to that
snapshot, and i can measure the battery regulary.
I guess it is a problem with updated libopencm3 adc structure.
Yesterday Chris had mentioned that everything seems correct with
the code, but there may be a specific buggy case for STM32F1 mcu
i don't know. Since i measure the same voltage for all different
voltage sources, i suspect i am measuring the same wrong ADc
channel. Or there maybe a problem with ADC interrupt priorities
and sample times in which V_bat pin is never readed. I suspect
these problems may be relevant with these commits which are made
after 22 Jan.
https://github.com/paparazzi/paparazzi/commit/daf9408171ad10f2d859f12b57d2dc818566f86c
https://github.com/paparazzi/paparazzi/commit/fd2ae6b95c0b4178fd88f431e9e1daba3b8750d0
_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel
|