Eric
Do not send private messages with technical questions; they will be discarded. All technical questions must be posted publicly on the forum.
About
- Username
- Eric
- Joined
- Visits
- 9,275
- Last Active
- Roles
- Administrator
Comments
-
You can use the AdvertisementConfig interface to modify the ad interval
-
The sampling rate is 0.033s (30Hz). If you run the sampling for longer, say 120 seconds, does the graph stop at 40 seconds? If not, then it seems like your device is not capturing all data packets.
-
I'm not sure what you mean by using motion detection inside a timer. Motion detection is a algorithm running on the accelerometer, independent of MetaWear.
-
Looks like it's an issue with the FitBit as well. Maybe one of the suggestions mentioned in this thread can help you out: https://community.fitbit.com/t5/Windows-10-App-Windows-Phone-App/Windows-10-driver-error/td-p/953839
-
I believe it's a bug with how the sensor needs to be configured for ODR less than 12.5Hz. Until it's fixed, you can set the ODR to a higher frequency and use the time filter to reduce the sampling rate.
-
Does the graph show 1 minute worth of data?
-
That depends on the accelerometer's output data rate. If you're running it at 100Hz, then it will fill up the logger in about 30 seconds. You should instead utilize the bmi160's build in detection algorithms to avoid storing acceleration data. …
-
Sorry about the confusion. Yes, standby time is in milliseconds and TIME_0_5 means 0.5ms. No, not at this time. The values and units are taken straight from the sensor's spec sheet.
-
I do not see any issues exporting data past 1 minute on my Nexus 6 (Android M) and Nexus 7 (Android 5.1.1). Just to be clear, you can see 1 min worth of data on the graph but when you export the CSV file, you only receive ~40 seconds?
-
With the old API, there only way is to use a counter as you mentioned.
-
I'm not sure then. You can try making a new C# Universal Windows app to see if fixes the issue. Copy the xaml and C# files and add the MetaWear.WinRT package from NuGet. Alternatively, you can see if the UWP starter template works for you. http…
-
Did you install the Universal Windows App development tools?
-
That description is wrong and will be fixed, apologies for the mistake and any confusions. 100Hz is the the highest stable frequency that we have observed the BTLE handle. You can check if my assumption about dropped packets is correct or not by …
-
You need to wrap callback functions with the appropriate delegate type from the Core namespace, in this case: FnVoidPtr.
-
This isn't an adapter issue. MatLab does not support the Bluetooth LE protocol so it cannot directly communicate with the MetaWear. You'll have to build your own Universal Windows app with the C++ API if you want to stream to the PC. https://mbie…
-
NullReferenceException moved here:http://community.mbientlab.com/discussion/1614/nullreferenceexception-with-uwp-starter-template#latest
-
@hsutuo You need to provide more information than a error message. * Does this error occur frequently? * Can you reliably reproduce it? * If so, what are the steps to cause the error? * What device and OS are you testing on? @jaybers This see…
-
It's hard to say. It could be an issue with Samsung's Android variant or a hardware issue. Bluetooth LE is inconsistent across Android devices and OSes so unless this problem frequently occurs, there isn't anything to worry about. The only thing …
-
Matlab only supports the Bluetooth SPP Profile so no, it can't be done. You can either use the MetaWear app to save data onto your mobile device and send them to your Matlab pc or use the APIs to build an app that pushes data to the cloud / remote …
-
I'm not sure if you can build a data processing chain that can accomplish the same thing as your code. The biggest roadblock is the accumulator variable (suma) that is either incremented or decremented based on some condition; there is direct equiv…
-
What Android OS and device are you using?
-
1) The passthrough filter you are using, as presently configured, is blocking all incoming data. 2) You should be able to manipulate accelerometer data in that fashion (math ops, comp, etc.) using feedback loops. What specifically are you trying …
-
Hrm...what could be happening is that the notify characteristic is being killed since the code does not save a reference to it. I modified the uwp starter app to save a reference to the notify characteristic. Let me know if this change fixes your …
-
What do you mean when you say it stops streaming? Does the valueChanged event handler stop being called? Or, it does but the subscribe delegate no longer get fired? Does this problem persist if you try using the UWP template instead of the tutor…
-
It appears that packets are being dropped due to the high frequency of the stream which is to be expected as Bluetooth LE is not meant for high frequency traffic. You can try to get the phone as close as possible to your board to improve signal str…
-
Attach a time processor to the acceleration data.
-
Sorry, that was a typo in the in the code snippet and has been corrected. The CompletionHandler generic should be RouteManager not Timer.Controller. AsyncOperation.CompletionHandler
-
It sounds like that logger is either full, which won't log any more data, or did not fully download. Stephen has addressed the other logger issue so assuming you are still running into problems after his fix, you need to first test your setup on 1 …
-
300 total samples is pretty excessive. Does a lower number work like 48 (16 per axis x 3 axes) ?
-
Bluetooth LE communication is not managed by the API; connection management needs to be handled by your underlying btle library. mbl_mw_debug_disconnect is not to be used in this case. The mbl_mw_metawearboard_tear_down and mbl_mw_metawearboard_f…