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, try reducing the sampling frequency to 2Hz (500ms). No, reading the analog input doesn't seem to be the problem but rather the frequency at which it is read. 30Hz is overkill if the sensor only changes between 1-2Hz.
-
What device and OS are you using the MetaWear board with? How long does it take until this issue occurs? Try using the MetaBase app to stream data instead. https://play.google.com/store/apps/details?id=com.mbientlab.metawear.metabase&hl=en
-
@aribesPost the code you are currently running
-
The MetaWear app needs to be updated to use the latest Android SDK, which addressed a bug with connecting to boards in the MetaBoot state. Change your app flow as I suggested in my previous post and make sure your device cleanly disconnects befo…
-
See the last section on the Troubleshooting page about the exchange process.http://mbientlab.com/troubleshooting/ It does appear your board is DOA.
-
The Android example apps use a separate library to handle the BLE scanning and UI elements.https://github.com/mbientlab-projects/BleToolbox You can try resetting the BT adapter to see if that helps however, as already stated, the only thing to …
-
What sensor are you attaching to the GPIO pins? The MetaWear app samples at 30Hz so you may want to try reducing the sampling frequency.
-
Looking at the spec sheet, the count can only be between 1 - 4, which the API apparently does not enforce or mention.
-
Stream the limiter, not the source. source.limit(100).stream(...)
-
Post the full code you are running. You may also need to tweak the ble connection parameters as outlined in this post. http://community.mbientlab.com/discussion/comment/3825/#Comment_3825
-
Is this only an issue with the Android apps? Does the gyro work as expected when using the iOS apps? Have you tried resetting the board or reflashing the firmware? How were you using the board prior to seeing these issues?
-
It looks like the board doesn't actually disconnect in the onDestroy function. You can try to reverse the app flow and only leave the activity once the board has disconnected.
-
Those status codes are internal codes returned from the BlueDroid C code. As mentioned in the linked thread, there isn't much you can do except try again and/or reset the Bluetooth adapter.
-
Hrm, does the magnetometer work? Try updating the firmware and see if that resolves the issue.
-
I don't have any issues with Android Studio 2.3.3. Do any of the tutorial apps work for you?https://github.com/mbientlab/MetaWear-Tutorial-Android
-
* What are the errors you are seeing? * What are your iOS and xcode versions?
-
As far as I am aware, you cannot connect by MAC address on iOS.
-
It would appear so. As Matt mentioned, MetaWear's I2C module doesn't play well with devices that do not follow standard I2C conventions.
-
Whatever libstdc++ library being loaded by default is incompatible with the version that was compiled with the metawear library. https://stackoverflow.com/questions/16345590/ldd-says-library-isnt-found-by-compile-completes-successfully
-
Since we didn't hear from you on a forum til now, I had answered the original github issue.https://github.com/mbientlab/MetaWear-SDK-Cpp/issues/14
-
Mixing two different APIs is not a good idea, stick with one or the other. If choosing the C# SDK, try using the start app from the tutorial solution to read the register from the BMP280 sensor https://github.com/mbientlab/MetaWear-Tutorial-CShar…
-
I suppose the simple question is, are you sure the batteries are completely demagnetized? I've also let the hardware engineer know to look at this thread.
-
Hrm, in that case, it could be a fw issue but we'll have to debug further. For now, just use the normal accelerometer data if you need to control the data rate.
-
Try the example I2C code in the documentation. https://mbientlab.com/csdocs/latest/serial_passthrough.html#i2c If that works, then it does appear that the RPro boards cannot talk to the VL6180X with its 10-bit addresses.
-
I've notified the iOS developer to checkout the issue mentioned in this thread. In the meantime, do you have an Android or Windows 10 PC you can try using the boards with?
-
No, you cannot do both simultaneously.
-
The BMI160 has a step counter built in to the sensor so you can simply query that value. Yes, you can stream the data through the bluetooth link.
-
Does it properly work if you remove the time limiter? You should also add error handling in the Continuation to check if the addRouteAsync task faulted. As a last resort, reset the board and try streaming quaternions from the MetaBase app. htt…