HI all, Just recieved the Jackpot board from Elecrow and installed the FluidNC firmware with the MPCNC config.yaml. THis was to replace a Ramps1.4 Marlin laser setup which was giving me pain so I took the leap.
IM running this machine wired via USB cable and Lightburn.
Im testing steppers/wiring, thus rewiring the whole machine one stepper at a time. Ive just got to X1 (A) driver (channel) and its running slow compared to the X0 side. Ive checked the wiring and swapped out the driver board but it doesn’t make a difference.
My belief with these TCM2209 boards is that the UART is enabled via firmware and after I had to solder the jumper on the bottom of the driver board ?
I shouldn’t need to bother with the vref at all as I can adjust it in the config unless its unusually high or low which its not?
Lastly and weirdly steppers seem to be moving at the same rate in CNCjs and the issue arises in Lightburn.
Jackpot/FluidNC do use the TMC2209 UARTS. For the recommended drivers, no change is necessary. If you bought drivers that have a different default configuration than having the UART enabled (and on the correct pin), then you will need to do whatever that driver needs to set the configuration.
FluidNC configures the TMC2209s including the drive current over the UART interface. If the driver is properly configured you will never need to touch the potentiometers.
Sorry about the formating Jim, flying by the seat of my pants as the machine is in bits in the workshop at the end of the garden 20 meters away and its chucking it down.
I think this is the total output…
[MSG:INFO: FluidNC v3.9.1 GitHub - bdring/FluidNC: The next generation of motion control firmware]
[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 MPCNC]
[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:2us Dsbl Delay:0us Dir Delay:1us Idle Delay:255ms]
[MSG:INFO: User Digital Output: 0 on Pin:gpio.26]
[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: X Neg Limit gpio.25]
[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: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: Y Neg Limit gpio.33]
[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: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:INFO: X Axis driver test passed]
[MSG:INFO: X2 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: Kinematic system: Cartesian]
[MSG:INFO: Connecting to STA SSID:VM4103303]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting…]
[MSG:INFO: Connecting…]
[MSG:INFO: Connected - IP is 192.168.0.48]
[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: Laser Ena:NO_PIN Out:gpio.27 Freq:5000Hz Period:8191]
[MSG:INFO: Flood coolant gpio.2]
[MSG:INFO: Mist coolant gpio.16]
[MSG:INFO: Probe gpio.36:low]
and all that about the drivers Im clear with now thanks for confirming that.
Its so visibly different in Lightburn you can tell; thats how bad it is. But not as obvious, if at all in CNCjs. Its not the stepper either as I tried the other axis steppers.
You need to eliminate the senders, do the testing from the FluidNC web UI or the FluidNC terminal.
Command a move, document how fare the stepper motor rotates. Much easier if the motors are out and flagged as I mentioned earlier. If the motors don’t move the same amount with a commanded X move direct from FluidNC, then we go from there.
OK Jim, after some serious striping down to bear connectors, Im still none the wiser as to what was wrong. I can only surmise that perhaps on the X1 connector to the stepper that perhaps the negative connector (black wire) was hanging on by a bit of soldered wire jacket rather than actual wire but then it wouldnt have moved at all.
Other than that after trying out a set of different steppers for testing and moving to your testing methodology of tape on the axle and back to “move direct from FluidNC” I didnt do anything new. Also the tape on axle thing clearly shows the steppers are turning the same.
Ive yet to see if its something mechanical but I doubt it however you never know it took me a week to figure out the belt gear was slipping on my LR3 a few weeks ago.
Anyway Ill take it as a lesson in testing methodology ftom you Jim, thanks.