yet again another 'cannot connect error' with the new software, surely something is amiss?
Paul
yet again another 'cannot connect error' with the new software, surely something is amiss?
Paul
Error Log
Changing monitoring state from 'Offline' to 'Opening serial port'
Connecting to: COM8
Connected to: Serial<id=0x350c670, open=True>(port='COM8', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=0.1, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Changing monitoring state from 'Opening serial port' to 'Detecting baudrate'
Trying baudrate: 250000
Send: M105
Baudrate test retry: 4
Send: M105
Baudrate test retry: 3
Send: M105
Baudrate test retry: 2
Send: M105
Baudrate test retry: 1
Send: M105
Baudrate test retry: 0
Send: M105
Trying baudrate: 230400
Send: M105
Baudrate test retry: 4
Send: M105
Baudrate test retry: 3
Send: M105
Baudrate test retry: 2
Send: M105
Baudrate test retry: 1
Send: M105
Baudrate test retry: 0
Send: M105
Trying baudrate: 115200
Send: M105
Baudrate test retry: 4
Send: M105
Baudrate test retry: 3
Send: M105
Baudrate test retry: 2
Send: M105
Baudrate test retry: 1
Send: M105
Baudrate test retry: 0
Send: M105
Trying baudrate: 57600
Send: M105
Baudrate test retry: 4
Send: M105
Baudrate test retry: 3
Send: M105
Baudrate test retry: 2
Send: M105
Baudrate test retry: 1
Send: M105
Baudrate test retry: 0
Send: M105
Trying baudrate: 38400
Send: M105
Baudrate test retry: 4
Send: M105
Baudrate test retry: 3
Send: M105
Baudrate test retry: 2
Send: M105
Baudrate test retry: 1
Send: M105
Baudrate test retry: 0
Send: M105
Trying baudrate: 19200
Send: M105
Baudrate test retry: 4
Send: M105
Baudrate test retry: 3
Send: M105
Baudrate test retry: 2
Send: M105
Baudrate test retry: 1
Send: M105
Baudrate test retry: 0
Send: M105
Trying baudrate: 9600
Send: M105
Changing monitoring state from 'Detecting baudrate' to 'Closed'
Changing monitoring state from 'Closed' to 'Error: No more baudrates to...'
Connection closed, closing down monitor
I should mention that I had this same problem with a RAMPS 1.3 board and a different Arduino as well.
Odd. I've never tried sprinter myself (as we use Marlin), one of the things that could be it is that it takes a while for sprinter to be start-up. If you use pronterface, how long does it take to connect? (Pronterface uses very long timeouts, while those of Cura are pretty short)
Pronterface connects almost instantly. I have to swap out my heatbed thermistor for one that Marlin won't read as absolute zero so until then, I'm stuck with Sprinter. I've only realised there's a new version of Cura available so I'll upgrade and see if that helps.
Did the upgrade fix it? I know when I had trouble with my Gen 6 connecting, once I upgraded to 13.03 I believe it was Cura connected just as well as the others. Before I upgraded I was having the same issues you are.
I haven't had the chance to try it with the upgrade, I'll post results at the weekend when I give it a try.
Recommended Posts
Daid 306
Could you post the error log?
Link to post
Share on other sites