Page MenuHomeAleph Objects Inc

Losing connection to printer after connected
Closed, ResolvedPublic

Description

Testing 2.6.25 on Windows 10 on Taz Mini - after connecting to printer, tested X, Y & Z movements. Made one movement and printer becomes disconnected from PC. Pressed Connect and was able to reconnect, but after making one more movement test, I lost connection again.
Behavior seems erratic. Click to move extruder and you get one movement, click on the same movement or another axis movement, and it may or may not movement and eventually no movement at all and suddenly get a message that "connection closed".

Event Timeline

Yahuba created this task.Sep 5 2017, 8:03 AM
Yahuba updated the task description. (Show Details)Sep 5 2017, 8:07 AM
Steven assigned this task to tranter.Sep 7 2017, 8:11 AM

@Yahuba Can you clarify if this was with a LulzBot Mini or a TAZ 6 printer?

Yahuba added a comment.Sep 7 2017, 9:29 AM

I experienced this with the Taz Mini

@Yahuba There is no such model as a Taz Mini. There is the LulzBot Mini and TAZ 6.

Sorry about that, I am terrible with names. I meant LulzBot Mini

@Yahuba See issue T1160. I noticed that issue while looking at this bug. I don't think it is the same issue, but it could be. Take a look and let me know what you think.

This is the same or similar issue I am having as well. In fact, I was doing pretty much the same thing, when I test the movements; I set it to 10mm because the movements are clearer to see vs 1mm. I wasn't able to get past more than one movement for each axis. The whole thing is a bit erratic and sometimes you can get more than one movement to happen and other times not.

I think there are two bugs here. T1160 should go away if you click on Home All. I have been able to see the printer disconnect a few times as you reported here.

If I keep hitting the move buttons I can sometimes get it to disconnect and report "Connection closed".
I haven't been able to reproduce this on Linux, only Windows.
It might be serial driver related and hard to track down.

I've been able to reproduce it on two Windows computers. I see this in the log file:

7-09-07 15:52:44,656 - DEBUG - USBPrinting.USBPrinterOutputDevice._connect_thread_function [427]: Attempting to connect to None
2017-09-07 15:52:45,977 - DEBUG - USBPrinting.USBPrinterOutputDevice._connect_thread_function [452]: Attempting to connect to printer with serial COM3 on baud rate 115200
2017-09-07 15:52:46,793 - DEBUG - AutoSave.AutoSave._onTimeout [48]: Autosaving preferences, instances and profiles
2017-09-07 15:52:47,712 - DEBUG - USBPrinting.USBPrinterOutputDevice._connect_thread_function [477]: Correct response for connection
2017-09-07 15:52:47,740 - INFO - USBPrinting.USBPrinterOutputDevice._listen [673]: Printer connection listen thread started for COM3
2017-09-07 15:52:47,746 - INFO - USBPrinting.USBPrinterOutputDevice._connect_thread_function [482]: Established printer connection on port COM3
2017-09-07 15:52:48,494 - WARNING - USBPrinting.USBPrinterOutputDevice._sendCommand [597]: Serial timeout while writing to serial port, trying again.
2017-09-07 15:53:10,669 - WARNING - USBPrinting.USBPrinterOutputDevice._sendCommand [597]: Serial timeout while writing to serial port, trying again.
2017-09-07 15:53:10,671 - WARNING - USBPrinting.USBPrinterOutputDevice._sendCommand [597]: Serial timeout while writing to serial port, trying again.
2017-09-07 15:53:15,786 - WARNING - USBPrinting.USBPrinterOutputDevice._sendCommand [597]: Serial timeout while writing to serial port, trying again.
2017-09-07 15:53:32,489 - WARNING - USBPrinting.USBPrinterOutputDevice._sendCommand [597]: Serial timeout while writing to serial port, trying again.
2017-09-07 15:53:47,664 - WARNING - USBPrinting.USBPrinterOutputDevice._sendCommand [597]: Serial timeout while writing to serial port, trying again.
2017-09-07 15:53:58,699 - WARNING - USBPrinting.USBPrinterOutputDevice._sendCommand [597]: Serial timeout while writing to serial port, trying again.
2017-09-07 15:53:58,699 - WARNING - USBPrinting.USBPrinterOutputDevice._sendCommand [597]: Serial timeout while writing to serial port, trying again.
2017-09-07 15:53:59,201 - ERROR - USBPrinting.USBPrinterOutputDevice._sendCommand [602]: Unexpected error while writing serial port Write timeout
2017-09-07 15:53:59,202 - DEBUG - USBPrinting.USBPrinterOutputDevice._close [552]: Closing the USB printer connection.
2017-09-07 15:53:59,209 - DEBUG - UM.Qt.QtApplication.preventComputerFromSleeping [415]: Prevent computer from sleeping? False
2017-09-07 15:53:59,210 - ERROR - USBPrinting.USBPrinterOutputDevice._sendCommand [602]: Unexpected error while writing serial port Write timeout
2017-09-07 15:53:59,221 - WARNING - UM.Qt.Bindings.Theme.getIcon [70]: No icon tab_status_stopped defined in Theme
2017-09-07 15:53:59,223 - DEBUG - USBPrinting.USBPrinterOutputDevice._close [552]: Closing the USB printer connection.
2017-09-07 15:53:59,228 - DEBUG - UM.Qt.QtApplication.preventComputerFromSleeping [415]: Prevent computer from sleeping? False

@efilenko Can you look at this one? I can only reproduce this on Windows. Maybe we need a longer timeout or more retries. If you have some proposed fixes or patches with additional debug code, I can test them for you if needed.

tranter changed the edit policy from "Custom Policy" to "Subscribers".
tranter added a subscriber: tranter.

Note that bug T1160 is a different issue but can mask this one.

@ Yahuba Please upgrade your firmware as per T1160 and then see how reproducible this is. I think this can be made a low priority. I have to go to a lot of effort, clicking on the move buttons many times, to cause it to occur now.

We suspect that the root cause for this is the same as T1170, so let's see if that fix addresses it.

Steven added a subscriber: Steven.Sep 15 2017, 3:36 PM

Now that T1170 is fixed, in build 2.6.33 under Windows 10 I can no longer reproduce this problem any more. Cura prompted me to upgrade the firmware.

efilenko closed this task as Resolved.Sep 26 2017, 12:09 PM

Closed per QA team request.