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
-
That depends on whether want to preserve the current board configurations or not. If you don't care and want to nuke the board, use resetAsync, otherwise, call tearDown.
-
C# SDK v0.3.0 was just pushed to NuGet with the FCU changes.
-
What model is your MBP and what OSX version is it running?
-
Timestamps for streamed acc, gyro, and mag data with the MetaBase app are discussed here: https://mbientlab.com/community/discussion/1934/metahub-timestamps#latest Given that you are recording data from multiple sensors (and devices) simultane…
-
Our iOS dev has pushed an update to the Swift SDK that enables configuring the BMI160 digital filters. This update isn't public yet so you will need to update your pod file to point to the GitHub repo: pod 'MetaWear', :git => 'https://github.com…
-
SDK v3.3.0 has been released which fixes using anonymous routes with the step counter.
-
So, to confirm, the checkpoint commit is working as is for you?
-
I tested the aforementioned commit on two other PCs (Integrated Intel adapter and Broadcom BT dongle) and the SDK is working fine on those machines. I suspect it could be a BT adapter issue on your end stemming from the first creator's update. …
-
Remove the buffer component.
-
Post your code and firmware / hardware revision strings for the board.
-
No, the Python SDK is Linux only. You can instead use the Javascript SDK on OSX.
-
Logger timeouts typically occur when the user tries to allocate too many loggers or continues to add loggers without removing old loggers. The illegal state exception with the step counter identifier is a bug with the Android SDK that will be pa…
-
See the I2C unit tests:https://github.com/mbientlab/MetaWear-SDK-Android/blob/master/library/src/test/java/com/mbientlab/metawear/TestI2C.java
-
Follow the example code provided in the Bolts documentation: https://github.com/BoltsFramework/Bolts-Android#error-handling
-
The task's result should not be null in this context, which indicates the task failed. Confirm that the task did fail and post its error.
-
Follow the example code in the Bolts documentation:https://github.com/BoltsFramework/Bolts-Android#error-handling
-
Post your code.
-
Yes the standard stream code should always work, however I am asking (again) that you check if the task failed or not. I cannot help you further until you have checked the task's status and posted the error message if any. As stated in my previous…
-
Post your Python script.
-
Given that you are not getting any output, it is highly unlikely the task did in fact succeed. Please confirm by adding error handling to the Continuation object.
-
Did the addRouteAsync task succeed?
-
There is already an on-going discussion regarding a similar topic: https://mbientlab.com/community/discussion/2240/sensor-fusion-makes-lots-of-noice#latest
-
Yes, we will update the SDKs to provide access to the BMI160's digital filters.
-
https://msdn.microsoft.com/en-us/library/wkze6zky.aspx
-
It doesn't yet exist in any public releases. You can try it out by cloning and building the latest version of the C# SDK source code.
-
Well, we don't know why only the Android platform is experiencing timeouts nor why it only occurs with logging. You will need to take this up with @FrozenKiwi to figure out the appropriate fix as Xamarin support is based on his fork. Some general…
-
Hrm, that doesn't make sense as both DownloadAsync functions call the same underlying function but with different default parameters. This log and download code snippets are working fine with my board: private async Task Start(IMetaWearBoard m…
-
You should be able to, yes.
-
Try logging data with the MetaBase app on your Android device:https://play.google.com/store/apps/details?id=com.mbientlab.metawear.metabase
-
My primary Android dev device is a Nexus 6 that also runs 7.1.1 and it doesn't have any scanning issues. Given that the nRF Connect app is working, its possible you did not allow location permissions for the MetaBase app. Double check the app perm…