MattS,
Thanks for demo-ing how to find the network enumeration.
I initially started out with your perspective that this was probably some get method and would find an associated set method in the library. However, while investigate the RSSI() function I noticed it calls, and returns the result of "getCurrentRSSI()". This naming convention puzzled me. So, I checked for documentation and comments. The header file describes it as,
/*
* Return the current RSSI /Received Signal Strength in dBm)
* associated with the network
*
* return: signed value
*/
... So I believed that I am going to get the current RSSI measurement.
So, to me and I'm assuming the other 5 or so contributors here, it was "automagic" when the old value was not being updated to a "current" measurement by the call to the SPI driver to send the wifi chip a message enumerated as "GET_CURR_RSSI_CMD".
But, like I said, I see your perspective as that is how I started out.
However, I'm not sure how the distinction between an API or OS is salient, because the API is exactly that: an interface. Regardless of valuable resources, the interface should do what it is documented to do, and I'm not sure that I believe it to "return the current RSSI".
Your example is much appreciated. I will play with the function I mentioned using this technique. Thanks again!