Thanks, William, for that description. That's the basic MV app in a nutshell, and a good succinct summary. And it applies, of course, to several different industries. Depending on the type of decision being made you need a higher or lower-res sensor, a color or B/W one, perhaps some visible light and some NIR cameras, various lens types, etc.
naperlou, I would suggest that in the embedded vision systems mentioned in the article, the main goal of the vision system is to collect lots, and lots of data; spend some time analyzing the images with the intent of making a decision; and then dumping the images after the decision has been made. Perhaps for archival purposes, a modest-resolution consumer video camera can be used in the loop for forensic logging. As the decisions become higher level, for example, reject or accept, routing, or even multi-sensor target recognition, or autonomous navigation, the analysis algorithms would love to have as much time as possible to make a correct decision. High-speed networks, such as 10-GBit Ethernet, present the data quickly and then the algorithms can start their processing. Now if the system calls for logging off all those images for offline analysis, I don't think the write-heads can keep up.
Beth, can you clarify your question? What kind of integration are you thinking of?
Regarding 10-Gbit Ethernet, I think that article and the comments attached to it cover those applications in quite some detail. In genetral, they are medical, military, and high-value quality inspection applications in multi-camera systems, and any app that can take advantage of high speed.
Ann, one of the articles referenced talks about 10-gigabit Ethernet. The question is, do vision systems need that much bandwidth. Do you see support for 10-gigabit Ethernet in systems like Vision Systems in the near future?
I would think that the trend of supporting general-purpose protocols is really a must in order for these new multi-camera vision systems to gain traction in all of the interesting applications you mentioned, Ann. With more and more cameras deployed on the factory floor or for medical applications, there's got to be a need to integrate the plethora of images with mainstream systems in real time in order to truly leverage the capabilities and achieve any kind of benefits. Beyond bus interfaces are there any other efforts going on to leverage standards and mainstream computing protocols to address this integration challenge?
Engineers at Fuel Cell Energy have found a way to take advantage of a side reaction, unique to their carbonate fuel cell that has nothing to do with energy production, as a potential, cost-effective solution to capturing carbon from fossil fuel power plants.
To get to a trillion sensors in the IoT that we all look forward to, there are many challenges to commercialization that still remain, including interoperability, the lack of standards, and the issue of security, to name a few.
This is part one of an article discussing the University of Washington’s nationally ranked FSAE electric car (eCar) and combustible car (cCar). Stay tuned for part two, tomorrow, which will discuss the four unique PCBs used in both the eCar and cCars.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.