hexagon logo

PC DMIS Crash all the time?

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?
Parents
  • 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.
Reply
  • 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.
Children
No Data