Octoprint Suddenly Won't Connect to Printer


#1

What is the problem?
Over the last 1-2 weeks it started taking a lot longer for Octoprint to connect to my printer. But, as of a few days ago, it won't connect at all. The only thing I have done over the last few weeks is update Octoprint to 1.3.9rc2, then back down to 1.3.8, and update Octolapse to v0.3.1.

The Serial Port is /dev/ttyACM0 when I have my printer plugged in via USB to my raspberry pi and it will automatically detect the baud rate at 115200. I believe these were the settings I used in the past when it would connect.

The IP for my raspberry pi has changed twice over the last few weeks (due to power outages in my house causing my internet to restart) but I've connected to my printer every time a new IP was generated for my pi. I'm guessing this isn't causing the issue.

Also, the firmware on my printer has NOT been updated since I got the printer. I've been using Octoprint successfully since approximately March 2018.

What did you already try to solve it?

  • Rebooted printer and raspberry pi many times
  • Cleared browser history
  • ctrl + f5
  • Increase timeout limits in "Serial Connections -> Intervals & Timeouts"
  • Searched on google for countless hours
  • Tried with both 1.3.9rc2 and 1.3.8 Octoprint versions
  • Removed Octolapse
  • Tried accessing Octoprint and connecting on another computer (thought I'd at least try)

Additional information about your setup (OctoPrint version, OctoPi version, printer, firmware, octoprint.log, serial.log or output on terminal tab, ...)

  • Octoprint - 1.3.8
  • OctoPi 0.14.0
  • Octolapse v0.3.1
  • Attached octoprint.log
    octoprint.log (298.9 KB)
  • serial.log output...
    2018-07-16 04:05:10,302 - Connecting to: /dev/ttyACM0
    2018-07-16 04:05:10,317 - Changing monitoring state from "Offline" to "Opening serial port"
    2018-07-16 04:05:10,319 - Connected to: Serial<id=0x7432a110, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
    2018-07-16 04:05:10,320 - Changing monitoring state from "Opening serial port" to "Connecting"
    2018-07-16 04:05:40,353 - There was a timeout while trying to connect to the printer
    2018-07-16 04:05:40,364 - Changing monitoring state from "Connecting" to "Offline"
    2018-07-16 04:05:40,370 - Connection closed, closing down monitor
    -Terminal Tab Output...
    Connecting to: /dev/ttyACM0
    Changing monitoring state from "Offline" to "Opening serial port"
    Connected to: Serial<id=0x6b02a570, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=10.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
    Changing monitoring state from "Opening serial port" to "Connecting"
    There was a timeout while trying to connect to the printer
    Changing monitoring state from "Connecting" to "Offline"
    Connection closed, closing down monitor

Thanks!


#2

Regarding IP addresses:

If it were me, I'd setup a permanent IP address lease in my router's DHCP server section of its configuration. That way, the IP address of your printer is always the same.


If you've added any other USB-based things to your printer, try disconnecting them. It's possible that they're fighting over the same device name, UART or there's low power to the Raspberry Pi.

Verify that you've got a 2.5A 5V power adapter at least for this.

Verify that your printer's serial cable is shielded (metallic shielding inside) or minimally, there are one or more ferrite cores. It's possible that both your micro USB power cable and the printer's serial cable are both trying to provide 5V to the Raspberry Pi.


#3

What printer is this? What firmware?


#4

@OutsourcedGuru, that's a good idea to setup a permanent IP address! I'm not the most "techy" guy so I would have never thought of doing that.

The only items plugged into my Raspberry Pi is my printer, and a USB powered 40mm fan that I use on my printer. I had a webcam plugged into it at one point but haven't for awhile (and Octoprint worked during and after it was unplugged).

The one USB cord I use to connect my printer to the Raspberry Pi has worked for months but I did try a different one last night with no success. I'll verify the power adapter tonight.

@foosel, I use a Monoprice Select Mini (Version 2) and the firmware is V35.110.2


#5

I wonder if I should wipe my micro SD card I'm using for my Raspberry Pi and try reinstalling everything...not sure if that would work.


#6

I haven't worked on this since I last posted because I have been replacing my hotend but I found a weird fix...instead of manually selecting the baud rate of 115200, I select "AUTO" and then it connects...using 115200. Weird but it works.

Edit: Forgot to mention I upgraded to version 1.3.9 (stable) and installed this plugin...