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
  • You don't have to defend yourself. There must still be a bug (feature?) in PC-DMIS involved.

    I could repeat the problem in your original program. Then I stripped everything after the two circles, so all I had was the partial manual alignment + two circles in CNC, (no BFALN) and I could still generate the problem. Then I made the alignment complete (but still oriented exactly the same), and the problem was gone (after that I tested the same fix on the original program, and all was fine).

    So, to me, it seems PC-DMIS is doing something wrong when we go into CNC after only a partial alignment. Or I'm not understanding how it is expected to work (which wouldn't be a first...).


    Verified - but with a totally different program.

    How would we go about to "explain" or "find" the culprit (the reason for this happening) here?
    Anders, got any ideas?

    I would say that when aligning on a plane and setting origin in it, PC-DMIS should retain the MCS, but sometimes it seems that PC-DMIS cannot do this, instead it moves/adjusts the nominals (although it should not!) by itself, just like if we have answered YES to a global "Do you want to update the nominals...".
Reply
  • You don't have to defend yourself. There must still be a bug (feature?) in PC-DMIS involved.

    I could repeat the problem in your original program. Then I stripped everything after the two circles, so all I had was the partial manual alignment + two circles in CNC, (no BFALN) and I could still generate the problem. Then I made the alignment complete (but still oriented exactly the same), and the problem was gone (after that I tested the same fix on the original program, and all was fine).

    So, to me, it seems PC-DMIS is doing something wrong when we go into CNC after only a partial alignment. Or I'm not understanding how it is expected to work (which wouldn't be a first...).


    Verified - but with a totally different program.

    How would we go about to "explain" or "find" the culprit (the reason for this happening) here?
    Anders, got any ideas?

    I would say that when aligning on a plane and setting origin in it, PC-DMIS should retain the MCS, but sometimes it seems that PC-DMIS cannot do this, instead it moves/adjusts the nominals (although it should not!) by itself, just like if we have answered YES to a global "Do you want to update the nominals...".
Children
No Data