# Cura not connecting to Lulzbot Mini

**URL:** <https://forum.lulzbot.com/t/cura-not-connecting-to-lulzbot-mini/4272>\
**Category:** Software\
**Created:** [December 2, 2016, 5:43pm UTC](https://forum.lulzbot.com/t/cura-not-connecting-to-lulzbot-mini/4272 "2016-12-02T17:43:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![demary](https://avatars.discourse-cdn.com/v4/letter/d/f475e1/32.png) [@demary](https://forum.lulzbot.com/u/demary)\
**Post date:** [December 2, 2016, 5:43pm UTC](https://forum.lulzbot.com/t/cura-not-connecting-to-lulzbot-mini/4272/1 "2016-12-02T17:43:45Z")

</div>

I am going through the initial setup of my Mini. After loading the rocktopus model, I can click on the Control button, but when the Printer Interface comes up, it shows that it is not connected to the printer. I click connect and it tries for a few seconds, then says “Closed” at the top. This happened with both version 19.08 that came with the printer, and version 21.02 that I downloaded (after uninstalling the previous version). I have tried multiple USB ports and two different computers, but the same thing happens. What am I doing wrong?

---

<div class="post-metadata">

**Author:** ![ttabbal](https://avatars.discourse-cdn.com/v4/letter/t/db5fbb/32.png) [@ttabbal](https://forum.lulzbot.com/u/ttabbal)\
**Post date:** [December 2, 2016, 6:04pm UTC](https://forum.lulzbot.com/t/cura-not-connecting-to-lulzbot-mini/4272/2 "2016-12-02T18:04:12Z")

</div>

Windows, MacOS, or Linux? Which version?

---

<div class="post-metadata">

**Author:** ![demary](https://avatars.discourse-cdn.com/v4/letter/d/f475e1/32.png) [@demary](https://forum.lulzbot.com/u/demary)\
**Post date:** [December 2, 2016, 6:16pm UTC](https://forum.lulzbot.com/t/cura-not-connecting-to-lulzbot-mini/4272/3 "2016-12-02T18:16:02Z")

</div>

Oh sorry! Both computers I have tried are running Windows 10.

---

<div class="post-metadata">

**Author:** ![demary](https://avatars.discourse-cdn.com/v4/letter/d/f475e1/32.png) [@demary](https://forum.lulzbot.com/u/demary)\
**Post date:** [December 2, 2016, 9:15pm UTC](https://forum.lulzbot.com/t/cura-not-connecting-to-lulzbot-mini/4272/4 "2016-12-02T21:15:06Z")

</div>

I went into the machine settings and changed the Serial Port and Baudrate both to AUTO and tried again. I got the following in my error log:

_Changing monitoring state from ‘Offline’ to ‘Opening serial port’  
Connecting to: COM3 with baudrate: 115200 (configured)  
Connected to: Serial\<id=0x31c54f0, open=True\>(port=‘COM3’, baudrate=115200, bytesize=8, parity=‘N’, stopbits=1, timeout=5, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor  
Changing monitoring state from ‘Opening serial port’ to ‘Connecting’  
Send: M105  
Send: M105  
Send: M105  
Changing monitoring state from ‘Connecting’ to ‘Closed’  
Connection closed, closing down monitor  
Changing monitoring state from ‘Offline’ to ‘Opening serial port’  
Connecting to: COM3 with baudrate: 115200 (fallback)  
Connected to: Serial\<id=0x3165510, open=True\>(port=‘COM3’, baudrate=115200, bytesize=8, parity=‘N’, stopbits=1, timeout=3, 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 test, and no s…’  
Connection closed, closing down monitor_
