Replies to This Discussion

Permalink Reply by KnutL on May 14, 2012 at 5:05am

Tried the same now on two PCs - Vista and WinXT- always the same effect. Mission planner does not accept any values in the Battery Input tab.

No idea what to do...

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on May 15, 2012 at 4:47am

the planner looks at the values in

measured voltage

current voltage

and the current divider to calc the new divider.

 

make sure all these fields have normal values.

• ▶ Reply

Permalink Reply by KnutL on May 15, 2012 at 7:39am

Thnx for your reply.

1. I am not really sure, which fields you are talking about, because the fields that I have, do not match with your description.

2. What I do is as follows

Step one: I enter the Batt Monitor tab and I see the following input table:

Step 2:

I try to input the measured APM Input voltage (field 1)

When selecting the next field, I see the following:

 

Step 3: Something is wrong, but now I try to input the measured battery voltage. Of course, I click on ok in the "Not available" window first and then I type in my 11.23 Value in Field #2.

 

When I hit <enter> I see the following:

 

When I leave the Battery Monitor Tab and come back, no values have been stored.

What do I have to do different ? Thnx for your help.

 

 

 

 

• ▶ Reply

Permalink Reply by Dave on May 15, 2012 at 4:32pm

I've had problems with that page too.  I think you need to enter a non-blank value in the Voltage Divider field, even though it's supposed to be an output, calculated field.  Then it only seems to recalculate when I go out of the page and come back in.

On a slightly broader note, why is the APM Input Voltage even needed?  If I just enter the Measured Battery Voltage, the program can read the A/D input and work out the overall scaling factor.  There should also be no need for Battery voltage (Calced) because that should always equal the Measured value.

As a final comment, the instructions displayed on the page are not complete / correct.

• ▶ Reply

Permalink Reply by Jake Stew on May 15, 2012 at 6:38pm

I'm not sure how this feature works.  The ESC/BEC provides a regulated 5v output right?  So even when the batter voltage drops the apm should still be getting 5v right?

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on May 15, 2012 at 8:01pm

what firmware are you using?

• ▶ Reply

Permalink Reply by Dave on May 15, 2012 at 10:31pm

I'm currently running 2.5.4 but was the same for the previous release.

• ▶ Reply

Permalink Reply by KnutL on May 16, 2012 at 12:37am

1. I am using ArduPlane V2.33

2. I tried to enter a non-blank value in the Voltage Divider Field. It seems, that a calculation is run (I will document that when I am back to my desk tonight), but

nothing changes in the flight data window in terms of displaying the batt voltage - or do I expect something wrong here ?

 

I would expect, that the current Batt Voltage ist displayed int the flight data window aftre the calibration process..

• ▶ Reply

Permalink Reply by KnutL on May 16, 2012 at 8:47am

Sorry mistake: I use Arduplane 2.24

• ▶ Reply

Permalink Reply by KnutL on May 16, 2012 at 9:16am

I did some additional tests and its getting impossible for me to understand whats happening.

I do the same 3 steps as described above.

In addition I enter a value in field 4 = Voltage divider (calced)

Step 4: Enter 1.0 (no idea why 1.0 but just to test) in field 4

If I user <enter> nothing happens, cursors still stays on field 4

a) If I use the mouse to go to field 1 and click left, the "not available" window pops up. I quit this window with OK

b) I goto field 2 , click left, same as above "not available" pops up.

Quit with ok.

c) Go to field 4, click left - a new value is calculated in field 4.

If I go again up to a) and repeat the steps a) b) and c) a new value in field 4 is calculated each time - and this value in field 4 is always growing by some factor (approx. 3.2??) each time I do the loop steps a, b and c.

Very strange.

 

• ▶ Reply

DeveloperPermalink Reply by Michael Oborne on May 16, 2012 at 4:10pm

KnutL, your arduplane version is to old. latest is 2.34

• ▶ Reply

Permalink Reply by KnutL on May 17, 2012 at 12:21am

ok, switched to 2.34. With that version I can get MegaPlanner in a status, that it seems to display the correct battery values..thnx.

Usage is still a little tricky - will not touch that aerea again if I dont need to :)

 

Thank you for your help.

• ▶ Reply