Support for RRF/reprap printers#148

Duet wifi and reprap interface printers are currently not supported like mainsail and fluid is

is this suggetion being worked on?

@Matthias Vester it’s not in progress, no. It is planned, we’d like to get on it at some point, but the demand is quite low. This suggestion will have its status changed to “In progress” when it’s being worked on :)

intrested as well!

Tim from Meltingplot has made an open source integration that seems to work quite well. It’s not official yet, not in our setup guide, but multiple Duet printers have been set up with our system using this. More info here; https://github.com/Meltingplot/duet-simplyprint-connector - please let us know if it works for you!

Looking forward to this. I just set up a VisionMiner 22IDEX v3, which has a Duet board.

The Meltingplot integration doesn’t seem to provide any benefits over a USB connection to a Duet3D controller with Octoprint. There are still these features missing:
-PSU Control
-GCode Macros / Scripts [not yet implemented by Simplyprint.io for Duet]
-GCode terminal [not yet implemented by Simplyprint.io for Duet]
-Receive messages from Printer in Simplyprint.io [not yet implemented by Simplyprint.io for Duet]

Well, except for letting you use your printer with SimplyPrint, giving you and your printer 30+ features that not Duet nor OctoPrint offers. If you’re fine with what DWC offers at the moment, even the fully released Duet integration probably won’t satisfy you - just to meet expectations - and that’s alright. But if you want AutoPrint, print queue, native remote monitoring, camera-based AI Failure Detection, built-in cloud based slicer and much more, that’s why you may want to use SimplyPrint, even without something like Macros, Terminal, etc.

That’s what I’m saying: Octoprint already works with Simplyprint. I’m already a paying customer, so no need to persuade me.

Interesting! If you use SimplyPrint via OctoPrint for a Duet-based printer, where do you host OctoPrint? Perhaps we need to add that as an official guide. I moreso thought it was the good old “why use SimplyPrint if you can use OctoPrint” we had going here heh.

The idea of our more direct integration with Duet, based on the meltingplot connector, is to make it easier, not require the use of OctoPrint and provide a more direct and native integration.

The Meltingplot Duet Simplyprint Connector requires a PC or Raspberry pi anyways, so running Octoprint on a pi with the Simplyprint Plugin and communicating with Duet3D over USB serial was the most straightforward solution to me. This might be more overhead on the pi, but is a familiar GUI that provides low-latentcy manual overriding if necessary and access to additional Octoprint plugins.
I’m not intending to confuse Octoprint (local 3D printing host) with a cloud service competitor like Obico (formerly Spaghettidetective).

You’re right that you’d need hardware in both cases (except when running the Duet that I forget what’s called that isn’t “single board” but has a Pi or a Pi-like device?). So if it works and it poses no general limitations; go for it! What printer are you powering this way? Native Duet or modded?

Generally we try to make direct integrations to not have limitations, like there would be if we just did Klipper via OctoKlipper, or Bambu via the Bambu Lab OctoPrint plugin. I’m not too familiar with the Duet plugin, but I imagine that down the line - if not already (with our Integration on our GitHub, not the original Meltingplot version), we, and our users, will be better off with the non-OctoPrint way. But for now, until we release the direct integration, a guide for using Duet via OctoPrint may be a good idea if it works well.

Please do let us know what works and what doesn’t, and how the experience generally is!