That should work, check your syntax....indent, commas and spaces

So, what is the output when you add the string literal?

I can't work out if you want the lock codes or not. In your original post you asked to get rid of them completely, now you want them or not?

He's decided he wants to keep the lock codes......

Try adding the string literal I added in the second copy pbld, n$, "G28 B0.", e$

peof$ #End of file for non-zero tool @end pretract if swt_lock_codes = one & rot_on_x, pbld, n$, *sunlock, sunlockcomm, e$ rotretflg = 1 # pbld, n$, *sg28, "X0.", "Y0.", protretinc, e$ #pbld, n$, *sg28, "Y0.", protretinc, e$ rotretflg = 0 if swt_lock_codes = one & rot_on_x, pbld, n$, *slock, slockcomm, e$ comment$ if not(index), n$, sgabsinc, e$ uninhibit_eof_probe$ n$, "M2", e$ mergesub$ clearsub$ mergeaux$ clearaux$ "%", e$ So we can move to peof. Assuming you always want to zero the B axis a simple string literal would do the trick peof$ #End of file for non-zero tool @end pretract if swt_lock_codes = one & rot_on_x, pbld, n$, *sunlock, sunlockcomm, e$ rotretflg = 1 # pbld, n$, *sg28, "X0.", "Y0.", protretinc, e$ #pbld, n$, *sg28, "Y0.", protretinc, e$ pbld, n$, "G28 B0.", e$ rotretflg = 0 if swt_lock_codes = one & rot_on_x, pbld, n$, *slock, slockcomm, e$ comment$ if not(index), n$, sgabsinc, e$ uninhibit_eof_probe$ n$, "M2", e$ mergesub$ clearsub$ mergeaux$ clearaux$ "%", e$

swt_lock_codes : 1 #Output Rotary Lock/Unlock M-codes #0 = Off #1 = Use lock codes for all operation types This is the Rotary Output settings at the top of the post. Try setting this to 0 to turn your lock codes off. This might not work as there has been some modification to the post. We can try looking at pretract if this doesn't work to your liking. There is a conditional statement there for swt_lock_codes=1, so changing the setting to 0 should work.

What is your base post?

I recently bought two HP z books. One off the shelf i9 with 64G RAM and an Quadro A2000. It performs better than I expected. I also got a custom build which I specified I wanted balanced DIMs to help control the heat from the 128G of RAM. I ended up with the latest Gen i7 (it had the configuration for the balanced DIMs) and with the 128G ram and A4000 card it totally smokes the "backup".

What kind of 3D path have you tried?

While you are at it you could do your control defaults as per Colin's Pro Tip at the top of the Indus. Forum. Well worth the effort.

No need, we used a tool library with all the fields prefilled. Grab a tool, grab a holder (holder library) set projection and it all comes out in the post (modified .SET) just referencing the parameters . The worst was building the tool and holder libraries (tedious doesn't do it justice) as nothing had been done before, but once done we could just add on as we went.

If you look in the MP documentation it will give you the parameter numbers of all the AVAILABLE fields. Some are not. it has been a while since I did my tool list post so I can't remember which exactly. They aren't necessarily related, so I know I used the "CHUCK" field for tool crib position. Basically, because it was the only one I had left. However, when it posts out the tool list it is labeled "CRIB LOCATION" not "CHUCK".

The overall length is fixed by the manufacturer, the projection will vary from job to job. People actually use all the fields to define the tool (including order number or location in the crib). Defining the OAL as tre actual OAL rather than using this number for projection aids in tool management and avoids confusion when selecting or ordering the tool.

That explains it.... If you can incorporate it into your post it is easy to use. Federal Applications Manager, very impressive C, congrats.

Dapra make carbide cored insert holders. True 90 degree cut

Tool Management, does Haas do that as an option?

Maybe I am not understanding, but the stock output (at least in Mpmaster) is controlled by pstock. pcomment is for posting comments and manual entries..

Just bought 2 HP lappys. One with an A4000 as my main standalone workstation and another back up with an A2000 which I will hook up to the net. The backup performs much better than I expected although not as well as the Hotrod.

I just got an HP with a latest gen i7. I wanted balanced DIMS (heat control) on my 128G RAM and that was the chip they could use within the architecture of the laptop to give me 4x 32Gs of RAM. It's pretty quick....

Have you played with the C axis utility? I got used to it, but the thing I like is that if you give it a C angle it will show you the cutter orientation. i used the CNC Multi axis lathe post as a base.

Ditto Ron. The other related problem I had was insufficient feed rate while stitching (swaging dies in D2 and S7). If your cutter looks like it has been rubbed like an old school eraser.....it has. I never had a problem once i just settled on being aggressive with feed rates. I machined annealed at 250 SFM left .015 - .02 stock. Hardened then finished. Can't remember what surface footage, whatever the machinists handbook recommended for the hardness we used worked good as I recall. High feed toolpaths ate it up. I did a whole bunch, once I had it down I could walk away and program, just checked the cutters.

No it is only available in Mill. There are Renishaw alternaitves (Inspection+?) but they are stand-alone, not "imbedded" in your Mastercam file. Have a look at Renishaws web site, or give them a call, I have always found them to be very helpful. And they DO know their stuff. you could possibly use modified drill cycles if you don't need all the functionality.

Head head machines are particularly vulnerable ..... have you got a test program to test your "adjustments".

Depends, the basis for a good continuous improvement program is a robust "post and go" source file. If you are never going to see the part again, all bets are off.