Printers stopped for few sec, console message included
Hello,
I'm using Repetier Server on two Raspberry PI 4, server A runs 4 machines flawless, server B has some issues with 3 machines (all Ender 3)
Here is the console error in the moment when all 3 machines stopped: https://ibb.co/4mwPSK0
Could you help how to solve the issue?
Thank you so much!
I'm using Repetier Server on two Raspberry PI 4, server A runs 4 machines flawless, server B has some issues with 3 machines (all Ender 3)
Here is the console error in the moment when all 3 machines stopped: https://ibb.co/4mwPSK0
Could you help how to solve the issue?
Thank you so much!
Comments
What that happens you should check if you can reload website and if all data appears or not. If it does not appear and UI seems to hang it might be a dead lock. If it works normally and if unplugging usb and reconnecting helps it is more likely a driver hanging.
Does this happen frequently? Any advaced features enabled?
All printers stopped, then continue around 20-30sec later normally. Certainly, it is still not good enough as they leave faults on the print where stopped.
The printers' icons switch to orange bars from the green connected one. When all complete and I unplug and plug in the cables, all switch back to green connected status.
I'm starting around 6-8hours jobs and it is happens generally around 1-2 times in this interval.
What does it mean "MQTT"? I'm using Repetier-Server Monitor and rarely the browser based local server page.
Is there a chance it is caused by a bad and/or long cable?
This is the current config for all 3 machines (certainly the Device port is different): https://ibb.co/gwD5d7r
The input buffer was 63byte before, now I tried with 127byte, but the problem is the same.
I don't think any advanced feature is enabled.
Thanks!
Still weird my other server doesn't has this issue, so I'm not sure it will help.
Will be back soon.
Reduced the timeout to 3sec as you suggested and it seems to be the period while the machines stopping is better, sometimes I even don't notice it was a break. Also the prints better, I can't see any issues from the stops.
However, I still have the communication error, after each print I have to unplug and plug in the cables to all printers (green online sign switch to orange connected)
Furthermore since I updated the server to 1.4.2, my Repetier-Server Monitor no longer shows the progress of the prints, it is always displaying 0% and the bar also doesn't go up. I'm not sure it is related with the communication error or something else. This is a new issue that come with the 1.4.2 version so probably there is no relation.
One other thing, when I send a print job from Repetier-Server Monitor, all jobs placed in the Print Queue on the browser based Repetier screen of the specific printer. Sometimes there are hundreds of jobs listed there. It is not a big deal, I can delete them, just I thought it is worth to mention.
Could you help with the communication error and the new progress bar issue, please?
Just uploaded one of the printer's server log here: https://filetransfer.io/data-package/LNX3KZtf#link
Thank you!
Seems to be the green online status turn to orange when communication timeout happens. Does it related with the cable or something else?
You should install 1.4.3 coming in the next minutes. There we add syslog messages from usb around the disconnect time so you can easily see what linux says about the disconnects.
You can also check the bolt icon menu. There you see if linux detected undervoltage since bootup. Especially after such a disconnect it might allow distinguishing power issue from EMI problems on usb from printers.
Thunder icon shows everything works fine: https://ibb.co/37vFL7S
Just updating to 1.4.3 and will come back with the log later. Thanks a lot!
Sep 21 14:49:34 Repetier-Server kernel: [27513.884540] usb usb1-port1: disabled by hub (EMI?), re-enabling...
Telling that USB hub disconnected device.
I didn't see any similar notice. Now I'm using the latest version, still there is some kind of communication error.
Could you check the logs, please?
Find it here: https://files.fm/u/dxxxh366v
Thank you!
By the way, all other issues fixed with the new release only the green status switch to orange (communication error) problem persist.
Linux closed port due to driver stopping with broken pipe error. If you google
"ch341-uart usb_serial_generic_read_bulk_callback urb stopped 32"
you find lots of users with same problem and several issues. Some seem to get this mor eoften if 5v line is taped on usb cable. Others say it's overload on usb if you have a webcam (probably with high resolution/FPS) making driver bail out. In the end something did go wrong in printer<->pi communication and driver disconnected. What helps to prevent this is something you must test, there seems to be no one reason.
What you can do and probably already have done is select the automatic contntinue of print after reconnect. This can not prevent driver failure but can continue in most cases so print is not ruined.
Have a great day! Thanks again for your professional support!
ch341 uart usb_serial_generic_read_bulk_callback urb stopped "-32"
to get more ideas on it. I got 990 hits on it.
I'll also check the "housing had contact to usb ground" thing, thank you!