Replies to This Discussion

Permalink Reply by Limebear (Rob) on June 3, 2011 at 5:20pm

My sonar didn't work properly when i first mounted it, it gave a more-or-less fixed reading. I was using 30 mm spacer legs to attach the sonar under the AC2 frame, and these spacers have brass inserts in them for the screws. I suspect the brass inserts were shorting the hole mounts to an adjacent pad, because when I added nylon washers as insulators, the sonar started working.

I have the LV EZ2 version, and it measures down to 21 cm min. (Anything less than 21 cm is still detected but displays as 21 cm).

• ▶ Reply

Permalink Reply by I.S. on June 7, 2011 at 6:06am

I also have sonar problems that I put here, but could be useful here too.

this is my info:

ArduCopterMega 2.0.23

LV EZ4 sonar

about constant 340cm reading on test/sonar on CLI no matter where I put

 

Any other one with sonar problems?

• ▶ Reply

3D RoboticsPermalink Reply by Chris Anderson on June 7, 2011 at 7:17am

we're only going to be supporting the XL MaxSonar EZ0 natively, as stated in the manual. Other sonars may work but need to be connected differently and may need different code calibration. People are free to configure their code for them, but the dev team can't support what we don't have.

• ▶ Reply

Permalink Reply by I.S. on June 7, 2011 at 1:06pm

Ok. Could you please point where that code is? So I can try to tweak it? Thanks

• ▶ Reply

Permalink Reply by geir on June 7, 2011 at 2:37pm

As i said earlier i think I revived a defect sonar, so I'll have to buy a new one :(  50 dollars out the window :( But thanks anyway :)

• ▶ Reply

Permalink Reply by I.S. on June 7, 2011 at 2:39pm

One thing to remember is the datasheet warning:

Each time after the LV-MaxSonar®-EZ4™ is powered up, it will calibrate during its first read cycle. The sensor uses this
stored information to range a close object. It is important that objects not be close to the sensor during this calibration
cycle. The best sensitivity is obtained when it is clear for fourteen inches, but good results are common when clear for at
least seven inches. If an object is too close during the calibration cycle, the sensor may then ignore objects at that distance.

• ▶ Reply

Permalink Reply by Limebear (Rob) on June 7, 2011 at 3:00pm

This is the case for all of the LV series, including the EZ0 version. This is actually quite an awkward restriction, because it means you have to hold the Quad off the ground every time you power it up.

 

Am I mistaken or has the Sonar manual page been recently updated to change the sentence

" the recommended sonar for altitude hold is the XL-MaxSonar EZ0 or the LV-MaxSonar EZ0" to read just

" the recommended sonar for altitude hold is the XL-MaxSonar EZ0"

 

Just after I have purchased to LV version D'oh!

Rob

• ▶ Reply

Permalink Reply by I.S. on June 7, 2011 at 2:41pm

<-- this is not the case of XL series which calibrate continously realtime.

 

@Chris

I understand not to give support to all the hardware but you (DIYDrones) sell that sonar

• ▶ Reply

Permalink Reply by wraith on January 29, 2012 at 4:17pm

i was having trouble to, couldnt get it hold , my problem was caused from changing modes to low to the ground

• ▶ Reply

Permalink Reply by Virgil Cartan on February 19, 2012 at 8:45pm

I had the same problem with sonar, was always very noisy  even the sonar was  disabled I had a rather large deviation in altitude fluctuating. This happens every time the telemetry was connected, if only the USB cable   was ok. I managed to eliminate interference between telemetry and sonar cable with small  ferrite ring on the telemetry close  to XBee. everything is fine now.even if the sonar is started less than 20 cm away from the ground.

• ▶ Reply

Permalink Reply by Ravi on May 6, 2012 at 7:14am

the quad is good in manual (stabilize) mode. when i switch it Altitude hold, the quad begins to climb. how do i calibrate my throttle for hover using channel 7.

• ▶ Reply

• ‹ Previous
• 1
• 2
• Next ›
• Page