2017_r2 sp10

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

  • 2017_r2 sp10

    Can't find any post about it, , but this SP is on ...

    http://software.hexagonmi.com/public.../2017_R2/SP10/

    Release Notes - 2017 R2 SP10
    • PCD-50401 - Fixed an issue where the Jump Hole functionality failed or caused scans to fail.
    • PCD-120462 - Fixed a German translation error for Location dimension of slots and edge points, L = L (slot length) and S = S (edge point-surface).
    • PCD-121392 - Self-centering support for Technology Server 1.5 client.
    • PCD-125813 - When the pointcloud is not well aligned to the CAD model, the resulting measured cross section (yellow polyline) may not be computed as expected and may produce the incorrect shape.
    By default, the PointcloudOperator CrossSectionCopCadCrossSectionDrivenByCad registry entry is set to 1.
    It is possible to obtain better results by changing the registry entry's value to 0 and recreating the cross section so that it uses this new setting.
    This alternative way to calculate COP/CAD cross sections could give better results when the medium distance between the cloud and the CAD model is relevant in the section zone, and the nominal section is strongly curved in this zone (distance is greater than 2 or 3 mm).
    • PCD-126533 - Fixed the issue of not able to skip holes for linear, path, section, rotary, and perimeter scans.
    • PCD-126732 - Corrected an issue where a continuous scanning made with an X1 probe was used to create a pointcloud surface colormap but the colors were not displayed.
    • PCD-135742 - Fixed an issue where path lines for probe head rotations were not drawn for probe heads with a C-joint (heads with 6 axis)
    • PCD-135786 - Added support for IDS uEye digital camera version 4.90 software to resolve issues seen installing earlier versions of the IDS software on Windows 10.
    • PCD-137806 - Eliminated a null pointer related to a commonly reported 2018 R1 issue where PC-DMIS stopped working.
    • PCD-140115 - When a new patch scan is created, all points taken for previous patch scan are deleted so as to create patch scan at new location.
    • PCD-144031 - Fixed a licensing issue that caused VisionBox to not work properly.
    • PCD-144198 - Restored functionality that existed prior to PC-DMIS 2017 R1 to display the probe at the correct location in the Graphic Display window when a MOVE command was edited.
    • PCD-144358 - Thickness now works for Auto Cylinder and Auto Cone.
    • PCD-145145 - Fixed an issue that was introduced in PC-DMIS 2017 R2. The selection and highlighting of CAD surfaces was not working as before.
    • PCD-145787 - Fixed an issue where the Illumination tab did not appear in the Probe Toolbox.
    • PCD-147666 - PC-DMIS I++ server has fixed readouts for DEA machine interface for manual CMMs.
    • PCD-148136 - Prevented a possible incorrect initialization of touch probes in combination with VisionBox.
    • PCD-149711 - Fixed scanning for the Zeiss direct machine interface.

  • #2
    I can't understand the software model Hexagon is using for this software. Three versions (2017 R2, 2018 R1, 2018 R2) that (if any logic behind this) shares the same bugs. I mean the ones fixed in 2017 R2 SP10 above must exist in the 2018 iterations as well, no? No wonder they call their architecture "complicated".

    Hoping a 2018 R2 SP2 is coming soon then, with 30-something issues fixed.
    Last edited by vpt.se; 10-04-2018, 08:46 AM.
    PC-DMIS CAD++ 2o19 R1 SP11

    Comment


    • #3
      Originally posted by vpt.se View Post
      I can't understand the software model Hexagon is using for this software. Three versions (2017 R2, 2018 R1, 2018 R2) that (if any logic behind this) shares the same bugs. I mean the ones fixed in 2017 R2 SP10 above must exist in the 2018 iterations as well, no? No wonder they call their architecture "complicated".

      Hoping a 2018 R2 SP2 is coming soon then, with 30-something issues fixed.
      One can hope!

      Comment


      • #4
        Originally posted by vpt.se View Post
        I can't understand the software model Hexagon is using for this software. Three versions (2017 R2, 2018 R1, 2018 R2) that (if any logic behind this) shares the same bugs. I mean the ones fixed in 2017 R2 SP10 above must exist in the 2018 iterations as well, no?
        My understanding is that it goes something like this: When a bug is found it is usually fixed *first* in the upcoming (not yet released) version. Then there is a priority thing to decide if/when the fix can/should also be backported to previous releases, and to which of them (sometimes the changes in the particular code area has been extensive, so the current fix doesn't apply to the older code).

        AndersI
        SW support - Hexagon Metrology Nordic AB

        Comment


        • #5
          So, the 2017 version must be one of the most deployed since it is up to SP10 - or, some very extra-special customers have it...
          PC-DMIS CAD++ 2o19 R1 SP11

          Comment


          • #6
            Actually it looks like most modern versions have around 10 SP:s - 2015.1, 2016, 2017 R1, 2017 R2...

            2018 R1 and R2 will catch up, given a little more time...
            Last edited by AndersI; 10-04-2018, 10:56 AM.
            AndersI
            SW support - Hexagon Metrology Nordic AB

            Comment


            • vpt.se
              vpt.se commented
              Editing a comment
              Looks like you are correct, AndersI - just checked.

          • #7
            Thanks for posting this update. I've been waiting for 2017 R2 SP10 to come out since it includes the fix for a bug I reported. You can also download it here: ftp://ftp.wilcoxassoc.com/PC-DMIS-Ve.../2017_R2/SP10/
            CMMXYZ Applications Specialist: PC-DMIS Support and Training. Check out my PC-DMIS tutorial videos... https://blog.cmmxyz.com/blog/tag/cmm-tech-tips

            Comment

            Related Topics

            Collapse

            Working...
            X