-
I don't see anything in that GCode that explains the problem.
Please can you:
-
Send M450 and confirm that it reports that the machine is in CNC mode.
-
Run that file again. When it stops, read off the XYZ coordinates from the web interface. Also send M122 from the web interface. With luck the GCodes section of the report will say what command is being executed.
-
-
Hi David. I know this is a very elementary question but how do I send the codes you mention? Do I need to link with USB and use the YAT software?
-
You can send them from the GCode Console page of Duet Web Control. See the "Send GCode" box in the screenshot you posted.
-
Thanks David will let you know
-
David when I send M450 I get "Printer Mode FFF". I assume problem is in here somewhere. Do I need to change something?
-
M122 File attached at point of stopping0_1548680231248_console.txt
-
@trev133 said in Strange issue when running programme on CNC:
David when I send M450 I get "Printer Mode FFF". I assume problem is in here somewhere. Do I need to change something?
Yes, you need to use M453 in config.g to put it in CNC mode. See https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M453_Select_CNC_Printer_Mode. Without that, G0 commands will execute at the same speed as G1 commands instead of rapidly.
Note, if the M453 command declares that a heater or fan output is to be used for spindle control, you must disable the corresponding heater or fan before the M453 command, using M307 or M106 as appropriate.
-
Thanks David. Will let you know
-
Hi David
Put M453 into config.g but it stopped any file from running. (Tried several files that had previously run OK) Got error message as attached. Had work co-ordinated established as before so i’m not sure what outside machine limits means. Removed the M453 and all was OK again. Sending M450 code I was able to confirm that machine was in CNC mode.
Any Thoughts
Trev
-
The problem is the "outside machine limits" message. In CNC mode, a movement command that commands movement outside the limits you have set in config.g will terminate the job, for safety reasons. So you need to identify that command in the GCode file, for example by executing lines from the file one at a time.
