losts of work, I think I'm running into an SRAM issue
Garrrgha
First pass at a threaded datalogger class, paired with working m2fs_tempmonitor

Threading seems a better way to deal with the datalogger. Part of the
unthreaded issue was the 5 seconds timeout on  the select call in
agent. It, coupled with using Agent.run, was causing protocol timeouts.
Slowly add back in functionality
Now working with logfile and sleeping, accelerometer next
Full Integration, Looks like we are actually working.
Lower the select timeout from 5s to 125ms so agent run loops are more responsive.
Bring M2FS_Datalogger2 back into M2FS_Datalogger