Closed OneOfEleven closed 5 years ago
Did you do a "pio lib update"?
The issue template suggests uploading your configuration files.
aahhh, I see you've sneeked some TMC slave address settings into the config adv file ;) ..
/**
* Four TMC2209 drivers can use the same HW/SW serial port with hardware configured addresses.
* Set the address using jumpers on pins MS1 and MS2.
* Address | MS1 | MS2
* 0 | LOW | LOW
* 1 | HIGH | LOW
* 2 | LOW | HIGH
* 3 | HIGH | HIGH
*/
#define X_SLAVE_ADDRESS 0
#define Y_SLAVE_ADDRESS 0
#define Z_SLAVE_ADDRESS 0
#define X2_SLAVE_ADDRESS 0
#define Y2_SLAVE_ADDRESS 0
#define Z2_SLAVE_ADDRESS 0
#define Z3_SLAVE_ADDRESS 0
#define E0_SLAVE_ADDRESS 0
#define E1_SLAVE_ADDRESS 0
#define E2_SLAVE_ADDRESS 0
#define E3_SLAVE_ADDRESS 0
#define E4_SLAVE_ADDRESS 0
#define E5_SLAVE_ADDRESS 0
Added them to my config file and all is now OK.
Sorry about that, my bad for not updating my config files.
I highly suspect I'll be swapping the TMC2208's with TMC2209's or TMC5160's shortly .. when money allows.
The issue template suggests uploading your configuration files.
Thank you for highlighting the problem @teemuatlut
On another note ..
I notice you specify that the TMC capable drivers that can do sensorless homing do it in spreadCycle mode, but from what I read the new TMC2209 does it in stealthChop mode (new stallGuard4).
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Using the latest bugfix 2 in Atom/platformio with TMC2208's using software serials getting ..
"error: 'X_SLAVE_ADDRESS' was not declared in this scope"
error (and Y_SLAVE etc) s showing up when trying to compile (totally fresh libs as deleted .pioenvs and .piolibdeps directories before compile).