Windows no re-connection
I have an annoying issue that happens on windows.
When my printer is turned off or loses connection to a windows based server, repetier server will not reconnect to the printer until I stop / start the server again.
The printer is running a custom Due based board with repetier firmware dev 1.0.0.
problem exists from repetier server 0.7 - 0.80.3 for me.
This behavior is not present on linux hosts and my printers.
Any ideas?
Comments
The only way to get it connected at this point is to stop the Server service and restart it.
Also when you power on the printer or if it's on and you attach the USB cable, the printer resets and reboots once. This happens regardless if Server is running or not. It's not an issue, but maybe a clue as to what's happening.
If the printer is on and the Server service doesn't have a connection, any command I send through either Host or via the Server console on the webpage, returns a warning that an OK should have been acknowledged and has no response or effect.
So right now I have a batch file that stops the Server service then restarts it. It's a pain since it has to be run as Administrator and it sort of defeats the purpose of having a server control the printer without having to manually interact with it.
My issue every time is while repetier server is running and the printer is powered down or disconnected for any reason from my windows pc, it will not reconnect with repetier again. It will show the green link but nothing would happen. to fix this I have to disconnect the printer, stop repetier service, reconnect printer and strat repetier service. or restart the pc.
It is like repetier is locking the usb port some how even though from windows perspective the port is no longer available.
Just stopping and starting the service does not help, I need to disconnect the usb in between to make it work again.
This is an issue as my hard stop button and emergency procedure cuts power to the printer and thus renders the server useless untill i perform this procedure above.
This issue is not present on an raspberry pi or a pc with linux. Unfortunately this is not a solution i can tolerate.
Faulting application name: RepetierServer.exe, version: 0.0.0.0, time stamp: 0x5849222c
Faulting module name: ntdll.dll, version: 6.3.9600.17031, time stamp: 0x53088928
Exception code: 0xc0000005
Fault offset: 0x0005a172
Faulting process id: 0xaf0
Faulting application start time: 0x01d2ebb18adcfb24
Faulting application path: C:\Program Files\Repetier-Server\bin\RepetierServer.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 07261ec7-57a8-11e7-9742-08d83468f4fa
Faulting package full name:
Faulting package-relative application ID:
and
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: RepetierServer.exe
P2: 0.0.0.0
P3: 5849222c
P4: ntdll.dll
P5: 6.3.9600.17031
P6: 53088928
P7: c0000005
P8: 0005a172
P9:
P10:
Are you using programming or native due port?
Have you modified it to power only over main power?