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
-
Doesn't look like you are writing to a valid path. Use is_open to check if the fstream is currently opened for file operations.
-
The third beta release of the v3.0.0 API is available, adding support for firmware v1.3.2 features and refactoring parts of the API. This release introduces breaking changes to the interfaces and MetaWearBoard serialization so you will need to upda…
-
Universal Windows apps can be run as both a desktop or mobile app.
-
@mgeorgi Try api v2.8.0
-
The command format is not explicitly documented. Support for other languages is done by either building on top of the C++ API or looking at the API code and unit tests, as done by the authors of the NodeJS API. What features do you need support…
-
Hrm..ok. I'll address this in the next API update
-
MetaHealth board? Or do you mean MetaWear C? Hrm, this is an odd behavior given that everything was working before. Can you try re-flashing the firmware with the MetaWear app and using a fresh coin cell battery?
-
Unfortunately we have not seen an issue like this before. One more question, did an iOS device see the board when doing a scan?
-
* What type of board are you using and what firmware is it running? * Where you only using the MetaBase app the entire time?
-
the flash memory is cleared after a log download
-
If I'm not mistaken, you can simply compute the cross product of two quaternion values at different points in time.
-
The sensor fusion code is proprietary software licensed from Bosch, not our own solution. For the moment, your best bet is to use an open source sensor fusion library, however, having the sensor fusion run independent of the MetaMotion firmware is …
-
The gyro reports degrees per second which can be easily converted to revolutions per second (1 revolution = 360 degrees).
-
Sweet, thanks for the NodeJS update.
-
How are you using the board prior to seeing this advertising issue?
-
Does the same error occur if you are building the non-beta variants of the projects? I am currently using Android Studio 2.2.1, so also trying updating the buildscript's classpath attribute to "2.2.2".
-
What android device are you using and do you see the same gatt error when using the nRF connect app?https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp&hl=en
-
Unfortunately I am not seeing this issue with both a C and CRPO board. It seems like your board is resetting while in iBeacon mode. To check this, program a macro that turns on the LED when the board boots.
-
What i mean is what is the code that is checking the device disconnected and what code is checking that the connection has been restored (or not).
-
Reduce the max connection interval to 7.5ms (11.25ms if using Android M or later).
-
The crash was an issue with the starter project that has been fixed with the commit a08ccda. Update your fork with the latest changes on the master branch.
-
A second beta of the v3.0.0 API has been released which adds Macro support to the API. Full release notes are on the GitHub page. https://github.com/mbientlab/Metawear-AndroidAPI/releases/tag/3.0.0-beta02
-
An update to the app (V1.1.4) has been pushed to the Google play store.
-
This has been fixed in the v2.7.2 API.
-
Released v2.7.2 to fix a null pointer exception, see OP for details.
-
What code are you using to test this?
-
http://community.mbientlab.com/discussion/1888/unable-to-connect-after-unexpected-application-closure#latest
-
Take a look at the unit tests for the C++ API or the Android v3.0 beta API.
-
Both are true
-
Generally speaking, a watchdog is a piece of code (or hardware) that monitors the system for specific issues.