MisterPi

Can we count this as a bug or perhaps a suggestion for improvement? It's pretty useless like it is now...

I have searched a while to see if anyone else has reported this, to no avail (guaranteed not an exhaustive search). I have two printers installed (and working) under Cura 4.5 running on MacOS 10.13.6 (High Sierra). In neither case are the machine settings resizable, making it very difficult to edit before & after gcode. Am I missing something or is it just me? Thanks.

Problem (if you want to call it that) solved. I could see no reason to have prefixes on the gcode files because I push them straight to the Pi with your wonderful plugin. Thanks!

If this has been addressed elsewhere, just say "RTFF" (forums) and I will. The Octoprint plugin has been working wonderfully pushing gcode files to my Octopi. Could not be happier. I added anew printer and Pi with an additional instance of Octoprint to my network and a new printer profile. I connected them and cant print without issues. One question: The filename that the plugin uploads is now prefixed with "MSMV2E3D_" whereas on the other printer, it is prefixed with "1_". Is this something I can change? If yes, how? I have looked and not found anything yet. Thanks from a fellow shelter-in-placer. --jm

At the risk of being active on too many forums simultaneously, a work colleague of mine (MUCH younger) was waxing rhapsodically (insert other, more over-the-top term here) about your creation so I have been searching high and low for it. Iread your other post and will follow whatever guidance you have for me. Now that I have read the whole message, I know what to do. Thanks for all your hard work here.

Happily running Cura 4.2.1 on a Mac (OS X 10.12.6). Using Octoprint on a Pi for a year or so and learned about the OctoPrintPlugin the other day. It does not show up in my Marketplace as I searched and came across this thread. Per a post above, downloaded "OctoPrintPlugin-v6.0.0-2019-07-18T12_32_22Z.curapackage" and dropped in onto Cura. Got the popup that it would be installed on restart. Restarted. Looked into Cura.log and found the following entry: Deleted all of what had not been installed (.../Library/Application Support/cura/4.4/plugins/OctoPrintPlugin/*). Downloaded the latest version of the repository into .../plugins/OctoPrintPlugin/, changed subdirectory name from "Cura-OctoPrintPlugin-3.5" to "OctoPrintPlugin". NOW under printers, I see the Connect OctoPrint button (!). However, my Octoprint instance is not discovered. So I enter the IP address. The settings dialog appears briefly and disappears. After tinkering a bit, I get the dialog to stay open long enough to request an API key, which Octoprint grants and Cura crashes. Enter details in the crash reporter which does not close when I click Send. Eventually I close the crash reporter. Re-open Cura and am told that my profile is corrupt (I only have one printer) and would I like to reset? I DO NOT say yes as I do not want to re-tune my Cura settings yet again (screen cap below). Cura continues to function, as near as I can tell. I re-loaded a stl previously sliced and it told me 1hr 40min to print which was over twice what it has said last time I had printed it. Loaded a new stl (8mm x 20mm solid cylinder) and got a print time of 10min. Things slice and print but the Cura crashes and it's clear I am going to do what nobody wants to do and start from scratch. But this time maybe I'll RTFM and use material profiles correctly. *sigh*