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 begin with the LED example from the starter template. Follow the README instructions to create an app that turns off/on the LED. https://github.com/mbientlab/MetaWear-Tutorial-Android/tree/master/starter Once you're comfortable with …
-
This post from SO might be useful: http://stackoverflow.com/a/28545134 You can through the use of a global variable. You can also pass the BluetoothDevice object with the Intent object instead as it is parcelable.
-
The error message tells you the service variable is a BinderProxy type so you have to cast it to the BinderProxy class, not the BtleService.LocalBinder class.
-
Yes, that variable. The error message says "null object reference" so you need to initialize it before calling scheduleAsync.
-
Double tap can be pretty finicky to configure correctly so you'll have to experiment with different configurations to find what works for your use case.
-
You'll need to play around with the double tap configuration to find what works for your use case. For the moment, you can also add a null pointer check to discard Tap objects with a null tap type.
-
Chaining filters together will behave like a logical AND and creating branches functions like a logical OR. The only thing to be mindful of is that all branches that accept the input data will let the data through rather than just the first valid b…
-
Did you initialize the timerModule variable?
-
The white button does not reset the board; either remove the battery, use the Debug module to issue a reset command, or use the MetaWear app to also issue the reset command.
-
Please see my previous post (2nd paragraph).
-
Documentation, sample code, etc. are provided in the api v3 thread:http://community.mbientlab.com/discussion/1993/android-api-v3-0#latest The project README has a section highlighting some important changes: https://github.com/mbientlab/MetaWe…
-
Are you testing with a board that is in a clean state or has your board been configured by other apps and is in an unknown configuration? Also, please post your api v2 code.
-
1) Use correctedAngularVelocity. The other sensor fusion outputs are also listed in the javadocs page. 2) Depends on how you are using them. Are you chaining them together or feeding the same data to multiple threshold filters with a multicast…
-
Looking over the API implementation again, the API actually assigns a new timestamp to each data forwarded to the apply function. Does your use case require that the packed data use the same timestamp?
-
API v3.0.7 is now available, see first post for change summary.
-
Other than a few syntax errors (missing assignment operator, should be addRouteAsync), that is how you access sensor data. The metawear app code, example apps, and unit tests all access data as outlined in the documentation. What code do you have…
-
Which timestamps are you comparing? Packing data combines values from the same sensor; it does not combine data from multiple sensors into 1 packet. The packed functions are working as described so it seems like this is simply a misunderstanding o…
-
We have discussed the counter idea before but it is not something we are planning on adding as we have a packed mode for high frequency streaming. Matt addresses briefly talks about adding a counter in this post (2nd to last paragraph). http://…
-
MBED support was not added.
-
I need the code you were using with API v2 since you said this issue occurred once you upgraded to v3. Please post that code. Are you configuring things such as odr and range along with tap detection? If so, post that code as well. The code sni…
-
Use the MetaHub app.
-
What kind of errors are you getting and what parts of the documentation is not clear to you? How are you attempting to use the sensors? You can also refer example projects linked in the thread as well, such as the MetaWear app, to see working cod…
-
The MetaTracker uses the LTR329 ambient light sensor. MetaEnvironment boards have the TCS34725 color sensor however those are only available in bulk quantities. If you are looking for the color sensor, please contact us directly for more informati…
-
Links to documentation and example code are provided in the API v3 thread. http://community.mbientlab.com/discussion/1993/android-api-v3-0
-
This pdf should get you pointed in the right direction though it is 2.5 yrs old https://mbientlab.com/docs/MetaWearFirmwareDevelopmentGuide.pdf
-
Please post the code you were using with api v2 and v3, specifically, all the calls to configure the accelerometer and tap detection. What board are you using again? BMI160 is the IMU not the board.
-
How were you configuring the tap detection with the previous API? Also what board and firmware are you using?
-
Counting the packets as described in this thread is sufficient to match acc & gyro data provided you have a stable and properly configured connection for streaming data at a combined 100Hz.
-
You only needed it in this case to remove cached information about the board from the previous API.
-
TapTypeBoth simply indicates that both single and double taps should be detected.