MaxBotix Inc., has now released the I2CXL-MaxSonar-EZ ultrasonic sensors for sale to the public.
We are excited about this new product offering especially in regards to the multicopter community. These are now the best sensors we have available for your application. The new sensor models still have the calibrated beam patterns that you may be familiar with.
New Features Include:
- I2C bus communication allows rapid digital control of multiple sensors with only two wires.
- Readings can occur up to every 25mS (40Hz rate) for up-close objects and every 67mS (15Hz rate) for the full 7.5 meter range.
- Some increased noise tolerance over the standard XL-MaxSonar-EZ models.
These features are now available in addition to the low power requirements, small-light-easy mounting, high acoustic power, long range, and wide operational temperature already available on our other products.
You can learn more about the new I2C sensor or take a look at code examples in the product datasheet.
Link here: MaxBotix I2C Ultrasonic Sensor
Enjoy! Keep up the great work everyone!
Best regards,
Carl Myhre
Systems Engineer
of MaxBotix Inc.
Phone: (218) 454-0766
Fax: (218) 454-0768
Email: info@maxbotix.com
Web: www.maxbotix.com
Follow us on Facebook at: http://www.facebook.com/pages/MaxBotix-Inc/125159384204938
Comments
@agmatthews,
Hi ! Can I ask you, how your I2C sonar code is working ?
I have I2CXL-MaxSonar-EZ wiring to my PixHawk I2C port with default 0x70 I2C address.
I activated, in arducopter, the user code loop (APM_config.h and UserCode.pde) and added some lines to write and read on I2C port using the library "AP_RangeFinder_Maxsonar_I2CXL.h" but the pixhawk starts and after remains blocked with the RGB Led Yellow.
I also tried directly with the I2CDriver ( or with the AP_RangeFinder_Maxsonar_I2CXL library with the line "ret_value = _mode_filter->apply(ret_value);" commented in the read() method ) and in this case the value returned by the I2C_Maxsonar is always the same even if it is disconnected from the pixhawk !
I'm totally lost !
NB : This Sonar works perfectly on my RaspberryPi with a python script !
Sorry for my English :-)
Erik V
Randy,
The I2C is a trigger operation only. There is no free run operation. You can click this link to view the datasheet which covers all the timing and I2C part operation http://maxbotix.com/documents/I2CXL-MaxSonar-EZ_Datasheet.pdf.
Please let me know if you have any questions.
Best regards,
Scott Wielenberg
Technical Support and Sales
of MaxBotix Inc.
Phone: (218) 454-0766
Fax: (218) 454-0768
Email: info@maxbotix.com
Web: www.maxbotix.com
Follow us on Facebook at: http://www.facebook.com/pages/MaxBotix-Inc/125159384204938
@Andrew,
That sounds really good. So the sonar is going to be smart enough to only ping when we ask it? I suppose it probably has a continous and on-demand mode. I'd expect the on-demand mode would need a significant delay before it's results are ready...but then I guess if we could kick off the reading and then come back for the results. Anyway, great!
-Randy
@Randy,
I've now got my I2C sonar code working with the 2.71 code (ie with the new i2c.h library).
Using i2C sonar may allow us to get back into collision avoidance - I'm thinking using sequenced sonars to ping in turn (to avoid intra sonar interference).
I'll have another look at the rangefinder library as it has changed a bit from when I last tried to use it rather than my roll your own code.
more to come.
Andrew
Thanks for all the comments.
agmatthews: We do not have any distribution at our distributors yet. We are in the process of notification of the distributors. You were the first to know :-)
Randy: The shielded cable is not required but is still better when used. The "power smoothing cap/resistor pair" is still needed. If the sensor receives dirty power,it can cause noise issues with the sensors ranging.
Please let me know if you have any questions.
Best regards,
Scott Wielenberg
Technical Support & Sales
of MaxBotix Inc.
Phone: (218) 454-0766
Fax: (218) 454-0768
Email: scott@maxbotix.com
Jack,
Thanks for your inquiry. Deadband generally is not a word that can be used when describing a Maxsonar product. For example these I2C sensors detect objects from within 1 mm of the front sensor face, and objects closer than 20 cm are reported as 20 cm. So objects closer than 20 cm are detected.
Please let me know if you have any questions.
Best regards,
Scott Wielenberg
Technical Support & Sales
of MaxBotix Inc.
Phone: (218) 454-0766
Fax: (218) 454-0768
Email: scott@maxbotix.com
So how did you get the deadband down to 20cm?
Sounds familiar - oh look -> http://diydrones.com/profiles/blogs/creating-an-i2c-sonar-for
:-)
Good to see a quality sonar with i2c interface direct from a manufacturer
I've recently been trying to compile my original i2c sonar code into arducopter 2.71 - seems the new arducopter "i2c.h" library interferes with the standard Arduino Wire.h library - time for a rewrite - I'd be happy to integrate the maxbotics sensor
@Carl - have you got anyone selling these in Australia yet?
and if PWM wasn't a blocking call, we might be using it. I use PWM in other applications of these sensors when that is not an issue. I've had success driving several of these sonars from a mini, for example, and connecting the mini to an APM over i2c.
Don't see why shielding is necessary, cap still might be though.
I think the only reason shielding is necessary currently is the numpty use of the analogue voltage signal from the sonar units. There is already a PWM output which would in theory be noise immune.
-
1
-
2
of 2 Next