hexagon logo
Register Sign in
  • Replies 37 replies
  • Subscribers 225 subscribers
  • Views 851 views
  • Users 0 members are here
Options
Related

Nominals in DIMENSIONS keep changing!

seppley
I have read most of the posts on this site, and they mainly seem to point to the nomials for the actual feature changing... and like most of you say " I have never had DMIS change a nominal ... ever! And if it is changing it on you , you have done somthing wrong!"

I am not talking about it changing a nominal for a feature! I am saying that when i create a dimension, without CAD, I have to tell it what nominal i want for the dimension, bedcause it always picks the wrong one! Then I print a report and all is fine... UNTIL I RUN THE PROGRAM AGAIN! Then, the next time i print the report, all the nominals are different and I have to update them again!

Also tolerances that i put in the angle dimension edit box won't transfer to the report at all.

Thoughts??

Sam
Parents
  • I've seen a case of nominals changing today (in a vpt part program Stuck out tongue closed eyes ). At least for this one case, it seems the cause was an incomplete alignment. The program only did level on a plane, set Z-zero on the plane, nothing more. I could reliably see the nominals change when testing offline.

    Then I added two 'fake' features, a line from an MCS axis, and the MCS origin, and used them in the alignment to make it complete (level, rotate, zero), and suddenly the nominals stopped changing.

    We'll have to wait for the final verdict when vpt has tried this online, in a CMM...

    Perhaps this should be taught as a caveat in the training lessons. If you want to lock in your nominals, start the program with a constructed alignment from generic features. We used to do this with our PMM w/QUINDOS (UNIX) and never had an issue. I believe that we were instructed to build features and place them in one of the db's , EDB, GDB, I don't remember. This way we could access the feature for an initial alignment for any program we built.
Reply
  • I've seen a case of nominals changing today (in a vpt part program Stuck out tongue closed eyes ). At least for this one case, it seems the cause was an incomplete alignment. The program only did level on a plane, set Z-zero on the plane, nothing more. I could reliably see the nominals change when testing offline.

    Then I added two 'fake' features, a line from an MCS axis, and the MCS origin, and used them in the alignment to make it complete (level, rotate, zero), and suddenly the nominals stopped changing.

    We'll have to wait for the final verdict when vpt has tried this online, in a CMM...

    Perhaps this should be taught as a caveat in the training lessons. If you want to lock in your nominals, start the program with a constructed alignment from generic features. We used to do this with our PMM w/QUINDOS (UNIX) and never had an issue. I believe that we were instructed to build features and place them in one of the db's , EDB, GDB, I don't remember. This way we could access the feature for an initial alignment for any program we built.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement