Commands A, P, R, M, and D work from the master end. Added comments to read_write.cpp. Uploading latest working version before I try and implement writing to non-volitile memory which may break everything.
Added a timeout to the send() command; the promise is rejected after a calculated timeout period depending on the command issued.  Discovered that the google API can also detect a lost connection.
Runes Commands A, P, R, M, and D. Stores data to EEPROM and runs recovery algorithm on startup. Will continue an experiment on startup if the Arduino was reset or lost power while an experiment was running. Recovers to the point in the experiement had no reset or loss of power occured. (i.e you may get less measurments than requrested.) Known Issue - There may be problems if too muchd data is writeen to the EEPROM
Removed a bebug flag from the EEPROMex library. Added a top address limit for writting to the EEPROM.Uncommenet a error check for D commmand that was commeneted out for debuging.
Application is now fairly robust against losing a device during an R-style experiment (desktop only logging).  An onReceiveError() function is invoked when a connection is lost.  This function marks a device as disconnected.  Buttons on the user interface have appropriate messages for when a connection is lost, whether or not an experiment is configured.
Removed the trash can from the serial log menu in the UI.
A first draft of a working application in which the application loses a connection with a DAQ and then reestablishes the connection during an experiment with daq-style logging.
Added a stop button that makes use of the underlying mini-SDI12 break command to stop M-style experiments.  Button is working and behaving as expected.
Corrected a frustrating problem.  Now detecting if R-style experiments are broken.  If all the devices of an R-style experiment are disconnected, the experiment is assumed to be 'broken' and the experiment is ended automatically.
Removed the Serial Log to prepare for the user studies to come in the next couple of days.  User studies will take place from the serialApp branch.
Attempting to create a commandQueue.  Right now, I can only handle a queue size of 1.  Anytime the system is overrun with commands, the commands are simply never sent and the promises are rejected.
Fixed a bug so that the daq qill repsond with the abort response if prompted with a D command before data is ready to be sent.
Merge branch 'Thermo' into commandQueue.  Obtain Mr. Pearson's fixes to the small bug in M-style experiments. D-commands were not getting a response if they were issued before any samples had been taken for the experiment. Now, D-commands get an Abort response if they are issued too early.
Able to gracefully reestablish a connection with the device during an M-style experiment.  I notice some strange responses coming from the DAQ when the device is re-enabled, but I wonder if that is some of Mr. Pearson's debug output.  I've contacted him on this matter.
Removed three debug statments that were left in by mistake.
Initial commit of the hardware documentation. Includes reference sheets for the breakout boards from Adafruit, the pinout for the Arduino Uno, the data sheet for the ATmega328P, and a schematic of the daq as it is currently built.
Parsed the datum string and inserted it into a table with headers. This is not ready to be pushed to production code. There are todos to be resolved after learning more about the codebase in first meeting. This is simply being pushed to a dev branch to be discussed over.
Commands A R M P and D work. Added functionality to  the D command such that aDm retrieves the last m meansurments that were taken from port a. The EEPROM now holds up to the most recent 144 measurments.
Made tables functioning in the correct way. While I still need to test this with a real DAQ, it should work. There is a test function left in my code that I will delete before pushing to main branch. Note that my changes killed the save feature (I took out the data.js file). I will rewire the save feature when I get the local database implemented.
Checking this in for the night. This is really incomplete, I would recommend not looking at this until a future push. Currently have the indexedDB working, but extra functionality may be needed. Next steps will be to wrap it up in a pretty API and connect it to the app.