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
-
Ah sorry, the Android API needs a minor update to accommodate firmware v1.2.5 changes which will fix this issue.
-
I tried writing 0xff to a few of the on board sensors via the I2C bus and didn't see any issues. On an R board, I wrote [0xfd, 0xfe, 0xff] to the XYZ offset registers on the MMA8452Q chip then read them back with no problems. i2cModule.writeData(…
-
If you have compatibility issues with the latest firmware, you need to tell us rather than silently reverting back to previous firmware versions. I can add in a function to the API that will download a specific version as opposed to always grabbin…
-
Is that IS_64_BIT section necessary when using the python wrappers provided in v0.5.0 and later? The functions.py file assigns all pointer types with the c_void_p which should also address the invalid pointer addresses we saw 6 months ago on 64-bit…
-
Your reference values need to be in units of g's, so it should be 0.7 not 700.
-
Sorry, I haven't had a chance to look into the issue any further.
-
The guide was removed as we no longer provide support for custom firmware. That is, you can create your own firmware but you are on your own if you choose to do so.
-
Do you get the same results of you are using the MetaHub app? What's the code you are using to enable the stream? I tested an RPro board last night running firmware 1.2.5 using the Windows app and the # of samples collected only differed by 3 and …
-
You will never have reliable timestamps when streaming data via Bluetooth LE due to the sensors pushing out data faster than the devices exchange data through the BTLE connection. The 6-axis IMU on the CPro produces data at very consistent interval…
-
Which version of the Android app are you running?
-
Unfortunately it is not possible with the current API. The API will always retrieve the most recent firmware available and we recommend that users use the latest firmware.
-
Since you're using the latest firmware, I presume that reading the battery through the Settings module also produces the same result? Also, Laura will follow up with you regarding this issue.
-
What happens if you update anyways?
-
How odd, are you able to at least start the DFU or does the update attempt fail at the firmware version check? Also, what is the hardware revision of the board and what Android OS and device are you using?
-
* What firmware version and board are you using? * What app version, iOS version, iOS device model are you running the app on?
-
What does the IDE show as valid functions when you attempt to use the MBLGpioPin object?
-
no, the current firmware will run for the allotted time.
-
Check the documentation for MBLGpioPin (iOS api v2.7.2).
-
* What android OS and device are you using? * What firmware are you running? * Does the same issue happen if you use the nRF Connect app?
-
Is the only issue with the 0% board the always 0% battery level i.e. everything else works just fine? Also, what API calls are you using to read the battery level?
-
Does the multimw app work as is? Assuming it does, then the problem might be with how the app is communicating with the boards. Please post your code so I can better understand what is going on in your app.
-
Ah my apologies, I completely missed the pastebin link. I'll try to create an equivalent test case with what we have in the office so the firmware dev can look into it further.
-
None of the code in the link subscribe to a single axis, which is what leihaiyong's code is doing. The code snippets apply data processors and subscribe to the output from a processor.
-
The I2C bus does not handle asynchronous data; data will only be send if explicitly read.
-
iBeacon simply uses the BTLE advertising feature to broadcast its own advertising packets in place of the standard btle ad packets. There is no difference in power consumption.
-
Install the Android support libraries
-
https://github.com/mbientlab-projects/MetaWearTutorial-Android/tree/master/multimw
-
Another user was able to setup bindings for Xamarin. You can check out what he did in this thread.
-
I updated the freefall tutorial to use the newest Android API (v2.6.5) which addresses the logging issue
-
Can first you check with the metawear app that the magnetometer is functioning correctly just to ensure that the board is working?