Logging issue using MetaBase
Just bought a MotionR and was able to pair it to the app using Android just fine. I then wanted to test out the features of the device, used the streaming data and it seemed to function correctly (had data values in the csv files). Then I tested the logging function and based on the tutorial videos, mine is NOT preforming correctly.
When I start a new logging sessions with whatever values I choose, and click configure, the next screen I get is the device/sessions screen, and not the "steaming" screen with the stop button at the bottom. The sensor DOES record and I can download the session afterwards, but I have no say over the time intervals this way. When It goes back to the device/sessions screen it instantly shows the device as disconnected then about 5 seconds later the app reconnects.
I expect it to function as it shows in the https://mbientlab.com/tutorials/MetaBaseApp.html Video 6.5.2 minute 3:03.
I have reinstalled the app twice, cleared it's cache and data, removed and added the MetaWear device, and nothing changes the function that I am getting. Is there something I might be missing or is this a bad device? The logging function is very important for me since I need higher freq for acceleration for my application.
Comments
There is no stop button for logging. The iOS video shows the correct flow of the app and we'll need to correct the Android version.
Ok, that is fine. Could you share how long the Logging works for? The documentation on it seems a bit lacking as I can't find out any time frames it records in, etc.
Am I able to control the log lengths from the device?
There is a calculator in our tutorial to calculate the logging time. You should ALWAYS check tutorials first.
I HAVE checked the tutorials located here https://mbientlab.com/tutorials/Basics.html on all tabs and I personally couldn't find anything related. Even SEARCHING logging brings up nothing to answer my questions or teach me.
ALSO, checking and reading the whole product documentation https://mbientlab.com/documents/MetaMotionR-PS3.pdf yielded less than helpful results.
Thats why I came to the FORUM to ask for help since I was unable to find the answers I was looking for. So I dont understand why you wouldnt rather be more helpful in your response vs. playing the blame game. Esp after we already established there is an error in the be-all end-all guide.
If you are referring to https://mbientlab.com/tutorials/Calculator.html then you should rename that to "Logging Memory Calculator" so it makes more sense what it relates to. It would also be helpful to have a tab deicated to the in's and out's of logging/streaming. Even after looking at the calculator I still have questions.
-Does the device always record the entire length of memory when logging? I.E. if the Calc says itll log for 11mins, can the user stop the logging sooner than that?
-Does the device clear its own memory once you download the data to a phone?
-How long will the device hold the last log for?
Of course I would rather not waste my time or anyone else's time on a forum if I could've found these answers easily and coherently myself.
-Does the device always record the entire length of memory when logging? No, why would it?
I.E. if the Calc says itll log for 11mins, can the user stop the logging sooner than that? Yes, as per our APIs and our metabase app, there is a start and stop button which you can use at anytime.
-Does the device clear its own memory once you download the data to a phone? Yes, this is also described in our API documentation
-How long will the device hold the last log for? That's what the calculator is for in our tutorials.