I have a new jackpot CNC controller board I am from in the UK and I have problems with it I don’t want to send it back as took so long to get here.
the issue when I first powered Port B (Z2) did nothing.
So I swapped out the driver from Z (working Port ) thinking maybe a dead controller anyway and still nothing.
I tested the driver from Port B (Z2) in port Z and nothing so i know its a dead driver iI have ordered a new one but port B is not doing anything even with a working driver Could this be a dead port and if so can I change the config to tell use port c as my new (Z2) and how would I do this Thanks in advance.
What a bummer that you have a board that isn’t working right.
There’s some more troubleshooting that we can do.
Can you power up your board with all 5 drivers installed, then send the following command from the terminal and report what it says ?
$SS
It might also be helpful if you can post high resolution pictures of the front and back of your jackpot board, and also the TMC2209 that isn’t working for you.
It is possible to change your config.yaml to re-define Z2 for the final driver location, but before we attempt that, it would be good to get the diag info from the command above so we can be sure there aren’t other issues with your board or config.
Download the newest version of Fluidnc here: Releases · bdring/FluidNC · GitHub
Then unstuff it and you will see fluidterm.
Connect your computer to the Jackpot with a USB cable and open fluidterm.
Then you can type $SS in the terminal.
If you’re using the web UI , you probably have the classic (version 2 WebUI- what ships with FluidNC)
In that case, you can send commands from the section I highlighed below (Much easier than fluidterm if you’re already using the WebUI)
Depending on your browser and screen size, that section may appear in different places in your browser.
If you’re not using the web UI, then you’ll need to use fluidterm as @Britt notes.
Have you swapped the Y2/Z2 TMC2209s and shown that the TMC2209 from the Y2 position works OK in the Z2 position?
Said differently, what does $SS report when you’ve swapped the Y2/Z2 drivers?
You still haven’t answered what revision of Jackpot you received.
I keep asking because there are nuances- and fixes- for things that affected certain combinations of Jackpot/ESP-32s.
When all 5 pluged in the step motor in b socket nothing i swapped the driver from b ro z and step motor in z dont work so dead driver. But if i put any other driver in b still the step motor dont work.
I have a new driver on way. But have no idea b dont work even with a working driver from z
Thanks for posting a driver picture. I"d still like to see the Jackpot itself.
That’s why I keep asking to see the $SS output from each test configuration you have. It provides meaningful debug information for trying to help troubleshoot your issue.
Even when your replacement TMC driver arrives, I’ll still want to see the $SS output as that tells us what FluidNC sees (or doesn’t see) when it boots up.
The solution to this might be dependent on the version of the Jackpot you have. This sounds a lot like the behavior mine exhibited. Have you tried using B without a driver in A? If that works, then I’d bet your board needs the resistor. Pretty simple and quick to add if that’s the problem.
Ryan @vicious1 can tell with high res pictures of the top and bottom of the Jackpot.
Swap the 2209 drivers from port A and B, Run $ss again and let us see it. Make sure all of your pins are in each socket, push the drivers straight in, take note if one feels different than the other.
The board was tested for this exact situation, so it was working when it left.
I need a picture of your Jackpot as wired, top and bottom, please.
I have an idea of what could be happening but I need to see the board itself.
Thank you for you help so far just want to get it working im quite new to this i have 3 3d printers and lazer cutter so not complely new but wanted to get a cnc up and running lol.
they do fit either way but the angles are making me nervous as well.
Please make sure your heatsink has not made contact with the pins on your bad driver, and please send the $ss we requested with the drivers swapped around. The driver can possibly go bad but the port should not.
