The more I play with this application where I’m tracking total consumed power the more frustrated I get at how the Spark Core will basically not run the main loop if there is anything but a good WiFi connection. All data logging stops and all data is lost as soon as there is a network issue.
I can’t use the Spark Core for stuff like this until the main loop runs independent of the CC3000 status.
So if the CC3000 has a good connection I can push data from my device out to the cloud, and if the CC3000 does not have a good connection then no data will be sent out but my main program will keep running regardless.
Kinda like my cell phone and laptop that keep running regardless of them having a Cell or WiFi signal or not.
It seems that @david_s5 latest updates for auto resetting the Spark Core after WiFi issues is not working like it used to maybe? When my Data connection to the net drops out but the WiFi stays on and the Spark stays connected to the WiFi network it causes the Dark Blue Flash and the whole core locks up. I’m getting this on 2 Spark Cores at the exact same time.
Using the Spark Core to just push sensor data to the web is doesn’t cause much issue when the core locks up since I just loose a few sensor reading data points between the time the core freezez up and its reset.
But when I have a LCD screen displaying live data and that data stream and processing stops because a WiFi signal is not present then that causes issues that are simply not acceptable. I look at the WiFi as a bonus feature that allows some cool web based data interaction but it shouldn’t keep the main application from running normally.
Sorry if this is redundant but I think this is the best place to express the issues I am facing when it comes to trying to design around the Spark Core at the moment.
From what I think I understand the Spark Team is working to keep the main loop running regardless of the CC3000 wifi status? Right?