MetaWearC timing issue
I am collecting streamed 200Hz packed acceleration data from a MetawearC sensor and also a MetaMotionC sensor (at different times). When I use the recommended approach to calculate the time by incrementing the timestamp by 5ms per value, the MetaWearC times are incorrect, while the MetaMotionC times are okay.
If I use a step value of 16.5ms for the MetaWearC sensor data, the times are correct.
What is the likely reason for this?
This discussion has been closed.
Comments
Post your code
public void onServiceConnected(ComponentName name, IBinder service) {
///< Typecast the binder to the service's LocalBinder class
serviceBinder = (BtleService.LocalBinder) service;
https://mbientlab.com/androiddocs/3/advanced_features.html#high-frequency-streaming
Noted.
What is the default maximum Connection interval and why do the MetawearC and MetaMotionC boards perform differently?
Default connection intervals are whatever the central device wants them to be; there is no set default value.
MetaWearC and MetaMotionC boards have different hardware and run different firmware.