Before you apply these macros you should take note that Klipper cuts against the grain when it comes to start and end code. In general, klipper likes to call a start and end macro and then the user can define what should happen within each macro within the klipper config. This de-embeds the start and end commands from the gcode and makes them flexible, even if you are printing the same file.
In principle this is useful but in reality it is not frequently used and therefore some people decide to stick with the start and end codes embedded into the gcode from the slicer. If you are one of those people then these macros will allow your klipper enabled BX to understand cura start code:
########################################
# MARLIN TO KLIPPER MACROS
########################################
[gcode_macro G34]
gcode:
Z_TILT_ADJUST
G28 Z
[gcode_macro G29]
gcode:
BED_MESH_CALIBRATE
[gcode_macro M900]
gcode :
{% set K = params.K|default(0)|float %}
SET_PRESSURE_ADVANCE ADVANCE={K}
I installed klipper on my B1 as the marlin build from Biqu doesn’t work well when fitted with a abl. now I have dual z, with the Biqu idex kit and CRTouch install, but would like to run marlin as I can’t get klipper to perform idex properly.
Any chance your thinking of doing a idex fork of marlin?