hexagon logo

PC-DMIS Software to Server connection unbearable. Please help.

Hello. I have a 7.10.7 SF electric machine running PC-DMIS 2020 R2. We all know the unfortunate notoriousness of software crashes. But, I am having too many issues and need help.

From my understanding, I have a virtual dongle and with that, every line of code or action I do with PC-DMIS communicates online to its server base. I have had my software crash several times just from saving as one example. There are also times when I try to re-open the software and when I open a project it says that the server is busy and I have to restart my computer to fix it. (I've checked my task manager and could not find anything to stop in order to avoid restarting the computer).

Should I try to receive a physical dongle like the older machines to avoid these issues? I never had this stuff happen until I started using the virtual dongle. I don't even know if I can do that to be honest.

Also, I haven't done my research thoroughly enough but I'm at the point where I feel I can't trust Exact Measurements versus Legacy anymore. Sometimes the differences in results can be over .001 (inches) and even greater. I know I've set up my datums properly for both ways to spit out the results. I also find it silly how in R1 you could get away with apparently a not properly constrained datum to give results that may be inaccurate and now 2020 R2 won't allow you to even create the feature if it's not constrained right with the datum scheme.

Thanks for taking the time to read my post! I appreciate it.
Parents
  • Are you submitting particular crash reports? Perhaps you can speak with Don Ruggieri ?

    There is no more XactMeasure in 2020 R2+. Hexagon substituted it with the new Geometric Tolerance command which uses a rebuilt GD&T library to closer conform to the applicable GD&T standards. You will receive large differences between the Geometric Tolerance command and Legacy if your alignment is not performed following GD&T rules and if your (datum) features are not nominally correct.

    Some may likewise consider your concern to be silly, others may consider it to be valuable. It is helpful to have the software yell at you if you're not following the rules because it makes everybody wiser to what the rules are. If you prefer, you can stick with Legacy but you won't see agreement if your dimensioning isn't performed properly.

    https://www.pcdmisforum.com/forum/pc-dmis-enterprise-metrology-software/pc-dmis-for-cmms/471877-weren%E2%80%99t-able-to-join-the-virtual-pc-dmis-users%E2%80%99-group-recordings-now-available?p=481419#post481419
  • Hey there Jacob.

    This may be an ignorant statement but I've seen the crash reports entry field pop up for a decade, and this kind of issue seems to never have a real solution. The only difference I know is that I never had these problems when using a physical dongle.

    I regards to XactMeasure and GT Command, I see what you mean. I notice the name of the dimension box called out differently. The options box just looks the same to Xact.

    The reason being why I find this silly is, up until this Geometric Tolerance new feature forcing you to constrain things properly even moreso than before (which I agree is not a bad thing), it makes me think about all of the legacy dimensions that myself/anyone else who had dimensioned something may or may have not been correct. It's concering seeing how all the sudden these restrictions are incorporated and before the software let you create your dimension anyway.

    I appreciate the message. If anyone knows if it's possible to get a physical dongle instead of this virtual one, I believe that to be the answer.
Reply
  • Hey there Jacob.

    This may be an ignorant statement but I've seen the crash reports entry field pop up for a decade, and this kind of issue seems to never have a real solution. The only difference I know is that I never had these problems when using a physical dongle.

    I regards to XactMeasure and GT Command, I see what you mean. I notice the name of the dimension box called out differently. The options box just looks the same to Xact.

    The reason being why I find this silly is, up until this Geometric Tolerance new feature forcing you to constrain things properly even moreso than before (which I agree is not a bad thing), it makes me think about all of the legacy dimensions that myself/anyone else who had dimensioned something may or may have not been correct. It's concering seeing how all the sudden these restrictions are incorporated and before the software let you create your dimension anyway.

    I appreciate the message. If anyone knows if it's possible to get a physical dongle instead of this virtual one, I believe that to be the answer.
Children
No Data