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
-
What phone and android model are you using, and what is the distance between your phone and board? On my Nexus 5 running Android M, I can stream 50Hz reliably granted my phone and board are very close to each other. For higher frequencies or fu…
-
@Dom_Crispi You need to make a new thread with your question; your post is completed unrelated to original poster. Furthermore you'll have to provide more details about your problem. What have you tried so far? Which datasheet are you referring…
-
50Hz each should be ok, 25Hz to be safe. You should try to keep the total amount of data sent to around 100Hz.
-
As mentioned in your previous thread, the btle connection interval limits how frequently data exchanges happen between the mobile device and the board. Unless you are connecting to an unknown board, your app should know what settings were used to c…
-
Bootloader mode is for performing firmware updates. There is no recommended way to do board resets other than connecting to the board and issuing the command manually through the API. Resetting the board is for the development stages of programmi…
-
Nope, nothing special for mbl_mw_gpio_start_pin_monitoring. I'll double check the implementation to see if anything is out of place.
-
The scheduleTask function is only for scheduling MetaWear commands to execute on board. Any function not a part of the MetaWear library is not a MetaWear command. Given how you are using the i2c module, I would use Android's Handler class to perio…
-
Holding the button down on boot is a built in method to force bootloader mode.
-
What is the full code you are executing in scheduleTask that does not work and what does the working code look like? I don't understand why you are storing the result into auxvar when you want to update the chart upon receiving new data. You shou…
-
You need to tell the board to stream data and setup a handler for the data. If you haven't already, please read the section on sensor data on the C++ api wiki:https://github.com/mbientlab/Metawear-CppAPI/wiki/API-v0.3.0-How-To#sensor-data You …
-
Wow! This is a very detailed guide, going beyond just a HowTo for MetaWear. The guide looks pretty solid to me; I only have two nitpicks. First, you can stream and log the same signal. As you mentioned, its not a recommended use case but neithe…
-
Not on the current firmware. We may look into ways to increase the throughput by utilizing the full 20 byte payload so you can get more data per response but that is not a high priority item at this time..
-
As I said in the other thread, this is not possible on vanilla firmware. Either you reprogram the board after the DFU, or you can contact us about building custom firmware for your device.
-
I would define the wrappers in the C# class that is using them. The provided C# wrapper files define the enums and structs for the various library functions. For example, if my MainPage class were using a gpio function, I would place the wrapper …
-
Code works fine for me. Did you start the sensor?
-
You are holding the button down too long, which causes the board boot into bootloader mode. The button should not be used to trigger resets for this reason.
-
The numbers correspond to how fast (angular velocity) the sensor is spinning around the XYZ axes (pitch, yaw, roll). The greater the magnitude, the faster it is spinning.
-
Just have your app set the device name back to what you want after the firmware update succeeds.
-
It just means that given a correct address, the I2C read is working in the Android API. I'm not really sure where to from here so I've let our hardware guy know of this thread; he can provide more assistance with the I2C sensor.
-
* How are you connecting the button to the board? * What kind of trouble are you having with your setup? * What have you tried so far? Assuming everything is connected properly, did you set a pull mode on the data pin?
-
That gist is for an older MetaWear API. The equivalent of that code is given in the Android Documentation sample code: https://mbientlab.com/androiddocs/#dataroute
-
Unfortunately no. Doing a firmware update clears the flash memory which will remove any data stored there (i.e logs or macros).
-
I'm looking into publishing on NuGet (haven't gotten around to setting everything up). In the meantime, you can make a new Universal app and copy the files and settings. The C++ API README lists out project properties that need to be changed to c…
-
You can check out the MetaWear C++ API GitHub page for how to information. https://github.com/mbientlab/Metawear-CppAPI/wiki/API-v0.3.0-How-To Are you planning on doing your whole project with C++? I have only used the C# Btle functions but I su…
-
I2C is on all the boards. Since you have a CPro board, try running this code snippet to see if I2C is setup correctly. The code reads the ID register on the BMP280 chip and should return 0x58. i2cModule.readData(0x77, 0xd0, (byte) 1).onComplete(…
-
The same code works for a Windows 10 universal app. The wrapper project itself is for C++ API v0.2.2 though so you will need to update the DllImport calls accordingly if you want to use API v0.3.0.
-
What board and firmware version are you using? There was a bug in firmware 1.1.0 (fixed in 1.1.3) where the above code snippet would not work.
-
Dropping the dice on a table will produce a spike in the acceleration. You could detect a spike in the acceleration sample (either XYZ, or perhaps RSS).
-
You cannot reliably stream data faster than 100Hz over a Bluetooth LE connection. If you want a higher ODR, you must log the data. The sample app streams at 50Hz.
-
We're in the process of updating the APIs and firmware to properly support the MetaWear env boards. Also, the env boards only have an accelerometer; they do not have a gyro.