Hello Guest it is December 02, 2024, 11:56:30 AM

Author Topic: CNC Router will always fail the first toolpath  (Read 13888 times)

0 Members and 1 Guest are viewing this topic.

CNC Router will always fail the first toolpath
« on: September 13, 2021, 01:39:35 PM »
Hi there, I've recently bought a  Cnc Router to use it in my workshop (Woodworker & Guitar Maker). It's been working just fine until recently. I have a problem where the cutter will dig straight down as soon as it starts (the depth is always the same as the first pass of the pocket it's supposed to cut). When I add a drilling toolpath to a random place where it doesn't matter (waste) the problem seems to go away however it'll fail to run that drilling toolpath to the right location, it runs the drilling toolpath on the corner of the workpiece (where it dives down when it's not supposed to), When I say the corner of the workpiece I meant where I manually set X0 Y0 Z0. I'd like the machine to not ruin the pieces I'm tring to cut without adding unnecessary drilling toolpaths at the start of every job obviously. The way I explained thing probably show how much of a newbie I am. I use Aspire and Mach3, as I mentioned I have successfully ran more than 50 jobs before this started happening. I tried adjusting the Safe Z and Homing/Limits setting (without having any real knowledge on how they work I might add).  I'd appreciate any help at this point, Thank you for reading.

Cheers,

Mehmet Çınar

Sycamore Guitarworks
Unchained Workshop

Offline Graham Waterworth

*
  • *
  •  2,742 2,742
  • Yorkshire Dales, England
Re: CNC Router will always fail the first toolpath
« Reply #1 on: September 13, 2021, 05:09:21 PM »
A sample of your g-code would help diagnose the issue.
Without engineers the world stops
Re: CNC Router will always fail the first toolpath
« Reply #2 on: September 13, 2021, 07:46:48 PM »
Thanks for the reply, here is the first few lines of the g code where it fails at the start, when it's diving into the material directly instead of going above the material to the first pocket (this is the first G-Code I generated without trying to trick it with an unnecessary drilling toolpath at the start).
T1M6
G17
G0Z35.000
G0X0.000Y0.000S15000M3
G0X56.770Y35.867Z35.000
G0Z5.000
G1Z-4.200F900.0
G1X56.633Y35.730F1800.0
X56.388Y35.581
X56.106Y35.509
X55.894

Offline Graham Waterworth

*
  • *
  •  2,742 2,742
  • Yorkshire Dales, England
Re: CNC Router will always fail the first toolpath
« Reply #3 on: September 14, 2021, 06:09:51 PM »
For a start you have no G90 to tell it its working absolute and no G43 to take offsets into account.

T1M6
G17
G0 G90 G43 Z35.000
G0X0.000Y0.000S15000M3
G0X56.770Y35.867Z35.000
G0Z5.000
G1Z-4.200F900.0
G1X56.633Y35.730F1800.0
X56.388Y35.581
X56.106Y35.509
X55.894

But maybe you programmed it in incremental which makes things very awkward.
Without engineers the world stops
Re: CNC Router will always fail the first toolpath
« Reply #4 on: September 14, 2021, 06:18:09 PM »
Well as I said I'm a newbie so I don't really get what you mean but in general logic configuration distance mode is set to absolute  and lJ to inc. if that's what you mean, sorry if I this has nothing to do with what you said :/

Offline Graham Waterworth

*
  • *
  •  2,742 2,742
  • Yorkshire Dales, England
Re: CNC Router will always fail the first toolpath
« Reply #5 on: September 14, 2021, 07:13:46 PM »
Add the G90 and the G43 as shown and see if it fixes your problem.

How did you generate the code?
Without engineers the world stops
Re: CNC Router will always fail the first toolpath
« Reply #6 on: September 14, 2021, 07:25:03 PM »
I will try doing this first thing in the morning and post an update, thanks for helping me out.
I use aspire to generate g codes, It's been working just fine. If the problem goes away once I add G90 and G43 on the g code should I do the same for all the jobs from now on or is there a way to make mach3 or aspire to add that automatically.
Cheers!
Re: CNC Router will always fail the first toolpath
« Reply #7 on: September 15, 2021, 05:23:49 AM »
Problem Solved: I was using the g code (.tap) post-processor, I switched to Mach2/3 arcs post-processor and everything runs without any issues.