-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot select PrusaLink for new physical printer #13286
Comments
The same for MINI.
The forum discussion with steps to reproduce and screenshots: https://forum.prusa3d.com/forum/prusaslicer/cannot-chose-octoprint/#post-719907 |
Same for me, PrusaLink no longer shows up in the host type dropdown. (see image.) I have to export gcode to desktop then upload+print from the Prusa Connect tab in prusaslicer. Selecting host type PrusaConnect always gives me a forbidden error, but thats a different issue. PrusaSlicer2.8.0+win64 |
Thanks, reproduced. It will be fixed in the next release. |
Fixed in 2.8.1-rc1. Closing. |
Description of the bug
I have the newest version of PrusaSlicer (see details below) and firmware version 6.0.4+14924 on my MK4.
I wanted to add a new physical printer without input shaping, but I can only select PrusaConnect as the option to connect to the printer. PrusaLink is missing.
When I try to add a new physical printer with the input shaper profile, I do have the option to select PrusaLink to connect the printer.
See the attached screenshots.
PrusaSlicer
Project file & How to reproduce
Not relevant I think, but:
Click on the gear on the right to add a physical printer
Select "Original Prusa MK4 4.0 nozzle" profile
Try to select PrusaLink (it's not there)
Click on the gear on the right to add a physical printer
Select "Original Prusa MK4 Input Shaper 4.0 nozzle" profile
Try to select PrusaLink (it's there)
Prusa.3mf.zip
Checklist of files included above
Version of PrusaSlicer
2.8.0+MacOS-arm64
Operating system
macOS Version 14.1 (Build 23B74)
Printer model
Prusa MK4
The text was updated successfully, but these errors were encountered: