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
  • When you run the "dcc alignment" are you using auto features? Also are you using guided points or just taking the points randomly in the areas? When I was usings arms I found that the changing nominals stopped for the most part when using auto features and guided points on the final alignment. This keeps consistency between runs and hopefully operators. Show some code, also someone else chime in, isn't there a setting about updating nominals? Never had to mess with it but I have heard of people having issues with this.

    The big thing to keep in mind is that the arm is a great piece of equipment that allows us to pretty much measure anywhere, but with that being said it opens up the door for additional issues because there is no fixed location/coordinate system on a table allowing for some error in measurement/setup. This means that the programmer has to take additional sets making sure that the points/programs are as repeatable as possible. This means additional alignments, guided points, pictures of setups, and lots of comments/notes. If things are done right arms will be extremely successful within your company. If these things are disregarded the arm will be put in a closet and will collect dust because everyone will say that the arm is a piece of crap (which at the end of the day is just company/employee lack of understanding).

    Hopefully this helps, and if you have more questions just let us know.

    Wicked
Reply
  • When you run the "dcc alignment" are you using auto features? Also are you using guided points or just taking the points randomly in the areas? When I was usings arms I found that the changing nominals stopped for the most part when using auto features and guided points on the final alignment. This keeps consistency between runs and hopefully operators. Show some code, also someone else chime in, isn't there a setting about updating nominals? Never had to mess with it but I have heard of people having issues with this.

    The big thing to keep in mind is that the arm is a great piece of equipment that allows us to pretty much measure anywhere, but with that being said it opens up the door for additional issues because there is no fixed location/coordinate system on a table allowing for some error in measurement/setup. This means that the programmer has to take additional sets making sure that the points/programs are as repeatable as possible. This means additional alignments, guided points, pictures of setups, and lots of comments/notes. If things are done right arms will be extremely successful within your company. If these things are disregarded the arm will be put in a closet and will collect dust because everyone will say that the arm is a piece of crap (which at the end of the day is just company/employee lack of understanding).

    Hopefully this helps, and if you have more questions just let us know.

    Wicked
Children
No Data