ESP32 Wifi DHCP Discover broadcast failure New Chip vs Old
Posted: Wed Aug 14, 2019 8:49 pm
Hello and thank you for reviewing.
I have prototyped an IOT device using the ESP32 WROOM-32 Module, wherein 100 modules were used from 2018. ALL GOOD!
I just finished a build with two new Reels (1100) of WROOM-32 modules, same design and am having a significant Wifi DHCP connection issue with an error indicating that SSID found, Wifi STA and CON; however a timeout waiting for an IP.
I used a network analyzer to watch the activity and see that the new modules post up onto the Wifi with a DHCP Discover, multiple times with no answer (ie:Offer / Request / Ack) handshake from the DHCP server, thus timing out with no connection.
I am using the same boards and the same firmware. The exception is the ESP32-WROOM modules which are newer.
Any thoughts would be greatly appreciated! Possibly the newer modules take advantage of newer toolchain builds with (now) enabled features that were not available prior so that my firmware leaves these in a default state which is different than the previous modules?
The antenna gives the same Db signal strength of an Access Point for either so the antenna is OK.
Module marking: (hard to read)
2019 Modules: ESP000V307
2018 Modules: ESP000V301
I have prototyped an IOT device using the ESP32 WROOM-32 Module, wherein 100 modules were used from 2018. ALL GOOD!
I just finished a build with two new Reels (1100) of WROOM-32 modules, same design and am having a significant Wifi DHCP connection issue with an error indicating that SSID found, Wifi STA and CON; however a timeout waiting for an IP.
I used a network analyzer to watch the activity and see that the new modules post up onto the Wifi with a DHCP Discover, multiple times with no answer (ie:Offer / Request / Ack) handshake from the DHCP server, thus timing out with no connection.
I am using the same boards and the same firmware. The exception is the ESP32-WROOM modules which are newer.
Any thoughts would be greatly appreciated! Possibly the newer modules take advantage of newer toolchain builds with (now) enabled features that were not available prior so that my firmware leaves these in a default state which is different than the previous modules?
The antenna gives the same Db signal strength of an Access Point for either so the antenna is OK.
Module marking: (hard to read)
2019 Modules: ESP000V307
2018 Modules: ESP000V301