LR4 JP3 config.yaml file not reliable, Z0 & Y0 motor slow

Hi!

(config.nc file attached).

This LR4 is driving me crazy but I am soldering through.

what happens is when I upload my latest modified (modded only for belt, square, level, and HY RS485 Modbus&UART1), then the machine will jog and home normally.

What is driving me crazy is how when I turn the machine off then on for the 3rd 4th or 5th time, both the Z0 and Y0 motors will only move about 1/16 distance compared to its counterpart motor.

If I upload the original config.yaml file with no corrections for belt, square, level, or HY RS485, it works just fine every time for ever and ever no matter how many times I delete it from flash and re-upload.

But if I modify by adding corrections for belt, square, level, and HY RS485, then the z0 and y0 motors will slow to 1/16 speed. but only after upload, then delete, then upload again maybe like 2+ times.

Not sure what is going on. Please help whenever you have some time.

I would upload a video by what happens is easily visualized: The z0 and y0 moves at about 1/16 speed of their counterparts.

On Notepad++ my UART1 and VFD blocks look like this:

BOOT Log here:

config.nc (7.3 KB)

Share the original and modified config file. Also, which version of the Jackpot controller do you have? What version of FluidNC do you have installed.

When getting the SD card error, do you have USB connected to the controller? Or is it powered by 24v?

Also, include the full $SS output.

Hi Jason,

*Note from edit: Now the file seems to get even more corrupted every time I delete from flash and re-upload. Now even the OG file (un-edited) is having issues where when I press “Restart Board” button on WebUIV3, it just says “restarting” forever. Then I can’t connect or even delete config from flash or even re-upload a new config. At that point I have to go to fluidncinstaller website via USB-C and delete then re-upload. Confusing.

Here is the $SS output:

$SS
[MSG:INFO: FluidNC v3.9.9 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 Jackpot3 TMC2226]
[MSG:INFO: UART1 Tx:gpio.14 Rx:gpio.15 RTS:gpio.13 Baud:9600]
[MSG:INFO: I2SO BCK:gpio.22 WS:gpio.17 DATA:gpio.21Min Pulse:2us]
[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:2us 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: User Digital Output: 2 on Pin:gpio.0]
[MSG:INFO: User Digital Output: 3 on Pin:gpio.2]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (3.000,1223.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:  Neg Limit gpio.25]
[MSG:INFO: Axis Y (3.000,2443.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:  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:  Neg Limit gpio.35]
[MSG:INFO: Axis Z (-147.000,3.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:  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:  Pos Limit gpio.34]
[MSG:ERR: X Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:ERR: Y Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:ERR: Y2 Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:ERR: Z Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:ERR: Z2 Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: Connecting to STA SSID:BINKY1135_2.4GHz]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connected - IP is 192.168.0.98]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://fluidnc.local/]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
[MSG:INFO: Huanyang Spindle Tx:gpio.14 Rx:gpio.15 RTS:gpio.13 Baud:9600]
[MSG:INFO: Probe gpio.36:low]
ok
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
<Idle|MPos:0.000,0.000,0.000|FS:0,0>
<Idle|MPos:0.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000>

I’m assuming that $SS output is from when you had it connected via the web installer since it shows the TMC drivers as not detected?

Is it disconnected from USB when you’re having these issues? And restarted after disconnecting USB? It won’t initialize properly if it is powered from USB first.

If that’s not it, I would try doing a fresh install from the web installer wiping everything. It’s possible there’s some issue with the flash which that will resolve.

1 Like

USB being connected with a power+data cable before the Jackpot is powered is a likely source of issues. Another would be a current loop with the spindle interface.

If this isn’t a USB related issue, disconnect the RS-485 module and repeat the assesement of boot reliability.