Jackpot Connection Issue

MakerJim · September 19, 2024, 9:49pm

Correct.

rtbal · September 24, 2024, 11:05pm

Sorry for the late reply’s. Just started a new full time job and already getting sucked in, you know how that goes.

So since last time, Ive had a few instances show up where I will power off (turn switch in series with 24V power supply and the board) after running a program. Turn back on because after my program ends I am unable to do any commands so I power cycle. I got this error last night below. I also ran into another issue last night cutting a larger 1.5MB gcode file. It paused mid run and did not resume. I am thinking all of these problems are some sort of connection issue from my laptop to the board itself.

Is there a way to directly connect to the board not over WiFi without buying the SKR Pro to be able to run the gcode file and not transmit all the data needed over Wifi? Any other suggestions would be great, I am sure this problems keep arising for some reason due to some connection issue.


$G
$SS
[MSG:ERR: Showing startup log from previous panic]
[MSG:INFO: FluidNC v3.8.0 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 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: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:   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 (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.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: Using spindle NoSpindle]
[MSG:INFO: Flood coolant gpio.2]
[MSG:INFO: Mist coolant gpio.16]
[MSG:INFO: Probe 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
<Alarm|MPos:0.000,0.000,0.000|FS:0,0|WCO:39.188,29.188,10.000>

vicious1 · September 25, 2024, 2:52pm

When you connect over wifi you should not be sending any information. Your gcode file should be on your memory card on the Jackpot. Your wifi connection is just to hit “go” and you no longer need to be connected at all.

rtbal · October 21, 2024, 11:55pm

Don’t mind me revisting this issue. Tried cutting tonight and started the program and about 1 minute into each cut, the CNC paused and would not resume. Sometimes it resumes and most times it just stops. Needed to restart the board every time. Not quite sure what is happening. Note that the error at the end was after I tried re-connecting to the board after restarting it and tried running X0 Y0 Z0.

$G
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
ok
$SS
<Alarm|MPos:0.000,0.000,0.000|FS:0,0|WCO:39.188,29.188,10.000>
[MSG:ERR: Showing startup log from previous panic]
[MSG:INFO: FluidNC v3.8.0 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: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: 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 (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.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: Using spindle NoSpindle]
[MSG:INFO: Flood coolant gpio.2]
[MSG:INFO: Mist coolant gpio.16]
[MSG:INFO: Probe 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
<Alarm|MPos:0.000,0.000,0.000|FS:0,0|Ov:100,100,100|A:>
X0 Y0 Z0
ERROR:9
G-code commands are locked out during alarm or jog state.
[MSG:ERR: GCode cannot be executed in lock or alarm state]

jeyeager · October 22, 2024, 12:06am

You should roll back FluidNC to 3.7.17. There are known issues like this with versions 3.7.18 through 3.8.3. This will be resolved in 3.8.4 which is close to release.

rtbal · October 23, 2024, 12:03am

I will try this. Thanks for the help. Cutting with no issues tonight (knock on wood)

rtbal · December 8, 2024, 5:44pm

Its been working great until today. I have a 32GB SD Card on the board and I am getting low memory issues. I was getting the same errors from my 16GB to the 32GB card.

[MSG:WARN:: Low memory: 14720 bytes]
[MSG:WARN:: Low memory: 14644 bytes]
[MSG:WARN:: Low memory: 9876 bytes]
[MSG:WARN:: Low memory: 6676 bytes]
[MSG:WARN:: Low memory: 4704 bytes]

jeyeager · December 8, 2024, 5:50pm

The memory it is referring to is not related to the SD card.

Did you ever roll back to FluidNC 3.7.17? I would use either that version or 3.9.1.

Also, with the WebUI, do you have that open in more than one place? For example, if you load that on your computer and on a phone at the same time, that can cause low memory issues.

rtbal · December 8, 2024, 5:55pm

I am on version 3.7.17. I only have it open on one browser tab on one device. It gave me low memory issues only a few times. I also have trouble uploading g-code directly to the SD card over the WebUI

jeyeager · December 8, 2024, 5:58pm

Are you using AP mode (connected to the FluidNC wifi network) or STA mode (connected to your home wifi)?

rtbal · December 8, 2024, 6:00pm

AP mode. I have noticed this low memory issue slightly more when I am running my laser. I am not using a USB to connect directly to lightroom, I export g-code and upload it to the controller

jeyeager · December 8, 2024, 6:09pm

Well, I’m not quite sure.

It differs from the current V1 recommendation, but the FluidNC team strongly recommends STA mode, to the point where they only support AP mode for setting up configuration. I use STA mode.

As far as the laser side goes, I’m not sure if memory comes into play, but there are significant updates in the 3.9.1 release that may help.

I’m still not sure that changing any of that would resolve the low memory warnings. I haven’t seen low memory warnings in a long time, and even then, not on that version.

vicious1 · December 9, 2024, 5:04pm

Laser gcode can be extremely dense. If you are trying to run raster images I highly suggest being very careful with dot density. If the steppers are stuttering at all you are either moving too fast or have to high of a dot density.

There is a section of using laser with these CNC’s and there are a commands per second limit. For the highest speeds possible, I recommend wired and wifi mode to off. For vector images, you should be fine either way.

A lot of people do not realize the huge change dot size can have on gcode density commands per second.