Announcements
Autodesk Community will be read-only between April 26 and April 27 as we complete essential maintenance. We will remove this banner once completed. Thanks for your understanding

Drilling: "Cannot do g1 with zero feed rate" Mach3

Anonymous

Drilling: "Cannot do g1 with zero feed rate" Mach3

Anonymous
Not applicable

Dear technical support, I encountered a problem after the latest update of Fusion 360 (2.0.9009)

When I post-process the drill file, Mach 3 crashes for this reason: "Cannot do g1 with zero feed rate".

Analyzing two different drill files (before and after the update of Fusion), it can be seen that the line "G1 F0" is introduced which causes the problem.

 

Example of Drill file BEFORE Fusion update:

 

(T2 D=4. CR=0. TAPER=118DEG - ZMIN=-7.202 - FORATURA)
G90 G94 G91.1 G40 G49 G17
G21
G28 G91 Z0.
G90

(FORATURA1)
M5
T2 M6
(PUNTATRAPANO4MM)
S18000 M3
G54
G0 X29. Y105.
G43 Z15. H2
Z5.
G98 G83 X29. Y105. Z-7.202 R5. Q1. F1000.
Y38.
X126.
Y105.
G80
Z15.

G28 G91 Z0.
G90
G28 G91 X0. Y0.
G90
M30

 

Example of Drill file AFTER Fusion update:

(T2 D=4. CR=0. TAPER=118DEG - ZMIN=-7.202 - FORATURA)
G90 G94 G91.1 G40 G49 G17
G21
(WHEN USING FUSION 360 FOR PERSONAL USE, THE FEEDRATE OF RAPID MOVES IS REDUCED TO MATCH THE FEEDRATE OF CUTTING MOVES, WHICH CAN INCREASE MACHINING TIME. UNRESTRICTED RAPID MOVES ARE AVAILABLE WITH A FUSION 360 SUBSCRIPTION.)
G28 G91 Z0.
G90

(FORATURA1)
M5
T2 M6
(PUNTATRAPANO4MM)
S18000 M3
G54
G0 A0.
G0 X215.561 Y76.
G43 Z15. H2
G1 F0.
G0 Z5.
G98 G83 X215.561 Y76. Z-7.202 R5. Q1. F1000.
X158.561 Y82.
Y15.
X61.561
X17.877 Y53.11
X61.561 Y82.
G80
G1 Z15. F0.

G28 G91 Z0.
G90
G28 G91 X0. Y0.
G90
M30

 

How can this problem be solved?

 

Thank you,
Rocco

0 Likes
Reply
Accepted solutions (1)
748 Views
2 Replies
Replies (2)

seth.madore
Community Manager
Community Manager

Known bug, sorry about that. We're working on getting a fix in place for this. For now, just manually remove the F0. line


Seth Madore
Customer Advocacy Manager - Manufacturing


0 Likes

Anonymous
Not applicable
Accepted solution

In the new version the bug has been fixed.

0 Likes