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

    Create restricted area on built plate

    Scheduled Pinned Locked Moved
    General Discussion
    8
    11
    659
    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.
    • MacNiteundefined
      MacNite
      last edited by

      Hey guys,

      at the moment I am building a new machine. Due to the design of the z-axis and the Tool head there are 2 corners (marked red in picture) which the print head is not able to reach because it would cause a crash with the z-axis top mount.

      Is there any way in RRF3 to restrict movements into this area so the printhead won't move there?

      33a5e96e-368a-44f9-9e5e-dcb080d54c03-image.png

      Thanks for your help.
      Max

      CorEssentials on GitHub | Instructables Profile | Thingiverse Profile

      dc42undefined PCRundefined A Former User? fcwiltundefined 4 Replies Last reply Reply Quote 0
      • dc42undefined
        dc42 administrators @MacNite
        last edited by

        @macnite, RRF does not provide that facility.

        Duet WiFi hardware designer and firmware engineer
        Please do not ask me for Duet support via PM or email, use the forum
        http://www.escher3d.com, https://miscsolutions.wordpress.com

        sinned6915undefined 1 Reply Last reply Reply Quote 0
        • PCRundefined
          PCR @MacNite
          last edited by

          @macnite

          best way would be the slicer i think 😉

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

            @macnite

            If it is because of the position of the endstops, because they are mechanically further out then what you would want to print later, then maybe consider to overwrite the homing-"0" in your homing files with for x for example something like:

            ...
            "actual/traditional/real" homing
            ...
            G1 H2 X2.5 F100     ; "free" the endstop (by moving a little bit away)
            G90       		    ; set to absolute positioning
            G92 X{(move.axes[0].min)}             ; set axis position as "val" (you may want to adjust this) -> in absolut coordinate system (G90)
            ...
            restoffileeventually
            ...
            

            of course you would restrict your total print area (by the help of also m208 in config.g) to something like this:

            7cd28447-2e7d-45fd-93ba-731e11ede56a-grafik.png

            You can of course also put it directly into M208 it seems, what might be a bit more elegant:
            https://forum.duet3d.com/topic/14414/y-offset-correction/9

            But I guess you know that already so this answer might be not really of any help for you.
            Anyway - regards

            1 Reply Last reply Reply Quote 0
            • sinned6915undefined
              sinned6915 @dc42
              last edited by

              @dc42 can this be added to the feature wishlist?

              This feature, definition or modifications of areas, could define and protect things. Like the OP needs "no motion here".
              It could be used to isolate motion for things like purge buckets, nozzle wipers, probe docks. These areas once defined could be combined with gcode meta commands to enforce them.

              for example- if swithching filaments, allow acess to purge bucket, else do not move into area.

              i would not trust any slicer to enforce motion conditions.

              1 Reply Last reply Reply Quote 0
              • fcwiltundefined
                fcwilt @MacNite
                last edited by

                @macnite Can you move the build surface back a bit?

                Printers: a small Utilmaker style, a small CoreXY and a E3D MS/TC setup. Various hotends. Using Duet 3 hardware running 3.4.6

                1 Reply Last reply Reply Quote 0
                • OwenDundefined
                  OwenD
                  last edited by OwenD

                  I would think this is more properly in the domain of the slicer.
                  It's not an uncommon scenario in cnc routers when clamps are used, but if it's in RRF what happens if you slice something that's in the boundary?
                  From memory the objects aren't defined until after the first layer, so it would be difficult for RRF to cancel an object completely until it knows it's extent.
                  This would likely require a simulation before every print.

                  It's easily done in Prusa Slicer.
                  Just create an STL of your bed shape by drawing it and paddiing it in a 3d cad system.
                  Then choose custom bed shape and select your STL
                  bed 1.png

                  Here's the result
                  bed 2.png

                  Prusa slicer won't show an error unless you're outside of the outer boundary of the bed, but the visual of the modified shape should be enough to stop you putting it in the wrong spot.

                  1 Reply Last reply Reply Quote 2
                  • MacNiteundefined
                    MacNite
                    last edited by

                    Thank you for your replies!

                    @dc42 Thank you for the info.

                    @Lbi No, it is not because of the endstop position, it is the other way round. I want to "limit" the movements additionally ot the endstop position without decreasing the built volume significantly.

                    @sinned6915 very nice idea! I think this would be a very helpful feature.

                    @fcwilt I could move the build surface back, but that would "decrease" my total built volume. ATM I am trying to maximise it.

                    @OwenD Very nice Idea! I think that will be the way I'll try it!

                    Greets
                    Max

                    CorEssentials on GitHub | Instructables Profile | Thingiverse Profile

                    sinned6915undefined 1 Reply Last reply Reply Quote 0
                    • sinned6915undefined
                      sinned6915 @MacNite
                      last edited by

                      @OwenD I am pretty sure there is a bug in PrusaSlicer that only defines the bed from the center, not lower left corner- so EVERYTHING had to be formatted that way.

                      Slicer level control does not work for general machine control. I can imagine the condition where a move command could path a tool throught a no-no region if its u-shaped as you have drawn. At the firmware level I would think that the same move command would alter the toolpath around it.

                      OwenDundefined 1 Reply Last reply Reply Quote 0
                      • OwenDundefined
                        OwenD @sinned6915
                        last edited by

                        @sinned6915
                        Regarding movement through a restricted area, perhaps that could be true.
                        It would depend on the slicer.
                        Given Prusa slicer didn't throw an error when placing a part in that area lends credence to your suggestion.
                        @MacNite should test that by creating a "restricted area" in Prusa Slicer that is in fact safe on the machine.

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

                          This kind of shapes called concave. There down side is that some straight lines between two inside points go through outside points. What would you like the duet to do if it gets such a move, refuse to move? Go around?

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