QGL with G38 commands help #29
Unanswered
WillowWispLboro
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey there! I've been following this fork for a while and am using it for a custom bioprinter build, a flying gantry CoreXY toolchanger machine using custom home-able syringe extruders as toolheads. I'm currently having a little trouble getting quad gantry levelling working using G38 commands and was hoping I could get some help getting things up and running.
The toolchanger setup is based on DraftShift's StealthChanger, and each toolhead has an OptoTap optical endstop used for recognition of the current active tool, listed in firmware as the tool probe per the StealthChanger installation instructions. There is then a standard microswitch Z endstop at the top of the gantry used for G28 commands, necessary for homing the Z axis prior to loading a tool, and finally a series of daisy-chained microswitches (defined as a multiprobing probe in firmware) at the 4 corners of the build area I would like to carry out QGL with.
The default Klipper behaviour for a QGL run on a toolchanger is to use the probe associated with the active tool for the necessary probe actions, but the tool probes are just the optical endstops used solely for recognition of the currently-active tool, leading to the process immediately failing. I'd like to be able to force the QGL process to instead use the "MULTIPROBE3" G38.3 command and probe towards the bed using the daisy-chained microswitches as the probe. Does anybody here know how I could set up a gcode macro to do this? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions