- Posts: 119
- Thank you received: 2
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
If you can make a direct SPI connection between the Raspberry Pi and the TMC drivers, then it should be very easy to adapt my code; all it does is sending the registers value to the drivers according to values you set via parameters until all the registers have been set, and then it reads the motor position. And another function sends velocity command. You'd just need to remove the write velocity part (or, simply said, not addf TMC5160.write) and not connect the position feedback pin. In theory you could still use the SPI line to get TMC status bit and be informed if one driver has an error.Yes. I wanted to communicate via spi only. Since I also configured it in spi mode in daisy chain config in FluidNC. Remora communicate with LinuxCNC via spi. If possible I can send spi config data to tmc via some module in LinuxCNC. Or if you modded remora-spi source to suit tmc 5160
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
More useful to whom? I do have a RPi and TMC drivers and want to avoid to buy an extra device. And the tests I made with FluidNC showed me that I was not able to get smooth acceleration at higher rates, that's why I decided to go full SPI. Maybe the audience would be larger if I'd add the functionality to the Remora code, but it would be useless for me.I think if you look into remora code. They are also sending hex codes payoad via spi such as estop is 0x65737470.
If you would integrate that into remora then it would be more useful.
Please Log in or Create an account to join the conversation.