Jackpot only moving one stepper

Lately I’ve had random issues with only one stepper moving when jogging Y or Z. It only happens in a jog, never when running a job or homing. And its completely random so far. I haven’t figured out how to make it happen. Just wondering if anyone else has run into this and if so what did you find?

Running fluidnc 3.7.10 and @vicious1 config. Only changes were I bumped the driver current up and changed the pins for WLED. Its been running fine. Did it once the other day then today its done it 4-5 times. But hasn’t in the last hour and I’ve been running several small jobs back to back with a lot of movement

1 Like

Does it go away when you power cycle?
Which version of Jackpot do you have?
Which ESP-32 (MicroUSB or USB-C)?
Does your ESP32 have a pullup resistor installed as an add-on?

I ask because we’ve seen a few instances where some ESP32s don’t boot properly, and if FluidNC doesn’t properly set up one or more of the steppers, then weird stuff like that happens.

I’m curious if it happens to you during a jog, and you power cycle the Jackpot, if the problem goes away (another indication you may have one of the ESP32s that needs the pullup resistor added)

1 Like

I also have not tested 3.7.10, I still use 3.7.8.

1 Like

Seems to, for a little while. But its not usually fresh after a power cycle when it happens. Y I’m forced to power cycle. Z I just home again and all is well. Like I said its very random

micro usb. No pull up resistor.

What module do you have on there? Was it a spindle controller? If so are you sure it is grounded well and the wires are far away from the rest. Some spindles are crazy electrically noisy.

Did you try 3.7.8 to see if it helps?

Yes it is a RS485 card from Bart. And yes the wires are all grounded. It hasn’t happened since about 4 hrs before I made the post. If it starts happening again I will take the card out and see if that has any difference.

No sir I haven’t yet. Didn’t run it much today. Yesterday it was cutting all the parts for a Dust filter that I put together and installed today. I did make about 5 small cuts today and it did good. Tomorrow I’m hoping to run a Vcarve and see how it does. But then again it doesn’t have any issues during a job. Only when moving the machine around to set zero or move it out of the way. So at that time the spindle isn’t even running… I will flash it back to 3.7.8 tomorrow and see how it does.

1 Like

Ok it went nuts tonight and messed up during a cut. This time it was driving one Y stepper faster than the other. Just downgraded to 3.7.8 and will see how that goes.

1 Like

I am literally updating to the latest to test it on a long cut right now.

What ESP32 is on your board?

Still using the spindle?

thats happened a few times when FluidNC didnt boot properly…

micro usb

Yes, but that’s been the case since the beginning of switching both of my machines over to the jackpot. The only 2 variables are the RS485 board and the update to 3.7.10. I am running your shielded cable for the RS485 but it runs straight out of the case and off the machine. And it is grounded

this wasn’t a fresh boot. It had actually been on for a while. Planned to start this cut much earlier but life had other plans.

Everything went good with the cut. Will hopefully been running quite a few more tomorrow so we will see if it acts up anymore.

But not in the middle of a cut, that part is really odd. How do you lose communication/settings with a driver mid job?

Have you changed the driver current from stock, any chance of them overheating and one not moving?

Does FluidNC spit out any error messages if a TMC driver goes into thermal shutdown? Where is that displayed on the GUI if it happens?

In the terminal, you will see something I would guess. If you do not reboot, you can scroll up to see it.

Dude, there is just no way you can possibly ALWAYS get the odd random weird issues. At this point it is blowing my mind. Everything has had some new issue we have never seen before, like everything…not just mine, Kobalt as well.

I did bump the current up a little bit. It couldn’t home Z at the settings it was at. And I have your temp gauges on all of the steppers and they are WAY cool compared to when I had the SKR on there. Next time it happens ill keep an eye on the terminal and see if it pops up anything. I didn’t even think to check before.

I’m sure it all boils down to user error LOL

Nope…

More than the current on my newest configs? How much? Do you have a fan in your case or a lot of room for airflow (tidy wires)?

Hmmmm also you are running LEDS…maybe dissconnect them to make sure they are not interfering, or messing with the power supply.

config.zip (1.6 KB)

My box is larger than yours but doesn’t have a fan on it. But i will say its been cool here in FL lol.

Also it didn’t stop running the stepper. They were both running, just at different speeds. Even after i canceled the job and tried to home the Y1 stepper was outrunning the Y2

I will give that a shot. I’ve been lazy and still haven’t tied the grounds together so that could be part of it. They are on a separate power supply from the jackpot if that matters

Absolutely. A voltage differential can do all sorts of odd things. This is suspect #1 for me right now.

1 Like