I have a spare ESP32-WROOM-23E that I picked up from Ryan (date on board: 1/6/24 - V1). I thought I’d try to test out the latest 3.8.4-pre6 and test it out to help out the community.
I plugged it in my laptop and used the FluidNC Web Installer.
I had to hold down the BOOT and then EN buttons, then release the EN and BOOT to get it to install. When it was done installing, it didn’t let me upload my config.yaml file. If I go to the Terminal, it just shows this over and over:
Brownout detector was triggered
ets Jul 29 2019 12:21:46
rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:1
load:0x3fff0030,len:1184
load:0x40078000,len:13260
load:0x40080400,len:3028
entry 0x400805e4
[MSG:INFO: uart_channel0 created]
[MSG:RST]
[MSG:INFO: FluidNC 3.8.4-pre7 https://github.com/bdring/FluidNC]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:ERR: 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: STA SSID is not set]
Is this to be expected when connected to the USB port of my laptop? I’ve done this in the past (with my active ESP32) and never saw this.
Might I have a faulty ESP32 card?
Am I good to go and put this in my Jackpot and then upload my config.yaml when connected (via WiFi since that’s what I do. I do have a dedicated WiFi router that is < 10 feet away and this is my preferred method of transferring and connecting to FluidNC which works just great for me with the active ESP32).
Okay if you are going to try the cutting edge stuff best to not use the web installer for now.
Download the pre7 assets package from the fluidNC github, unzip it.
Run erase.bat, then install_fs.bat, then install-wifi.bat, from there use the web installer to dump our version 2 or version 3 webui and files on it.
For some reason the web installer is being a bit funky this week I posted a message with the designer. On a fresh boot and single try with the web installer I need to spam the boot button sometimes, after a dozen boards it gets hard to get it to trigger even in an incognito window.
Ok, I’ve tried 3 different cables. Each one with a shorter length (shortest is only 8"). Each one gave me the same ‘Brownout’ message. I tried multiple different USB ports, same message.
I even moved to my desktop and tried the different cables/USB ports. Same message.
Moving to my desktop computer removed the need to hold down the BOOT and EN buttons (that was a nice relief ).
Each case, I was able to install FluidNC using the Web Installer. And after it finishes, it restarts the board and then I get back to this screen which doesn’t show me the File Browser or WiFi options. I’m guessing this is because I’m stuck in the ‘Brownout’ case.
hmm. Any other suggestions to rule out a bad board?
@vicious1 I did as you suggested using the .bat files, when I went back into FluidNC Web Installer, the same screen above showed up. Not allowing me to upload any files and still had the ‘Brownout’ condition.
While I don’t use the Web Installer often, I’ve seen it display like that after a successful install. So, it might be fine. Assuming it’s still in the default Wifi settings, you could try and connect to it’s network (FluidNC) and connect via http://192.168.0.1 or http://fluidnc.local
That will let you upload files and you can also configure wifi via the main WebUI.
I cooked an ESP32 and got that brownout message. I don’t think I was able to flash it in that state so I don’t know that this is what you are experiencing. How to cook an ESP32 on your Jackpot (Don't do this)
Thanks Jason. For thought (1), yes, that was what I was asking. If my USB port isn’t providing enough power, then maybe if I put it in the Jackpot and then see if I could connect and if so, then I could finish uploading the config.yaml and WebUI and get it set up.
I didn’t put in in backwards, like thought (2), and I see your brownout message is just like mine. So, if thought (1) doesn’t work, then I think I have a bad ESP and will need to order another one from Ryan.
Got to do some other stuff tonight. Have no real plans for tomorrow, so I’ll try thought (1) tomorrow morning.
Tried it with the ESP32 on the Jackpot, no FluidNC SSID shows up. Tried to connect via USB and the same things happen…Web Installer installs FluidNC, but the terminal still shows brownout.
I’m guessing sometime since I purchased it, it flaked out and I’ll need to purchase a new one.
If this helps, its a dark colored PCB version. I currently have the White PCB version as my ‘active’ one that’s been working just fine.
Nope. Only have the 1 desktop and 1 laptop. I plugged the ESP32 into all available ‘blue’ USB ports (3 different ones) on the desktop using the shortest cable I had (~8"), and then opened up fluidterm.bat. Every time it was showing the brownout message.
So I can make sure I satisfy your curiosity, when you say ‘on the Jackpot with power’, do you mean, put it on the jackpot, power up the jackpot (with the 24v DC power) and then plug it into my USB port and open up fluidterm.bat? If so, it shows the brownout message still.
Are you perhaps plugging this into a USB extender or like a extra 4 port USB device connected to your computer? This needs to be plugged into the back of your comptuer if desktop or any port if laptop otherwise the ports don’t provide enough power to get it going.
).
