Remora - Rpi Software Stepping Using External Microcontroller via SPI

Thanks a lot, it kinda works now or at least i can move the motors. Only weird thing is motor0 and motor1 aren't working but the other 6 do, so that's a good thing i guess.
Oh and sorry again for my stupid questions.
see ya

What part worked?

The motors will move even if the TMC doesnt configure. motor0 and motor 1 are connected to the same output buffer, if the buffer is damaged motors0 and 1 wont get the enable signal it looks like

Ah okay, so just because the motors are moving doesn't mean the firmware configured right?
So the problem is still there

If there was an issue with the motor0/1 not working at all, that could explain why the TMC drives werent working but maybe not. Just start up and check the remora serial output as you have been doing, and look for " TMC drivces OK" or something like that.

If the TMC drives dont get configured, they load the default settings, so your microsteps and current might not be what they are supposed to be.

Even on the other motor ports the TMCs aren't responding.
The serial output didn't change.

 

Hmm I see the level shifter for the UART pins on the PRO is not present on the regular octopus v1.1(where i tested more stuff). I am having issues with another board that has a level shifter on the UART, so I will ask around if its working and test out this week and will report back

Hmm ok that confirms it. I did most of my octopus functionality testing on the octopus v1.1, I didnt like the buzzer on the pro. The octopus PRO has level shifters on the UART lines. When I jumper the TMC UART line to another pin, it configures fine. That is the only thing I can think of. But this overlaps with another issue Im having with another board, that also has a level shifting circuit on the UART line.

Scott, if you can provide input/assistance on this issue, it would be appreciated.

Im trying to support this mellow flyCDY3 board, but the uart isnt working. I tried changing the baudrate, but no luck. Thankfully my buddy mdroberts is much smarter than me, so he collected some data for me on the issue.

It looks like i cant upload the excel file he made, but here is what he said

Further to the TMC2209 read-back. I used the scope UART decode feature to confirm that the programmed values sent to the TMC2209 seem reasonable and consistent with the registers, but the TMC2209 doesn't put any data out after a register read is requested. The sequence after resetting the board is provided in the attached.

I just don't see any output from the 2209 when a register read is done.

So nothing i can do against it right now? :/
 

For those who may be interested. I've updated the remora-spi component to now interrogate the device tree to determine the hardware being used.

github.com/scottalford75/Remora/tree/mai...omponents/Remora-spi

I've been a little quite online lately. Been busy working on the STM32H7xx version of Remora with a lot of refactoring and hardware abstraction in preparation for the next steps to a common code base. I've also managed to get PlatformIO up and running for development and debugging. Important to be able to support multiple boards.

For those interested, the testing repo is:https://github.com/scottalford75/Remora-STM32H7xx-PIO

Inspired by the great work done by Sean McCully, github.com/seanmccully , the Remora code base has been significantly been reworked:

Remora is now a class of it's own
Communication is now handled via a comms handler, with hardware abstraction via a CommsInterface class
Hardware agnostic by creating hardware specific classes in main and then passing them over to the Remora constructor

The next steps....
Setup a organisation repo for Remora. We need a repo name as Remora is already taken
Setup the core Remora repo
Test the submodule approach with the STM32H7 work to date
Test with STM32F4 etc

BTW, TMC5160 support is working in the H7 testing repo so were not too far off having this across other boards as well.