Cannot print anymore
-
If the extruder goes back and forth when it is trying to print, this could mean that you have sliced in relative coordinate mode (as recommended for RRF) but the printer is in absolute mode. Add M83 to your slicer start gcode.
One reason you may see this is that in RRF 1.17 and 1.17a, each input source has its own relative/absolute extruder setting. An unforseen consequence was that an M83 command in config.g to set relative extrusion was forgotten once config.g had completed. This is fixed in 1.17b.
-
How would that explain the fact that a file prints perfectly and the next time I load the same file, it doesn't?
Also, I am running 1.17b
But I certainly will add M83 to the startup code. Thanks -
How would that explain the fact that a file prints perfectly and the next time I load the same file, it doesn't?
Also, I am running 1.17b
But I certainly will add M83 to the startup code. ThanksIs that the next time you print the same file without restarting the Duet, or the next time after restarting the Duet?
Some slicers put M83 in the starting gcode themselves when you specify relative extrusion.
-
Ah, OK.
I will test it out tomorrow and let you know.
Thanks -
Funny: Exactly the same problem, today at about the same time!
I was using version 1.17 downloaded on January 2 on a fresh DuetWifi.
Many successfull prints since, before suddenly the extruder went crazy at the beginning of an print (endless retracted-unretracted-retracted), then the DuetWebControl said "Communication error" and then died completely. Can not make it alive since: the page does not respond.No power problems, no abnormal temperature. The red light next to the SD card is always on. I do not remember if it's normal or not …
I tried to switch to 1.17b, changing the bin files in the / sys directory of the SD card. No luck for now.
P.S.
I also can not access DuetWifi via USB.The Windows drivers for the USB port that I downloaded (duet.inf and duetinf.cat) no longer work normally. Their re-installation results in the installation on the COM7 port of a component named "Bossa Program Port", and not "Duet 3DPrinter ...".
Examination of the "Bossa Program Port" shows that this is some Arduino stuff. What is that doing there? In any case, nothing good ...
As a result, I can not send any code to DuetWifi.
Any idea?
-
I tried to switch to 1.17b, changing the bin files in the / sys directory of the SD card. No luck at the moment.
The firmware sits in the flash memory of the controller, changing it on the SD card without also telling it to Flash the controller does nothing. I don't have the bin file in my sys folder or SD card as it does nothing once flashed.
Jeff
-
Funny: Exactly the same problem, today at about the same time!
I was using version 1.17 downloaded on January 2 on a fresh DuetWifi.
Many successfull prints since, before suddenly the extruder went crazy at the beginning of an print (endless retracted-unretracted-retracted), then the DuetWebControl said "Communication error" and then died completely. Can not make it alive since: the page does not respond.No power problems, no abnormal temperature. The red light next to the SD card is always on. I do not remember if it's normal or not …
I tried to switch to 1.17b, changing the bin files in the / sys directory of the SD card. No luck for now.
P.S.
I also can not access DuetWifi via USB.The Windows drivers for the USB port that I downloaded (duet.inf and duetinf.cat) no longer work normally. Their re-installation results in the installation on the COM7 port of a component named "Bossa Program Port", and not "Duet 3DPrinter ...".
Examination of the "Bossa Program Port" shows that this is some Arduino stuff. What is that doing there? In any case, nothing good ...
As a result, I can not send any code to DuetWifi.
Any idea?
If you are now seeing a bossa programing port it means you have erased the firmware you need to visit the emergency recovery section of the Wiki to get the info to recover your board.
-
It is possible that I pressed the "Erase" button by believing to press "Reset", during the abnormal behavior of the extruder.
According to the documentation, this could corrupt or erase the firmware. Does this make sense?
In this case, I have to apply "Backup procedure #3" specified in the documentation, right?
P.S. Thanks Dougal1957 ! I will do that.
I find it strange that it is as easy to erase the firmware … -
To me it feels like a software problem. It is not just the extruder stepper going crazy, the web server crashes as well.
It would be nice to be able to have some sort of error logging, so we can trace what is happening.
I would be more than willing to run a debugging version, if it would help to figure this out. -
In my case, the web server probably crashed as a consequence of the fact that I probably pressed the "Erase" button. We do not have proof that he would have crashed if not …
-
After applying Backup # 3, everything is now normal. I can print from Wifi and from USB.
It remains to understand the abnormal behavior of the extruder motor, but the key is that everything works again.
Thank you to all of you !
-
After applying Backup # 3, everything is now normal. I can print from Wifi and from USB.
It remains to understand the abnormal behavior of the extruder motor, but the key is that everything works again.
Thank you to all of you !
The reason for the extruder problem is probably as I explained a few posts back here https://www.duet3d.com/forum/thread.php?pid=7011#p7011.
-
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
