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
-
Talked with the firmware dev and we're getting a fix out for this issue.
-
The button is not an on/off switch; the board is always on when it is supplied power.
-
These settings are not exposed to the user.
-
What do you mean by "it's not accurate enough"? First off, are you receiving the expected amount of data? No, the logger cannot free the flash memory while a btle connection is active. If you are streaming at a slow enough rate, you might be abl…
-
* What android device and OS are you using? * Does the same issue occur on other Bluetooth apps such as the nRF Connect app?
-
That should work. Alternatively, you can try using the macro to have the board automatically rebuild the entire data route.
-
That is true. Well, we should first get to why your board is resetting as the firmware shouldn't be behaving like this. How are you configuring your MetaWear?
-
via the android/ios api or through firmware?
-
An unexpected disconnected will trigger the failure function from the ConnectionStateHandler function however it can take up to 20 seconds for Android to realize the btle connection was lost. There is no method to check if a route is still valid…
-
Each btle stack has different default connection parameter settings; the 30ms and 50ms sounds correct for iOS and Android devices. It's possible the Nexus 5 and Optimus Fuel ignore the connection parameter update requests. You should try your test…
-
* What Android OS and device are you using? * How does this issue happen exactly? Do you have a stream going and then it randomly stops without the user doing anything? * Can this be reliably reproduced with your setup The tearDown function do…
-
Match the nth accelerometer data with the nth gyro data. The time difference between the two sensors is probably milliseconds so I highly doubt that will negatively impact your algorithm if at all.
-
1) Yes. 2) You have the sampling frequency and start time. Using those two variables, you can approximate how many data points you expect to see at a point in time and check that you have received the expected amount.
-
Since the sensors produce data at very consistent time intervals, your counter method is all you need to sync data. If you need accurate timestamps, then you will have to use the logger and even then, there will always been a time difference betwee…
-
The haptic driver circuit for R is laid out in the product spec sheet, section 2.5 (page 8).
-
You retrieve the logs by calling mbl_mw_logging_download as outlined in the Downloading Data section. Logged data is handled in the same way as streamed data. If you not yet tried data streaming, you should first try streaming before doing logging.
-
2 log entries per accelerometer data
-
6 bytes per record
-
You cannot get accurate timestamps from a live stream. The accelerometer produces data at consistent intervals so you can rely on the 50Hz setting as a reliable time offset between two data points.
-
The firmware manages all of the log data, you do not need to worry about when log data is deleted. Read the section about the MblMwDataLogger object.
-
OK, so do you have the pins correctly set? Assuming they are correctly defined in your code, what does your bmi160 init code look like? Also, what exactly have you tried thus far?
-
There are two 4 byte data chunks per packet.
-
Check out this thread from Stack Overflow for example code
-
Are you guys using CPRO boards?
-
Call the code multiple times with different BluetoothLEDevice objects
-
Please see this post by Matt regarding measuring battery charge.
-
Write [0xfe, 0x01] to issue a reset. Regarding the MetaWear app, does the board not show up in the scan or it does but the app fails to connect?
-
Do you have offline mode enabled in your IDE? Does the same error occur if you try older versions?
-
The only thing I can think of is to move the start function into the CompletionHandler, otherwise the code works fine for me.
-
This sounds like the board is resetting at some point. Try updating to the latest firmware and program a macro to turn on the LED on boot to see if the board is indeed resetting.