1HCL Ponderings

[ShaunCro]

Evening Gents,

Just wondering why you chose the 2160-TA over the 5160-TA for the 1HCL?

I take it you are doing the encoder tracking on the STM MCU? And wondering why you didn't go for the 5160-TA which has the ability natively to track the encoder pulses without the additional MCU (or the TMC4361 chip which wants you to use on the lower end *130*160 chips) also, will we perhaps see a board with the 5160 later on? Nothing wrong with the 2160, just been wondering about that since I stumbled across the git repository a couple months ago.

[dc42]

@shauncro the TMC5160 shares the encoder input pins with the step and direction pins. So implementing open loop mode (which is needed for tuning at least) would have been more difficult. Also reading the encoder count from the TMC5160 over SPI would incur additional latency and probably reduce the achievable PID loop frequency.

[ShaunCro]

@dc42 thanks for the info, makes perfect sense when you put it like that. Hoping Day Vinci Lab will get some in soon as they the only retailer for us locally. Any plans to look at brushless esc's coupled with encoders any time? Or adding o-drive can compatibility?

[dc42]

@shauncro said in 1HCL Ponderings:

Any plans to look at brushless esc's coupled with encoders any time? Or adding o-drive can compatibility?

Hangprinter 4 already uses Duet 3 with O-drives. It uses the secondary CAN bus to setup the drivers, but standard step/direction signals to step them in order to get precise motion control.

[ShaunCro]

@dc42 OOOOH. Thanks for the info, I'll get to playing then!