Lathe Rapid moves

[Rocketmachinist]

I was wondering how can I modify the post to not have the z and x axis rapid together then coming from tool change position. I want it to go to Z axis first and then do the x axis moves, instead of both of them together.

[Jimmy Wakeford from Barefoot CNC]

You could change it in the toolchange section of the post, depending on the type of cut may not be what you want everytime. Instead of changing the post you could use points to move the tool to Z(whatever) then do your od operation. You could also use points to drop X first for id ops.

 

To create the "goto " points use toolpath- point.

[Rocketmachinist]

Jimmy, how do i change it so it never rapids is both axis. The guy that runs the lathe refuses to use the post until the post shows up the way he likes it.

[Sbarner]

Can't it just be changed in the control definition? Under linear in the control def, "Each axis moves at maximum feedrate independently". Unless I'm not understanding what you are wanting.

[Mr. Wizzard]

The guy that runs the lathe refuses to use the post until the post shows up the way he likes it.

If the code is good and the program works, maybe you need a new lathe guy.

The only way I could think of is to tediously edit the post so that the axis moves are split up on every postline. That would be quite time consuming and I don't see any need for it.

[Jimmy Wakeford from Barefoot CNC]

To get only one axis the "goto" point needs to be the same X as your home postion. (May need to some logic at top of tlchg so the value is not output anyway.) I have had to do alot of "operator" specials in the past.

[Pimp_your_post]

If you take mplmaster as an example you will see that most rapid move go through one post block : prapidout. In this postblock, you need to setup your output lines like this :

 

pbld, n$, psgplane, psgcode, pxout, pcout, pyout, pscool, strcantext, e$

pbld, n$, pzout, e$

 

In this case you will get an X move (and Y if applicable) first, then you will get a Z move.

 

Will this fix everything? Most likely not because you still need to check and see if there are other places in your code where rapid moves are ordered. The most likely places are ptlchg$ and ptlch0$ but you should also check your retract routines.

 

Somebody mentioned that it can all be done in the control definition but that only works for mills (or mill tool paths on lathes). For your lathe tool paths you have to set that up manually.