Diagnose stopped printer
Hello,
My printer stop printing and I'm looking for which reason. I looked a my repetier server logs here what I got.
What may cause this?
Thank you in advance!
My printer stop printing and I'm looking for which reason. I looked a my repetier server logs here what I got.
What may cause this?
2020-02-06 18:57:49: Websocket opened
2020-02-06 20:53:08: error: Reading serial conection failed: Accès refusé. Closing connection.
2020-02-06 20:53:08: Port closed for CR10
2020-02-06 20:53:08: C:\ffmpeg\bin\ffmpeg.exe -loglevel error -f concat -i input.txt -c:v libx264 -threads 2 -r 30 -pix_fmt yuv420p -profile:v baseline -level 3.0 -movflags +faststart -b:v 1000k -y video.mp4
2020-02-06 20:53:09: Connection closed: CR-10
2020-02-06 20:53:17:
2020-02-06 20:53:18: C:\ffmpeg\bin\ffmpeg.exe -loglevel error -f concat -i input.txt -c:v libx264 -filter_complex [0:v]transpose=1 -threads 2 -r 30 -pix_fmt yuv420p -profile:v baseline -level 3.0 -movflags +faststart -b:v 1000k -y video.mp4
2020-02-06 20:53:39: Connection started: CR-10
2020-02-06 20:53:39: Reset printer CR-10
2020-02-06 20:54:00: Websocket opened
2020-02-06 20:54:58: Starting print recover CCR10_boite Spacemouse
2020-02-06 20:54:58: start printjob CCR10_boite Spacemouse on printer CR-10
2020-02-06 20:54:58: Added timelapse 20200206T205458_CCR10_boite Spacemouse
2020-02-06 20:54:58: Added timelapse 20200206T205458_CCR10_boite Spacemouse_1
2020-02-06 20:59:23: Reset printer CR-10
2020-02-06 20:59:52: Closing websocket for missing ping
2020-02-06 21:06:06:
Thank you in advance!
Comments
is the key. As you see windows refused reading data from serial, so we closed the connection. That is an error happening outside repetier-server - so much is clear. It could be as simple as printer has reset for some reason. On raspberry pi I know it is also often back EMF from printer that causes linux to close the port for a short while. Don't know if windows would do the same. What exactly it is is not visible from this, just that windows stopped communication for unknown reason and apparently the problem was fixed a few seconds later. You might want to use a different usb cable or port. That sometime help. Also long usb cables have more often problems then short ones. Use a usb 2 port if available.