System Requirements

To Install and use PC-DMIS you will need:

• Windows Operating System (Win95, Win98, Me, or Win2k supported). (Recommended Windows NT).
• Pentium II Processer, 400 MHz or Higher IBM-compatible computer (Recommended Pentium III with 800 MHz or equivalent).
• Minimum 64 MB of RAM (Recommended 256 MB of RAM).
• A hard disk drive with 100 MB of free disk space (Recommended 200 MB).
• 9.0 GB Hard Drive (Recommended)
• A VGA or higher resolution monitor (Recommended 16M-color.
• Graphics card with OpenGL support (driver that supports OpenGL) with a minimum 8MB ram (Recommended 32 MB RAM, hardware accelerated Transform and Lightning)
  
• CD-ROM (Required).

Product Summary

PC-DMIS for Windows is a full-featured, geometric measurement package. It translates the high-level commands required to measure parts into the detailed steps necessary to drive a Coordinate Measuring Machine (CMM). PC-DMIS for Windows incorporates Microsoft's Windows interface to create, as well as execute part programs. The user can easily begin the measurement process by taking advantage of the drop-down menus, dialog boxes, and icons. The versatility of PC-DMIS' interface also provides an easy way to customize the software to meet the individual specifications.

The Primary goals driving the design of PC-DMIS for Windows were flexibility and user friendliness. To meet these goals, PC-DMIS provides a flexible environment allowing for real-time error correction of part programs, as opposed to the long, tedious debugging process of other geometric software packages. It is dimension oriented to reduce the need to analyze and interpret the results of the CMM measurements. The techniques used for the part programming on a CMM are straightforward and, with practice, systematic.

PTB Certified

PC-DMIS for Windows version 3.25 has been PTB certified. This certification ensures that the math algorithms used in this version of PC-DMIS adhere to known standards.

See these scanned images for more information:

• Certificate (German/English)
• PTB Info 1 (German)
• PTB Info 2 (German/English)
• PTB Info 3 (German/English)

For more information on PTB certification, visit this site: http://www.ptb.de/en/index_en.html

New Features & Enhancements

Version 3.25's major features and enhancements include:

• Translated DMIS syntax is now viewable in the Edit Window. - A new button in the Edit Window toolbar allows switching between Summary Mode, Command Mode, DMIS Mode, and the Report Mode.
• An ability to save part programs in the format of previous versions was implemented. - The save format can only be done with version 3.2 and forward.
• A Reverse Axis mode was added to reverse the coordinate system of the Arm2 of a dual-arm system when used in single arm mode which enables Arm1 programs to run without changes. - This method is implemented via a "-r" command line argument on the Arm2 machine.
• UNDO and REDO commands were added for Edit Window operations.
• The ability to print a listing of calibrated tip data.
• AutoCones can now be programmed.
• Column passing was added for machines with System 5 fixturing.
• A radial Autotrigger tolerance zone for creating manual points.
• Mark Child Mode and Mark Parents Mode which allow for marking only highlighted sections.
• A positive deviation reporting option when the X,Y,or Z axes may be negative.
• Better support of DMIS dual-arm programs which make use of the CRMODE and CRSLCT.
• Iterative alignments now include starting and error lables as well as convergence values for more than 3-2-1 alignments.
• Message prompting was improved for calibration of dual-arm machines.
• Improved import of DMIS lines and planes to make the direction vector the closest possible to the nominal.
• The DMIS COMMAND/PSTHRU option was added for setup options which can affect the part program.
• Password protection is now available to the setup options.
• The ability to obtain individual hit data from Auto Features and post it to DMIS programs.
• Control commands within jumped program sections are no longer executed.
• Reporting form deviation within the dimensions for standard geometric elements. Debug file reset is now available at the start of each new execution.
• Enhanced ON-ERROR functionality for Auto Features.
• DES output files can now be created from nominal feature values.
• A new marking method was implemented for Dual-Arm part programs to allow changable fonts in the Edit Window, clearer defined step-mode execution, and dual-arm commands (both arms execute).
• Fly mode radius is adjustable in the Edit Window.
• DMIS Support upgraded from DMIS 3.0 to DMIS 4.0.

Updates and Fixes for MR1

Download the fixes listed below in .doc format:

Version 3.25's Maintenance Release 1 contains these fixes and updates:

Enahancements:
No major enhancements since the initial release.

Fixes:

• The interface objects were assuming too high a priority and occupying too many computer resources.
• Importing AVAIL programs was failing when there were Measure statements in the AUTO/DONE block.
• 2D Vector fit alignments were causing application errors when the active plane set to YPLUS.
• Clearance planes were not always working correctly if scans were not relative to the Z plane.
• The latest version of the wcompens32_2.dll was not being installed with PC-DMIS.
• Dimensions reporting in Degrees,Minutes,Seconds format were not displaying negative values.
• Executing an external object was not working if the path name contained spaces.
• Variables used as control points in scans were being replaced with real values.
• Cylinder construction from 3 measured circles was not working.
• The settings toolbar was being truncated to the right.
• The slave arm was not always recognizing slave only alignments.
• Circles constructed from Vector Points were not being created at the correct Z coordinates.
• The notch feature was prompting for manual execution during a DCC execution.
• The LK interface was not properly recording probing points during calibration.
• Probe file errors were generated after looping many times with LOADPROBE commands of probe files that used more than one DRAW component inside loops.
• Execute Mode was incorrectly prompting the operator to overwrite existing files during file write.
• The DEVANG option in the FORMAT command wasn't being set.
• Creating a constructed point and then canceling was leaving the point in the graphics window.
• Using the Show Path option was causing application errors in dual-arm part programs.
• The ISIOChannelSet command was not working correctly for setting Slave Arm bits from Master Arm commands.
• The IGES export engine only supported export of 262,144 objects.  16,777,216 are now supported.
• Probe changers could not be used in Reverse Axis Mode if calibrated while not in Reverse Axis Mode.
• Statistics sent to Datapage by Feature type were being converted to Dimension type.
• Manually adding a SAVE/ or EQUATE/ALIGNMENT command in the Edit Window was not working if a SAVE or EQUATE command already existed.
• DMIS export was not properly formatting "T" dimensions.
• Operator mode was not generating correct PDF report files.
• Using a time delay of zero seconds was generating unnecessary error messages when using ACTIV temperature compensation.
• An emergency generated during System-5 column unload would necessitate recovering all columns in a rack.
• Slave module offsets were not being loaded correctly for use in dual-arm System-5.
• Selecting Wcompens32.dll compensation on a Leitz interface machine that was previously set to DEA Standard was causing application errors.
• An incorrect error message was being displayed during import of an IDEAS DCI CAD model.
• The fixture_slv.dat file was not passing through the armarm.dat matrix when entering and leaving master/slave mode.
• ISIOCHANNEL bits were not being set correctly for slave arm System-5 columns during full calibration.
• If Column 1 was not loaded in the System-5 rack at the beginning of Full Calibration, the machine would attempt to retrieve the column anyway.
• The manual hand switch point trigger button was not functioning with the Tech80 interface.
• Execution was hanging when branch commands were being used in the part of the alignment that is re-executed automatically by the MEASALL=ALWAYS option.
• Expressions created in v3.2 programs were sometimes being corrupted on import into v3.25.
• GOTO commands for marked for slave arm only would cause PC-DMIS execution to hang.
• Application errors could be generated when executing Linear Closed scans with Relearn mode.
• Hits were not displaying in the Readout Window when using the Faro interface.
• The debug file was being created when using the Sharpe interface regardless of the options setting to create the file.
• The Report Mode window was not drawing the dimension tables used in loops correctly.
• Executing some Dual-Arm part programs that included subroutines could cause application errors.
• Temperature compensation could cause execution to hang on some Leitz interface machines.
• Angle Between dimensions were not showing the correct Out of Tolerance condition.
• The Fixture.dat and Fixture_slv.dat files were being saved in the program directory instead of the PC-DMIS root directory.
• Columns passed with modules attached to them were not being placed correctly in System-5.
• Part Coordinates were not properly displaying on the Leitz PMM jogbox.
• Constructing a point from any feature was creating the point at the origin rather than the feature's coordinates.
• Using the jogbox Done button in response to Read New Probe Position was causing application errors.
• Saying No to Read New Probe Position prompts was causing the CMM to move to the previous targe location.
• IO bits were not being set correctly for slave arm System-5 columns in the rack.
• Cutting from the Edit Window and then Undoing the cut was not recognizing valid TIP commands.
• Temporary installation files were not being deleted following installation.
• Analysis views were not opening in the correct workplane.
• Feature Cursor Highlight was not working in Text Box mode with wireframe views.
• The ISOCHANNELSET function was not working correctly according to program marking.
• Some programs utilizing While loops and array indexing were difficult to edit due to time delayed responses.
• The realative feature ID wasn't showing in the dimension list for Analysis Views in the Hyper-report window.
• Some problems with selecting surfaces for creating points were corrected.
• The SLCTMP and WKPPAR temperatures were not updating properly on Leitz interface machines.
• Dimensions created using variables for looped features were not outputting to statistics.
• PDF files were not created when executing from marked sets.
• Constructed feature ID's were not being updated in the Graphics Window simultaneously with the Graphics Window.
• Application errors were sometimes encountered when using File | Exit.
• Edge Point nominals were not being correctly found for the CAD surfaces.
• Toggling a newly created offset plane (without any inputs defined) to a point caused an unhandled exception.
• Indexed loop ID's were not displaying in real time in the Inspection Report Window during execution of dimensions.
• Hits taken while not executing an Operator Mode program were being appended to the part program on exit.
• Typing in a leapfrog command in the Edit Window followed by an F9 edit and then Close was causing application errors.
• Manually updating statistics was not functioning following abnormal exit of part program execution.
• A false probe trigger during calibration with the Tech80 interface was causing application errors.
• The Center Scan option was available with the Leitz interface even though it was not implemented in the controller.
• Surface point scans were not being properly compensated.
• Using the Axis option for the Center scan was not working.
• Editing the hit locations for sheetmetal features was not correctly recalculating the hit vectors.
• When using Find Nominals and Point Only Mode, messages indicating that a surface could not be found were not always displaying in the status bar.
• Comments remarks could not be inserted from the clipboard on new lines.
• Executing a program with an iterative alignment inside a loop was causing an application error on the second instance of the loop.
• Canceling execution of a part program using the Metrocom interface could cause application errors.
• Using a retract distance of 1mm with the Metrocom interface was not working correctly.
• Using Absolute Speeds and a default value of greater than 100 was always inserting 100 for new part programs.
• Dimensions reported from nested loops that included alignments were not calculating correctly.
• Printing to PDF with Hyper-Reports in-line was generating 2 copies of the PDF file and also the hyper-report.
• The Delete and Backspace keys were functional in Operator Mode.
• Workplanes were not being correctly defined during Best Fit alignments causing previous alignments to be modified.
• Problems with circular moves during qualification were resolved with the DEA interface.
• Visual Basic Post functions were not working correctly.
• First selecting a Scriber tool was not latest allowing proper selection of SP600 probes.
• Incorrect vectors were found for curves that were close to straight.
• Manual probe changes were not being correctly prompted.
• Communications problems with the Metrocom controller were resolved.
• Using a VB script to construct a circle from basic scan points was not working correctly.
• Blank pages were being inserted into results output to an rtf file.
• DCC Move Points were enabled in the SMX interface to allow fixturing device placement.
• Temperature compensation was implemented for the SMX interface.
• Dual-Arm part programs were not correctly attaching the associated arm to respective commands in included subroutines.
• Error messages relating to DCC machines were being generated on Manual DEA interface machines.
• The correct dialog window was not opening when a Catia DCI model could not be found.
• Exiting part programs utilizing the Metrolog interface could cause application errors.
• During learning of a part program, feature labels used as variables could occasionally be replaced by other feature labels.

Updates and Fixes for MR2

Download the fixes listed below in .doc format:

Version 3.25's Maintenance Release 2 contains these fixes and updates:

Enahancements:
No major enhancements since the initial release.

Fixes:

• Some changes to SP600 probe qualification routines to enhance accuracy.
• PC-DMIS was not always maximized on opening.
• The SP600MSTAR probe model was not utilizing all 9 connection points.
• The Axila machine interface was added and installation problems resolved for this interface.
• Reloading the active part program was causing application errors on exit.
• The Sharpe interface Done button was not working.
• "Alt -" was not working for deleting hits on Auto Cones.
• Spacing in the Probe Readout Window was not well organized.
• The Find coordinate function was not work in with Auto Point type features.
• Offset value signs were being inverted when constructing offset lines in loops.
• Curve construction was being limited to 530 points.
• The dialog boxes in the German language were incorrectly sized.
• The title bar in opened part programs was displaying old version information.
• Piercing a B spline curve with a ray does not always work.If this fails, the operator will need to set the PCDLRN.INI option AlternateCadMath=1.
• The measured hit points were not being calculated correctly for Auto Cones.
• Comment commands were not always recognizing variable inputs.
• The CAD Info dialog was not showing the correct import path for Pro-E files.
• It wasn't possible to select more than 119 features in a Construction dialog.
• The best-fit math was not solving for Auto Cones.
• Box selecting of Auto Circles was not working.
• Axis scans were not always working with laser probes.
• The Automation GETCOMMAND and GETTEXT functions were failing.
• Imported DMIS constructed lines did not always have the correct vector.
• Autocalibration did not support wrist mapping on a dual-arm machine with infinite wrists.
• Clicking on the Active Tip List followed by a Ctrl+Home keystroke produced application errors.
• Best Fit alignment weights were utilizing only default tolerances.
• Extra spaces were being added after the $ symbol during DMIS import.
• Auto Circles created from AVAIL imports had Auto Move set to YES with Distance equal to 0.
• Manually edited tip IJK vectors were not being saved.
• It was possible only in Summary Mode to change the fit type of a 2D Best Fit alignment.
• Changes in probe orientation were not always updating graphically for the Faro interface.
• Using alignments inside loops could cause extra movement of the CMM.
• Internal errors were causing some outside Auto Circles to be measured twice.
• The PH1 rotation increments we incorrectly defined.
• True Position dimensions were not being correctly exported to Visual Basic scripts.
• CAD files generated from the Pro-E DCI were attempting to connect to the Pro-E workstation.
• 2D Best Fit rotate only was not working.
• Setting Show Inputs for Best Fit alignments to OFF was having no effect during execution.
• Point selection on curves was not properly working.
• The NC-100 sensor was not capable of being used on the slave arm of a dual-arm machine.
• Using the Tolerances button in the Probe Utilities dialog was causing an application error.
• The Sheffield controller Error 50 was not being properly processed by PC-DMIS.
• Translating the CAD origin via Make CAD 3D was destroying the CAD graphics.
• The Calculations function of DPUPDATE was working correctly.
• After starting a new part program, clicking the Print button in the Results window of Probe Utilities was causing various problems.
• Axis reassignment was not allowing the Leitz interface to correctly calculate the SP600 matrix.
• Pierce point construction was generating errors even though the point was being created.
• Electing to show Extended Sheet Metal Options was causing probe crashes during scanning.
• Inserting an Autocalibrate Tip command was not correctly adjusting for tip diameter when using the Leitz protocol Trax calibration on common firmware controllers.
• With auto hyper-report turned on and auto print on load set, the report printed without dimensions.
• Calculation of the increments used for wrist calibration was improved.
• Continuously holding the Enable button with Leitz firmware was only collecting the first probing point.
• Slave Arm Autocalibrate Probe commands were not executing the correct positioning moves.
• Construction of some surfaces was producing application errors due to memory problems.
• Creating a BF constructed cone in the Edit Window and then changing the feature type was producing application errors.
• Collision detection was not working correctly.
• The DMIS output file name was changed to be the same as FILNAM/ statement.
• Generic feature ID's now will have the default labels starting with "F" instead of "SLT".
• True Position dimensions of cylinders using the option Deviations to Centerline were not displaying correct graphical analysis.
• Calibration data for multiple probe files in a qualification part program using qualification checks was not being saved.
• It was possible to delete all tips in a probe file and lose the reference to any calibration data.
• The LK interface was responding slowly to manual hits during execution.
• Opening the SMX Tracker Pad 2 times was causing run-time errors.
• The German resources had problems with changing tabs for CMM Interface Options.
• The label format for scans in loops was being distorted after several executions.
• RMEAS functionality was causing probe crashes for imported DMIS programs.
• Constructing a cylinder from 2 Auto Circles was not functioning correctly.
• Unigraphics fixed a problem where UG was not releasing applications utilizing a UG file.
• The Unigraphics DCI was updating too frequently.
• Hyper-reports that combined text and graphics were not capable of also displaying dimensions.
• Using the PROBEDATA() variable with no arguments was not returning the correct value.
• The Format command was not always correctly setting the header information for True Position dimensions.
• Base b-spline surface info was not being calculated for some trimmed surfaces causing import of these surfaces to fail.
• Deleting a feature from a Best Fid 2D alignment was causing application errors.
• Best Fit alignments could not be constructed from Feature Sets.
• Exclusion zones during System-5 column positioning were not being calculated correctly.
• Surface types that were not trimmed or bounded were not returning the correct surface vectors.
• Hyper-reports and the inspection report might not have had the same dimensions output.
• Arm2 could unexpectedly stop execution during a dual-arm part program.
• The version creation data was not being saved individually for probe files.
• The initial construction of a generic point was not being created in the CAD window.
• Probe triggers received after execution of a part program finished on a Tech80 interface were causing occasional application errors.
• Basic scripts in nested loops were sometimes hanging execution.
• A pcdlrn.ini variable clearance distance was added for ACR1 toolchangers.
• Y axis offsets were not correctly calculating collision errors with Fixturing.
• Scan point compensation was causing application errors in large scans.
• Editing the weights of a Best Fit alignment was setting the Show All Parameters flag to NO.
• Iterative Alignments made from 3 spheres were not correctly calculating level and rotation vectors.
• Calibration of Faro arms was not returning the correct calibration error.
• The Autotrigger function was not working correctly with the trigger plane.
• Executing a marked but uncalled subroutine was hanging the report object when executing a branch command.
• The start points of constructed Mid Lines were not being calculated correctly.
• Dependent curves constructed from feature sets were not updating during execution.
• The Unigraphics DCI was not completely importing complete files of assembly drawings.
• The Best Fit alignment dialog was not showing all of the hit points in a scan.
• Sheffield machines were not always homing to the same position.
• The last line of inspection reports was not always printing.
• Nested IF statements were not executing correctly.
• The RAMOPTIC probe was incorrectly defined as a trigger device.
• Outside Diameter circles in AVAIL programs were being imported as Inside Diameter.
• Form and Location Profile dimensions that were out of tolerance were being displayed in the report mode as in tolerance.
• Importing a DMIS file with illegal syntax was causing application errors.
• Repositioned dimension labels were not having their positions saved for printing of Hyper-Reports.
• Alignments marked for slave arm only were not being properly updated by measurements of master arm features.
• Sheffield machines were not always homing to the same position.
• The values recorded in the OPTIONPROBE command were not always being used for probe calibration.
• Deleting Features from the Graphics menu were causing memory violations.
• Starting execution of a part program using a toolchanger was not always prompting correctly based on the first load probe command.
• The PCD_DMIS_DEFINES.DMI file was not being properly named when programs were exported in DMIS format.
• Full System-5 Calibration encountered alignment errors between the 2 arms during column calibration.
• Pattern pasting Best Fit alignments was not correctly creating the new alignments.
• External Command path names were not allowed to use spaces.
• Disengage Drives Mode on Leitz interface machines was generating unnecessary error messages.
• Performing low level matrix calibrations on SP600/Common controllers could corrupt the matrix if a previous matrix already existed.
• Probe components were not properly connecting to generic machine models.
• Leitz interface machines were not always executing every step in a part program due new ESTATUS error responses not being registered correctly.
• Saying No to take manual points after a scan interruption following an emergency was generating an application error.
• Having the PRBATT firmware parameter set very close to the machine limits was not always allowing a Leitz PMM to record points.
• Circles constructed from cones were not giving the correct result.
• The available alignment list was not updating after saving alignments.
• The initial vector of offset planes was not considering the vectors of the input features.
• The *.STEP extension is now available for STEP file import in addition to the *.STP extension.
• Invalid VolComp messages were being incorrectly generated on Numerex machines.
• Editing the THEO values of a feature and then copying the feature was retaining the original values.
• Changing a cast cylinder with no inputs to a BF cylinder caused application errors.
• Saving a program to an older version schema was corrupting the probe file when trying to re-use in the v3.25 schema.
• Qualifying in Fastprobe mode was not calculating the correct probe matrices or probe diameters.
• Selecting a subroutine that did not have the same serialization data as a part program prevented saving of the part program.
• Probe compensation was not always working correctly with the Faro interface.
• Point Only Mode with Find Nominals and CAD was sometimes producing application errors.
• It was not possible to change the workplane while a dimension dialog was open.
• Entering a negative tolerance in some dimension dialogs was not carrying the negative symbol to the edit window.
• The locations of Dimension Info boxes were not being saved in Hyper-Reports when they were edited.
• Incorrect prompts were being displayed for homing PMM machines.
• Slave arms were not executing subroutines with GOTO commands correctly.
• The Re-Measure option was displaying as Relative Measure in Summary Mode.
• The Edit Dimensions Info buttons were not correctly associated with the proper action in the German resources.
• Line feeds were not added after location dimensions when using the print command.
• Application errors were generated when converting an Offset Point to a Cast Point via the edit dialog.
• The PROBEDATA variable was not passing the correct information when no arguments were assigned.
• The LK v5.3 interface was not correctly processing movespeed commands.
• IDOffsets were not saving correctly preventing leader lines for Auto Points to not draw correctly.
• Best fit constructed cylinders can now be created with more then 2 circles.
• The Automation PutText command was not supporting all possible values for PC-DMIS.
• Correct scale resolution was not always being set with Mitutoyo Bright interface ISA cards.
• Some VDA files were causing application errors on import.
• Dual-arm DEA interface machines were performing point-to-point scanning at different speeds.
• Probe graphics were being distorted by utilizing the fixturing dialog.
• Some VDA-FS files would cause application errors on import.
• Not all of the correct features were appearing in Autozoom Hyper-Reports.
• Find Hole ability was added for some Mitutoyo interface machines.
• Breaking the SMX tracker beam was causing problems with the ADM function.
• The Finish button was being made available in the Iterative Alignment dialog even if the feature selection was not finished.
• Modifying the scan increment in the edit window was not affecting the actual scan increment.
• The iterative alignment wizard was not allowing correct "drag and drop" or Next functionality.

Updates and Fixes for MR3

Download the fixes listed below in .doc format:

Version 3.25's Maintenance Release 3 contains these fixes and updates:

Enahancements:
No major enhancements since the initial release.

Fixes:

• When a PH9 crash occurred, the CMM didn't stop to move or measure with a DEA-rs232 interface.
• The default color for AS3 file displayed as blue in DataView instead of black.
• Machine movement was not smooth around a sphere during probe qualification on LK machines.
• The SMX Laser was slow to record measurement points using the Ctrl+H option.
• The Qualification Check option in the Probe Measure dialog was not active if a non-motorized probe head was not present.
• Stop button on Zeiss-GPIB machine did not interrupt program execution.
• Switching a second toolchanger type after calibrating a first toolchanger caused application errors.
• The automation call for feat.GetInputID(index) failed for scan type features.
• Axis scans were not working on the common controller.
• An optional delay after rotary table movement was added to improve measurement accuracy.
• Executing a manual sphere offline jumped through the hits without waiting for acknowledgement.
• Programs imported from earlier versions would have the nominal values for angle between dimensions changed.
• FeatCommand.NumHits returned incorrect values for constructed features.
• The Angle2 Start and End angles for Auto Spheres were being changed during a Y axis mirror.
• The CAD select dialog was remaining open after closing the Auto Features dialog.
• Some surfaces in a UniGraphics DCI assembly drawing were difficult to select.
• Random errors were generated when using a rotary table with the Sharpe interface.
• Meausuring an outside Auto Cylinder using Height was creating an inaccurate location.
• Orbix error messages for the I-DEAS DCI were not being searched for in the proper direcotry.
• ID's couldn't be changed by the ASSIGN statment.
• The Keystone tracker was not functioning.
• Parallel plane contstruction was not working properly.
• Surface Points were causing error messages requiring an integer to be generated.
• The manual retract distance was not being properly reset after and illegal touch error on LK controllers.
• The target vector was updating incorrectly for Round Slots that were measured manually.
• The menu item for "Send Current Stats to File" did not function after Execute Feature was used.
• Check distance on find hole centering measurments was increased to 115%.
• The probe radius was added to the calculation for the check distance value.
• Autofeatures derived from a basic hit did not support the RMEAS/ABSOLUTE function.
• The INIT text was disappearing when switching to FINDNOMS for Auto Circles.
• Indications were added to the program printout to indicate Arm1 or Arm2 commands.
• End of page indicators were not being properly written to RTF files.
• True position deviation was not being calculated correctly for perpendicular to a centerline.
• The path to the statistics database now allows 255 characters.
• Find Nominals did not work properly for Auto Circle when selecting from a Unigraphics DCI files.
• A partial execution on a Zeiss GPIB would cause the probe readout counters to freeze.
• A change was made to the faceting tolerance to improve the rotation of Unigraphics DCI models.
• Copying programs with hyper-reports could cause the hyper-reports to be destroyed on execution.
• Manual DEA machines were not initializing properly.
• Vector Point find vector failed if the feature had metal thickness.
• Application errors ocurred after editing weights of best fit alignment features.
• Buttons in the Auto Features dialogs were remaining in a depressed condition.
• Importing DMIS programs with very many points was taking excessively long.
• An EnableEstatus argument was added to the pcdlrn.ini file to allow real-time updating of the XYZ readouts on Sharpe32 controllers.
• In F9 edit mode, the captioning for the AutoCone button was incorrect.
• Roundness (Conicity) for Auto Cones was not being calculated correclty.
• Some part programs with Auto cones and Hyper-reports were generating application errors if executed more than once.
• Auto Cone was not calculating correct nominal angle values.
• A pop-up menu is now available for hiding DES labels.
• Individual levels of a PC-DMIS generated AS3 files could not be viewed in DataView.
• Defining a probe with the LK interface could have caused the computer to hang.
• Taking a hit with Find Nominals in Curve Mode and the LK interface could haved caused the computer to hang.
• Emergencies on the DEA controller could not be reset after cancelling execution of a program with breakpoints.
• The CAD window in Hyper Reports was showing all elements after a second execution.
• Find Nominals in Point Only mode took to long to process with the Unigraphics, ACIS, and I-DEAS DCI's. DCI.
• Constructed perpendicular planes were not calculating correctly.
• User defined calibration order did not work with non-indexable star probes.
• Multiple probe changer operations were not function on Arm 2 of dual arm machines.
• Pierce CAD while in 3D Rotate mode did not work with the Unigraphics DCI.
• The cursor was repositioning in the part program after deleting features from the Edit Window.
• The CAD vector was not being used as the default vector for Ellipses.
• The graphical vector arrow for a new feature was drawing at the part origin after a vector edit.
• Startup with the SMX Laser was not always completing.
• Auto-Trigger, Auto-Trigger Plane, and Distance to Target with Auto Zoom between Feature types was not working correctly with the Faro interface.
• The XYZ scales froze after resetting the SMX tracker machine.
• Resetting the SMX tracker could lose XYZ indication if the Home procedure was not performed.
• Homing was not working after breaking the beam on an SMX tracker.
• Dimensions were not updated properly when using Positive Reporting.
• The TP20 sometimes generated errors when being changed with an ACR1.
• Auto Points could not be created from a DES set.
• The PDF print drivers were updated to resolve various file generation problems.
• The Polar / Cartesian toggle for generic features was operating in reverse in the German language.
• onstructed from scans were not always working due to bad initial scan points.
• The LK jogbox was ignored after an illegal touch during execution measurement of Auto Features.
• Constructed perpendicular and parallel planes were not caclulating correctly.
• Metal thickness could not be calculated correctly when using the Unigraphics DCI.
• An External Alignment didn't have an effect in the executing part program.
• The EditDimensionsInfo dialog had no proper selection of the checkboxes with German language settings.
• It was not possible to open the percentage listbox in the Edit Dimension Color dialog in the German version.
• The Metrolog interface was attempting to measure circles as cylinders.
• Measuring Auto Circle Studs with Read Position was causing probe crashes.
• Uninstall was not cleaning up all files.
• Duplicate copies of debug files were being created for the LK interface.
• Optimizations for CAD files were causing computer crashes with some graphics cards.
• The Undo function was causing switching from the Report window to the Edit mode to take too long.
• Changing the nominal in a dimension prompted excessively to update a features nominals.
• Zeiss probe changers were not working on Arm 2 of a dual arm machine.
• The tempdata.dat file now generates warnings when the file size is more than 250K.
• Measured points were not snapping to an alignment axis when using fixed probes.
• Auto Feature Find was not working with a Thickness and an inverted CAD vector.
• PC-DMIS created the wrong start and end angles for partial arc measurment with Auto Circle.
• Iterative alignment did not work on manual Sheffield machines.
• The minus sign could not be used as part of a variable.
• Multi-level toolchanger support was added for the TRAX toolchanger.
• AS3 export was processing all CAD entities instead of currently viewed entities.
• The T deviation was not displaying well in the Probe Readout Window.
• RTF files were always being saved as 8-1/2 by 11 paper size.
• Hyper-report leader lines were repositioning after several executions.
• Searching for probe files in sub-directories with the Global Used button in Probe Utilities for tip angles in now possible.
• Passing a tall System-5 column from one arm to another while passing a short column from the other arm to the first arm did not work.
• It was not possible to break program execution when in an endless loop.
• Circular moves have been implemented for the Mitutoyo interface.
• Wireframe selection order was not consistent with measurement order for square slots.