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
-
yes, that should be 10 microseconds, thanks for the heads up.
-
I've let the iOS dev know about this thread and we'll look into it.
-
Ah that is correct, removing a route before the log download will cause the unknown log entry to be fired.
-
1) On Android and Win10, all received data is immediately written to disk so you can manually retrieve the files later. 2) As long as both devices are running the same OS (Android / Win10), it is possible to start recording on one device and downlo…
-
You can only poll data from one pin at a time however, you can configure other pins by editing the pin field before using the other GPIO settings.
-
No, we do not provide sensor fusion code for standalone applications though you can try the libraries mentioned in this post: http://community.mbientlab.com/discussion/comment/3556/#Comment_3556
-
* What boards are you using? * What sensors are you recording and how frequently are you recording data? * What iOS device and version are you using?
-
C++ API v0.7.14 is available, see first post for details.
-
Can you post some data of the different throws?
-
The unknown log entry error function is executed if the API receives log data but doesn't know which route to send the log data to. This typically happens if you connect to a board that already has an active logger or you rebuild a route before rem…
-
Thanks for sharing the code with the community.
-
No, any device can connect to the board once it is advertising.
-
This post might solve your Linux issue. http://community.mbientlab.com/discussion/comment/3647/#Comment_3647 Initializing the API is always the first thing to do so after calling initialize. I used 16G for acc range but everything else is the…
-
Implement the failure function in the CompletionHandler object and log the error message if any is received. The code you have looks fine to me so the error could be from somewhere else.
-
What are you trying to achieve with the data processing? Depending on what you want, it may be better to gather the raw sensor data and post process it with a more advanced data processing library such as numpy.
-
Closing the app destroys API state; you need to serialize the state before closing the app and restore it prior to downloading the data. Checkout the example from this blog post: http://www.polyglotprogramminginc.com/logging-thermistor-data-with-…
-
* The IMU can measure motion on the order of inches. Be aware that MetaMotion boards cannot directly communicate with each other and don't have any proximity sensors so relying on solely IMU data may be an impossible task. * Check out the tips outl…
-
The demo iOS sensor fusion apps collect raw sensor data perform sensor fusion on the iOS device using an external library. MetaMotion boards have a sensor fusion algorithm as part of the firmware and do the computations on-board.
-
I am able to stream raw acc / gyro (100hz each) along with quaternions (25Hz) without any issue on Android. Try reducing the max connection interval to 7.5ms before configuring the board.
-
We do not have a i2c scanner. Based on the example java code, you try using 0x76 for deviceAddr, and 0x0 for registerAddr.
-
Use the sample app to see a real-time graph of measured acceleration on the xyz axes and move the board up/down & left/right to see which axis responds to what motion. These values depend on the sensor orientation which differ among the boards.
-
Sensor fusion is only available on MetaMotion boards.
-
The code works fine for me. Are you using a metamotion board?
-
Sensor fusion output does not support high frequency streaming so you should stream raw acc and gyro data, and use time processor to reduce quaternion to 25Hz.
-
* There's no direct way to check; the simplest way is to remember which boards have been programmed using sharedpreferences. * Loggers are removed when their owning route is removed. The switch differs from other sensors in that there isn't a "stop…
-
C++ API v0.7.10 has been released, see first post for details.
-
Ah yes, that is a mistake in the code using the wrong hour formatter. We'll address that in the next MetaHub update.
-
No, the spec sheet states that the device address is in the form 1110110x where x=1 for read and x=0 for write, not the address is 0x76.
-
The C++ API does not yet correctly configure the time filter for use with sensor fusion output. We are working on a small update to address this and a few other bugs.
-
My apologies. you are correct in that your code did compute velocity with the average velocity equation. Some more poking around yielded these threads on SO: http://stackoverflow.com/questions/12926459/calculating-distance-using-linear-accelerati…