Replies to This Discussion

Permalink Reply by Al Ros on May 10, 2011 at 7:30am

Also looking at code it seems to default to use the XL sonar rather than LV. I tried changing that to LV like in pirates code , but it generates a compile error.

Al

• ▶ Reply

Permalink Reply by Christopher Cooper on May 10, 2011 at 4:34pm

Where did you try and make the change? On line 183 of ArduCopterMega.pde I changed:

AP_RangeFinder_MaxsonarXL sonar;

to:

AP_RangeFinder_MaxsonarLV sonar;

 

It compiles but I don't it makes a difference.

Am I correct in assuming that any #defines I add in APM_Config.h will override the same #defines found elsewhere in the code?

• ▶ Reply

Permalink Reply by Al Ros on May 11, 2011 at 9:48pm

Yes that's were I tried it.

 

I just went back and tried again and it compiled - I must have made a typo initially.

 

Interesting that it made no difference. I will try in AM. with the ardupirates code, the change made a difference for me and the readings were much more accurate. I'll report back

 

Al

• ▶ Reply

Permalink Reply by Michal Rusina on May 11, 2011 at 1:16am

am also getting weird numbers, B_alt oscillates around 100+/-50, sometimes dropping to 0 and sometimes  up to 65000, without any movement of the apm, also no props installed, so that cant be the issue...

• ▶ Reply

ModeratorPermalink Reply by John Church on May 11, 2011 at 10:57pm

This has been fixed as of r2242 with a change to a printf type variable. Either check the changes in the trunk and make the modification manually, or download the latest trunk code to get up to date. ;)

• ▶ Reply

Permalink Reply by Christopher Cooper on May 12, 2011 at 1:03am

I'm not too familiar with how the repository works. If I go to r2242 the only file with that rev is GCS_Mavlink.pde. Is that where the changes have been made for that revision?

• ▶ Reply

Permalink Reply by Michal Rusina on May 12, 2011 at 1:28am

download tortoise svn if youre using windows or versions if mac and checkout the whole repository, that way you get always the latest code.

• ▶ Reply

Permalink Reply by Christopher Cooper on May 12, 2011 at 3:39am

Thanks! The latest version seems to be giving more sensible values for the barometer. From the sonar however, I get values around 330. They don't change when I raise or lower the quad, or when I remove the sonar! Something's not right there...

• ▶ Reply

Permalink Reply by Shawn on May 12, 2011 at 3:51am

So to be a bit more clear on this...is the latest stable code on the download link from the main arducopter page (all zipped up) or should we go to the trunk for the best code?

 

• ▶ Reply

Permalink Reply by Michal Rusina on May 12, 2011 at 4:02am

its like this: the latest code wich should be stable is on the main page all zipped up. BUT! that code is in beta, and it means that there are some bugs wich are continually fixed and those fixes are revisions in svn. unfortunately, by fixing something somewhere, you can break something elsewhere, thats why the revisions in svn cant be "trusted" to be stable until someone wont test everything altogether and say that everything is working fine.

anyway, latest svn code is working much better than the beta. i wouldnt trust it to strap a dslr to a quad running it or even test it without strapped to something heavy so it wont flys away and kills someone...

• ▶ Reply

Permalink Reply by Shawn on May 12, 2011 at 4:07am

Thanks, that clears that up.

Not too reassuring ;) 

but clears it up.

 

• ▶ Reply

Permalink Reply by Michal Rusina on May 12, 2011 at 4:08am

its better than it sounds. working on "large" opensource projects is like this :)

• ▶ Reply