Sometimes its very important to say what features are absolutely necessary or required and what features are "Nice to have". Then a brainstorming or review can be done and that's it. Just because the tool can support and people can play with, the system should not be compexed. Many projects fail because they try to get everything on board rather than concentrating on what is required.
Adding a robot and multiple algorithms to a vision system makes it look like the AOI systems I'm used to see in PCB assembly. They are pretty expensive, being off-the-shelf. So I imagine a custom solution would be cost prohibitive.
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.