Duet 3D goes in pause state without any apparent reason
-
Do you have an M911 command in your config.g?
-
No, Neither in the config files (which includes config.g) neither in the gcode file to printing.
-
It's out this conversation but is it compulsory to connect the "Earth Bonding for shielded cable" somewhere? I have a plastic box so I decided to leave it unconnected….
-
Yes! Connect one end of the shield to ground. If your Duet is mounted in a grounded metal enclosure to reduce EMI then connect it to that enclosure. Otherwise, connect it to Duet ground.
-
Error status 8 does mean something, but I'm out of the office and replying on a tablet, so I can't look it up right now. Feel free to remind me tomorrow.
Causes of a print pausing include:
- M25 received from any input channel
- M226 seen in the GCode file
- Filament sensor reported a problem
- Heater fault
- VIN voltage dropped below the threshold set by M911
The last 3 should all cause a popup in DWC or a message in the GCode Console page.
-
Hello,
Thanks for your replies.I checked and my gcode is free of M25 and M226 commands, moreover DWC never popped out a message error different from the one I've already reported.
Unfortunately I cannot wire the shield to ground until tomorrow: In my toolbox I don't have a so small faston so I have to wait tomorrow for the shop to be open. Hope is will not be the causes of the issue.
@dc42 This is also as reminder for you for error status 8 meaning.
-
Error code 8 means "output stack overflow". Are you using DWC on more than one device to access the Duet, e.g. PC and smartphone?
Output stack overflow shouldn't cause pausing, but it is likely to result in some messages being lost.
-
Thanks for your reply.
Yes, I usually leave a window always open on the PC and then check the status from PC or Smartphone: i.e. nearest one.Today I decided to disable the web server and use only ftp and USB console; I also connected the Ethernet's shield to the ground ( I finally managed the missing of the faston but I'm a little bit ashamed of the style)
Now I'm going to send another print.. I'll report you what will happen.
Have a great day!
-
The output stack overflow is probably caused by the PC or smartphone going to sleep with the connection still open. There is a known bug when this happens and you have more than one device using the web interface, which is close to the top of my priority list for fixing. Meanwhile, pressing the Disconnect button before the device goes to sleep avoids the issue.
-
ok.
Alter a few experiments, I think that the problem could be caused by bad configuration of filament run out trigger for E0.
I reviewed my configuration but by now I cannot see anything wrong… even if there there should be.
Here my configuration files:
https://drive.google.com/drive/u/0/folders/1fVkJjVDBfn9F5m76dgao4u8epiJoJ4-G
-
I hope I found the problem that generated the malfunction: the filament run-out switch which wasn't positioned correctly; this causes a fast random switching and a false signaling on E0 connector.
Every time this was happen my duet wrote on USB console [c]Resume-after-power-fail state saved <cr><lr>Printing paused[/c]
In my opinion not a very appropriate description since it drove me in the wrong hypothesis of a power failure.Obviously in the trigger there was a[c]M117 No Filament!!![/c] but I wasn't able to see it because this command write only on web interface (that was malfunctioning due to a firmware bug) and at display that I don't have.
My solution:
I moved the switch closer to the filament in order to avoid fast switching (so the false signaling on E0). Than I added to the trigger code the following line in order to receive the message also on USB console. [c]M118 S"Hello Duet"[/c]My 2cent:
@dc42 I strongly suggest to replace the [c]Resume-after-power-fail state saved <cr><lr>Printing paused[/c] message with something that can't be associated so easily to a real power issue.PS: I'm using this Filament Detector: https://www.thingiverse.com/thing:2629228</lr></cr></lr></cr>
