No movement at all

22:58:22.708 : N15 M122*22
22:58:22.708 : X Y Y2 Z Z2
22:58:22.708 : Enabled false false false false false
22:58:22.708 : Set current 800 800 800 800 800
22:58:22.708 : RMS current 792 792 792 792 792
22:58:22.708 : MAX current 1117 1117 1117 1117 1117
22:58:22.708 : Run current 15/31 15/31 15/31 15/31 15/31
22:58:22.708 : Hold current 7/31 7/31 7/31 7/31 7/31
22:58:22.708 : Global scaler 133/256 133/256 133/256 133/256 133/256
22:58:22.708 : CS actual 0/31 0/31 0/31 0/31 0/31
22:58:22.708 : PWM scale 0 0 0 0 0
22:58:22.708 : vsense
22:58:22.708 : stealthChop false false false false false
22:58:22.708 : msteps 256 256 256 256 256
22:58:22.708 : tstep 0 0 0 0 0
22:58:22.708 : pwm
22:58:22.708 : threshold 79 79 79 658 658
22:58:22.718 : [mm/s] 800.63 800.63 800.63 24.03 24.03
22:58:22.718 : OT prewarn false false false false false
22:58:22.718 : OT prewarn has
22:58:22.718 : been triggered false false false false false
22:58:22.718 : off time 0 0 0 0 0
22:58:22.718 : blank time 16 16 16 16 16
22:58:22.718 : hysteresis
22:58:22.718 : -end -3 -3 -3 -3 -3
22:58:22.718 : -start 1 1 1 1 1
22:58:22.718 : Stallguard thrs 0 0 0 0 0
22:58:22.718 : DRVSTATUS X Y Y2 Z Z2
22:58:22.718 : stallguard
22:58:22.718 : sg_result 0 0 0 0 0
22:58:22.718 : fsactive
22:58:22.718 : stst
22:58:22.718 : olb
22:58:22.718 : ola
22:58:22.718 : s2gb
22:58:22.718 : s2ga
22:58:22.718 : otpw
22:58:22.718 : ot
22:58:22.728 : Driver registers:
22:58:22.728 : X 0x00:00:00:00 Bad response!
22:58:22.728 : Y 0x00:00:00:00 Bad response!
22:58:22.728 : Y2 0x00:00:00:00 Bad response!
22:58:22.728 : Z 0x00:00:00:00 Bad response!
22:58:22.728 : Z2 0x00:00:00:00 Bad response!
22:58:22.728 : Testing X connection… Error: All LOW
22:58:22.728 : Testing Y connection… Error: All LOW
22:58:22.728 : Testing Y2 connection… Error: All LOW
22:58:22.728 : Testing Z connection… Error: All LOW
22:58:22.728 : Testing Z2 connection… Error: All LOW
22:58:22.728 : ok

Whats with the Ok at the last promt?

The ok is just saying it heard your M122.

The 170 is normal. You don’t need a resistor, it is set to 170C in software. You are still not talking to your drivers.

I keep receiving a kill operation on display.

Think perhaps I fried the drivers?

What firmware are you using? Did you compile it yourself?

I used… The one that was posted on here that was already compiled. I apologize, but I can not remember the user that posted it.

Was it configured for 5160 drivers?

I believe so, let me find the link.

https://forum.v1e.com/t/teaching-tech-skr-1-3/11897/2

Autobot blocked my post for the link to this forum. ha ha Here

Did you read the stuff about 5160 problems at the bottom of that thread?

I have.

That’s the binary file I’m using. It looks like to me that there has been 3 successes. Or am I missing something ?

I’ve bent the CLK pin back, and now I get all HIGH errors…

THE CLOCK PIN NEEDS TO BE GROUNDED !!!

Funny as though I only have one driver (CLK) grounded.

00:17:57.078 : N15 M122*22
00:17:57.081 : X Y Y2 Z Z2
00:17:57.081 : Enabled false false false false false
00:17:57.081 : Set current 800 800 800 800 800
00:17:57.081 : RMS current 792 792 792 792 792
00:17:57.081 : MAX current 1117 1117 1117 1117 1117
00:17:57.081 : Run current 15/31 15/31 15/31 15/31 15/31
00:17:57.081 : Hold current 7/31 7/31 7/31 7/31 7/31
00:17:57.081 : Global scaler 133/256 133/256 133/256 133/256 133/256
00:17:57.081 : CS actual 8/31 8/31 8/31 8/31 8/31
00:17:57.082 : PWM scale 8 8 8 8 8
00:17:57.082 : vsense
00:17:57.085 : stealthChop false false false false false
00:17:57.086 : msteps 256 256 256 256 256
00:17:57.086 : tstep max max max max max
00:17:57.086 : pwm
00:17:57.086 : threshold 79 79 79 658 658
00:17:57.086 : [mm/s] 800.63 800.63 800.63 24.03 24.03
00:17:57.087 : OT prewarn false false false false false
00:17:57.087 : OT prewarn has
00:17:57.088 : been triggered false false false false false
00:17:57.089 : off time 0 0 0 0 0
00:17:57.089 : blank time 36 36 36 36 36
00:17:57.089 : hysteresis
00:17:57.089 : -end -1 -1 -1 -1 -1
00:17:57.092 : -start 6 6 6 6 6
00:17:57.092 : Stallguard thrs 0 0 0 0 0
00:17:57.092 : DRVSTATUS X Y Y2 Z Z2
00:17:57.092 : stallguard
00:17:57.093 : sg_result 0 0 0 0 0
00:17:57.093 : fsactive
00:17:57.094 : stst X X X X X
00:17:57.094 : olb
00:17:57.098 : ola
00:17:57.098 : s2gb
00:17:57.098 : s2ga
00:17:57.098 : otpw
00:17:57.098 : ot
00:17:57.098 : Driver registers:
00:17:57.098 : X 0x80:08:00:00
00:17:57.098 : Y 0x80:08:00:00
00:17:57.099 : Y2 0x80:08:00:00
00:17:57.099 : Z 0x80:08:00:00
00:17:57.099 : Z2 0x80:08:00:00
00:17:57.099 : Testing X connection… OK
00:17:57.099 : Testing Y connection… OK
00:17:57.101 : Testing Y2 connection… OK
00:17:57.101 : Testing Z connection… OK
00:17:57.101 : Testing Z2 connection… OK

1 Like

Now a bigger problem…

My motors still dont move. …

Motors work just fine. I forgot I didn’t have the belts connected :pleading_face::tired_face:

2 Likes

So final report.

If you are reading this, here was my solution.

When installing the 5160 drivers, the CLK pin (Third pin on the right, (yellow side) ) needs to be either removed, or bent off to the side. Take caution to ensure the CLK pin, when bent, does not touch other pins on the board.

Once your satisfied with the CLK pin position, you need to ground the CLK pin. I used the input power to accomplish this. However, I would guess that any other ground will work. You DO NOT need to ground each driver. I grounded the x axis driver (far left on the board) and that was the only one I grounded. //Edit// I ended up grounding the CLK pin to the top left hand side of the driver with a simple jumper wire. Which just so happens to be the ground on the driver. :slight_smile: The other CLK pins from their respected drivers were just cut off. You may choose to leave them if you think you will ever need them for other projects.

A special thanks to @jeffeb3 for sticking it out with me for an oddly late evening. Just one last note, I used firmware listed at post 7 of this forum post Here .

Hopefully this will save you a few hours of your time.
Thanks again, Jeff! You’re incite is greatly appreciated!

2 Likes

I wonder if the clk pin is available under the driver as a jumper.

Grounding it seems odd, but I haven’t used the 5160, so maybe it really isn’t clk?

I bought some 2209 drivers with my skr and they work well, FWIW.

But, I am super happy for you. Glad your moving along.

That’s what I’m thinking. I’ll have to dig into the 5160 board layout, but I’m betting what is labeled “clk” on the controller isn’t being used as CLK on the the 5160 and then one of the other pins is being used for that. Maybe it’s using “step” and “dir” for the data and clk to the SPI chip.

I have no idea. This is just me spitballing.