Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
In my project, the WiFi credentials will be changed in the field (by programming a configuration file via USB at installation time). I cannot find any API or example that updates the WiFi credentials for automatic re-connection.
All I can come up with is to use wiced_wifi_scan_networks(), finding the network(s) configured in the field, and connecting to a network using wwd_wifi_join_specific().
Is there a better way to change (or add to) the credentials read from wifi_config_dct.h?
Is "join" sticky? I.e. will the stack re-connect to that AP if connection is lost?
Even if the answer to #2 is "yes", it seems like the device will be stuck with a single network; losing the ability to fall back f that network goes down. Unless I build my own scan-reconnect on every disconnection.
as you can see, pretty easy. Now the limit if 2 is imposed in the WICE/internal/unit/dct.c file. if you want to add more entries you can add some lines in here. find the line <#if defined(CLIENT_AP_2_SSID)> and under that sections endif, add these lines:
then, right below that you should see a line <#define DEFAULT_AP_LIST \>, in that section, under <DEFAULT_AP_LIST_ENTRY_2 \>, add the line:
and thats the whole process for adding another AP entry. For the third entry in the config_dct, just change the 2's to 3's.
The behavior on calling wiced_network_up() is a bit different - if it should fail to join the first network, it will try the second, then third, and so on if they keep failing, so keep that in mind -> that isn't necessarily a good thing all the time (as in my case), and if you used this method you would still need to swap the dct entries everytime you wanted to change networks, so I went a different way and it uses the method in the post that rroy mentioned above - add a few #defines with all your different AP names and pass them to the read_write_dct function after you've disconnected from the prev network.
As for if this breaks OTA2 support, I have no idea, and id also be curious to know. rroy , any ideas?