stephen
About
- Username
- stephen
- Joined
- Visits
- 557
- Last Active
- Roles
- Administrator
Comments
-
Edlee, We were actually just debugging this issue and already have a fix. I'll just need get a release published, should happen within 24 hours.
-
Hmm, what happens if you increase the timeout? There are some limitations on how many devices you can connect to simultaneously, and performance starts to drop as the number increases, so it may take longer to connect.
-
Okay then, can you expand on what you mean by "not responding to the code"? Are they timing out in the connection or they don't show up in the saved MetaWear list? Using retrieveSavedMetaWearsWithHandler: will only give devices you have previousl…
-
I'm wondering whats going on this line:if ([selectedDeviceIdentifiers containsObject:currdevice.name]) { Are you storing device identifiers or names? The [MBLMetaWear name] is always "MetaWear" by default, whereas the [MBLMetaWear identifier] …
-
Glad you got things working! I know the crash occurred because of file protection, i.e. framework trying to write to a file when it didn't have sufficient permission. It's hard to say why exactly turning off Data Protection didn't fix it, but cha…
-
// Here is an example unit test - (void)testButton { XCTestExpectation *waitingExpectation = [self expectationWithDescription:@pause for manual verification]; [self.device setConfiguration:[[ButtonConfig alloc] init] handler:^(NS…
-
#import @interface ButtonConfig : NSObject @property (nonatomic) MBLDataSwitch *disconnectedSwitchEvent; @property (nonatomic) MBLDataSwitch *connectedSwitchEvent; - (void)didConnect; @end @implementation ButtonConfig …
-
Regarding hypothesis 1, you are correct. Here is a expert from the documentation of programCommandsToRunOnEventAsync: @warning THE BLOCK IS ONLY EXECUTED ONCE DURNING THIS CALL AND NEVER AGAIN, DON'T ATTEMPT TO USE CALLBACKS INSIDE THIS BLOCK…
-
Looks like this has to do with Enabling Data Protection (iOS, WatchKit Extension, tvOS) on an App. With that enabled, files are encrypted and not accessible when the device is locked by default. Looking at the available File Protection Values I th…
-
Good catch, there was a bug in the App which has been fixed. If you have access to Xcode, try installing the latest from: https://github.com/mbientlab/Metawear-SampleiOSApp. Otherwise, the next App Store release will come in roughly 1 week! T…
-
The fourth one is RMS, so it goes X,Y,Z,RMS!
-
Have you tried deleting the MetaWear sample app and re-installing the latest from the App Store?
-
This is interesting, but it also sounds like it could be a complex issue, so I'll need a few additional details:1) iOS Version 2) MetaWear SDK Version 3) MetaWear Model and Firmware Version 4) Explanation of events that leads to the bug (I.E. wha…
-
I've been unable to reproduce here, but here is a random thought that could help: The frequency of accelerometer data is usually pretty fast (100Hz default), so based on the code linked it would be telling the haptic to buzz for 350ms ever 10ms. …
-
What version of iOS are you running on your device?
-
We have successfully used backgrounding in apps before, and I don't ever remember seeing this issue. Is there anyway you can share the project source or provide more details around what functions are being called in the background?
-
Thanks for the report, we have found and fixed a bug which will be fixed in the next release. In the mean time I have a revised code snippet for you to try. I'm assuming you wanted the LED to illuminate when the device isn't "flat" (i.e. the z-axi…
-
1. How to detect if device is not around anymore - We addressed this with a commit on Mar 8, should of made it into version 2.5 on App Store, that indicates with a "no signal" icon if no ad packet has been seen from a device in over 10 seconds 2. …
-
Yes it is! You can set the callback queue to whatever you want, see https://mbientlab.com/iosdocs/#mm-dispatch-queue
-
The state property is KVO compliant, so after you connect to the device attach an observer and whenever it changes to disconnected, you can call connectWithHandler again. Take a look at the sample app code here: https://github.com/mbientlab/Metawe…
-
I've just updated the project with some beta code that enables the BMI160. Note that it hasn't been thoroughly tested, but please give it a try and send any feedback (or a pull request) our way!
-
Thanks for the detailed report. That error comes from a timeout if a response doesn't occur within a certain time. I imagine that with around 6-8 concurrent connections the timeout length is no longer valid. We will have a fix in the next iOS SD…
-
Sorry, there is no way to erase all events other than a device reset. I think you still want to use a configuration object for your use case. If the threshold ever changes then you download the log, update properties on the configuration object, …
-
This does happen sometimes during development, it's just a corrupted cache file used internally. You need to delete the app from your device to fully clear out all cached data and then reinstall.
-
The MetaWear objects are global in nature, so you can certainly keep a connection to one and access it from any controller. You could make a shared global manager class to abstract what it is you are doing, or simply pass references to the MBLMetaW…
-
Thanks for the questions, the documentation isn't clear on this so I will update that and fill you in here. isGuestConnection is only valid once a connection is established. It works by looking a special app specific token stored on the MetaWear …
-
Thanks for the report, please see if SDK 2.1.1 fixes your issue. Thanks!
-
Confirmed an SDK bug, will publish release within 48 hours.
-
See our docs for an example on how to do this: https://mbientlab.com/iosdocs/#a-bmi160-freefall
-
I've removed the old tutorial using the drag framework method, and put a link to the CocoaPod one. CocoaPods was at one time optional, but now it is the recommended way. Thanks!