- Fri Jan 01, 2016 5:48 pm
#37649
But I'll bet it would get rid of my console messages also. I found two things that get rid of all the chatter about A3_180 and so forth. One is to plug in my wireless router -- even if it can't authenticate, it seems happy that it has something to try to talk to. But the real thing to do is this call:
wifi_set_opmode(NULL_MODE);
This just turns off the wifi subsystem entirely, and seems to be just the thing for projects (or experiments) that don't need Wifi. You might say, "why use this chip if you are gonna turn off the wifi?", to which I would answer that for $5 it makes a heck of a little controller for many projects without the wifi.
dkinzer wrote:You might try invoking os_install_putc1() with a pointer to a do-nothing function early in your app. Doing so may suppress the OS messages.
But I'll bet it would get rid of my console messages also. I found two things that get rid of all the chatter about A3_180 and so forth. One is to plug in my wireless router -- even if it can't authenticate, it seems happy that it has something to try to talk to. But the real thing to do is this call:
wifi_set_opmode(NULL_MODE);
This just turns off the wifi subsystem entirely, and seems to be just the thing for projects (or experiments) that don't need Wifi. You might say, "why use this chip if you are gonna turn off the wifi?", to which I would answer that for $5 it makes a heck of a little controller for many projects without the wifi.
