Do you have the USB plugged in?
Should take about 30 seconds to connect.
yes …
Pull the ESP32 off the board and flash it naked.
i will try that and then how about i put a new esp32 board on the jackpot. I have 2 brand new ones.\
Some are finicky, but it should work naked for sure. If it does not then it is a bad ESP.
no joy. going to flash one of the new esp32. be a few minutes
Make sure that is not a charge only USB cable.
just put new usb cable on. same thing. known good cable.
Did you try another esp32?
You are trying the esp not plugged into anything but the usb cable right, not plugged into the jackpot?
It has to work, it was flashing before.
ets Jul 29 2019 12:21:46
rst:0x1 (POWERON_RESET),boot:0x3 (DOWNLOAD_BOOT(UART0/UART1/SDIO_REI_REO_V2))
waiting for download
*** Connecting to jserialcomm://COM7:115200
?
**** Connection closed ****
*** Connecting to jserialcomm://COM7:115200
[MSG:INFO: FluidNC 3.7.10 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 spiffs]
[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: Axis count 4]
[MSG:INFO: Axis X (0.000,490.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,490.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: Axis Z (-100.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: Axis A (-720.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:3 CS:I2SO.14 Step:I2SO.13 Dir:I2SO.12 Disable:I2SO.15 R:0.110]
[MSG:INFO: X Axis driver test passed]
[MSG:INFO: Y Axis driver test passed]
[MSG:INFO: Z Axis driver test passed]
[MSG:INFO: A Axis driver test passed]
[MSG:INFO: feed_hold_pin gpio.39:low]
[MSG:INFO: Kinematic system: Cartesian]
[MSG:INFO: Laser Ena:NO_PIN Out:gpio.27 Freq:5000Hz Period:8191]
[MSG:INFO: Using spindle Laser]
[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]
Grbl 3.7 [FluidNC 3.7.10 (wifi) ‘$’ for help]
?
ok
$I
[VER:3.7 FluidNC 3.7.10:]
[OPT:PHS]
[MSG: Machine: MPCNC]
[MSG: Mode=STA:SSID=:Status=Not connected:IP=0.0.0.0:MAC=E0-5A-1B-E4-7B-D0]
[MSG: ]
[MSG:Mode=AP:SSID=FluidNC:IP=192.168.0.1:MAC=E0-5A-1B-E4-7B-D1]
ok$10 = 1 (Status report options, mask) $30 = 255 (Maximum spindle speed, RPM) ok >>> $G [GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0] ok
So if flashed fine, you plugged it back in, and connected it to your sender and things are all moving?
Please be careful with that sender, I highly recommend you stick with the onboard stuff, or cnc.js, until we get it working. I can not troubleshoot using a program I have never used and I am not confident supports fluidNC.
NOT correct. will respond in a few
One of the devs seems to indicate there is a compatibility issue with UGS currently. Joacim works on cnc.js, fluidnc, and UGS it seems. He knows what he is doing. https://groups.google.com/g/universal-gcode-sender/c/QvpaZXEc_p4?pli=1
Please use cnc.js or the onboard sender.
will the jackpot work with Lightburn
So why am I having the same problems with cncjs and ESP3D
Also switched to a Meanwell 24v 5a PSU
yes, with lasers.
What issues? Please use the onboard wifi sender and run $ss again. Let’s make sure UGS didn’t mess anything up (again?).
Should not change anything.
The same problems I have had from day 1.
But no worries.
I have done everything you asked. UGS has not been used since right before lunch. I got Chrome and used the onboard sender. Got cncjs and got that going. None of that has solved any issues. I can shut it all down power, USB, and restart computer. Bring it back up and I may get - cannot connect. Start back up and it will connect sometimes and also give different boot screens. Tomorrow I am going to start over and take pictures of the screens that I see and just let you see how screwed up this deal of mine is. BTW I am going to take the hardware back in the house and use another (#3) computer and experiment. This will be an HP i5 touchscreen laptop.
PLease reiterate what exactly is happening at this point.
Some things I am expecting others can not possibly be the same, since we have changed firmware several times.