IDEX and Z Offset
-
there are a lot of bugfixes in rrf3 regarding offset of tools
-
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
-
@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
-
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
-
So you are on 3.2 now?
-
yes i'm on 3.2
-
I hit the same issue when I config as below.
Start script:
T1
G28
T0Root 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;
// }
// } -
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!)
-
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.
-
if it is zmax already, tools are far enough to the buildplate, why need such stupid logic.