forced m08 in mpmaster

[Beardog]

Hi

 

I have a quick question, how would I force a m08 at every tool change in the mp master for x4?

We have had problems with tool coolant turning off when importing operations.

So I would like to hard code it into the post.

 

thanks

[CJep]

Beardog,

 

Go to a postblock in MpMaster called ptlchg_com look for this line of code -

 

pbld, n$, "G43", *tlngno$, pfzout, scoolant, next_tool$, e$

 

change scoolant to "M08"

remember to use the open quotes then close quotes this will hard code the information

 

The one issue is though if you have the coolant turned on in the toolpath you will get double coolant output and you won't get an M09 output to turn the coolant off, you will need toi hard code that as well

 

Possibly a better solution would be to select all the toolpaths in the operations manager and do an edit selected operations / edit common parameters then do a mass edit turning on the coolant

[Beardog]

thanks

 

That is what we have been doing. but the new guys keep forgetting to do it.

[Charlie Pierson]

one of many ways:

 

 

in postblock ptlchg_com #Tool change common blocks

change

pbld, n$, "G43", *tlngno$, pfzout, scoolant, next_tool$, e$

to

pbld, n$, "G43", *tlngno$, pfzout, "M08", next_tool$, e$

[Charlie Pierson]

ooops, I type too slow.

[CJep]

Beardog,

 

I should have read that before I hit "send it", if the coolant is turned on in the toolpath it will result in double coolant codes if you're using the X-Style coolant.

 

I you do not have the coolant turned on in the toolpath there will be no M09 output to turn the coolant off "M09" would need to be hard coded as well in the pretract post block

 

There is a scoolant command in the line associated with the G91 G28 Z0. line

[Beardog]

thanks everyone.

 

going to try that.

 

I would like to figure out what causing it in the first place. We have converted all tool files to x4 coolant.And it does not happen all the time so it is hard to track down.

 

but thanks

[Storkman]

What ya gonna do if ya wanna run a dry tool?

[chip]

forcing the coolant shouln't matter so long as it's not on the same line. Some machines don't like double M code.

[Tony35]

if you have coolant set to "from tool" when you import the ops you have to pick the tool to update the coolant command PIA i know i say if you save a op it should save it just how it was coolant etc

 

HTH

[Beardog]

thanks tony

 

that does like what is happening.

[Grievous]

No message

[Rob @ Target Machine]

Maybe a better way to hardcode coolant on.

 

If you look at pretact, 'coolant$ = zero' is what turns off the coolant.

 

Add 'coolant$ = one' right before scoolant is called in ptlchg_com.

 

From MPMASTER:

code:

---

ptlchg_com

 

coolant$ = one #<--------Add this to hardcode coolant on

pcan1, pbld, n$, *sgcode, sgplane, [if not(index), sgabsinc, pwcs], pfspeedout, scoolant, pfcout, strcantext, e$

 

 

 

pretract

 

coolant$ = zero #<--------This should already be here

pbld, n$, strcantext, scoolant, e$

---

This will eliminate double coolant code output and allow you to use M00 before an operation at a null toolchange (mi10$).

eg. tool check, move clamps, remove slug, etc.