2019 r2 sp2

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

  • 2019 r2 sp2


    here :
    http://software.hexagonmi.com/public...e/2019_R2/SP2/
    ftp://ftp.wilcoxassoc.com/PC-DMIS-Ve...19_R2/SP2/x64/


    Release Notes - 2019 R2 SP2
    • PCD-146773 - Fixed an issue with the Outlier filter where you couldn't apply it to auto circles and line features.
    • PCD-151139 - Fixed an issue where a double-click didn't open a measurement routine file. Instead, PC-DMIS displayed an error about a bad archive.
    • PCD-155563 - Fixed an issue where the B5 controller would not accept any commands from PC-DMIS when it's in PARK mode. This fix ensures that no temp comp commands are sent to the B5 controller until the ENDPARK status was set in the measurement routine.
    • PCD-161289 - Fixed a crash that occurred when you tried to calibrate additional tips after a tool changer calibration.
    • PCD-162867 - Fixed an issue that occurred when you opened or edited an old custom report.
    • PCD-167498 - Fixed an issue where an incorrect diameter was computed when you box-select a laser cylinder feature from a COP.
    • PCD-170533 - Fixed an issue where the software deletes the LampDefinitions.xml from the ProgramData folder when you reset PC-DMIS.
    • PCD-171391 - Updated the HR-MP rack calibration measurement to account for a design change in the production rack. This fix also allows the TP20 probes to be used with the HR-MP rack.
    • PCD-173138 - Fixed an issue to allow PC-DMIS to show snapshots in landscape orientation in report templates.
    • PCD-173438 - Fixed a crash in summary mode that occurred when a start block command was used without an end block command.
    • PCD-173470 - Fixed a crash that occurred when you tried to open the Thickness Scan dialog box after Quick Linear scans.
    • PCD-173545 - Fixed the issue where silent or passive install modes failed to install on network license servers.
    • PCD-174088 - Fixed an import VISI issue where the surface colors were not correct.
    • PCD-174370 - Fixed Solidworks tessellation issues.
    • PCD-174472 - Removed the unneeded blank space in the Axis field to correct the value in the statistics.xml for legacy profile dimension.
    • PCD-174473 - Corrected a probe drawing issue.
    • PCD-174982 - Fixed an issue where the Scale Drawing dialog box would not open from the Shift+Right-mouse button combination.
    • PCD-175419 - Fixed an issue where the camera ID for a vision probe was changed, but any existing optical calibration data was not deleted.
    • PCD-175673 - Fixed a crash that occurred when you used the Analysis window on a custom report.
    • PCD-175777 - Corrected DMIS syntax for the MEAS/ENDMES block.
    • PCD-175818 - Fixed an issue where PC-DMIS would not open an Online measurement routine from the Home page on a Portable system.
    • PCD-175846 - Fixed the issue where filtering didn't work as expected because the conversion from decimal to percentage was missed when calculating the point reduction filter value in Laser Scan dialog boxes.
    • PCD-176129 - Fixed a crash in a dual arm machine configuration that occurred when you used Arm 2 to measure a point in manual mode and clicked the Done key on the jogbox.
    • PCD-176574 - Fixed a crash that occurred when you used nested groups.
    • PCD-176641 - Fixed an issue that caused some torus surfaces in IGES imported files to not render properly. This was an issue especially noticed in IGES files that were exported out of TubeShaper.
    • PCD-176746 - Added a change to our service pack policy that requires a Software Maintenance Agreement for installation.
    • PCD-176898 - Fixed an issue that occurred when you set the SkipNumberOfStripes registry entry in the Settings Editor application to -1. This value indicates that no purple scan stripes were visible in the Graphic Display window for the active scan pass. Once the scan pass was finished, the graphically rendered blue pointcloud was seen.
    • PCD-177036 - Fixed an issue related to Euler transformations where the I++ server can do ScanCircle features with HSSDAT and set a manual retract.
    • PCD-177426 - Fixed a software error that occurred because of a startup timing issue.
    • PCD-177452 - Fixed an issue in the feature extraction where laser features were measured relative to others.
    • PCD-178020 - Fixed an issue where readouts of x, y, z, a, and b were corrected for I++ server.
    • PCD-178572 - Fixed an issue with the TempComp for the Wenzel version of the I++ server that supports GetProp/SetProp part.
    • PCD-178618 - Fixed an issue where the hardware component name was corrected from Senmation_HP-S-S-X5 to Senmation_HP-S-X5.
    • PCD-178990 - Fixed a typographical error which caused a tip to report a thickness of 0.



    Last edited by JEFMAN; 11-22-2019, 09:00 AM.

  • #2
    FYI

    A confirmed bug by Hexagon in 2019 R2 (JIRA 180393), referencing this thread: https://www.pcdmisforum.com/forum/pc...bration-offset pertains to vision-to-tactile auto calibration. Program, as written, works in 2019 R1 and older releases, but does not work in 2019 R2.

    From the awesome vision people in the UK:

    "I am able to reproduce the issue you are seeing... once the vision probe completes the calibration the machine just stops moving.. the execution timer continues but nothing else happens. I will see if I can identify anything obvious but this looks like a bug introduced in 2019 R2."

    "I actually made a second discovery today with this issue. After the machine stops (once the vision probe cal is complete ) I went ahead and stopped execution.
    Pc-dmis appeared normal.. so I executed the routine again expecting it to perform the vision probe cal again, instead the machine moved over to the rack and picked up the tactile probe, it moved to the machine centre and then just stopped with the execution dialog counting…. Again cancel and execute.. this time it dropped the probe off, before picking it up again and pausing the machine."

    I will double check that is issue is still valid in R2 SP2, but I have a feeling it will be.

    Comment


    • bfire85
      bfire85 commented
      Editing a comment
      Still an issue with SP2.

  • #3
    PCD-176746 - Added a change to our service pack policy that requires a Software Maintenance Agreement for installation.

    This one is pretty surprising...and a little alarming....
    Ex-Hex

    Comment


    • #4
      Originally posted by anthony.alfaro View Post
      PCD-176746 - Added a change to our service pack policy that requires a Software Maintenance Agreement for installation.

      This one is pretty surprising...and a little alarming....
      Agree... Not a nice enhancement !

      Comment


      • #5
        Originally posted by anthony.alfaro View Post
        PCD-176746 - Added a change to our service pack policy that requires a Software Maintenance Agreement for installation.

        This one is pretty surprising...and a little alarming....
        Thought there was a whole big thing recently about getting all SP's for a version (i.e. supporting that version through its life span)?
        Automettech - Automated Metrology Technology

        Comment


        • anthony.alfaro
          anthony.alfaro commented
          Editing a comment
          I just checked with some people at Hexagon and it's confirmed.

          You now have to have a current SMA to get the service packs.

          It USED to be that way, get all SPs for the life of the version, but seems to be no longer.

        • AndersI
          AndersI commented
          Editing a comment
          Actually, in the MR1, MR2,...,MRx times you could only install the MR if your SMA was valid, then for a while, the SP:s have been possible to install as long as your SMA covered your base version. Now the SP:s behave like the old MR:s.

      • #6
        Originally posted by NinjaBadger View Post

        Thought there was a whole big thing recently about getting all SP's for a version (i.e. supporting that version through its life span)?
        I thought that was the case too. Maybe they are trying to find more ways to squeeze the $$$ out of it's users. I'd think it would be pretty crappy on their part to leave a customer hanging with a bad release of a service pack if there was a critical issue.

        Comment


        • #7
          Originally posted by bfire85 View Post

          I thought that was the case too. Maybe they are trying to find more ways to squeeze the $$$ out of it's users. I'd think it would be pretty crappy on their part to leave a customer hanging with a bad release of a service pack if there was a critical issue.
          Maybe this new rule allows to avoid applying new fixes to old releases ?

          Comment


          • #8
            Originally posted by JEFMAN View Post

            Maybe this new rule allows to avoid applying new fixes to old releases ?
            So they get to work less?

            Comment


            • #9
              PCD-176746 is insane. (but really should not be a surprise)
              the Hexag00ns take your $$$ for a release, ask you to help them repair the product thru Tech Preview, and then if the customers point out flies in their ointment, or make creative suggestions, any 'SERVICE pack' is now gonna be charged to you for much of the work done BY CUSTOMERS them self!. It was too true to be believed for the time that Hexag00ns supported fixing a major release and didn't bill you.

              Comment


              • #10
                Originally posted by sealevel View Post
                PCD-176746 is insane. (but really should not be a surprise)
                the Hexag00ns take your $$$ for a release, ask you to help them repair the product thru Tech Preview, and then if the customers point out flies in their ointment, or make creative suggestions, any 'SERVICE pack' is now gonna be charged to you for much of the work done BY CUSTOMERS them self!. It was too true to be believed for the time that Hexag00ns supported fixing a major release and didn't bill you.
                Please tell us how you really feel.

                Comment


                • A-machine-insp
                  A-machine-insp commented
                  Editing a comment
                  Yeah... Don't hold back now...

              • #11
                ...Yeah... Don't hold back now..
                Actually? I was. However, I'll put the latest Hexagon buffoonery in the proper forum.... Vision....... a hint::
                it's actually not about PC-DMIS SMA & lie-sensing stuff, but more so about the great Hexagon hardware service.

                Comment


                • #12
                  One more question about PCD-176746 - Added a change to our service pack policy that requires a Software Maintenance Agreement for installation.
                  Is this also valid for older versions, or just for future ones?
                  I don't understand how Hexagon can sell a product with potential bugs, and also sell the patches. Is it really legal?
                  I can understand it for real enhancements, not for fixes !

                  Comment


                  • anthony.alfaro
                    anthony.alfaro commented
                    Editing a comment
                    i have no confirmation on if it applies to older versions. I would assume it would be, "Just going forward" as it is part of a software release which would indicate that it's part of the code and as long as you stay in the older versions, you'll never have that code.

                    unless of course, they add it to any service packs released from here froward regardless of the version? I'm not sure....

                    I wouldn't really put it past Hex...

                • #13
                  We find the bugs, on our time, our arguments with IT, Management, and still have to pay!! Im not getting any real value from this except conversing and learning from you folks.
                  Happy Thanksgiving.
                  Rule#1 of business - NEVER give your customers a reason to buy from you competitors.
                  sigpicTAU ALPHA PI INDIANA DELTA CHAPTER
                  "Due to the highly confidential nature of my job, I am not allowed to know what I am doing" - author unknown

                  Comment


                  • #14
                    • PCD-176746 - Added a change to our service pack policy that requires a Software Maintenance Agreement for installation.
                    Surprised? Lol.
                    PC-DMIS CAD++ 2o19 R1 SP11

                    Comment


                    • #15
                      Nevermind. It won't let me update. I have 2019R2 but Universal Updater will not allow me to get SP2.
                      Last edited by JacobCheverie; 11-26-2019, 10:01 AM.

                      Comment


                      • bfire85
                        bfire85 commented
                        Editing a comment
                        Is your SMA current? Otherwise, grab it from the ftp site.

                      • JacobCheverie
                        JacobCheverie commented
                        Editing a comment
                        bfire85 It is current, but we are waiting for the license server to be setup here so I do not have an active license. It let me download the .exe but I can't activate.
                    Working...
                    X