Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
For several years I've had a workflow that upgrading to 2.9.3 has screwed up.
Normally I import my STL files to PrusaSlicer, slice them, then hit the button to upload to OctoPrint on my Pi that controls my Prusa printer. I prefer using OctoPrint in a browser, since I access it from several computers and trying to do things one way on one computer and another way on a different one is confusing to me.
I upgraded to 2.9.3. I see the "Physical Printer" tab at the top and log in. I see my OctoPrint web page. Okay, nice for a lot of people, but not helpful for me, especially since the upload function no longer works. I click it and get a red error box message that specifies the name of the physical printer, the name of the file it's trying to upload, and it says, "ERROR." Nothing more, no explanation, just, "ERROR."
So, nice, I can use OctoPrint in the slicer, but I CANNOT upload to it like I could in the past. I checked my physical printer list and it's still there - but it won't just send the GCode directly to the printer anymore.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
This is unfortunate, however since PS 2.4 has been the rule not the acceptation, your going to to see these kind of changes in the Future, based on the understanding use of new users that had no clue, of what was possible in the past. The company aims to make money, not make past users happy with the state of of things.
Regards, if your not active in the state of the matter then you have no say so in the matter.
RE:
Did you check the config dialog for your physical printer in PrusaSlicer if all the values for transfer to your printer are still correct, e.g. IP address, API key, Host type?
When I open the Slicer it has one of the standard printer profiles selected, not one of my configured physical printers. I have to either open an existing project that I have printed before or I have to select one of my configured physical printers in the dropdown menu to get it right.
To clarify: I do not use the web page for OctoPrint in the slicer, I use my browser for OctoPrint. But that works with PrusaSlicer version 2.9.3 like it worked before.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
To clarify: I do not use the web page for OctoPrint in the slicer, I use my browser for OctoPrint. But that works with PrusaSlicer version 2.9.3 like it worked before.
So you are getting it to do this (upload to OctoPrint) in 2.93? Just verifying that. Like you, I prefer to use my browser. I'm just double-checking, so I'm clear you're saying it is possible, before I spend time trying to mess with it.
When I open the Slicer it has one of the standard printer profiles selected, not one of my configured physical printers. I have to either open an existing project that I have printed before or I have to select one of my configured physical printers in the dropdown menu to get it right.
So counting on the profiles I've set up for physical printers no longer works. I can't just open PS and expect it to communicate properly with my printer/OctoPrint unless I load a project I used previously? (If so, since I save GCode, but often don't save the project, it'll be easiest to downgrade to 2.92, save a default project using my physical printer, and then re-upgrade to 2.93 and, when I start PS, load that project first, then I can switch over to my new project and it'll read the right info and work with OctoPrint?)
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
Yes, I printed this a few days ago with version 2.9.3. No, it is not necessary to load a previous project for this. I just sometimes find it easier and faster to use an earlier project and just replace the stl file in it and save it under a new name than to start with an empty project and check all the settings again and again. When I start PrusaSlicer it has one of the standard printer profiles active, not one of my existing physical printers. So the bottom right button for upload is not there. After I have selected one of my physical printers, the upload button appears and everything works as before. So selecting one of the existing physical works as well, they are just not loaded automatically.
RE:
To Bad I can't just Post my opinion any longer, Prusa Has deemed me a threat, compared to the more delicate users that make them money, and have arrived.
The community is in a very poor State, perhaps they deserve it.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
To Bad I can't just Post my opinion any longer,
In all honesty, I came here to get help to make my program work, so opinions, especially in a thread asking about being able to do something, are not a help, and, perhaps, even a hinderance.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
When I start Prusa Slicer, the default printer is the one I am trying to upload to. It's my default. And it defaults to the last filament I used. After reading your last reply, about changing to the physical printer, I went back to PS, tried the upload again, expecting it to fail (it did), then changed to another printer, then back to the one I wanted to send it to. It worked, without a problem. Then I quit PS, restarted it, and the physical printer was still set for my printer. I imported an STL and exported directly to my printer.
I think most will get the sense of what happened, but let me clarify (this is the TL;DR part): I did that 1st test, expecting it to fail, to verify it was still failing. Then I switched printers and switched back and it worked - and worked again on the next startup. This tells me that whatever the problem in 2.9.3, it's only there at the start and once you change to any printer and back to the physical one to upload to, it works. The change is also preserved after quitting and restarting. I just wanted to be sure the ONLY factor I changed from getting the error until seeing it work was changing to another printer and coming back to the one I wanted.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
sorry you weren't able to understand this point of view, ill make a point of not offering help to you in the future.
no further communication necessary.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
sorry you weren't able to understand this point of view, ill make a point of not offering help to you in the future.
I'm not saying, at all, that I don't understand the point of view. I am saying that in the context of my first post, it was not useful information. Some of your posts have been a big help, but there was no need or reason to editorialize instead of providing a solution.
no further communication necessary.
I find that a rather self-serving declaration. "I've said my piece. I don't want to hear another point of view."
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
I too am having this problem. 2.9.3 is failing with
Could not connect to OctoPrint: Couldn't connect to server: [Error 7]
. My 2.9.2 installation still works. I made NO configuration changes. Is any more logging available about this?
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
Try changing your physical printer to another and then back. Check the connection info in the config dialog for the physical printer that all the info is correct, i.e. host type, IP address, API key.
I have been using version 2.9.3 on my two printers for last week without a problem.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
Tried both, config looks fine (as you'd expect since 2.9.2 still works) and changing printers had no impact.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
What happens when you use the "Test" button in the config dialog of your physical printer?
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
The same error I posted above.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
Which operating system are you on? Windows, MacOS or Linux?
You could also try to create a new physical printer for your printer, e.g. for a different nozzle size and see if that works. I did this a few days ago when I needed to print some things with a 0.6mm nozzle. And this worked without a problem on both of my printers. My OS is Debian Linux.
RE:
Googling for your error message seems to indicate a network problem. Can you ping the IP address of the OctoPrint system for your printer?
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
Which operating system are you on? Windows, MacOS or Linux?
You could also try to create a new physical printer for your printer, e.g. for a different nozzle size and see if that works. I did this a few days ago when I needed to print some things with a 0.6mm nozzle. And this worked without a problem on both of my printers. My OS is Debian Linux.
MacOS. I can give that a try, but I don't hold out hope.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
Googling for your error message seems to indicate a network problem. Can you ping the IP address of the OctoPrint system for your printer?
Yes. I can ping. I can access OctoPrint via the browser. I can access via PrusaSlicer 2.9.2. 2.9.3 did _something_ to break this. It might be broken for everyone, but it's broken. Which is why I asked if there was any more logging available. This seems to be a very brittle part of the system (based on past experiences) where they could give far more clear failure information or at least provide additional logging.
RE: Upgraded to PrusaSlicer 2.9.3 - Can't Upload GCode to OctoPrint anymore
Can you start the binary from a terminal? When I do this on Linux I can see all the logging of the binary in that terminal. I have no experience with MacOS and don't know if it works the same way there.