hexagon logo
Register Sign in
  • Replies 6 replies
  • Subscribers 5 subscribers
  • Views 215 views
  • Users 0 members are here
Options
Related

PCDMIS 2022 update Geotol from ".UAME" to ".SIZE" screws up QDAS

Froush
Updating from PDCMIS 2021 to 2022 the naming in Geotol for features of size changed from ".UAME" to ".SIZE"

This completely jacks up QDAS as it creates features based of feature names in PCDMIS. See attached...

I now have 100s of parts in QDAS with added ".SIZE" features shoved at the end of all parts. Anyone have an idea to fix this?

In the future can we stop changing the extension for features... It was difficult enough going from Xactmeasure to Geotol now this.
Attached Files
  • Yes. I know how to fix this. And I am not being sarcastic either:

    STOP USING XACT/GEOTOL COMMANDS

    If you stick with Legacy commands, the code will never change regardless of what "new ideas" they have about wreck..I mean...changing.. the software. Plus, you'll have more control over your programs/alignments.

    Good luck, I understand your frustration completely. Hexagon is the only company I have ever worked with that changes their software every four years and then literally tells people to f off over it lol.
  • Yes. I know how to fix this. And I am not being sarcastic either:

    STOP USING XACT/GEOTOL COMMANDS

    If you stick with Legacy commands, the code will never change regardless of what "new ideas" they have about wreck..I mean...changing.. the software. Plus, you'll have more control over your programs/alignments.

    Good luck, I understand your frustration completely. Hexagon is the only company I have ever worked with that changes their software every four years and then literally tells people to f off over it lol.

    True! lol this is the 2nd time i've been screwed over with XACT/GEOTOL commands. I figured with hexagon acquiring QDAS someone would throw red flags at this. Guess not!

    Don't get me wrong its a powerful tool and we utilize it all the time. I genuinely like the software, its just extremely frustrating the amount of time put into setting QDAS up to then be thrown off by a PCDMIS update for syntax changes. Then on the QDAS side your required to purchase "service hours" for assistance. I bought "service hours" to ask questions because not all of the "help files" are converted to english yet makes sense... I would not recommend QDAS as your solution if your looking to quickly capture CMM data. It takes a ton of time to set up and right now you are crutched to use QDAS service hours because the help files suck.
  • Jakep379 There should be a toggle to shut this off in PC-DMIS and not send the data. Let me see if I can get you the exact process and post it here.

    Legacy is fine, but it you have MMB on your Datums, you could not be fitting optimally for part acceptance.
  • Jakep379 There should be a toggle to shut this off in PC-DMIS and not send the data. Let me see if I can get you the exact process and post it here.

    Legacy is fine, but it you have MMB on your Datums, you could not be fitting optimally for part acceptance.

    Planes are still in the sky, my prgs work well Sunglasses
  • Jakep379 There should be a toggle to shut this off in PC-DMIS and not send the data. Let me see if I can get you the exact process and post it here.

    Legacy is fine, but it you have MMB on your Datums, you could not be fitting optimally for part acceptance.

    Yep this also is why we are using Geotol to utilize MMB to better represent a fit. Also correlates with functional gages great! I like it, just stop changing the syntax for it! lol

    Thanks Chris for looking into this. Any help is Appreciated
  • Update for a solution. Not really a fix and it was a huge pain took hours... But essentially I had to Archive all part data and start fresh. This way the data moving forward created new parts that no longer has .UAME & .SIZE mixed. Also to point we will be slowly moving away from GEOTOL to not run into any more issues.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement