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
-
Are you wrapping the settings commands in a Macro code block? https://mbientlab.com/androiddocs/#macro-recording
-
The major.minor version message relates to using an incompatible JRE/JDK version. Either switch your API to Android M or install JDK8.
-
As mentioned in my post, accelerometers, and similar sensors, have very accurate clocks, typically with only 1% error. If you set the data rate to 50Hz, you will consistently receive data every 20ms. Unless you need the absolute time of when the d…
-
You can compile the API as a Win32 DLL or integrate the code directly with your project.
-
What JDK version are you using?
-
yes
-
Check out the C# wrapper solution, specifically the WrapperTest project.
-
If you haven't already, please read the Visual Studio section in the README and take a look at the C# Wrapper project for a working example. What are the errors you are seeing in your build? I don't think a Windows Runtime component is compatib…
-
Please see my post from a similar thread regarding this issue:http://community.mbientlab.com/discussion/comment/1792/#Comment_1792
-
What are the inconsistencies you are seeing? Again, I can take an educated guess but you need to provide me with more context and explain what is wrong with the Android data compared to the iOS data. I'm not sure what a RION meter is.
-
The rectangular case will not be available. It is nothing more than a fancy paperweight.
-
We provide Android, iOS and C++ libraries for the MetaWear platform so any developer with mobile platform experience will suffice. You can check out the tutorial page on our website for information on getting started.
-
Your OP suggests that the raw data you were receiving is wrong thus I need to know if both 1) the MetaWear app and 2) the sample code from the documentation work with your accelerometer and Android device. Assuming, both are reporting the correct r…
-
* Does increasing the delay time fix the problem? What is the smallest delay that causes this issue? * What is your device model and Android OS that you are using? Manually issuing reads every 1 second should not cause any Bluetooth related issu…
-
* Does the accelerometer function as you expect with the sample app? * Does the sample code given in the documentation work? * What exactly is wrong with the data on the Android side? Is the data being is off by +1g the only issue? The sample cod…
-
@kuubusYes, it appears that something has changed with the interrupt handler, possibly in the attempt to fix the acc/gyro/mag compatibility. I'll let the firmware guy know to look into it.
-
The max voltage on the GPIO pins is 3V so I don't see why this specific optocoupler wouldn't work with the MetaWear. You can use the GPIO module to set or clear the dout signal.
-
If you're developing a Windows Universal app, then the C++ calls are pretty much the same as the C# calls. If you're on *nix, then you'll have to use the bluez library and unfortunately I'm not that familiar with using the bluez library.
-
It will be released in the next iOS update.
-
Yes this is possible. You can use the settings module to control the ble advertisement. However, the board cannot initiate a btle connection so your mobile device will have to periodically perform btle scans to see if the board is connectable.
-
If you're developing on Android, then you can change the power preset to high accuracy.
-
Firmware v1.2.1 was released to address this issue.
-
Can you elaborate on what you trying to accomplish? What sensor specifically are you looking at?
-
No, metawear is a Bluetooth LE platform.
-
@maged I pushed a bug fix to address the pin monitoring, commit 3648fbf0.
-
Firmware v1.2.1 has been released to address the "missing" accelerometer bug on C and CPro boards enabling them to safely use the v1.2.0 firmware. The thread about this bug is here.
-
The default firmware does not support time granularity smaller than milliseconds. Even if the firmware supported this, Bluetooth LE is not designed for high frequency data streams and the logger will be full within a matter seconds. For your …
-
You might be ok with using only accelerometer data: acc_z = cos(Θ) acc_y / acc_x = -tan(φ) where φ is rotation around the stationary z axis and Θ is rotation around the stationary y axis. If you need something more accurate, then you'…
-
The gyro reports angular velocity in degrees per second (°/s). For example, if you get (t, x, y, z) = (3, 1, 4, 1) , then it means at time = 3s, the sensor was spinning around the x-axis at 1°/s, y-axis at 4°/s, and z-axis at 1°/s.
-
We discovered an issue with starting up the accelerometer on C and CPro boards with firmware v1.2.0. There is no reason to be using v1.2.0 unless you have an environment or detector boards; you should rollback to v1.1.3 until we get a fix out. Do…