russ
New Member
Posts: 16
|
Post by russ on Aug 29, 2020 16:54:54 GMT -5
So I had this happen to me and I'm wondering if maybe any of you have had this happen before, or if Chad or any of the guys at Axiom can explain what may be going on.
It's no longer an issue, as I went into vCarve and re-drew the exact tool path and swapped out a 1/2 end mill for a 1/4 end mill to get the project done but nevertheless I'm curious in case it happens again. This by the way happened on a toolpath I have cut many times before without issues...
I'm running the project and about halfway into the tool path, the milling bit just stops. All X and Y axis movement just ceases (no Z axis movement as this is a pocket cut, all at the same depth). The router (no spindle) is still spinning, just no movement.
I look at the pendant controller and this is what I see:
ASSERT
../zwork/zarc3d;
nterpolateorg.c:
107
I was unable to pause or stop the progress using the pendant - not a single button would accept input. The only way to stop the spinning router was to hit the emergency stop button or shut the machine off using the green button and reboot altogether. I tried the project on a different flash drive thinking it was corrupted... nope, same issue on a new thumb drive.
Thanks!
Russ
|
|
|
Post by gerry on Aug 29, 2020 18:38:24 GMT -5
Static.... Try grounding your dust collector hose.
|
|
|
Post by Axiom Tool Group on Sept 14, 2020 10:40:33 GMT -5
We've experienced this ourselves....sometimes on new files, on multiple drives...other times on files that we had ran many times in the past.
In most cases, deleting the tool-path and recreating them completely helped elevate the errors.
Complete machine restart is always required, however, we have found that when the machine starts back up....after you finish the HOME operation, it will ask if you'd like to resume from the last point (due to power failure). Press OK and then it will show you the actual line of gcode that you were on...
If you use the X+/X- buttons, you can scroll forward in the list of gcode lines 3 lines specifically and restart from there.
This seems to get past the error and allow the file to resume without the need to go back and forth creating new toolpaths and resaving.
Unfortunately, we have not identified a cause for the creation of the glitch. But we generally recommend reformatting the drive once able too (you may need to complete the job first).
|
|
russ
New Member
Posts: 16
|
Post by russ on Sept 19, 2020 13:56:39 GMT -5
We've experienced this ourselves....sometimes on new files, on multiple drives...other times on files that we had ran many times in the past. In most cases, deleting the tool-path and recreating them completely helped elevate the errors. Complete machine restart is always required, however, we have found that when the machine starts back up....after you finish the HOME operation, it will ask if you'd like to resume from the last point (due to power failure). Press OK and then it will show you the actual line of gcode that you were on... If you use the X+/X- buttons, you can scroll forward in the list of gcode lines 3 lines specifically and restart from there. This seems to get past the error and allow the file to resume without the need to go back and forth creating new toolpaths and resaving. Unfortunately, we have not identified a cause for the creation of the glitch. But we generally recommend reformatting the drive once able too (you may need to complete the job first). This solved the problem... just moving one line ahead of where the g-code error was (where it stopped) and continuing on from there. Thanks Axiom
|
|