|
| From: | ebahier |
| Subject: | Re: [Paparazzi-devel] V4.9 and BAT value problem |
| Date: | Mon, 28 Jan 2013 20:19:42 +0100 |
| User-agent: | Internet Messaging Program (IMP) H3 (4.3.9) |
Hi felix, I pocedd : git reset --hard e5b2e9a make paparazzi_version.... OK ./paparazzi clean upload Nothing better B value still ignored. Today I fly with 5 lipo... 21V, I have a big one, ready to fly in 10 cells lipo... or 12 if necessary. thank, Eric Felix Ruess <address@hidden> a écrit :
Hi Eric, the latest version is v4.2.0_stable-3-ge5b2e9a But as I said, this proposed fix is _NOT_ in the stable v4.2 yet, but in master. If it works as expected I can backport it to v4.2... Did you try to set it to some high value like 50? For convenience I also pushed the potential fix to my github repo on the v4.2_vsupply_fix branch. To test it: git remote add -f flixr https://github.com/flixr/paparazzi.git git checkout v4.2_vsupply_fix Cheers, Felix On Mon, Jan 28, 2013 at 7:31 PM, <address@hidden> wrote:Hi Felix, Today, I make a git pull.... gitk I am on xxxxxx:~/paparazzi$ ./paparazzi_version v4.2.0_stable-2-gd155873 I suppose is the uptodate version? with any valu in "VOLTAGE_ADC_B".... the GCS value stay the same (almost ok on the real useable value) <define name="VOLTAGE_ADC_A" value="0.0081" unit="V"/> <!--theorique 0.0074 +1.6--> <define name="VOLTAGE_ADC_B" value="5" unit="V"/> <define name="VoltageOfAdc(adc)" value ="(VOLTAGE_ADC_A * adc + VOLTAGE_ADC_B )"/> Many thanks, Eric Felix Ruess <address@hidden> a écrit : Hi Eric,Regarding VoltageOfAdc:Are you sure it's not changing anything at all? As electrical.vsupply is in decivolts you need to define VOLTAGE_ADC_B to 20 if you want an offset of 2V. Could you please check this? I think fixed this in master so you can specify that in V as it should be. (commit d266565227<https://github.com/**paparazzi/paparazzi/commit/* *d266565227bb81f071662d104e4ccf**0244ff87df<https://github.com/paparazzi/paparazzi/commit/d266565227bb81f071662d104e4ccf0244ff87df> > ) If that works I'll backport the fix to v4.2 as well.did you try that fix in master for the VOLTAGE_ADC_B? If that does what you want/expect I'll backport it to v4.2 and we can make a minor maintenance release.. Cheers, Felix On Wed, Jan 9, 2013 at 12:39 AM, Felix Ruess <address@hidden> wrote: Hi all,so the ADC should now work again properly in master. If the radio_control/ppm subsystem with input on SERVO6 (default) is used the ADC is now automatically configured to use TIM1 instead of TIM2. (fixed with commit ad81033ed<https://github.com/** paparazzi/paparazzi/commit/**ad81033ed3573027b137fb86072893**b0857c133d<https://github.com/paparazzi/paparazzi/commit/ad81033ed3573027b137fb86072893b0857c133d> > ) If anyone has a good idea on how to automatically check and configure if the same hardware resources are needed by several subsystems, ideas are very welcome. Cheers, Felix On Tue, Jan 8, 2013 at 11:55 PM, Felix Ruess <address@hidden >wrote: Hi Eric,Stephen probably found the problem with adc in master: radio_control/ppm on servo6 and adc both use TIM2 So it e.g. works if you use UART1_RX as RADIO_CONTROL_PPM_PIN (uses TIM1 for that). In the meantime you could add <define name="USE_AD_TIM1"/> to your firmware section if you use the ppm subsystem with the default input pin (servo6). We are still working on a good solution to configure that better. Regarding VoltageOfAdc: Are you sure it's not changing anything at all? As electrical.vsupply is in decivolts you need to define VOLTAGE_ADC_B to 20 if you want an offset of 2V. Could you please check this? I think fixed this in master so you can specify that in V as it should be. (commit d266565227<https://github.com/**paparazzi/paparazzi/commit/ **d266565227bb81f071662d104e4ccf**0244ff87df<https://github.com/paparazzi/paparazzi/commit/d266565227bb81f071662d104e4ccf0244ff87df> > ) If that works I'll backport the fix to v4.2 as well. Cheers, Felix On Tue, Jan 8, 2013 at 10:46 PM, <address@hidden> wrote: Hi felix,V4.2 solve my BAT problem, a small bug still aliv : <section name="BAT"> <define name="VOLTAGE_ADC_A" value="0.0080" unit="V"/> <!--theorique 0.0074 +1.6--> <define name="VOLTAGE_ADC_B" value="2" unit="V"/> <define name="VoltageOfAdc(adc)" value ="(VOLTAGE_ADC_A * adc + VOLTAGE_ADC_B )"/> <define name="CATASTROPHIC_BAT_LEVEL" value="16." unit="V"/> <define name="CRITIC_BAT_LEVEL" value="17." unit="V"/> <define name="LOW_BAT_LEVEL" value="17.5" unit="V"/> <define name="MAX_BAT_LEVEL" value="23" unit="V"/> </section> I can change "VOLTAGE_ADC_B" to any value, the value on the ground still the same. Best regards, Eric Felix Ruess <address@hidden> a écrit : Hi Eric,as I said the bug was introduced when we switched from the stm lib to libopencm3 in master... there is no point in wasting effort to find at what time the bug was introduced (is fine in v4.0 and v4.2 as there we didn't port ADC to libopencm3 yet). We rather need to find which other subsystem "destroys" the adc initialization/settings, or if there is some timing/sync issue or what ever... I would also recommend to use v4.2 instead of v4.0 .... Regarding the calculation of the battery value (via VoltageOfAdc(x)): is B defined? Can you post the relevant part of your airframe file? It should work fine if it's defined properly, e.g. https://github.com/paparazzi/****paparazzi/blob/v4.2/conf/**<https://github.com/paparazzi/**paparazzi/blob/v4.2/conf/**> airframes/examples/twog_****analogimu.xml#L94<https://** github.com/paparazzi/**paparazzi/blob/v4.2/conf/** airframes/examples/twog_**analogimu.xml#L94<https://github.com/paparazzi/paparazzi/blob/v4.2/conf/airframes/examples/twog_analogimu.xml#L94> > Cheers, Felix On Mon, Jan 7, 2013 at 11:03 PM, Eric BAHIER <address@hidden> wrote: Hi felix,I have make many test to try to define when the bug appear. Today I have fly on version v4.0.1_stable-8-gbe4f487-dirty 2012-08-30 On this version evrything smell good. My airframe fixwings.xml file was ok for IR, it need some modification to be perfect in IMU. Today man and aut1 was OK, AUTO2 was "full camicase version". On V4.0.1 the bat value is fonctional. If I try to use BATVALUE= Amul*adc+B. A coef is ok, B coef is not functional. To try it , Iput it to 10 (volts)... nothing change on BAT on the ground station. I will have two days with flying weather.... end of week will be with dirty weather... It will be the perfect weather to test some versionsssss and try where is the bug in the GIT tree.... Thank for your help, best regards Le 07/01/2013 22:32, Felix Ruess a écrit : Hi Eric, it should work fine in the stable releases v4.0 and v4.2. In master (v4.9) we completely switched to libopencm3 and it seems there were some regressions introduced when porting the drivers. Eduardo also reported that the problem only occurs in his setup if he is using the radio_control ppm subsystem, but not with the spektrum subsystem. It is probably related to some low level initialization of one of the drivers... Still hoping that Stephen will have some time to look at this ;-) Cheers, Felix On Tue, Dec 18, 2012 at 1:27 PM, Eric BAHIER <address@hidden >wrote: Hi felix,Thanks to look at my bug.... I test with 4 targets: Lisa/L 1.0 without alone (no GPS, no IMU.....) just the Xbee Lisa/L 1.0 full ready to fly (GPS,IMU,Xbee, Rx) Lisa/M 1.0 full ready to fly (GPS,IMU,Xbee, Rx) booz ready to fly (GPS,IMU,Xbee, Rx) On my side I work on a lab PC, actualy in paparazzi V4.0.1... it smell good. I will verifiy evrything on 4.0.1.... and make the update step by step to try to find when the bug appear, I will send you his birthday..... Last time I play with GIT with limited updated, it was not complete succesfull.... I will win to GIT!!! Yesterday I look in source code... batcheker.c.......... I can not see anything. My feeling is a time schedule problem, I suppose we "forgot" to restart the ADC processing, the ADC value stay the same evrytime after the first read.... Today it is only a idea, a feeling...... many thaks, Eric Le 18/12/2012 13:04, Felix Ruess a écrit : Hi Eric, it works on my Lisa/L 1.0 (no IMU connected at the moment). I tested it on the Lisa/M 1.0 as well and it indeed doesn't work correctly, and it seems that there is some problem with proper adc setup if other peripherals are used as well. It works when adding adc_init(); electrical_init(); to the end of main_init()... The test_adc target works fine. Couldn't find the actual problem yet... Stephen, Esden, any ideas/time to look into this? Created an issue for it: https://github.com/paparazzi/****paparazzi/issues/339<https://github.com/paparazzi/**paparazzi/issues/339> <https://**github.com/paparazzi/**paparazzi/issues/339<https://github.com/paparazzi/paparazzi/issues/339> > Cheers, Felix On Mon, Dec 17, 2012 at 12:35 PM, Eric BAHIER < address@hidden >wrote: Hi,I try to kill my bug of BAT value on GCS.... it stil alive..... I have 2 problems, To have a good value (8V) I need to modify the adc value.....with the documented function <section name="BAT"> ... <define name="VOLTAGE_ADC_A" value="0.011"/> <define name="VOLTAGE_ADC_B" value="0.635"/> <define name="VoltageOfAdc(adc)" value ="(VOLTAGE_ADC_A * adc + VOLTAGE_ADC_B)"/> </section> With this my first mistake is solve (or work around.... perhaps it is a visible part of th iceberg....) My real bug (I can not find any solution or work arround) The BAT value is correctly read at power up, GCS give the good infomation (if I use VoltageOfAdc...), Message windows give also the good value. If the BAT value change (LAB power supply can do it easly), the GCS an Message value still th power up value... In Message windows the message is updated, but with the power-up value.... This morning I have take My LISA/M, I have used the standard fraser.....xml, I have juste change the IMU to my version, and comment the prog mode to use the standard jtag interface. This mornig I have updated my config (git pull, make clean, make) My paparazzi version v4.9_devel-337-g34b46d2-dirty. Anyone I have any idea where I have make the mistake...... Many thanks, Eric -- **************************************** Lez Concept EURL Eric BAHIER 15 chemin neuf 34 980 Montferrier sur LEZ France Tel : 33 4 67 59 92 53 Fax : 33 9 59 15 92 53 **************************************** ______________________________****_________________ Paparazzi-devel mailing list address@hidden https://lists.nongnu.org/****mailman/listinfo/paparazzi-****devel<https://lists.nongnu.org/**mailman/listinfo/paparazzi-**devel> <https://lists.nongnu.**org/mailman/listinfo/**paparazzi-devel<https://lists.nongnu.org/mailman/listinfo/paparazzi-devel> >______________________________****_________________ Paparazzi-devel mailing address@hidden:// lists.nongnu.org/**mailman/**listinfo/paparazzi-**devel<http://lists.nongnu.org/**mailman/listinfo/paparazzi-**devel> <htt**p://lists.nongnu.org/mailman/**listinfo/paparazzi-devel<http://lists.nongnu.org/mailman/listinfo/paparazzi-devel> > -- **************************************** Lez Concept EURL Eric BAHIER 15 chemin neuf 34 980 Montferrier sur LEZ France Tel : 33 4 67 59 92 53 Fax : 33 9 59 15 92 53 **************************************** ______________________________****_________________ Paparazzi-devel mailing list address@hidden https://lists.nongnu.org/****mailman/listinfo/paparazzi-****devel<https://lists.nongnu.org/**mailman/listinfo/paparazzi-**devel> <https://lists.nongnu.**org/mailman/listinfo/**paparazzi-devel<https://lists.nongnu.org/mailman/listinfo/paparazzi-devel> >______________________________****_________________ Paparazzi-devel mailing address@hidden:// lists.nongnu.org/**mailman/**listinfo/paparazzi-**devel<http://lists.nongnu.org/**mailman/listinfo/paparazzi-**devel> <htt**p://lists.nongnu.org/mailman/**listinfo/paparazzi-devel<http://lists.nongnu.org/mailman/listinfo/paparazzi-devel> > -- **************************************** Lez Concept EURL Eric BAHIER 15 chemin neuf 34 980 Montferrier sur LEZ France Tel : 33 4 67 59 92 53 Fax : 33 9 59 15 92 53 **************************************** ______________________________****_________________ Paparazzi-devel mailing list address@hidden https://lists.nongnu.org/****mailman/listinfo/paparazzi-****devel<https://lists.nongnu.org/**mailman/listinfo/paparazzi-**devel> <https://lists.nongnu.**org/mailman/listinfo/**paparazzi-devel<https://lists.nongnu.org/mailman/listinfo/paparazzi-devel> >______________________________****_________________ Paparazzi-devel mailing list address@hidden https://lists.nongnu.org/****mailman/listinfo/paparazzi-****devel<https://lists.nongnu.org/**mailman/listinfo/paparazzi-**devel> <https://lists.nongnu.**org/mailman/listinfo/**paparazzi-devel<https://lists.nongnu.org/mailman/listinfo/paparazzi-devel> >______________________________**_________________ Paparazzi-devel mailing list address@hidden https://lists.nongnu.org/**mailman/listinfo/paparazzi-**devel<https://lists.nongnu.org/mailman/listinfo/paparazzi-devel>
| [Prev in Thread] | Current Thread | [Next in Thread] |