hexagon logo
Register Sign in
  • Replies 16 replies
  • Subscribers 32 subscribers
  • Views 246 views
  • Users 0 members are here
Options
Related

PC DMIS Crash all the time?

Wolfram
We just purchased a Romer Arm 7525 and I've been feeling my way in the dark for the past couple of days. I haven't had the training yet, next class is full and won't be another until December?!?... Anyhow, that's a different issue.

I've had success pulling in CAD's, running alignments(starting to wrap my head around it, but I think a lot has been luck), but the real problem I'm running into is PC DMIS crashing several times a day. Can it sense I don't know what I'm doing? This thing may be smarter than I thought...

Situations where it crashes: manual alignment to part without CAD (3 times in a row, measured plane, taking hits on circle, on third hit it crashed)
Many other times, don't know enough about what I did to lead to the crash...

Anybody experience this? Suggestions?
  • I had a problem with PC-DMIS crashing and locking a lot also, as well as losing contact with my Romer. I couldn't identify any specific circumstances that would cause it. Then, my Hexagon support told me there was a new version of WinRDS available. No crashes since installation. Worth a try!
  • We just purchased a Romer Arm 7525 and I've been feeling my way in the dark for the past couple of days. I haven't had the training yet, next class is full and won't be another until December?!?... Anyhow, that's a different issue.

    I've had success pulling in CAD's, running alignments(starting to wrap my head around it, but I think a lot has been luck), but the real problem I'm running into is PC DMIS crashing several times a day. Can it sense I don't know what I'm doing? This thing may be smarter than I thought...

    Situations where it crashes: manual alignment to part without CAD (3 times in a row, measured plane, taking hits on circle, on third hit it crashed)
    Many other times, don't know enough about what I did to lead to the crash...

    Anybody experience this? Suggestions?

    Most likely, you're putting corrupt code in the program, and it's choking on it.

    Suggestion...go to class. I know that classes are held weekly, throughout the US. If your company is willing to pay for a plane/hotel, you could be in class tomorrow!
  • Most likely, you're putting corrupt code in the program, and it's choking on it.

    Suggestion...go to class. I know that classes are held weekly, throughout the US. If your company is willing to pay for a plane/hotel, you could be in class tomorrow!

    If he needs the Romer/Reshaper class, it is ONLY held in NC and one facility. We are looking at the 7525 here as well and that is what we've been told for training. ONE location and one only.
  • If he needs the Romer/Reshaper class, it is ONLY held in NC and one facility. We are looking at the 7525 here as well and that is what we've been told for training. ONE location and one only.

    I think that would matter only for a 7525SI, with the scanning option.

    But let's try to keep it to the point: if you don't have PCDMIS experience, as a trainer, I recommend that you stick to using QuickMeasure prior to going to class. You'll waste more time fiddling with the unknowns in PCDMIS, and you won't ever be able to trust your results until you're formally trained.

    ......Of course, you COULD start messing around in PCDMIS Portable in the Help Menu, but I never said that, as I think it would be only a slightly less colossal waste of time. Save your mental energy, let us get you started on the right path before you waste time walking in circles.
  • I’ve found that PCDMIS is not accustomed to allowing unorthodox methods. While there may be more than one way to skin a cat, PCDMIS is like a candy store. However even though there is more than one method that will get you from A to B, PCDMIS doesn’t like it when you take short cuts. You have to follow software protocol.

    Whenever you start hitting undo, backspace, escape, cut, paste, copy, skip, repeat…etc etc etc. PCDMIS “learns” if you will that the programmer/operator is having trouble following commands. I'm guessing maybe it’s some what of a safety feature to protect the integrity of the software, I don't really know what you could call it. Keep your eye on the command line as this will tell you a lot about what is going on at the time. And SAVE often. PCDMIS also doesn’t like to remember everything you tell it to do then erase and do again. Keep doing that and it is sure to crash. So stop doing that for the rest of your life so long as you program with PCDMIS.
  • Most likely, you're putting corrupt code in the program, and it's choking on it.

    Step 1) Blame the user....

    I agree with your statements about the necessity of training, but still. The fact that pc-dmis requires the user to tread very carefully or suffer the consequences (crash) is a software problem, not a user problem.

  • Whenever you start hitting undo, backspace, escape, cut, paste, copy, skip, repeat…etc etc etc. PCDMIS “learns” if you will that the programmer/operator is having trouble following commands. It’s some what of a safety feature to protect the integrity of the software.

    That's just silly.
  • Step 1) Blame the user....



    This is probably relevant.

    I think that just about covers the original post. Should I get more information, I'll reassess.
  • I’ve found that PCDMIS is not accustomed to allowing unorthodox methods. While there may be more than one way to skin a cat, PCDMIS is like a candy store. However even though there is more than one method that will get you from A to B, PCDMIS doesn’t like it when you take short cuts. You have to follow software protocol.

    Whenever you start hitting undo, backspace, escape, cut, paste, copy, skip, repeat…etc etc etc. PCDMIS “learns” if you will that the programmer/operator is having trouble following commands. It’s some what of a safety feature to protect the integrity of the software. Keep your eye on the command line as this will tell you a lot about what is going on at the time. And SAVE often. PCDMIS also doesn’t like to remember everything you tell it to do then erase and do again. Keep doing that and it is sure to crash. So stop doing that for the rest of your life so long as you program with PCDMIS.

    I'm not sure where this is coming from, but PCDMIS doesn't have any sort of learning algorithm embedded in the coding. More than likely, confirmational bias is leading you towards assigning what you view as a trend to random circumstance.
  • That's just silly.

    Is not! That's how programs get corrupted, by using undo too often on top of copy/paste and then missing something or inadvertently deleting something. Maybe not with the newer versions but 4.3 certainly don't like it. OK, I admit the safety feature was for lack of better words but I don't know how else to describe it just kicking you right out but that's what it does. I'd say 99% of the time I'll go back into someone's program and find an unfinished command where they tried to copy something and didn't get everything they needed. I tell them to quit trying to save time by copying commands from other programs and just program normally.

    If we have time to fix it and do it over then we have time to do it right the first time.
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement