Seems like the dizzying array of standards would present huge challenges to engineers building machine vision applications and systems in terms of dealing with compatibility issues and a host of extra configuration work. Is this mix of standards holding back adoption of machine vision tools or is this something where there is a pretty standard workaround?
Beth, it's going to make me pause long and hard while trying to decide which protocol to use. This is a sore point for me; anyone who wants to adopt these early stands the chance of seeing that company's favorite protocol falling into disfavor.
Good point, Tim. It's ironic that on the one hand, the automation industry is attempting to get away from proprietary fieldbus protocols, which is leading to widespread adoption of Ethernet and new standards (e.g., for safety) being grafted on top of it. Yet here in the machine vision sector, which see forking and a battle among standards. The technical version of "can't we all just get along." More correctly, this is a typical market battle driven by advancing technology. USB3 is looking strong right now.
Beth, I'm all for standards... as long as they make my job easier. The great thing about standards is that in an ever-evolving technology environment they are of most benefit to the early-adopters. Standardizing on VHS, ZIP-disks, or RS-232 were all fantastic choices at the time -- and then we (predictably) evolved. Spending lots of time fretting about which standard will be around in 10 - 15 years really isn't a relevant question. In 1998 I was tasked with building a system that integrated six (6) scientific-grade 1-Megapixel CCD cameras. The frame grabber boards could only support two (2) cameras each, so the solution was three (3) PCs with one running as a master and the other two running as slaves. The fastest interface at the time was Ethernet so after lots of low-level TCP code the system acted as a single unit. I would have killed for USB3. =]
What is wrong with CoaXpress? That is a good standard! USB3 is an unneeded standard thhat is destined to deliver inferior results due to inferior hardware. Besides that, the only ones destined to benefit from USB3 are those selling the hardware. The connector format is neither robust nor particularly reliable, and not suited for any application where a field repair may ever be needed.
I realize that promoting a standard that someone has a financial stake in is logical, but the real purpose of USB3 is to obsolete previous versions and make money for the sellers. It is not really in a position to fill anyother real need.
So let us instead consider the other standards that are able to fill the requirements and fill the need for robustness and reliability.
I think there's some misunderstanding about machine vision standards, and the article's title may be a bit misleading. While some companies decide to adopt only one on the factory floor, for instance GigE because of its networking capabilities
the fact is that cameras compliant with more than one standard can often be mixed and matched in the same system or network (along with their frame grabbers if they have one). So there aren't really any major incompatibility issues.
Also, these standards are not created equal. They run at different speeds, use different types of cabling, etc. Only some of them are "proprietary," such as Camera Link and Camera Link HS, in the sense that their protocols are not used outside machine vision. The main big deal about GigE Vision and USB3 Vision is the fact that they are based on open, non-vision standards. Each vision standard is a specification, some very long and detailed, some pretty short, and each one governs the camera interface, either to a PC or to a frame grabber, or some other network device. Whether the spec is long and complicated or short and sweet depends on how much needs to be specified about things like data transfer conventions. In the case of USB3, these already exist, and so do the connectors, so very little is needed there.
TJ and Alex, machine vision standards tend to be fairly long lived, at least in semiconductor "time", including the original Camera Link, now 11 years old. To date, none have fallen by the wayside. Also, none are single-sourced. It's true that some new standards have been promoted by a single company, but that's a normal process within any standards organization. And this seems to be happening less often. Several recent standards, not confined to machine vision, have been promoted by industry groups, as happened with WiFi, DisplayPort, and now USB3 Vision.
Another thing to keep in mind is that, in machine vision standards govern the camera interface, and very little else. Where things can become confusing is on the customer end, not so much on either the vendor or system integrator end. The confusion has to do with sorting out what's now a lot more choices than there used to be, and deciding what's best for your particular app.
William, the one thing I can think of to justify a USB3.0 standard for vision is the availability of the interface as a standard feature of many computers. There is still a need for the others becuase of the limited cable distance that USB supports.
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.