2019 r2 sp1

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 2019 r2 sp1

    https://www.wilcoxassoc.com/public/P...19_R2/SP1/x64/



    Release Notes - 2019 R2 SP1
    • PCD-36046 - Fixed an issue where the find hole option would not work with
    the Wenzel interface.
    • PCD-109698 - Fixed an issue where performance was decreased during the
    execution of a laser scan and COP commands in a loop.
    • PCD-132016 - Fixed an issue where PC-DMIS stopped responding when you
    ran the Zeiss interface on new computers. This fix also enhanced the
    performance of the execution of many independent features.
    • PCD-156784 - Fixed a crash that occurred when you used a 4 bit-per-pixel
    bitmap for the CAD texture.
    • PCD-158609 - Added support for DEVA 037 Manual Counter Card. To use this
    interface, you must rename MANUALCMM.DLL to INTERFAC.DLL, and
    GMS_for_Deva_EncLib.XML to GMS.XML. All files related to the DEVA card are
    installed with the DEVA driver.
    • PCD-158646 - Fixed an issue where the pointcloud cross-section Show/Hide
    distance gages button was disabled in the Slideshow view.
    • PCD-167625 - Improved compatibility with some USB serial cables used to
    connect the HP-C-VE controller to the PC via USB.
    • PCD-169328 - Fixed an issue where PC-DMIS did not pass the surface ID to
    the command when you created a 3D Laser QuickFeature and had to re-pick
    the CAD surface from the Laser Auto Feature dialog box.
    • PCD-169386 - Fixed an issue where the points went to the wrong surface
    when you picked point pairs in a pointcloud to CAD alignment. This issue
    depended on the view orientation.
    • PCD-169906 - Fixed an issue where pointcloud stripe IJK information was not
    included in the Pointcloud | Export XYZ file format.
    • PCD-170207 - Added a change for the PointcloudOperator |
    ExportXYZSeparator registry entry to define one or more separator
    characters used for the Pointcloud XYZ export.
    • PCD-171304 - Fixed an issue where PC-DMIS reported the worst point instead
    of the measured centroid for non-plane features.
    • PCD-171381 - Fixed an issue with a Chinese operating system where settings
    to execute the collision avoidance during calibration were not read correctly
    from the registry on machines.
    • PCD-171396 - Fixed an issue where the Mesh colormap annotation points
    were not created unless the measurement routine was closed and then reopened.
    • PCD-172057 - Fixed an issue where the news feed on the Home page was
    empty for Chinese (Simplified). It now uses Chinese (Traditional).
    • PCD-172202 - Fixed an issue where PC-DMIS did not obey the marked set's
    output settings when PC-DMIS executed a marked set.
    • PCD-172853 - Fixed an issue where the execution of laser probe calibrations
    from the auto-calibrate command didn’t finish. The Execution dialog box
    had to be closed through the Stop button.
    • PCD-173186 - Fixed an issue where the Home page was switched off when
    the Part/Machine Setup tab was the active tab in the Setup Options dialog
    box.
    • PCD-173227 - Fixed an issue for laser auto cylinders and spheres where the
    CAD offset value was incorrectly applied for inch units.
    • PCD-173264 - Fixed a timer functionality for the CMM-OS interface.
    • PCD-173687 - Fixed an issue that occurred when you executed toolkit
    module features.
    • PCD-173721 - Fixed an application error that occurred when you created a
    linear open scan with a CWS probe, and the Measure option was selected in
    the Linear Open Scan dialog box.
    • PCD-173743 - Fixed an issue where the measurement routine stopped
    responding if you opened the Tilt Readouts window (Tracker | Nivel | Start
    Tilt Readout) for the Leica ATS600 Tracker.
    • PCD-174456 - Fixed an issue where the Home page overrode PC-DMIS locale
    enforcement for decimal numbers, which caused issues with entering
    numbers of specific locales.
    • PCD-174671 - Fixed a Vision probe-focus calibration error that occurred
    when the Find Surface (Focus) parameter was incorrectly enabled.
    • PCD-174797 - Fixed an issue where the Tracker Operation toolbar was
    missing the measurement profile buttons for the AT40x Leica Tracker
    interface.
    • PCD-175045 - Fixed an application error that occurred when you edited or
    executed a Vision feature with multiple hit targets.
    • PCD-175460 - Fixed an issue where, after the machine left a probe change
    rack, PC-DMIS computed an incorrect mount-point move. This issue caused
    either an incorrect movement or an "out of machine limits" error

  • #2
    so looks like another sp for mostly laser fixes?
    sigpic

    Comment


    • #3
      They fixed the probe changer mount point. I did not use 2019R2 from start because of PCD-175460, but now (first hour) I notice that 2019R2 is much much slower than 2019R1. Anybody else noticed this?

      Back to 2019R1 for me.

      Comment


      • #4
        Can you try this for me please? We have heard a few rare instances of slow performance, and in those cases, doing a Reset User seems to resolve that. This clears the customizations you may have made, so beware of that. You can also back up these files before you reset them. If this helps, I'd like a copy of those files please?

        Comment


        • mitkos
          mitkos commented
          Editing a comment
          A couple of computer restarts fix it. I did not use user reset option.

      • #5
        I am getting some funky force closes on simple tasks like copying or modifying code. And it's on random programs too. I have a standard template that I have. I am making a small tweak and every time I type in IGN and tab for IGNOREMOTIONERRORS it force closes.

        I am trying to shell a program, but when I select the code and select copy, it force closes. This was for Online and Offline vision program.

        Just random weird stuff that seems odd to me. Usually I am more vocal in the tech preview, but I have taken on some more roles and I have not been able to do the testing like I used to.

        --------------------------

        Edit: Of course, shelling the template works. I find it odd when adding in IGNOREMOTIONERRORS in my previous template, the software force closes. The reason I do this is because I have a TP20 NI.

        Edit #2: Still having issues with copying in code (Forms, File I/O, Comments, etc), then changing/ adding in probe changes, comments, etc. It's buggy as h-e-l-l.

        Edit #3: My initial run of my Vision-tactile auto calibration program no longer works with my defined parameter sets. I had to calibrate everything manually, probe by probe. The first few times, the vision probe would not turn on the back light for measuring the ring.

        Don Ruggieri NeilRyan
        Last edited by bfire85; 09-27-2019, 05:53 PM. Reason: Various edits

        Comment


        • #6
          OK. I got the IGNOREMOTIONERRORS and some of the copying issues to go away with an uninstall and reset user. One program is still corrupt after I perform the light migration.

          I have not re-tested the auto cal program yet.


          Does anyone have issues with the CAD model disappearing?

          Comment


          • bfire85
            bfire85 commented
            Editing a comment
            A-machine-insp I have a ticket into Hexagon, along with all my CPU specs. We'll see. All this junk seems to be happening on my offline seat, especially on the vision side of it. I am not sure if it has to do with the new vision migration thing.

          • A-machine-insp
            A-machine-insp commented
            Editing a comment
            The only issue I've had is with the NIST test. There are some things I need to try but I haven't had the time. I swear, when I die, they are going to cover my coffin with parts to check.

          • gibsonridge
            gibsonridge commented
            Editing a comment
            many times

        • #7
          Hello all,

          I noticed the correction below recently.

          PCD-171304 - Fixed an issue where PC-DMIS reported the worst point instead
          of the measured centroid for non-plane features

          Could someone please clarify which exactly features this concerns?
          Should we update immediately or go back to version 2019 R1?

          Thanks !

          Comment


          • #8
            I have noticed that user preferences that run fine on previous versions do horrible things on 2019 R2 SP2 and above. I performed a complete factory reset and re-install, but have only restored partial functionality. I have seen the buffer become completely disconnected from the reporting element and as my current case I have been reduced to remedial scans. Hexagon has suggested that i employ a new set of parameters. I feel, that with the parameters suggested almost any value could be obtained, and these may not be used in good conscience for part validation.
            This machine in its current state 2019 R2 SP3, is not functioning to the envelope in place at the time of purchase a short three years ago.
            sigpic

            Comment


            • #9
              Originally posted by Don Ruggieri View Post
              Can you try this for me please? We have heard a few rare instances of slow performance, and in those cases, doing a Reset User seems to resolve that. This clears the customizations you may have made, so beware of that. You can also back up these files before you reset them. If this helps, I'd like a copy of those files please?
              I had to double my paging file over what was needed for 2017 to stop PC-Dmis whiting out or crashing to desktop.
              sigpic

              Comment


              • #10
                Originally posted by Cumofo View Post

                I had to double my paging file over what was needed for 2017 to stop PC-Dmis whiting out or crashing to desktop.
                If this is Windows 10 then blame Microsoft. Paging files are best left to auto in Windows 10 and are impossible to turn off now regardless of how much ram you have.
                Systems Integrator
                Hexagon Manufacturing Intelligence

                Comment


                • Peter Fuller
                  Peter Fuller commented
                  Editing a comment
                  As a side note, anything other than an automatically managed page file in Windows 10 is bound to cause issues with all kinds of software. Running 64 gigs of ram on my gaming PC about half my games crash with a page fault if I play for more than an hour.

              Related Topics

              Collapse

              Working...
              X