Return to Wilcox Associates, Inc. Home Page

Created on: September 24, 2002
Last modified: July 09, 2008

VERSION 3.25
Errata and Addendum

This page is dedicated to finding and correcting errors found in the PC-DMIS Version 3.25 Reference Manual as well as documenting portions of the application that were developed after the manual was completed . In the list below, chapters that have changes are indicated with a red bullet . Click on the links of the chapter headings below to find corrections to the manual:

Chapters Introduction User Interface File Options Utilities Construction Options Dimension Options Auto Utility Scanning Options System Options Graphic Options Editing a Part Program Executing a Part Program Guide to Measuring a Part Hyper-View Reporting Tutorial	Appendices Off-Line Part Programming Translating a Part Program into PC-DMIS Using Master / Slave Mode PCDLRN.INI File Using a Wrist Device Operator Mode Measuring Auto Features with the NC-100 Video Probe Shortcut Keys
	Glossary of Terms

Chapter 1 Introduction

Chapter 2 User Interface

The topic "Shortcut Keys" in this chapter contains an incomplete listing of the shortcut keys available. For a complete list, see the "Shortcut Keys" appendix. -----

Chapter 3 File Options

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."

Chapter 4 Utilities

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. - - - - - The "Active Arms Toolbar" topic's first line of text reads: "The 'Active Arms' toolbar contains two toggle buttons depicting probes will be available." It should be changed to read: "The 'Active Arms' toolbar contains two toggle buttons depicting the master and slave modes. " - - - - - The text for the "Active CMM Interface List" topic should be rewritten to read "The Active CMM Interface list simply displays the interface you initially selected for the current part program. You cannot use this list to switch between off-line and on-line modes." - - - - - For our foreign language documentation, the topics "Views list" and "PC-DMIS Modes Toolbar" contain the text "See Error! Reference source not found....". This is a cross reference whose link was broken. It should read "See 'View Setup'...." - - - - - For our foreign language documentation, the topic "Text Box Mode" contains a note with this text "See Error! Reference source not found....". This is a cross reference whose link was broken. It should read "See 'Translate Mode'...." - - - - - 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." - - - - - In the "PC-DMIS Modes Toolbar" topic a table describes each of the icons and what they're used for. For the Curve and Surface mode icon, the description should be changed from "Uses available the curve or surface data" to "Place's PC-DMIS into either Curve mode (for use with wire-frame data) or in Surface mode (for use with surface data)." - - - - - Text for the "External Command" topic should be rewritten as follows: "The 'Utilities | External Command' menu option allows you to insert a command into the Edit window that, when marked and executed, runs an external executable or batch file into the part program. * Normal DOS commands can be executed if they are put into a batch file. * The command must be marked in the Edit window for PC-DMIS to execute the external command. * A valid path and file name must be used. * PC-DMIS will halt the execution of the program and display a message when it encounters a EXTERNALCOMMAND/DISPLAY command during execution. Click 'OK' to continue part program execution. The Edit window command line for this option reads: EXTERNALCOMMAND/DISPLAYSTATE ; path name DISPLAYSTATE = This toggle field controls whether or not PC-DMIS pauses execution and displays a message notifying you of an external execution. This field switches between DISPLAY and NO DISPLAY. path name = This string represents the path and file name of the executable or batch file." - - - - - Under the "External Command" topic there is a "Display" and a "No Display" topic. These topics refer to the 'Display' and 'No Display' options on the 'External Command' dialog box. In the past these controlled whether or not the 'External Command' dialog box would be displayed. The 'Display' topic should be changed to read as follows: "Selecting the 'Display' option displays a message that lets you know that program execution is paused in order to run the external command. PC-DMIS pauses execution until you click 'OK' on the displayed message." The 'No Display' topic should be changed to read as follows: "Selecting the 'No Display' option runs the specified external command without displaying any sort of message. PC-DMIS will continue execution while the executable or batch file runs simultaneously." - - - - - A new topic has been added that describes how to calibrate a Faro probe. The topic title is "Faro--Probe Calibration Utilities". The text for this topic should be as follows: ==Faro-Probe Calibration Utilities== If you are using a Faro arm, the "Probe Calibration Utilities" dialog box appears in place of the standard "Measure" dialog box that appears when you click "Measure" from the "Probe Utilities" dialog box. ==Available Dialog Box Options== The following lists each option available in the "Probe Calibration Utilities" dialog box and what each does. The "Probe Calibration Utilities" dialog box allows for two methods of calibration * "Sphere Calibration Technique": Most Faro arms have a calibration sphere built into them which is usually a 1.000" ball so PC-DMIS defaults to this method of calibration. * "Hole Calibration Technique": If preferred, you can use a hole to calibrate the Faro probe instead of the sphere. * "Error Zone of Last Calibration": The Error Zone of last calibration box displays the volumetric number that Faro calculates after the calibration routine is complete. This number is for display purposes only. It is generated by the Faro controller; it isn't calculated by PC-DMIS and can't be edited. * "Number of Hits Taken": The "Number of Hits Taken" box displays the number of hits taken per calibration zone. * "Popup large window showing hits": Selecting the "Popup large window showing hits" check box shows the XYZ and number of hits in real-time as the calibration process takes place. * "Beep after completing a segment of calibration": Selecting the "Beep after completing a segment of calibration" check box causes the computer system to emit a beeping sound when a specific calculation zone or segment is complete. The status area on the dialog box (located just below the Number of Hits Taken box) then tells the user what calibration zone to measure next and how many hits to take. ==Faro Calibration Procedure== To correctly calibrate your probe using a Faro arm, follow this procedure: 1. Access the "Probe Calibration Utilities" dialog box (the "Road map" chapter provides instruction on accessing all dialog boxes and options). 2. Select the appropriate calibration method from the "Calibration Method" area. 3. Select any useful check boxes. 4. Click the "Measure" button. The calibration process will begin. 5. Follow any on-screen instructions (including instructions that may appear in the dialog box's status area). - - - - - The following procedure should be added under the "Subroutines" topic: "To delete arguments from a CALLSUB command: 1. Place the cursor on the CALLSUB command. 2. Press F9 to access the 'Call Subroutine' dialog box. 3. Select the desired argument(s) from the list. 4. Click the 'Delete Arg' button. 5. Click 'OK'. You can also delete an argument in the Edit window text directly. To do this, 1. Place PC-DMIS in Command mode. 2. Place the cursor on the CALLSUB command, and press TAB until you highlight the desired argument. 3. Type the letters "del". This will delete the argument. Pressing DELETE or BACKSPACE won't work. They merely change the argument to an empty argument." - - - - - 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 Curve and Surface Mode topic, the documentation states that CTRL + F5 is used as a shortcut to switches between CURVE and SURFACE modes. This is not the case. Pressing CTRL + F5 places PC-DMIS into Text Box mode. - - - - - - - - - - Under these topics dealing with statistics, the acronym DES does not stand for "Data Exchange Standard". Instead it stands for "Data Evaluation System": "Database Options", "DES Option". - - - - - After this manual was completed, the "Measure Probe" dialog box was modified with a new area called "Parameter Sets". A new subtopic of documentation was added to the "Measure" topic. It reads as follows: ==Parameter Sets== The “Parameter Sets” area allows you to create, save, and use saved sets of probe calibration parameters. To create your own named parameter sets: 1. Allow PC-DMIS to automatically update your probe file to at least the version 3.5 format. 2. Select Utilities | Probe. The “Probe Utilities” dialog box appears. 3. Click the “Measure” button. The “Measure Probe” dialog box appears. 4. Modify any parameters on the “Measure Probe” dialog box. 5. From the new “Parameter Sets” area, type a name for the new parameter set in the “Name” box and click “Save”. PC-DMIS displays a message telling you that your new parameter set has been created. You can easily delete a saved parameter set by selecting it and clicking “Delete”. 6. Click the "Measure" button if you want to calibrate your probe tips right away. If you want to calibrate them later, click "Cancel". 7. On the "Probe Utilities" dialog box, click "OK". Clicking "Cancel" on this dialog box will delete any changes made to the probe file, this includes the creation of any parameter sets. Once you create a new parameter set you can use it in the AUTOCALIBRATE/PROBE command (see the "AutoCalibrate Probe" topic in this chapter). Note: Parameter Sets are specific to the probe that was in use when they were created. - - - - - Functionality for the new AUTOCALIBRATE/PROBE command mentioned in the “Parameter Sets” topic (also included in this addendum) was added after this manual was completed. Documentation for it is included below; you should paste the following after the “Print List” topic of this chapter. ==AutoCalibrate Probe== PC-DMIS provides a command that automatically calibrates the current probe during part program execution. PC-DMIS will begin the calibration routine once it executes the command. To insert this command, select the “Insert AutoCalibrate Probe" from the “Utilities” menu, or in the Edit window while in Command mode, type AUTOCALIBRATE and press TAB. The Edit window code for this command reads: AUTOCALIBRATE/PROBE, PARAMETER_SET=, QUALTOOL_MOVED=Y/N, SHOW_SUMMARY=Y/N, OVERWRITE_RESULTSFILE=Y/N PARAMETER_SET= This field specifies the name of a named set of probe qualification parameters. A default set named ALL-TIPS-WITH-DEFAULTS is always available and will calibrate all tips defined in the current probe using the default set of qualification parameters, which are the last ones that were used interactively. To create your own parameter sets, see the "Parameter Sets" topic in this chapter. QUALTOOL_MOVED= This YES / NO field sets your response to the computer's query of whether or not the calibration tool has moved. SHOW_SUMMARY= This YES / NO field determines whether or not PC-DMIS displays a summary of the calibration. OVERWRITE_RESULTSFILE= This YES / NO field determines whether or not PC-DMIS overwrites or appends information sent to the results file. This is the same results file that's referenced when calibrating interactively. - - - - - Add the following documentation beneath the "Calling a Subroutine" topic somewhere: ==Using CALLSUB Statements in Master / Slave Mode== * If you mark a CALLSUB statement as Master Only; all of the commands in the subroutine will be marked as Master Only when the subroutine is called. * If you mark a CALLSUB statement as Slave Only; all of the commands in the subroutine will be marked as Slave Only when the subroutine is called. * If you mark a CALLSUB statement for both arms, PC-DMIS leaves the subroutine markings as they were originally setup. * If a subroutine contains a MOVE/SYNC command in it, and you mark the CALLSUB statement as Master Only or Slave only, at execution time PC-DMIS displays an error indicating that this is invalid and the subroutine is not called. For information on assigning a command to execute for a specific arm, see the "Enter Master / Slave Mode" topic in the "System Options" chapter. - - - - - The note in the "Erase Hit" topic mentions the PRINT_STORE_MOVE entry in the PCDLRN.INI file. This entry is obsolete. You should use the PRINTBUTTON entry in its stead. - - - - - [ADDED 22 MARCH, 2002] The "Measure Probe" dialog box has undergone these changes: * The ManDCC option was added. * The "Type of Operation" area was added. * The "Wrist Calibration Angle Setup" area was added, * The "Calibration Order" area was removed. - The "Tool Override IJK" boxes were renamed to "Search Override IJK" and were placed in the "Add Tool" and "Edit Tool" dialog boxes. - The "Default Mode" and "User Defined" options were combined to one check box named "User Defined Calibration Order" and placed on the "Probe Utilities" dialog box. Because of these changes, the following topics in this chapter have been added or modified: Under the "Measure" topic, under the "Probe" topic these topics are new: ====ManDCC Mode==== ManDCC mode is a hybrid between Manual and DCC modes. This mode helps with calibrating odd probe configurations that aren't easy to model. In most cases ManDCC behaves like DCC mode with the following differences: * You must always take the first hit manually for each tip, even if the qualification tool hasn't moved. All remaining hits for that tip will then be taken automatically in DCC mode. * None of the pre-measurement clearance moves for each tip are performed since all first hits are performed manually. * Once PC-DMIS completes the sphere measurement for a given tip, depending on the type of wrist you have, it may or may not perform the final retract moves. If you have a moveable wrist like a PH9, PH10, PHS, etc., PC-DMIS performs the final retract moves as it would in regular DCC mode. It proceeds without prompting you thereby ensuring that the probe has sufficient clearance to move to the next tip's AB angles, and to perform the next AB move. If you do not have a moveable wrist, PC-DMIS doesn't perform the final retract moves. Instead, PC-DMIS proceeds directly to the prompt for the manual hit for the next tip. ====Type of Operation==== The "Type of Operation" area allows you to select the operation that will be performed when you click the "Measure" button on the "Measure Probe" dialog box. The available operations include: Calibrate Tips: This option is used to do a standard calibration of all marked tips. Calibrate Unit: This option is used to error map an indexing probe head such as the PH9 & PH10. A special probe configuration, consisting of three identical tips connected to a 5 way center in the shape of a upside down "t", is placed in the probe head and as many tip orientations (all possible orientations is best) that the user desires are measured with the special configuration. Once this has been completed it is possible to change tip configurations without having to do a complete tip calibration. Each of the orientations measured in the original map will now automatically be calibrated in the new configuration. PC-DMIS provides complete support for calibrating and using a Renishaw PHS wrist as well as the DEA wrist. Note: This option, as discussed here, refers exclusively to probe heads that have repeatable indexed wrist positions such as the PH9. This calibration requires a 3 tip star probe. After this calibration is performed, only the indexed positions that were qualified during the wrist calibration can be used in future probe files without performing a full calibration. See also the "Using a Wrist Device" section for more information on calibrating wrists. The Process 1. Create the Unit probe configuration as shown in the graphic below: [See the five way center probe diagram in your documentation] The exact sizes of the components may vary but the shape must remain the same. It is also best to choose the lightest components as possible. Gravity can cause some error in the measurements. 2. From the Probe Utilities dialog box, click the Add Angles button and add as many different orientations as you desire. A complete mapping of the probe head would mean measuring each possible orientation. 3. Select the Measure button from the Probe Utilities dialog box. The Measure Probe dialog box appears. 4. Enter the default values to use. 5. From within the Measure Probe dialog box, click on the Measure button. A menu appears. 6. From the menu select Calibrate the Unit. PC-DMIS will then measure each of the three tips at each of the selected orientations. PC-DMIS will use this data to map the Offset, Pitch, and Yaw of each different orientation. 7. Next, place a probe configuration that you wish to use for measurement on the probe head. 8. Choose at least three of the mapped orientations. 9. Calibrate this tip in the chosen orientations, by clicking on the Measure button in the Measure Probe dialog box and selecting Calibrate Tips from the menu. This will allow PC-DMIS to calculate the actual length offset for this probe configuration. Then PC-DMIS will automatically create the position for each of the mapped orientation. Qualification Check: This re-measures the tip orientations specified by the user and does a comparison to the previously measured data for these tip orientation. The user can use this comparison to determine if a complete calibration is needed. Home the Unit: This will home the probe head to A=0 and B=0 for most probe heads. PC-DMIS includes Home the Unit for selection if the Pcdlrn.ini file contains the line: RenishawWrist = 1 Note: The port lock must have the wrist option turned on in order for PC-DMIS to enable the wrist support. Calibrate NC-100 Artifact: This option is used to calibrate an NC-100 qualification tool. To enable this option you must have previously purchased the NC-100 option. Having this option available on the portlock will enable the NC-100 tab in the Setup Options dialog. The NC-100 must then be correctly setup before the Calibrate NC-100 Artifact option will be available for selection. ====Wrist Calibration Angle Setup==== This area allows you to specify wrist positions in a pattern of up to nine sphere measurements for indexable wrist calibration. The "Wrist Calibration Angle" Setup area becomes available for selection when you meet the following conditions: * Setup an infinitely indexable wrist device such as the Renishaw PHS or Brown and Sharpe CW43L in the Probe Utilities dialog box. See the "Probe" topic. * Select the "Calibrate the Unit" option from the "Type of Operation" area in the "Measure Probe" dialog box. Selecting this option will result in a wrist calibration during which a new wrist error map file will be calculated. For in-depth information on using and calibrating wrist devices, see the "Using a Wrist Device" section. Defining AB Wrist Positions To Calibrate: In order to calibrate the wrist, you need to calibrate wrist positions in a pattern of at least three A angle positions by at least three B angle positions for a total of nine sphere measurements. The "Wrist Calibration Angle Setup" area gives you the ability to specify the angles for calibrating both the A and the B axes. The "Start", "End" and "Increment" boxes allows you to specify the starting and ending angles for mapping the wrist and the increment for mapping in both the A and B axes. For example, suppose you type in these values into the appropriate boxes: A Angle Start: -90 End: 90 Increment: 90 B Angle Start: -180 End: 180 Increment: 180 PC-DMIS would calibrate the positions of A-90B-180, A-90B0, A-90B180, A0B-180, A0B0, A0B180, A90B-180, A90B0, and A90B180. Note: You should choose the actual "Start" and "End" angles according to the type of wrist device you are using, the mechanical availability, and the manufacturer or vendor recommendations. In some cases PC-DMIS will automatically determine the "Start" and "End" angles based on controller specifications (although in these cases, PC-DMIS will only map 359.9 degrees of the B axis roll). While a minimum of nine positions is required to calibrate a wrist device, you may choose to use more than this minimum. PC-DMIS will give you a slightly more accurate calibration if you use more than the minimum number of positions. When you calibrate a wrist, you can also create a wrist error map to correct for angular errors in the wrist between calibrated positions. See "Calculate Error Map" in the "Using a Wrist Device" section for information. ====Parameter Sets==== Documentation for this area has already been provided earlier in this errrata. The "Add Tool" topic has the "Search Override I, J, K Vectors" subtopic added with this information: These boxes allow you to specify a vector used by PC-DMIS to determine the most efficient order to measure all the tips. The "Probe" topic has this sub topic added: ==User Defined Calibration Order check box== The "User Defined Calibration Order" check box allows you to determine the order PC-DMIS takes to measure selected tips. * If you select this check box, PC-DMIS will measure the tips in the order defined by the user when marking the tips for calibration in the Active Tip List. (See "Active Tip List".) If no tips are chosen, PC-DMIS will use the I, J, K vectors defined in the Search I, J, K boxes in the Edit Tool or Add Tool dialog boxes to determine the most efficient order to measure all the tips. * If you do not select this check box, PC-DMIS will measure the tips in an order that it determines to be the most efficient. When this happens, PC-DMIS ignores the order that was given to selected tips in the Active Tip List. (See "Active Tip List" .) PC-DMIS will also use the calibration tool vector to determine the most efficient order to measure. - - - - - ADDED MAY 30, 2003 This new topic was added to provide clarification when using looping with alignments: ==Looping Offsets and Alignments== If you have an alignment command inside a loop and the loop is using offsets, you must define all axes for that alignment. Additionally the alignment inside the loop must use features measured inside the loop. - - - - -

Chapter 5 Construction Options

The procedure to construct a High Point, described in the topic, "Constructing a High Point Plane", should be updated to include patch scans as inputs as well. It should now read: "A High Point plane can be constructed using features forming a set or a patch scan. To construct a High Point Plane: 1. Select 'Construct | Plane' from the menu bar. The 'Plane Construction' dialog box will appear. 2. Select the 'High Point' option. 3. Select one set of at least three features of any type or a patch scan. See 'Feature Set Construction' or 'Patch' in the 'Scanning Options' section. 4. Click the 'Create' button." - - - - - 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 topics "Constructing a Drop Point" and "Constructing a Pierce Point" there's this phrase: "Note: For his construction method you must select feature types in the correct order." The word "his" should be rewritten "this". - - - - - 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". - - - - - Under the "Constructing an Intersect Point" and "Constructing a Drop Point" topics, the following note should be added: "Note: If you select a slot as one of your input features, PC-DMIS will use the slot centerline vector when constructing this point instead of the slot normal vector (in versions 3.2 and earlier PC-DMIS used the slot normal vector). If you want to use the older slot normal vector, you will need to modify the value for the UseLegacySlotVector entry in the Pcdlrn.ini file. For information on how to do this, see 'Use Legacy Slot Vector' in the Pcdlrn.ini appendix". - - - - - 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,......" - - - - - Under the "Point Construction" topic, the table for the Pierce Point row should be modified as follows. The cell for Feat #1 should read: "Cone, Cylinder, Line, Slot, Circle, Ellipse". The cell for Feat #2 should read: "Cone, Cylinder, Plane, Sphere, Circle, Ellipse". The cell for Comments should read: "Constructs point where feat_1 pierces surface of feat_2. Order of selection is important. If first feature is line, direction is important." - - - - - Under "Constructing a Pierce Point" step three of the procedure only lists some of the types of features that can be used to pierce another feature. This step should be rewritten to include circle and ellipse features: "3. Select the first feature. It must be either a cone, cylinder, line, slot, circle, or ellipse." - - - - - Under the topic "Constructing a Circle from a Cone", the following sentence has been added for clarification: "A Cone Circle feature at a given diameter is also commonly known as a Gage Diameter." - - - - - Under the "Tolernace " topic under the "Constructing a Gaussian Filter Set" topic, the following text should be added for clarification: "The tolerance you type can be zero or any positive value. If you type a zero, the tolerance becomes the default of 3. - - - - - ADDED JANUARY 11, 2003 Step 3 in the "Constructing a High Point" feature should be modified to read as follows: "Select three or more features (any feature type may be used). A set using at least three features or a patch scan can also be used. "

Chapter 6 Dimension Options

The "Profile" dialog box has had the "Projection" area with the "Distance" box removed. Under the "Profile" topic the "Projected Distance" topic should be removed. - - - - - The following subtopic has been added under the "Printing Dimensions to Inspection Report" topic to describe differences in dimensions printed to a PDF file or an RTF file : ==Displaying Dimensions in RTF and PDF Files== You can send the inspection report with its dimensions to an external RTF (Rich Text Format) or PDF (Portable Document Format) file by selecting the output options in the Print Options dialog box for the Edit window. See "Printing from the Edit window" in the "Using Basic File Options" chapter. Be aware that because of formatting limitations between the RTF and PDF outputs, dimensions are displayed somewhat differently in the two files. * In RTF files, dimension are printed with a light border around the header, a blue background color, and the dimension symbol. * In PDF files, dimensions are printed without a border, there is no background color, and no dimension symbol. Dimensions are printed with a left margin. - - - - - [ADDED 22 MARCH 2002] Under the topic "Profile" there's a procedure called "To Dimension a Feature Using the PROFILE Option:" the numbered steps of this procedure have been updated with some extra information. It now should read as follows: 1. Create a Best-Fit alignment. Generally, creating a best-fit alignment improves the numbers of a profile dimension. Also, best-fit alignments are necessary if you select the Form Only option later. 2. Access the "Profile" dialog box. 3. Select the feature(s) to dimension from the "Feature List" box. If a datum feature is selected, it must be a plane. 4. Type the plus tolerance value in the "Plus" box. 5. Type the minus tolerance value in the "Minus" box. 6. Select either "Inch" or "MM" in the "Units" area. 7. Select where to output the dimension information. Select either the "Statistics", "Report", "Both", or "None" option. 8. Select the optional "Display" check box if you want to view dimension information in the Graphics Display window. 9. Select either "Form Only" or "Form and Location" in the "Control Options" area of the dialog box. 10. Select the desired analysis options by marking the "Textual" check box or the "Graphical" check box. If the "Graphical" check box was marked, type the multiplier value in the "Multiplier" box. 11. If desired, select the "Display" check box in the "Dimension Info" area and click "Edit" to select the "Dimension Info Format" you would like displayed in the Graphics Display window. · If you've selected the "Form and Location" option earlier, be sure to select the "MaxMin" check box from the "Dimension Info Format" area of the "Edit Dimension Info" dialog box. · If you've selected the "Form Only" option earlier, be sure to select the "Measured" check box from the "Dimension Info Format" area of the "Edit Dimension Info" dialog box. 12. Click the "Create" button. - - - - -

Chapter 7 Auto Utility

In the "Using Surface Data on the Screen for a Cylinder" topic, the text used to read that six points was needed to generate the cylinder. This procedure should be changed to read as follows: "To generate a cylinder using surface data: 1. Click on the 'Surface Mode' icon . 2. Position the cursor (outside or inside the desired cylinder). 3. Click on three locations around the cylinder. PC-DMIS will highlight the selected cylinder. The dialog box will display the center point and diameter from the CAD data of the selected sheet metal cylinder once the sixth point has been indicated. 4. Set the length of the cylinder by typing a value in the 'Height' box. 5. Click the 'Create' button." ----- The topic "Surface Point Field Definitions" has a typo: Under "Showallparams=" the text "$ INIT" should be simply "INIT". ----- In the topic "Box Select for Sheet Metal Features ID's" the possessive "PC-DMIS'S" should be rewritten as PC-DMIS's (lowercase 's). ----- Under "Circle", "Cylinder", "Sphere", and "Cone" there are Edit window code samples showing the make up of each of these commands. In these samples and in their respective "Field Definition" sections ("Circle Field Definitions", "Cylinder Field Definitions", "Sphere Field Definitions", "Cone Field Definitions"), the term "DNOM" should be re-written as "DIAM". ----- Under the topic "Spacer for a Surface Point" the caption to the sample graphic says "Graphical Representation of Spacer from the actual hit". It should be rewritten to read "Graphical Representation of Spacer from the nominal point location". ----- Under the topic "Vector Point Field Definitions" the text "THEO/ = This value represents the target hit" should be rewritten as "THEO/ = This value represents the nominal hit". ----- The topic "High Point Field Definitions" for the WIDTH / OUT RADIUS value contains a description with a typo. The phrase "it represents the valued...." should be rewritten as "it represents the value....". ----- The topics "Circle" and "Extended Circle Options" have a sample code snippet from the Edit window that shows "INIT = .n". References to "INIT = .n" should instead read "INIT = n" (no decimal point). ----- In the topics "Pitch for a Sheetmetal Circle" and "Pitch for a Sheetmetal Cylinder" the following clarification should be added: "In order to follow a standard (clockwise) thread pattern, you need to reverse the starting and ending angles (ie. 720 - 0) and in order to cause the measurement to reverse from a rising pitch to a falling pitch (up/down) you need to negate the value of the pitch." - - - - - The note in the "Insert Move Point" topic mentions the PRINT_STORE_MOVE entry in the PCDLRN.INI file. This entry is obsolete. You should use the PRINTBUTTON entry in its stead. - - - - - An introductory paragraph in the "IJK Surface Report for an Edge Point" topic reads: "The Dimension | Location option, ST check box displays the deviation calculated along this vector." This should be changed to read: "The Dimension | Location option, RS check box displays the deviation calculated along this vector." - - - - - ADDED DECEMBER 09, 2002 The following information should be added to the Inital and Perm topics for stud features: "Note: If a value is keyed in to the Height box and you have non-zero values for the Initial and Prem boxes, PC-DMIS assumes that a stud is being measured and will require that a hit be taken on top of the stud. However, if your Initial and Perm values are zero then the Height value changes meaning and works as described for TYPE = HOLE."

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 Tab" 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. - - - - - Under the "Cylinder" topic, the "Pitch:" topic has an example that contains some errors. It says: "Example: If the cylinder has a CutVec of 0,0,1, a Pitch value of 1.0 and a positive angle of 720 , the scan would execute two revolutions and would move up the axis of the cylinder one unit from the start point. If, for the same cylinder, a negative pitch is entered, the scan would execute down the axis of the cylinder one unit." It should be rewritten to read: "Example: If the cylinder has a CutVec of 0,0,1, a Pitch value of 1.0 and a positive angle of 720 , the scan would execute two revolutions and would move up the axis of the cylinder two units from the start point. If, for the same cylinder, a negative pitch is entered, the scan would execute down the axis of the cylinder two units." - - - - - In the "Scan" dialog box the "Perimeter " tab contains an "Inner Bound" check box that wasn't documented. This check box allows you to select whether the perimeter scan is an interior scan (selected) or an exterior scan (deselected). This will be added to the "Options" topic under the "Common Functions of Scan Dialog Boxes" topic. - - - - - [ADDED 22 MARCH 2002] The "Scan" dialog box for manual scanning has a new "3D" check box. Documentation is provided here: ==3D check box== This check box only becomes available if you are using a hard probe (liked a Faro arm). The 3D check box allows you to take hits in a three-dimensional manner, in any direction. Normally when scanning manually, PC-DMIS requires that you first take your manual hits in the direction of the InitVector in the Initial Vectors area. However if you select this check box, you can move the probe in any direction. This option is very useful when using a machine with axes that cannot be locked (such as the Faro or SMX machines). Probe Compensation Limitations: Once you select this check box, the probe compensation direction for all of the points becomes unknown. * If CAD surfaces do not exist, then probe compensation will not occur. All data will remain at Ball Center. * If CAD surfaces exist, then PC-DMIS will attempt to find the nominal values for each point (FINDNOMS is used). If the nominal data is found, then the point will be compensated along the found vector; otherwise, it will remain at Ball Center. - - - - -

Chapter 9 System Options

In the "Pierce CAD on 3D Rotate" topic, there's a spelling error in the second bullet in the bulleted list. The word "peirce" should be spelled "pierce". - - - - - In the "ID Setup" tab documentation for the "Show All ID" check box wasn't included. It's is included here as follows: "If the Show All ID check box is selected, PC-DMIS will display that feature's ID label in the Graphics Display window for all newly created features. If this is deselected, the feature still gets created in the Edit window, but the ID label doesn't show up in the Graphics Display window."- - - - - A new "Edge Point Only" checkbox was added to the "General" tab of the "Setup Options" v325 after documentation was written. Documentation for it is below: ==Edge Point Only Mode== The Edge Point Only Mode check box controls how PC-DMIS responds to each set of probe hits. In this case, a set is defined as two singular probe hits. The first hit should always be taken on the surface. The second hit should always be taken on the edge. When this check box is selected, PC-DMIS automatically considers each set of probe hits to be a single point measurement and automatically creates an Auto Edge Point. If the check box is not selected, PC-DMIS will accumulate probe hits until you press the END key. Only then will it determine the type of feature just measured. PD-DMIS will use the options as displayed in the "Feature Setup" section of the "Edge Point" dialog box when creating the Edge Point (See the "Edge Point" topic in the "Auto Utility" chapter). CAD nominals will be applied if the "Find Noms" option is checked. - - - - - The "Probe Trigger Options" topic should have the following note added to it: "Important: The AUTOTRIGGER command only works with Measured Points and Auto Vector Points." - - - - - The "CMM Interface" topic contains this added description on the dialog box that appears when you select the CMM Interface menu option: "The dialog box that appears contains three boxes and three lists. The lists represent the machine`s default X, Y, Z axes, and the boxes represent the intended X, Y, and Z orientations." - - - - - Under the "Ignore CAD to Part" topic, add this subtopic to clarify what happens to theoretical features copied and pasted into a new location with this check box selected or cleared: =Theoretical Values for Copied Features= * If you clear this check box and copy a feature to a new location in the Edit window, the theoretical values of the feature will be associated with the alignment at the feature's original location and will seem to change. * If you select this check box and copy a feature to a new location in the Edit window, the theoretical values of the feature will be associated with the alignment at the feature's new location and will seem to be unchanged. Additionally, add the following subtopic to identify how this affects "CAD Equals Part" =Effects on Cad Equals Part= If you want to execute an alignment from features measured without CAD data in DCC mode, and if you will be using the "CAD Equals Part" menu option, be sure to select the "Ignore CAD to Part" check box prior to selecting the "CAD Equals Part". menu option. For information on setting the CAD equal to the part, see the "CAD Equals Part" topic in the "Utilities" chapter. - - - - - Under the "Find Nominals Tolerance" topic, the following clarification has been added. "You must type in an amount greater than the radius of the probe or else the Find Nominals operation will fail." - - - - - A new "Use Automotive Deviation Letters" check box was added to the "General" tab of the "Setup Options" v325 after documentation was written. Documentation for this check box is included here: == Use Automotive Deviation Letters == The "Use Automotive Deviation Letters" check box causes PC-DMIS to add a letter after the deviation number in Location and True Position dimension reports. PC-DMIS inserts the letter · 'F' when the feature deviates in the direction of the front of the car. · 'B' when the feature deviates in the direction of the back of the car. · 'I' when the feature deviates towards the centerline of the car (meaning the car is too narrow). · 'O' when the feature deviates away from the centerline of the car (meaning the car is too wide). · 'H' when the feature deviates towards the top of the car. · 'L' when the feature deviates towards the bottom of the car. These letters are added to the Location and True Position dimensions just following the deviation numbers reported. - - - - - ADDED SEPTEMBER 02, 2002 The following sub-topics on .stp files were added to the "Compensating for Temperature" ==Using STP Files== Each CMM uses machine-specific parameters for temperature compensation for each axis, such as thermal coefficients and sensor assignments. these parameters, along with embedded code that tells PC-DMIS if the file is a structural or linear compensation file, are stored inside special STP files (named for the .stp extension) created by Brown and Sharpe and DEA. PC-DMIS requires these STP files to compensate for temperature. Prior to compensating for temperature, ensure that these STP files reside in the appropriate locations on your harddrive: * The DEA Linear Thermal Compensation method expects to find the Serv1.stp file in the C:\Program Files\Thermal_OCX directory. * The DEA Structural Thermal Compensation method expects to find the Serv1.stp file in the C:\Thermal_OCX directory. Important Note for Dual Arm Systems: In addition to having the STP file (Serv1.stp) in the appropriate directory on the slave arm's computer, you must also ensure that another STP file for the slave arm (named Serv1s.stp) resides in the corresponding directory on the master arm's computer. To do this, copy Serv1.stp from the slave arm's computer, rename it to Serv1s.stp and place it on the master arm's computer. ==Linear and Structural Temperature Compensation== Linear compensation = (Thermal Coefficient of Expansion) X (Displacement Change in Temperature of Each Axis and the Part). If multiple temperature sensors exist on an axis, PC-DMIS averages the readouts to find the temperature change. Structural compensation recognizes that a CMM's various material components may have different temperatures (a single axis of the machine, for example, may have several different temperatures, which cause bending, bowing or skewing of the machine in some way). Structural compensation, then, applies the temperature corrections for specific areas of the CMM. When you select the "Temperature Compensation" menu item, the Structural Thermal_OCX gets called and PC-DMIS calculates a new temporary volumetric compensation map. - - - -

Chapter 10 Graphic Options

Chapter 11 Editing a Part Program

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 "Print Options" topic for the Edit window, has a typo under "Using the Auto Option". The term "incrementthe" should have a space and be rewritten as "increment the". - - - - - The topic "Colors (Shift F6)" contains a grammatical error. The description for "Dimension Background Color" currently reads "sets the background color for a dimensions reporting boxes displayed in report mode." This should be rewritten to "sets the background color for a dimension's reporting boxes displayed in report mode." - - - - - 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 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 "Toggle master/slave arm" the bulleted list contains some errors. * In the first bullet, the text "Features assignd to the the slave arm are indicated using the green line." should be rewritten as "Features assigned to the slave arm are indicated using the green line." * In the third bullet, the text "Features assigned to both the master arm and the slave arm are indicuated using both red and green lines." should be rewritten as "Features assigned to both the master arm and the slave arm are indicated using both red and green lines." - - - - - 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." - - - - - In the topic "Layout", the text "PC-DMIS's summary mode layout is in the form of an expandable and collapsible pieces of data." should be rewritten as "PC-DMIS's summary mode layout is in the form of expandable and collapsible pieces of data." - - - - - In the topic "Expression Components" the word "discusssed" should be spelled "discussed". - - - - - The description for the "Bottom" value in the "Pointer Functions" topic contains a misspelling. The text "This value signigies . . ." should be changed from "signigies" as "signifies". - - - - - The example in the "Pointer Functions" topic contains a misspelling. A line of text in the example says "...'TOP' would be passed in as the second paramater as shown here." The word "paramater" should be spelled "parameter". - - - - - 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". - - - - - The first bullet in the topic "DMIS Mode" makes reference to a support document for DMIS. The text "...see the document titled, 'PC-DMIS 3.0 Support Documentation for DMIS 3.0'...." should be changed to "...see the document titled, 'PC-DMIS Support Documentation for DMIS'....". - - - - - The topic "Mathematical Functions" needs some clarification on what trigonometric functions return. Additionally, documentation for the tangent function (TAN) was missing. This topic should be rewritten as follows: ==Mathematical Functions== Each of the trigonometry functions takes and returns radians. ABS Absolute Value: ABS(<Double>) Returns absolute value of input. ACOS ArcCosine: ACOS(<Double>) Returns the arc cosine of the expression. For example, ACOS(5.0) returns 0. In general, ACOS(<expression>) returns the arc cosine of the value of the expression. ASIN ArcSine: ASIN(<Double>) Returns the arc sine of the input. ATAN ArcTangent: ATAN(<Double>) Returns the arc tangent of the input. COS Cosine: COS(<Double>) Returns the cosine of the input. DEG2RAD Degrees to Radians: DEG2RAD(<Double>) Returns the input divided by 360 and multiplied by 2p. Converts from degrees to radians. EXP Exponential: EXP(<Double>) Returns the exponential of the expression. LN Natural Log: LN(<Double>) Returns the natural logarithm of the expression. LOG Log Base 10: LOG(<Double>) Returns the log base 10 of the expression. RAD2DEG Radians to Degrees: RAD2DEG(<Double>) Returns the input multiplied by 360 and divided by 2p. Converts from radians to degrees. ROUND Rounding: ROUND(<Double>) Returns the input rounded to the nearest integer. SIN Sine: SIN(<Double> ) Returns the sine of the input. SQRT Square Root: SQRT(<Double>) Returns the square root of the input. TAN Tangent: TAN(<Double>) Returns the tangent of the input. Note: Functions where the input is out of range (i.e., for ACOS, ASIN, LOG, LN, SQRT etc. that would cause the computer to crash) return 0. - - - - - The "Keywords" topic contains a list of formatting keywords. In the table, the description for the keyword #ELAPSTIM should be re-written to read "Inserts the time elapsed between start and end of execution. This is ideal for use in the ELOGO.DAT file." - - - - - 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>) " - - - - - In the "Measured Features Dialog Box" topic documentation for these check boxes have been added: =Regenerate Hits= The 'Regenerate Hits' check box regenerates this feature's HIT/BASIC commands so that they are updated with changed data from the 'Feature Theorticals' area. =Copy to Actuals= The 'Copy to Actuals' check box copies any changes made to the 'Feature Theoreticals' area of the dialog box and applies the same changes to the actual measured data. - - - - - - [ADDED 22 MARCH 2002] Under the "Expressions" topic, under the "References of Type Double" topic, the following dimension extension has been added: "Valid Extensions for Dimension Reference of Type Double by Example" DIM5.BTOL is the Bonus Tolerance Value where DIM5 is a True Position. - - - - - [ADDED 26 APRIL 2002] Version 3.25 now contains some icon changes to the Edit window toolbar. The "Report Mode" icon was changed to "Full Report Mode" icon and an additional icon was added named "Last Execution Mode" icon. The following documentation should be added under your "Edit Window Toolbar" topic: ==Full Report Mode== The "Full Report Mode" toolbar icon places the Edit window into report mode. It allows you to view all the items in your part program-marked and unmarked-and part program items from all your executions. ==Last Execution Report Mode== The "Last Execution Report Mode" toolbar icon places the Edit window into report mode. It displays your report, but it only shows marked items from your last program execution. - - - - - [ADDED JULY 15, 2002] Under the "Find" and "Replace" topics, functionality to search and/or replace text using regular expressions has been added. A new check box called "Pattern matching" has been added to the "Find" dialog box and the "Replace" dialog box. To perfrom regular expression pattern matching, you must first select this check box. - - - - - - [ADDED JANUARY 02, 2003] The "Utilities | Override FindNoms" menu option was added into version 3.25 after its initial release. The documentation for the menu option and the "FindNoms Override" dialog box that appears is given here. ===Overriding Found Nominals=== The "FindNoms Override" dialog box allows you to choose the appropriate nominal point from CAD surfaces for Auto Vector Points, Auto Surface Points, and individual hits inside other features (such as scans). It overrides the default FindNoms behavior of PC-DMIS during Learn mode and Execute mode. When attempting to find a valid nominal point (within the FindNoms tolerance) by taking a manual hit, PC-DMIS will, most of the time, choose the correct point. However, there are exceptional circumstances when PC-DMIS cannot find an appropriate point and instead chooses an inaccurate point on the CAD model. In these situations, you can use the FindNoms Override dialog box to help PC-DMIS find the appropriate nominal point from the CAD surfaces. The following topics describe the dialog box itself and how to use the dialog box in the different modes: ==Understanding the FindNoms Override Dialog Box== The Priority Surface, Pierce Point, and Drop Point Columns This area of the dialog box contains these three columns: 1.) Priority Surface 2.) Pierce Point 3.) Drop Point A "T-value" is the distance of the measured hit from the nominal point along the nominal CAD surface vector. They display the relevant nominal point values and their T-values (the value displayed to the left of the X, Y, and Z values in parentheses). Priority Surface column - This column lists the surfaces that you have stored as priority surfaces in the Edit CAD Elements dialog box. It displays the type of surface and a check box. The check box allows you to add or remove the surface from the list of priority surfaces maintained by PC-DMIS. If you select the check box, PC-DMIS adds the surface to the priority list. Deselecting the check box removes the surface from the list. Pierce Point column - This column lists the nominal point values found using PC-DMIS's Pierce Point operation. If you see the text "Failed OP" in this column it means that the pierce point operation failed to find the nominal point on that surface. If PC-DMIS highlights a point in green, then that point is the best nominal point found by the selection algorithm. You can of course course override this selected point. Drop Point column - This column lists the nominal point values found using PC-DMIS's Drop Point operation. =The Tolerance box= The "Tolerance" box allows you to specify a new tolerance value to use when finding the nominal points using this dialog box. =The Use Previous Surface check box= The "Use Previous Surface" check box tells PC-DMIS to use the most recent surface to look for the nominal points. This check box becomes available for selection only after you take the a hit on a surface with the dialog box open. After you take a hit, PC-DMIS then has a surface to work with for future hits. =The Override button= The "Override" button overrides an incorrect nominal point found by PC-DMIS with the nominal point data selected from the list containing the "Priority Surface", "Pierce Point", and "Drop Point" columns. ==Using the FindNoms Override Dialog Box in Learn mode:== To access this dialog box in Learn mode: 1. Select the "Point Only Mode" and "Find Nominals" check boxes from the "General" tab of the "SetUp Options" dialog box. 2. Ensure that you have imported a CAD's solid model. 3. Select the "Surface mode" icon from the "Graphics Modes" toolbar. 4. Select the "Override FindNoms" menu option. The "FindNoms Override" dialog box appears. With the "FindNoms Override" dialog box open, when you take a manual hit, PC-DMIS follows its normal logic to choose as accurate a nominal point as possible by using the most recently measured hit coordinates and approach vector. You can then use the "FindNoms Override" dialog box to perform additional procedures allowing you to override the found nominal point. =Procedure 1: Finding Nominal Points on the Previous Surface= If you select the "Use Previous Surface" check box, the "FindNoms Override" dialog box attempts to find a nominal point from the most recent surface used. If the dialog box can find a point within FindNoms tolerance on the most recent surface it will select that nominal point and create an Auto Vector Point based on the nominal values. =Procedure 2: Finding Nominal Points on Priority Surfaces= If the "FindNoms Override" dialog box cannot find a nominal point on the recent surface, it tries to find a nominal point from the priority surfaces. Priority surfaces are surfaces that the user has selected as a subset of CAD surfaces to find nominal points. Priority surfaces can be selected or deselected using the Set as Priority check box in the "Edit CAD Elements" dialog box. If PC-DMIS finds an appropriate point among the priority surfaces, it selects the point and creates an Auto Vector Point based on the nominal values. It also displays the valid nominal points within the FindNoms tolerance of all the priority surfaces in the FindNoms Override dialog box. =Procedure 3: Finding Nominal Points on All CAD Surfaces= If PC-DMIS still cannot find a valid nominal point by using the procedures discussed in procedures 1 and 2, (see the "Procedure 1: Finding Nominal Points on the Previous Surface" and "Procedure 2: Finding Nominal Points on Priority Surfaces" topics), it does the following: · Looks for the best nominal point on all the CAD surfaces within the FindNoms tolerance · Creates an Auto Vector Point based on the best available nominal point. · Displays all the CAD surfaces that had nominal points in the "FindNoms Override" dialog box. =Procedure 4: Choosing a Nominal Point Later= If PC-DMIS still cannot find an appropriate point on all the CAD surfaces, it asks if it can create the Auto Vector Point and you can choose a nominal point later. If you accept, then PC-DMIS creates an Auto Vector Point in the Edit window and you can select from these options: Option 1. You can take a new hit and PC-DMIS will try to find a new nominal point. Essentially you're starting over if you do this. Option 2. You can choose a different nominal point from the dialog box and click the "Override" button. PC-DMIS will then override its earlier chosen nominal point with the new selected point for the recently created Auto Vector Point. You will usually want to do this if you don't like the nominal point that PC-DMIS attempted to find in the procedures discussed in these topics: · "Procedure 1: Finding Nominal Points on the Previous Surface" · "Procedure 2: Finding Nominal Points on Priority Surfaces" · "Procedure 3: Finding Nominal Points on All CAD Surfaces" Options 3. You can select a CAD surface on the screen. PC-DMIS would then attempt to find nominal points on the selected surface and display those points in the "FindNoms Override" dialog box. You can then override the previous found nominal, by selecting a point from this new surface and clicking "Override". Note: PC-DMIS ignores the FindNoms tolerance with this option. So, even if the selected CAD surface is out of FindNoms tolerance the dialog box still displays the points. Option 4. You can increase the FindNoms tolerance by changing the value in the "Tolerance" box and clicking the "Apply" button. PC-DMIS will then apply these procedures again, using the higher tolerance value and display any appropriate points: · "Procedure 1: Finding Nominal Points on the Previous Surface" · "Procedure 2: Finding Nominal Points on Priority Surfaces" · "Procedure 3: Finding Nominal Points on All CAD Surfaces" You can then choose a valid point and click "Override" to accept a nominal point for the recently created Auto Vector Point. Increasing the FindNoms tolerance in the "Tolerance" box has the same effect as changing the FindNoms tolerance from the "General" tab of the "SetUp Options" dialog box. =After Choosing the Best Nominal Point= After choosing the best nominal point, PC-DMIS will remember the chosen surface for that feature. During execution in manual mode, PC-DMIS will: 1. Use the tolerance value held in the "FindNoms During Execution" box, available on the "General" tab of the "SetUp Options" dialog box. You must select the "Find Nominals During Execution" check box (also available on the "General" tab) for this to work. 2. Attempt to use the same surface and CAD operation (Pierce Point or Drop Point operation) to find the new nominals for the recently executed point. If it cannot find a nominal point on that CAD surface, it will again access the "FindNoms Override" dialog box. See the "Using FindNoms Override in Execute Mode:" topic below for execution time behavior. ==Using FindNoms Override in Execute Mode:== As mentioned in the "After Choosing the Best Nominal Point" topic, the "FindNoms Override" dialog box, PC-DMIS displays this dialog box in execute mode upon meeting the following conditions: · You must import a solid model with surfaces and select the "Surface Mode" icon from the "Graphic Modes" toolbar. · You must select the "Find Nominals During Execution" check box from the "General" tab of the "SetUp Options" dialog box. · The Auto Vector Point or Auto Surface Point must have a valid nominal point found in Learn mode (see "Using the FindNoms Override Dialog Box in Learn mode:"). · Execution must take place in Manual mode. · PC-DMIS must execute the Auto Vector Point or Auto Surface Point feature. · PC-DMIS must fail to find a nominal point for executed Auto Vector Point or Auto Surface Point. Once the dialog box appears, execution stops and you can interact with the dialog box in ways already discussed in the "Using the FindNoms Override Dialog Box in Learn mode:" topic. You can also choose to re-execute the recently measured point feature. In that case, PC-DMIS re-executes and attempts to find nominal values again. If it still can't find any nominal values for the point, PC-DMIS again displays the "FindNoms Override" dialog box. You can then do one of the following: · Re-execute again. · Use the "Override" button as discussed in the "Procedure 4: Choosing a Nominal Point Later" topic · Close the dialog box by clicking the "Cancel" button. If you close without choosing an appropriate nominal, PC-DMIS replaces the measured data with the previous nominal values. ==Using the FindNoms Override Dialog Box from the Edit window:== You can also access the "FindNoms Override" dialog box by right-clicking the mouse on one of these features and selecting Override FindNoms from the short-cut menu: · Vector point · Surface point · Individual Hit The dialog box will then use the feature's measured data (point and vector) to find an appropriate nominal point as discussed in the "Using the FindNoms Override Dialog Box in Learn mode:" topic. - - - - -

Chapter 12 Executing a Part Program

Chapter 13 Guide to Measuring a Part

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 ----

Appendix A Off-Line Part Programming

Appendix B Translating a Part Program into PC-DMIS

The topic "Avail to Windows" should be updated to read as follows: "Avail files 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. To import Avail files, follow the instructions located in 'Importing a Part Program File'." -----

Appendix C Using Master / Slave Mode

ADDED JANUARY 11, 2003 In the "Causing an Arm to Wait to Prevent Collision" topic, add the following example: "For example if you want each arm to check a common sphere using automatic sphere commands, you should set up the part program like this: MOVE/EXCLUSIVE_ZONE=ON (for Arm 1) AUTO/SPHERE(for Arm 1) MOVE/EXCLUSIVE_ZONE=OFF (for Arm 1) MOVE/EXCLUSIVE_ZONE=ON (for Arm 2) AUTO/SPHERE (for Arm 2) MOVE/EXCLUSIVE_ZONE=OFF (for Arm 2)" - - - - -

Appendix D PCDLRN.INI File

The following topic and text should be added to this chapter underneath the "Option" topic: ==Use Legacy Slot Vector== "This entry lets you specify the vector PC-DMIS will use when constructing an Intersect Point or Drop Point if one of the inputs is a slot. The entry line in the PCDLRN.INI file reads: UseLegacySlotVector=0/1 If you set this entry to 1 (one), then PC-DMIS will use the slot normal vector. If you set this entry to 0 (zero), then PC-DMIS will use the slot centerline vector. Zero is the default value for versions 3.25 and higher." - - - - - The following topics and text should be added to this chapter after the "DMIS" topic: === Edit Window === The [Edit Window] section of the Pcldrn.ini file allows you to store values used to modify aspects of the Edit window. == Edit Window Use Markset Names When Printing == This entry specifies whether or not PC-DMIS uses the name of the marked set when printing contents of the Edit window to a file. By default PC-DMIS uses the name of the marked set as the file name. Entry line in the PCDLRN.INI file: EWUseMarksetNamesWhenPrinting=n n = 0 or 1. If this entry is set to 1, PC-DMIS uses the marked set file name. If it's set to 0, then PC-DMIS uses the file name specified in the Print Options dialog box. - - - - These two entries were been added to the [OPTION] section of the PCDLRN.INI: ==Disable Load Time Expression Checking== This entry allows you to disable expression validation checking when loading a part program. This speeds up PC-DMIS when using very large part programs. Entry Name: DisableLoadTimeExpressionChecking Entry Type: Boolean value. If set to 0, the expression validation checking is enabled. If set to 1, expression validation checking is disabled, yet PC-DMIS speeds up. ==Disable Summary Mode And Undo== This entry allows you to disable working in Summary Mode and the ability to perform Undo and Redo operations in the Edit window. This speeds up PC-DMIS when used with very large part programs. Entry Name: DisableSummaryModeAndUndo Entry Type: Boolean value. If set to 0, working in Summary Mode and performing Undo operations are enabled. If set to 1, Summary mode and performing Undo operations are disabled, yet PC-DMIS speeds up. - - - - - The "Print Store Move" topic has been changed since the PRINT_STORE_MOVE ini entry is obsolete. The topic should be rewritten as follows: ==Print Button== The Print Button entry determines the function of the print key on the jog box. Entry line in the PCDLRN.INI file: PrintButton=1/0 1= a move will be inserted if the Print key is pressed. 0= the last probe touch will be removed from the hit buffer if the Print key is pressed. - - - - -

Appendix E Using a Wrist Device

ADDED 26 SEPTEMBER 2002 The following information should be added to ensure accuracy when using an SP600 probe. ==Caution When Using SP600 Probes == For most probe types on an infinite wrist, the wrist device calibrates a zone of angles and approximates the rest. However, if you have an SP600 probe on an infinite wrist, the SP600 probe needs its own defelection matrix. You must, therefore, calibrate each AB tip angle that wasn't part of the original mapping process or suffer innacurate results in your measurements.

Appendix F Operator Mode

Appendix G Measuring Auto Features with the NC-100 Video Probe

Appendix H Shortcut Keys

This should be added to the table of shortcut keys: "CTRL + F5 This shortcut key combination places PC-DMIS into Text Box mode." -----

Glossary of Terms

Due to confusion between two separate meanings for the DES acronym, the definition for the "DES" topic should be changed to read: "If importing a DES file type, this stands for 'Data Exchange Standard'. If working with statistical databases, DES stands for 'Data Evaluation System'. - - - - -

VERSION 3.25 Errata and Addendum