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
-
You can approximate the actual time of the entries after reset by treating them as offsets from the last known timestamp prior to reset. Out of curiosity, why are you resetting the board during a log session?
-
Which Linux distro are you running? The latest Python SDK works fine on my Ubuntu 16.04 and openSUSE tumbleweed VMs
-
* What version of the SDK are you running? * What board are you using? * What are the firmware and hardware revisions? * What Android devices are you testing with?
-
Please provide some data that illustrates this timestamp issue you are seeing. There is no real time clock on the device. It does know how much time has elapsed and relies on the the host device to recalculate timestamps. When connection is e…
-
Yes they are in that the function now returns a Task now instead of simply being a void function, which changes the meaning of the function and what the user expects it to do. The top level interfaces defined in the MetaWear namespace are based aro…
-
Making every function that internally calls sendCommand return a Task is not an ideal solution. The top level interface should not care about the implementation details and nor should the user i.e. the API should not be built around the assumption …
-
As stated previously, we have to be on the same page i.e. I need to be executing the functions in the same manner you are therefore I need as much context as possible. Simply providing me two code snippets with no indication of how they are used do…
-
No, the sensor fusion algorithm is not distributed as a standalone library.
-
None of those functions' implementations return a Task object. Where are you seeing that version of the code? Are these out of order writes only occurring on Android? I haven't seen these issues in unit testing and .net/uwp apps.
-
Also add this code at the beginning of the function that write_gatt_char points to: cout << "{type: " << writeType << ", value: [" << hex << setw(2) << setfill('0') << "0x" << (int)value[0]; …
-
After setting up the data route, you can dump data processor configs to check that everything was at least correctly setup. There is no publicly visible SDK method to do this but if you are up for it, you can implement a debug function to the IData…
-
A few questions regarding the code in relation to the macro -> sleep step in your test process (steps #3 and #4) * What is being run in the macroWritten callback function? * When is the sleep code being executed in relation to the macroWritten…
-
Post the code are you using to configure the board as described in your previous post. This is the first time these additional commands were mentioned so we need to be on the same page if we are to replicate your results. Also, when testing t…
-
Yes, we will look into ways to make it easier for MetaHub buyer's with the old images to upgrade. If you are comfortable with the Linux command line and want these changes now, we can send you the files you need. You can stream from multiple devi…
-
Acceleration is a 3 component vector; your graph and CSV file only show one column of values. Also, what kind of motion are you subjecting the device to?
-
The primary change is the inclusion of the MetaBase app, which is basically a command line version of the Android and iOS app that also shows streamed data in a real time graph.
-
* What exactly is the graph and CSV files showing? Please provide more context to the posted data. * What is the QQuaternion class and why is it being used with both corrected imu data and quaterion values? * Try using raw IMU data directly from t…
-
Please post a video that shows the devices being put to sleep, confirm they are in sleep mode, then being woken up via motion as described by your OP. It also sounds like the boards have other code running on them before the sleep mode command. Po…
-
Yes. See how the Python and JavaScript SDKs utilize the C++ library for DFU. https://github.com/mbientlab/MetaWear-SDK-Python/blob/master/mbientlab/metawear/__init__.py#L305 https://github.com/mbientlab/MetaWear-SDK-JavaScript/blob/master/lib/m…
-
* How many units are exhibiting this behavior? * When were these units purchased? Please send MbientLab a few of these boards exhibiting this behavior.
-
These features are only a quick fix to help you test the sensor fusion algorithm and should be considered as experimental SDK changes. Being marked "official" is irrelevant given that it does not affect your ability to use the features.
-
Transitioning to/from 0 and 360 degrees is expected; the yaw data in the second sheet looks fine. Also, your picture is not visible. The OP was experiencing jumps occurring before the pi/2pi mark.
-
The simplest way is to send us back the SD card and we can load an updated image onto it for you. Alternatively, you can also purchase an SD card with the updated image. Please contact support directly with how you want to proceed.
-
The source code and APK files are available on GitHub: https://github.com/mbientlab/MetaWear-SampleApp-Android/releases
-
Yes, using 0xffff means indefinite.
-
tearDown does exactly what it says in its comment, which does not mention anything about sensors. Whether there is a reboot period or not is irrelevant from the app's perspective, not to mention the host device's BLE stack has to register that the…
-
How are you scanning for the MetaWear device on your mac? Are you using the JavaScript or the Swift SDKs to perform a device scan?
-
* What model, hardware, and firmware revision are you running? * How are you configuring the sensor fusion algorithm? * Post data as a CSV file that quantifies this "nearly completely random" data
-
Ah, this is a bug with schedule indefinite variant. It should set repetitions to 0xffff but instead sets it to 0xff which will then stop after 63 seconds. Your modified code is the correct way to create an indefinite scheduler.
-
Can you point me to specific lines of interest? I took a quick glance at the file and noticed some pitch values going from ~4 degrees to ~176 then back to ~4.