Jackpot unboxed Easy setup except Y2 won’t turn

So I gave up on Klipper and ordered the Jackpot board for my Primo build. Plugged in my wires and 24v power supply, found the Wi-Fi and the control dashboard came up. Easy peasy!

This was so easy compared to what I had to do with klipper!

I twitched 0.1mm moves to test direction and I just had to flip the plug over on X2. X and Z axes work perfectly.

But Y2 doesn’t move at all.

I’ve tried 3 different 2209 drivers, including one that was definitely working 2 days ago on the klipper board. I also tried switching y1 and y2 and confirmed that the motor is good.

I haven’t touched any of the files

All the motors hold their position when the board is powered, including y2.

I’m lost, don’t know what to try next. Any help?

Thank you
Mark

Step 1, post your config. Lets go through that.
Have any pics you can post?

When you move Z, does Y2 maybe move then? It seems to me that with a 0.1mm movement you might have missed a bit of movement of the other motor. (Even though the Y would move 4× the expected Z movement.)

It’s a thought as to what might be wrong…

Your config file and a picture of the board connections would be helpful. A pic of the overall machine, too.

config yaml.gcode (6.5 KB)
This is actually config.yaml I had to copy it into notepad and save it with an extension that the forum would allow. This file is unchanged from the flashed Jackpot board I just received this week.

I moved X and Z 10mm and felt no movement on Y2.

I followed the wiring in this image from the documentation:

I couldn’t find a pinout to check against the config.yaml file.

Looking ahead to the next couple questions: I don’t know how to have the (DW660 single speed) spindle start/stop with a 5-24v signal to my SSR, or how to use the probe. [Also I would like to set up the 6th motor driver for a rotary unit, either as a substitute for X, or as a true 4th axis. the pinout would help with that ]

Here are some pictures of the board and the Primo, not sure what you are looking for, happy to take more photos.



Thank you

Y1 moves? But y2 does not? Switch the terminals on the board, does it follow through? Does y2 now move?
Both motor 1s have addr: 3

I dont have tmc but i think they need to be unique dont they?

Yes. If I switch y1 and y2, then y2 moves but not y1. All signs suggest that something is wrong on the main board at the B driver position. I don’t know if the addr3 must be unique.
I also could try using C position but I don’t know what to change in the yaml file.

No.

On the jackpot board, the last three TMC2209s all have address 3. They’re on a serial mux.
A, B, C as labeled on the board all share address 3.
So, as labeled on the Jackpot board:
X TMC address 0
Y TMC address 1
Z TMC address 2
A TMC address 3
B TMC address 3
C TMC address 3

I think the problem here is that @MarkC 's config.yaml file might be wrong.

The Y2 motor should look like the following. (Try changing the bolded section)
Edit: The order is different but the bold item is the only one different.
Edit 2: If this doesn’t fix it, we could have you put the TMC2209 in the C position and edit the YAML to be for that position. That would help rule in/out a problem with the B position on the Jackpot.

#B
motor1:
limit_neg_pin: gpio.34:high
limit_pos_pin: NO_PIN
limit_all_pin: NO_PIN
hard_limits: false
pulloff_mm: 5.000
tmc_2209:
uart_num: 1
addr: 3
cs_pin: i2so.19
r_sense_ohms: 0.110
run_amps: 0.680
hold_amps: 0.500
microsteps: 8
stallguard: 0
stallguard_debug: false
toff_disable: 0
toff_stealthchop: 5
toff_coolstep: 3
run_mode: StealthChop
homing_mode: StealthChop
use_enable: false
step_pin: I2SO.18
direction_pin: I2SO.17
disable_pin: I2SO.16

This is taken from Ryan’s github

1 Like

Also taken from Ryan’s github, here’s what the C position would be: (I note the GPIO39:low seems odd to me)

c:

motor1:
  limit_neg_pin: gpio.39:low
  limit_pos_pin: NO_PIN
  limit_all_pin: NO_PIN
  hard_limits: false
  pulloff_mm: 3.000
  tmc_2209:
    uart_num: 1
    addr: 3
    cs_pin: i2so.22
    r_sense_ohms: 0.110
    run_amps: .1000
    hold_amps: 0.050
    microsteps: 16
    stallguard: 0
    stallguard_debug: false
    toff_disable: 0
    toff_stealthchop: 5
    toff_coolstep: 3
    run_mode: StealthChop
    homing_mode: StealthChop
    use_enable: false
    step_pin: I2SO.21
    direction_pin: I2SO.20
    disable_pin: I2SO.23

No luck yet.

With y2 on B position
#B
motor1:
limit_neg_pin: gpio.34:high
Same behavior as originally

With y2 on c position
motor1:
limit_neg_pin: gpio.39:low

No movement. In fact no holding, it behaves as if it’s not plugged into anything.

What does it do if you make C be
motor1:
limit_neg_pin: gpio.39:high

The same

@Ryan any ideas?

This refers to the limit switch pin. If you leave the limit switch plugged into the original spot you need to keep that gpio at 34.

It doesn’t even move, let alone home.
By the way, X will home.
Z moves even though I don’t have a limit switch connected

Think about it, but I can’t mess with it until Monday.

Thanks
Mark

That is on the bottom of the board, There are pictures of that if you don’t want to flip it over.

Let’s focus on the basic moments first.

C is not configured in my file, it is just a placeholder with the right pins.

1- Lets take a step back, using my config file as shipped. Start up with everything plugged in and run $ss in the terminal. Please post the results here. (you can say none to polling to get it to stop scrolling).
This will tell us if it sees the driver or not.

2- when you are swapping the Y2 to prove it works you are also swapping the wire extension? (yes is what I want)

1 Like

:man_facepalming:. You probably spent a bit of time getting that nicely printed on the board. …
I’ll do the $ss and send it when I’m back home.
Thanks

The next batch has in now printed on the top as well. :wink:

1 Like

Here’s the output from $ss.
I don’t see anything unusual on the board, good quality soldering etc.

$ss

[MSG:INFO: FluidNC v3.7.8]

[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]

[MSG:INFO: Local filesystem type is littlefs]

[MSG:INFO: Configuration file:config.yaml]

[MSG:INFO: Machine MPCNC]

[MSG:INFO: Board Jackpot TMC2209]

[MSG:INFO: UART1 Tx:gpio.0 Rx:gpio.4 RTS:NO_PIN Baud:115200]

[MSG:INFO: I2SO BCK:gpio.22 WS:gpio.17 DATA:gpio.21]

[MSG:INFO: SPI SCK:gpio.18 MOSI:gpio.23 MISO:gpio.19]

[MSG:INFO: SD Card cs_pin:gpio.5 detect:NO_PIN freq:20000000]

[MSG:INFO: Stepping:I2S_static Pulse:4us Dsbl Delay:0us Dir Delay:1us Idle Delay:255ms]

[MSG:INFO: User Digital Output:0 on Pin:gpio.26]

[MSG:INFO: User Digital Output:1 on Pin:gpio.27]

[MSG:INFO: Axis count 3]

[MSG:INFO: Axis X (0.000,1220.000)]

[MSG:INFO: Motor0]

[MSG:INFO: tmc_2209 UART1 Addr:0 CS:NO_PIN Step:I2SO.2 Dir:I2SO.1 Disable:I2SO.0 R:0.110]

[MSG:INFO: X Neg Limit gpio.25]

[MSG:INFO: Motor1]

[MSG:INFO: tmc_2209 UART1 Addr:3 CS:I2SO.14 Step:I2SO.13 Dir:I2SO.12 Disable:I2SO.15 R:0.110]

[MSG:INFO: X2 Neg Limit gpio.35]

[MSG:INFO: Axis Y (0.000,2440.000)]

[MSG:INFO: Motor0]

[MSG:INFO: tmc_2209 UART1 Addr:1 CS:NO_PIN Step:I2SO.5 Dir:I2SO.4 Disable:I2SO.7 R:0.110]

[MSG:INFO: Y Neg Limit gpio.33]

[MSG:INFO: Motor1]

[MSG:INFO: tmc_2209 UART1 Addr:3 CS:I2SO.19 Step:I2SO.18 Dir:I2SO.17 Disable:I2SO.16 R:0.110]

[MSG:INFO: Y2 Neg Limit gpio.34]

[MSG:INFO: Axis Z (-100.000,200.000)]

[MSG:INFO: Motor0]

[MSG:INFO: tmc_2209 UART1 Addr:2 CS:NO_PIN Step:I2SO.10 Dir:I2SO.9 Disable:I2SO.8 R:0.110]

[MSG:INFO: Z Neg Limit gpio.32:low]

[MSG:INFO: X Axis driver test passed]

[MSG:INFO: X2 Axis driver test passed]

[MSG:INFO: Y Axis driver test passed]

[MSG:ERR: Y2 Axis TMC driver not detected - expected 0x21 got 0x0]

[MSG:INFO: Z Axis driver test passed]

[MSG:INFO: Kinematic system: Cartesian]

[MSG:INFO: Using spindle NoSpindle]

[MSG:INFO: Flood coolant gpio.2]

[MSG:INFO: Mist coolant gpio.16]

[MSG:INFO: Probe Pin: gpio.36:low]

[MSG:INFO: STA SSID is not set]

[MSG:INFO: AP SSID FluidNC IP 192.168.0.1 mask 255.255.255.0 channel 1]

[MSG:INFO: AP started]

[MSG:INFO: WiFi on]

[MSG:INFO: Captive Portal Started]

[MSG:INFO: HTTP started on port 80]

[MSG:INFO: Telnet started on port 23]

ok

That doesn’t seem right. Is the driver plugged into Y2? If so swap it with another driver and see if the problem moves

1 Like

I already tried that, thanks.
It’s not the tmc2209 chip, I tried 3 different ones.

1 Like