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:

Click here to read the entire article

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.