Jackpot3 stepper confusion

Software / Firmware Jackpot Board / FluidNC
1

So, I’m very confused. I’m switching from SKR 1.2 on my MPCNC to a Jackpot3 and the stepper motor connections seem completely out of whack. I carefully labeled the all of them before removing them and have checked each one again, tracing them back to the steppers. Somehow, the X, Y and Z connections are all mixed up. I know it’s more than a mistake on my end because when I send a command to the board to move my single Z stepper motor, it’s activating both my Z stepper one of my Y steppers. How can that be? Only one driver lane should be transmitting to Z because there is only one stepper for Z. Why are two of them sending out that signal. Something seems very wrong with this new board or the firmware on it. Can anyone help? Am I in fact missing something? I don’t even know how I can connect my four X and Y steppers if Z is using two of the driver lanes.

Thanks,

Nick

2

You need to download and install the MPCNC config files from here:

It has the LR4 configs on it now.

3

Wow, that was fast. Thank you! I’ll give that a shot tomorrow.

4

Dang Britt you are fast, good catch!

5

@vicious1

This has tripped up several people. You might want to add a note in the store that the Jackpot comes with the LR4 config installed and if they are using it for the MPCNC or any other CNC they will have to change the config for that machine.

6

Thanks, added a note to the shop page.

7

So, I figured out how to download the config.yaml file, but I’m not sure how to get it to the correct place on the board. I found instruction on the form for how to update the file ( Jackpot 3 board configuration for MPCNC ), but when I go through that process, it tells me the upload failed and to try a lower baud rate. At the lowest baud rate, it continues to fail. What am I doing wrong?

Thank you for your help, BTW.

8

Can you connect to the JP3 over wifi? If so, you can upload the config file to the flash on the JP3 by dragging and dropping.

9

Actually, just figured it out. Everything seems to be working now, except for homing on Z. It’s giving me an error message. Haven’t spent any time trying to diagnose that yet. Currently making dinner. :slight_smile:

Thank you for spending the time to help me out by the way. Super awesome of you!

10

Do you have an endstop set up for homing the z axis. I don’t have one on mine. Just on the X and Y axes.

11

No, I have the touch-plate and it’s connected to the last set of pins on the inputs section of the board. Pins 36 I believe. The message I’m getting is “Homing fail. Pull off travel failed to clear limit switch”. X and Y home perfectly and Z moves up and down perfectly, but if I try to home Z it just moves down a smidge and then reports the error. I’ve flipped the plug for the touch-plate and have removed it completely, but it reports the error regardless.

Thanks for any help you can give. Haven’t found a solution yet.

12

With the touchplace not touching anything, what does it say when you type in $limits in the terminal?

That is a live display of all your inputs. Check each one.

13

You want to use the Probe pane on the webui, not Home Z.

14

So, no idea what I’m looking at here. Here is what’s coming out, but it just keeps going:

$limits

Send ! to exit

Homing Axes : xyz         

Limit Axes :             

  PosLimitPins NegLimitPins Probe Toolsetter

:   z                      

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z|Ov:100,100,100>

:   z                      

:   z                      

:   z                      

:   z                      

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z>

:   z                      

:   z                      

:   z                      

:   z                      

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z>

:   z                      

:   z                      

:   z                      

:   z                      

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z>

:   z                      

:   z                      

:   z                      

:   z                      

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z>

:   z                      

:   z                      

:   z                      

:   z                      

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z>

:   z                      

:   z                      

:   z                      

:   z                      

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z>

:   z                      

:   z                      

:   z                      

:   z                      

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z>

:   z                      

:   z                      

:   z                      

:   z                      

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z>

:   z                      

:   z                      

:   z                      

:   z                      

<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:Z|WCO:3.000,3.000,-80.000
15

While that is scrolling, you can test each endstop and the probe and it will show up there.

Currently one of your Z endstops is triggered.

16

So, I’m using an MPCNC, so I don’t have a Z endstop, just the touchplate, which was not touching while this was running. Sounds like you’re saying the board is reporting that the touch-plate loop is closed when it’s not? What would cause that? Someone else on here said I shouldn’t be using Z homing, and should instead use something else to home the Z access. Am I just homing Z incorrectly?

Thank you for your help.

17

Thanks for all your help, but I think I’m just going to do the Z homing by eye manually like I used to with my SKR board. The touch plate doesn’t seem to be worth the trouble. I thought it would be nice, after seeing how nicely the X and Y homing works now, but setting the Z height is super easy to set anyway. Thank both of you for all your help.

Best,

Nick

18

The config has a couple of errors for the MPCNC. This is what it should have for the Z axis:

 z:
    steps_per_mm: 200.000
    max_rate_mm_per_min: 1200.000
    acceleration_mm_per_sec2: 80.000
    max_travel_mm: 300.000
    soft_limits: false
    homing:
      cycle: 0
      positive_direction: true
      mpos_mm: 200
      feed_mm_per_min: 300.000
      seek_mm_per_min: 800.000
      settle_ms: 500
      seek_scaler: 1.100
      feed_scaler: 1.100

    motor0:
      limit_neg_pin: NO_PIN
      limit_pos_pin: NO_PIN
      limit_all_pin: NO_PIN
      hard_limits: false
      pulloff_mm: 4.000
      tmc_2209:
        uart_num: 1
        addr: 2
        cs_pin: NO_PIN
        r_sense_ohms: 0.110
        run_amps: 0.800
        homing_amps: 0.800
        hold_amps: 0.700
        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.10
        direction_pin: I2SO.9
        disable_pin: I2SO.8

This is what’s in the config on github:

    homing:
      cycle: 1

      limit_pos_pin: gpio.32:high

I submitted a change on github. It’s the first time of done that so hopefully I did it correctly.

19

I added the change, but we never used to hit “home all”. With fluidnc it is okay to do that with the changes, but it is not a typical thing to do on an MPCNC.

20

Thank you. I’ll enter that new info in when I get home and see how it goes. Touch-plate went bye-bye yesterday while trying to do a test job, so I need to put new wires on it first. :slight_smile: Got me a little gun shy with putting the clip on the bit to be honest.