movepoints

[RussL]

V3.7 MR2 - XP SP2
We generally use clear planes but must from time to time use movepoints.
We generally re-align a particular program a number of times in various ways to accomodate whoever is requesting the data.
When I re-align a program, the features nominals update fine, the movepoints do not.
I have to update all the movepoints manually and with the parts we have, this can be time consuming (datums are more than not, at some compound angle).
Is there any way to get PC D-MIS to update the movepoints as it does the features nominals?

[craiger_ny]

It should. I do not remember having that problem when I used MR2. If you edit your alignment then you should get a dialog asking if you want to update the commands, select "Yes". Like I said I do not remember that being an issue when I used MR2 but going to MR3 may help.

So will drinking beer.

[JamesMannes]

Don't mean to sound like a smarty axx or anything but maybe mr3? Guys? maybe someone else would know?

[Underspec]

Updating after the new alignment should work. I'm not sure about MR2 though. Anothing thing you can try is move increments instead of move points.

[#2#]

Don't mean to sound like a smarty axx or anything but maybe mr3? Guys? maybe someone else would know?

It should be working as long as you click yes to update. Maybe that question is turned off though.

Well, I'd say download mr3 and install it. It is much more stable than mr2. Also, make sure you have the hotfix for SP2 installed.

You aren't modifying your original and only copy of the program are you? Make a copy of the program and modify that so that if you make a bad oops, you won't have to re-write the entire program. Marking a program as "read-only" is a good way to make sure you don't accidentally mess up the original.

[justncredible]

Yes you can, here is a example of "tieing" a move point to a feature, in this case a PNT1, will work for most I have heard. Useing this will force the move point to update with the feature and not based off the alignments. It works independant of the rest of the part and will move from the feature tied to.

MOVE/POINT,NORMAL,PNT1.X+1,PNT1.Y+1,PNT1.Z+1.5

[T Miller]

Yes you can, here is a example of "tieing" a move point to a feature, in this case a PNT1, will work for most I have heard. Useing this will force the move point to update with the feature and not based off the alignments. It works independant of the rest of the part and will move from the feature tied to.

MOVE/POINT,NORMAL,PNT1.X+1,PNT1.Y+1,PNT1.Z+1.5

nice to know thanks

[#2#]

Yes you can, here is a example of "tieing" a move point to a feature, in this case a PNT1, will work for most I have heard. Useing this will force the move point to update with the feature and not based off the alignments. It works independant of the rest of the part and will move from the feature tied to.

MOVE/POINT,NORMAL,PNT1.X+1,PNT1.Y+1,PNT1.Z+1.5

Good tip. I'll have to file that one away for future use.

[Ravenmaniac]

Just for the knowledge of : mr2 will autoupdate movepoint criteria when a new alignment is introduced. Just make sure that you don't have the auto commands refering to updating all related criteria below the new alignment turned off.

[justncredible]

A guy in my cad++ class showed me.

Remember that it moves from the feature you tie it to.

[craiger_ny]

A guy in my cad++ class showed me.

Remember that it moves from the feature you tie it to.

Keep in mind when doing features of size to use appropriate extensions. If you want to move a certain distance from a circle (lets say 0.100 in this case) you'd want to do something like:

MOVE/POINT,NORMAL,CIR1.X + (CIR1.D / 2) + 0.1,0,1.5

or

MOVE/POINT,NORMAL,CIR1.X + CIR1.R + 0.1,0,1.5

Or some variation of that. I use it a lot for hitting faces of thin walls where there is a lot of possible variation. Good tip and very flexable. Movepoints are the quite flexable which is one reason I prefer them over clearplane (though clearplane has it's merits).

Craig

[Roberto]

V3.7 MR2 - XP SP2
We generally use clear planes but must from time to time use movepoints.
We generally re-align a particular program a number of times in various ways to accomodate whoever is requesting the data.
When I re-align a program, the features nominals update fine, the movepoints do not.
I have to update all the movepoints manually and with the parts we have, this can be time consuming (datums are more than not, at some compound angle).
Is there any way to get PC D-MIS to update the movepoints as it does the features nominals?

Why don't you do the re-aligning at the end of the program (right before recalling dimensions).
That way you don't have to deal with updating move/points.

Roberto.

[Roberto]

Keep in mind when doing features of size to use appropriate extensions. If you want to move a certain distance from a circle (lets say 0.100 in this case) you'd want to do something like:

MOVE/POINT,NORMAL,CIR1.X + (CIR1.D / 2) + 0.1,0,1.5

or

MOVE/POINT,NORMAL,CIR1.X + CIR1.R + 0.1,0,1.5

Or some variation of that. I use it a lot for hitting faces of thin walls where there is a lot of possible variation. Good tip and very flexable. Movepoints are the quite flexable which is one reason I prefer them over clearplane (though clearplane has it's merits).

Craig

I think the option MOVE/INCREMENT does the same...Am I wrong?

[craiger_ny]

I believe move increment moves incrementally from your retract. There may be instances where you need to move to a point that is a set distance from a feature. In some cases yes increment is the same (when moving a set distance from a feature you just measured) in some cases it is not (when moving a set distance to within a feature previously measured).

[#2#]

Why don't you do the re-aligning at the end of the program (right before recalling dimensions).
That way you don't have to deal with updating move/points.

Roberto.

That is a good idea. Unless his dimensions are interspersed with his feature measure commands and not all at the end of the program.