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
-
How long were you sampling data in that CSV file? It looks like there are lingering data points from previous logged data. I'll have more time to do another batch of tests tomorrow.
-
It probably should be OK though doing so defeats the purpose of using asynchronous tasks and it makes error handling more complex than it needs to be.
-
@wko27 5 seconds should suffice. Do not hijack threads; post your issues in a separate thread along with your code and steps to reproduce.
-
The data is stored locally on your device. Use iTunes or a file browsing app to check the device's "documents" directory for any CSV files. Only devices that have been setup to log data by MetaBase will show up in the "Download" scan. If your d…
-
Yeah, we are migrating the web server and did not move the "releases" subdomain. Everything is in order now.
-
All temperature measurements are handled by the board/firmware and simply forwarded to the host device. None of the code in the SDK or sample app performs any temperature calculations.
-
I haven't run into any issues with scheduling the logger to start. accelerometer.acceleration().addRouteAsync(source -> source.log((data, env) -> Log.i("MainActivity", data.toString())) ).onSuccessTask(ignored -> timer.scheduleAsync(…
-
You can use timers to schedule different haptic events. https://mbientlab.com/androiddocs/3/timer.html
-
Some users have tried creating unity projects with the C++ SDK but that was a while ago and I don't know if they were successful or not. https://mbientlab.com/community/search?Search=unity MbientLab has not developed any Unity assets or tutorial…
-
@Eric said: You can't directly retrieve the resistance. You can instead read the voltage at GPIO 0 and use that to calculate the thermistor's resistance: https://mbientlab.com/androiddocs/latest/gpio.html#analog-data Is there a reason …
-
Post board model, firmware version, hardware revision, and the code you are currently running. Regarding your specific issue: * Is the acc, gyro, and mag still providing correct data? * Have you tried resetting the board? * How are you usi…
-
Rather than crunch numbers with your example, run the x-axis code yourself while streaming the raw, lpf, and raw-lpf values. You'll understand how things work faster than trying to think everything through on paper. Same thing for your other quest…
-
Add a delay after calling clearEntries. Looking at the Logging interface again, that function should be an asynchronous task. You also don't need to disconnect anymore.
-
Did you create a data route to direct acceleration data to the logger?
-
Please post the actual log data.
-
Use a passthrough limiter in count mode. * https://mbientlab.com/androiddocs/latest/data_route.html#passthrough * https://mbientlab.com/androiddocs/latest/data_processor.html#modifying-processors * https://github.com/mbientlab/MetaWear-SDK-An…
-
* Can you attach the data you have collected so far? I would like to see if the data is simply all bad, or if it starts out good then eventually becomes invalid. * Since you are running the acc @ 25Hz, do you see the same issues if you don't use i…
-
Yes, that is expected behavior as gyros are inherently noisy and will accumulate drift, hence why people have developed sensor fusion / filtering algorithms to correct the data.
-
multicast is simply an API feature to let you reuse the same data producer for different chains; it does not affect data flow. Each data processing component is executed in the order it is added. Since you are looking to compute "x0 - lpf(x0..…
-
Since you are basing your code on the sample app, follow how that code base handles a reconnect: https://github.com/mbientlab/MetaWear-SampleApp-Android/blob/master/app/src/main/java/com/mbientlab/metawear/app/HomeFragment.java#L147
-
As the error message says, you do not have onServiceConnected defined; this function is present in the original file. Regarding the switch issue, the example code is using the Android switch widget, not MetaMotion's push button switch. It looks …
-
If you aren't at least seeing the sensor data in Logcat, then you probably are not running the code correctly. Use the variant downloadAsync method with the error handler and post any messages being forwarded to the handler.
-
For step 2), which raw value are you using when computing "raw - lpf"? The lowpass processor delays the stream until it has collected enough samples so in your case, it won't provide a value until the 10th data sample.
-
It should be the time of the last sample.
-
What errors are outputted when you compile the code? Please post the actual code, not screen shots of it.
-
* The "Limited Connection" message is explained in the SDK's README * Are you running these tests with fresh batteries? * Were these tests running successfully before? Devices won't always successfully connect the first time thought we have…
-
After doing some tests, I suspect the root cause of these issues is that the battery is low on charge. How long have you been using the current batteries in your devices? If you put in a fresh CR2450 battery, do these issues arise?
-
Probably not; the module depends on C++ code.
-
Huh, looks like that section was linking to the wrong code template. This is the project that tutorial is based on: https://github.com/mbientlab/MetaWear-Tutorial-Android/tree/master/starter The instructions will be much clearer with that code …
-
This is explained in the documentation: https://mbientlab.com/androiddocs/latest/data_route.html#handling-data And in the tutorials: https://mbientlab.com/tutorials/SDKs.html#on-board-logging