Around 7 minutes of preparation for each print?

[DevWMJ]

I’m trying to figure out why my AD5X with ZMOD takes ~7 minutes before every print starts, despite print quality being excellent.

Observed behavior:

• nozzle heats to target (210C)
• then drops to ~ 121C
• printer performs multiple homing, probing, purge, and cleaning routines
• reheats back to 210C
• repeats additional purge/filament routines
• finally starts printing

From the logs it looks like:

• _PRINT_CLEAR_NOZZLE
• native nozzle cleaning
• AutoZ / _TEST_POINT
• PROBE_CALIBRATE
• repeated GET_FILAMENT_VALUE
• multiple purge cycles

are all running in sequence.

The biggest delay seems to be:

• cooling from ~183C to ~121C for probing
• then reheating back to 210C afterward

I suspect:

• duplicate startup logic between native Flashforge routines and ZMOD macros
• duplicate nozzle cleaning
• duplicate AutoZ/probing
• excessive filament verification

Question:
Which startup routines are considered redundant/safe to disable on AD5X + ZMOD setups to reduce startup time without hurting first layer quality?

Attached log excerpt shows:

• _START_PRINT
• _PRINT_CLEAR_NOZZLE
• _ORIG_CLEAR_NOZZLE
• PROBE_CALIBRATE
• _TEST_POINT
• repeated GET_FILAMENT_VALUE

klipper_console.txt

[DevWMJ]

My current way to fix the delay is by running the following commands:
SAVE_ZMOD_DATA AUTOZOFFSET=0
SAVE_ZMOD_DATA MESH_TEST=0
SAVE_ZMOD_DATA PRE_CLEAR=0
SAVE_ZMOD_DATA PRINT_LEVELING=0
SAVE_ZMOD_DATA CLEAR=NONE

Not ideal, but it's the best I can do, this saves almost 4-5 minutes of the preparation.

[ghzserg]

Turn off your native screen and control exactly what you need.

[DevWMJ]

I wonder if there is a way to get an optimized screen less configuration? Which steps are a must-have? What does the native screen usually do?

This is a rough sketch of what AI tells me is needed, but I am by no means an expert in these things.

[gcode_macro START_PRINT]
gcode:
# Parameters passed from your slicer
{% set BED_TEMP = params.BED_TEMP|default(60)|float %}
{% set EXTRUDER_TEMP = params.EXTRUDER_TEMP|default(210)|float %}

# Start heating bed and extruder simultaneously
M140 S{BED_TEMP}
M104 S{EXTRUDER_TEMP}

# Home the printer
G28

# --- AD5X Specific Commands from Z-Mod ---

# Wait for bed to reach temperature
M190 S{BED_TEMP}

# Load your saved bed mesh (e.g., "45" or "35")
BED_MESH_PROFILE LOAD={BED_TEMP}

# Inform the system about the total number of layers (for progress display)
SET_PRINT_STATS_INFO TOTAL_LAYER={total_layer_count}

# This is a key command for the AD5X's IFS to manage the purge tower and multi-color logic
SET_ZCOLOR FILENAME="{filename}" ALLOWED_TOOL_COUNT=4

# Wait for extruder to reach temperature
M109 S{EXTRUDER_TEMP}

# --- Done ---
RESPOND PREFIX=info MSG="Print Started"

I am using the Nopoop .4 orcaslicer profile, would i need to change things in the g code?

RESPOND MSG="Pre-Processing purge mode results:"
{if purge_in_prime_tower && print_sequence == "by layer"}
RESPOND MSG="Purge in prime tower option enabled. Using 'nopoop' mode."
SAVE_VARIABLE VARIABLE=use_trash_on_print VALUE=0
{else}
RESPOND MSG="Purge in prime tower disabled or print 'by object' detected. Using 'slicer-controlled' poop mode."
SAVE_VARIABLE VARIABLE=use_trash_on_print VALUE=2
{endif}
START_PRINT EXTRUDER_TEMP=[nozzle_temperature_initial_layer]
BED_TEMP=[bed_temperature_initial_layer_single]
MESH=[bed_temperature_initial_layer_single]
M140 S[bed_temperature_initial_layer_single]
M104 S[nozzle_temperature_initial_layer]
SET_PRINT_STATS_INFO TOTAL_LAYER=[total_layer_count]