Failing to Home Before Print

Printer Model: Voxelab Aquila 3x
MCU/Printerboard: Aquila N32
Board #: FFP0173

I just got a Voxelab Aquila 3x and I’ve done some configuration for my printer, following the instructions from the following videos for both installing Klipper and configuring my probe for bed leveling:
youtube . com /watch?v=a6ru0mH3F8M

Everything seemed to go as expected until I go to run a print job. The extruder successfully heats up, but I receive the following error:
08:16:53 PM $ SET_HEATER_TEMPERATURE HEATER=extruder TARGET=230
08:16:55 PM $ SET_HEATER_TEMPERATURE HEATER=extruder TARGET=230
08:17:05 PM $ START_PRINT
08:17:05 PM !! Must home axis first: 0.000 0.000 0.200 [-4.000]
08:17:05 PM !! Must home axis first: 0.000 0.000 0.200 [-4.000]

I have a macro name START_PRINT that begins with homing the axes:

[gcode_macro START_PRINT]
gcode:
G28 # Home all axes
G92 E0 # Reset Extruder

G29 # 25 point Bed Level

G1 Z2.0 F3000 # Move Z Axis up little to prevent scratching of Heat Bed
G1 X0.1 Y20 Z0.3 F5000.0 # Move to start position
G1 X0.1 Y200.0 Z0.3 F1500.0 E15 # Draw the first line
G1 X0.4 Y200.0 Z0.3 F5000.0 # Move to side a little
G1 X0.4 Y20 Z0.3 F1500.0 E30 # Draw the second line
G92 E0 # Reset Extruder
G1 Z2.0 F3000 # Move Z Axis up little to prevent scratching of Heat Bed
G1 X5 Y20 Z0.3 F5000.0 # Move over to prevent blob squish

I’ve made sure to set my macro in my machine settings in Cura by setting START_PRINT in the Start G-Code and END_PRINT in the End G-Code.

I’ve done some research but I haven’t found anything that sounds like the issue that I’m having.

Klippy.log:
klippy.log (802.2 KB)

I have the printer.cfg and the gcode for the print job but I wasn’t able to put it up since I’m a new user.

Hello @modsbyus !

Yes, you have, but instantly, you turn off all motors:

[gcode_macro START_PRINT]
gcode = 
	G91
	G1 E-2 F2700
	G1 E-2 Z0.2 F2400
	G1 X5 Y5 F3000
	G1 Z10
	G90
	
	G1 X0 Y230
	M106 S0
	M104 S0
	M140 S0
	
	M84 X Y E Z  #<--------------

https://reprap.org/wiki/G-code#M84:_Stop_idle_hold

For what’s inside that macro, it should be named: [END _PRINT]

This one does not appear in the log.

1 Like

Where do you see that?? I have M84 in my END_PRINT macro… Not my START_PRINT macro.

[gcode_macro START_PRINT]
gcode:
    G28 # Home all axes
    G92 E0 # Reset Extruder
    G29 # 25 point Bed Level
    G1 Z2.0 F3000 # Move Z Axis up little to prevent scratching of Heat Bed
    G1 X0.1 Y20 Z0.3 F5000.0 # Move to start position
    G1 X0.1 Y200.0 Z0.3 F1500.0 E15 # Draw the first line
    G1 X0.4 Y200.0 Z0.3 F5000.0 # Move to side a little
    G1 X0.4 Y20 Z0.3 F1500.0 E30 # Draw the second line
    G92 E0 # Reset Extruder
    G1 Z2.0 F3000 # Move Z Axis up little to prevent scratching of Heat Bed
    G1 X5 Y20 Z0.3 F5000.0 # Move over to prevent blob squish

    [gcode_macro END_PRINT]
gcode:
    G91 ;Relative positioning
    G1 E-2 F2700 ;Retract a bit
    G1 E-2 Z0.2 F2400 ;Retract and raise Z
    G1 X5 Y5 F3000 ;Wipe out
    G1 Z10 ;Raise Z more
    G90 ;Absolute positioning

    G1 X0 Y230 ;Present print
    M106 S0 ;Turn-off fan
    M104 S0 ;Turn-off hotend
    M140 S0 ;Turn-off bed

    M84 X Y E Z ;Disable all steppers but Z

I found it in your log.

That is a part of my End_Print macro, not my Start_Print macro. If you look at my printer.cfg, you’ll see that my macro should home my axes first.
printer.cfg (6.1 KB)

However, this part of the macro isn’t working, instead it’s failing to do that, which is evident with the error I put in my initial post:

08:16:55 PM $ SET_HEATER_TEMPERATURE HEATER=extruder TARGET=230
08:17:05 PM $ START_PRINT
08:17:05 PM !! Must home axis first: 0.000 0.000 0.200 [-4.000]
08:17:05 PM !! Must home axis first: 0.000 0.000 0.200 [-4.000]

Here is the gcode of the print job I am running:
CalibrationCube-01102024.gcode (467.9 KB)

Here’s a screenshot of my machine settings in Cura:

Right from your klippy.log in the first post as screen copy:

grafik

Did you reload the printer.cfg after you changed it?

image

Check your indentation. If there is indeed this indentation then Klipper will not correctly parse your macros and in this case just continue to attach the instructions from END_PRINT to the preceding START_PRINT

The indentation was definitely there, when I copied the macro, it must of copied funny and I missed it. I’ve fixed that and I’ll run another print job this evening.

IT’S ALIIIIVE!
Thanks you for catching that indentation issue. I can’t believe we missed that. SMH…

1 Like

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