You would just call up the new fixture offset and start over. They doo NOT need to be exactly placed if you use your G54, G55, etc. (Never ran a Haas other than rotary) They can be enywhere. If you use "fixture offsets" you would indicate each fixture and enter that into your offsets page. In case I'm down a fixture or adding another fixture in a seemingly random place, and don't want to go back to Espirit to write/add/edit programs and what not. Write one program complete, open it up in multi fixture mode, tell it how many fixtures, tell it wether part dominant or tool dominant, post the code, stand back and look pretty. No copying ops, no moving fixtures, no duplications, organizations, rearranging, keeping track, forgetting one, getting pissed.
#HOW TO CHANGE TOOL NUMBER IN A PROHRAM ON FEATURE CAM CODE#
It will create the identical code above right outta the box. OTOH if you really want this really really really simple, just use FeatureCam and it's multifixture capability. Your post should be able to handle the structure no problem, so hand editing will end up relatively simple. For Fanuck you gotta jump through some hoops by either using external subs or conditional GoTo-s, but the idea is the same. Cut the blocks between N110 and N111, paste it into another local sub.Īll you have to do now is to put the sub-calls and offset changes in place of the original code and you're done: When you're ready to split it into subs, just cut and paste the blocks between N100 and N101, paste it into a local sub. You can proove it out, tweak it whatever. If you look, this is a straight forward single part code. My programming, no matter what is done as this:
What you can do however is to make your programming structure sub-friendly. I think Street's issue is to not have to go through the subroutine route.įrankly, I don't think there is a reasonable way around it.