So do other 100.000.00 of things....:(

Is that in the plastic? Or a sensor? Weird that it only causes cancer in the state of California haha love that wording

....yeah california has a very long list, exhaustive at times.....

Quote:

California's cancer-warning policy comes from a 1986 state law called Proposition 65, enacted to protect California's drinking-water supply from toxic and potentially cancer-causing chemicals. It also mandates the state keep a master list of all chemicals known to be toxins and requires manufacturers and businesses to warn people about these chemicals if they're present in products or buildings, even in extremely small doses.

@DJ: Regarding the camera T265, it seems the product is on auto pilot mode, is not discontinued or retired and is available, but, Intel moved the focus to other products.

I have been burned a few times by intel. I have two realsense cameras deprecated on a short period time, broken promises e.g. skeleton tracking sdk. Looking to the other side: embedded boards: I have 2 edison, 1 damaged Galileu and 1 x Arduino Intel curie somewhere in the basement, everything is gone , remember Intel Joules (EZB 5).

It's my guess, and off course I'm biased not very happy with some Intel decisions, but, you can check the open tickets and won't be fixed replies, plus the lack of response. There are a little bit of everything: stability issues, SDK crashes, missing features, and broken promises.

It's a shame because it's really a good idea.

yah - i'm in the same opinion. The main trouble is there isn't a good plug'n'play navigation system out there. The IPS is great for indoor but no one is manufacturing it. And doing any inside out navigation like the realsense is.. well, that's all there is.

I'm hoping because there are enough real sense around that it'll at least stick around for a bit. It's not very well supported - i had a call with the cto of realsense division and even he didn't seem super optimistic about it, which was a little disappointing. I do recall our effort with Intel during the EZB V5... we had great expectations but they used us for the dog and pony show on stage and then discontinued the product.

on that note, it isn't a great SDK to work with. There's a lot of marketing buzz words about navigation, localization and SLAM... but it's not really there. It can give you some data about movement but it doesn't know where you are. It also doesn't seem to create a map of where you are or how to get anywhere, so no path generation.

Not sure exactly how anyone else is using it. Hoping someone will shed some light

@ptp do you have a good suggestion for an affordable solution for navigation ( inside and out) if not intel products?

Wonder if we're going to have to group together and make something --- or make something compatible with something that already exists.

@ptp, the EZ SLAM skill will take lidar data and generate a map. However, the issue we ran with that is dead reckoning would drift. It needs wheel encoders. And even with wheel encoders, we found the SLAM map eventually started twisting and getting bent out of shape because the wheels slip.

So really the SLAM is good for immediate room navigation but not good enough for a whole house or anything - in a real world environment. I know there's test cases and laboratory/university examples of slam working super well. But in the real world, we're not seeing it often because it's really used for obstacle avoidance.

I'm not sure what a real good navigation system is. Maybe we should start by discussing our navigation needs/requirements and working from there.

James Bruton has a turtlebot 3 and I think he used ROS navigation, but in that particular video he says its lidar had to be used with wheel encoders....so must always be drifting (slipping) issue when using lidar and lightweight robots...at least for the robot locating itself with in the map accurately...also explains why my Neato has very thick silicone wheels!

So no Lidar and no TOF (time of flight) cameras..what options does that leave?