I’ve never been able to get a clean first layer with this machine. I have given it a beacon probe and it just made it much faster to get the same problem to happen again. Where am I going wrong?

  • muusemuuse@lemm.eeOP
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    3 days ago

    I have reworked the start_print gcode macro to incorporate a heat soak before scanning for a mesh. While its running that 20 minute soak, I notice that the temperature reading on the beacon coil is actual dropping while everything else is increasing during the soak. Is just above the bed, in the center, doors closed, and its readings are getting steadily lower. What could possibly cause that?

    EDIT: Here’s where I ended up with my printer.cfg file for my 300 mm^3 voron trident. Do you see anything suspicious? https://pastebin.com/AxxEypK4

    • VinS@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      2 days ago

      Heat soak should not change what you have here. During the heat soak, machine expands a little. You will get a more usefull Z / mesh when the machine gets to equilibrium.

      If you still have problems after that, it’s probably a X twisted, see the linked document above. Unfortunately I do not have much time to dig into your configs.

      I don’t have any experience with beacon. I use Tap or Klicky. With a twisted X, as tap use the nozzle, it should work even with a twisted X