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

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

timgramley
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
  • I have unchecked "Ignore CAD<->Part" under the F5-settings and set the registry flag "UseTHEOsForCADToPartLevelAlignment" to "1" (true). This setting is versionspecific so your mileage may vary.
    This has done wonders for my wandering nominals. But as DaSalo says, this is surely mentioned in other posts handling the topic.

    I made a program like this today and after measuring a plane I did a level and origin and then measured a circle and a slot (the THEO's taken from points clicked on the model).
    I ran it and noticed a small deviation in the theo's. I polished these up and moved my part slightly.
    Ran it again and noticed larger deviations in the theo's. Moved the part slightly more.
    Rinse, repeat - still getting theo's that deviated. Polished them again.

    Closed PC-DMIS, fired up the settings editor and looked up the UseTheosForCADToPartLevelAlignment. I changed the setting to TRUE (1), saved and closed the settings editor.
    Ran the program again and still got theo's that deviated. At this time, I almost blew a gasket, thinking that it didn't work.
    Anyway, I polished the theo's once more, saved and closed the program.
    Opened it up again and ran it. No deviating theo's!
    Moved the part slightly, ran it - no deviating theo's!
    I repeated this at least three more times, all resulted in the theo's staying the same.

    Heureka! Finally! (time for a happy dance!)

    So, all in all, it seems that the registry setting did the trick! Too early to tell if the setting affects something else though... (knock on wood)

    From the links posted earlier.
Reply
  • I have unchecked "Ignore CAD<->Part" under the F5-settings and set the registry flag "UseTHEOsForCADToPartLevelAlignment" to "1" (true). This setting is versionspecific so your mileage may vary.
    This has done wonders for my wandering nominals. But as DaSalo says, this is surely mentioned in other posts handling the topic.

    I made a program like this today and after measuring a plane I did a level and origin and then measured a circle and a slot (the THEO's taken from points clicked on the model).
    I ran it and noticed a small deviation in the theo's. I polished these up and moved my part slightly.
    Ran it again and noticed larger deviations in the theo's. Moved the part slightly more.
    Rinse, repeat - still getting theo's that deviated. Polished them again.

    Closed PC-DMIS, fired up the settings editor and looked up the UseTheosForCADToPartLevelAlignment. I changed the setting to TRUE (1), saved and closed the settings editor.
    Ran the program again and still got theo's that deviated. At this time, I almost blew a gasket, thinking that it didn't work.
    Anyway, I polished the theo's once more, saved and closed the program.
    Opened it up again and ran it. No deviating theo's!
    Moved the part slightly, ran it - no deviating theo's!
    I repeated this at least three more times, all resulted in the theo's staying the same.

    Heureka! Finally! (time for a happy dance!)

    So, all in all, it seems that the registry setting did the trick! Too early to tell if the setting affects something else though... (knock on wood)

    From the links posted earlier.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement