Hi guys,
I'm having somewhat of an issue here.
I just recently replaced my printer board with a ramps 1.4 board so I could utilize the TMC2130 drivers.
So I also got 4 of those, and have wired them according to this guide: [toms3d.org]
I've got Marlin 1.1.8 on it, and did all the changes I believe necessary, to utilize the TMC2130's.
Unfortunately, when I power the printer on, I get the following message:
And it then goes into a loop of turning down the current.
untill I kill it (even goes into negatives..).
It is definitely not overheating. It is immediately after boot and cooler is not warm at all.
I've googled around a bit, and saw some people had success with changing the Y_CS_PIN to 4. I've tried that, but it didn't really help. In fact, after doing that, I now also get the warning for the e0 driver.
So, my big question here is, is there any way I can proper debug this issue?
I'm guessing it could be me who did something wrong or the drivers that are damaged. Can I determine this somehow, without ordering new drivers?
I'm having somewhat of an issue here.
I just recently replaced my printer board with a ramps 1.4 board so I could utilize the TMC2130 drivers.
So I also got 4 of those, and have wired them according to this guide: [toms3d.org]
I've got Marlin 1.1.8 on it, and did all the changes I believe necessary, to utilize the TMC2130's.
Unfortunately, when I power the printer on, I get the following message:
READ: 00:00: Y driver overtemperature warning! (800mA)
And it then goes into a loop of turning down the current.
READ: Y current decreased to 750 READ: Y current decreased to 700 READ: Y current decreased to 650 READ: Y current decreased to 600
untill I kill it (even goes into negatives..).
It is definitely not overheating. It is immediately after boot and cooler is not warm at all.
I've googled around a bit, and saw some people had success with changing the Y_CS_PIN to 4. I've tried that, but it didn't really help. In fact, after doing that, I now also get the warning for the e0 driver.
So, my big question here is, is there any way I can proper debug this issue?
I'm guessing it could be me who did something wrong or the drivers that are damaged. Can I determine this somehow, without ordering new drivers?