Note that in the lower image, there are two pins at the “front” of the module which are missing in the upper image. One of these pins is “DIAG” and if it is missing, then you will not be able to get sensorless homing working.
If that’s the case then you have to solder in the two pins or get a couple of TMC2209 modules from somebody other than Two Trees (which have the two pins already soldered in).
This is particularly frustrating for me because a couple of weeks ago I wrote:
Note that I didn’t include the Two Trees module as I haven’t worked with it.
Hopefully this is your problem and I’m sorry that it can’t be fixed in software.
I’m really happy we figured out your problem and you are back working. I’m going to go back and update that page with the Two Trees TMC2209 Module so that anybody with the same problem in the future will have some clues as to what to do.
I think the decision as to whether or not go with RatRIG is based on what you have set up in terms of your host. When I look at the RatRIG OS page:
If you’ve set up a Raspberry Pi to work with with RatRIG OS already then I would say go back and take the comments out of the macros and go from there.
If you haven’t set up RatRIG OS, then I would recommend that you continue with what you have as you’re more than half way to a functional printer, you understand everything which makes it easier to tune to get everything working.
The big thing you’ll need is a homing macro and I think you can work with these:
[gcode_macro global] ### Global Variables
variable_xy_run_current: 0.8
variable_xy_home_current: 0.6
gcode:
[gcode_macro _HOME_X]
gcode =
SET_TMC_CURRENT STEPPER=stepper_x CURRENT={printer["gcode_macro global"].xy_home_current}
SET_TMC_CURRENT STEPPER=stepper_y CURRENT={printer["gcode_macro global"].xy_home_current}
G4 P500
G28 X
SET_TMC_CURRENT STEPPER=stepper_x CURRENT={printer["gcode_macro global"].xy_run_current}
SET_TMC_CURRENT STEPPER=stepper_y CURRENT={printer["gcode_macro global"].xy_run_current}
G91
G1 X150 F1200
[gcode_macro _HOME_Y]
gcode =
SET_TMC_CURRENT STEPPER=stepper_x CURRENT={printer["gcode_macro global"].xy_home_current}
SET_TMC_CURRENT STEPPER=stepper_y CURRENT={printer["gcode_macro global"].xy_home_current}
G4 P500
G28 Y
SET_TMC_CURRENT STEPPER=stepper_x CURRENT={printer["gcode_macro global"].xy_run_current}
SET_TMC_CURRENT STEPPER=stepper_y CURRENT={printer["gcode_macro global"].xy_run_current}
G91
G1 Y150 F1200
[homing_override]
axes = xyz
gcode =
{% set home_all = 'X' not in params and 'Y' not in params and 'Z' not in params %}
{% if home_all or 'X' in params %}
_HOME_X
{% endif %}
{% if home_all or 'Y' in params %}
_HOME_Y
{% endif %}
{% if home_all or 'Z' in params %}
G28 Z
G1 Z10
{% endif %}
The first macro (global) provides you with the ability to set your operating currents for printing and homing.
The next two execute the homing and places the toolhead in the middle of the movement range (going by your printer.cfg, your print area is exactly 300mm x 300mm) so that when you do your Z axis homing, you do it in the middle of the print bed.
The final one supercedes the basic Klipper homing functionality and customizes it to your board.
Let me know how you make out and if you have any other questions.
I’ve now gotten reply permissions again, and I’ve already set up a raspberry pi with RatOS, going back to it it now homes properly but can probably be softer, will probably tune driver_SGTHRS for a bit, but for some reason now it is homing towards maximum Y instead of minimum. The homing macro listed above works perfectly in all regards, so might be something in the RatOS macro.
I think I’m going to use the RatOS macros and leave the direction it homes in since it parks towards the back, and everything else is working. I’ve gotten the homing to bump at 80 sensitivity on both, and I think that’s all I needed to do. Thanks for all your help and patience for getting this issue fixed!
