Jackpot cnc clearing alarm/panic

Software / Firmware Jackpot Board / FluidNC
1

Hi all, I am really stumped on this one. My jackpot was working fine the other day and when I fired it up last night nothing would happend. My MPCNC wouldn’t move. After logging into the WebUI, upon loading the page I was presented with the following: MSG:ERR: Showing startup log from previous panic]. I’ve tried clearing the alarm and resetting the firmware but nothing changed. I even went as far as reflashing the ESP and running the controller off the jackpot board but I keep getting the same result. Any help is very much appreciated. Thanks.

2

Welcome Mike,

In the Terminal on the WebUi type in $SS. Paste the results here so we can figure out what’s causing the error.

2 Likes
3

Thank you for your help. Here is what I get after running the command:

[MSG:ERR: Showing startup log from previous panic]
[MSG:INFO: FluidNC v3.9.8 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_Laser.yaml]
[MSG:INFO: Machine MPCNC Laser]
[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.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: 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:low]
[MSG:INFO:  Pos Limit gpio.35:low]
[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: 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:low]
[MSG:INFO:  Pos Limit gpio.34:low]
[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: 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:  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: 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]
[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]
ok
<Alarm|MPos:0.000,0.000,0.000|FS:0,0|WCO:0.000,0.000,0.000>
4

Can you check your config? You have a Neg Limit and Pos Limit setting for X and Y. This is what I have in my config for the MPCNC:

    #X
    motor0:
      limit_neg_pin: gpio.25:high
      limit_pos_pin: NO_PIN
    #A
    motor1:
      limit_neg_pin: gpio.35:high
      limit_pos_pin: NO_PIN

    #Y
    motor0:
      limit_neg_pin: gpio.33:high
      limit_pos_pin: NO_PIN
    #B
    motor1:
      limit_neg_pin: gpio.34:high
      limit_pos_pin: NO_PIN
5

Thanks again. I have a limit switch near the origin(limit_neg_pin) and one at the furthest extent (limit_pos_pin) so that is why I have both pos and neg assigned to pins. This is the case for both the x and y axis. I’m really scratching my head on this because it was working fine as I have made several projects using my mill and the laser and then out of nowhere this error came up. I’m worried that something is wrong with the ESP32 board.

1 Like
6

Have you solved this yet? I’m having a similar error on our LowRider4.

7

Greetigs, tc601 and welcome to the V1 community forums.

Please feel free to create a new forum topic for your issue as machines and configurations vary.

The topics are free and we can help focus on your specific case.

1 Like