Maxbotix Range Finder
 

How do you wire the am-2435 to the robot and the cRIO?
http://www.andymark.com/product-p/am-2435.htm

Re: Maxbotix Range Finder
 

Wire the ground, 5V, and analog signal to the analog breakout to receive voltage that translates to distance. 2.54 V = 254 cm

Re: Maxbotix Range Finder
 

You can also wire it using the DIO port on the Digital Sidecar and measure the signal coming in. There are Labview examples for both methods (analog and digital) if you use that as your coding program.

Re: Maxbotix Range Finder
 

Here is the link for the Maxbotix Range Finder White Paper/datasheet;

http://maxbotix.com/documents/XL-Max..._Datasheet.pdf

Is anybody using this currently? We are using it and having problems picking up what we can only assume right now is the carpet and giving us extremely low values quite often. I'd be curious to see how anybody else is mounting this, and if anybody else is having this problem. We are running it off the analog output right now, and today are going to print a mount which will hopefully "focus" the cone more.

Re: Maxbotix Range Finder
 

We're using it. We are mounting about 20 in above the ground. We bent some polycarb and made a little mount

Re: Maxbotix Range Finder
 

We are using ours in analog mode and it's mounted about 30" above the ground. It was working really well until mid-day yesterday and now it's flatlined at about 3ft. We'll troubleshoot tonight. Other than that, only issue was slow response (due to 2 Hz filter) in analog mode. But for what we're doing, that was good enough.

Also found this little gem to help with mounting at Allied Elec: Item # 70196662, P/N BF-010175. It's a small black box with mounting tabs that holds the sensor perfectly.

Re: Maxbotix Range Finder
 

We've used these before and they are very sensitive (they pick up leaves, small leaves). I'd recommend checking for any debri on the floor and also checking to ensure you haven't fried the sensor.

Update: with the printed cone mount as high on our robot as possible we're having no trouble with it, we did go ahead and take the largest value every 1/5th of a second to smooth outputs as well which really helped.