0.5.2 Documentation missing for USB and non Zero Pi  

Problems with connecting to printer?

I can get the prusa-link local web page up, but it seems it's not connecting to the printer.

Are there any specific things to do when creating the ini file that I could've possibly missed?

Try this

dmesg | grep tty

Look for something like this:

[ 5.155995] cdc_acm 1-1.1:1.0: ttyACM0: USB ACM device

In my case, ttyACM0 (/dev/ttyACMo) as I wrote above, is the only tty device attached as USB.  That is the printer.  Most anything else USB attached will not be tty - just your printer.

Yours might be different?

And you setup with the character after ACM as a zero, and not the letter O?

Trying to do the same

Hey, I am attempting to do this too with a Pi3. Are you adding the directory and ini file to the pi or to the printer?

I have attempted to add the [printer] command into the ini file inside the pi sd card and I still can't communicate with the printer.

Yes

You create the directory and create the file on the Pi file system.

I don't have a Pi3, so I don't know, but do try the dmesg thing above.  Even if we are both running the exact same version of Raspberry OS, the different hardware - especially very different USB hardware, may lead to different naming.

Do you, for example, even have a /dev/ttyACM0?  If not... that might be a clue.

And, do confirm that the directory and .ini file are readable by everyone

Success on Pi3

After much fiddling I can confirm this does work on the Pi 3.

Thanks for the info Eric E.

The problem for me was putting the file in the correct place. /etc does already exist, but for clarity you have to ssh into the pi to find it.

RE: have the same problem

created file , prusalink boots up but can't connect

[ 0.001809] printk: console [tty1] enabled[ 1.438434] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 36, base_baud = 0) is a PL011 rev2[ 3.159768] systemd[1]: Created slice system-getty.slice.[ 5.120656] cdc_acm 1-1.2:1.0: ttyACM0: USB ACM device

these are my connected devices. I asume mine is ttyACM0

it connects somehow since my mk3s reboots when i reboot pi

Re: have the same problem

The fact that your MK3 reboots when you boot the pi does sound promising.

I would recheck the prusa-link.ini file on the pi to make sure the info from above is actually in there. 

Got it to work

did a reinstall on sdcard and now it works!

RE: 0.5.2 Documentation missing for USB and non Zero Pi

Confirmed that the above instructions work on PrusaLink version 0.6.0 also.

Note: please make sure you  >sudo su  before creating the new folder/file.

Note: once the file is added and you want to reboot - for beta try > sudo reboot --force --force 

Note: If for some weird reason your printer does not register on PrusaConnect on first try - no need to start over. Delete the prusa_printer_settings.ini in the /home/pi folder and reboot the pi. It will start the printer registration sequence again for PrusaLink. Its a good idea to open https://connect.prusa3d.com and leave the tab open in the same browser you open http://prusalink.local/ . In the final registration step of PrusaLink if you have to log-in to PrusaConnect,  the registration menu goes away and you are left with nothing to register and PrusaLink in error mode for the web service. 

RE: 0.5.2 Documentation missing for USB and non Zero Pi

Hi

I think iam stupid...

I installed Octoprint on a Raspberry pi 4 and installed it on my MK3S + via USB. This all works too.

Now I have got access to PrusaConnect and would like to use it. Since I don't have a Raspberry Pi Zero W, I would like to use this with my existing Raspberry Pi 4.

Now I came across your instructions. I created the folder and the file with the specified content via Putty: File /etc/Prusa-Link/prusa-link.ini

I have also adjusted the authorization so that everyone can read it.

How can I now connect the PrusaConnect web interface to my printer?

Thanks for the help.

RE: 0.5.2 Documentation missing for USB and non Zero Pi

Problem solved. Had to install PrusaLink and not Octoprint. I have now run it on a Raspberry PI 3 and connected it to PrusaConnect.

GETTING STARTED – Introduction & Instructions – Prusa3D Forum (prusaprinters.org)

RE: 0.5.2 Documentation missing for USB and non Zero Pi

Works on Zero W and Software 0.6.0

Thanks

Posted by: @eric-e

Documentation should include the fact that other Pi devices do work, and can be connected via USB.

File /etc/Prusa-Link/prusa-link.ini

If the directory and/or file do not exist, just create 'em.  No biggie.

In that file, insert

[printer]

port=/dev/ttyACM0

baudrate=115200

This will enable communication via USB.

If you are feeling particularly neurotic, edit /etc/rc.local

printf 'M117 Starting Prusa Link\n' > /dev/ttyACM0

 

Above works perfectly for a Pi 4 & MK3S+

RE: 0.5.2 Documentation missing for USB and non Zero Pi

How do you create the .ini file?

RE: 0.5.2 Documentation missing for USB and non Zero Pi

Connect with Putty via SSH and Create the File.
go to the Folder etc: cd /etc
Create Folder: mkdir Prusa-Link
Create File with: touch prusa-link.ini
Edit File with: nano prusa-link.ini
Past that in de File and Save -
[printer]
port=/dev/ttyACM0
baudrate=115200

reboot: sudo reboot

RE: 0.5.2 Documentation missing for USB and non Zero Pi

Might need a sudo or two in there for mkdir and touch.  Otherwise spot on, nice post. 

RE: 0.5.2 Documentation missing for USB and non Zero Pi

hey.

i cant connect via SSH. is there any option you need to activate on the sd card before using SSH?

Error Message: "Network Error: Connection refused"

RE: 0.5.2 Documentation missing for USB and non Zero Pi

Yes, you will need to use the Raspberry Pi Imager software advanced settings to allow for SSH.

Posted by: @schrotti

hey.

i cant connect via SSH. is there any option you need to activate on the sd card before using SSH?

Error Message: "Network Error: Connection refused"

RE: 0.5.2 Documentation missing for USB and non Zero Pi

Is there an alternative to Putty for Mac users?

RE: 0.5.2 Documentation missing for USB and non Zero Pi

Might need a sudo or two in there for mkdir and touch.

Can you elaborate on "a sudo or two", I'm not the best with programming so I'm not sure how to do this.