Closed ANYCUBIC-3D closed 6 years ago
Have you tested endstops with M119?
Also change ZMAX
with _ZMAX_
@GMagician thanks for your answer. I had tested M119, when I trigger 'ZMAX' endstop manually, it shows 'z2_min: TRIGGERED', otherwise it shows 'z2_min: open'. Also yeah, the two underscore of ZMAX was disappeared when I publish this comment.
Do tou have ENDSTOP_INTERRUPTS_FEATURE or not? What about ENDSTOP_NOISE_FILTER? sure you don't have EMI issues?
I'm still using your config (dual z dual endstops) and it works
I didn't enable ENDSTOP_INTERRUPTS_FEATURE and ENDSTOP_NOISE_FILTER , The same config to marlin 1.1.0 run on the same machine, it works fine. Should I must be enable ENDSTOP_INTERRUPTS_FEATURE?
Yes if you can (if your HW support interrupt on endstop inputs)
EDIT: from 1.1.0 something has been changed to endstop logic. Now is prune to error if signals are not stable (EMI issues)
Sorry. Could you test Dual Z endstop with disable ENDSTOP_INTERRUPTS_FEATURE? my Y_MIN_PIN had used for UART3, so I can't open interrupt endstop inputs.
I can't, I burned my arduino 12V to 5V converter and I'm waiting for spare part. Try with firstly with ENDSTOP_NOISE_FILTER, just to be sure no EMI issues
OK, thanks , I opened ENDSTOP_NOISE_FILTER, the result is same, so maybe not EMI issues.
Sure that when you manually trigger z1 endstop z2 will stay open?
Yeah, I am very sure, I had use marlin old version two years
That's weird... everything seems ok. Can you attach full configuration.h and configuration_adv.h?
Really I'm using 2.0 but it should be the same logic.
Hello there, here are full config:
I checked your config and it seems ok, nothing related to your issue.
Something that is not Marlin standard:
#define OutageTest
#define TFTmodel
Something strange:
#define USE_XMAX_PLUG
#define E1_DRIVER_TYPE A4988
#define Z2_USE_ENDSTOP ZMAX
#define HOMING_FEEDRATE_XY (4060)
'#define HOMING_FEEDRATE_Z (660)'
Today I'll be able to fix my printer and I'll try configuration without interrupts, just to see it this is the cause of your trouble
Thanks again.
//#define OutageTest
//#define TFTmodel
write by myself, now I disabled.
//#define USE_XMAX_PLUG
about #define E1_DRIVER_TYPE A4988
, I used E1 motor as another Z motor. and E1 driver type is A4988
about #define HOMING_FEEDRATE_XY (4060)
… #define HOMING_FEEDRATE_Z (660)
there is 'myltiply' in my project, but disappered when I comment to here.
Now another Strange thing, when I home all axis, X Y works well(trigger endstop two times), but Z axis trigger one time and stop there, about 1 minutes(or maybe later) later,it raise and trigger one time again by itself.
about '#define E1_DRIVER_TYPE A4988, I used E1 motor as another Z motor. and E1 driver type is A4988
you have to #define Z2_DRIVER_TYPE A4988
for second Z axis
trigger one time and stop there, about 1 minutes
this seems a issue already reported by other people.
To help you may compile with DEBUG_LEVELING_FEATURE enabled and execute home. Maybe can help to signal in echo messages where pause is
@ANYCUBIC-3D — Please read this before posting any more code or other text with characters like asterisk, underscore, etc.: https://guides.github.com/features/mastering-markdown/
Thanks to all.
I had compile with DEBUG_LEVELING_FEATURE
, NOTHING important feedback (except X:-10.00 Y:0.00 Z:0.00 E:0.00 Count X:-800 Y:0 Z:0
… ok
), and didn't response G/M code until Z axis move again.
@ANYCUBIC-3D after compiling with DEBUG_LEVELING_FEAUTURE
, and before doing home, you have to execute M111 S255
.
This is all feedback:
M111 S255
echo:DEBUG:ECHO,INFO,ERRORS,DRYRUN,COMMUNICATION
ok
G28
echo:G28
Error:Printer halted. kill() called!
(this message feedbacked at the second time of Z endstop trigger) How can I fix this issue?
Uhm... this message with Z_DUAL_ENDSTOPS_ADJUSTMENT
= 0 was fixed time ago.. Please try with 0.001. If you still have it maybe we are facing some regression
@ANYCUBIC-3D — If you're trying to get the extra debug output during G28
here are the full instructions we usually hand out:
bugfix-1.1.x
or bugfix-2.0.x
to test with the latest code.DEBUG_LEVELING_FEATURE
and M114_DETAIL
and re-flash the firmware.M111 S247
to enable maximum logging.G28
to do your standard homing procedure.G29
to probe the bed. This will also enable bed leveling.As for the printer doing a "kill" on G28
… Double-check with M119
that all your endstops (and probe) are working correctly.
I had set Z_DUAL_ENDSTOPS_ADJUSTMENT
=0.001;
I had enable DEBUG_LEVELING_FEATURE
and M114_DETAIL
;
then re-flash and reboot system.
Below is the log:
M111 S247
echo:DEBUG:ECHO,INFO,ERRORS,COMMUNICATION,LEVELING
ok
G28
echo:G28
>>> G28
Machine Type: Cartesian
Probe: NONE
current_position=(0.00, 0.00, 0.00) : setup_for_endstop_or_probe_move
> endstops.enable(true)
Raise Z (before homing) to 2.00
>>> do_blocking_move_to(0.00, 0.00, 2.00)
<<< do_blocking_move_to
>>> homeaxis(X)
Home 1 Fast:
>>> do_homing_move(X, -630.00, [40.00])
current_position=(0.00, 0.00, 2.00) : sync_plan_position
<<< do_homing_move(X)
Move Away:
>>> do_homing_move(X, 5.00, [40.00])
current_position=(0.00, 0.00, 2.00) : sync_plan_position
<<< do_homing_move(X)
Home 2 Slow:
>>> do_homing_move(X, -10.00, 10.00)
current_position=(0.00, 0.00, 2.00) : sync_plan_position
<<< do_homing_move(X)
>>> set_axis_is_at_home(X)
For X axis:
home_offset = 0.00
position_shift = 0.00
soft_endstop_min = -10.00
soft_endstop_max = 410.00
> home_offset[X] = 0.00
current_position=(-10.00, 0.00, 2.00) :
<<< set_axis_is_at_home(X)
current_position=(-10.00, 0.00, 2.00) : sync_plan_position
current_position=(-10.00, 0.00, 2.00) : > AFTER set_axis_is_at_home
<<< homeaxis(X)
>>> homeaxis(Y)
Home 1 Fast:
>>> do_homing_move(Y, -615.00, [40.00])
current_position=(-10.00, 0.00, 2.00) : sync_plan_position
<<< do_homing_move(Y)
Move Away:
>>> do_homing_move(Y, 5.00, [40.00])
current_position=(-10.00, 0.00, 2.00) : sync_plan_position
<<< do_homing_move(Y)
Home 2 Slow:
>>> do_homing_move(Y, -10.00, 10.00)
current_position=(-10.00, 0.00, 2.00) : sync_plan_position
<<< do_homing_move(Y)
>>> set_axis_is_at_home(Y)
For Y axis:
home_offset = 0.00
position_shift = 0.00
soft_endstop_min = 0.00
soft_endstop_max = 410.00
> home_offset[Y] = 0.00
current_position=(-10.00, 0.00, 2.00) :
<<< set_axis_is_at_home(Y)
current_position=(-10.00, 0.00, 2.00) : sync_plan_position
current_position=(-10.00, 0.00, 2.00) : > AFTER set_axis_is_at_home
<<< homeaxis(Y)
>>> homeaxis(Z)
Home 1 Fast:
>>> do_homing_move(Z, -682.50, [6.00])
current_position=(-10.00, 0.00, 0.00) : sync_plan_position
G29
About 1 minute later
<<< do_homing_move(Z)
Move Away:
>>> do_homing_move(Z, 8.00, [6.00])
current_position=(-10.00, 0.00, 0.00) : sync_plan_position
<<< do_homing_move(Z)
Home 2 Slow:
>>> do_homing_move(Z, -16.00, 1.50)
current_position=(-10.00, 0.00, 0.00) : sync_plan_position
<<< do_homing_move(Z)
>>> do_homing_move(Z, 0.00, [6.00])
current_position=(-10.00, 0.00, 0.00) : sync_plan_position
Error:Printer halted. kill() called!
Reboot machine manually
M119
Reporting endstop status
x_min: TRIGGERED
y_min: TRIGGERED
z_min: TRIGGERED
z2_min: TRIGGERED
ok
M119
Reporting endstop status
x_min: open
y_min: open
z_min: open
z2_min: open
ok
@thinkyhead Any news?
Any news?
I fixed your formatting for readability. Please read this page to learn how to use Markdown formatting.
As for the logs, they only reveal that the Z endstop is not showing as triggered when homing is complete. It could be a wiring issue. It's impossible to tell without more hands-on diagnostics.
As a temporary workaround, you can comment out all occurrences in Marlin of…
endstops.validate_homing_move();
only work NC
only work NC
// Mechanical endstop with COM to ground and NC to Signal uses "false" here (most common setup).
#define X_MIN_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define Y_MIN_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define Z_MIN_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define X_MAX_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define Y_MAX_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define Z_MAX_ENDSTOP_INVERTING false // Set to true to invert the logic of the endstop.
#define Z_MIN_PROBE_ENDSTOP_INVERTING false // Set to true to invert the logic of the probe.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Hello, the mainly config like below:
Without auto leveling, now dual Z motors are stoped by ZMIN endstop when homing, dose I mis-configed something?