Tool plunges into work piece before spindle RPM reached

Tool plunges into work piece before spindle RPM reached

trober14
Explorer Explorer
1,343 Views
12 Replies
Message 1 of 13

Tool plunges into work piece before spindle RPM reached

trober14
Explorer
Explorer

I've had this issue before and changing the CAM helped but it would be nice to trust the CAM that fusion is exporting without always having to check the g-code. To sum up my issue, fusion is exporting g-code in which there is a G0 command to below the stock material top surface. This means my CNC will execute it before the spindle is up to speed. Is this a bug or is there something I'm doing wrong?

0 Likes
1,344 Views
12 Replies
Replies (12)
Message 2 of 13

Anonymous
Not applicable

Hi

I checked and post it with fanuc and didn't find any issue. Please check the picture.

On the other hand if you face the problem then it means its a problem in post not Fusion.

 

plung.PNG

0 Likes
Message 3 of 13

Richard.stubley
Autodesk
Autodesk

Hi @trober14,

 

Is this more of a question that your spindle takes a set amount of time to ramp up to speed?

 

Most controllers have a handshake to check the spindle is up-to speed before executing the next move. However if your machine does not do this, have you thought of putting a dwell in after the spindle speed call?

 

You can put a line of code in that will dwell for 1 second per 1000 RPM (using a P in the G4 denotes milliseconds)Spindle dwell.PNG

Hope this helps.

 

 



Richard Stubley
Product Manager - Fusion Mechanical Design
Message 4 of 13

seth.madore
Community Manager
Community Manager

The questions that the last two posters have failed to ask is:
What's the machine and controller? What Post Processor are you using?

What would you like to see for behavior, do you have sample code you can share that represents desired output?


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes
Message 5 of 13

trober14
Explorer
Explorer

N16 is where the error is. Tool moves to Z -0.1075 before the first G01 command is issued. So the machine doesnt wait till spindle is up to speed before executing. 

0 Likes
Message 6 of 13

trober14
Explorer
Explorer

Its a home built machine using linuxcnc. I post to EMC2. I dont believe its on the machine or post side. Another commenter tried posting to Mach3 and the error was still present at N16. 

 

Attached is a similar part where the g-code generates correctly. The machine rapids to Z0.2, the next command issued is a G01 to Z0.0394 with a plunge feed rate of 5in/min which means the machine will wait till the spindle reaches 16k rpm before executing this line. Then the tool plunges to Z-0.9375 with the same feed rate. 

 

Fusion is exporting code with that G01 missing causing the machine to plunge into work piece before the spindle is up to speed. I would think it was an issue with my CAM skills if it happened regularly but I see this only 1 out of 50 programs. 

 

 

%
(1001)
(T2 D=0.25 CR=0. - ZMIN=-1. - FLAT END MILL)
N10 G90 G94 G17 G91.1
N15 G20
N20 G53 G0 Z0.
(2D CONTOUR1)
N25 M9
N30 T2 M6
N35 S16000 M3
N40 G54
N45 M8
N50 G0 X-0.025 Y1.8177
N55 G43 Z0.6 H1
N60 G0 Z0.2
N65 G1 Z0.0394 F5.
N70 Z-0.9375
N75 Z0.2 F60.
N80 Z-0.9375 F5.
N85 Y1.7927
N90 Y1.7677 F60.
N95 G3 X0. Y1.7427 I0.025 J0.

0 Likes
Message 7 of 13

Richard.stubley
Autodesk
Autodesk

Have you got a example where it is not doing what you expect?

 

My guess is your heights are not set correctly for what you are trying to achieve.

 

I still think the correct solution to the problem is to not move the machine in any direction until your spindle is up to speed, its not good proactive to use the slow plunge move to let the spindle ramp up to speed.

 

If you do not have a mechanism of writing a handshake with the spindle encoder then I would recommend using a dwell in relation to the spindle speed.



Richard Stubley
Product Manager - Fusion Mechanical Design
Message 8 of 13

Anonymous
Not applicable

Quick look reveals crash in your file during simulation at start of first cut, raising vertical lead in value to .1  clears crash. With home built machine and potential errors in your file and / or post processor checking G-code in back plotting software may be a good idea until you can trust output to be on target.

 

2019-10-01 05_17_25-Window.png

2019-10-01 05_18_35-Window.png

0 Likes
Message 9 of 13

MJK_Performance
Advocate
Advocate

Your best bet here is to sketch a containment boundary and use that to drive your adaptive, that way your helix lead in will actually work, also depending on your router, you might want to ramp in that contour pass.

Capture.JPG 

0 Likes
Message 10 of 13

Anonymous
Not applicable

Well ...... , It's not my project, in my last post I downloaded model from original post and just ran simulation.

First picture shows tool crash, so I looked in operation details and raised vertical lead in value from .025 to .1, that cleared crash and tool completed the operation.

I did not look into refining his tool path, just edited lead in as you can see in screenshots below, I thought that was pretty obvious reason for concern regardless of spindle RPM'S.

 

 

2019-10-01 19_25_41-Autodesk Fusion 360.png2019-10-01 19_27_36-Autodesk Fusion 360.png

 


0 Likes
Message 11 of 13

Anonymous
Not applicable

@Anonymous wrote:

Hi

I checked and post it with fanuc and didn't find any issue. Please check the picture.

On the other hand if you face the problem then it means its a problem in post not Fusion.

 

plung.PNG


Looking at original post, the post title,......... then look at the original Fusion file and resulting G-code.

Problem is in operation settings for tool approach on first plunge. Vertical "lead in" was set to .025.

In above G-code, look at the lines N15 - N17, tool does exactly what was programmed in Fusion.

N15- tool rapids to Z.2,

N16 - tool rapids in position before given vertical lead in of .025

N17 - lead in move is executed at given feed rate,......... Z-.1325 minus Z-.1075 = -.025 ( .025 vertical lead in )

 

Problem goes away when you change vertical "lead in" value in Fusion operation to prevent rapid plunge into the stock, I used .1 and that cleared stock in rapid tool approach as shown in screenshots of my first reply to this thread.

 

Inkedplung_LI.jpg

0 Likes
Message 12 of 13

trober14
Explorer
Explorer

I guess my question is why doesn't fusion use the plunge feedrate when entering the material? The logical way for me to interpret the CAM settings would be as follows

 

N15 tool rapids to Z0.2

N16 Tool plunges to Z-.1075 at F5

N17 Tool performs the 0.025 lead in 

 

I know there are ways to make this work. This just seems like the intuitive way for someone to set this program up, yet it causes behavior that I don't see on any of my other programs. 

0 Likes
Message 13 of 13

Anonymous
Not applicable

I can't explain why Fusion does what it does the way it does it, but if I was to draw some conclusions from the way I have been using it then I can say that all strategies don't share universal options, features and refinements.

 

That being sad it is up to me to find optimal output from any tool path I chose, debug results first in Fusion simulation and then in NC editor with back plot feature because post processor is filter that can loose its marbles and I have to check final G-code before plowing into the stock.

I don't work with wood so damage is exponential if I skip those check points.

 

0 Likes