Skip to content
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

Internal error when using Mainsail/Fluidd physical printer #10210

Closed
1 of 2 tasks
TheEnigmaBlade opened this issue Mar 31, 2023 · 39 comments
Closed
1 of 2 tasks

Internal error when using Mainsail/Fluidd physical printer #10210

TheEnigmaBlade opened this issue Mar 31, 2023 · 39 comments

Comments

@TheEnigmaBlade
Copy link

TheEnigmaBlade commented Mar 31, 2023

Description of the bug

Attempting to use a physical printer with host type of "Mainsail/Fluidd" results in any attempts to connect to the printer failing.

  • Pressing the "Test" button results in an "Unhandled unknown exception" and terminates the application with the error below.
  • Uploading to the printer results in the error below but does not terminate the application.

image

image

image

I have tried both editing an existing physical printer functioning fine in Octoprint mode and creating a new physical printer.

Project file & How to reproduce

  1. Create or edit a physical printer.
  2. Set printer type to "Mainsail/Fluidd".
  3. Press "Test" or upload to printer.
  4. Get error.

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.6.0-alpha6+win64

Operating system

Windows 11

Printer model

Voron 2.4 w/ Mainsail

@cpasoft
Copy link

cpasoft commented Mar 31, 2023

Confirmed... I also have that error

@VagnPetersen
Copy link

Confirmed... I also have same error.

@iqubik
Copy link

iqubik commented Mar 31, 2023

also have this error

@pauluchin
Copy link

I also have this error :(

@joshua70448
Copy link

I'm also having the same error with Mainsail v2.4.1, using both host name and IP address.

@Jonibygg
Copy link

Jonibygg commented Apr 1, 2023

Same here

Version of Prusa
2.6.0-alpha6+Mac Universal

Os
iMac MacOs Ventura 13.2

@b4rRa
Copy link

b4rRa commented Apr 1, 2023

100% exact the same issues with 2.6 alpha6

Mainsail v2.5.0; fluidd v1.23.4; Klipper v0.11.0-157-g36e0afea

@TypQxQ
Copy link

TypQxQ commented Apr 1, 2023

Same here.
URL by IP. Tried with and without starting http and trailing /

Version: 2.6.0-alpha6+win64
Build: PrusaSlicer-2.6.0-alpha6+win64-202303311519
klipper: v0.11.0-159-gfec7ddd8
moonraker: v0.8.0-30-g110cbd1
mainsail: v2.5.0

@TravisWilder
Copy link

When I select Mainsail PS is setting up in the INI Duet.
It seems there are wrong offsets used

@CloudYeti
Copy link

CloudYeti commented Apr 1, 2023

I have the same issue on MacOS

Version: 2.6.0-alpha6+linux+x64-GTK2
Build: PrusaSlicer-2.6.0-alpha6+linux-x64-GTK2-202303311518
klipper: v0.11.0-146-ge2d7c598
moonraker: v0.8.0-30-g110cbd1
mainsail: v2.5.0

@LazeMSS
Copy link

LazeMSS commented Apr 2, 2023

Confirmed

@Dark-Noir
Copy link

+1

@orion23rigel
Copy link

Same issue here

@tildeyy
Copy link

tildeyy commented Apr 3, 2023

+1, macos 13, current klipper release (can't remember exact version but shouldn't matter)

As a workaround for everyone, setting the gcode flavour to klipper still works. And if you select "octoprint" as the host and point it to the IP of the klipper server, that will allow gcode uploading. I've been using that workaround since I started using klipper. Technically I think that feature (imitating an octoprint server) is actually part of moonraker, but I'd imagine 99% of people using klipper also have moonraker installed.

Cheers.

@lukasmatena
Copy link
Collaborator

lukasmatena commented Apr 3, 2023

Thanks for the reports. Can you please try the following build and report back? It should be fixed.

PrusaSlicer-2.6.0-alpha6+1-lm-mailsail-fix-win64-g9346cf119-202304030833
PrusaSlicer-2.6.0-alpha6+1-lm-mailsail-fix-MacOS-universal-g9346cf119-202304030843
(No Linux build, sorry.)

@VagnPetersen
Copy link

For me it is working now.
Minor thing is that pressing the "test" button returns this: "Connection to OctoPrint works correctly"

@Jonibygg
Copy link

Jonibygg commented Apr 3, 2023 via email

@TravisWilder
Copy link

Thanks for the reports. Can you please try the following build and report back? It should be fixed.

PrusaSlicer-2.6.0-alpha6+1-lm-mailsail-fix-win64-g9346cf119-202304030833 PrusaSlicer-2.6.0-alpha6+1-lm-mailsail-fix-MacOS-universal-g9346cf119-202304030843 (No Linux build, sorry.)

MacOS (M1)
Setting changeable - test works .. ini is now set to "host_type = mainsail"

@Jonibygg
Copy link

Jonibygg commented Apr 3, 2023 via email

@TravisWilder
Copy link

M1 Ultra 13.3
PS Alpha 6-1
Voron V2 (Klipper + Mainsail 2.5.1 + moonraker v0.8.0-30-g110cbd1)

@GAZ082
Copy link

GAZ082 commented Apr 3, 2023

Thanks for the reports. Can you please try the following build and report back? It should be fixed.

PrusaSlicer-2.6.0-alpha6+1-lm-mailsail-fix-win64-g9346cf119-202304030833 PrusaSlicer-2.6.0-alpha6+1-lm-mailsail-fix-MacOS-universal-g9346cf119-202304030843 (No Linux build, sorry.)

Are we going to have a Linux release of this fix?

@lukasmatena
Copy link
Collaborator

@TravisWilder and @VagnPetersen: Thanks.

@GAZ082 It will be fixed in the next 2.6.0 alpha/beta. You can use OctoPrint print host until then.

@auditor3d
Copy link

auditor3d commented Apr 3, 2023

They have the drop down list out of order and or missing information. workaround until an updated alpha for linux... use the Octoprint dropdown option and input your mainsail/klipper IP or hostname and test.

@churls5495
Copy link

Thanks for the reports. Can you please try the following build and report back? It should be fixed.

PrusaSlicer-2.6.0-alpha6+1-lm-mailsail-fix-win64-g9346cf119-202304030833 PrusaSlicer-2.6.0-alpha6+1-lm-mailsail-fix-MacOS-universal-g9346cf119-202304030843 (No Linux build, sorry.)

Win64 version fixed the issue for me.

@tyrscgm
Copy link

tyrscgm commented Apr 5, 2023

Confirmed... I also have same error. with Mac osx Ventura

@mpaw
Copy link

mpaw commented Apr 7, 2023

Thanks for the reports. Can you please try the following build and report back? It should be fixed.

PrusaSlicer-2.6.0-alpha6+1-lm-mailsail-fix-win64-g9346cf119-202304030833 PrusaSlicer-2.6.0-alpha6+1-lm-mailsail-fix-MacOS-universal-g9346cf119-202304030843 (No Linux build, sorry.)

Fixed the issue for me on MacOS Ventura (M1 Pro). Although the popup says Octoprint instead of Mainsail/Fluidd

image

@iqubik
Copy link

iqubik commented Apr 7, 2023

@cristianmur
Copy link

Todos tenemos el mismo error, lo implementan supuestamente para mejorar pero te fastida todo

@pauluchin
Copy link

here everything works normally with the correction

@GAZ082
Copy link

GAZ082 commented Apr 10, 2023

Todos tenemos el mismo error, lo implementan supuestamente para mejorar pero te fastida todo

This has already been fixed. This is the release:
#10210 (comment)

No linux version tho :(

@e-dreyer
Copy link

e-dreyer commented Apr 13, 2023

Can confirm that this happens to me when I press the "test" button. Otherwise, the settings are saved and the same error occurs when I try to upload, and the PrusaSlicer crashes and closes. I am running Alpha 6.

Edit:

I just tried the supplied build above, but just get an endless "resolving address" even though the test is successful. The app however no longer crashes.

@lapja
Copy link

lapja commented Apr 24, 2023

When trying to upload I get: Error uploading to print host:
(1): expected value

@Darkknight33
Copy link

I saw this issue when I had Octoprint selected as the destination in the A6 build. Test worked, however, would just say unresolved address on attempt to upload. Selecting Mainsail crashed the slicer. Using the testfix build, it works properly. Just uploaded a file.

lukasmatena added a commit that referenced this issue May 13, 2023
… UI fixes ('OctoPrint'->'Mainsail/Fluidd')
@lukasmatena
Copy link
Collaborator

Should be fine in 2.6.0-beta1. Closing.

@TacII
Copy link

TacII commented Jun 12, 2023

Problem is back again in 2.6.0-RC1+Win64-2002306091137

@GAZ082
Copy link

GAZ082 commented Jun 12, 2023

Working fine in linux.

Version: 2.6.0-rc1+linux-x64-GTK3-202306091240

@Jan-Soustruznik
Copy link
Collaborator

Problem is back again in 2.6.0-RC1+Win64-2002306091137

Hello, @TacII , could you share your 3mf file, please?

@TacII
Copy link

TacII commented Jun 16, 2023

Scratch that! I think the upgrade changed the default printer to one with old settings that probably didn't work. It works now.

@lukasmatena
Copy link
Collaborator

@TacII Ok, thanks for the heads-up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests