hexagon logo

Nominals in DIMENSIONS keep changing!

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
  • To my own defense, the primary alignment - the very first one, is the same as I do in every program. Measure a plane, level and set origin to the plane. Then I go about and measure features for locking rotation and setting origin.

    The program AndersI is referring to had the primary alignment - just as he describes, but the following alignment (rotation lock and origin) was a bestfit alignment, I am sure AndersI noted this, so there was
    a complete alignment in the program - not only a level and origin. This is not the first time this have happened to me and almost all times, there is a BFALN involved.

    This procedure should work nevertheless - the nominals (THEO's) should not be touched, unless you as a user allow or tell it to.
    The way I see it, this is a bug somewhere in the underlying PART/CAD/MACHINE transformation matrix that just does not work.
Reply
  • To my own defense, the primary alignment - the very first one, is the same as I do in every program. Measure a plane, level and set origin to the plane. Then I go about and measure features for locking rotation and setting origin.

    The program AndersI is referring to had the primary alignment - just as he describes, but the following alignment (rotation lock and origin) was a bestfit alignment, I am sure AndersI noted this, so there was
    a complete alignment in the program - not only a level and origin. This is not the first time this have happened to me and almost all times, there is a BFALN involved.

    This procedure should work nevertheless - the nominals (THEO's) should not be touched, unless you as a user allow or tell it to.
    The way I see it, this is a bug somewhere in the underlying PART/CAD/MACHINE transformation matrix that just does not work.
Children
No Data