Server wont connect unless restarted
Repetier server refuses to talk to my smoothieboard unless I stop and restart the server with the smoothieboard connected. Disconnecting and reconnecting the printer does not fix the issue - only a server restart.
On the server dashboard the printer shows as connected, but no commands are going through, and the communications timeout error keeps on popping up.
Smoothie always comes up on the same com port, so thats not the issue.
Once comms are established everything runs just fine.
I also find that if I try to go direct to com port from Repetier Host the print always freezes after a few moves - no error messages or anything, it just stops.
By comparison Pronterface works just fine, direct to serial.
Any ideas?
On the server dashboard the printer shows as connected, but no commands are going through, and the communications timeout error keeps on popping up.
Smoothie always comes up on the same com port, so thats not the issue.
Once comms are established everything runs just fine.
I also find that if I try to go direct to com port from Repetier Host the print always freezes after a few moves - no error messages or anything, it just stops.
By comparison Pronterface works just fine, direct to serial.
Any ideas?
Comments
When does the com show up in windows? When you connect port or when you enable printer? And is communication possible when printer is disabled? I have only a smoothieware board for testing and there it gets powered from usb and runs already when com shows up. This is what server expects.
I have also tried deactivating the printer, unplug / replug USB, and reactivate - still no joy.
The comport shows up in windows device manager almost as soon as I plug in the USB - my board is powered from USB.
Not sure what you mean by 'disabled'.
The thing is, the Server 'thinks' its connected to the printer - I get the green link symbol - but when I go to the server's printer control menu none of the commands work ( can't home, jog, or set or read temps).
So I've just booted my pc, with the printer already connected. The com port is visible in Device manager. Server Frontend shows a green link to the printer. I hit 'connect' on Host and...
Here's what I see:
the communications timeouts keep repeating every 30 seconds.
Attempting to connect with pronterface confirms that the Server has control of the serial port. It doesn't relinquish control properly when I shut it down either.
Could this be the Server not shutting down properly when the PC is powered down?
Make sure you have in printer configuration set firmware to smoothieware and also baud rate matches. When I do so and activate printer I get something like this:
Telling the server to deactivate/reactivate the printer I see this:
Which looks like its connected ok, but then I try to home:
and it fails.
If I stop and restart the server, (and do nothing else!) I get this:
It occurs to me this may be some kind of weird usb driver/win8.1 issue, so I may dig out a Linux box and see if thats any better.
I can deactivate and activate and it is there. What in deed does not work on the windows version is unpower the board and then power it up again. Then we get no response from the firmware causing the timeouts also the usb port seems to connect correctly. I wonder what is going on there and why it should have worked in older versions.
Can you say which version had worked without that problem?