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
-
Sorry, I mean increase the standby time which reduces the frequency.
-
Please contact MbientLab directly and link this thread. We would likely need to get the board in our lab to look into the bootloader loop. https://mbientlab.com/contact/ This can take a while to be fully resolved so in the meantime, try using …
-
Assuming you have no issues running the gyro and acc at 50Hz each, try reducing the barometer's standby time.
-
The first line of code is completely nonsensical and I cannot discern what you are attemping to do. Regardless, you do not create the Acceleration object; the API creates one for each data sample received from the accelerometer and passes it to you…
-
No additional changes to the PWM have been made thus far.
-
* What Android device and OS are you using? * What firmware is the board running? * What board do you have? * Do you see a similar issue when using the MetaHub app?
-
Combining results from multiple outputs is not easily implemented with the on-board data processing. It can be done but it is very messy; see these posts: http://community.mbientlab.com/discussion/comment/2053/#Comment_2053 http://community.mbi…
-
As matt said, its piezo could be accumulating charge or generating voltage spikes. Can you try measuring the current/voltage produced by your test vibrations using a multimeter? The MetaWear app reads analog data at 33ms. You should try with you…
-
* Which board are you using and what firmware is it running? * How fast are you running the acc, baro, and gyro? * Try syncing something small like 60 temperature samples * When MetaBase is in this unconnectable state, what does the home screen l…
-
Try re-pairing the board to your Win10 device. It sounds like for whatever reason, your app no longer has access permission to the board. As mentioned in my previous post, you'll have to configure the acc and gyro settings for your use case. You…
-
* What type of Android device are you using? * What app or code are you running?
-
2 is not a valid connection interval value. Call the function with the sample parameters as in the code I linked. How are you configuring the sensor fusion algorithm? It's likely the acc and gyro settings are not properly set for your spe As …
-
I don't need the entire stack trace but it should contain at least all of the MetaWear API calls. Based on your specific usage, you should not be constantly removing timers. Create the timer once and have it execute its task a fixed number of tim…
-
Use the passthrough limiter in count mode to only record a fixed number of samples. You need to remove resources allocated on the board when you are done using them. It looks like you are simply creating routes and never removing them which res…
-
Matt's primary suggestion is to follow the Arduino tutorial and add the 1Mohm resistor. You should ensure that no more resets are occurring after enabling the pull down pin and if the circuit is stable, start collecting data with your sensor.
-
The removeTimers method only removes timers the API is aware of so if you close the app without saving its state, it won't remove anything next time you call it. You should remove timers and routes when you are done using them. You can also use…
-
Update the dependencies to use API v3.0.17 instead of v3.0.0.
-
That issue indicates that the device is still connected even after the disconnect method is called which doesn't seem like the same issue mentioned in this thread.
-
Check out the latest commit to the C++ SDK.
-
Outside of waking up the device and force starting BLE advertising, it doesn't do anything, it's just a button.
-
MetaHub automatically attempts to reconnect if connection is lost.
-
use mbl_mw_logging_clear_entries.
-
What are the firmware and hardware revisions for your board? Issue a reset command with: mbl_mw_debug_reset. How long does your app run before it crashes with the app window disappearing? This see,s like a case of delegates not being stored…
-
What mode and data ranges are you using for sensor fusion? Another user had mentioned discrepancies with vertical usage but was able to correct the data. http://community.mbientlab.com/discussion/comment/3697/#Comment_3697
-
Try reducing the max connection interval to 7.5ms http://community.mbientlab.com/discussion/comment/3825/#Comment_3825
-
Did you add the 1Mohm resistor as described by the Arduino tutorial? What values are you reading so far with your sensor?
-
Use the MetaHub app for streaming data. The sample app simply provides an example of what can be done whereas MetaHub is built for streaming. To steam sensor fusion at 100Hz, you'll need to modify the max connection interval as described in the d…
-
Place a breakpoint at mbl_mw_metawearboard_tear_down and check that board and logger_state are still pointing to valid addresses. The debug build compiles the shared library with the "-g" flag. When are you calling mbl_mw_metawearboard_tear_down i…
-
Reduce the max connection interval to 7.5ms. You might have to reconnect to the boards to have the connection intervals renegotiated, not sure if the Linux ble stack supports live changes. http://community.mbientlab.com/discussion/comment/3825/#C…
-
Yes