I can't get a connection between the SKR Mini E3 V3 and octoprint.
What did you already try to solve it?
Tried a data only usb cable, tried different firmware.
Printer connects effortlessly in windows, on both cura and pronterface. Device is showing up in linux as "STMicroelectronics Virtual COM Port". usb connection showing up under ttyACM0. Just hangs on "Opening serial connection". Baudrate is set correctly in both firmware and in octoprint. My creality 4.2.2 board works no problem on the same setup without restarting or anything, plug in, refresh, connect and boom it works. switch back to my main printers usb and back to the stalling. It's almost like the board just doesn't have the proper linux driver or the driver its using isn't utilizing the hardware correctly. As mentioned earlier the windows drivers are functioning as intended.
Have you tried running in safe mode?
Yes, no difference
Did running in safe mode solve the problem?
no ):
Systeminfo Bundle
You can download this in OctoPrint's System Information dialog ... no bundle, no support!)
Yes, I might not have been very specific on that, but isolating the power is what I meant by data only usb cable. I actually had set the cable that way long ago because I’ve always printed via usb and I didn’t like how the printer screen would stay on even when the printer was powered down, unless I removed the usb cable ):
Yes, I have 3 cables I’ve tried. One without the +5v connected, and one where it’s covered by tape. I also tried a third cable that hasn’t been altered. All 3 produce the same results. Device shows up correctly under lsusb, USB port shows up under octoprint, but connection can’t be established )-:
I've tried every baudrate in the dropdown menu within octoprint, but I haven't tried changing the buadrate in the printers firmware. It's set to 115200
You do not need to isolate the 5v USB on the E3V3 board. There is a link on the board that isolates the 5v. You have to bridge the link is you need to supply the board from the USB port
Originally I was running "Marlin bugfix-2.1.x" from both a precompiled service I pay for and also from a firmware I compiled myself. baudrate is locked to 115200 in both firmwares. As far as serial definitions, I'm not sure what to do there but assume they are set right because the board connects fine in windows, and the same definitions are being used on a creality 4.2.2 board that connects fine both in windows and to octoprint. I just now tried Marlin 2.0.9.3 directly from BTT's github page but am experiencing the same behavior )--:
I just installed Marlin 2.0.9.3 directly from BTT's github page but that is giving me the same results )--: is there any other firmware you know of that I could try? Honestly, my mind is telling me it's the driver being used that is causing the issue but I don't know how to look into something like that on linux
Yes, pronterface and cura will connect just fine under windows, I've even ran a 3 day print via usb that way, which leads me to believe it's the driver being used in linux isn't talking well with this specific board. Creality 4.2.2 board with firmware almost identical (besides hardware related code) is working fine both in windows and in linux to communicate with octoprint.
So initially I thought that I had fixed the problem, but the issue came right back after a restart. I found that I had to edit the rules for ACM devices to match the rules for USB devices for it to actually hold. I did so by following this post-
(Previous solution, wasn't persistent upon restart)
So a help page admin on facebook suggested I reinstall the controller drivers from the top. Following the instructions on the page he sent me, issuing commands for the usb COM would lead to the error "no such file or directory"
Now I just need to figure out how to get this command to run on startup since the permission seems to reset on startup after a restart, which shouldn't be very difficult :--)
