You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Raspberry Pi Pico W with RP2040; Raspberry Pi Pico 2 W with RP2350
MicroPython version
MicroPython v1.24.0; MicroPython v1.25.0;
Reproduction
Install RPI_PICO2_W-20250415-v1.25.0.uf2 on Raspberry Pi Pico 2 W.
Create main.py with script below on device.
Power on device with USB or batery.
Wait 10 hours. Do not access the device over the network.
On PC (in my case Windows 10) run command "ping 192.168.10.241 -t".
# main.py
import network
from time import sleep
from machine import Timer, Pin
led = machine.Pin("LED", machine.Pin.OUT);
wfssid = "xxxxxxxxxx"
wfpass = "xxxxxxxxxx"
wlan = network.WLAN(network.STA_IF);
wlan.active(True);
print(f'Connecting to "{wfssid}" AP. ', end="")
wlan.connect(wfssid, wfpass);
while wlan.isconnected() == False:
sleep(1.0);
print('.', end="");
print(' Done !');
print(wlan.ifconfig())
def cb1sec(timer):
# To be sure that the device is working
led.on()
sleep(0.001);
led.off()
timer1sec = Timer(period=1000, mode=Timer.PERIODIC, callback=cb1sec)
while True:
sleep(10.0);
Expected behaviour
Starts respond on pings immidiately.
Observed behaviour
Starts to respond after 10...60 unsuccessful pings.
Additional Information
The device stops responding to ping after a few hours of operation.
Powered by USB or battery, no USB connection (with USB connection it also sometimes "hangs")
The device "hangs" after 1...10 hours.
During this time, do not access the device over the network!
During "hanging":
Unable to connect to FTP server on device.
Ping from device continues to work!
When device is "frozen", you can "wake it up" using command:
ping 192.168.10.241 -t
Initially, the device does not respond to pings, but after 10...60 unsuccessful pings, device starts responding and normal operation of network interface is restored.
See:
Raspberry Pi Pico W network becomes inaccessible when not used for some time #9455
With network.PPP device hangs after several hours of operation #16340 #9455 and #16340 probably have the same root cause.
Not Reproducing on:
MicroPython v1.25.0 on 2025-04-15; ESP module with ESP8266. (ESP8266 Wemos D1 mini)
Code of Conduct
Yes, I agree
The text was updated successfully, but these errors were encountered:
Port, board and/or hardware
Raspberry Pi Pico W with RP2040; Raspberry Pi Pico 2 W with RP2350
MicroPython version
MicroPython v1.24.0; MicroPython v1.25.0;
Reproduction
Expected behaviour
Starts respond on pings immidiately.
Observed behaviour
Starts to respond after 10...60 unsuccessful pings.
Additional Information
The device stops responding to ping after a few hours of operation.
Powered by USB or battery, no USB connection (with USB connection it also sometimes "hangs")
The device "hangs" after 1...10 hours.
During this time, do not access the device over the network!
During "hanging":
When device is "frozen", you can "wake it up" using command:
ping 192.168.10.241 -t
Initially, the device does not respond to pings, but after 10...60 unsuccessful pings, device starts responding and normal operation of network interface is restored.
See:
Raspberry Pi Pico W network becomes inaccessible when not used for some time #9455
With network.PPP device hangs after several hours of operation #16340
#9455 and #16340 probably have the same root cause.
Not Reproducing on:
MicroPython v1.25.0 on 2025-04-15; ESP module with ESP8266. (ESP8266 Wemos D1 mini)
Code of Conduct
Yes, I agree
The text was updated successfully, but these errors were encountered: