I got a post working, sent it to my co worker. First thing he says is there is no coolant. So I go look and sure enough no coolant. I check my original copy... coolant works. I file compare the two... he changed a few formatting things but nothing that looks like it would affect the coolant. So I have played around with it, put some watches on my debug and ran it. Got to a break point after my scoolant. Scoolant = 0, prv_scoolant = 0, coolant$ = 1, prv_coolant$ = 0... Why isn't my scoolant updating? Being still pretty new to post edits I would love a quick run down on how updates work. Tried a ! but got nothing. Looked over my fstrsel and it looks fine. # Coolant M code selection sm09 : "M9" #Coolant Off (Use sm09_0 through sm09_2) sm08 : "M8" #Coolant Flood sm08_1 : "M7" #Coolant Mist sm08_2 : "M8" #Coolant Tool sm09_0 : "M9" #Coolant Flood Off sm09_1 : "M9" #Coolant Mist Off sm09_2 : "M9" #Coolant Tool Off scoolant : "" #Target for string fstrsel sm09 coolant$ scoolant 7 -1

I found my mistake. I didn't see there are two places it calls the G43. Problem fixed.

I got the sub programming to spit out the number I wanted with a subnumber = t$ * 10 + 2000. Everything works fine until you call up the tool again and it spits out the same subnumber. I am trying to figure out a way to initialize a counter for every tool that only ticks if that tool has been called up before. I am going to sleep on it but probably wont come up with it by tomorrow. Any ideas would be appriciated.

I am trying to do the same thing but can't seem to find the param you are talking about. Using a MPmaster x8 mod post. Tried a pfcout but it only picks up the first sub. The rest are null

As always, You're awesome Colin! Thanks

Is there a string I can use to detect the size of a program? Sometimes we post programs bigger than the machine will read. I want to setup a mprint for this.

I have been working on the MD for a 5 Axis machine. I think I have something backwards. When I look at the NCI i see a B300. move where I want a B60. Any one know what I did wrong? Or is it in th CD?

I wanted to take a moment and encourage the eMastercam users to fill out the Mastercam customer survey if they have not filled one out before. Here is a link https://ux.mastercam.com/satisfaction/

Did not read page two. Pretty much said what 5th (Ron) said.

EPIC!

Interesting. I'll keep that in mind. We only have upper turrets so I think we are safe. Thanks for the heads up.

Could you upload pictures of your progress? I am going to look into Zoller today.

Thanks guys, I seem to have most of it posting out correctly but I am not fully understanding what you are talking about 5th. What problem crops up when using axis substitution? How is the dummy defined in the post?

I was able to finish it up last minute yesterday. Thanks be to both of you for the help.

Yeah, I saw that section... was hoping to avoid it but I am sure you are right. It's in there... some where.

I am working on edits to the MPLMaster for a dual spindle dual turret lathe. I finally figured out my machine definition and the NCI looks great. Z moves are negative when they should be negative and that stays true when I switch to the sub spindle. When I post the NC file it looks good on the main spindle but when it hits the sub my Z numbers get flipped. I double checked the NCI and I am sure it is good. I can't find a switch that is setup for the Master pst X8 that gives the invers only when it is hitting the sub. The other thing I thought was odd is that the NCI reads a 1001 for a facing move on the main but then does a 1002 for a facing move on the sub. I thought 1002 was tool change. Does any one know what I am missing here?

Still stuck but making progress. Moving to the post processer form for my next issue and I hope my last.

Got it, I didn't set my axis combination up after I built a new setup

Thanks Cathedral, I have been playing around with it for a few hours. I have the machine setup with dual spindle and then a left turret that reads +x as the positive relative to the WCS for the z axis and then a second turret that reads -x for the z axis. I have flipped it around and tried rebuilding it a few times but it doesn't seem to change how my T-Plane is being created. Maybe I am missing a step after I save it to update the machine?

Get a 3D mouse from 3DConnexion. It lets you rotate the part any which way you could imagine with one hand. I bought the basic one for my self but have used the ones with the key boards. You can map key strokes to it that make things like chaining and drawing a breeze. I love my little mouse.

I am new to using Mastercam lathe. I learned a few things from IHS lathe book and went to get started on a lathe job. The problem I ran into is trying to do a stock transfer. On the machine I am working with the sub spindle's turret runs opposite in Z when compared to the main spindle. When I transfer stock my Z does not flip. Is this an issue in my MD? or am I missing something else?

Colin, I got the sub to work with the spindle_no$. I suck in a few sub triggers and a submerge and it looks good. You have me a little nervous that I missed something. Why were you thinking this was such a poor way to do it?

But the control requires two separate programs, one for the main spindle and one for the sub spindle. How else would I be able to get two programs in one shot? EDIT: Fixed Typo

If there isn't one I could just use the work offset as the trigger, but I would rather have something more solid. Worst case I could always have the MISC INT and use that.

I think I am going to work the post out to run the whole thing without macros in the machines. I have a pretty good idea on how I want to do this. I am going to use a sub program merge and post two programs with the one post. No big deal but I am struggling on one thing. I want to add some logic to my post that says if I am working with the right spindle then post that section out to the sub program. I don't know any variables off the top of my head I can use to achieve this. Is there one for the axis combination?