I know we can have client and AP running together so long as they are on the same channel. (Since it is a single band device).
I'll look into what you are trying.
The problem was a faulty WiFi router which since then been replaced and it now works much better.
Still I have problem connecting to the http server on config AP when at the same time trying to join on STA interface. Our firmware scans for AP:s every minute when not connected with STA.
If config AP is on one channel and STA interface joins an AP on another channel which seems to work. What happens with config AP? Does it jump channel to?
Haven't looked at appliance demo because our HW can't use power save mode. Will check it out but it should work because we doesn't have issues on STA interface.
The config AP jumps channel as well however, the channel is changed without informing clients.
At this time we don't support gracefully changing the channel of an AP with the set_channel() API that does a CSA to tell clients the AP is going to move.
Hope this helps.
Still have problems with config AP. Scanning for APs at the same time. Can that affect channel?
Just started to investigate this issue again.
We have a very crowded WiFi environment.
Then I have another question. When it loses connection on STA interface our firmware scans for other known APs for a new WiFi connection. What is the correct way to handle the network. Shall we do a wiced_network_down() or leave it "up" and just try to connect to remote AP? TCP and UDP server won't return form wiced_tcp_accept() , wiced_udp_receive() when we lost WiFi STA connection. It's therefore hard to restart everything in a nice way.
Thanx for help
Config AP doesn't show up. Soft AP works. I will use that instead.