First cut success - with questions!
-
@joergs5 Sorry, I edited the question as you answered...
I've now placed the spindle at the Work XYZ (without the cutter installed!) so should I set Work XYZ then run M114?
-
M114 before setting Work XYZ...
X:37.000 Y:204.000 Z:85.000 E:0.000 Count 14800 81600 34000 Machine 37.000 204.000 85.000 Bed comp 0.000Some more information:
Since installing the spoil board, my Z height has reduced to 75mm, but I haven't changed it in the config.g file yet.M114 after setting Work XYZ...
X:0.000 Y:0.000 Z:0.000 E:0.000 Count 14800 81600 34000 Machine 37.000 204.000 85.000 Bed comp 0.000 -
@nightowl999 said in First cut success - with questions!:
M114 after setting Work XYZ...
X:0.000 Y:0.000 Z:0.000 E:0.000 Count 14800 81600 34000 MachInteresting! I was not sure, whether it will be corrected or not.
So work change (did you make it by G54?) doesn't change the count values.
I've learned here something also!
XYZ are the values from the work XYZ view, and the Machine coordinates behind are the true original coordinates. -
@joergs5
I just clicked the Work XYZ button on the Dashboard. I don't know anything about G54?? -
@joergs5
The workzero.g file has the following lines:; workzero.g
; G90 ; set to absolute positioning
G53 G1 Z{move.axes[2].max} F1500 ; raise the Z to the highest position
G1 X0 Y0 F2400 ; go directly above the work zero position
G1 Z0 F2400 ; go to the work Z zero position -
@nightowl999 said in First cut success - with questions!:
@joergs5
I just clicked the Work XYZ button on the Dashboard. I don't know anything about G54??I think it's not so important now, we want to find the reason for the error message.
One possible reason could be that the M208 limits take the XYZ values. But let's verify by you searching for the first error G0/G1. -
@joergs5 OK. Shall I load and run the file?
Actually, what I did was upload the gcode file, then right-clicked it and simulated the project, with these results:
21/05/2022, 19:54:21 File 0:/gcodes/102 Avalon Pocket_1-102 Avalon Pocket.gcode will print in 0h 14m plus heating time
21/05/2022, 19:54:19 M37 P"0:/gcodes/102 Avalon Pocket_1-102 Avalon Pocket.gcode"
Simulating print of file 0:/gcodes/102 Avalon Pocket_1-102 Avalon Pocket.gcode -
@nightowl999 said in First cut success - with questions!:
G53
G53 is to clear coordinate changes and not using any machine coordinates, so I would not run it.
https://duet3d.dozuki.com/Wiki/Gcode#Section_G53_Use_machine_coordinatesThere should be G54 to G59 somewhere else, probably in your Cut2D software.
The problem now is that I don't know your software and which commands are run. I can only help to find out the reason why there is the G0/G1 error message.
-
@nightowl999 said in First cut success - with questions!:
and simulated the proj
unfortunately it didn't find an error line, so it didn't help.
The simulation mode may have some shortcuts, e.g. not checking limits.... -
Well, starting the file seemed to work, too.
I'm not sure what's going on here, but I'm also getting random disconnects
-
@nightowl999 said in First cut success - with questions!:
also getting random disconnects
I am innocent
-
What I'll do now I know this file runs is to let it finish, s
hut everything down and use the same Work XYZ coordinates again tomorrow, but with the other file, and see how that goes. -
-
@nightowl999 when you get a G0/G1 error, you know now how to analyze it. I expect a conflict between what the software wants to make and your M208 limits.
I checked Cut2D, there was one similar problem in
https://forum.vectric.com/viewtopic.php?t=32804
but I am not sure whether it can be the reason in your case. -
Thank you, @joergs5
I'll check that forum out tomorrow, but that thread is exactly the issue here - if not the resolution!
Have a good evening and thank you for your help
-
@nightowl999 you're welcome, and I wish you success tomorrow!
-
Maybe I've got to the bottom of this...
I've simulated several files from a specific Work XYZ, which is X27 Y198 and Z82. The maximum axis limits are X535 Y787 Z100.
I need to look at the Vectric software to see why, but I've compared a few gcode files produced by the Vectric software, and I've found this:
In both working and non-working files, there are four consistent lines of code at the start (excluding the headers) as follows:
G17 (Sets the XY plane for arc moves)
G21 (Sets the units to mm)
G90 (Sets to absolute positioning)Then the files differ.
In the files that can be simulated, this is the next line:
G0Z6.350 (Which moves the Z axes to a safe height, I guess)
...but in the files that can't be simulated, this is the next line:
G0Z20.320
I think this is the problem because if the Z Axis is already at 82mm when the Work XYZ is set, then trying to move the Z axis another 20.320mm will exceed the available Z axis movement of 100mm (82 + 20.32 = 102.32mm).
Does anyone agree, or am I talking out of my hat?
Thanks
-
@nightowl999 said in First cut success - with questions!:
I think this is the problem because if the Z Axis is already at 82mm when the Work XYZ is set, then trying to move the Z axis another 20.320mm will exceed the available Z axis movement of 100mm (82 + 20.32 = 102.32mm).
Does anyone agree, or am I talking out of my hat?Yes, I think that is exactly what is happening.
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
Thank you, @dc42.
I was getting a bit tied up with this last night, but in the cold light of day - and after a good nights sleep! - a clear look at the problem certainly helps.
My thanks to @JoergS5 for pointing me towards the Z height, and everyone else who joined me on this journey.
Now all I have to do is find out why and prevent it from ruining my day again!
-
This post is deleted!
