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
-
Yes, you use setLogMessageHandler to handle logged data. Please post your code so we can find exactly what is wrong.
-
A C# console a[[lication is a .net application however you can call into Win32 dlls I guess there could be an issue with how the nuspec file is setup. What you can do is download the NuGet package directly and manually add the DLLs to your project.
-
There has not been any changes to the BLE code in a long time. Can you try connecting to the MetaWear using the nRF BLE app? If you see the same behaviour there, then try turning off both wifi and BT then turn on only BT.
-
What Android device and OS are you using?
-
Did you save the serialized the MetaWearBoard state and subsequently deserialize it?
-
* What BTLE radio are you using? * What boards are you using? * What firmware version are they running? * What sensors are you using? * How are the sensors configured? * What code are you using to communicate with the BTLE radio? We are busy …
-
This is a result from the board allocating too many resources. You can reset the board to put it back into a clean state.
-
No, other than the Cordova plugin still needs more work to support the rest of the Android and iOS APIs.
-
The MetaWear.Win32 package is for Win32 projects. It sounds like you are still trying to make a .net or uwp project. If you're going to make a Win32 project, you'll have to use the bluetooth functions from the Bluetoothleapis.h header file.
-
What firmware are you running and what android device/OS are you using?
-
@lgleasain manages the project and is the only person working on the plugin at the moment. Any additional community contributions are much appreciated so you should create pull requests for your changes.
-
You already have the correct code, it's just not placed in the correct location as detailed in my previous post.
-
I don't see any code that starts the accelerometer so what you have provided effectively starts the logger and then immediately attempts a download before any data is recorded. Your CompletionHandler should only start the logger and accelerometer. …
-
What does your data route code currently look like? Also, does the onFailure function return an exception when you create a date route?
-
You can try tweaking the board's connection parameters, specifically lowering the connection supervisor timeout.
-
For logging, you use setLogMessageHandler instead of subscribe. You still need to start the accelerometer and logger to log data. An easy way to check if you have the accelerometer properly configured is to stream data to your device first before…
-
Setting up a data route to log data is covered here and the following section, and controlling the logger is covered here.
-
You can try changing the connection parameters as mentioned in the post you linked or see if Android M offers better performance. Since all Android devices are different, there's not really much you can do if the BLE radio in the Galaxy Tab A does…
-
You can try reducing the connection interval to 7.5ms.
-
Sorry, seems like the docs are out of date. Use MBLAccelerometerBoschRange16G
-
There's not much help we can provide at this point; you should instead ask this question on the Parallel's forums. Again, I highly doubt that this is can't be done in a modern VM but this is better suited to be handled by the Parallel's community.
-
The blog post in the above post gives tips on how to post-process the data to synchronize the timestamps.
-
It seems unlikely that a modern VM would be unable to utilize the host Bluetooth device. You should check out the Parallel's documentation to see how to enable Bluetooth support on the guest OS.
-
What is the code you are using to subscribe to a data signal? Does the same thing happen if you use the UWP Starter project as your project template?
-
Yes, you should clean the board, remove the battery, and try powering the board by USB.
-
* Yes, through the SPI bridge. * No, acc/gyro offsets are not exposed in the APIs. * The next update will occur when the firmware is ready, sometime before the end of the month.
-
If your bridge runs Android, use the Android API. If it's running a more traditional Linux build (Fedora, Ubuntu, Debian, etc.), you can use the C++ API with BlueZ to communicate with the boards.
-
The C++ and Android API source code serve as documentation as to how the MetaWear communicates over Bluetooth LE.
-
The battery voltage looks fine. Does the board work when powered by a USB cable? It's possible the battery was not correctly soldered on.
-
How are you computing degree's rotated? Gyros are only reliable for short term measurements and will start to drift over time. You can check if the sensors are properly configured by subjecting them to some motion and verify that the recorded dat…