MaxSonar®-EZ1 problem

Hello all,

I have acquired a MaxSonar EZ1 and a MaxSonar EZ0;

i’m connecting a clean 5V supply, ground and testing the analog out pin with a voltmeter. I see a range of ~0.1V-0.7V and the data is rather choppy.

i see around the web that some have had the same problem, but i can’t find any solutions posted. has anyone encountered this?

also, if anyone can tell me how to tell a MaxSonar EZ1 from a MaxSonar EZ0 i’d be grateful. both have “MaxSonar EZ1” written on them, and the 1 is blacked- or browned- out with a marker; i reckon one color is EZ1 and the other EZ0… but hmm.

thanks,

a

Don’t forget that these modules recalibrate themselves on each power-up…

And so it’s best to use them in serial mode if you have more than one running at a time…

You also have two differnet LV-MaxSonar®-EZ1™ modules, look at page two of the [datasheet:wink:](http://www.maxbotix.com/uploads/LV-MaxSonar-EZ1-Datasheet.pdf)

hello,

perhaps it wasn’t clear, but i’m not using both modules (EZ0 and EZ1) simultaneously. i’m having the same trouble with both (when used on their own): output is around 0.2V-0.7V instead of 0.-2.5, and the values are rather choppy even in the range they work.

as for recalibration, does that mean each time they move i need to re-power them? and what is the ideal space to use them in?

a

I understand you aren’t using them simultaneously, but i belive you actually have two EZ1’s,

one with a brown dot and one without, they are ‘slightly’ different according to the [datasheet. :wink:

About the recalbration, each time you power the modules, they recalibrate… Quite a stupid design really… :roll:

I shall quote the datasheet, it says it better than i could:

LV-MaxSonar®-EZ1™ Datasheet:
"Each time after the LV-MaxSonar®-EZ1™ 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."

](http://www.maxbotix.com/uploads/LV-MaxSonar-EZ1-Datasheet.pdf)

Thanks for the reply.

I’m having better luck with the sensor now that i’m respecting the calibration phase when it powers and leaving a 14 inch clearance at that time.

Nonetheless, my real problem is that the output range of the sensor is still really small. with 5V Vcc from an arduiono (also tried a wiring board), my sensor’s output is still about 0-0.7V.

Has anyone any thoughts on that?

a

With that .7V, whats the distance?

Around 70" / 1.75 Meters?

Correct, about 1.75M and then the data gets REALLY choppy, as opposed to the FAIRLY choppy/flakey data i get up to 0.7V.

However i look at it, i’m NOT getting the promised 10mA / inch…!

a

Forgot to ask earlier, do you use a hard suface for calibrating?

And you should be getting around ~9.8mV/in, apparently and as my calculations are correct, you are getting that voltage…

But yes, it should go upto ~5V.:?

Could you be reading from it too fast?

i’m not using any surface to calibrate;

i point the sensor in the direction of wall in my studio, the wall is about 10 feet away. i then try to sense the distance between my body and the sensor.

is that not right?

The modules lose their calibration data after the power has been cycled, so they have to be 7-14" from a hard-ish surface on each power-up/cycle…

That’s down to the stupid firmware that these modules use… :roll:

So at the moment, when you power your module, it is trying to calibrate at 120"!

wow, that is truly a bone headed design. Is there no way to save calibration data?

Not to my knowledge.

I’ve also read that they don’t have their stated operation range…

Any updates batchku?

I just spent some time on the phone with Bob of Maxbotix. He was very kind, concise, informed and helpful.

The deal is:

  1. there is NO weird calibration process. when you power up the sensor, you should just make sure there’s nothing in front of it

  2. a good test to see whether the elctronics of the sensor are function is: cover the sensor with tape, power it up with 5V from a clean powersupply, and measure the voltage output from the analog pin with a meter. should be 2.5V. Mine was in fact that

  3. the sensors are very sensitive to acoustic noise from other things that may generate ultrasoound (refrigerators, electronics, …); they are also more wide-beamed than i had generally assumed.

  4. the difference between the EZ0, 1, 2, 3, and 4 is the beam shape AND the gain; the higher the number, the narrower the beam, the lesser the gain on the ultrasound; if you’re detecting things that aren’t perfectly reflective (like a person in a sweater), the higher number models may not have enough gain at higher distances.

  5. these sensors are calibrated in a big room covered in fur, i.e. very few unwanted reflections. whatever room you’re working most likely has a lot of acoustic noise.

i’m back to believing i can make these suckers work.

I had no problems getting an EZ1 to work and return accurate results. However I was using the serial output instead of the analog signal.

I believe Bob from Maxbotix just joined this Forum… :smiley:

Would you be able to give us some hints on how the modules are supposed to operate?

Or go into more detail about what is said in the datasheets?

All,

You guys wanted an explanation about the MaxSonar sensor line calibration process. The calibration process does not require that an object be close (or far for that manner) from the front face of the sensor. It is just better (for most users) if the sensor is clear for the first 14-inches during calibration.

The reason for the calibration is twofold.

First, the ring-down pattern of the transducers can change from power-up to power-up (for various reasons), and so this calibration accounts for this.

Second, the calibration accommodates for most mounting arrangements. For example, say a sensor, on a robot, is mounted a few inches from the floor. For a normal ultrasonic range finder, the floor returns a very high reflection (and may cause a false detection). But for this MaxSonar sensor line, when the sensor calibrates, the sensor stores data for the first 14 inches. So in this example it calibrates itself to accommodate the reflection from the floor. This allows the sensor to ignore the floor. The sensor can do this because the floor is part of the stored ring down pattern. This is a very good feature for mobile robotics, and a very significant benefit to the sensor end user. In addition, one can mount the sensor back and even have some fixed nearby objects in front of the sensor and still have excellent operation.

Therefore, with all of the above, the calibration really does make the sensors perform much better for most users.

And, if an object is too close during the calibration cycle, the sensor may then ignore objects at that distance.

Can you send me the link or post the link to where you read this information. (We do not know of any of our sensors not working at their stated distances.)

The reason we believe that each sensor works at the distances specified on the datasheet is that each senor is calibrated at our factory (not to be confused with the power up calibration), to specified distances that ensures they match the beam patterns that are recorded in the data sheets. This calibration is unique to each sensor and is stored within the sensor’s firmware. This is in effect, a test of each sensor, but it is much more than a test. Each sensor is calibrated/verified to match the stated performance. An, EZ0, EZ1, EZ2, EZ3, EZ4, and WR1 all have repeatable part to part performance, factory calibrated and verified. This makes MaxBotix Inc., and the MaxSonar product lines stand out, because in the low-cost sensor market, MaxBotix Inc., makes this type of quality control its standard practice.

Whenever there is a problem that could be directly attributed to our sensors, we work very hard with the customer (they do have to email us or call us) to determine if the sensor are faulty or if the cause is some other source. If the anomaly is from the sensors, we correct it and give the customer, new (or corrected) products. If any users experience problems, we will replace the parts under warranty, with no cost to the customer. (We even pay for shipping.) Yet, the only way we can support our customers, is if they let us know they are having a problem.

If you have any further questions, please let us know.

Best regards,

Scott Wielenberg

Technical Support & Sales

of MaxBotix Inc.

Phone: (218) 764-2489 Ext. 2

Fax: (218) 764-2194

Email: scott@maxbotix.com

Web: www.maxbotix.com

Here’s a link for ya: http://forums.trossenrobotics.com/showthread.php?t=885 - It may just be his setup, not too sure…

Anyway, thank you for taking your time to join this community to help answer your customers questions! :wink:

Thanks for the link. I reviewed the link and it pertains to the non-brown dot sensors sold prior to July 2007. The non-brown dot parts were not calibrated with the same process as the current sensors. It became an issue that not all the sensors matched the beam plots. For this reason we changed the programing process to be 100% factory calibration and testing to ensure that all sensor meet the specified distances. We have not had an issue with this since the release of the new dotted parts.

Did this information help?

scott@maxbotix.com:
Did this information help?

Absolutely! :wink:

Batchku (OP) mentioned that he had two EZ1’s, one with a brown dot and one without…