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

    duet3 post processor for fusion360???

    Scheduled Pinned Locked Moved
    CNC
    5
    15
    1.5k
    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.
    • Danalundefined
      Danal
      last edited by

      In Fusion, when you select "post process", it gives you a long list of choices. Mach3 should work.

      Delta / Kossel printer fanatic

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

        @jlipavsky79 said in duet3 post processor for fusion360???:

        @jay_s_uk Not the firmware.... the post processor for fusion 360

        if you'd scroll down as instructed...
        https://learn.ooznest.co.uk/Wiki/WorkBee_Firmware_Releases#Section_Fusion360

        jlipavsky79undefined 1 Reply Last reply Reply Quote 0
        • jlipavsky79undefined
          jlipavsky79 @A Former User
          last edited by jlipavsky79

          @bearer ok so the workbee-duet.cps i found is working except it doesn't turn on the spindle, I opened the gcode and there wasn't a M3 command and at the end of the file there also wasn't a M5

          and mach3 did not work at all

          i turned on the spindle by sending a m3 command for the workbee one and it did the cut as it should, so......................... spindle fix?????

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

            I haven't tried it, forget which one i use and can't access it for a few days. anyways, seems it should use M0, M2, M3, M4 and M5.

            i wouldn't expect M3 at the end, M2 or M0 seems to what the code is meant to produce.

            var mapCommand = {
              COMMAND_STOP:0,
              COMMAND_END:2,
              COMMAND_SPINDLE_CLOCKWISE:3,
              COMMAND_SPINDLE_COUNTERCLOCKWISE:4,
              COMMAND_STOP_SPINDLE:5
            };
            

            edit: hmm, the onClose section was infact somewhat empty, try adding this to that

            function onClose() {
              onImpliedCommand(COMMAND_END);
              onImpliedCommand(COMMAND_STOP_SPINDLE);
            }
            

            (But you're probably better of asking a ooznest forum for help with their post, seems odd that stuff is missing though)

            jlipavsky79undefined 1 Reply Last reply Reply Quote 0
            • 3DOesteundefined
              3DOeste
              last edited by

              Fanuc post should work. I made one for powermill (it’s here on the forum). David fix the firmware some time ago so G1 and F commands are maintain until a change in one of those, which was the primary difference I found with industrial cnc controllers.
              You should disable fix cycles in post or write the program without them (I don’t know how fusion works), since RRF doesn’t support them.

              1 Reply Last reply Reply Quote 0
              • jlipavsky79undefined
                jlipavsky79 @A Former User
                last edited by

                @bearer its missing because it was written for the duetwifi and I'm using the duet 3 so its more so that some of the assignments have changed and the some of the codes reference different codes for the rrf_3

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

                  @jlipavsky79 said in duet3 post processor for fusion360???:

                  @bearer its missing because it was written for the duetwifi and I'm using the duet 3 so its more so that some of the assignments have changed and the some of the codes reference different codes for the rrf_3

                  right, then you fix it...

                  jlipavsky79undefined 1 Reply Last reply Reply Quote 0
                  • jlipavsky79undefined
                    jlipavsky79 @A Former User
                    last edited by

                    @bearer im a mechanical engineer.... not a software engineer ..... looks like french....

                    A Former User? 1 Reply Last reply Reply Quote 0
                    • Danalundefined
                      Danal
                      last edited by Danal

                      It is fairly hard to be your own CNC operator without knowing at least a little bit about G Code. You don't need to be an expert. You do need to know the basics.

                      The main difference between post processors will be the g-codes they put at the start and end of a job. Things like homing, or starting the spindle, etc. The actual moves are very likely to be the same between posts.

                      Therefore, you can experiment with different posts and see which one works best. I'm surprised that the Mach3 post did not work, it is very generic. You could also try grbl.

                      Here is an example. The startup g-code is a little different, the moves are EXACTLY the same.

                      Screen Shot 2020-01-30 at 10.33.23.png

                      Delta / Kossel printer fanatic

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

                        @jlipavsky79 said in duet3 post processor for fusion360???:

                        @bearer im a mechanical engineer.... not a software engineer ..... looks like french....

                        Your clipboard can copy and paste french just fine. Open your ooznest post, find onClose and insert the two lines I posted. That would most likely as the stop code you're missing.

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