New Homing Issue

Software / Firmware Jackpot Board / FluidNC
1

Yesterday I updated my Jackpot to 3.7.18 and have ran several jobs since then. It has been running great with no issues at all until this evening. I went to home and it will raise Z up until it touches the endstops on both sides and just stops. Never comes down and hits it a second time. Have tried several restarts. Occasionally it will complete the Z home and then move X over until it hits the endstop and stop there. Only twice has it made it that far. Has not made it past that since this issue popped up. I tried doing a complete reflash on the ESP32 and that did nothing for the issue. I tried removing my RS485 board and that made no changes. I have tested and according to the lights on the jackpot all of the endstops are good. Nothing else has changed on the LR3 or in the shop to have any effect on anything.

Here’s what $SS shows after startup…

$SS
[MSG:INFO: FluidNC v3.7.18 https://github.com/bdring/FluidNC]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:config.yaml]
[MSG:INFO: Machine LowRider]
[MSG:INFO: Board Jackpot TMC2209]
[MSG:INFO: UART1 Tx:gpio.0 Rx:gpio.4 RTS:NO_PIN Baud:115200]
[MSG:INFO: UART2 Tx:gpio.14 Rx:gpio.15 RTS:gpio.13 Baud:9600]
[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:2 on Pin:gpio.2]
[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: 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.14 Step:I2SO.13 Dir:I2SO.12 Disable:I2SO.15 R:0.110]
[MSG:INFO:  Y2 Neg Limit gpio.35]
[MSG:INFO: Axis Z (-300.000,0.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 Pos Limit gpio.32]
[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:  Z2 Pos Limit gpio.34]
[MSG:INFO: X Axis driver test passed]
[MSG:INFO: Y Axis driver test passed]
[MSG:INFO: Y2 Axis driver test passed]
[MSG:INFO: Z Axis driver test passed]
[MSG:INFO: Z2 Axis driver test passed]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: Huanyang Spindle  Tx:gpio.14 Rx:gpio.15 RTS:gpio.13 Baud:9600]
[MSG:INFO: Using spindle Huanyang]
[MSG:INFO: Mist coolant gpio.16]
[MSG:INFO: Probe gpio.36:low]
[MSG:INFO: Connecting to STA SSID:Jones]
[MSG:INFO: Connecting.]
[MSG:INFO: Huanyang PD0011, PD005 Freq range (200,400) Hz (12000,24000) RPM]
<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:P>

And I get this on the screen after trying to home and it stops…

$H
<Home|MPos:0.000,0.000,4.425|FS:800,0|Pn:Z>
<Home|MPos:0.000,0.000,2.635|FS:300,0|Pn:P>
<Home|MPos:0.000,0.000,0.730|FS:300,0|Pn:P>
<Home|MPos:0.000,0.000,4.270|FS:0,0|Pn:PZ>
<Home|MPos:0.000,0.000,0.395|FS:0,0|Pn:P|WCO:0.000,0.000,0.000>
<Home|MPos:0.000,0.000,-0.130|FS:0,0|Pn:P|Ov:100,100,100>
[MSG:Homed:Z]
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX|WCO:0.000,0.000,0.000>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX|Ov:100,100,100>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX|WCO:0.000,0.000,0.000>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX|Ov:100,100,100>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>
<Home|MPos:-1.220,0.000,0.000|FS:300,0|Pn:PX>

The HomeIMPos: message just keeps going and going until I power down and restart.

2

is it repeatable after a cold power cycle?

1 Like
3

Is it actually tripping the switches?

1 Like
4

Yes. Hasn’t homed right yet since this started. Only way to even be able to try again is to power cycle.

Yes it is. It hits the switch and just stops. Instead of backing off and hitting them again.

5

It seems to have some parallels to the issues I was having that 3.7.18 resolved. Can you zip and post your config.yaml? I can compare it with mine if you would like.
Edit, to elaborate. My issue seemed to start in a similar way as this. And it got worse. I messed around with the config until I plugged the esp32 in backwards and blew the regulator. I think the esp32 was failing though. Have you got a spare one you can setup and just switch between the two?

1 Like
6

Yes sir I sure can. Its just so weird. I updated it 2 days ago and ran at least 8 jobs that ran flawless. Now this. Absolutely nothing has changed…

config.zip (1.5 KB)

7

I just edited my post above to add…

I’ll get my config and post it in a few mins.

1 Like
8

Ahh yes I missed this. I do have a spare. Its actually a V1 ESP32 that I have been meaning to swap out anyways. Just procrastinated due to needing to add the resistor lol. Ill get that done real quick and swap it in and see what happens.

9

I didn’t add the resistor to the two replacements I’m using now and they both boot/work fine.
config rob 3718.zip (1.4 KB)

10

Which version of the Jackpot do you have? the newer ones have the resistor built into the board. All of mine predate this addition

11 

axes:
  shared_stepper_disable_pin: NO_PIN
  shared_stepper_reset_pin: NO_PIN
  homing_runs: 2

That homing_runs bit is in mine but not yours I think.

1 Like
12

I will add that in and see if it makes a difference. I know I had to add the homing_amps to mine so it would home Z. My beam is too heavy lol

13

Mine is one of the first I bought it really early.
Screenshot 2024-06-24 13.03.00
RC2 - I guess that is pretty early?

1 Like
14

Yeah me too but I didn’t add it. I just used the old config, made a change using the UI and saved - that seems to add in all the new stuff that is needed. Then I also changed homing_amps for my chunky gantry.

1 Like
15

Well I’m being lazy this morning and skipping the resistor lol. Hopefully I don’t regret it later. Either way it will be easy to add. Loading up Fluid and all on the new ESP and will give it a shot.

1 Like
16

I had to add the resistor to get the V1 ESP32 to work on my Jackpot.

1 Like
17

The new ESP32 got me back running but I will need to add the resistor for sure. I have to power up and then hit the reset button on the ESP32 to get it to start up now. But it will get me going to finish this current project hopefully!

Thank you everyone for the help!!!

2 Likes
18

Okay, I need to take a look at the configs more today. Mine did run fine, but these two new edits are needed.

19

Mine was running fine without that until last night. But I do think the esp32 was the main culprit. I was having some other odd issues with the spindle not turning off right at the end and it would randomly change speeds in the middle of a cut. Now it’s back to running perfectly with the New ESP32

20

What esp was on there before? Micro USB, or USB-C, from me?