How to configure TMC5160 on MKS Tinybee?

[ashokmanker]

I am using MKS Tinybee board. I know mks Tinybee don't support tmc5160 natively. But I have successfully configured tmc5160T on selected axis on FluidNC. After few modifications and jumper wiring I was able use tmc5160 with spi interface.
How can I configure tmc5160 on selected axis on grblhal? I am using tmc5160 in Daisy chain config.
Any help will be appreciated

[terjeio]

You'll have to modify the map file, see this for an example.

[ashokmanker]

I have seen this and configured but where do i define driver index since I have wired in daisy chain. In FluidNC i defined
Miso, mosi, clk, cs. Miso mosi clk same as sdcard. Defined separate cs for tmc. Then defined driver index for each axis which is using tmc according to position of driver in chain.

[terjeio]

Driver CS is defined here, chain is X first, then Y, Z , M3 (A or ganged motor) etc, SPI pins shared with any SD card.

[ashokmanker]

I have done that. And defined Trinamic_spi_enable 1Trinamic_enable 5160Motor_cs_pin gpio_num_14Estop_enable 1Estop_pin auxinput0_pin
I want to use drv8825 on xyzAnd 5160 on a,b in daisychain
(In FluidNC i define spi_index 1 & 2 for a and b respectively)

[ashokmanker]

always this error comes. [MSG:Warning: Could not communicate with stepper driver!]

[ashokmanker]

I have done that. And defined Trinamic_spi_enable 1Trinamic_enable 5160Motor_cs_pin gpio_num_14Estop_enable 1Estop_pin auxinput0_pin I want to use drv8825 on xyzAnd 5160 on a,b in daisychain (In FluidNC i define spi_index 1 & 2 for a and b respectively) Yahoo Mail: Search, organise, conquer On Fri, 26 Apr 2024 at 15:10, Terje ***@***.***> wrote: Driver CS is defined here, chain is X first, then Y, Z , M3 (A or ganged motor) etc, SPI pins shared with any SD card. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[terjeio]

Tried hard but evertime driver fails.

How? Crashes completely or with this message: [MSG:Warning: Could not communicate with stepper driver!]

[ashokmanker]

Yes. Could not communicate with stepper error. By the way I am compiling on linux with esp-idf. Because firmware compiled on platformio always causes CPU fault on ESP32.

[terjeio]

Have you commented out M3_LIMIT_PIN and M4_LIMIT_PIN in the map file? These pins are used for SPI and cannot be used as limit inputs.

[ashokmanker]

Yes i have already commented out those pins. And double checked for conflicting pin assignment

[terjeio]

Somewhat improved SPI code for the ESP32 was committed yesterday. Tested ok (no motor connected) with a single driver for the A-axis ($338=8) on a breadboarded ESP32 and with a single TMC5160.
I have not tested with the SD card enabled, not sure that will work since it has separate and possibly incompatible SPI initialization.