M6End macro thoughts (newbie alert)

[StanLewis]

After getting my 5'x10' router running...  I am looking at ways to make things more efficient (read I want the machine to work for me 

My question is simple.  Why would I want the machine to return to the previous spot called out before a tool change?  I am working towards having a certain location that the machine moves to (got this one), wait for the tool change (got this one), and when cycle start moves to the start of the next tool operation (know how to do this conceptually) not the previous position.

I'm not sure if my idea is sound.  Basically, moving the bit to machine coord z0 in the M6End macro and then letting the gcode take over to go do whatever it is that the gcode does.

BTW, I cut molds so it is mostly 3d with CV on and don't want to mess those up.

Stan

[ger21]

You can do whatever you want in the M6 macros.

 In my M6 end, after pressing cycle start, the new tool is zeroed by probing to a fixed reference plate, then returns to the previous tool's position when the M6 was called, then resumes cutting.

[StanLewis]

I understand that I can do what I want in the M6End macro....

The question is more of "should I" as I do not see any reason to return to the previous location to start the next cutting operation.  Usually the gcode goes to x0y0 (whichever offset is working) and then begins the operation.

I noticed this while manually moving the cutter to a tool change location, then moving it manually to near the starting point, only to have Mach move to the previous location and then back to the location that I had moved it to.....

so what if I don't use the M6End to move back to the previous location before resuming the gcode?

What kind of scenarios would rise up and bite me?

Stan

[ger21]

Actually, I'm not sure why I'm moving back to the previous position.

It shouldn't make any difference, provided your first move after the M6 is to a rapid height.

If you're not going back to the previous position, then why not go one step further, and don't go to X0 Y0 either?

[StanLewis]

Well that is what I'll probably end up doing.  It is just that Visual Mill usually rapids to x0y0 and then onto the actual cutting.

Right now it is more of a visual fuzzy to make sure the machine hasn't hiccuped....

Stan