hexagon logo

Nominals are changing once in a while when I rerun the program

We recentely purchased a new version of PC-Dmis 2012 mr1. I've written a few part inspection programs and verified / ran them on different parts. I am seeing the nominals change every once in a while when I just run a program or more so when modify a program by adding a new dimension to the program. It doesn't seem to affect the new dimension, just random dimensions on the report which causes me to have change the nominal back and then refresh the report.

I experience this to a greater occurance when I run programs that I had created using 2010 MR1.

The 2012 MR1 program was installed on a brand new laptop.

I was told that 2010 MR1 had some memory leaks and that was the cause of the nominals changing. Does 2012 have the same issues too? ( we upgraded to get rid of the nuissance of having to shut down and restart every 10 -15 minutes of use on the old system )
Parents
  • there is a setting to toggle in settings editor that fixes the problem with not using a fully constrained alignment.. have to dig a little to find the post but I remember it and it worked.

    make sure that 'allow fine tuning of alignments' in NOT checked in your f5 page. Only use this when you want to update your theoreticals but not your measured values.

    be sure you don't have any warnings defaulted such as 'carry nominal back to feature'; i always reset these to a select few with every program.

    play with the update dependent features option and fine tune alignments in a test program to get a very good understanding of what these will do in the different possible combinations. Those pesky little questions can mess up a lot of things with a quickness if not careful. Good luck!
    +1 yes the warnings are critical if your clicking yes or no without knowing the repercusions. It can be a disater. Use to run into this problem all the time in my first year of programming
Reply
  • there is a setting to toggle in settings editor that fixes the problem with not using a fully constrained alignment.. have to dig a little to find the post but I remember it and it worked.

    make sure that 'allow fine tuning of alignments' in NOT checked in your f5 page. Only use this when you want to update your theoreticals but not your measured values.

    be sure you don't have any warnings defaulted such as 'carry nominal back to feature'; i always reset these to a select few with every program.

    play with the update dependent features option and fine tune alignments in a test program to get a very good understanding of what these will do in the different possible combinations. Those pesky little questions can mess up a lot of things with a quickness if not careful. Good luck!
    +1 yes the warnings are critical if your clicking yes or no without knowing the repercusions. It can be a disater. Use to run into this problem all the time in my first year of programming
Children
No Data