No Motor Power With TMC2209

Hopefully I am posting in the right section. I have an issue that could be related to a couple of things but I have gambled on this...
I have just converted my home-brew printer from a Cartesian to corexy and made a couple of other mods too. I was originally running DRV8825 stepper drivers, which I've changed to BTT TMC2209 V1.2's (with UART) and with it, upgraded to Marlin 2.
Having completed re-assembly and Marlin config, I am pretty sure that my motors are not being supplied with power. After powering up I've completed a number of troubleshooting routes, which includes buzzing out motor wires to make sure they are all working correctly and the stepper drivers are connected to correct lines in the motor. I have also confirmed that each driver is receiving 12v and the VCCIO reads 5V and both the 12V and 5V board outputs are reading their associated voltages. Both the heated bed and hotend power up and achieve desired temps. I think this rules out a dead board. I have also tested a spare 2209, which also results in no power output. The drivers are read by the board, so an M122 command gives all relevant driver info. My final test has been to replace my E0 TMC2209 with an original DRV8825 (updating Marlin accordingly). This results in motor movement, which i think means there is connection between drivers and motors (not shorted something there).

Back to 2209s. I have been puzzling over this for a week now and I have no idea what the issue could be. This is my first stab at configuring using both Marlin 2 and TMC drivers so there is a chance I have missed something obvious but after comparing my build to several tutorials, I can't see what I have done wrong. Any help would be HUGELY appreciated!

Full build is as follows (wiring pictured, also):
Board: Makerbase MKS Gen V1.4 (MS1, MS2 & MS3 jumpers disconnected beneath stepper drivers)
PSU: 12V, 30A
Drivers: BigTreeTech TMC2209 V1.2
Motors: MT-1703HS168A
Endstops: Physical (to rule out a potentially oversensitive stallguard)
FW: Latest Marlin 2 (as of 05/07/2020)

Thanks in advance,
DK

how about including the m122 output?

Your using aux-2, but sadly image is not clear enough to see what pins are going where

Not all pins on the Mega and Mega 2560 support change interrupts, so only the following can be used for RX: 10, 11, 12, 13, 14, 15, 50, 51, 52, 53, A8 (62), A9 (63), A10 (64), A11 (65), A12 (66), A13 (67), A14 (68), A15 (69).

So you have to ensure that your using 63, 64, 65, 66 as RX pins.

Should be wired as

GND|D63 |D40 |D42 |D65
5V |D59 |D64 |D44 |D66

GND|X_RX|X_TX|Z_TX|Z_RX
5V |Y_TX|Y_RX|E_TX|E_RX

Edited 2 time(s). Last edit at 07/14/2020 12:44AM by Dust.

Sure:

X	Y	Z
Address		0	0	0
Enabled		false	false	false
Set current	756	756	630
RMS current	734	734	610
MAX current	1035	1035	860
Run current	23/31	23/31	16/31
Hold current	11/31	11/31	8/31
CS actual	11/31	11/31	8/31
PWM scale	13	13	10
vsense		1=.18	1=.18	0=.325
stealthChop	true	true	true
msteps		16	16	16
tstep		max	max	max
PWM thresh.
[mm/s]
OT prewarn	false	false	false
off time	0	0	0
blank time	24	24	24
hysteresis
 -end		-1	-1	-1
 -start		1	1	1
Stallguard thrs	0	0	0
DRVSTATUS	X	Y	Z
sg_result	0	0	0
stst
olb
ola
s2gb
s2ga
otpw
ot
157C
150C
143C
120C
s2vsa
s2vsb
Driver registers:
		X	0xC0:0B:00:00
		Y	0xC0:0B:00:00
		Z	0xC0:08:00:00
Testing X connection... OK
Testing Y connection... OK
Testing Z connection... OK

Is the Driver registers output obscure? There seems like a lot a 0's in there but being fairly inexperienced with electronics and software I was happy that it wasn't yelling something obscene. (I have just noticed that it is missing E0, ignore that, as I still have a DRV8825 in there)

I checked the pins.h file, which eluded to being able to. Attached image is my 'fag-packet' wiring diagram for the 2209s (sensor-less homing not connected, currently)

Nothing obviously wrong with wiring.

Basically power is applied on driver being enabled.

check
#define X_ENABLE_ON 0
#define Y_ENABLE_ON 0
#define Z_ENABLE_ON 0
#define E_ENABLE_ON 0

and SOFTWARE_DRIVER_ENABLE is off.

Dust you are my Hero!

Commented out software_driver_enable and hey presto we have life! So I have misinterpreted what that function is and assumed it was a requirement to enable communication through UART. I had made a note to check the enable pins (they were already set to low) but not really fully understanding how it all worked, I was hesitant to fiddle with it.

For a slightly greater understanding, what does the software driver enable actually mean/do?

But thank you so much! You have no idea how much headache this has brought me over the last week!

The comment above SOFTWARE_DRIVER_ENABLE in Configuration_adv.h says it all really

* Use for drivers that do not use a dedicated enable pin

You have dedicated enable pins, so should not enable this.

This is for stepper drivers that enable and disable via commands over uart or spi communications