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

    IDEX and Z Offset

    Scheduled Pinned Locked Moved
    Using Duet Controllers
    6
    19
    1.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.
    • Vetiundefined
      Veti
      last edited by

      there are a lot of bugfixes in rrf3 regarding offset of tools

      1 Reply Last reply Reply Quote 0
      • mbtobecaundefined
        mbtobeca
        last edited by

        I look in bugfixes, but not find.
        Here is the error message after tool change :

        Error: New tool too close to Z axis limit. Aborting tool change

        Vetiundefined 1 Reply Last reply Reply Quote 0
        • Vetiundefined
          Veti @mbtobeca
          last edited by

          @mbtobeca said in IDEX and Z Offset:

          I look in bugfixes, but not find.

          see https://github.com/Duet3D/RepRapFirmware/blob/v3-dev/WHATS_NEW_RRF3.md

          search for offset

          1 Reply Last reply Reply Quote 0
          • mbtobecaundefined
            mbtobeca
            last edited by

            In fact, I did find this page, but I couldn't find anything about my problem. I even believe that it is a desired security. I saw that he was talking about the max limit in Z, but not the min limit:
            "If a tool change is requested but changing tool would cause the Z max limit to be exceeded because of the changed tool Z offset, the tool change is now aborted"

            Thanks to try help me

            1 Reply Last reply Reply Quote 0
            • Phaedruxundefined
              Phaedrux Moderator
              last edited by

              So you are on 3.2 now?

              Z-Bot CoreXY Build | Thingiverse Profile

              1 Reply Last reply Reply Quote 0
              • mbtobecaundefined
                mbtobeca
                last edited by

                yes i'm on 3.2

                1 Reply Last reply Reply Quote 0
                • hestiahuangundefined
                  hestiahuang
                  last edited by

                  I hit the same issue when I config as below.

                  Start script:
                  T1
                  G28
                  T0

                  Root cause:
                  Reading from code is due to I am using zmin as probe, however I have zmax endstop too. And my zmax saved is small then actual.

                  Solution:
                  However I don't want to config zmax again and again.
                  comment the code and build without checking
                  Gcodes4.cpp
                  // auto currentTool = reprap.GetCurrentTool();
                  // if (currentTool != nullptr)
                  // {
                  // const float newZPos = (moveBuffer.coords[Z_AXIS] - currentTool->GetOffset(Z_AXIS));
                  // if(newZPos > platform.AxisMaximum(Z_AXIS) || newZPos < platform.AxisMinimum(Z_AXIS))
                  // {
                  // gb.MachineState().feedRate = toolChangeRestorePoint.feedRate;
                  // doingToolChange = false;
                  // gb.MachineState().SetError("New tool too close to Z axis limit. Aborting tool change");
                  // AbortPrint(gb);
                  // gb.SetState(GCodeState::checkError);
                  // break;
                  // }
                  // }

                  1 Reply Last reply Reply Quote 0
                  • alankilianundefined
                    alankilian
                    last edited by

                    How are you planning on getting each nozzle down to where they need to be to print a layer when they are 6.5mm offset in Z?

                    Won't one need to be 6.5mm BELOW the level of the print to get the other one down to the level of the print?

                    I'm probably misunderstanding something. (as usual!) 🙂

                    SeemeCNC Rostock Max V3 converted to V3.2 with a Duet2 Ethernet Firmware 3.2 and SE300

                    1 Reply Last reply Reply Quote 0
                    • hestiahuangundefined
                      hestiahuang
                      last edited by

                      I think this is unnecessary logic. Why I can't switch tools when I am using the zmax endstop? That is the problem in that logic.

                      1 Reply Last reply Reply Quote 0
                      • hestiahuangundefined
                        hestiahuang
                        last edited by

                        if it is zmax already, tools are far enough to the buildplate, why need such stupid logic.

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