Neptune4.help

FAQs and Facts for the Elegoo Neptune 4 Series 3D Printer

User Tools

Site Tools


run_bed_mesh

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
run_bed_mesh [2025/10/03 19:56] dshooprun_bed_mesh [2025/10/07 05:43] (current) – ↷ Links adapted because of a move operation dshoop
Line 36: Line 36:
 ==== G29 ==== ==== G29 ====
  
-Note: the G29 gocode is a marlin gcode and not an actual gcode in [[Klipper]], and in Elegoo's distribution of [[printer.cfg]] it may, or may not otherwise, be implemented as a [[macro]]. Klipper instead natively implements the ''BED_MESH_CALIBRATE'' command which features a richer set of parameters and can accomodate [[adaptive_bed_mesh]]. As such consider that using G29 instead of the Klipper command is unreliable and unpredictable as its behavior may change. There's no reason not to use the Klipper correct ''BED_MESH_CALIBRATE''+Note: the G29 gocode is a marlin gcode and not an actual gcode in [[Klipper]], and in Elegoo's distribution of [[printer.cfg]] it may, or may not otherwise, be implemented as a [[macros]]. Klipper instead natively implements the ''BED_MESH_CALIBRATE'' command which features a richer set of parameters and can accomodate [[adaptive_bed_mesh]]. As such consider that using G29 instead of the Klipper command is unreliable and unpredictable as its behavior may change. There's no reason not to use the Klipper correct ''BED_MESH_CALIBRATE''
  
 ==== Full Bed Mesh ==== ==== Full Bed Mesh ====
/app/data/attic/run_bed_mesh.1759535783.txt.gz · Last modified: by dshoop

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki