LowRider 3 Jackpot Config

Ok, so I’m trying to test my initial setup.

Here’s my wiring setup:

I checked all of the endstops and the LED lights turn off when I trigger the switches in all the correct order.

The Odd thing is, in the FluidNC interface, here’s what the controls do:

X+ : Moves the X and Y2 motor
Y+: Moves the Y1 and Z2 motor
Z+: Moves the Z1 motor only

If it was only moving the wrong motors, I would assume wiring, but the fact that X has a single motor, but 2 are moving, and Z has 2 motors but only 1 is moving leads me to believe maybe it’s configuration??

Maybe @vicious1 has some insight?

I’m going to retrace and make sure everything is plugged in correct, but in the meantime, any ideas what else to check other than verifying motor wires?

I’m mostly confused as to why X is moving 2 motors and Z only one.

I have the config loaded directly from the V1 github in the LowRider3 folder

Sounds like you have a Primo config. X will run drives 0 and 3, Y will run drives 1 and 4, Z will ru drive 2 (numbering from 0 to 5)

I thought the same thing, that I must have made a mistake, but this is the file directly on the SD card:

and there’s only 1 motor defined for X:

With the disclaimer that the last 20 minutes is my entire experience with FluidNC (and all CNC in general lol)…

Is it possible that maybe it’s not loading my config.yaml properly and falling back to the default firmware settings as flashed?

Maybe there’s a way I can check that?

Ok, so config items say MPCNC instead of LowRider

It can see the SD card

I wonder why it isn’t loading the config.yaml

[MSG:INFO: FluidNC v3.7.6]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]
[MSG:DBG: Spiffs mount failed: ESP_FAIL]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:config.yaml]
[MSG:DBG: Running after-parse tasks]
[MSG:DBG: Checking configuration]
[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 6]
[MSG:INFO: Axis X (0.000,1220.000)]
[MSG:INFO: Motor0]
[MSG:DBG: TMCStepper Library Ver. 0x0x703]
[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:DBG: X Neg Limit 0]
[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:DBG: X2 Neg Limit 0]
[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:DBG: Y Neg Limit 0]
[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:DBG: Y2 Neg Limit 0]
[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:DBG: Z Neg Limit 1]
[MSG:INFO: Axis A (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis B (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis C (-150.000,150.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:3 CS:I2SO.22 Step:I2SO.21 Dir:I2SO.20 Disable:I2SO.23 R:0.110]
[MSG:INFO: C Neg Limit gpio.39:low]
[MSG:DBG: C Neg Limit 0]
[MSG:INFO: X Axis driver test passed]
[MSG:DBG: X Axis StealthChop]
[MSG:INFO: X2 Axis driver test passed]
[MSG:DBG: X2 Axis StealthChop]
[MSG:INFO: Y Axis driver test passed]
[MSG:DBG: Y Axis StealthChop]
[MSG:INFO: Y2 Axis driver test passed]
[MSG:DBG: Y2 Axis StealthChop]
[MSG:INFO: Z Axis driver test passed]
[MSG:DBG: Z Axis StealthChop]
[MSG:ERR: C Axis TMC driver not detected - expected 0x0x21 got 0x0x0]
[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 mask channel 1]
[MSG:INFO: AP started]
[MSG:INFO: WiFi on]
[MSG:INFO: Captive Portal Started]
[MSG:INFO: HTTP started on port 80]
[MSG:DBG: config.yaml hash “4F247EAB6308564A28CBA2A2D7780C0FBB7DFBD36EB0F3FF8AEF69652B336181”]
[MSG:DBG: favicon.ico hash “E64C199444593D5D7B529AD9BDC622D2A39A09EAC643131EF96EE32BBC7C5B78”]
[MSG:DBG: index.html.gz hash “7A9C15E55C5CC41861C898408921F1A0ABCA5FE91381867F024BA92E00DC9E40”]
[MSG:DBG: macro1.g hash “ECB8C22C9ACDF856A96A4CAF35331C72DDA92875DF5A5377F592C0C051FA8F02”]
[MSG:DBG: macro2.g hash “2B3D0792530D69584DD83D1D4D0682A801F9B045EC7D8B0A056882C703746766”]
[MSG:DBG: macro3.g hash “567A6B4BDAC2021C872A3D95025630D0E5B9A1468B2E649E850BC34B551014BF”]
[MSG:DBG: macro4.g hash “ECA59FED8BD8397495E88729309E7CC58F2528D00F8CD9E23BDF7A1656FBFA70”]
[MSG:DBG: macro5.g hash “E7D13631B82AB3C1894D4CFFD1D3C62DC7EB5AB1687DF7A7D8D242416A0B1B20”]
[MSG:DBG: macro6.g hash “863036858474AFCCA7E221AB41AC005C16CB30BE61F91388087AA26E0BC148D9”]
[MSG:DBG: macrocfg.json hash “F9DF1B43C8984FA8B47A4168ED3C962B886C18C8602DD3D9BF5C22685449DDB7”]
[MSG:DBG: preferences.json hash “57E0664345E08D0D8362797C20ADA0D0AFE984C71BB0A769748D2B67346EB5AA”]
[MSG:INFO: Telnet started on port 23]

Startup messages show MPCNC. I reformatted the SD card and made sure nothing was on it except the contents of the LowRider folder from GitHub. No change.

It does see and show the Macro config, but I can’t tell if that’s just because that’s what was flashed rather than because the macro files are on the card.

The config is stored in the microprocessor Flash according to FluidNC Wiki

Right, but my understanding is that it should load the config.yaml and override the settings that are flashed

It’s been a bit since I was messing with my config but it needs to know where the new config is located here $Config/Filename=yourfilename.

Delete your current config.yaml file. Upload the lowrider config.yaml file power down, wait a minute and power up. That should load the right config.

I should not have gotten that wrong. Very sorry.

1 Like

Just use the built in file browser, you can do it all from your computer and the web gui.

1 Like

Delete from the SD card? The SD card already has the LowRider one on it.

Or do you mean something else?

It only uses the one on the device. So if you have one on the SD it doesn’t matter.

1 Like

Oh….maybe I misread the docs. I thought it just said to put it on the SD card.

If so, sorry about that. I’ll go back and re-read

1 Like

Ok. Thanks Ryan. Much better now.




And now it’s dead lol

So, I went to the config and changed a config setting. The Y-Axis was configured to Home in the negative direction instead of positive.

I change that value and clicked Set.

Now this is the screen I get:

So now I don’t know what to do to get it back.

I guess I should have changed the yaml and re-uploaded it, but I didn’t expect changing a setting to wipe the filesystem

Edit: I rebooted it again and it came back now…. 3rd times the charm I guess

Giving me gray hairs here…