Unknown Status of 2 From Network #10746
Replies: 2 comments 7 replies
-
|
My understanding is that Micropython error messages are or were preceded by a - sign to distinguish them from "normal" Python errors. Hmmm, I see some have - signs and another ones don't. Can you do a scan? I use this on my ESPNow systems and it should give you more information: https://github.com/glenn20/micropython-espnow-utils |
Beta Was this translation helpful? Give feedback.
-
|
I have no other issue other than if I check status, sometimes it's 2 which is not defined by any of the STAT_* values. |
Beta Was this translation helpful? Give feedback.
-
|
Status 2 could be STAT_NOIP, reading the LINK Status definitions directly in the cyw43 driver here in line 80-86 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @th3w. That makes sense. |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Me too gets the status() == 2 after an apperently successful connect. 'connected: ('0.0.0.0', '255.255.255.0', '192.168.0.1', '8.8.8.8') `for a in dir (network): STAT_CONNECTING = 1 |
Beta Was this translation helpful? Give feedback.
-
|
It looks like, you got no ip adress from the WLAN. it must be a private ipV4 adress. |
Beta Was this translation helpful? Give feedback.
-
|
No, my code and hardware work. Mostly, that is. I now let it do a few retries until I get the GOT_IP, and up to now (not very long) that works. I cannot say I completely understand it, but it seems to be related to cold starting the pico. When connected to the USB and run through Thonnie, making the connection is so much easier, that I suspect either the controller or the router does not completely disconnect. I have the impression that after a cold start, the first connection attempt returns -1 or -3, the second +2, and the subsequent +3. The controller's mac-address has a fixed IP leased from the router, so it may be the router that is to reluctant to make the ip-address available again after the controller was disconnected. Another possibility is that more time is required after leaving the while status() == CONNECTING loop and testing the new status. I now have a sleep(2) to add some time. When I have a bit more time, I'll rewrite the module in Asyncio-style. |
Beta Was this translation helpful? Give feedback.
-
|
For the PICO_W using the CYW43 the link status 2 refers to :
As you found you need to wait 'some time' to allow for the router/dhcp server to check its pool, assignment and allow for the offer to be accepted. perhaps also useful: a simple explanation of DHCP |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, that was very informative. It suggests that just waiting a few seconds after receiving NOIP (2) the queried status just might change into GOT_IP/UP (3). I would have tried that just now, but unfortunately today (with another picoW-board) I am not getting the NOIP again. Either way, my workaround to repeat the connection request also overcomes the steady first connection failure after a cold boot. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm getting a status of 2 coming back from WLAN.status() after WLAN.connect(...). What does the 2 mean? I can't see it listed in help(network)
Here's the code snippet
wlan.connect(secrets.ssid, secrets.pwd)
sleep(3)
# If the status is not 'connecting' (1) or connected abort
status = wlan.status()
if not ((status == 1) or wlan.isconnected() ):
This is what I see from help(network)
STAT_IDLE -- 0
STAT_CONNECTING -- 1
STAT_WRONG_PASSWORD -- -3
STAT_NO_AP_FOUND -- -2
STAT_CONNECT_FAIL -- -1
STAT_GOT_IP -- 3
Beta Was this translation helpful? Give feedback.
All reactions