search

bdring / FluidNC

The next generation of motion control firmware
Other
1.61k stars 383 forks source link

Brownout detector was triggered when wifi wants to begin #1269

Open mstfyghm opened 3 months ago

mstfyghm commented 3 months ago

Wiki Search Terms

Brownout detector was triggered

Controller Board

esp32 D1 mini

Machine Description

co2 laser cnc

Input Circuits

No response

Configuration file

not needed.

Startup Messages

FluidTerm v1.2.1 using COM3
Exit: Ctrl-C, Ctrl-Q or Ctrl-], Clear screen: CTRL-W
Upload: Ctrl-U, Reset ESP32: Ctrl-R, Send Override: Ctrl-O
[MSG:INFO: uart_channel0 created]
[MSG:RST]
[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 spiffs]
[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]

Brownout detector was triggered

ets Jun  8 2016 00:22:57

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 v3.8.0 https://github.com/bdring/FluidNC]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is spiffs]
[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]

Brownout detector was triggered

User Interface Software

Fluidterm

What happened?

After OTA firmware update from v3.7.16 to v3.8.0 it didn't work. so I tried with erase and installing fluidnc using usb cable. and after opening Fluidterm it shown that brownout was detect when wifi is going to start. By downgrading to v3.7.16 every thing is ok.

GCode File

No response

Other Information

No response

MitchBradley commented 3 months ago

This is a common problem with mini ESP32 boards. Some of them have inadequate filter capacitance on the 3.3V rail, after the LDO regulator on the board. On my mini-32 boards, I added external 50uF capacitors on 3.3V. Just to be safe, I also added them on the 5V rail. Without the capacitors, if you look at the voltage rails with an oscilloscope, you can see a substantial voltage dip when wifi turns on. It is especially bad with some USB cables that have small-gauge wire inside.

Yes I know that it sometimes works with some versions of the firmware. We don't have time to track down subtle details of wifi-turn-on sequencing that only affect a small proportion of boards.