Version 3.0
Errata and Addendum

Chapter 1 Introduction

Back to Top

Chapter 2 User Interface

Back to Top

Chapter 3 File Options

The first three paragraphs of the "Import" topic in the "File Options" section should be changed to exclude TUTOR file types. It should now read: "The FILE | IMPORT option lets you import data from an input data file into the current part program. The input data files that can be used can be any of these file types: · CAD (IGES, DXF, STEP, VDAFS, DES or XYZIJK) · DMIS · AVAIL · DIMS PC-DMIS keeps track of the CAD data as a separate file. This file will have the same OS file name as the part program, but will have the ".CAD" extension. All operations, such as RENAME, DELETE, and COPY are also done on the associated CAD file (if one exists). " - - - - - Detailed information on using the "IGES Setup" dialog box to Alter the CAD display for imported and exported images has been added to this site: http://www.wilcoxassoc.com/files.htm#instructional_files (see the IGES Setup link). Information from that document will appear in the v35 manual. - - - - - ADDED JANUARY 9, 2003 In the "Mirror" topic, the following "Important" note should be added: "Important: PC-DMIS also attempts to mirror your probe's AB tip angles. If your probe does not have the exact mirrored tip angles already defined and calibrated, PC-DMIS may choose the closest calibrated tip angles. It chooses closely calibrated tip angles if the calibrated tip angles exist, and are within the wrist angle amount specified in the Wrist Warning Delta box on the Part/CMM tab of the SetUp Options dialog box (the "Using the Road Map" appendix provides instruction on accessing all dialog boxes and menu options). If no closely calibrated AB tip angles exist, then PC-DMIS will create perfectly mirrored yet uncalibrated AB tip angles."

Back to Top

Chapter 4 Utilities

The toolbar in the topic, "Basic Script Editor Toolbar", should be changed to only contain the following icons: New Open Save Print Print Preview Find Cut Copy Paste Undo Start Minor Issue: Since statistics software other than DataPage can be used with PC-DMIS (i.e. SPC-Light) references in the manual to "DataPage" as a generic term for a statistical software package should be replaced with "Statistics", "Statistical", or "statistics software" as appropriate. Some items deal with DataPage specifically. These didn`t change. For example, Utilities | Statistics shows the Database Parameters dialog box. This dialog box has the DataPage Variable Name area. Specific references to Datapage like this didn't change. ----- The procedure located in the "Equate Alignment" topic should be updated to read as follows: "For example, to measure a dimension that references features on two sides of the part that are not accessible from a single part orientation: 1. Measure the alignment features on the first side of the part. 2. Create the original alignment. 3. Measure all required features that can be reached from the first orientation of the part. 4. Move the part to its new position. 5. Measure the new alignment features. The origin must be the same and the axis must be in the same direction as the axis of the alignment you are equating to. It is easiest to understand this if you imagine that the original origin and axes' arrows were glued onto the part before moving it. The new alignment places the origin and axes' arrows in the same position with respect to the part. 6. In the Equate Alignment list, select the new alignment. 7. In the With Alignment list, select the old alignment. 8. Click the OK button." ----- The topic "Active Tip List" contains a subtopic "Calibration Order" the procedure described to set the calibration order should be re-written as follows: "To set the calibration order: 1. Select the 'User Defined' option in the 'Measure Probe' dialog box (See the 'Measure' topic). 2. Hold down the CTRL key. 3. With your left mouse button, select the tips from the Active Tip List for calibration. A number representing the index of the tip measurement order appears next to each Tip ID as it is selected." ----- The topic "Read Line" contains three examples. The second example is incorrect. The example should changed from... The command line: File/ReadLine,F1, "Location:"+{CIR1.X}+ ","+{CIR1.Y}+ ","+{CIR1.Z}+ ","+{CIR1.I}+ ","+{CIR1.J}+ ","+{CIR1.K} would read in comma delimited text after the string "Location:" and store the values in the X, Y, Z, and I, J, K values of CIR1. ... and should be rewritten as follows: The command lines: File/ReadLine,F1, "Location:"+{VARX}+ ","+{VARY}+ ","+{VARZ}+ ","+{VARI}+ ","+{VARJ}+ ","+{VARK} ASSIGN/CIR1.XYZ = MPOINT(VARX, VARY, VARZ) ASSIGN/CIR1.IJK = MPOINT(VARI, VARJ, VARK) would read in comma delimited text after the string "Location:" and store the values in the X, Y, Z, and I, J, K values of CIR1. - - - - - Under the "Rotate 3D" topic, the sub-topic "Rotate 3D using Rotate Dialog Box" contains a procedure that had references to an Apply button, that doesn't exist on the 'Rotate' dialog box. The procedure should be changed to read: "To rotate the drawing using the dialog box: 1. Select the view to be altered (numbered as 1-4 option buttons). 2. Determine the amount of rotation by selecting the 'Degree Increment' (1, 5, 10, or 45) option. 3. Click on the desired axis button to rotate the drawing. 4. Select the 'Close' button. PC-DMIS displays the changes to the CAD image in the Graphics Display window. Clicking the Reset button will change the drawing in the dialog box back to the previous view." - - - - - The "Rotate 2D by Dragging" topic contains a paragraph that reads "When the mouse button is released, PC-DMIS will re-draw the rotated image to reflect the amount the mouse was dragged around the imaginary center point." This is incorrect. PC-DMIS redraws the image dynamically as the mouse is being moved. The procedure and the ending paragraph should be re-written as: "To rotate by dragging: 1. Position the mouse pointer in the Graphics Display window (in any area other than at the center). 2. Hold down the right mouse button. 3. Move the pointer clockwise about the imaginary center of the display window. PC-DMIS redraws the image dynamically as you move the mouse. 4. Release the mouse button. PC-DMIS keeps your current rotation." - - - - - The "Alignment Start" topic doesn't contain documentation describing the LIST=YES/NO portion of the ALIGNMENT/START command. It should be rewritten as follows: ==Start Alignment Command== ALIGN_ID=ALIGNMENT/START,RECALL:ID, LIST=YES/NO Changeable fields: "Align_ID" This is the ID the alignment will be stored as. The ID is assigned by the operator. A default name will be assigned if an ID is not specified. Example: A1. "ID" ID is a previous internal alignment that will be recalled to start a new alignment. "LIST" Setting this equal to YES or NO lets you determine whether or not PC-DMIS should display the alignment ID in the Alignments list on the Settings toolbar for later insertion in the part program. This is useful if you have a lot of temporary alignments and you don't want them all listed in the Alignments list on the Settings toolbar (see the "Alignments List" topic). - - - - - Under the "Else / End Else" topic the line "The Edit window command line for a WHILE / END WHILE statement reads:" should be rewritten as follows: "The Edit window command line for a ELSE / END ELSE statement reads:" - - - - -

Back to Top

Chapter 5 Construction Options

In the topic "Constructing a Cast Cylinder" steps one and two should be rewritten as follows: 1) Select Construct | Cylinder from the menu bar. The Construct Cylinder Mode dialog box will appear. 2) Select the Cast option. - - - - - Step 2 of "Changing the Direction of a Cylinder" uses the word "either" with only one option: "Select either the Reverse option." This should be rewritten to read "Select the Reverse option". - - - - - The topic "Constructing a Cast Cone" uses the word "either" with only one option: "2. Select either the Cast option". This should be rewritten as "2. Select the Cast option". - - - - - The topic "Constructing a Point" uses the word "either" with only one option: "5. Click either the Create button". This should be rewritten as "5. Click the Create button". - - - - - In the topic titled "Sphere Construction" there is a statement that reads, "You can switch between the different types of spheres by placing the cursor on TOG3 and clicking the left mouse button." This is incorrect. It should read "You can switch between the different types of spheres by placing the cursor on TOG3 and pressing F7 or F8." The sentence, "The keyboard can also be used to switch toggle fields" should also be deleted. - - - - - The first sentence of the "Constructing a Projected Sphere" topic reads: "A sphere can be constructed from any feature into the current working plane." This should be changed to read "A sphere can be constructed by projecting any feature into the current working plane." - - - - - The opening paragraph of "Constructing a Perpendicular Line" should be rewritten as "A line can be constructed perpendicular to the first input feature and passing through the centroid of the second input feature." - - - - - The topic "General Command Format" under the text for "TOG2" contains a list of possible constructed features. These are "CIRCLE / CONE / CYLINDER / LINE / PLANE / POINT / SPHERE / CURVE / SURFACE / SET / ELLIPSE". This should be rewritten as "CIRCLE / CONE / CYLINDER / LINE / PLANE / POINT / SPHERE / CURVE / SURFACE / SET". The ellipse construction type shouldn't be included. - - - - - The following should be added to the "Constructing an Intersect Point" topic: "If you want to 'intersect' or pierce a circle with a line, see "Constructing a Pierce Point". - - - - - The "Cylinder Construction" topic describes the Edit window syntax for a sample cylinder construction. The diam and length should be switched. Thus, it should be changed to read as follows: "The Edit window command line for a sample Cylinder Construction would read: feature_name=FEAT/CYLINDER,TOG1,TOG4,TOG5 THEO/x_cord,y_cord,z_cord,i_vec,j_vec,k_vec,diam,length ACTL/x_cord,y_cord,z_cord,i_vec,j_vec,k_vec,diam,length CONSTR/TOG2,TOG3,......" - - - - -

Back to Top

Chapter 6 Dimension Options

The defenitions for different check boxes for the "Default Axes" topic (the Axes area on the Feature Location dialog box) was missing definitions for the H value and the Prad and Pang values. The check box definitions should read as follows: Z = prints Z axis value. Prad = prints the Polar Radius. Pang = prints the Polar Angle. D = prints Diameter value. R = prints Radius (half of Diameter) value. A = prints Angle (for cones) value. L = prints Length (used for cylinder and slots.) H = prints the Height (usually height on slots, but also length on cones, cylinders, and ellipses). V = prints the Vector location. ---- Under the topic "Sheet Metal Axes", the default dimension info "RT, S, RS" for a sheet metal edge point should be replaced to read: "X,Y,Z, and T"

Back to Top

Chapter 7 Auto Utility

Back to Top

Chapter 8 Scanning Options

The topic "Execute Mode" describes various modes used when executing a learned scan. The text under "Normal Mode" should be rewritten as follows: "When Normal is selected, PC-DMIS will execute the scan in it's 'normal' manner; it will trigger a hit when the probe touches the part." ----- Under the "Basic Scan" topic, the "Boundary Dialog Box" sub-topic's initial sentence has an error. It currently says: "Some of the Basic Scans like Circle, Cylinder, Axis, and Null do not need a Boundary condition since they are executed by the controller. " The word 'Null' scan should be replaced with 'Center'. Null is not a scan type.

Back to Top

Chapter 9 System Options

The Optional Probe section (see Options | Parameters | Opt. Probe tab) should change to read: The Opt. Probe tab gives you additional capabilities for controlling analog probes. These capabilities include the following probing related values: · Max Force · Low Force · Upper Force · Trigger Force · # Return Data · Return Speed · Positioning Accuracy · Probing Accuracy · Probing Mode · Manual Fine Probing It also includes the following Scan related values and general purpose buttons: · Point Density · Offset Force · Acceleration · Default button · Recall button · Clear button Each of these is described below in greater detail. Max Force The Max Force box allows you to enter the maximum force that a probe will take before an error will occur thus stopping measurement. During an analog probing cycle, when the probe first touches the part it continues to move into the part until it reaches this Max Force value. It then reverses direction and moves away from the part. This movement into the part, after touching the part, is sometimes referred to as the contact force. The value is specified in Newtons. In a normal deflection mode (DFL) probing cycle, the controller collects data as the probe moves away from the part. Note: A "newton" is a unit of force. One Newton is the force needed to accelerate a mass of 1 kilogram to a speed of 1 metre per second per second. Low Force The Low Force box allows you to enter the minimum force required to determine when the machine is in contact with the object being measured. For a normal deflection mode (DFL) probing cycle, this is the force at which the controller stops collecting data. The value is specified in Newtons. Upper Force The Upper Force box is the upper limit for a measurement. When this force is reached the machine moves back, away from the object being measured. For a normal deflection mode (DFL) probing cycle, this is the force at which the controller starts collecting data. The value is specified in Newtons. Trigger Force The Trigger Force box allows you to enter the force at which a measurement reading is taken. For a normal deflection mode (DFL) probing cycle, this is the force at which the Actual Point (APT) will be calculated and returned to the application. The value is specified in Newtons. Not all analog probes/controllers use this input. # Return Data The # Return Data box allows you to enter the number of readings taken when the machine is moving away from the object being measured. This value defines the minimum number of data to be collected within the probing window defined by the Upper Force and Lower Force values. Return Speed The Return Speed box allows you to set the value, which determines the speed at which the probe comes off the object being measured. This is specified in mm/sec. Positioning Accuracy The Positioning Accuracy box is a parameter specific to the Leitz interface. The value submitted tells the CMM how carefully it should remain on the approach vector as the probe is moved into the part for a measurement. The smaller the value, the more difficult for the machine to acquire the desired location but the more accurate the measurement. This value is always in millimeters. This should normally be left at the default value. Probing Accuracy The Probing Accuracy box allows you to determine the accuracy required to take a measurement. If this value is not met then no measurement is taken and an error is given. It is specified in mm and should normally be left at the default value. Probing Mode This specifies the type of probing cycle used. The most common cycle is deflection mode (DFL). Other modes, such as soft probing (SFT), may also be supported by some analog probes/controllers. In some cases the probe/controller may not have multiple modes and this value is ignored. Manual Fine Probing If the Manual Fine Probing check box is selected, then when a manual probing point is taken, the controller automatically switches to DCC mode while moving away from the part in order to use the normal deflection probing cycle. This may result in slower manual probing but improves accuracy. Not all analog probes/controllers have multiple modes for manual probing. In those cases this value is ignored. Point Density The Point Density box allows you to set the number of readings to take per millimeter of measurement during a scan. Offset Force This allows you to specify what level of force to maintain during a scan. The value is specified in Newtons. Acceleration This allows you to specify what acceleration to use during a scan. The value is specified in mm/sec/sec. ------------------- The "Temperature Compensation Setup" section (accessed in PC-DMIS from Options | Temp Comp menu)of the manual contained very limited information on compensating for temperature. Follow this link to download additional information: ftp://ftp.wilcoxassoc.com/docs/UsingThermalCompensation.zip

Back to Top

Chapter 10 Graphic Options

Back to Top

Chapter 11 Editing a Part Program

Under the section "Add Generic Feature" these two subsections should be included: Alignment Dependent Generic Feature: Alignment dependent generic features have values dependent upon the alignment from which they are referenced. They change so that they are always relative to the current alignment. Their location is constant in 3D space. Example in 2D: Suppose 0,0 is your machine origin. An alignment is set up that locates the origin at 5,5. Now, an alignment dependent feature is defined after the alignment with the values of 2 for x and 2 for y. Relative to the alignment, its values are 2 and 2. Relative to the origin, its values are 7 and 7. No matter what alignment the numbers are given relative to, the point will always be located at 7,7 relative to the true origin. Alignment Independent Generic Feature: Independent generic features have values that remain the same regardless of which alignment they are referenced from (therefore considered "independent"). Their location in 3D space changes as the alignment changes. Example in 2D: Next, consider the same example of 2,2 (as shown in the Alignment Dependent example) but this time with an alignment independent generic feature. If you ask for the x and y values relative to the alignment, the object will report 2,2. If you ask for its values relative to the origin, the object will still report 2,2. The set 2,2 relative to the alignment is located at 7,7 relative to the true origin. The set 2,2 relative to the origin is exactly that: 2,2. Thus, the point appears to move in 2D space. Note: The independent option was added so that a generic feature named XAXIS, for example, could always be used as an input feature to a construction or a datum to a dimension and it would always have the values of 1,0,0 independent of the current alignment. ----- A sentence in the "YES / NO" topic currently reads: "The message box will displayed any previously entered text and YES / NO buttons.". This should instead read as follows: "The message box will display any previously entered text and YES / NO buttons. " - - - - - - - - - - The "Replace" topic should contain the following note after the initial paragraph.: "Note: Replacing text in limited to only one field. Example: you cannot replace all instances of PERM = 0 with PERM = 3 because PERM = 3 is actually two separate fields: "PERM =" and "3". This addition will appear in the version 3.5 manual. - - - - - The first line under the topic "Command" reads: "The Command tab allows you to chose which of the following display options are available for command mode." The word "chose" should be changed to "choose". - - - - - The "Report" topic contains a table describing various check boxes found in the Report tab of the Customize dialog box. In the table there is an extra period preceding one of the Show Comments check box headings. The text ".Show Comments" should simply read "Show Comments". The step 2 for the topic "Copying, Cutting, and Pasting Commands" says "Chose the copy or cut commands from any of these locations". The word "chose" should be changed to "choose". - - - - - The "Report" topic contains a table describing various check boxes found in the Report tab of the Customize dialog box. In the table there is an extra period preceding one of the Show Comments check box headings. The text ".Show Comments" should simply read "Show Comments". - - - - - The topic "Breakpoints" contains a sentence that's missing a period. In the second paragraph, the sentence "Once PC-DMIS has paused for the breakpoint, you may want to use the Step Next button" needs a period at the end. - - - - - In the "Breakpoints" topic, under "Remove Defaults", the sentence: "The Edit | Breakpoints | Remove Defaults menu option allow you to remove breakpoints throughout the part program from default locations." contains the phrase "allow you to remove". This should be rewritten as "allows you to remove". - - - - - In the topic "Mark All", the text "PC-DMIS also displays an asterisk (*) next to each feature ID in the Graphics Display window that are marked for execution." should be rewritten as "PC-DMIS also displays an asterisk (*) next to each feature ID in the Graphics Display window that is marked for execution." - - - - - The first note under the "Miscellaneous Functions" topic has a line that says "Adding a 'T' in front of 'Offset', 'Diameter', or 'Thickness' will returned the theoretical information". The phrase "will returned" should be "will return". - - - - - Under the "ID Wild Cards" topic, the sentence "The question mark '?' character is used to a single instance of any character." is incomplete and should be rewritten as "The question mark '?' character is used to refer to a single instance of any character." - - - - - In the printed documentation, the topic "Analysis" needs a space before the word "in" with the phrase "see 'Analysis Settings'in chapter....". It should read "see 'Analysis Settings' in chapter....". - - - - - The topics "Cut", "Copy", and "Paste" mention the Clipboard as the "Windows 95 clipboard" or "Windows clipboard". These should be changed to simply "Clipboard". - - - - - Under the "String Functions" topic, syntax for the second expression in the LEFT string function should be changed to read as follows: "LEFT Left n characters of string: LEFT(<String>, <Integer>) " - - - - -

Back to Top

Chapter 12 Executing a Part Program

Back to Top

Chapter 13 Guide to Measuring a Part

Back to Top

Chapter 14 Hyper-View Reporting Tutorial

Nov. 9, 2001 - In depth documentation is available for all the HyperView objects on the "Object" bar and for all the options on the "Layout" bar. This documentation will be made available as part of PC-DMIS Version 3.5's documentation. You can download this document from our ftp site, by following this link in your internet browser: ftp://ftp.wilcoxassoc.com/docs/hyperviewobjectsandlayout.zip ----

Back to Top

Appendix A Off-Line Part Programming

Topic "XYZ ASCII File", text defining the generated feature following the number 3 should be replaced with the following: Numbers per Row (with description and generated CAD): 3 1st number=X value 2nd number=Y value 3rd number=Z value Point with no vector 4 1st number=X value 2nd number=Y value 3rd number=Z value 4th number=diameter CAD circle with a workplane based vector 5 1st number=X value 2nd number=Y value 3rd number=Z value 4th number=nothing 5th number=nothing Point with no vector 6 1st number=X value 2nd number=Y value 3rd number=Z value 4th number=I value 5th number=J value 6th number=K value Point with a vector 7 1st number=X value 2nd number=Y value 3rd number=Z value 4th number=I value 5th number=J value 6th number=K value 7th number=diameter Circle with vector 8+ 1st number=X value 2nd number=Y value 3rd number=Z value 4th number=I value 5th number=J value 6th number=K value 7th number=nothing 8th number=nothing Point with a vector Topic "XYZ ASCII File", The example table at the end should show a comma following each number.

Back to Top

Appendix B Translating a Part Program into PC-DMIS

This section of the manual should be changed to exclude TUTOR file types from the translate-into-PC-DMIS process. It should now read: "Translating a Part Program into PC-DMIS: Introduction PC-DMIS will allow a user to take part programs that were created in DOS or Avail and translate them to run in PC-DMIS for Windows. The original part program must have been created using Avail or PC-DMIS (DOS) version 3.1 or higher in order for the translation process to be available. Note: Importing Tutor for Windows part programs will not be available in this release. The main topics in this chaptersection include: · Creating a Part Program File · Importing a Part Program File Creating a Part Program File To translate a file, the following procedure must be followed: DOS to Windows 1. Using DOS, start up PC-DMIS. The Active Parts list will be displayed. 2. Click the POST button from the menu list. 3. Select the part program to be translated. PC-DMIS will display the Post Options menu. 4. Select the DIMS CMDS button (DIMS commands) from the menu list. PC-DMIS will ask for the Output File name. 5. Type the appropriate file name, followed by the three-character extension. It is suggested (but not mandatory) to use the extension ".dim". 6. When PC-DMIS is post processing the part program, it will ask you to enter the name of a PC-DMIS for Windows Probe File. Type the appropriate name. 7. Make sure that it is a probe file being used for Windows. 8. Press the ENTER key. 9. When the post processing is complete, PC-DMIS will display a message asking you to press any key to continue. PC-DMIS will then return to the Active Parts list. 10. Exit out of PC-DMIS for DOS. Avail to Windows Avail files do not need to be translated in order to run in PC-DMIS for Windows. It is recommended (but not necessary) that the files are saved with a LLF*.* file name. Simply follow the instructions located in "Importing a Part Program File" on page B-2 below. Importing a Part Program File The following procedure should be followed when importing a part program file. The process is the same regardless of the file type. DOS and Avail Files 1. Start PC-DMIS for Windows by double clicking on the appropriate desktop icon (or by selecting the desktop's Start Button | Program Files | PC-DMIS For Windows). PC-DMIS will load and show the Open File dialog box. 2. Click the Cancel button to close the dialog box. 3. Select File | New to create a new part program. The New Part Program dialog box will appear. 4. Type a new part program file name and other information as needed. 5. Click the OK button. The dialog will close and PC-DMIS will open the Probe Utilities dialog box. 6. Click the Cancel button to close the Probe Utilities dialog box. 7. Select File | Import. PC-DMIS will ask you to save your file. 8. Click the SAVE button. PC-DMIS will display the Post In Data dialog box. 9. Select the appropriate input data type (DIMS or AVL) from the Data Type box. 10. Highlight the correct file. If it was saved with a .DIM / .LLF*.* extension, PC-DMIS will automatically display all available files with the appropriate extension. If necessary, change to the correct directory. 11. In the Post in Data dialog box select either the Merge option, or the Replace option to merge with or replace the current part program. 12. Click the OK button (or press the ENTER key). PC-DMIS will translate the DIMS/AVL data and return to the part program. Your part program is now ready to run in PC-DMIS for Windows."

Back to Top

Appendix C Using Master / Slave Mode

Back to Top

Appendix D PCDLRN.INI File

Back to Top

Appendix E Using a Wrist Device

Back to Top

Appendix F Operator Mode

Back to Top

Appendix G Hot Keys

Back to Top

Appendix H Automation

Back to Top