Qidi X-Max Icarus BLTouch mount

thingiverse

To [measure the distance of the toolhead to the mesh for the klipper](https://www.klipper3d.org/Bed_Mesh.html) bed mesh (compensation), you need a probe like an BLTouch which needs to be mounted to the toolhead. I've switched from the original Qidi Extruders to [humebeam](https://www.thingiverse.com/humebeam)'s [Icarus 2.1](https://www.thingiverse.com/thing:4968938) due to massive problems with the print quality. This switch also allowed me to add various measurement devices (like a dial gauge) to the front of the toolhead. Only a new adapter had to be designed to mount the BLTouch firmly in place. It follows the same principles as the original dial gauge holder but also uses the screw head of one of the fan screws to vertically stabilize the mount. Additional materials required: * 1x M3x20 screw for icarus holder (can be a little bit more or less in length) * 3x M3 inserts ([ruthex](https://www.ruthex.de/collections/gewindeeinsatze/products/ruthex-gewindeeinsatz-m3-100-stuck-rx-m3x5-7-messing-gewindebuchsen)/[CNC kitchen](https://www.cnckitchen.com/shop#!/Gewindeeinsatz-threaded-insert-M3-Standard-100-Stk-pcs/p/431146823/) recommended) * (optional) 3x M3 inserts for the front facing holes to temporarily mount an ADXL345 * (optional) 2x M3x6 screws for the ADXL345 (can be a little bit more or less in length) It is not recommended to leave the ADXL345 on the Icarus after finishing the resonance measurement. Otherwise there is a chance to collide with camera mounts or similar things. It is also recommended to check manually if the mount would collide with anything. I have for example reduced my stepper_y's position_max after noticing problems with the filament guide - which also gave me enough room for this bltouch mount. It also looks like the V4.6 board didn't connect the S pin (actually the control pin) of the Level JST-XH terminal on the toolhead mini-PCB to the CPU/MCU. Interestingly, the S of the 2-pin JST-XH terminal next to it was connected fine to the MCU (PE3) and can be used as Zmin endstop. I've worked around the missing control pin by using some flex cable to connect the control pin of the BLTouch to either the WiFi socket of the mainboard or an raspberrypi: The klipper configuration for for an raspberrypi on GPIO27 (not recommended due to some timing problems with the Linux MCU process of Klipper which can cause "No trigger on probe after full movement" emergency shutdowns): ``` [mcu rpi] serial: /tmp/klipper_host_mcu [adxl345] cs_pin: rpi:None [resonance_tester] accel_chip: adxl345 probe_points: 150, 125, 20 [bltouch] speed: 3 lift_speed: 10 sensor_pin: PE3 control_pin: rpi:gpio27 probe_with_touch_mode: False sample_retract_dist: 3 samples: 1 x_offset: -25 y_offset: -53 z_offset: 2.060 [bed_mesh] speed: 120 horizontal_move_z: 10 mesh_min: 5, 5 mesh_max: 270, 186 probe_count: 5, 5 ``` It works a lot better when removing the ESP8266EX based wifi module and use following configuration instead: ``` [bltouch] speed: 3 lift_speed: 10 sensor_pin: PE3 # WARNING: this pin is originally connected to the WiFi module (which needs to be removed first) control_pin: PG1 probe_with_touch_mode: False #samples: 3 x_offset: -25 y_offset: -53 z_offset: 2.030 [bed_mesh] speed: 120 horizontal_move_z: 7 mesh_min: 5, 5 mesh_max: 270, 186 probe_count: 5, 5 ``` The PG1 pin can be found easily when looking from the top on the board: ``` WiFi +------+------+------+------+ | VDD | PG1 | VDD | Vcap | +------+------+------+------+ | PB10 | GND | NC? | GND | +------+------+------+------+ | | | | | | | ESP8266EX | | | | | | | +---------------------------+ ```