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
-
* [Logging] Sample at lower frequencies * Use the accounter to mark the streamed data How long are you collecting data for?
-
@fryjs said: The iOS MetaBase app (latest on the appstore) tries to update firmware to the MetaMotion R, but just sits there saying "Updating Firmware" without ever doing it. The device never switches to metaboot. Is this not supported by …
-
var value = data.Value();
-
The calibrate state should be polled until it the sensors report high accuracy. We are adding a function to stramline this process, but you will have to do this manually for now. Modify your code so it does the state polling and post the result …
-
Test with a data source that has configurable frequency, like accelerometer. Due to how data is arranged, you'll want to combine it with gyro data to get the transmission frequency as close to 100hz as you can. acc @ 200h, gyro @ 100hz. What …
-
@Teddybee said: Good afternoon, I would like to collect hi speed data from accelerometer and gyro (as fast as possible). As I read the documentation when metamotion logging, it saves the data into the rom. Max logging capacity of the devic…
-
* What iOS API version are you using? * Does cleaning and rebuilding the project fix the errors?
-
The best way to have accurate timestamps and avoid huge data gaps is to log the data.
-
Try with 15ms.
-
Easiest way is to plot it.
-
Hrm...not sure what could be wrong. The gyro should be the first one to reach high accuracy calibration and fairly quickly too. Does the accuracy ever change?
-
Yes. Download this firmware image and upload it to the board with the DFU button. https://mbientlab.com/releases/metawear/0.1/6/vanilla/1.4.4/firmware.zip
-
* Where should I be looking in the CSV files for the data loss? * Yes, I know you were using the windows app. That does not fully answer my question. I need the steps to reliably reproduce the issue. * That version of MetaBase is only for MetaHu…
-
Those are the UUIDs not the characteristic values. I need you to read them.
-
Your script hasn't caused any issues so far in my Linux VM. I haven't been able to test on our Pi yet but will do that soon. @donald_cascom said: @Eric I have started to look into some possible workarounds as well as attempt to further nar…
-
Yes it's possible
-
Read the values of the requested characteristics.
-
@Eric said: You will need a MeraMotion C board instead or the version 0.5 of the MWC hardware I don't know how many 0.5 MetaWear C are left in stock. Fill out the contact form stating how many you want to purchase. If the order is not h…
-
@pwwooldridge said: @Laura said: @pwwooldridge, Please don't update firmware via our Python script/example. We have actually removed the update_firmware.py script from the Python repository. You can only update…
-
The board should exit metaboot mode on its own in 60s. If not, connect to the board with the nRF Connect, then post the hardware and firmware versions and the model number under the "Device Information" service.
-
@Ben said: I need 30s + of high speed data from gyro, accelerometer and fusion, at 200 samples/s, so streaming is not an option. I would like to also have some low-rate (20 samples/s would be sufficient) streamed data from the sensor to confirm…
-
The boards are Bluetooth Low Energy, not classic Bluetooth. Aren't Beats by Dre a classic Bluetooth headset?
-
v1.4.4 is not supported on that version of the MetaWear C boards. You will need a MeraMotion C board instead or the version 0.5 of the MWC hardware. I will update the announcement post to include that information.
-
The underlying issue is with how the libblepp library is used. We are still looking into it.
-
* Can you stream data from each device individually? * Can you stream from both devices if you stream at a lower frequencies? * What are the the hardware, firmware, and model number of the boards?
-
@donald_cascom said: @Eric - did you get a chance to look into this further? No, I have not been able to debug this further.
-
* Post data showing the data loss * What do you mean by "tested MetaWear R"?
-
Ok, in that case, the behavior you are describing does not sound normal. Ttry increasing the tx power to 4db. https://mbientlab.com/androiddocs/3/settings.html#ble-advertising Do you have other boards to test with?
-
I only asked you to update the firmware. Follow my instructions exactly; do not any more or any less.
-
Yes, the empty check should happen since the disconnect handler clears the pending_fns queue. Thanks for bringing that up. We'll add that in the next release