[Sticky] Troubleshooting  

RE: Troubleshooting

Does PrusaLink not support the original MK2s? I upgraded to the latest firmware and with it plugged in I got "Unfortunately, we can’t detect your printer on any serial port, or the printer is booting." Also, there is not a RPi option under settings. 

Thanks.

RE: Troubleshooting

Now that I've upgraded my Revo Mk3s+ and MMU2 to the latest versions of everything, I thought I'd give PrusaLink a go using a PI Zero W1 I had previously used a couple of years ago when experimenting with OctoPrint.

On initial installation I appeared to have everything working. I even did a small test print using PrusaLink so at that point was happy....However the next day....

On switching on my printer the "Starting PrusaLink" message seemed to be permenant. However I could access PrusaLink locally on my browser but that now complained about i) Not being connected to Prusa Connect and, more worryingly ii) Unable to establish a connection with the printer.

Yes, my RPi option in Settings is still set to "On".

So, looking at the troubleshooting guide here, I re-flashed the SD card and re-tested. Thiss still resulted in a permanent "Starting PrusaLink" message but this time I can only access the PrusaLink welcome page and the error shown in the attached screenshot:

.

Is there a way to dig deeper into this issue?

RE: Troubleshooting

Hi, sorry for that. Let me just check this might actually be what I think it is. MK3 - 3.13, MMU2 with the latest (MMU3) firmware. If that's the case, please try disabling the MMU and try again. The firmware updated the printer type to mean MK3MMU3 for all MK3s with an MMU on the latest FW and PrusaLink was not ready for it. It's fixed now, but the update is not out yet.

BTW this screen absolutely blows. I have a port description which tries to tell you what the heck happened. You might see "Unsupported printer type" there, but it does not seem to show in the web UI, so I'm shooting in the dark.

RE:

Posted by: @tojik

Hi, sorry for that. Let me just check this might actually be what I think it is. MK3 - 3.13, MMU2 with the latest (MMU3) firmware. If that's the case, please try disabling the MMU and try again. The firmware updated the printer type to mean MK3MMU3 for all MK3s with an MMU on the latest FW and PrusaLink was not ready for it. It's fixed now, but the update is not out yet.

BTW this screen absolutely blows. I have a port description which tries to tell you what the heck happened. You might see "Unsupported printer type" there, but it does not seem to show in the web UI, so I'm shooting in the dark.

When will it be out

RE: Troubleshooting

It's vacation time here in the northern hemisphere, so releasing anything that needs approval from people gets complicated. The problem exists because I was on vacation and the 3.13 went out. I will know more next week.

RE: Troubleshooting

You nailed it. After disabling the MMU it all kicked into life. I'll await the update!!!

RE: Troubleshooting

Hello, I cannot  send print files from prusaslicer. When I send to PrusaConnect I get a connection timeout (using the connect api key). When I send to printer  throufg prusalink useing the printer api key I get Error uploading to print host:Timeout was reached: But I can see the printer in Prusaconnect!

So how do I get the Prusaconnect working?

thanks, Maarten

Posted by: @stepan

The LCD shows “Starting PrusaLink” even after 5+ minutes

• Make sure you are using the latest FW or
• Reflash the SD image

“ERR: NO IP” on LCD

• Make sure you have Wifi in reach or
• Make sure the SSID and password are correct - download the config file wpa_supplicant.conf, add your SSID and password, save the file to the boot partition on the MicroSD card and restart the Link (turn OFF and ON the printer) or
• Reflash the SD image

White/blank screen after finishing the Wizard

• Make sure you are logged in on connect.prusa3d.com

The Wizard can’t get the serial number from the printer

• Make sure you are using the latest FW or
• Check the SN via e.g. Pronterface (@;C32u2_SNR) and let us know

Deleting files from the micro SD card

• Go to Connect Local (the IP address from the printer, login and password was set in the 2nd step of the Wizard - Authorization) -> Projects -> Prusa Link gcodes

Forgotten login/pass to the Link’s website

• You have to go through the Wizard again, remove the prusa-printer-settings.ini file from /home/pi and restart the Link or
• Reflash the SD image

Slow uploading of the gcode to PrusaLink

• The upload is limited while printing to prevent slowing down the print

RE: Troubleshooting

Hi, when setting up the physical printer, what does pressing the test button result in? If using Prusa Connect, you will need to put "connect.prusa3d.com" into the address box, if using PrusaLink, the printer IP needs to be there. Same goes for the API key. There are two, one for Connect, one for Link, but you don't seem to be running into that issue. At least not yet. We know about the address bar being a bit confusing and the slicer teem is thinking about ways to make it less so. Hopt this helps

RE: Troubleshooting

Hi Tojik,

I used the IP the printer gives me. In Prusaconnect (which works fine) I get  Api keys for Connect and link, so I use link api.

when I test Prusaslicer-phycical printer I get:
Kan niet verbinden met PrusaLink  (cannot connect to PrusaLink): Timeout was reached:Connection timed out after 10001 milliseconds[Error 28] .

I have both PC and MK4 connected to an access point with lan cable. So, while prusaconnect has no trouble seeing the MK4, it does not show up in the decive manager of my PC (win10pro).

I do hope you can help me with this, as I had hoped walking around with flash drives would be a thing of the past.

thanks, Maarten

RE: Troubleshooting

Can you connect to the PrusaLink web interface from your web browser? It is really weird that your browser could but your slicer could not. What version is your slicer? And also, did it ever ask you for firewall permissions? If not, i am not sure whether it needs that enabled, but I would make sure it is, just in case

RE: Troubleshooting

Yes, I can connect to prusalink in the browser window.

When I hit send to printer I get  message: Upload has failed. There is no suitable storage found at 192.168.19.29. Which is exactly the URL of prusalink.  Do I need to add storage to the printer?

Slicer is v 2.6.1 Win64. Firmware is 5.0.1 +12089

RE: Troubleshooting

Please make sure the test button result is ok first. If it is, and you're getting this message, please make sure your usb drive is inserted with some free space on it.

Just making sure. Your physical printer is set to PrusaLink with ip of the printer and the PrusaLink API key.

You can also try setting it to PrusaConnect, address would be https://connect.prusa3d.com and API key would be the Prusa Connect one.

If not sure, go to firewall settings and let PrusaSlicer through, se it can talk to the network uninhibited

RE: Troubleshooting

The firewall was already set to let Prusaslicer through in private networks (could not set it for public). I inserted a USB flash drive, same results.

So, I am getting nowhere. I tried with prusaconnect, using the Connect Api key. But what do I set as host?

thanks, Maarten

RE: Troubleshooting

Mine looks like this for the PrusaConnect host type

For PrusaLink, you can either try host type PrusaLink, url is the ip and auth can either be the API key, or you can try your luck with authoriztion type HTTP Digest. The name would be maker and the password the api key

RE: Troubleshooting

😀Thanks! it works I am printing over prusalink using http. Also the prusaconnect URL worked. Now I know again why I choose prusa.

Djiekujim, if thats the right word.

Maarten

RE: Troubleshooting

Hi, just installed the RPI zerro on my mk3s+ with the firmware 3.14.

The lcd screen show me the IP, but the wizard tel me that the serial port is not working.

RE: Troubleshooting howto delete Files

Hi, I use PrusaLink 0.8.1 on a Raspberry Pi4 and accidently load a *.3mf File to the PrusaLink, how can I delete this File? There ist no delete Icon and I can't open it as a Project.

RE: Troubleshooting

ssh or directly log in to the rpi4  and delete the file?

RE:

I also have this issue with an mk3s+ printer not being detected by the raspberrypi zero W 2 running the latest prusalink image. The pi is installed in the back of the mk3s+ einsy board using the header pins as shown in the instructions here: https://help.prusa3d.com/guide/prusalink-and-prusa-connect-setup-mk3-s-_221744

MK3S+ firmware 3.14.1-8237

Prusalink version 0.8.1  (also tried 0.7.2)

The mk3s+ display shows "RPi booting..." then after about 30 seconds it shows "Starting PrusaLink" I've been troubleshooting this on and off for 3 days and at one point I left it overnight so I'm guessing that covers the 'looooooonnnng time' in the instructions.

I first flashed the 0.8.1 image and tried this without changing anything. I didn't get any further than the "Starting PrusaLink" on the mk3s+ display. Because I set the hostname when I flashed the prusalink image onto the sd card I was also able to find the raspberry pi on my LAN by going to http://mk3sprinter.local where I see a similar message to the person I'm replying to above. Specifically it shows the same webpage and the error message is "/dev/ttyAMA0: NOT USABLE ." I then tried to flash 0.7.2 and I didn't get any further than the "Starting PrusaLink" message and the same error message on the webpage at http://mk3sprinter.local. I then re-flashed 0.8.1 and set ssh credentials so that I could ssh into the pi and edit the config. Based on the comments on the 0.8.1 release at the releases URL here https://github.com/prusa3d/Prusa-Link/releases I added the file "/etc/prusalink/prusalink.ini" and edited it to look like this:

[printer]
port = /dev/ttyAMA10

When I access the prusalink webpage on my pi the error message now says "/dev/ttyAMA10: NOT USABLE ." So this has had no effect.

I've desoldered and resolderd and tested all the pins on the raspberry pi with an led and a 1k resistor and they all work. I did this by disabling the the serial port using raspi-config and then using the pinctrl command using the following sequences to turn the led on:

pinctrl set 14 op dh

and this turn it off again:

pinctrl set 14 op dl

I did this for pins 14, 15 and 22 and they all work fine. I then used raspi-config to re-enable the serial port but with the tty login turned off (as it was set up with the newly flashed image). I've searched various raspberrypi forums to see if the serial port could be disabled in software somehow and as far as I can tell if I have used raspi-config and set the answers in menu 3 menu I3 to:

"Would you like a login shell to be accessible over serial?" NO

"Would you like the serial port hardware to be enabled?" YES

it should be working. Also, I'm guessing that the serial port must be working at some level because otherwise how does the mk3s know that the status of the pi has changed from "Rpi booting..." to "Starting PrusaLink" I am literally at a loss for what to try now. Does anyone have any ideas? Should I downgrade the firmware on the mk3s+ to something that was current when the 0.7.2 prusalink image was released and try that again? What combinations of firmware versions are working for others?

...After writing all this, I thought I will just comment out the line that changes the port in "/etc/prusalink/prusalink.ini" and f**k me it works now... maybe it was a dodgy solder joint that I fixed when I re-soldered it the third time... I've posted this here anyway so that hopefully it will help someone in the future.