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
-
* Do you have the sensors correctly connected to the gpio pins? This interference you are describing could be due to the sensors being incorrectly writed. * Does the same issue with gpioValue2 if you repeat the test but don't use the data route fo…
-
I did not have any issues, other than the usual connect exception, when doing some quick tests with 2 adapters. I modified the multi_device.py example to toggle between 'hci0' and 'hci1' and the script was working fine. use_snd_adapter = False …
-
The mwBoard variable operates on whatever value you assign it to.
-
You can change the connectAsync's continuation to only transition to next activity once you have the required number of connected devices.
-
No, i mean max connection interval.
-
Please post some screens that illustrate the problem you are having and post the full code. Have you taken a look at the barometer code as previously suggested?
-
The BMI160 do not provide both filtered and raw data simultaneously.
-
See this section in the documentation for high frequency streaming:https://mbientlab.com/cppdocs/0.11/advanced_features.html#high-frequency-streaming The code looks fine in terms of using multiple adapters. Can you at least stream from 2 devic…
-
Sensor fusion frequency is fixed based on the mode.https://mbientlab.com/iosdocs/latest/sensor_fusion.html#corrected-sensor-readings You will also need to modify the connection parameters if you want to stream sensor fusion from 2 devices: htt…
-
What is your app doing? If the template app is still working, perhaps something in your app is not properly using the iOS SDK. Some other users have had similar issues before, perhaps those threads can provide some insight. http://mbientlab.com/…
-
Please post the python script you are currently running. It sounds like you should split your devices across multiple dongles, perhaps 2-3 max per dongle. Also, if you have the time, perhaps running a NodeJS version of the script will yield better…
-
The timer creation also needs to be contained in the runOnDeviceBoot block.
-
Create the timed event and use the disconnect event to start the timer.
-
* In your use case, are you placing the devices in a case? * Does the same issue occur for both NDoF and IMUPlus mode? * Does doing random motions with the board, like figure 8s in the air, stabilize the data? * Is it only the yaw value that is off…
-
Checkout the barometer code for examples on drawing multiple lines on the same chart.
-
You can use the existing APIs to generate the commands you want to send which will avoid attempting to reverse engineer the communication protocol.
-
Does this only happen if the battery is discharged? If you reset the board instead, do you see the same behavior? What are the steps to reproduce this issue?
-
I am not aware of any such effort.
-
What is GpioStreamSetup_3? It sounds like your code is adding points to the same data series instead of using 2 data series.
-
From what I understand, the images provided are images of CPros not having sensor fusion thus have nothing to do with the sleep issue. We will have time to look into the issue more next week.
-
You can't.
-
I would disable the internal adapter and try using a bluetooth dongle.
-
Post the code that is actually adding data to the graph.
-
Call mbl_mw_datasignal_subscribe with different callback functions
-
Is the bluetooth adapter you're passing into the VM the one integrated into your laptop? I also use VirtualBox to run Linux and I find that passing a USB adapter works better than the integrated radio in VB.
-
Use the MBLTimer class:https://mbientlab.com/iosdocs/latest/timer.html
-
Yes, use the disconnect handler to start the logger when connection is lost. When connection is restored, your connect callback can stop the logger.
-
see the i2c unit test https://github.com/mbientlab/MetaWear-SDK-Cpp/blob/0.11.4/test/test_i2c.py#L9
-
Ok, I'll take a look when I can. Also, there is no 150Hz setting for any of the sensors. Do you mean 100Hz?
-
IMU data means accelerometer, gyro, and magnetometer data. Those sensors consume the most current and are sampled at higher frequencies than other sensors. No, if you are constantly sampling, the LiPo battery powering the MetaMotion R boards will…