The CMM Handbook


Announcing the most comprehensive CMM Handbook. The CMM Handbook is now available. This book will put the best CMM resource material at your fingertips. Never before has this data been collected and placed in one resource book.

This book is the resource book you want in your library of books.

Click on the picture to see a sampling of the table of contents.

This book is available for $115.00 U.S. and includes shipping in the U.S. add $10.00 for international orders to cover shipping.

To purchase The CMM Handbook click on the Buy Now Button on the upper right hand panel.

DMIS programming ... Overview.

This is the first in a series of articles describing the process of DMIS programming.

This is the first in a series of articles describing the process of DMIS programming. In future articles I will be covering specific areas of a typical DMIS program and providing actual program listings of those areas. I will try to cover the most important aspects of each area, giving the reader tips and tricks learned along the way. This first article is designed to provide an overview of the basic structure of a program and highlight the areas that any user should consider including in their program.

DMIS programs should be designed to be as portable as possible so that they can be used on different DMIS compatible CMMs. This means that all aspects of a program’s operation must be defined and the user should not assume that the CMM will take responsibility for any setting. A typical DMIS program starts with a DMIS main or module statement (DMISMN or DMISMD) and ends with an end file statement (ENDFIL). The commands contained between these statements will be driven by the demands of the inspection process. Most DMIS programs should include the following areas:

PC-DMIS

Forms

With the introduction of new versions of software, there will be leaders and there will be followers. The leaders take the reigns and forge ahead using the “beta” version of the software, wallowing in the fact that they have the new version and they are at the forefront of their profession....

The followers wait for the leaders’ feedback on what they have encountered with the new software; good or bad.
PC-DMIS is well known for releasing new and improved versions at least once per year. With the introduction of the newest version 4.0 and above, the group at WILCOX has changed the playing field once again. The reporting methodology has been overhauled, HYPER-REPORTS have been removed from the software, FORMS have been added as an option, and a multitude of vision and articulated arm algorithms have been added or improved. Future articles will be covering some of these topics and more.

Today’s topic will look at the usage of the FORM as an alternative to hyper-reports in a program. Specifically, the process for embedding a set up photo into a FORM and linking it in a program will be reviewed. Keep in mind that all the options that a FORM may be appropriate for will not be covered in this article.

When the FORM window is opened for the first time, one would think they are looking at the HYPER-REPORT window.

PC-DMIS

Probe Qualification

Probably the most important aspect of measuring parts on a CMM is getting the probe, or probes, to be in relationship to one another. As it happens, this procedure is one of the most frequently asked questions on the internet forums and least understood. Qualification, as this process of relating a probe setup to the CMM is called, is the topic of discussion today. We will start by qualifying a single probe setup. To begin, the PROBE UTILITIES window must be accessed. To do this, go to INSERTHARDWARE DEFINITIONPROBE. Once the PROBE UTILITIES window has been accessed, a name has to be given to the probe that is going to be created.

PC-DMIS Training

Using CAD models in 4.1 and above; importation and transformation.

The software developers at Wilcox have been hard at work to improve PC-DMIS for the last few years. With their hard work they have added many new features that may not be known to the average programmer. This flexibility is making the usage of the software easier and easier for the seasoned programmer. At one time the programmer would have to hunt down an engineer that had some knowledge of CAD software if a “tweak” was need to an .iges or .step model. As of the PC-DMIS 4.1+ version(s), the CMM programmer can easily manipulate the models from within the software.

As an example, many times a program will have been created in standard units and the next CAD model given to the CMM programmer will have been exported from its native software in metric units. This change may have been intentional or an oversight, but either way, it would have a required a rewrite of the program or the very least for someone that had access to the native CAD software to export in the proper units. All of this manipulation can cause errors. PC-DMIS now allows the CMM programmer the ability to import .iges and .step files regardless of the units used for its’ creation.

Another improvement in PC-DMIS is the ability to “transform” the CAD data once the .iges or .step file has been imported. Similar to the units of measurement issue, sometimes a CAD model can be imported and the origin of the part may not be where the blueprint states it should be. In many cases there are a number of authors that work on a CAD model. Each one of those authors opens, saves, and closes the CAD model numerous times in its’ life and at some point the origin is either moved or re-oriented upon a new model being created.


Click Here to read the entire article

Welcome to CMM Handbook - The Blog

CMM Handbook is designed to help the coordinate measuring machine programmer with general understanding of how to program a CMM. Techniques and advice will be given along with knowledgeable articles.

Your comments are welcome.