I was reading through a Mastecam X3 pdf, and in a portion dedicated to control parameters there is a page that points out the post variable strings associated with the different fields on the NC output, Mill page in the Mastercam machines/default control menue. It says that the check box labeled "Reset sequence numbers in subprogram" is associated with a string variable "sub_seq_typ$" in the post processor. I checked through my custom post, the generic mastercam mill posts for Haas, fadal, fanuc etc and none of them contained this variable.
I would like to know the exact function of this check box (the pdf description was somewhat nebulous) and how the variable is applied to the post syntax such that it will apply itself.
Perhaps a different approach. Does anyone have a post that has this Variable string included in it? Would it be possible for you to paste those bits of the post file here so I can see how it's logic works?
Perhaps you guys can help me out in a little different capacity. I have a MasterCam file with a basic program in it made up of contour toolpaths. I needed to be able to mix and match different elements of this program to create some 50 or so different program setups. I did this through toolpath transform operations. Each transform represents a separate program and is posted separately into its own NC file. The issue is that with over 50 transforms, in the one file, that contain subroutines, the output carries the subroutine sequence numbers through all of the transforms even though they are posted individually. For example when I post transform #1 the first subroutine sequence number is L100 as you would expect it to be, but transform #5 posts L500 rather than restarting the sequence. This is a simplified case.. my transforms have about 16 subs a piece and at the end of them the sequence numbers are so large they go beyond the limitations of the machine.
I would like to figure out if the "Sub_seq_typ" variable properly implimented will in fact resequence those subroutines for any given NCI output. Or perhaps this variable does something completely different...
This will help out a lot with creating arrays of programs.
If any of you have any suggestions on how to create arrays of programs efficiently that spit out NC code that needs minimal amount of editing I'm all ears (eyes) for sure.