Configuration Bundle 1.11.5 with Octoprint
 
Notifications
Clear all

Configuration Bundle 1.11.5 with Octoprint  

  RSS
ScottW
(@scottw)
Estimable Member
Configuration Bundle 1.11.5 with Octoprint

Upon updating to PrusaSlicer 2.7.0, I also received configuration bundle 1.11.5.

In configuration 1.11.5, all "Print Settings" profiles tagged @MK4 and @MK4IS now default to binary G-Code!  So, even though I have a "physical printer" defined with an Octoprint interface, all of the new Print Settings profiles send it Prusa's proprietary binary gcode -- which is incompatible with Octoprint.

The only obvious solution is to create duplicates (with new names delineating Octoprint) of every Print Settings profile in the bundle, with the binary gcode option disabled.  Since I have two nozzle sizes and need both MK4 and MK4IS, that's (26) new "user" Print Settings profiles:  (10) for MK4IS and (16) for MK4.  What a mess!

Is there a better way? 

And why is the binary gcode option within "Print Settings, Output options" anyway?  This relates to a printer interface capability.  Why is it in Print Settings rather than Printer Settings?  If the binary gcode output option was placed in Printer Settings, each physical printer could set the binary or text option as needed for that printer interface.

Posted : 23/11/2023 8:59 pm
Neophyl
(@neophyl)
Illustrious Member
RE: Configuration Bundle 1.11.5 with Octoprint

Unfortunately that is the way it is.  I agree that it makes more sense to have had the new binary gcode option on the Printer Settings.  Prusa have chosen differently though.

Posted : 24/11/2023 7:47 am
RichM
(@richm)
Active Member
RE:

I agree, PrusaSlicer 2.7.0 defaulting to "Export as binary G-code" is a pain for Octoprint users. A tick box in Prusaslicer settings to set it ON or OFF as default would be nice.

This post was modified 3 months ago by RichM
Posted : 24/11/2023 11:45 am
ScottW
(@scottw)
Estimable Member
Topic starter answered:
RE: Configuration Bundle 1.11.5 with Octoprint

Hopefully there will be an improvement.  This choice (binary vs. text) really belongs in the PRINTER settings, not PRINT settings (or in both, with priority on the PRINTER setting).  

My solution for now:   I hand-edited the configuration bundle to make text gcode the default.  I will have to do that every time a new config is pushed out, but it only took a couple minutes -- and is much better than having to change the setting every time I print or creating a bazillion new Print Settings profiles.

Posted : 24/11/2023 4:13 pm
Nigel Johnson
(@nigel-johnson)
Eminent Member
RE: Configuration Bundle 1.11.5 with Octoprint

I am onboard with the option and the Prusa move to enable it by default for all of their printers, or even for all printers that knowingly support binary gcode, but where is the thumbs up to move this option to the pintER settings where it logically belongs?

This move suggests that every printer with every old firmware ever supported by Prusa  Slicer supports binary code. Bad move. Ender 3's don't. I have a few prusa printers, including an old MINI that has not had a firmware upgrade in a while cuz it just works perfectly for what it needs to do, while my MINI+ does not do that stuff, so I won't be upgrading that printer, ever.

Bad Prusa 🙁

Fingers crossed that this is fixed quickly. My current workaround for now is to clone the print setting option I use 90% of the time and disable it.

Just out of interest, I have MINIs and MK3S+. The default profiles for the MK3S+ is not checked.

Posted : 07/12/2023 7:12 am
ScottW
(@scottw)
Estimable Member
Topic starter answered:
RE:
Posted by: @nigel-johnson

This move suggests that every printer with every old firmware ever supported by Prusa  Slicer supports binary code. Bad move. Ender 3's don't. I have a few prusa printers, including an old MINI that has not had a firmware upgrade in a while cuz it just works perfectly for what it needs to do, while my MINI+ does not do that stuff, so I won't be upgrading that printer, ever.

Actually, Prusa mostly avoids this because their configuration bundle includes a different set of "Print Settings" profiles for each printer.  Select the MK4 or MINI, and you get a set of PRINT profiles with "Binary Gcode" and "Firmware Object Labels" enabled in every single PRINT profile.  Select a MK3, and you get a set of PRINT profiles with "Binary Gcode" disabled, and "Octoprint Object Labels".   But you are correct, it still affects a MK4 or MINI that has not yet upgraded its firmware.

It is needlessly complicated because Prusa chose to place these PRINTER attributes in the PRINT settings, instead of letting them be defined for the Physical Printer.  Of course, I'd be fine if they were in both places -- as long as the Physical Printer settings had priority in defining the capabilities of the printer and print host.

Posted : 07/12/2023 6:42 pm
ScottW
(@scottw)
Estimable Member
Topic starter answered:
RE: Configuration Bundle 1.11.5 with Octoprint

There appears to be GOOD NEWS on this subject in PrusaSlicer 2.7.0, released today!  From the release notes:

The option Export as binary G-code was removed from Print Settings. Instead, there is a new option in Printer Settings named Supports binary G-code so it can be set at printer level. There is also a new global switch in Preferences->Other, which controls whether binary G-code will be generated for printers which support it. It is therefore easy to turn the feature on or off without doing any changes in profiles (#11734, #11873).

 

Posted : 14/12/2023 5:40 pm
ScottW
(@scottw)
Estimable Member
Topic starter answered:
RE: Configuration Bundle 1.11.5 with Octoprint

Sorry, that's PrusaSlicer 2.7.1 (not 2.7.0).  Time to edit post had expired, so couldn't update it!

Posted : 14/12/2023 5:47 pm
Share: