So I’m looking into an SD card for my project and I started here: [quote=“BDub, post:32, topic:2666”]
Come one come all… get your red hot SD Card library here:https://github.com/technobly/SparkCore-SD
The main reason I want to implement a SD card onto my project/system is to ensure data is continuously being logged. I’m sending data via the core every 30 sec to a server for logging, graphics, etc. So if I ever lose WiFi what I want the Core to do is, without skipping a beat (within reason of course) just continue logging data, but now on a CSV file (or appropriate text file) that is on the SD card. THEN when WiFi is back up, Core connects back to WiFi and sends the data stored to the SD card to the server, then continues logging and sending data via WiFi. So two questions: (I’ll try and ask them clearly this time )
Is the above feasible? Or should I add a separate device and/or processor that only handles the offline data logging, then when WiFi is back on it hands the data off to the SparkCore so that it can send it via WiFi?
Almost completely unrelated. But I also am interested in using the Tinker app alongside my project, with the main goal being data logging. I know Tinker uses the SparkCloud to communicate to the Core so that it can write or read pins in near real time. Would I be able to use the Tinker app without interrupting the Core’s logging functions and it’s capability of sending data to my specified server? The issue I feel I would run into is, while sending data via WiFi to my server there might be a chance that at the same time Tinker would be trying to communicate with the Core; so I’m not sure if the Core can do both at once.
Sorry for the moth full but I would really appreciate any insight or direction on how to tackle mainly #1 and possibly #2 . Thank you