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
-
Please email us directly (CC me) and attach pictures of the board. We may need to take a look at board with our equipment if we can't discern the issue(s) from the images.
-
You need to use the high frequency streams (for both acc and gyro) since you are attempting to sample both sensors at 100Hz each.
-
For a MetaWear R board with that old of a firmware, try using an older app to do a DFU. You can download the v2.5.12 APK from our GitHub release page. The DFU option is a menu item located in the drop down menu on the action bar. Once the DFU act…
-
Try putting the board in MetaBoot mode (press the button then power up the board) then reconnect to the either app. Once connected, attempt a firmware update.
-
Are you using the metawear app to stream the data? If so, the apps already write the data to a CSV file.
-
* How long is a 'period of time" in your use case? * Are you streaming acc and gyro both at 100Hz? * Please post the exact code you are using to stream data
-
Given that you mentioned keeping out water, did you submerge the enclosure in water? What exactly was the board subjected to over the previous 5 weeks?
-
ADC values do not have units as they are simply a ratiometric number.
-
I haven't had any issues with Nexus 6 (Android M) or 9 (Android N). We test the boards across a variety of devices such as: * Raspberry Pi * Nexus 6, 7, 9 * Iphone 6, 7 * Samsung Galaxy S4 and S4 mini * BLU Win HD LTE (Win10 Phone) * Zenbook l…
-
Haven't had any issues using either a Nexus 6 or 9.
-
The API & documentation will be published when they are ready.
-
Assuming you are using GPIO pins, 0 - 3V.
-
What is the model number and hardware revision of the bricked boards?
-
You mixed up mbl_mw_acc_set_odr with mbl_mw_acc_bmi160_set_odr at line 220, assuming you are using sample_rate_param instead of sample_rate.
-
Sorry, I'm not sure what that piece of code means or how it is related to the Android API.
-
You don't need the Debug class if the board is already in MetaBoot mode; use the API to download the latest firmware and pass the downloaded file into the Nordic DFU library. The MetaWear app already handles this case so you should be able to just …
-
What changed between now and before?
-
The Motion R does not have the hole that the RG and RPRO have; that area is now occupied by the 8MB NOR flash chip. The physical dimensions are the same as the RG and PRO boards. The first image on the store page is the Motion R board. whereas th…
-
You can still call them after your re-establish connection.
-
The data is send in bursts rather than on creation resulting your receiving the data in bunches that have nearly identical timestamps rather than evenly spaced timestamps. You can image the butter queues up 1 by 1 then is dequeued in chunks. In t…
-
What Android device are you using i.e. Nexus 5, Moto G, Galaxy S7, etc. If you only record one sensor at a time with MetaBase, which sensors do work with the app? And, just to be clear, everything is fine when using the MetaWear sample app?
-
No, we only support the recommended operation modes as outlined in the documentation, enumerated in the aforementioned powerPreset property. The accelerometer and gyro cannot be directly sampled at 20Hz directly. You can use periodic sampling to …
-
Every "enable*" and "start*" function has a corresponding "disable*" and "stop*" function respectively. All you have to do is call the inverse functions of the enabled sensors.
-
Please check out this post from one of the firmware devs about packing acc/gyro data together and time sync. Again, knowing the sampling frequency and start time is sufficient enough to reconstruct the actual timestamps of the data and combine data …
-
Can you forward this issue to MbientLab support via the contact form? Please also include a picture or video of the hardware issue with your message. Thanks
-
* What Android OS and device are you using? * What firmware is loaded on the boards? It sounds like your device cannot maintain a stable connection with multiple devices. Check that the app properly works for 1 board, then try 2, 3, etc.
-
Not directly. You can change the powerPreset property which does modify frequency but only when using the high accuracy preset (20Hz). The other settings still use 10Hz.
-
As stated in the documentation, a monitor should only contain metawear functions as it is programming the board to react every time new sensor data is available. If you want your android device to react instead, you need to stream the data to the d…
-
Because you casted the value as a short, see:https://mbientlab.com/androiddocs/latest/accelerometer.html#acceleration-sampling
-
Can you post your code? It sounds like you have setup logging but did not remove them before restarting your app resulting in accelerometer data being logged twice on board. The received_unknown_entry callback function is only called if the API d…