stephen
About
- Username
- stephen
- Joined
- Visits
- 557
- Last Active
- Roles
- Administrator
Comments
-
That is just a warning message that can safely be ignored.
-
The code as posted has no errors, but the error you mentioned occurs when you try to access variables from within the closure that are declared externally. The only way to pass data into the closure is via the context pointer. You would use _sel…
-
The issue here is that the sensor fusion module outputs floating point values natively in the firmware, but the data processor is only implemented to deal with fixed point or integer values. This means you can't manipulate the data on device with t…
-
It is important to note that calibration only affects the sensor fusion outputs, so if you are streaming raw accelerometer values then no calibration is needed. The calibration constants for the accelerometer and gyroscope account for hardware va…
-
This is a hardware limitation that is unlikely to be lifted any time soon. Due to the complexities of non-volatile memory and in an effort to maximize log space and performance while minimizing power usage, we must always read, write, and erase seq…
-
Eric is correct, Bolts-Swift hasn't been updated to swift 5 yet and they don't define swift_version in their Podspec. You need to set the swift version for the Bolts-Swift target to 4.0. This can be done manually in the Build Settings or you could…
-
Issue has been identified and fix will be in version 4.2.3 due out in a week. As a workaround, force quit and restart the app after the 4th download. Thanks, Stephen
-
This looks like an issue with the App. We have pushed a new version (4.1.2) to the store and it should be up in a couple days.
-
For anyone that needs to develop in objective-c I would stick to version 2.X of the MetaWear iOS SDK. You can find the docs here: https://mbientlab.com/iosdocs/2/index.html. Version 3.X, was never tested with objective-c. We haven't looked, in …
-
Issues have been fixed, please try latest code on develop branch
-
Sorry, this feature hasn't made it in to 3.X yet. There isn't a simple workaround, so we will add this in the next release within the week.
-
Please try the latest 3.1.5
-
In the next release I'll setup the submodule to pull from https instead of git protocol. See if that fixes the access issue.
-
Also try deleting the Pod folder and re-installing. You may need to clean the project (Cmd+Shift+K) or even clean the entire build folder (Alt+Cmd+Shift+K)
-
Sorry for the confusion, but the Bolts-Swift Pod has just been updated so you can go back to using: pod 'MetaWear', :subspecs => ['UI', 'AsyncUtils', 'Mocks', 'DFU'] Note the subspecs are not required but could be helpful based on your needs
-
The new version uses the C++ library as a submodule so it should read: pod "MetaWear", :git => 'https://github.com/mbientlab/MetaWear-SDK-iOS-macOS-tvOS.git', :submodules => true, :commit => 'd1c417c'
-
The 2.X version of the API is deprecated, but we will make maintenance updates like this for the next year. Please try version 2.10.1. Thanks, Stephen
-
Thanks for the report. We have found and fixed the issue, the next release should be on the App Store within 2-3 business days.
-
You can try using the new Swift SDK which contains the watchOS target. It isn't in the CocoaPods trunk yet, so you need to use the following to pull directly from our GitHub: pod 'MetaWear-Swift', :subspecs => ['UI', 'AsyncUtils', 'Mocks'], :…
-
We just released a new version which removed the need for us to store the "device configuration". Please delete the MetaBase app from you iOS devices and download the latest version from the AppStore.
-
We just released a new version which removed the need for us to store the "device configuration". Please delete the MetaBase app from you iOS devices and download the latest version from the AppStore.
-
For a real life example see the updated StarterProject
-
After a few experiments, the only reliable way to do this on macOS was with serial requests. macOS defaults to very low BLE bandwidth and it just can't support 2 devices at the same time.
-
I'll be taking a look at this today, and hopefully publishing a more in depth guide to persistent configurations, but I have a few offhand pointers that may help: * There is no need to use the MetaWear sample app to reset, when you call setConfigura…
-
The preset modes have been tuned by the manufacture and should be good for most use cases, if you know the BMM150 well and want to fine tune the magnetometer, I would directly modify the code in MBLMagnetometerBMM150.m. You may need to adjust the R…
-
Thanks for the well documented error report. We have been able to reproduce and are looking into it now. We have run into issues before with the saturating CoreBluetooth, however, it's not well documented. We currently throttle writes on a per-…
-
I believe this has been answered here: https://github.com/mbientlab/MetaWear-SDK-iOS-macOS-tvOS/issues/4 Let me know if this is a separate issue.
-
Just wanted to confirm that support for this is in our development pipeline, but it is at least a couple months out. If that timeline is too long, then your best option is modify the SDK as needed to enable your use case.
-
In that case, this is most likely due to un-balanced calls to start/stop logging. Double check that you are calling start/stop on the exact same event. If you are using filters, you need to use an MBLRestorable config in order to persist the event…
-
Please try deleting your app from the iOS device and try again.