Connection probs with 1.5

Get Help Networking
1

What is the problem?
Hello, and thanks for the add.
I've been using octoprint for 4 months (I've only had a 3d printer for 6) and it's been great - I've been able to download gcode straight to the Pi4, and straight to my Prusa i3 Mk3 without needing the sd cards.
And then I got a new PC and upgraded to octoprint 1.5i.
I followed my network settings, and can link on Firefox to octoprint no problem.
But in SLicer, in the print host upload section, when I type in the IP address that works on firefox, and click on Browse, it comes up with no options. If I click test, then I get the same error that I get when I click on the G button (So slicer finds octoprint, it just doesn't know how to print to it amy more)

What did you already try to solve it?
Lots of restarts, of both laptop and printer and Pi4.
I've checked the IP address that Firefox uses to connect, and typed that into Prusa Slicer's Hostname, IP or URL box. I've typed both the user name and the password into the API Key/Password box both without success (What's an API key?)

Logs (syslog, dmesg, ... no logs, no support)

The error from Prusa slicer when I try to print gcode to octoprint
Error uploading to print host:
HTTP 403:

403 Forbidden

Forbidden

You don't have the permission to access the requested resource. It is either read-protected or not readable by the server.

In Firefox, when I click on connect, it cycles through the baudrates

Changing monitoring state from "Offline" to "Detecting serial connection"
Performing autodetection with 7 port/baudrate candidates: /dev/ttyACM0@115200, /dev/ttyACM0@250000, /dev/ttyACM0@230400, /dev/ttyACM0@57600, /dev/ttyACM0@38400, /dev/ttyACM0@19200, /dev/ttyACM0@9600
Trying port /dev/ttyACM0, baudrate 115200
Connecting to port /dev/ttyACM0, baudrate 115200
Handshake attempt #1 with timeout 2.0s
Connected to: Serial<id=0xb2a0bf70, open=True>(port='/dev/ttyACM0', baudrate=115200, bytesize=8, parity='N', stopbits=1, timeout=2.0, xonxoff=False, rtscts=False, dsrdtr=False), starting monitor
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyACM0, baudrate 250000
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyACM0, baudrate 230400
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyACM0, baudrate 57600
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyACM0, baudrate 38400
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyACM0, baudrate 19200
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Trying port /dev/ttyACM0, baudrate 9600
Handshake attempt #1 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #2 with timeout 2.0s
Send: N0 M110 N0*125
Handshake attempt #3 with timeout 2.0s
Send: N0 M110 N0*125
Changing monitoring state from "Detecting serial connection" to "Error: No more candidates to test, and no working port/baudrate combination detected."
Changing monitoring state from "Error: No more candidates to test, and no working port/baudrate combination detected." to "Offline (Error: No more candidates to test, and no working port/baudrate combination detected.)"
Connection closed, closing down monitor

Octoprint.log (77.7 KB)

Additional information about your network (Hardware you are trying to connect to, hardware you are trying to connect from, router, access point, used operating systems, ...)
I have both the laptop and the Pi4 hardwired to the home network, wireless is not being used. I'm running Win 10, with Firefox, and Prusa Slicer 2.2.0
I've just upgraded octoprint to ver 1.5 today - it was all working before that, but it is a new laptop. (Dell Inspiron 3793)

Any advice about how to get over this hump would be gratefully received.

Many thanks

Pad

2

Hello @001Pad!

You get the API key from OctoPrint:

grafik
grafik648×616 27.8 KB

You copy it there (there is a button to click on the right) and paste it into PrusaSlicer's API Key field.

For the connection to the MK3:

I assume you have powered on the MK3 and connected it with a proper USB cable to the Pi on which OctoPrint is installed, yes?

3

Hi Ewald,
I wonder if the API key is the problem? I am trying that right now. Yes, that did it!
When I fill in the API key, I have full communication with Octoprint at last. I tried to generate a Manual application key but if had no effect at all.

So thank you very much: that seems to have been the problem.

And in answer to your second question, no, the computer isn't linked directly to the Pi, but they are both physically linked to the home network. Is that an issue, do you think?

Pad

4

No. I am wrong - It hasn't fixed the problem I now can't connect on the octoprint front page. It does even less than it did before.

The error has stopped on the Octoprint setup page, but now I have an issue with connection elsewhere.

I've been an this for half the night, so I'm off to bed now - fresh ideas (and energy) in the morning.

Thanks, though, for your help so far.

Pad

5

These message are from the connecting tries of OctoPrin to the printer.

2020-12-02 14:22:48,465 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2020-12-02 14:22:48,467 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-12-02 14:22:50,472 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2020-12-02 14:22:50,476 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-12-02 14:22:52,482 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyACM0, baudrate 19200
2020-12-02 14:22:52,487 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2020-12-02 14:22:52,491 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-12-02 14:22:54,496 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2020-12-02 14:22:54,500 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-12-02 14:22:56,505 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2020-12-02 14:22:56,509 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-12-02 14:22:58,513 - octoprint.util.comm - INFO - Serial detection: Trying port /dev/ttyACM0, baudrate 9600
2020-12-02 14:22:58,516 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #1 with timeout 2.0s
2020-12-02 14:22:58,520 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-12-02 14:23:00,522 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #2 with timeout 2.0s
2020-12-02 14:23:00,526 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-12-02 14:23:02,529 - octoprint.util.comm - INFO - Serial detection: Handshake attempt #3 with timeout 2.0s
2020-12-02 14:23:02,532 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
2020-12-02 14:23:04,534 - octoprint.util.comm - INFO - Changing monitoring state from "Detecting serial connection" to "Error: No more candidates to test, and no working port/baudrate combination detected."
2020-12-02 14:23:04,545 - octoprint.util.comm - INFO - Changing monitoring state from "Error: No more candidates to test, and no working port/baudrate combination detected." to "Offline (Error: No more candidates to test, and no working port/baudrate combination detected.)"

So this was my question in my previous post:

6

Hi Ewald,

At the end of my last post, I wrote a reply to your earlier question, "And in answer to your second question, no, the computer isn't linked directly to the Pi, but they are both physically linked to the home network.
Is that an issue, do you think?"

I have been using octoprint only for a couple of months, and all of that time it has been at the other end of the network cable, with the signal from my laptop getting to the Pi4 via the router.

That system has now run into the connection problems I have mentioned, but it has worked for months well up until now. The big change is trying to make it work on another laptop. Somehow I can't get the settings right.

Would it help temporarily to connect them directly first, and then separate them on the network later? That's not what I did last time, but there have been several updates since then to octoprint and things might have changed.

Thanks

Pad

Hello again Ewald,
Things have moved on again, with another update to 1.5.1 when I got back home today, and without any more ado, the connection worked out perfectly, and it is printing happily. Thanks for your help with the API key.
Pad

7

HI

Further to that, yes, I have powered on the printer, the laptop and the Pi.

Pad

8

Hi Ewald.
I slept on it, and went back in the morning.
It was working like a dream. I'm really not sure why it wasn't working at the end of the day.

But I was trying to run without the key or ISP In Prusa Slicer, and once that was sorted, so was everything else.

Thanks v much for your help.

001Pad

1 Like