Homing override in secondary .cfg not working

General Discussion
1

Basic Information:

Printer Model: Seckit Tank V2
MCU / Printerboard: CB1 Manta M8P

dab.cfg (9.7 KB)

printer.cfg (15.8 KB)

Describe your issue:

Hello,

I am new to using klipper and am using a custom Z probing setup that doubles as an endstop. I have been unable to get the homing override to work. Everytime I press home it finds x and y and then starts moving z before moving x and y to a place on the bed. Is there something wrong with either of my files? Only some of the macros present in the DAB.cfg are present in the UI… not sure if that’s related.

HELP!

…

2

Hello @Myceliuman !

Where is the klippy.log?

3

It would only let me upload two files. Here it is

klippy (2).zip (1.4 MB)

4

This looks somehow wrong:

variable_dist_x_move_latch = 11.5
variable_bed_drop_after_z_home = 15.0
gcode = 
	
	
	
	
	
	
	[homing_override]
	axes: xyz
	set_position_x:10

It seems that the macro [gcode_macro _dabSettings] is not properly closed/finished

The config dab.cfg is messed up:


variable_dist_y_collision_zone: 20.0
variable_dist_x_move_latch: 11.5

variable_bed_drop_after_z_home: 15.0


gcode:
    # SET_GCODE_VARIABLE MACRO=_dab_settings VARIABLE=debug VALUE={printer.heater_bed.target}

# # == homing_override start =====================================================
# # Uncomment [homing_override] after you have tuned position_endstop, 
# # position_min, position_max in [stepper_x] and [stepper_y]
# # ==============================================================================
 [homing_override]
 axes: z
 set_position_x:10   # explicitly set a coord even before homing
 set_position_y:10   # explicitly set a coord even before homing
 set_position_z:10   # explicitly set a coord even before homing
 gcode:
     {% set is_x_homed = False %}

You may consult the author

5

These are the original files from the author. He hasn’t been the greatest at helping atm but maybe the issues you’re noticing in my files are different from his?

6

Great!

The author throws some code into the net and awaits others to fix the issues?

That is the great risk with macros from somewhere out of the blue.

Try with commenting out the line gcode: (I marked it)

7

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.