PrusaSlicer fails to connect to Raspberry Pi 4  

RE:

Hi, sorry, the hotfix version isn't as much of a hotfix as I have hoped. Turns out addidng HOTFIX at the end of the version number broke stuff in Connect in unforseen ways. Sorry. The file uploads in 0.6.x break when interrupted and need the STOP_TRANSFER command that should have been generated internally.

This isn't your problem exactly tho. IDK, all i can do right now is ask for logs. Those are in the local web under settings. I want the one named syslog. If it's too big, try zipping it, or give me a link to a gdrive upload or something along those lines. Thank you

RE: PrusaSlicer fails to connect to Raspberry Pi 4

I was also unable to ping it

If you can't ping it then it's an OS issue not a Prusaslicer one.

I suspect it's name resolution. Use the AP config to find the IP of the Pi and use that and report back.

Loath to suggest Apple software but Bonjour can sometimes resolve such issues.

RE: PrusaSlicer fails to connect to Raspberry Pi 4

I wouldn't count on it being  name resolution. OP mentioned the IP and a ping from a network scanner utility. Idk why would it not respond while being connected and working :/

RE: PrusaSlicer fails to connect to Raspberry Pi 4

@tojik You may well be correct, I kindda discounted the network scanner result, assuming it's correctly configured.

RE: PrusaSlicer fails to connect to Raspberry Pi 4

Hi, here is a link to the syslog files. I didn't change their extensions, they downloaded from the local web page as those file types. Also, since I'm posting the logs on a public forum, I changed all instances of my printer's serial number in the logs, to the value MySerialNumber

While initially setting it up, I was having a hard time getting the printer to communicate with the Raspberry Pi 4 due to this not being in the documentation so you will probably see a lot of errors related to it in the logs. I just wanted to make you aware so, you know it's unrelated to the bug.

Oddly enough, the remote webpage didn't show that anything was being uploaded, or failed to upload when I ran the STOP_TRANSFER command.

Thank You

RE:

@towlerg I pinged its IP address. The scanner (Advanced IP Scanner) was correctly configured and all devices were on the same subnet so no VLAN issues. Thank you for the advice though. 🙂 

RE: PrusaSlicer fails to connect to Raspberry Pi 4

I guess all that leaves is a bad install of Octoprint (or atleast the Wifi bit). Anyway if you can't ping it it's certainly not PrusaSlicer issue.

Oddly enough, I was able to manipulate the printer and start prints via connect.prusa3d.com

Not that Prusa savvy but I guess that your talking to the printer not the Pi. How sure are you that you put the correct SSID when you did original Octoprint install? Did you install OctoPrint or OctoPi?

RE: PrusaSlicer fails to connect to Raspberry Pi 4

I think you missed this part of my first post. "I got it to start working again, by sending the "STOP_TRANSFER" command to the printer via connect.prusa3d.com."

And I was using Prusa's Prusa Connect/Link, not Octoprint or Octopi.

RE: PrusaSlicer fails to connect to Raspberry Pi 4

Posted by: @momo

I think you missed this part of my first post. "I got it to start working again, by sending the "STOP_TRANSFER" command to the printer via connect.prusa3d.com."

And I was using Prusa's Prusa Connect/Link, not Octoprint or Octopi.

I did indeed, saw Pi and jumped to all sorts of conclusions. I read what I expected rather than what was posted. Mia culpa for my nonsense posts.

I'm sure you're aware that Prusa Connect is very much a work in progress.

RE:

There is this new thing we are writing, it's called PrusaLink and it's supposed to allow 8bit machines on the latest firmware to work with Prusa Connect

There is an issue of an interrupted file transfer not getting closed. Instead the socket is read from repeatedly.

Have not yet replicated the ping issue, the broken transfers are fixed in 0.7.0 that should be coming very soon

RE:

I have failed to reproduce this, your pi is losing connection like 3x a day, but even when i put it into the unfinished upload bug state and make it lose connection, it reconnects fine and can be pinged as if nothing happened. I've recently seen a router that couldn't handle a LAN game of minecraft. The server was on an I7 9750H and it just couldn't, people were teleporting all over the place. After that experience, I don't trust WiFi routers anymore and I'm inclined to throw it up to that. Need to move on, so the 0.7.0 can be a thing, apparently, we need to fix more bugs before the release. This one will have to pop up more for me to catch it. If you figure out a consistent pattern I could repeat to reproduce it in 0.7.0, i'll gladly re-visit it.