Now this is the tmc2130 version, using the same hardware setup, except the 8 pin cable with control pins.

Now that I know how to talk to tmc2130 in standalone mode, next step is to talk in SPI. I am starting by searching EEQE for any old post useful. I found 17 posts but they are not very useful either because they are too short for newbies, or they are not for Rpi and python.

I do find useful tips on how to power up down so not to fry the drivers:

References:

Another useful tip I got from old EESE posts are: (1) TMC21xx version 1 and version 2 have different pinouts, (2) Some mdoule have bugs (wrong/missing connections)

Anyway, I am going to spend this lock down weekend to try out my luck on (1) SPI mode operation and programming of TMC2130 v1.1, 1.2, 3.0.

I found that I have fried 2 tmc2130 module, perhaps because (1) I did not power up Logic poser and Motor power in the correct sequence, (2) my bad soldering job when messing with the SPI jump opening/shorting, (3) carelessly wrongly connected the wrong wires (12V to 3V cct, wrongly reversing voltage polarity, etc).

Si this time I am tidying up the wiring and labelling them properly:

Bad photo to late to delete, therefore uploading another one.

I am drafting my SPI mode operation testing plan. Below is a summary.

1. I will first use Pico MicroPython GP pins to do pin configuration, using MicroStep Resolution full step and 1/16 step for comparison with SFT mode setting.

2. I will also use Pico code to send Step/Dir pulses to move the motor.

3. I will then open SPI enable/disble jumper to select SPI mode.

4. I will use Datashet Section 23.1 to try to initialize the driver, and hopefully using MicroPython code to send Step/Dir pulses to move the motor.

5. I will then write 40 bit datagrams to write to registers to change microstep resolution eg, full step and 1/16 step, and see if motor speed changes.

Comments and suggestions welcome. Almost bed time. See you tomorrow.