Mazak Smart Control for Mill (using fusion 640M post).

Mazak Smart Control for Mill (using fusion 640M post).

Anonymous
Not applicable
1,305 Views
3 Replies
Message 1 of 4

Mazak Smart Control for Mill (using fusion 640M post).

Anonymous
Not applicable

Hi Guys,

 

I've just managed to convince the powers that be, that an upgrade in our CAM capabilities is in order, due to the increasing complexity of our 3 axis work.

 

I had a couple of hours to dip my toes into Inventor HSM with a simple test part on Friday (an arbitrary 2d contour with a tapped hole). These are the issues I encountered using the Mazak fusion 640M post on a Mazak Smart control (we use a 640M post with our One CNC advantage software, so I figured it might be pretty close), I'm sure there will be more:

 

*I could only save the posted file with the .nc extension. I need it to save as .eia  so the control sees it via the DNC link (I manually changed it for the purposes of this test).

 

*The control doesn't like the % symbol at the beginning and end of the program. I've found the corresponding code in the PP - writeln("%"); - can I just delete this without any other consequence?

 

*The control ran the facing, 2d adaptive and 2d contour ops without problem, but when it came to the tapping op, the post spits out an M29 (unrecognised by the control) and a G84 (I think synchronous right hand tapping on this control would be G84.2 with no M code). I've found this area in the PP too, but have no experience hand programming beyond a few manual alterations to a program, so I'd like guidance on how to proceed with any changes.

 

Would there be a more suitable post already available perhaps?

 

 

I'd massively appreciate any help anyone can offer. New to all of this!

 

Dave.

0 Likes
Accepted solutions (1)
1,306 Views
3 Replies
Replies (3)
Message 2 of 4

Anonymous
Not applicable

So I've tried the generic Mazak post this morning, which has resolved a few of my issues:

 

The posted file is saving with the .eia extension and the % symbols have gone. Also, the M29 has gone before the G84, but I still need a bit of advice getting the PP to output G84.2/G84.3.

 

 

Thanks in advance!

0 Likes
Message 3 of 4

Anonymous
Not applicable
Accepted solution

Dave

 

You are looking for the section for drilling it is under this function.

 

function onCyclePoint 

 

from there look for the tapping sections.  They start as follows.

 

case "tapping"

 

From there you can just replace the 74 with your left hand tapping code and the 84 with yor right hand tapping code.  the gCycleModal.format handles the formatting of the code with the g letter.

 

Hope this helps.

0 Likes
Message 4 of 4

Anonymous
Not applicable

Thanks.

0 Likes