Slicing G-Code curves from solid (not mesh) geometry.

A Former User

@Phaedrux said in Slicing G-Code curves from solid (not mesh) geometry.:

The default gives an .NC files...

thats fusions default extension for g-code btw; but weather or not compatible with RRF is another story.

schneik80

@bearer Using an additive post will default to .gcode

bot

Ahh, they have a "generic FFF" post process.. Gonna see what the toolpaths look like in s3d preview.

schneik80

@bot I have a work in progress post for Duet3D hardware... it's still very rough.
Th Post is attached and here is a link to the github page for future developments: https://github.com/schneik80/ACME-REPRAP-F360Post

ACME-REPRAP.cps

Phaedrux

@schneik80 said in Slicing G-Code curves from solid (not mesh) geometry.:

Try this. Open the Machine Configs from the additive toolbar.
In the samples find a test machine, and drag it to your local folder so you can modify it.
Next, select the local folder, pick the machine and choose the post (1).

This brings up the post library. Filter to Additive (2).
Then select one of the sample posts to use (3).

Thanks. That did it.

bot

Dang the community moves fast. Thanks @schneik80! I'll check it out.

A Former User

@bot said in Slicing G-Code curves from solid (not mesh) geometry.:

Ahh, they have a "generic FFF" post process.. Gonna see what the toolpaths look like in s3d preview.

no ~~G4~~ G2 in sight it seems? oddly enough the post has a setting for allow helical moves which seems less usefull unless they implement vase mode?

bot

@bearer not sure why you'd want g4, but if you meants g2 (curves) then, negative... not a curve in sight. And the resolution that it generates segments at is terrible. Even when loading a detailed mesh, it reduces the resolution. Facets galore. Sigh.

A Former User

@bot said in Slicing G-Code curves from solid (not mesh) geometry.:

@bearer not sure why you'd want g4, but if you meants g2 (curves) then, negative... not a curve in sight. And the resolution that it generates segments at is terrible. Even when loading a detailed mesh, it reduces the resolution. Facets galore. Sigh.

haha, 5AM ... i definitviely meant G2:)

Phaedrux

I'm back and forth in Fusion and Cura constantly when doing prototypes and I can't say the workflow has been an issue. Export STL, import and slice, send to Duet. Frankly it's a breeze compared to the obtuse setup of Fusion. The slicing is very slow as well, and cura isn't exactly fast. The gcode produced isn't anything to write home about. Pretty basic. Lacks a lot of the finesse options of Cura. Dealing with corner cases becomes the most important thing in my opinion. There's nothing there yet that could convince me to switch over to it, and I really don't think they have the commitment and depth of talent there to make it into a true competitor for the existing slicers. But who knows. If they give it the same attention they have given to CAM, there might be a time when it becomes pretty powerful. And I guess anything is possible with the post processing?

A Former User

what he said (except less doubt about talent, but more so on comittment)

gimme true arcs and we'll talk

DocTrucker

Effort would probably be better spent moving away from vectors and to nodes. Have a few different classes of node such as a corner (or must hit) node and path nodes (with a variable must be within x). Then let the controller do the per machine settings rather than the slicer too far away from the coal face.

DocTrucker

...of course what I have just described is one node with a value of 0 or something else...

OBELIKS

Interesting and they added 3mf export (unfortunately only in the Manufacturing space)!
And I like this support structure:

bot

@OBELIKS The support structures were hard for me to understand on a complex model. I had to walk away and laugh, because I thought it was outputting garbage. Seems the supports are trying to "anchor" down edges -- I suspect these supports are lifted directly from Netfabb, but I don't know I've never gotten results from Netfabb in the trial period they gave me.

OBELIKS

In this case it is trying to support the circle above with minimal waste. It is looking at bridges and making them shorter than a value.

gtj0

Just posted...
https://www.youtube.com/watch?v=Yd0l2ZOQQek

Phaedrux

@gtj0 said in Slicing G-Code curves from solid (not mesh) geometry.:

Just posted...
https://www.youtube.com/watch?v=Yd0l2ZOQQek

Ooof. They make it look so easy to use!

gtj0

@Phaedrux said in Slicing G-Code curves from solid (not mesh) geometry.:

@gtj0 said in Slicing G-Code curves from solid (not mesh) geometry.:

Just posted...
https://www.youtube.com/watch?v=Yd0l2ZOQQek

Ooof. They make it look so easy to use!

Yeah. I'm actually in the process of trying print. If I can get back to stable RRF3 release that is.

MegaAndy

I gave it a go earlier with prusa/generic FFF settings. Print came out pretty nice, can see some slight Z banding which may just be my printer/filament (shows up more in the photo due to very bright LED light above the printer)

Found it a bit of a pain to setup and had no indication of print time or a good way of seeing what speeds at different parts of the print. Found it interesting it seems to move in the Z axis while bridging too, not sure what it was trying to achieve with that.

Edit: Also, I had to download an additive post process settings file, I just used the prusa one. https://cam.autodesk.com/hsmposts