Trying to connect Windows computer to ender 3

What is the problem?

I am currently trying to connect my printer to octoprint on my windows laptop. When I press connect it is failing to connect. Anyone have suggestions?

What did you already try to solve it?

I have tried switching out cables and switching between usb ports

Have you tried running in safe mode?

not applicable

Did running in safe mode solve the problem?

not applicable

Systeminfo Bundle

You can download this in OctoPrint's System Information dialog ... no bundle, no support!)

WRITE HERE

Additional information about your setup

OctoPrint version, OctoPi version, printer, firmware, browser, operating system, ... as much data as possible

Printer : Ender 3
Firmware: Marlin 2.0.x

Well we need a bit more information.

At least a systeminfo bundle with activated serial logging

2021-05-16 19:49:24,775 - octoprint.util.comm - INFO - Serial detection: Performing autodetection with 7 port/baudrate candidates: COM3@115200, COM3@250000, COM3@230400, COM3@57600, COM3@38400, COM3@19200, COM3@9600
2021-05-16 19:49:24,775 - octoprint.util.comm - INFO - Serial detection: Trying port COM3, baudrate 115200
2021-05-16 19:49:24,775 - octoprint.util.comm - INFO - Connecting to port COM3, baudrate 115200
2021-05-16 19:49:24,808 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-05-16 19:49:24,812 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:26,822 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-05-16 19:49:26,832 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:28,863 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2021-05-16 19:49:28,889 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:30,910 - octoprint.util.comm - INFO - Serial detection: Trying port COM3, baudrate 250000
2021-05-16 19:49:30,927 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-05-16 19:49:30,931 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:32,968 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-05-16 19:49:32,984 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:34,993 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2021-05-16 19:49:34,996 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:37,017 - octoprint.util.comm - INFO - Serial detection: Trying port COM3, baudrate 230400
2021-05-16 19:49:37,037 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-05-16 19:49:37,042 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:39,047 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-05-16 19:49:39,066 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:41,085 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2021-05-16 19:49:41,093 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:43,113 - octoprint.util.comm - INFO - Serial detection: Trying port COM3, baudrate 57600
2021-05-16 19:49:43,122 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-05-16 19:49:43,124 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:45,145 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-05-16 19:49:45,153 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:47,159 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2021-05-16 19:49:47,166 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:49,174 - octoprint.util.comm - INFO - Serial detection: Trying port COM3, baudrate 38400
2021-05-16 19:49:49,179 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-05-16 19:49:49,180 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:51,186 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-05-16 19:49:51,193 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:53,198 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2021-05-16 19:49:53,208 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:55,226 - octoprint.util.comm - INFO - Serial detection: Trying port COM3, baudrate 19200
2021-05-16 19:49:55,234 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-05-16 19:49:55,237 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:57,252 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-05-16 19:49:57,258 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:49:59,275 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2021-05-16 19:49:59,280 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:50:01,292 - octoprint.util.comm - INFO - Serial detection: Trying port COM3, baudrate 9600
2021-05-16 19:50:01,301 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2021-05-16 19:50:01,305 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:50:03,319 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2021-05-16 19:50:03,325 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:50:05,341 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2021-05-16 19:50:05,347 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2021-05-16 19:50:07,366 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Error"
2021-05-16 19:50:07,377 - octoprint.util.comm - INFO - Changing monitoring state from "Error" to "Offline after error"
2021-05-16 19:50:07,390 - octoprint.plugins.action_command_notification - INFO - Notifications cleared

browser.user_agent : Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:90.0) Gecko/20100101 Firefox/90.0
connectivity.connection_check : 1.1.1.1:53
connectivity.connection_ok : true
connectivity.enabled : true
connectivity.online : true
connectivity.resolution_check : octoprint.org
connectivity.resolution_ok : true
env.hardware.cores : 4
env.hardware.freq : 2808
env.hardware.ram : 17093189632
env.os.bits : 64
env.os.id : windows
env.os.platform : win32
env.python.pip : 21.1.1
env.python.version : 3.9.5
env.python.virtualenv : true
octoprint.safe_mode : false
octoprint.version : 1.6.1
systeminfo.generator : systemapi

That is a serial.log, and a system info dump. Please share a full system info bundle.

octoprint-systeminfo-20210517110135.zip (25.2 KB)

Have you verified the device and it's associated com port shows up in the device manager?

Yes I have I identified it as comport 5

So based on that and the logs it appears to be trying to connect but getting permission denied. Is anything else open that might be trying to connect to the printer?

Are you able to connect using something like PuTTy?

hm i saw that. I dont think I have anything open that might interfere with it. I think i tried connecting to the printer using a usb feature on the creality slicer. It wasnt able to connect so I am gessing the answer to the 2nd question is no. What should I do if I cant connect via usb?

Close pretty much everything you can, slicers (particularly Cura) will connect automatically whether you ask them to or not.

When I did my tests they were all closed

Your issue is that the Ender 3 is not a Plug and Play device. I had to download the Windows drivers to make it work correctly. Then it would assign a Com port to it and it was happy. You can find the windows drivers on the flash card that came with the Printer.

I searched the usb but I didnt find any driver

You may google for "Win 10 USB driver Ender 3"

Just get a pi 3. My windows laptop is right by my ender 3, but i have a pi 3. I have the ability of wireless where ever i am.. You are not going to have that with window(or so i believe), if you want to start a print wirelessly from another location at home or away from home.

I see you have Marlin in the Ender 3...
What is the comport setting you used in Marlin?
Should be in configuration.h (about line 100 to 125 deal with the comports of the board)

If set incorrect, there is nothing Windows can do....