AP with multiple clients issue #15358
Replies: 3 comments 2 replies
-
Of course Wifi connections are not perfectly reliable. One other thing that comes to mind: Could it be that there is interaction of the Wifi protocols between the AP and clients 1 and 2? If these are different then there might be a way to de-synchronize their activities somehow... |
Beta Was this translation helpful? Give feedback.
-
It can be to a problem of close socket.. |
Beta Was this translation helpful? Give feedback.
-
I note that Output 2 seems to indicate the the wifi scan failed to find the ssid. However, this does not necessarily mean that a connect() would have failed. It would be better to skip the check_SSID() and simplify your Also, a note that |
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.
-
Hi All.
First post here.
My project involves 3 Pico-Ws.
One of them is set up as an AP and the other 2 as Clients. We will call them Client # 1 and Client # 2.
Upon code execution, the AP Pico sends the current time data to both clients.
Ideally, both clients receive the current time data and set the Real Time Clock modules attached to them. Job is done.
Here is the issue:
When I run the AP code, 60% of the time, it runs fine and both clients receive the data and life is good. Both clients have an 'Output type 1'.
( Please see the end of this post below for the 3 types of output )
The other 25% of the times that I run the AP code, Client # 1 produces an 'Output type 1' and Client # 2 produces and 'Output type 3'.
The other 15% of the times that I run the AP code, Client # 1 produces an 'Output type 2' and Client # 2 produces and 'Output type 3'.
( I use Thonny. I click 'run' on the AP code, then 'run' on Client # 1's code and then 'run' on Client # 2's code; in that sequence )
I tried resetting the Pico-W before running code each time but that doesn't seem to help.
I tried putting a pause in the AP's code but that didn't help.
I did a ton of other things but this random behavior keeps popping up.
My reading online tells me that 'Output type # 3' happens due to the connection being forcibly closed by the remote host. This Output type # 3 can also mean that the AP is overloaded or misconfigured, which causes it to drop connections. It just probably cant handle multiple simultaneous connections properly.
When I have just a single client, I never have any issues and the output is always 'Output type 1'.
Can someone please give me feedback on whats going on?
Ty for the replies!
AP CODE below:
Client # 1 code below:
Client # 2 code below:
Beta Was this translation helpful? Give feedback.
All reactions