I am standing over my ESP32 from the V1 store. It’s worked fine most of the time but occasionally it will fail to load the web app as it normally does. I had it in STA mode and there have been no changes to my wifi network.
I can’t see the FluidNC wireless network SSID in my available networks. If I kill the power and restart, the situation persists. If I leave it powered off for an hour or so and try again, the situation persists. There is nothing over the ESP32 - no wires, nothing.
Should I try to reflash the ESP as per FluidNC Installation | Wiki.js ? Or are there some other steps I should try to fix?
The first thing I would try:
Disconnect the USB cable if one is present.
Power down the jackpot.
Power back up the jackpot.
Plug in a USB cable, connect to the jackpot with FluidTerm.
From the FluidTerm terminal, send a $SS command and paste the output here in the forum.
Use the preformatted text option, it looks like this in the forum editor toolbar: </>
1 Like
When I plug in the USB cable, the Jackpot powers on. I downloaded fluidnc and ran fluidterm.bat and am presented with the option to connect via COM3 or COM4. If I do COM3 it fails, saying “cannot open COM3, press any key to continue”. If I do COM4, it shows options to Exit, Clear Screen, etc. None of the commands respond when I do anything. If I just type in $SS and press enter, nothing happens.
Edit: must have been the cable, I tried with another one and saw the ESP on tty33. I ran $SS and got the output below:
MSG:INFO: FluidNC v3.9.1 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: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: 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:ERR: X Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:ERR: X2 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:INFO: Kinematic system: Cartesian]
[MSG:INFO: Connecting to STA SSID:Ivalice]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connecting...]
[MSG:INFO: Connecting....]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connecting...]
[MSG:INFO: Connecting....]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: WiFi off]
[MSG:INFO: Flood coolant gpio.2]
[MSG:INFO: Mist coolant gpio.16]
[MSG:INFO: Probe gpio.36:low]
I tried running $Wifi/Mode STA and hit Ctrl-R to restart. It cycled the Connecting… line a few times and then returned to WiFi Off. I ran $Sta/Password mypasswordhere and $Wifi/Mode STA>AP, then Ctrl-R again, same situation.
The password is definitely correct, I used it on my phone to reconnect to wifi successfully.
There’s an important detail. You have to leave the USB cable not plugged into your computer, power up the jackpot with its normal power supply, then and only then run FluidTerm and get that $SS output.
If you don’t power up first on the main jackpot power supply, the TMC drivers will not initialize and there isn’t enough power to be certain the ESP-32 will run correctly.
2 Likes
That definitely made a difference. I was also omitting the = from $WiFi. I got it communicating again, thanks to your help!
1 Like