[Release 3.4.3] - New G0/G1 Error...
-
A few days ago I ran a project on my CNC machine, quite successfully and without any issues. The firmware version was 3.4.2
After upgrading to version 3.4.3 today I simulated a different project, but when I ran the simulation I got G0/G1 error, and wonder if this is related to the upgrade.
I had this error before, but was related to the safe height being excessive, but it's not the reason this time, as the safe height is the same.
I've tried with a different g-code file, but I get the same error.
The only thing I've done since the last project is upgrade the firmware to v3.4.3, and I couldn't see anything in the release notes that would cause this.
I'm going to try the project that did work and, if that presents the same issue, I'll revert back to v3.4.2 and try again.
Thanks
First Update: I really doubt this is the issue, but I've checked the "safe" heights in the design software, Vectric VCarve Desktop, v11.016. The original design was produced in Vectric Cut2D Desktop. Here are the settings:
Cut2D:
VCarve:
Second Update:
I reverted back to 3.4.2 and ran the project from last week, but I get the same error. As there was no difference I reinstalled 3.4.3 and tried the file again, with no luckI tested the file in NC Viewer, and it viewed/ran as expected. I'm also going to send it to a friend to try some faultfinding, too.
To reiterate: I made no changes to the project gcode or config.g files since the successful cut, just upgraded the firmware from 3.4.2 to 3.4.3
I've produced a text file showing the errors when trying to simulate and run the files, and also the M122 file, which I've added to the post
[Deleted]
I've also uploaded one of the gcode files:
[Deleted]
I'm at my wits end with this, but will start from scratch with a new, simple project, to see if that helps.
-
Error: G0/G1: target position outside machine limits
Tt looks like from your report that this happens immediately. What is the maximum limits on your X/Y/Z with tool 1 selected? It strikes me that you have the file named "t2..." when the gcode in it switches to T1. could it be the tool offsets.
The way i would trouble shoot this is send the gcode commands in the file one at a time from the console to find which one is commanding the move outseide of the limits.
-
@t3p3tony
Thank you. It's quite possible I've missed something really simple/basic, which I'll check out in a few minutes, but I'll bear your thoughts in mind.I'll let the forum know how I get on...
-
It was me, mostly.
For some reason, changing from Vectric Cut2D, where the safe height is 5.09mm above the stock, to VCarve, also changed the safe height to 5.00mm. Reverting to the Cut2D values resolved the problem - but I'll ask them why this happened.
The reason the 'old' file reported the same error is because normally I use the front LH corner for my projects, but didn't for this one. I used the middle of the stock. So, when I ran the project a second time, with the milling motor set to the front LH corner, it correctly pointed out my schoolboy error.
How embarrassing!