No Duet and Octoprint direct support <rant>

[RoboDLC]

Is a glaring omission.
Sure, some of the high-end printers have built in networking, but the majority of us do not have those printers, if S3D is really only being designed for high-end printers (which have their own slicers), then I can understand that, the rest of us can just go use CURA.

The vast majority of us use Octoprint to network our printers. Omitting support for Octoprint is whack, who decided that?
Duet controllers are another really large part of the market, sometimes built into high-end printers too. Another low-hanging fruit ignored.

If your next release with anything else new for V5 comes out, network support for these had better be on it if you want to be relevant.
The V5 upgrade is about the cost of a dinner out with the family, so its cost is trivial, but I am tempted to get a refund just to make a statement. "We waited three years for this?" I have not yet found any compelling reason for those more cash-strapped to get V5.

be well, (do better),
DLC

[onyxius]

Uggg I just went to start a test print only to find out that I cannot even connect to my octoprint with the new version. all 3 of my printers are on octoprint. I sure hope this get's added VERY soon.

[Theboz1419]

Uggg I just went to start a test print only to find out that I cannot even connect to my octoprint with the new version. all 3 of my printers are on octoprint. I sure hope this get's added VERY soon.

I have no issue connecting to Octoprint with the new version. Just save the file G.code on the computer that has S3D and then transfer to Octoprint by uploading it. It only takes a couple seconds.

[S3D-Jason]

I know the team is already tracking this as a request for future versions.

That being said, I know many of our customers just add a single line to their post processing script to upload the build files automatically to Octoprint or Klipper, so that is also an option if you want something working right away.

[RoboDLC]

I know the team is already tracking this as a request for future versions.

That being said, I know many of our customers just add a single line to their post processing script to upload the build files automatically to Octoprint or Klipper, so that is also an option if you want something working right away.

There are strings that can do this in the "post processing" section of the "Scripts" tab. I have NO IDEA how this works or how someone figured it out, but they did. Because, again, this relies upon the hidden scripting engine of S3D doing things that S3D does not tell us about or explain. Have I said "it would sure be nice to have the scripting engine explained to us with all that it is capable of doing"? I think so.

This is what I did with 4.x, and it works with 5.0 as well:
curl -k -H "X-Api-Key: 0D0C004E41CB46ADBD1FE71E3E08AC34" -F "select=true" -F "print=true" -F "file=@[output_filepath]" "http://192.168.1.221/api/files/local" {STRIP "; postProcessing"}

Put your own URL in there and copy/paste the API key from Octoprint. This is clunky and somewhat "spotty" in functionality on S3D 4.x. It seems to work better on 5.0 - But still, clunky.

Something similar works with Duet boards (maestro is the URL name of my Duet printer):
curl -F "file=@[output_filepath]" "maestro/rr_upload?name=gcodes/[output_filename].gcode"
curl "maestro/rr_gcode?gcode=M32[output_filename].gcode"
curl "maestro/rr_disconnect"

This works, but is also clunky and make sure your gcode file does not begin with a number or that will barf. Also, errors get thrown on the Duet with this, but it will work. As a side-effect of the error thrown on the Duet, it will print the actual model print time out when the print completes.

I still think that this would be better done as part of the UI in S3D, that would make it look like you meant it to work.

be well,
DLC

[Jordanbourns]

Share with us this line, you have mentioned a few times but never said. Whats the code Jason?

[S3D-Jason]

Share with us this line, you have mentioned a few times but never said. Whats the code Jason?

It's pretty similar to what was mentioned above. For example, here's what I use on my computer for uploading to OctoPrint:
curl -k -H "X-Api-Key: YOURKEYHERE" -F "select=false" -F "print=false" -F "file=@[output_filepath]" "http://10.0.0.1:5000/api/files/local"

Replace your API key, along with the IP address (10.0.0.1) and port (5000) in the command above, then it will upload the file to OctoPrint whenever you are ready to export it from S3D.