Cannot print anymore
-
Things are getting worse. Adding M83 to the startup code messed up my prints.
Removing it made things even worse. Now I cannot print at all any more, even when the file is accepted.
It prints a little while and then the extruder shoots back to its previous positions. Net result, no filament coming out.I am switching back to 1.15 for now, but keeping the micro sd card intact, so I can still test if and when needed.
-
Lykle
Can you give a bit more information, what do you mean by "shoots back to previous positions" ( how much is retracted?). What slicer are you using? Does the error start occuring at the same point in the gcode file?
Regarding M82/M83 these obviously need to match what your slicer is set to. Can you share the first 20 or 30 lines of the gcode file you are using.
-
Things are getting worse. Adding M83 to the startup code messed up my prints.
Removing it made things even worse. Now I cannot print at all any more, even when the file is accepted.
It prints a little while and then the extruder shoots back to its previous positions. Net result, no filament coming out.I am switching back to 1.15 for now, but keeping the micro sd card intact, so I can still test if and when needed.
1. Are you slicing with relative or absolute extrusion?
2. Is your slicer putting any M82 or M83 commands near the start of the gcode file it generates?
-
Oh I have a different issue now, I cannot upload a file. I changed back to 1.15 using the 1.15 sd card I had, and the M997 commands
Printing a files stored on my SD card works, but uploading doesn't gives an error after the upload has completed.
I will switch back to the 1.17b again and see if that problem has been removed, then I can start looking at the retractions.I am using S3D and the Relative extrusion distances was not set. I have now set it. And have included M83 to my startup code.
Correct?Edit: OK, back in 1.17b and can upload files again.
-
Phew, that is a relief!
Printing again. I checked everything and switched on Relative extrusion distances.
Uploaded the file and started printing.
As I am trying out a new print surface I had to cancel and restart the print all the time. That worked like a charm, no more issues with the extruder stepper.Now, why this suddenly started to happen I have no idea. Only thing I can think of is that I have been switching factory files a lot lately. (correct, I have no idea!)
Thanks David and Tony for your help.
-
That is why I stop upgrading the firmware now unless I have an issue that the revised firmware fixes. If it already works, I stop upgrading just to get to the latest and greatest bugs.
-
Shadow, while being at the cutting edge is not always a good idea I agree, in this particular case it was not an issue in 1.17b but a absolute vs relative extrusion mismatch
-
That is why I stop upgrading the firmware now unless I have an issue that the revised firmware fixes. If it already works, I stop upgrading just to get to the latest and greatest bugs.
Haaa, I've already had to unsolder and soler in a new processor, I'll be the guinea pig. I'm also a software engineer by trade so I expect bugs. If everything works perfect the product life cycle was Way too long and should have been shelved long ago.
Jeff
-
Sorry, it is happening again.
This time after I completed a print. Redid something in the model, reprinted it and boom, server crashed and extruder stepper going back and forth.
I have M83 in my start file, in fact it is in there twice I saw. So retried with only 1, no difference.I had to switch off the printer and leave it for 10 mins before it would print normally again. Switching it off, waiting 10 sec's and switching it on again, did not solve it.
-
@Lykle,
I notice that way back near the top of the first page of this thread, you gave your start gcode which has this line
M80 ; lights on
What is that all about? A quick look at the wiki tells me that M80 is used to turn an ATX power supply on from standby. Have you got some sort of lights that run from a separate power supply? Could this line be screwing things up for you? Can you comment it out and see if that fixes the issue?
Ian
-
Good point.
-
Lykle please send a link to your gcode, and config.g cheers
Tony
-
Hi Tony,
Here you go.
https://www.dropbox.com/s/53k0jzpjyzs4qxa/3D%20Printing.rar?dl=0 -
@Lykle,
I notice that way back near the top of the first page of this thread, you gave your start gcode which has this line
M80 ; lights on
What is that all about? A quick look at the wiki tells me that M80 is used to turn an ATX power supply on from standby. Have you got some sort of lights that run from a separate power supply? Could this line be screwing things up for you? Can you comment it out and see if that fixes the issue?
Ian
I think the "M80; lights on" goes back to Lykle's BI V2.5 printer default settings before he upgraded to DuetWifi. The BI printers running the Rumba board used the ATX on/off commands (M80/M81) to turn on and off the LED lights. Repetier had a nice button on the screen, so they hijacked that command as the LED switch.
-
Thanks lykle
From the point of view of the configuration the config.g and the start gcode both set the printer to relative extrusion. the file is also sliced for relative extrusion so thats all good.
I don't think this is the issue but I noticed that your config.g is for a delta printer but you have a different maz speed for your Z axis than your X/Y these three axis should all be the same.
You have a M501 at the end of your config.g - whats in your config over ride gcode file?
-
Thank for the speed comment. I will make them identical. Never gave it any thought,
I notice that I can print normally now, but I have to do a Home before I can print, otherwise the extruder starts misbehaving. This is not a real problem, but it seems to be new. I don't remember eve having this issue, but I am back at 1.15b so I must have just happen to miss it during that time.
Anyway, thanks for the help.
