USB connection issue only resolved with a server reboot
Here's my setup:
I'm running 15 delta printers on a Windows 10 machine all running through USB. Sometimes I get connection issues with a printer which is understandable with all the cables running everywhere. The symptoms are the printer no longer responding to server commands and the server console for the printer showing 'Seems like we missed an ok, continue sending' Nothing I try seems to get it to recover from this state except rebooting the server. The issue with rebooting the server is the other 14 printers are constantly running and so its better to leave one off then mess with the others. I have found that I can 'add' a new printer to the server, give it the same COM port and it runs without issue. By adding a printer I just mean creating a new printer profile but using the same physical printer that was having issue.
So to my question: Is there a way to get the server to forget, delete, or remove the prior connection so that it can establish a new one without being restarted?
I've tried deactivating-activating; turning the printer off and on; plugging it into a different USB port so that it has a new COM port and every combination sequence between the three. The fact that by using a new printer config(slug) and then the printer works fine, leads me to believe the issue resides somewhere with the servers connection tied to the printer config(slug). Thats what I'm trying to reset.
I'm running 15 delta printers on a Windows 10 machine all running through USB. Sometimes I get connection issues with a printer which is understandable with all the cables running everywhere. The symptoms are the printer no longer responding to server commands and the server console for the printer showing 'Seems like we missed an ok, continue sending' Nothing I try seems to get it to recover from this state except rebooting the server. The issue with rebooting the server is the other 14 printers are constantly running and so its better to leave one off then mess with the others. I have found that I can 'add' a new printer to the server, give it the same COM port and it runs without issue. By adding a printer I just mean creating a new printer profile but using the same physical printer that was having issue.
So to my question: Is there a way to get the server to forget, delete, or remove the prior connection so that it can establish a new one without being restarted?
I've tried deactivating-activating; turning the printer off and on; plugging it into a different USB port so that it has a new COM port and every combination sequence between the three. The fact that by using a new printer config(slug) and then the printer works fine, leads me to believe the issue resides somewhere with the servers connection tied to the printer config(slug). Thats what I'm trying to reset.
Comments
Can you say what happens if you deactivate and activate? Does it start a connection loop that constantly fails or does it not try to reconnect at all?
here is the log showing me change the printer configs from 'K8' to 'K1'
In the above situation both printer names K8 and K1 were the same physical printer. Everything works fine using K8 config but hangs using the K1 config. And both configs are the same except for printer name and slug name. And if I restarted repetier-server K1 would work again.