hexagon logo

Update dependant commmands prompt is not appearing

PC DMIS 2014.1 X64 Build 767 Service Pack 2

When changing or adding an alignment the update dependant commands prompt is NOT appearing. This is on both the CMM and the offline station

Looked in the setting editor at the Update Below Changed Alignment during Execution entry. The current value is 0 which I believe is correct.

Also looked at the Updat EXTERNAL Alignment Dependant Commands during File Open entry. I don't think this applies since its for external alignments. The current value for it is 0.

To the best of my knowledge nothing has been changed from the default setting in the Settings editor.
Parents
  • I'm pretty sure this is the bandwagon I need to be on.

    I have had more than one program, recently written, all in 2018, that continues to change feature coordinates in everything below an alignment. My "recalled" alignment COULD be affecting it, but since I am changing the zero point on the last measured feature, I'm expecting feature coordinates below the alignment to remain where I left them.

    Example: I measure a feature that I measured the last time I ran the program and it's moved a little. In one case a slot that is 3.05 mm tall on a YZ plane. The alignment in the tool that stamped and formed the part wasn't correct so the slots can actually seem to be lower on some parts and higher on others. Touch the bottom of the bottom slot, set zero in Z. Now touch the top of the same slot and it didn't usually run too bad, but could. Limp through by slightly changing the Z move on that point. Touch the front and rear of the same slot (last time I ran it five minutes ago I changed these moves to be 1.5 mm in Z (halfway up the height of the slot) but now, after setting zero for Z on this current slot, those drive moves are near to zero, sometimes in the negative. Won't run. reset to 1.5, goes on. Slots directly above this slot now also all have to be modified. Wash, rinse, repeat, repeat, repeat....

    Is this something new that is occurring with 2018? (Corporate is sending me my more recent licenses, but not sweating that yet). It's alot like the old Lotus 1-2-3 relative vs. absolute feature types. Is there a setting I am missing? H-E-L-P.

    Thank you!
Reply
  • I'm pretty sure this is the bandwagon I need to be on.

    I have had more than one program, recently written, all in 2018, that continues to change feature coordinates in everything below an alignment. My "recalled" alignment COULD be affecting it, but since I am changing the zero point on the last measured feature, I'm expecting feature coordinates below the alignment to remain where I left them.

    Example: I measure a feature that I measured the last time I ran the program and it's moved a little. In one case a slot that is 3.05 mm tall on a YZ plane. The alignment in the tool that stamped and formed the part wasn't correct so the slots can actually seem to be lower on some parts and higher on others. Touch the bottom of the bottom slot, set zero in Z. Now touch the top of the same slot and it didn't usually run too bad, but could. Limp through by slightly changing the Z move on that point. Touch the front and rear of the same slot (last time I ran it five minutes ago I changed these moves to be 1.5 mm in Z (halfway up the height of the slot) but now, after setting zero for Z on this current slot, those drive moves are near to zero, sometimes in the negative. Won't run. reset to 1.5, goes on. Slots directly above this slot now also all have to be modified. Wash, rinse, repeat, repeat, repeat....

    Is this something new that is occurring with 2018? (Corporate is sending me my more recent licenses, but not sweating that yet). It's alot like the old Lotus 1-2-3 relative vs. absolute feature types. Is there a setting I am missing? H-E-L-P.

    Thank you!
Children
No Data