Fusion 360 FDM/FFF Slicing



  • I posted my post-processor. You can find it here:

    https://github.com/LittleHobbyShop/RRFPostProcessor

    Thought I'd share here that Fusion 360 March update brings FDM/FFF slicing in the Manufacture environment.

    https://www.autodesk.com/products/fusion-360/blog/march-2020-product-update-whats-new/

    It's sparse at the moment but usable. I have managed a quick test cube. There are plenty of settings available but obviously it's just the start and there are omissions and probably bugs too.

    The most difficult part for me was start and stop gcode, it's not available in the format we're used to yet. It can be adjusted via the already existing post-processor system in Fusion but it's not easy. I'm sure this will change in time given the number of FFF users that will try this and we'll have the usual textboxes before long. Likewise, there are no entry points for layer change or tool change scripts.

    Fortunately, thanks to RepRap Firmware this will be easier to overcome than any other system I'm aware of. Almost all of my start and end scripts are already in firmware on the Duet board and I used an existing post-processor for the BigRep (found in the Fusion 360 post library) and tweaked it.

    So, if you intend on having a go with this, get moving your start and end routines from your slicer into the start.g and stop.g files in RepRap Firmware and add M0 to your end script in the slicer.

    I'll have another look at the tweaked post-processor I used and see if I can clean it up enough to share here. Caveat, I've never written a post-processor before so downloader beware!





  • Regarding the post process config. I grabbed the prusa one from here https://cam.autodesk.com/hsmposts (filter to additive) and it outputted straight to gcode, I checked the gcode and all I did was change a g28 z0 to just g28, it seemed to home twice anyway so I think no edits needed.

    That said like you mention it's got a long way to go to be worth using



  • I posted my post-processor. You can find it here:

    https://github.com/LittleHobbyShop/RRFPostProcessor

    Early changes to generic fff example:

    • Removed all pre-print homing, these should be added to start.g.
    • Replace deprecated M107 with M106 S0.
    • Replace deprecated M104 & M109 with G10 commands (untested for tool changes).
    • Removed other functions start and end scripts.
    • Append M0 to execute stop.g at end of job.


  • Nice!

    For best compatibility, you might want to add H1 to the M0 to keep the heaters on. This way cancel.g or stop.g can decide whether to turn them off or not.



  • @gtj0 Good shout, I'll update it later.



  • Update 11/03/2020

    Added post-processor properties

    • Optional layer change macro property. Executes a macro at start of each layer. Insert full path to macro as per M98 in post-processing properties window. Useful for timelapses etc.
    • Minimum layer to run layer change macro, default 2. Layer change macro will execute at the start of this layer and every layer thereafter.
    • Optional post-heat macro property. Executes a macro after heating but before print start. Insert full path to macro as per M98 in post-processing properties window. Useful for additional wipe or purge routines.

    @gtj0 Unfortunately adding H1 to M0 is pointless at the moment, the heaters are turned off automatically by the toolpath generator at the end of the routine which can't be edited. Much like the purge line. There may be a workaround, I'll keep at it.



  • @littlehobbyshop Great update! I guess we can always turn the heaters back on in a stop script if needed. When conditional gcode gets to the point where we can set global variables via Mcodes, maybe there can be an option to pass things like that to the stop script (and other) scripts.



  • Is the expectation that it will result in better prints because it has the exact model rather than STL approximation?



  • @zapta You would think so but it's gonna take some work to figure out whether that's the case or not.



  • @zapta The big difference will hopefully come on curves. At the moment Fusion is breaking up curves into linear segments for FFF printing, much like you would get from an STL. Hopefully this will change in future as Fusion already has proper curve generation in the machining CAM. I'm yet to work out whether this is limited by the toolpath generation or whether it's something to do with the machine definition, documentation is non-existent right now.



  • UPDATE 12/03/2020

    Workaround for disabling generated toolpath control of extruder and bed heaters. Enable Heater Control (Default: Yes) decides whether the slicer should include commands to control initial warmup of the extruder and bed, followed by shut off at completion of the print. Enable for simplicity, disable if you want to use other methods (eg. the filament system) to control extruder and bed temps. The post-heat macro property remains but is not necessary if heater control is disabled, in that case any methods that would otherwise go here can be moved to start.g.

    Re-instated M0 H1 at end of print

    Right now this is probably as far as I can go functionality wise. the idea was always to strip out any excess gcode commands and so far that has been done so it will stay as it is until the next Fusion update or they release more documentation.



  • @littlehobbyshop said in Fusion 360 FDM/FFF Slicing:

    UPDATE 12/03/2020

    Wait, IT'S DECEMBER ALREADY??? 🙂



  • I have never been able to understand why there are two different notations for dates.
    Personally I think it should be 2020/3/12 🙂



  • Full ISO please... 2020-03-12T16:47:31-06:00



  • My bad 😞
    Apologies all around!



  • We should just count milliseconds since the big bang if we wanna get precise.



  • Would we be able to do that with 64 bits or do we need to go with 128 bits instead ?

    Maybe we should all standardize on the 'Stardate' system ?



  • Someone stretching his neck to create an optimal RRF post for F360, and you guys start a date notation discussion?



  • @DaBit said in Fusion 360 FDM/FFF Slicing:

    Someone stretching his neck to create an optimal RRF post for F360, and you guys start a date notation discussion?

    We paid the man his upvotes, let us have some fun.


Log in to reply