Hello all, new to the group and I am needing some help
I recently acquired a LowRider V2 from a local Enthusiast but the Controller was fried from error the previous owner did but everything else is in great shape. I am currently not in a position to upgrade to V3 just yet.
I am wondering is it possible to use or if anyone has used the Jackpot controller on the V2 LR?
if so any advise or where to start?
Thanks for any help!
Jackpot should work fine for your LR2.
First step- get a jackpot.
Next step- give us some pictures and details of your machine, there are plenty of us who can guide you along with making it live again.
Yeah it should works as is just be careful not to home the Z axis. The LR2 did not have that as the LR3 does. Besides that nearly plug and play I believe.
will do! ordering it today and will post pics soon! Thanks !
Noted! thanks again, just place my order
Hi, I will post photos soon. as of this moment I have the motors connected to the Jackpot, I went to the FluidNC site and tried to jog the X and Y axis, but the motors did not move… Am I missing a step with the FluidNC interface setup? Also the Motor connections do not have a locking tab for the ports on the JP. is there a way to make sure I have them in the right orientation ?
Do you have the power plugged in or just USB?
power plugged in, and using the web ui
In the terminal type $ss and paste what it say here.
Grbl 3.7 [FluidNC v3.7.12 (wifi) ‘$’ for help]
$ss
[MSG:INFO: FluidNC v3.7.12 GitHub - bdring/FluidNC: The next generation of motion control firmware]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:WARN: Cannot open configuration file:config.yaml]
[MSG:INFO: Using default configuration]
[MSG:INFO: Axes: using defaults]
[MSG:INFO: Machine Default (Test Drive)]
[MSG:INFO: Board None]
[MSG:INFO: Stepping:RMT Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:255ms]
[MSG:INFO: Axis count 3]
[MSG:INFO: Axis X (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Y (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Z (-1000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: STA SSID is not set]
[MSG:INFO: AP SSID FluidNCLRv2 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]
ok
This part seems to be an issue. Normally there should be a config.yaml file that the firmware can locate and use.
Looks like all the files got erased, have a look at this first section, easy fix, flash and copy over some files. Jackpot CNC Controller - V1 Engineering Documentation
kept getting this message. while holding down the boot switch, any advise?
Bootloader not active - Try holding down the BOOT switch
esptool.js
Serial port WebSerial VendorID 0x8086 ProductID 0x54a8
Update: this was fixed. had to update my drivers. thanks for the link to that!
below is the $ss in terminal after update. and files moved over
Grbl 3.7 [FluidNC 3.7.14-webui3-test (wifi) ‘$’ for help]
$ss
[MSG:INFO: FluidNC 3.7.14-webui3-test GitHub - bdring/FluidNC: The next generation of motion control firmware]]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]]
[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: 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 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: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: 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 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]]
ok
2nd attempt at $ss and it show the Axis drivers test passed. but moving the X axis is still not working from the webui
$ss
[MSG:INFO: FluidNC 3.7.14-webui3-test GitHub - bdring/FluidNC: The next generation of motion control firmware]]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]]
[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: 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 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: 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 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]]
ok
Power down completely, swap the X driver with any other drivers. What happens?
That is just the difference of having board power or only USB power.
IT’S ALIVE!!!
I tested each axis individually and they worked. I will text all axis together later today and share what happens.
Ryan Thank you so much!!
Just a note of something I realized today- you can send $MI at the FluidNC terminal at any time to have FluidNC attempt to initialize the stepper drivers. Better to just power the board up before conecting your USB, but in some situations it’s possible to recover from starting with only having USB power.
It also lets you re-apply the driver current if you edit the config.yaml, without needing to power cycle the board for this to take effect.
From the documentation here:
$Motors/Init
$MI
This is used to reinitialize motors. It is primarily for SPI and UART types. If you forget to have power on at startup or change a setting like run current. You can send $MI to reinitialize the motors.
That is a great find. I want to try that on a couple weird ESP32’s that did not pass testing. I really get the feeling the boot up on fluid is a bit too fast or something. That seems like it is worth a shot. I have a few that only show a couple of the drivers and if I reboot it show random one but never all, wonder if they are just a bit slow.
I use $MD all the time, how did I miss $MI