Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Fusion 360 FDM/FFF Slicing

    Scheduled Pinned Locked Moved
    3D Printing General Chat
    10
    28
    3.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • littlehobbyshopundefined
      littlehobbyshop
      last edited by

      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.

      BLV MGN Cube w/Hemera, K8200, Sunlu S8

      1 Reply Last reply Reply Quote 3
      • gtj0undefined
        gtj0
        last edited by

        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.

        littlehobbyshopundefined dc42undefined 2 Replies Last reply Reply Quote 1
        • littlehobbyshopundefined
          littlehobbyshop @gtj0
          last edited by

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

          BLV MGN Cube w/Hemera, K8200, Sunlu S8

          1 Reply Last reply Reply Quote 0
          • littlehobbyshopundefined
            littlehobbyshop
            last edited by

            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.

            BLV MGN Cube w/Hemera, K8200, Sunlu S8

            gtj0undefined 1 Reply Last reply Reply Quote 3
            • gtj0undefined
              gtj0 @littlehobbyshop
              last edited by

              @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.

              1 Reply Last reply Reply Quote 0
              • zaptaundefined
                zapta
                last edited by

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

                gtj0undefined littlehobbyshopundefined 2 Replies Last reply Reply Quote 0
                • gtj0undefined
                  gtj0 @zapta
                  last edited by

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

                  1 Reply Last reply Reply Quote 0
                  • littlehobbyshopundefined
                    littlehobbyshop @zapta
                    last edited by littlehobbyshop

                    @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.

                    BLV MGN Cube w/Hemera, K8200, Sunlu S8

                    1 Reply Last reply Reply Quote 1
                    • littlehobbyshopundefined
                      littlehobbyshop
                      last edited by

                      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.

                      BLV MGN Cube w/Hemera, K8200, Sunlu S8

                      gtj0undefined 1 Reply Last reply Reply Quote 4
                      • gtj0undefined
                        gtj0 @littlehobbyshop
                        last edited by

                        @littlehobbyshop said in Fusion 360 FDM/FFF Slicing:

                        UPDATE 12/03/2020

                        Wait, IT'S DECEMBER ALREADY??? 🙂

                        1 Reply Last reply Reply Quote 0
                        • jens55undefined
                          jens55
                          last edited by

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

                          1 Reply Last reply Reply Quote 0
                          • gtj0undefined
                            gtj0
                            last edited by

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

                            1 Reply Last reply Reply Quote 2
                            • jens55undefined
                              jens55
                              last edited by

                              My bad 😞
                              Apologies all around!

                              1 Reply Last reply Reply Quote 0
                              • botundefined
                                bot
                                last edited by

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

                                *not actually a robot

                                1 Reply Last reply Reply Quote 1
                                • jens55undefined
                                  jens55
                                  last edited by

                                  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 ?

                                  1 Reply Last reply Reply Quote 1
                                  • DaBitundefined
                                    DaBit
                                    last edited by

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

                                    botundefined 1 Reply Last reply Reply Quote 1
                                    • botundefined
                                      bot @DaBit
                                      last edited by

                                      @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.

                                      *not actually a robot

                                      1 Reply Last reply Reply Quote 2
                                      • DaBitundefined
                                        DaBit
                                        last edited by

                                        OK, granted 😁

                                        1 Reply Last reply Reply Quote 1
                                        • gtj0undefined
                                          gtj0
                                          last edited by gtj0

                                          Tom just did a video on Fusion 360 Slicing...
                                          https://www.youtube.com/watch?v=J_0lLZg4JkY

                                          A Former User? 1 Reply Last reply Reply Quote 1
                                          • A Former User?
                                            A Former User @gtj0
                                            last edited by A Former User

                                            @gtj0 said in Fusion 360 FDM/FFF Slicing:

                                            Tom just did a video on Fusion 360 Slicing...
                                            https://www.youtube.com/watch?v=J_0lLZg4JkY&t=338s

                                            time code to the middle deliberate? (the &t=338s bit)

                                            gtj0undefined 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA