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

Is there any way to define "no go areas" of a print bed?

Scheduled Pinned Locked Moved
Firmware wishlist
3
5
210
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.
  • undefined
    deckingman
    last edited by deckingman 28 Mar 2023, 14:41

    This is no big deal but I thought I'd ask the question......

    The latest iteration of my printer design will have the ability for the nozzle to reach just outside the limits of the build plate. Which is nice because I'll be able to use the full 400mm x 400mm of surface area. BUT, I use a glass build plate (and no, I don't want to change that), which will be held down to the aluminium plate with clips in each corner. Which means that bad things would happen if I wanted to print something that had to extend completely into one or more corners. Or more likely, if I home X then try to home Y without first moving to (say) X+25.

    So I just thought I'd ask if anyone knows of a way that these four "no-go" areas (about 20mm square in each corner) could be defined such that the firmware would treat them as hard limits, similar to axes minima and maxima. Of course, I still wouldn't be able print in these "no go" areas but at least it would stop the nozzle colliding with the plate clamps if when I do something stupid.

    Edit I realise that this won't help with the start of homing where the initial axes positions are unknown.

    Ian
    https://somei3deas.wordpress.com/
    https://www.youtube.com/@deckingman

    undefined undefined 2 Replies Last reply 28 Mar 2023, 14:50 Reply Quote 0
    • undefined
      droftarts administrators @deckingman
      last edited by 28 Mar 2023, 14:50

      @deckingman There's the new M599 Define keepout zone? However, this is limited to 1 zone in 3.5b2. Maybe ask @dc42 if support for more is coming.

      Ian

      Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

      undefined 1 Reply Last reply 28 Mar 2023, 15:49 Reply Quote 0
      • undefined
        deckingman @droftarts
        last edited by 28 Mar 2023, 15:49

        @droftarts Thanks - that's the sort of thing I was thinking of. @dc42 four or more zones would be good. 🙂 Also, maybe simply restrict movement similar to the way axis limits are treated, rather than abort the job (but with warning message) ?

        Ian
        https://somei3deas.wordpress.com/
        https://www.youtube.com/@deckingman

        1 Reply Last reply Reply Quote 1
        • undefined T3P3Tony moved this topic from Tuning and tweaking 28 Mar 2023, 16:12
        • undefined
          o_lampe @deckingman
          last edited by 29 Mar 2023, 07:37

          @deckingman With the latest FW you should be able to define those clamps as (parked) tools and define a collision zone around them?
          Just a wild guess...Not sure what the active nozzle would do when approaching one of the zones?

          PS: Can't you define the bed shape in your slicer? It would only be an optical aid where NOT to place parts, though...

          undefined 1 Reply Last reply 29 Mar 2023, 08:49 Reply Quote 0
          • undefined
            deckingman @o_lampe
            last edited by 29 Mar 2023, 08:49

            @o_lampe Good thoughts. I'll look into the "parked tools" thing. I've just looked at my slicer and it seems that I can use a custom shape rather than a fixed rectangle, by defining it as an stl and uploading it. I'll add that to my seemingly ever growing "to-do" list. 👍

            Ian
            https://somei3deas.wordpress.com/
            https://www.youtube.com/@deckingman

            1 Reply Last reply Reply Quote 1
            3 out of 5
            • First post
              3/5
              Last post
            Unless otherwise noted, all forum content is licensed under CC-BY-SA