RE: Prusa MK4 & Octoprint
Instead of bugging the plugin developer, bug the Prusa developers to implement it in the firmware the same way as for the MK3. Same effort for you, perhaps more promising result. 😉
RE: Prusa MK4 & Octoprint
I don't know why? That "feature" is not an "Issue" related to the MK4 itself lol
RE:
Then why does it work on the MK3 and not the MK4? As far as I know (not owning one) it works on the Mini that has similar hardware as the MK4. This should not be the job of one plugin developer but the firmware developers (plural) providing the API for all the third party software. And there are other plugins that rely on this API.
RE: Prusa MK4 & Octoprint
?!?!?!
Different hardware, different firmware???
RE: Prusa MK4 & Octoprint
On the firmware page it says "Firmware for the Original Prusa MINI, Original Prusa XL and the Original Prusa XL 3D printers by Prusa Research." And as I said, as far as I know it works on the Mini.
RE: Prusa MK4 & Octoprint
You're trolling aren't you?? Different hardware! Different firmware!!! How can you compare the mini and a mk4 even if they share a similar looking LCD?
RE: Prusa MK4 & Octoprint
I am not trolling. I just think that it is not the job of some plugin developer to fix the problem. That is all.
RE: Prusa MK4 & Octoprint
It's EXACTLY the plugin's developer job to ADAPT to different hawdware variations...
RE: Prusa MK4 & Octoprint
Yes, this way we wind up with a fix for the TP-Link plugin, a fix for the Tasmota plugin ... you see what I am getting at??? 🙂
RE:
Yes, backwards compatibility to old hardware, but I guess that's on the bottom of their list to fix....
Specially when Prusaconnect/Prusalink is there to "compete" vs Octoprint.
RE: Prusa MK4 & Octoprint
We as purchasers of Prusa printers should feel more "entitled" towards Prusa fixing something or providing a feature than toward some hobby plugin developer who does this in his free time and should in no way feel obligated to fix anything. That was my whole point.
RE:
It's not on the plugin side to fix but on the MK4 Firmware side.
The issue is the MK4 not using M73 & M117 for reporting back to host over serial.
If the MK4 does not communicate properly, there is no way to get that information from the printer and into the plugins.
You can vote or contribute to this ticket here to get it resolved:
https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/189
RE: Prusa MK4 & Octoprint
Hi, I'm a FOSS maintainer, and a developer advocate, as well as an employee for one of the largest developer resources in the world.
Prusa's firmware is open source. If it's "missing" something, then anyone is enabled to branch and PR a change to the firmware. Prusa can be asked to do it, but just as well, Octoprint and plugin devs can just do it themselves.
As I mentioned, I'm a FOSS maintainer. If the things I maintain end up broken due to upstream changes (in my case, kernel/OS changes), I have the same options. I can ask upstream to address it, or, I can fix my service to fall in line with the upstream changes. Similarly, when someone depends on my service and isn't compatible with a change I make, they can ask me to implement something, or do it themselves.
There's not a strong "right" or "wrong" here, in terms of who and how it should be fixed. My personal philosophy is that change and progress warrant the cessation of "backwards compatible at all costs" type thinking. Prusa has in a sense moved on from Mini and MK3, and developed the new firmware. If something isn't working with it, my personal thinking is that octoprint and plugin devs are the ones who need to move, not Prusa. They're more than capable to extend the firmware or add an API for their use all they want. If the developer of the plugin isn't going to maintain their plugin as the world continues to move, they should relinquish the maintainer status to someone who will.
I am not trolling. I just think that it is not the job of some plugin developer to fix the problem. That is all.
RE:
I build software for an independent print farm running exclusively Prusas. MK3s work great right out of the box. MINIs had a little headache with figuring out the M876 P1 command to initiate the host communication. As it's been explained many times in this thread MK4s work, but they are missing key host functions (filament runout, crash detection, etc...) that buyers should expect because previous models support them.
While it's true there isn't a party that should be wholly responsible for plugin implementation and maintenance. Prusa did support a whole lot more with their host communication over serial from the MINI vs the MK4. I really really hope they add the same features into the MK4 API because they run the same firmware, and it shouldn't be too hard to translate the same features, but I'm not a firmware developer and I say "too hard" relatively because they're a larger organization. We ordered 10 MK4s with the expectation that the firmware was going to support the host commands, but now these MK4s are either going to collect dust until Prusa releases compatible firmware or they're going to run from USB drives which poses a huge headache for our inventory quantity management.
In time if the features aren't provided and our MK3s become antiquated I can see our farm transitioning to Bamboo printers.
RE: Prusa MK4 & Octoprint
Thanks; I bought the assembled version this time and put it the Průša enclosure without really studying it first
RE: Prusa MK4 & Octoprint
So what's Prusa's plan here?
Step 1: Design a crappy board that shares the wifi and usb serial connection so you only can use one of both
Step 2: Get a perfectly working firmware and butcher it until stuff doesn't work
Step 3: make sure to mention Prusa at least twelve times per square inch of every visible piece of the products surface and software UIs
Step 4: blame every issue on somebody else
Step 5: ???
Step 6: Profit
RE: Prusa MK4 & Octoprint
I'm happy to report that the developer of this plugin fixed this specific issue on the Mk4 and it is addressed in the latest release candidate.
I have a smart switch for the power of my Prusa and using an Octoprint Plugin ( https://github.com/jneilliii/OctoPrint-TPLinkSmartplug) , it can detect when the printer completes a job and after and idle timeout period it will turn off the printer automatically from the smart switch. This function is broken as the MK4 does not report back the idle state the same way the Mk3 does.
Can you elaborate on this "feature"?
....and it does not turn off my printer automatically when it is idle after a print job completion.
RE:
I love Octoprint. I use it's core functions. I monitor the startup progress, tweak the temps on the fly, etc. And I use the pause functionality which moves the printhead to an easy to clean location when needed, then resumes properly. I also use a couple of plugins, Arcwelder whick is nice but I coudl live w/o it. But one plugin that's very important to me is the Cancel object plugin.
I don't care who's responsibility it is to fix it. Although I believe the issue is the firmware. And as cool as it is to say "... it's open source fix it yourself...", well that's not really a viable option for most of us. Not me anyway.
I like Octoprint enough that I'm seriously considering bailing on my MK4 purchase if it's not going to work with it.
Are there any other conversations going anywhere on this topic? Do the Octoprint developers know?
RE: Prusa MK4 & Octoprint
What discord server did you come from? It's obvious you came here with an axe to grind.
So what's Prusa's plan here?
Step 1: Design a crappy board that shares the wifi and usb serial connection so you only can use one of both
Step 2: Get a perfectly working firmware and butcher it until stuff doesn't work
Step 3: make sure to mention Prusa at least twelve times per square inch of every visible piece of the products surface and software UIs
Step 4: blame every issue on somebody else
Step 5: ???
Step 6: Profit
RE: Prusa MK4 & Octoprint
It's EXACTLY the plugin's developer job to ADAPT to different hawdware variations...
I'd like to interject here; it's not our job, but our choice if we want to bend over backwards to support some random new firmware that is broken in so many different ways.
As already stated I've patched my plugin for this random new temperature report coming from mk4 in TP-Link smart plug plugin, but wouldn't even have known about unless someone warned me about it. You can't expect developers of OctoPrint or its plugins to program around every single device produced in the worldb unless you want to start paying the bill for that?