With so many vision systems available today, it can be a daunting task trying to figure out which one is right for your particular application. Simply finding a system that can perform the necessary vision tasks is not enough; there are several other factors that need to be considered to ensure a successful deployment.

With competitive price and timely delivery, HBVCAM sincerely hope to be your supplier and partner.

 

These include:

&#; Variations in lighting conditions
&#; Networking and communications capabilities
&#; Accessories and product support options
&#; Ongoing post-deployment support

Advertisement

 

Whether you are new to machine vision or an experienced user, this guide will help you through the vision system selection process, providing answers to 10 critical questions and valuable tips for evaluating specific product features.

 

1. Does the vision system make it easy to set up applications, create custom operator interfaces and administer vision system networks?
Setting up a vision application should not require you to be a machine vision expert. Does the setup interface walk you through all of the steps of a vision application, including setting up the acquisition settings, finding and inspecting the part and communicating the results to other devices on the factory floor?  Does it require programming knowledge, or is it a configurable system?  Does the setup software make it simple to calibrate the system to work in real world units instead of pixels?  As you add tools to the application, does it show you a quick view of which tools are passing and failing to help you understand how well the application is set up? Does it allow you to build a complete operator interface to allow changing tolerances or to support line changeovers?
 
2. What is the importance of part location tools, and how can I assess their performance?
Part location software tools find the part within the camera&#;s field of view. This is typically the first step in any vision application, from the simplest robot pick-and-place operation to the most complex assembly verification task. It&#;s also the most critical step, because it often determines whether an application succeeds or fails, since you can&#;t inspect, measure or identify the part if you can&#;t find it.

Advertisement

While it sounds simple enough, locating parts in an actual production environment can be extremely challenging. Vision systems are trained to recognize parts based on a pattern, but even the most tightly controlled manufacturing processes allow some variability in the way a part appears to the vision system. Therefore, the vision system&#;s part location tools must be intelligent enough to quickly and accurately compare trained patterns to the actual objects moving down a production line, and tolerate variations in part appearance. It&#;s important for pattern matching tools to be able to tolerate large variations in contrast and ignore lighting changes, while being reliable enough to always find the right part.

 

3.  Does the vision system have a complete set of image pre-processing tools? 
Image pre-processing tools alter the raw image to emphasize desired features while minimizing undesirable features. This prepares the image for optimal performance by more powerful vision tools and can significantly improve the accuracy and robustness of the overall system. Pre-processing tools can:

&#; Increase the contrast between the part and its background,
&#; Mask insignificant and potentially confusing image features,
&#; Eliminate &#;hot spots&#; reflecting off the part surface, and
&#; Smooth rough surface textures.

Advertisement

Make sure that a complete set of image pre-processing tools is included with the vision system you choose.  

 

4.  What should I look for in character reading and verification capabilities?
Whether you&#;re reading stamped alphanumeric codes on automotive parts or verifying date and lot code information on medicine bottles or packages, there are several capabilities to look for when evaluating character reading and verification tools, including:

&#; Statistical font training&#;This capability builds a font by learning models of characters that appear in a series of images. The images should include multiple instances of each character, and span the full range of quality likely to occur in production. The resulting font will be highly tolerant of normal variations in print quality, whether due to poor contrast, variable locations, degradations, or variations in stroke widths. Unless you know in advance that every code will be marked with the same quality seen in the reference images used to learn the character models, statistical font training can be crucial to the success of your reading or verification application.
&#; Image pre-processing tools&#;These tools optimize a trained model by sharpening the edge contrast of characters and filtering out extraneous background in the image. Optimized models maximize the reliability and repeatability of the vision system.
&#; Instant image recall&#;This capability enables line operators and technicians to quickly and easily view failed images on a display. Whether the failure is caused by a camera jarred out of position or a missing or damaged label, it is important to know immediately why the failure occurred so corrective action may be taken.

 

5.  How can I determine the repeatability of a vision system&#;s gauging tools?
If your application involves critical dimensional measurements, the vision system&#;s gauging tools must be accurate and perform with a very high degree of repeatability. 
The vision system should have a full suite of gauging tools which will allow you to choose the right one to fit the requirements of your measurement application without having to write custom scripts or functions.
For high accuracy measurements, the vision system should be able to correct the lens distortion that can affect measurements, especially in the outer areas of the image.

 

6.  How do I evaluate industrial code reading tools and what are some specific features to look for?
Industrial environments demand a vision system that can read 2D Data Matrix codes that are degraded, poorly marked, or vary in position from part to part. The vision system should perform well regardless of the part material (such as metal, glass, ceramic, and plastic) and the type of part marking method employed (such as dot peen, etching, hot stamping, and inkjet).
Beyond these criteria, there are several specific code reading features worth inquiring about:

&#; Code quality verification&#;Look for products that can verify code quality to established standards. This can provide valuable information about how well the marking process is working.  
&#; Reading speed&#;Depending on your production line speed and throughput requirements, you may need a very high-speed reader. The fastest vision systems available today can read more than codes per minute.

Contact us to discuss your requirements of Camera Module Suppliers. Our experienced sales team can help you identify the options that best suit your needs.

 

7.  What networking and communications features should I look for?
Networking is essential to many vision applications as a means to share data, support decision-making, and enable highly-efficient integrated processes. For example, networking enables vision systems to transmit pass/fail results to PCs for analysis, or communicate directly with PLCs, robots, and other factory automation devices in an integrated process control system.
If you need to link your vision systems to PCs at the enterprise level, choose a system that supports the complete set of standard networking protocols:

&#;TCP/IP client/server enables vision systems to easily share results data with other vision systems and control devices over Ethernet without any code development.  
&#;SMTP (Simple Mail Transfer Protocol) enables you to immediately receive an on your PC or cell when a problem occurs on the production line.  
&#; FTP (File Transfer Protocol) allows inspection images to be stored on the network for later analysis.
&#; Telnet is an Internet standard protocol that enables remote login and connection from host devices.
&#; DHCP (Dynamic Host Configuration Protocol) allows  a vision system to automatically receive its network IP address from a server, enabling true plug-and-play performance.
&#; DNS (Domain Name Service) allows you to assign each vision system a meaningful name, such as &#;Bottling Line System 1&#;, instead of having to use a numeric IP address.

To integrate a vision system with the PLCs, robots and other automation devices in your plant, the system you choose must also support the following:

&#; Industrial Ethernet protocols such as EtherNet/IP,  PROFINET, MC Protocol and Modbus TCP. These enable vision systems to be linked to the most popular PLCs and other devices over a single Ethernet cable, eliminating the need for complex wiring schemes and costly network gateways.
&#; Fieldbus networks, including CC-Link, DeviceNet, and PROFIBUS. A protocol gateway accessory is usually needed to add a vision system to a Fieldbus network.
&#; RS-232 and RS-485 serial protocols, needed to communicate with most robot controllers.
Finally, as more and more vision systems are used throughout the manufacturing process, the need for a centralized way of managing them becomes increasingly important. Make sure the vision system you choose comes with software that allows you to easily control and monitor the operation of all your vision systems remotely over the network from any location&#;on or off the plant floor.
 
8.  What should I know about vision system accessories?
Too often, so much attention is given to evaluating the vision system that accessory products are almost an afterthought. But the choice of accessories can go a long way towards ensuring trouble-free system integration and, in the case of lighting, can even make or break the application.
For quick and painless integration of your vision system, it makes sense to buy from a vendor that offers a complete family of compatible accessories. This gives you the assurance of knowing that each and every accessory has been tested and confirmed to be compatible with the vision system. More importantly, during the application evaluation process, the salesperson should be able to help specify the best lighting and optics solution to give the best chance for a successful vision application.
Accessories to look for include:
&#; Lights&#;No two production areas have the same ambient light conditions, and parts can exhibit a wide range of surface characteristics. Nearly every machine vision solution requires a unique lighting approach to meet its objectives and optimize performance. Your vision system vendor should offer a variety of lighting options, including: ring lights, which provide soft, even illumination from all directions; back lights, which create maximum contrast between a part and its background; and dark field lights, which provide low-angle illumination for imaging of part surface irregularities.
&#; Communications modules&#;Make sure your vendor offers communications peripherals such as I/O modules and network gateway modules that support easy, quick connectivity between the vision system and PLCs, robots, and other factory automation devices and networks. Industrial connectors?
&#; Operator interface panels&#;A networked operator interface panel allows easy, plug-and-go set-up and deployment, plus ongoing monitoring and control of vision systems without a PC. When selecting an operator interface panel, look for  one with an intuitive, touch-screen interface and support for multiple camera views. It should also be tough enough to stand up to the manufacturing environment, with an anti-glare impact shielded LCD display and NEMA-rated mounting bezel that provides a dust- and liquid-tight seal when mounted in a panel or enclosure.

 

9.  Does the vision system vendor offer a wide range of hardware options? Are they rugged enough for my environment?
Your chosen supplier should be able to offer you a variety of choices of systems base on performance, resolution and durability. Machine vision is not a &#;one-size-fits-all&#; purchase. Your application may require a line scan camera as opposed to an area scan system or even a color system.  You may need more resolution in order to meet your tighter tolerances or need a system that can withstand wash down. Your supplier should be able to provide options that will meet your needs of inspection and also for your physical environment.
Additional questions include: Do you have room to install a vision system on your line? If space is a constraint, there should be options in terms of actual system size as well as acquisition options. For example: If the viewable product space is limited, a line scan camera maybe an option to consider. Unlike area scan cameras that need to see the entire part to take a full snapshot of it, a line scan camera needs to see only a sliver of the product to build the entire image into memory. Think of this comparison as a photo copier (area scan), vs. a desktop scanner (line scan). Or if the space to install the vision system is limited, a smaller package would take up less room and require less mounting space.
Once you have the physical size constraints taken care of, it is now a question of what resolution is necessary for your specific application. Resolution of a vision system is the size of the imager used and is given in pixels. Typically, the more pixels you have, the more data you capture per feature. The more data per feature, the more accurate and repeatable measurements you will have. To get an idea of resolution, ask yourself, what
field of view do I really need? Do I need to capture the width of the assembly line, or a portion of a larger part, or the entire part itself?  What do I need to see in the image in order to inspect this part? The target resolution is determined from these answers.  For example: Your inspection is to count the number of parts on a tray. If your field of view is the width of your assembly line, for example, 12 inches, and your vision system has a
resolution of 640 x 480, then you would have 640 pixels to equal 12 inches. This equates to 53 pixels per inch (or each pixel represents 0.018 inches).  If you are counting the number of parts in each tray, this resolution may be sufficient. However, if you are measuring the width of each individual part and need a tolerance of +/- 0.001 inches. Then more pixels will provide you with more data per feature to achieve the accuracy of the tolerance.  
Sometimes, the features you are inspecting do not have enough contrast in a monochrome vision system, even with specific lights and filtering. A color system maybe able to bring out the subtle differences in features and colors that you need in order to complete your inspection.
Some vision systems are assembled into rugged, IP and NEMA-rated metal cases to withstand dust and moisture without requiring a separate enclosure accessory. However, if the environment in your plant is especially harsh or requires frequent wash down of equipment, ask your prospective supplier if they offer external enclosures pre-qualified for use with the system.

 

10.  Does the vision system supplier provide the support and learning services I need?
Even the highest performance vision system is only as good as the suppliers who stand behind it. Whether you buy your vision system from a distributor, a systems integrator, or direct from the manufacturer, it&#;s important to know in advance the full range of support services available to you. Be sure that the vision supplier you choose understands your unique support requirements and provides you with all of the resources you will need during every phase of the project, from application development and systems integration, to deployment and beyond.

John Lewis is the market development manager for Cognex. To learn more, visit www.cognex.com.

Choosing a Camera for your Product

by Maharajan Veerabahu  

Introduction

This document would serve as a reference to customers interested in using e-con's e-CAM solution or use its Windows CE/Linux/Windows Mobile* solution to develop various applications such as 1D/2D bar code capture, face recognition, visiting card data capture and Video capture.

Intended Audience

The document is intended for product managers who are interested in integrating camera in to their products and are in need of a complete solution starting with lens assembly, choosing the right sensor for their application and finally provide the Linux/Windows CE/Windows Mobile drivers with appropriate applications.

Choosing the camera and the software

One of the most frequent questions we receive is how do I choose the right camera. By camera we mean the right CMOS sensor with the right lens assembly. Here are the questions the product manager should ask before choosing the camera

 

 

• Do I require a fixed focus or an auto focus camera?
• Does my application need capture at very close distances like 10cm or do I need to capture pictures beyond 20m? How far is my target object from the camera?
• What is the resolution I need to support my application?
• Do I need an OS to use the camera? If yes, what OS should I use?
• Is my environment noisy?
• What type of sensor do I need?
• What is the ambient lighting condition for my application? What is the performance level expected in low-light condition?
• If my application requires video capture, what is the capture rate required at the desired capture resolution?
• If my application requires preview, what is the preview resolution required and preview fps (frames per second) required? How much processing is required after capture of each frame?
• How can I interface e-CAM with my target board? What are the requirements on power supply, clock and interfacing?

 

Let's take an example here. If the need of the customer is to capture data from a visiting card then the camera needs to have a fixed focal length and that needs to be less than 10cm. By fixed focal length, the distance between the camera and the object of focus is fixed with 30-40% variance in distance. Also a VGA resolution is good enough for this type of application since the capture area is very small. The application here such as scanning the visiting card and getting the data out of it would involve programming in a high level language and would use many commonly available libraries that run on top of an OS like Windows/Linux. Hence a need of an OS becomes necessary. If the environment is noisy then it is important to choose a sensor that has a high S/N ratio. Finally applications like this need a black and white sensor

 

Another example would be if the customer wants to capture pictures at variable distances from the camera. This would mean the customer needs an auto focus camera and if the customer needs to capture Video and save it or would want to give an application interface for the end user to develop applications using the camera, it would become mandatory to go for a standard interface like Microsoft Direct show or Video for Linux. Table 1 shows a table that would indicate what type of sensor you should choose based on the application.

  Application Fixed focus Auto focus Recommended sensor and software framework 1D/2D bar code

x

  VGA type black and white sensor with macro lens assembly. Good Facial recognition

x

x

Auto focus sensor is a requirement. IRIS recognition

x

  VGA type black and white sensor with macro lens assembly Still image capture  

x

Auto focus 2M pixel or higher. Microsoft Directshow or video for Linux is recommended. PDA camera  

x

Auto focus 2M or higher Video capture and recording, Video mixing  

x

Microsoft DirectShow  

e-con's Camera solution

 

e-con provides complete end-end solution for a customer interested to include camera in its product line. Fig 1 shows the various strengths and skill sets e-con possesses. Here is the brief outline of e-con&#;s strengths

 

 

• e-con has got ready made drivers for Windows CE / Windows Mobile and Linux for various camera modules on processors like PXA270, PXA320, AU. So if the product that is to be integrated with camera
• e-con has camera solution ranging from 0.3 M to 5M pixel.
• e-con has a good network of sensor and lens assembly makers. In this aspect, e-con would be able to understand the application requirement and would choose the right sensor and lens assembly for the customer.
• e-con has daughter boards for the various camera modules for reference boards like Sirius, Triton starter kit 3 and Triton starter kit 4 . Customers can test their application with various camera modules and once they decide that a particular camera is the right fit for their application then they can go ahead with that. e-con indirectly saves lot of R & D time for the customer in this aspect since tested drivers and daughter modules are available for the various modules.
• e-con has got integrated sample applications with its camera drivers like Video streaming, video capture/still capture and has relationships with third parties which can do 1D/2D bar code capture and facial recognition.
• E-con exposes the API for its driver package with complete documentation and provides sample applications for easy reference
• e-con would act as a one stop shop for the customer regarding the camera.

 

Figure 1 - e-con's camera strengths

 

Summary and conclusion

Choosing a camera involves lot of steps like defining the application, choosing the right sensor/module for that application, choosing the right OS and then deciding on the application development. All these involve considerable time and e-con would fit in the role of a partner to the customer with extensive experience in camera development there by reducing the time to market.

If you want to learn more, please visit our website 2mega Pixel USB Cameras.