Jump to content
Ultimaker Community of 3D Printing Experts
Sign in to follow this  
pretengineer

Cura 12.12 with RAMPS 1.4 connection issue

Recommended Posts

Hi,

I've recently downloaded Cura 12.12 to use with my RepRap Prusa but I can't get it to connect. When I click connect in the print dialog, it goes from 'Machine State: Detecting baudrate' to 'Machine State: Error: No more baudrates...'

I've tried setting different baudrates in the firmware but no luck. I've been using Slic3r and Pronterface for the past few weeks with little to no issues.

I'm using RAMPS1.4 and Sprinter software.

Any ideas on a solution?

 

Share this post


Link to post
Share on other sites

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.

 

Share this post


Link to post
Share on other sites

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)

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

Terms of Use Privacy Policy