JackPot3 Y0/Z0 slow

LowRider CNC Troubleshooting
1

Hey there,

I built out a 4x8 Lowrider4 that has been working splendidly - mounted on a temp table and then built a bench inspired by Ryan’s designs (used it as an excuse to practice Fusion)

I have been tinkering more with it and built out a CYD pendant and had that working well. Jogging/homing/etc from the pendant was working as intended.

Then I picked up a Sienci AutoSpin T1, and followed some of the threads on this forum to get my config setup correctly and the T1 was firing up on M3 commands as expected.

Then the problem manifested. My Z0 and Y0 channels crawl, it seems to be the board headers/channels. If I switch around Z1/Z0 the problem follows whatever motor is plugged into the Z0 channel. Same with Y.

I’ve reverted my config back to a working state (prior to PWM changes) and still have the same issue. I had the T1 plugged into the 5v gpio.2 slot

Currently the board is unplugged and removed so I could inspect components much closer in a space better lit than the garage. But can provide photos if needed. Best I can tell it doesn’t look like anything is burned/popped. At least not that my naked eyes can discern.

I’m a software dev by day, but microelectronics are certainly new. So I’m out of my element

2

To add:

I picked up the components kit from the V1 shop, so the power supply/cables and all other components were picked/supplied by that kit

3

Let’s start very much within your element.

When the machine is misbehaving, send a $SS command in the terminal. Copy/Paste the terminal output back here in the forum. Use the preformatted text formatting option. It looks like this on the forum editor toolbar: </>

Also: welcome to the V1 community forums, and congratulations on your LR build

4

Hey MakerJim,

Thank you for taking the time to respond! I think I figured it out… maybe, I have a theory - but it’s all still new so it might not be a good one. Good news first, things are working again so I don’t think the board is burned up or damaged.

I decided to just nuke the config all together and found what I think was a default one the the meta key has 11-01-25 RyanZ so I went with it. All I copied over were my steps_per_mm from the old one. And as I get it all set back up I’ll re input my bed size again.

My theory is that I goobered it up when I was trying to configure the CYD Pendant. I messed with the UART and probably didn’t fully understand that other components used the same lanes. I changed baud to 1000000 to match what the pendant had on its Info screen for its baud - I also changed some TX and RX pin numbers. I “suspect” that was related. It is strange though that after setting it all up I was able to jog all around my table with the rotary encoder without any issues…

So I suppose its back to the drawing board (learning board) to figure out how to change my config for my Pendant to connect again. I was following the wiki on FluidNC for the CYD Pendant, so I’ll revisit that and see if I can connect the dots and learn it. Here’s what I did to my uart settings that I suspect messed things up…

uart1: 
  txd_pin: gpio.15
  rxd_pin: gpio.12
  rts_pin: NO_PIN
  cts_pin: NO_PIN
  baud: 1000000
  mode: 8N1
  passthrough_baud: 0
  passthrough_mode: 8E1

uart_channel1:
  uart_num: 1
  report_interval_ms: 75

Before that though, I want to get my T1 working off the GPIO.2 again, I think that should be pretty straightforward… I think - previously I had: (uncommented when it was working of course)

# pwm:
#   pwm_hz: 5000
#   output_pin: gpio.2
#   enable_pin: NO_PIN
#   direction_pin: NO_PIN

#   disable_with_s0: false
#   s0_with_disable: true

#   spinup_ms: 500
#   spindown_ms: 500

#   tool_num: 0

#   speed_map: 0=0.000% 6000=25.000% 12000=50.000% 18000=75.000% 24000=100.000%

#   off_on_alarm: false

It does give me an excuse to cleanup my enclosure, I have a dupont crimp tool and all the connectors to take all the slack out of these wire runs and free up a lot of space for some needed airflow in the box. And since it’s all blown apart now for troubleshooting it’s probably as good a time as any.

Here’s that $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.16 Rx:gpio.4 RTS:NO_PIN Baud:115200]
[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: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: 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]
[MSG:INFO: Probe gpio.36:low]
5

And to add - again:

I just now realized at the bottom of this config file I have, there are commented out sections for uart2 and pwm … so I am “hoping” I am in a much better starting point to figure those out. My original config didn’t have those, so I was kinda winging it off with forums and a touch of AI to help search through/parse FluidNC docs

6

You’re on a better path now. AI confidently destroys working configs all the time.

7

Oh yes, as a career software dev I am all too familiar with how confidently wrong it is quite often. I have learned to get better results out of it as companies push for more AI assisted work. So now I treat it largely like the tool that it is - it’s great at parsing through large amounts of data for me, but to blindly trust it can definitely get you in hot water. I’m learning that with embedded stuff even more so. For web its not too bad these days.

Thank you again for your help! Once I get this all cleaned up I’ll post some pictures on the completed builds - it’s been a real fun project and has exposed me to all sorts of things that have really grabbed my attention and encouraged me to build things I wouldn’t have ever attempted before

1 Like
8

Please do. We love to see community members’ builds here in the forums.

Even better if you post your projects and makes as you go.