Z-Axis problem with FAST_COREXYZ and two z-axis-endstops.
Hi,
i am experimenting with my corexy printer. I'm using a ramps with repetier-firmware and i have two z-motors with two endstops.
The Problem: if i define FAST_COREXYZ my z-axis won't home anymore, if i move it manually in z-direction the firmware just resets.
This i find is very strange.
If i deactivate FAST_COREXYZ homing with two endstops works fine.
if i deactivate multiple-endstops for z and activate FAST_COREXYZ it is also working.
Config follows
regards
i am experimenting with my corexy printer. I'm using a ramps with repetier-firmware and i have two z-motors with two endstops.
The Problem: if i define FAST_COREXYZ my z-axis won't home anymore, if i move it manually in z-direction the firmware just resets.
This i find is very strange.
If i deactivate FAST_COREXYZ homing with two endstops works fine.
if i deactivate multiple-endstops for z and activate FAST_COREXYZ it is also working.
Config follows
regards
Comments
https://forum.repetier.com/discussion/4305/corexy-with-fast-corexyz-defined-is-failing-to-home-z#latest
I'm working on an update that will contain this as well. I guess it also solves the dual z endstop issue.
I wrote in the other tread that i have a problem with dual z endstops but the original thread poster doesn't have dual z endstops.
I think this are two separate issues so i opened a second thread.
So first things to check:
- If compiled with ALWAYS_CHECK_ENDSTOPS false, can you move?
- Can you move also with Z homing speed?
- When it resets, what doe slog show as reset reason?
- At which stage of homing does the reset happen?
- Does M119 work or also reset?
- Does X/Y homing also reset?
First target must be to isolate the code part that causes a reset, so as you see you should test parts of homing seperately. Later if the bigger block is identified you will start adding output to log what position you could reach.
always check endstops disabled: z axis wont move or home.
Z Homing speed and moving speed are equal.
When homing Z in the log shows "busy processing" several times.
M119 doesn't reset. shows for all z max and z2max L. If i trigger the endstops manually the state goes correct to H.
x/y homing and moving is working correct.
Offtopic: which IDE do you use for firmware developing? I'm playing right now with Visual Studio Code with Arduino Plugin and must say i'm impressed.
But Z doesn move.
What I also see is that you need to use z2MinMax as this is used for dual z endstop testing. The z2Max seems unused so far.
Next I see that the nonlinear version uses a different endstop testing code which does not have the second endstop test at all. I have added it locally for me, but the next update has some bigger changes so needs some testing before I can publish. If you send me a pm with email I can send you the modified motion.cpp.
pm is on its way.
Thanks for great support.