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
-
The BMI160 chip only reports angular rotation rate. You can integrate the rotation rate using the on-board data processor, take a look at event filters, http://mbientlab.com/iosdocs/#e-filter.
-
Yes, the firmware supports on-board data processing and offline logging. You can read about how to use these features on the iOS docs page, http://mbientlab.com/iosdocs/#events.
-
* The gyro measures rate of rotation around the XYZ axes, i.e. how fast it is spinning, in degrees per second. * How much did the values deviate from 0 when the board is at rest? There is always noise that the sensor picks up and unless there is…
-
Yes, RPro comes with a gyro. The iOS docs page has more info on communicating with the on-board sensors. Specifically, the gyro section is here: http://mbientlab.com/iosdocs/#gyro.
-
Have you charged your MetaWear? If you have another mobile device (phone, tablet, etc), does it also fail to pickup the board in a scan?
-
You can take a look at the MbientLab GitHub page for sample code and the Getting Started guide on the website. A MetaWear app is available both on Google Play and the Apple Store, just search for "MetaWear".
-
You have to create a Shapeways account to see the download link.
-
Actually, I have an alternate idea that may work better. Instead of using iBeacon mode, you can try using the settings module to to manually change the scan rseponse with the setScanResponse method. Instead of resetting the response after a delay,…
-
The MMA8452Q chip reports active movement when the device exceeds a certain accelereation which can be caused by a sudden jerk or even tilting the sensor. You can try configuring the duration (debounce) parameter in the MovementConfigEditor interfa…
-
Hrm...it could be the ibeacon module is not working properly with the activity monitor. I'll have to check with Matt with the ibeacon firmware code.
-
Stephen, our iOS developer, is still on vacation at the moment. I will let him know about your post when he's back.
-
I'll get back to you on the motion question, i have not had a chance to think about motion detection on the door motion. You can only retrieve the magnitude of the acceleration vector from the axis sampling.
-
How are you trying to cause a connection failure?
-
Does the sample code from the blog post work?
-
The api does cache information about the boards it had seen, such as what type of metawear it is. But, not sampling acceleration data is strange as it does know how to communicate with all metawear boards. Good to hear that a reinstall fixed the p…
-
What version of the iOS API are you using and what type of MetaWear boards are you using (R, RG, or RPRO)?
-
UART is something we considered but it is not high on our priority list at this time. I'd also check out the iOS documentation regarding logging (https://mbientlab.com/iosdocs/#e-log).
-
The board is always on when it has a power source attached i.e. battery or usb cable. You can connect to it with the MetaWear app and read the battery level. The 100mAh battery, from 0%, should be fully charged in at most 2 hours.
-
The logger cannot free memory while the connection is active. It appears that the log has filled up so no more data is being recorded until you drop the connection. Storing raw accelerometer data is generally not a good idea due to the sheer bulk…
-
That is correct, the chip does not report an orientation vector. The best you can do is compute rotation angles around the axis using the acceleration data but that would have to be done on your device, not the board.
-
You can download while logging.
-
The iOS / Android device is only needed to program the board to respond to your event. After that one time setup, you can disconnect the phone and let the board run on its own.. One of the main feature of MetaWear is that you don't need to write …
-
There is no sensor fusion on the board. The gyro chip only reports portrait/landscape, not orientation angles.
-
With all these unknown log entries, it looks like you are not resetting the board in between your debugging sessions, and simply tacking on more routes. Try resetting the board and rerun the code. Since you're calling accelerometerMe, remove the …
-
Your most recent code snippet showed "fromAxes()" as the source and casting the data as a float but I guess that was just a typo. Try overriding the receivedUnknownLogEntry method in the DownloadHandler and see if it is called with any unknown log…
-
Your use case seems strange to me. You are logging data, then periodically downloading it at every few seconds. This defeats the purpose of logging and it seems like you should just stream data to your device as that is effectively what you are do…
-
The R and RG have the same length and width dimensions.
-
We should back up a bit. First, do you have working code to stream accelerometer data to your device? If you don't, then you should be focusing on getting a live stream working first before you try logging. You can use the code snippets from the …
-
We just finished the Android portion of the tutorial videos which are on the MbientLab website, link here. Scroll down to the "MetaWear Advanced Programming" section.
-
Logging Documentation https://mbientlab.com/androiddocs/index.html#logging You can also check out the freefall detector app we built as part of a video tutorial.https://github.com/mbientlab-projects/FreeFallDetector/blob/master/app/src/main/ja…