Hi,
What is 3v3? Â
I would say the most obvious advantage is with a better range and angular resolution the scan matcher or other algorithm for matching up the landmarks will have more data to work with and have an easier time.
Camp has run gmapping and amcl with ros on the Raspberry Pi 2. It's doable.
To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+...@googlegroups.com.
To post to this group, send email to hbrob...@googlegroups.com.
Visit this group at https://groups.google.com/group/hbrobotics.
For more options, visit https://groups.google.com/d/optout.
-----Original Message-----
From: Chris Albertson
Sent: Aug 3, 2016 2:06 AM
To: hbrob...@googlegroups.com
Subject: Re: [HBRobotics] Neato LIDAR
It looks like the Neato LIDAR will work and the data rate is reasonable. They are available for about $100 which is not bad, I I get one.But I was thinking about building one myself and had some ideas on how to greatly reduce the cost. The key I think is NOT to use pulsed light but instead a continuous beam that is amplitude modulated by (say) a 10MHz local oscillator.  Then you compare the phase of the reflected light to the local oscillator and make a map of phase offset vs. degree of scan.  Distance is proportional to phase. One must select a local oscillator frequency such that the wavelength is >2 times greater than the room size. (10MHz is 30 meters so a 180 degree phase shift means the round trip distance from laser to wall to receiver is 15M, so the max measurable distance somewhat under 15M.)  Phase can be measured using analog circuit so there is no computer needed inside this kind of LIDAR.
On Tue, Aug 2, 2016 at 11:29 PM, Ralph Gnauck <ralp...@pacbell.net> wrote:
I have robots with both a lidar (neato botvac) and a home built base with a Kinect.The Neato will consistently  create a good map and can navigate pretty well using it.The robot with the kinect (and creating a fake laser scan from the 3d data) has problems creating the map - have not got to try its navigation yet as I have not got the good map from it.BTW: The kinect bot has much more CPU power - A jetson, while the neato only has a Pi2 and the neato bot is still better at mapping.So I would recommend that a lidar is much better for navigation.The main reason is the limited field of view ~45Deg from the kinect.The mapping and navigation have a lot of trouble with this small  amount of data - especial when the robot rotates - you have to turn very slowly or it  is easy to have no overlapping data from scan to scan so the SLAM will not be able to do any matching.Ralph
Sent: Tuesday, August 2, 2016 11:03 PM
Subject: Re: [HBRobotics] Neato LIDAR
Yes generating the message is cheap, but those massages must be read and processed
On Tue, Aug 2, 2016 at 6:38 PM, Michael Wimble <mwi...@gmail.com> wrote:
Generating a point cloud (well, actually a scan topic message) from the laser data stream is cheap. It's hardly a load at all.Â
Sent from my iPhone
How many points are needed and how many can be processed by a small ARM processor like on the Pi3?The Neato does about 4 revolutions per second and 360 points per revolution. Over 1,000 points per second to process. At the far end of a room ( 30 feet distant) the one degree spacing works out to about 1/2 foot.  ÂI guess I should try a simulation.Â
On Mon, Aug 1, 2016 at 11:41 PM, Griswald Brooks <griswal...@gmail.com> wrote:
I would say the most obvious advantage is with a better range and angular resolution the scan matcher or other algorithm for matching up the landmarks will have more data to work with and have an easier time.
On Aug 1, 2016 11:35 PM, <alberts...@gmail.com> wrote:
In old drawings the reproductions were not best quality. A dot would be hard to see and might not even print. So they need something bigger to use in place of the dot. It is so common I almost did not understand your question. I read it as 3.3V and wondered what was being a asked.
It is like writing exponentIl notation like 1.23E6Â it is actually clearer
 BTW these are only about $100 on eBay and Amazon. It should be obvious they work. 1E8 vacuum cleaners can't be wrong.
QUESTION:Â in practical terms what do you get in terms of indoor localization by buying a more expensive LIDAR scanner?
> On Aug 1, 2016, at 7:05 AM, °|° Walt Perko °|° <wpe...@Brainless.org> wrote:
>
> Hi,
>
> What is 3v3?
>
>
>
> ==============================================================================================
> C U L8r, °|° Walt Perko °|°    "Kids ... teach them the good stuff, and they still learn the bad stuff on their own."
>
> http://www.Brainless.org/
>
Last night there was some discussion about getting a raw feed from the Neato LIDAR. Â For those that are interested, there are some resources at:
https://xv11hacking.wikispaces.com/LIDAR+Sensor
which lays out the data format for the packet. Â It also has some example code that you can use as-is or use as a reference for ginning up your own. Â
As Camp points out, anything close to 3V on the motor will get it spinning and it will start spitting out data.  If the speed isn’t pretty close to 300 RPM, the angle error will probably be enough to screw up maps.  Each packet contains a speed measurement that is RPM*64, so a simple PID loop (or even just using the I term, with P & D zero) targeting the speed value == 19200 will get you within 1% of 300 RPM pretty quickly.  A PWM output from an Arduino with a simple low-side driver transistor works great.
Some other misc notes:
The XV-11 LIDAR and the BotVac LIDAR have identical protocol, but electrical hookup is less forgiving on the BotVac LIDAR.
* XV-11 LIDAR will run happing on 3v3, BotVac LIDAR really must be powered by 5V.
* The TTL-UART signals are 3v3 in either case, so don’t use 5V TTL UART with either.
* The XV-11 LIDAR doesn’t care if you leave it’s RX data dangling, but the BotVac LIDAR will usually wedge or print garbage if you let that input float, so either tie it off or hook up the TX data from your USB converter to the LIDAR.
* If you don’t want to run the LIDAR data through an Arduino or such on the way to your main processor, it works perfectly well to simply use a y-cable type tap to sniff the TX data from the LIDAR to use for speed control.
> If you can tell butter from a dead crab you won’t have any problems.ÂMmm... dead crab.- Camp
From: Dave Curtis <da...@dave-curtis.com>
To: hbrob...@googlegroups.com
Sent: Wednesday, August 10, 2016 8:01 AM
Subject: Re: [HBRobotics] Re: Neato LIDAR
> Some other misc notes:
> The XV-11 LIDAR and the BotVac LIDAR have identical protocol, but electrical hookup is less forgiving on the BotVac LIDAR.
> * XV-11 LIDAR will run happing on 3v3, BotVac LIDAR really must be powered by 5V.
> * The TTL-UART signals are 3v3 in either case, so don’t use 5V TTL UART with either.
> * The XV-11 LIDAR doesn’t care if you leave it’s RX data dangling, but the BotVac LIDAR will usually wedge or print garbage if you let that input float, so either tie it off or hook up the TX data from your USB converter to the LIDAR.
> * If you don’t want to run the LIDAR data through an Arduino or such on the way to your main processor, it works perfectly well to simply use a y-cable type tap to sniff the TX data from the LIDAR to use for speed control.
>
> Interesting. I think all the Neato LIDARs I've got are from XV11s and not BotVacs. Are there identifying marks that would let you tell the two apart in random parts bin ?
Completely unmistakable. The base is a different shape and the mounting screw holes are moved. BotVac LiDAR is asymmetric. If you can tell butter from a dead crab you won’t have any problems.
-dave
>
> 'dillo
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+unsubscribe@googlegroups.com.
> To post to this group, send email to hbrob...@googlegroups.com.
> Visit this group at https://groups.google.com/group/hbrobotics.
> For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+unsubscribe@googlegroups.com.
To post to this group, send email to hbrob...@googlegroups.com.
Visit this group at https://groups.google.com/group/hbrobotics.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "HomeBrew Robotics Club" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hbrobotics+unsubscribe@googlegroups.com.