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

    The ULTIMATE RepRap Post-Processor for Fusion 360

    Scheduled Pinned Locked Moved
    CNC
    7
    11
    3.0k
    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.
    • bruceundefined
      bruce
      last edited by

      The ULTIMATE Duet3D RepRap CNC Post-Processor for Autodesk Fusion 360
      Here is my take on a post-processor for Fusion 360 😊

      Get it here from my GitHub 👇 : https://github.com/BruceRoyce/UltimateRepRapPost/blob/main/UltimateRRPost.cps

      This post-processor takes care of some issues and shortcomings that I found with other existing posts for RepRap, such as Linear Backlash Compensation, support for multi-tool and accurate tool change, inline probe and more

      I made this for my own use, so please exercise caution if you take it! Obviously I won't be responsible for anything related to the use of this post-processor! Use own your own risk

      a75f59ed-be18-4dab-bbbe-fc3d3a240c6d-image.png

      bruceundefined 1 Reply Last reply Reply Quote 4
      • bruceundefined
        bruce @bruce
        last edited by

        See Instructions here
        https://github.com/BruceRoyce/UltimateRepRapPost

        1 Reply Last reply Reply Quote 4
        • bruceundefined
          bruce
          last edited by

          I updated the ULTIMATE post-processor for RepRap (get it here on GitHub).
          With this release the backlash compensation is improved and now offers two compensation methods:

          • Steps: This method is preferred over the old compensation by distance method. This method compensates backlash by adjusting the Steps Per Unit and keeps motion distances as they are reported by the CAM. To use this method in this version you will need to know your current Steps Per Unit configuration. To get these configuration, open "config.g" file (normally under /sys/ folder) and note M92 X and Y and Z values. When posting your part, enter these values in the backlash compensation input as asked. (Section 4 of the post "Linear Backlash Compensation)
            The post Steps Per Unit values you enter are ONLY effective if you choose "Steps" as your compensation method and check "Apply Backlash Compensation" tick box
          • Distance: This is the older method and still quite useful if you don't know your Steps per unit configuration, or for whatever strange reason you don't want to use Steps method.
            In both methods X, Y and Z axis measured backlash for 1mm and 10mm is required for a successful compensation calculation.
          • Tolerance: By setting tolerance you tell the post-processor to not trigger backlash compensation for motion distances smaller that the tolerance value. When dealing with small detail this will increase the machine stability by ignoring tiny backlashes.
          1 Reply Last reply Reply Quote 5
          • tom33undefined
            tom33
            last edited by

            @bruce Thanks for your post pro !

            I tried with my config but when I use an other tool than T0 my spindle doesn't turn. How do you manage this ?

            1 Reply Last reply Reply Quote 0
            • baird1faundefined
              baird1fa
              last edited by

              Hello @bruce Thanks for the post processor, I'm just getting started with my CNC using a duet 2 Wifi and I just did a test circle as my first attempt using it. No cutting just moving in air. I noticed that the post doesn't output arc (G2) is there a way to enable that? I know that the duet boards can handle arcs as I have used the arc welder plugin for my 3D printers. I just noticed that with my machine being large and having accelerations relatively slow that many segments for a circle make for some choppy movements.

              Thanks for your help.

              baird1faundefined 1 Reply Last reply Reply Quote 0
              • baird1faundefined
                baird1fa @baird1fa
                last edited by

                @bruce

                I have managed to fix the G2-G3 issue with this post (or at least is was an issue for me)

                there is a piece missing after allowedHelicalMove = true; which should be allowedCircularPlanes = undefined;

                d4eab7ef-2b3a-401a-869e-ffd12e280150-image.png

                Then under // circular output all the i, j, and k variables are forced false that needs to be replaced with
                // circular output
                false
                falsevar iOutput = createReferenceVariable({ prefix: "I"}, xyzFormat);
                false
                falsevar jOutput = createReferenceVariable({ prefix: "J"}, xyzFormat);
                false
                falsevar kOutput = createReferenceVariable({ prefix: "K"}, xyzFormat);
                false
                false

                667cac87-2cd9-4405-837a-a6ac35449a19-image.png

                and that should give you G2 and G3 movements. I haven't tested the Gcode yet but at least circular movements are arcs and not thousands of segments.

                TeamCocoundefined 1 Reply Last reply Reply Quote 1
                • TeamCocoundefined
                  TeamCoco @baird1fa
                  last edited by

                  @baird1fa Any chance you can explain the second change to the post? I made the circular plane addition, but I can't quite follow what is described in the second image/change.

                  Thanks in advance!

                  @baird1fa said in The ULTIMATE RepRap Post-Processor for Fusion 360:

                  Then under // circular output all the i, j, and k variables are forced false that needs to be replaced with
                  // circular output
                  false
                  falsevar iOutput = createReferenceVariable({ prefix: "I"}, xyzFormat);
                  false
                  falsevar jOutput = createReferenceVariable({ prefix: "J"}, xyzFormat);
                  false
                  falsevar kOutput = createReferenceVariable({ prefix: "K"}, xyzFormat);
                  false
                  false

                  baird1faundefined 1 Reply Last reply Reply Quote 0
                  • baird1faundefined
                    baird1fa @TeamCoco
                    last edited by

                    @teamcoco sorry I cannot explain as I really don't know. I just took what I was told to do from the Autodesk HSM post forum and posted it here. But I think what is happening is that the i j and k variables are disabled by default because when the autodesk guys wrote the post G2,G3 were not supported by Reprap. The text in the screen shot is what you want to add and replace what is there.

                    chernogorskyundefined 1 Reply Last reply Reply Quote 0
                    • chimaeraghundefined chimaeragh referenced this topic
                    • chernogorskyundefined
                      chernogorsky @baird1fa
                      last edited by

                      I have issue with G3. it looks like something is wrong within the duet itself, it looks good in gcode viewers, but created an oval

                      will check and probably open a d3 issue
                      at the moment I back to thousands of segments

                      1 Reply Last reply Reply Quote 0
                      • MaxGyverundefined
                        MaxGyver
                        last edited by

                        Hey @bruce

                        Thank you so much for developing and sharing your post processor! I use it with the HSM-Works plugin directly in SolidWorks for my duet based CNC Mill.

                        Any chance to also include a profile for turning as well? I am in the process of converting a Lathe to CNC using a Duet3 6HC board. With lathe support, it would really be the "one post processor to rule them all" 😁

                        Cheers Max

                        TQKez 0undefined 1 Reply Last reply Reply Quote 2
                        • TQKez 0undefined
                          TQKez 0 @MaxGyver
                          last edited by

                          @bruce This is much better than other Fusion PP's I've experimented with, but I have the same problem as I do with all the the Fusion post processors in that it tries to do the first move into position without lifting the spindle.

                          Once it gets to the first ramp down position, it moves the spindle up first before plunging, but it's already too late as it's crashed into the stock on the move and snapped the end mill.

                          Not so hard to fix manually by inserting the appropriate move command just before the first G0, but its easy to forget.

                          Is there a setting I'm missing that would make raise the spindle first (ideally to Z Max, and ideally also after a tool change) by first moving the spindle up and out of the way of the stock and clamps.

                          Thanks.

                          1 Reply Last reply Reply Quote 0
                          • droftartsundefined droftarts referenced this topic
                          • MaxGyverundefined MaxGyver referenced this topic
                          • First post
                            Last post
                          Unless otherwise noted, all forum content is licensed under CC-BY-SA