hexagon logo
Register Sign in
  • Replies 38 replies
  • Subscribers 223 subscribers
  • Views 401 views
  • Users 0 members are here
Options
Related

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

Alvin_A2
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.
  • 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
  • in reply to JacobCheverie
    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.
  • Just to be clear, can you share an image of the error message you are seeing? When does it occur?

    Also, it sounds to me like you are describing multiple issues in your post. In the future, please try to separate them into separate posts, to the best of your ability.
  • in reply to Don Ruggieri
    Sorry, I know I asked a random question at the end there.

    I will try to take a screen capture the next time it happens but to describe what happens, I re launch PC-DMIS after it froze and I had to force close it from task manager (this is not a PC-DMIS has crashed and it's collecting data issues, it literally just freezes) and the program list on the home screen has a spinning loading indicator that goes from blue to green. Then I have to open a program from the file open box. When I open my program it says "Server is busy, please switch to or end the application (which I think it thinks the previous PC-DMIS is still running but it's not in my task manager)"

    It's a little vague but I'll get a picture of the error when it comes again.
  • in reply to Don Ruggieri
    I would suggest the following, to help identify the issue and possibly get you going at the same time.

    Reboot the computer to ensure a fresh start

    Start by disabling the home page before you run PC-DMIS. Go into the Settings Editor and then Connect and look for the option captioned ShowHomePage and set it to False. Save this and Exit the Settings Editor

    Start PC-DMIS, and watch for this issue to repeat.

    Let's start there, see if it tells us anything
  • in reply to JacobCheverie
    I understand your concern entirely. Some users seem to be dreading the potentially inevitable migration due to the exact same reason. If you have many older programs, it may be quite the task to migrate to the new Geometric Tolerance. I'd assume that is part of why Hexagon is still supporting Legacy. Even coming from XactMeasure and using custom report templates will be quite a task to migrate properly.

    In any event, it is a valid concern. The way I see it - If we or our co-workers were doing something wrong, there's no time like the present to get up to speed and fix it before any measurement errors continue. It is easier to turn a blind eye, but it's best to adjust when you can.
  • I appreciate the input. I will follow up when I can.
  • On post #2.2 you said "I'd assume that is part of why Hexagon is still supporting Legacy."

    My two cents on that...if hexagon did away with legacy that would be my last straw and i would make sure that my company and all of our divisions switched to a different software.
  • for real though im not playing that would be WILDLY disappointing. not everybody wants to use their GD&T stuff. I have lots of customers who give me jacked up prints, I need legacy! geotol is great and i can comfortably use it when I need to but if I was forced into only using that, nope see ya!

    Making Constrained L2 as a best fit math type for autofeatures as well as constructed features is what we really need!
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement