Transform - Match Existing Offsets

[Brian Pallas]

I never noticed until a few weeks ago on the Transform tab the "Match Existing Offsets Stored in Planes".  Overall I think it works pretty slick, I like it. 

1. Seems that it works the best if the start value for work offset is "0".  If the first actual plane being used has, and increment "1".  It kind of seemed like those fields should be greyed out if using the match offsets feature.  

2. If you change the work offset number of the plane with the planes manager, you need to regen the transform op to get the output to change.  This had me chasing my tail a little bit trying to figure out why the match offsets feature didn't appear to be working.  

 

Does anyone know what the variable name is for the plane comment?  

 

 

[Guest]

I set mine up and rarely have an issue

[Brian Pallas]

Also, is there any way to add logic into the post that would detect that a pre existing  plane was not detected if the "match offsets" feature is being used?  It would be nice to get an alarm when you post, instead of it just doing whatever.

[Guest]

1 minute ago, Brian Pallas said:

Also, is there any way to add logic into the post that would detect that a pre existing  plane was not detected if the "match offsets" feature is being used?  It would be nice to get an alarm when you post, instead of it just doing whatever.

I'm thinking no.....

If a plane was skipped that info would never get into the nci file......so I don't think there is a then a way to check against info that doesn't exist

[Brian Pallas]

If you change a work offset number in the plane manager and then just repost, does the change show up?

 

[Guest]

I set up the transforms like this...so it should pick up whatever offset number you give the existing plane

I use the by Toolplane when rotating paths

 

Edited June 21, 2017 by Guest

[Brian Pallas]

Yeah, I think I got it working, and understand it.  

I found the code for the tool plane comment - it is 20011.  I added it into the post, but it seems I am only getting output from the plane that the original operation is using. Any ideas around that?  

 

 And actually as I was trying some things as I was doing this post the 20010 prmcode takes the name that you give the plane without needing an additional comment, so I think I will use that.

 

I attached some pics showing the desired output that I hand edited and the current mastercam output, and what I added/am using.  Basically I am just trying to label which fixture position is being machined at each sub call.

 

 

 

[Guest]

You may have to use the code inside of the postblock for the transform as well to pull the active plane

Never done it, so not sure if it will work

[Brian Pallas]

Aah, under the "Transform Operation Parameters" changing the "Source" from NCI to Geometry made it so: 

1. The comment for the planes updates and

2. Made it so that if I change the plane work offset under the plane manager, that the posted output reflects the change without needing to regen the transform op.