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
-
Did you ever remove previous macros?
-
No, those other devices should not cause the reported behavior. It would make sense if the board lost connection but you say that is not the case. What are the firmware and hardware versions of the boards?
-
* What is the hardware revision of the boards? * Post a minimal script that reproduces the issue. * You can use MetaBase to revert to back to v1.4.1 I haven't seen any connection issues with the v1.4.2 firmware with this simple connect script:…
-
How far does the script progress before it stalls?
-
No, it means exactly as stated. The second quote is a typo, should be "sensor fusion algorithm" and has been corrected in my previous post. Post unrelated questions in their own thread.
-
Calibration state refers to the same accuracy values used by the corrected IMU data. https://github.com/mbientlab/MetaWear-SDK-Cpp/blob/0.16.3/src/metawear/sensor/sensor_fusion.h#L16#L19 It doesn't matter what sensor fusion mode you select. The…
-
What do you mean by "handle Android Wear"? It can be a component in a smartwatch but all it will provide is sensor data.
-
You can't shared serialized states across different languages. Instead, use anonymous data signals: https://mbientlab.com/cppdocs/0/advanced_features.html#anonymous-signals
-
As stated in the macro documentation: The on-board flash memory can also be used to store MetaWear commands instead of sensor data. And timer documentation: The Timer module schedules tasks to be executed periodically on the boar…
-
I'll have to look into the NPE more. Regardless, use the Timer class to schedule period reads, especially if you are doing them that frequently: https://mbientlab.com/androiddocs/3/timer.html
-
No, the firmware does not send synced events. I highly doubt that your sensor fusion library will be impacted if the data is synced in the app vs by the firmware.
-
How are you using the device? Is the device simply disconnecting, or is it resetting / running out of power?
-
No, that property does not exist. Have your app store the mac address of the devices it has configured.
-
Try changing the ble connection parameters after you have connected to the remote device: https://mbientlab.com/csdocs/0/advanced_features.html#high-frequency-streaming Do you experience the same issue when you were using the older releases? Ho…
-
Issue being resolved on GitHub. https://github.com/mbientlab/Warble/issues/4
-
Does the same behavior occur when using the MetaBase app? Post the relevant portions of your code so we can see if anything is wrong with your SDK usage.
-
* It doesn't matter, do the physical motions demonstrated in the video for each IMU. * It means exactly as stated; when the device is powered on, start the sensor fusion algorithm then calibrate the sensors before you collect the data. Calibrati…
-
Tesla
-
Read the documentation: https://mbientlab.com/androiddocs/3/sensor_fusion.html#calibration About the firmware update, quoting myself from my previous post @Eric said: When is the calibrate function called? What code is executed before …
-
Watch the sensor fusion calibration video linked in the documentation: https://mbientlab.com/androiddocs/latest/sensor_fusion.html#calibration
-
Configure and start the sensor fusion algorithm before you read the calibration state.
-
use mbl_mw_logging_clear_entries. MetaWear.mbl_mw_logging_clear_entries(device.board) MetaWear.mbl_mw_debug_reset_after_gc(device.board) MetaWear.mbl_mw_debug_disconnect(device.board)
-
* No * It is exactly as stated, there isn't more to say about it. The method you are talking about in your first question is how you use it. * No * Calibrate the sensors before collecting data.
-
When is the calibrate function called? What code is executed before calling said function? The sample DFU code in the Android documentation should iterate through the list of files to upload with 1 function call. It is extracted from the MetaBa…
-
Did you install the latest release (v0.2.0 as of this post)? If so, try deleting the node_modules folder and reinstall.
-
The update npm message comes from npm, it is not a MetaHub message. Regardless, I have not run into any issues when updating npm so I can't address your specific issue. Next time, record the commands you run and their output, and post errors you e…
-
@jimjam said: First of all, some movement from the Unity folks. We're made it through QA at least: https://fogbugz.unity3d.com/default.asp?1065590_p5vr9ftohapf1apf Although that does not necessarily mean they'll fix it. I've followed up wi…
-
* I do not have issues using MetaHub with firmware v1.4.1. Does the MetaBase app on you Samsung work with the board? * Probably next month. * Yes, you should always be using the newest firmware.
-
That type is defined in the Python bindings file: https://github.com/mbientlab/MetaWear-SDK-Cpp/blob/0.16.3/bindings/python/mbientlab/metawear/cbindings.py#L460 The Makefile sets the PythonPath env variable to point the appropriate so it should …
-
Did you tell them the board bricked during the update to firmware v1.4.1? Fill our the RMA regardless, support needs all the information they need to verify the issue.