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
-
Start with a simple macOS application that uses CoreBluetooth to connect and discover BLE services. Test that your app works with your MetaWears. No, there is no plan on releasing a macOS version of MetaBase.
-
What you are describing sounds like normal behavior. The graph zooms to where you started dragging your fingers, which should result in the origin being moved out of the window.
-
Run git pull in the MetaBase folder. v1.2.0 is the current version.
-
What sensors are you using and how fast are they streaming?
-
* Can you connect to the board in the diagnostic page and view the device information? * Does the board work with the Android or Windows version of MetaBase? * Do you have other boards to test with?
-
You're running the most power hungry sensor (gyro) and using sensor fusion. Either disable sensor fusion and run the gyro at a lower data rate, or attach a bigger LiPo battery.
-
That question had already been answered in the other thread you posted it in.
-
No, that won't save battery. What sensors are you running and how fast are you sampling them?
-
* What do these test entail? * How are you running the tests? * Do the boards work with the MetaBase app? * Use with nRF Connect to see if the boards are disconverable and can be connected to
-
Run the command multiple times with different NOBLE_HCI_DEVICE_ID values.
-
* What OS are you using? * Do your adapters support Bluetooth 4.0? * Are you connecting with the MetaBase app?
-
Try using the nRF Connect app to connect to the problem board and read the device information characteristics: https://play.google.com/store/apps/details?id=no.nordicsemi.android.mcp&hl=en_US
-
@marieesc said: Hello Eric, We have started to test on a higher transmission power of 0. What was the default transmission power before? Also what does the 4 value mean in terms of transmitting data would that make it more stable? …
-
* Hrm...based on the log files, it looks like the crashes are occurring when you are trying to connect to the board? * As you were also building your own app, post the relevant code from the app and what exception was thrown when it crashed. * Wha…
-
Use the generic Windows 10 BT drivers then.
-
You previously said that MetaBase works without BlueSoleil. We're you using another adapter to test? If not, then I'm confused as to why you then stated the adapter in question only works with BlueSoleil.
-
What if you uninstall BlueSoleil?
-
Look at the scripts I linked in my previous post, and read the documentation: https://mbientlab.com/cppdocs/latest/index.html
-
* What is the hardware and firmware revision of the boards? * What Bluetooth adapter is your windows machines using? * MetaBase creates log files, store by default in "$user_dir\Downloads\MetaBase\Log". Post the log of one of the crashes. * Can …
-
How are you currently syncing files to Google drive? Post the relevant portions of your code.
-
I have never had good BLE experiences with the Moto G, though in my case it was 2nd gen. The iPhone issues are interesting as we've always had good BLE performance with iOS devices (both phones and tablets). This does suggest however, that your mo…
-
We haven't had any issues using the dongle on Linux. Use the MetaBase app to test your board, not 3rd party Bluetooth software that may or may not properly work.
-
Mix the RGB base colors to create new ones.
-
Python is not supported on iOS. You will need to either use JavaScript or Swift, or switch your platform to Windows 10 or Linux. Look at the example scripts: https://github.com/mbientlab/MetaWear-SDK-Python/blob/master/examples/multi_device.py
-
pip is an executable, not a Python function.
-
Reduce the max connection interal to 7.5ms before starting the download. See the 2nd paragraph in the documentation: https://mbientlab.com/cppdocs/0/advanced_features.html#high-frequency-streaming
-
You don't need to use anonymous signals unless you want to download the data to another device. Anonymous downloads work with all signals. Post your code and any errors you are able to capture during the crashes.
-
This is explained in documentation I linked to in my first post.
-
Yes, when the device powers on. You should also check the calibration state every time you start sensor fusion.
-
No, we have not encountered this specific issue. As I have previously asked: * Do you see these same issues if you are using an Android or another iOS device? * What iOS device(s) are you using in your tests? * Are you 100% sure that …