Laura
About
- Username
- Laura
- Joined
- Visits
- 3,381
- Last Active
- Roles
- Administrator
Comments
-
What is the error?
-
* I looked into the BLE API from Apple the other day and I could not find a way to do so. There is nothing to do on our side, the Nordic BLE stack works as intended. * It is not on our side, it is on the master side that you would change the BLE se…
-
Oh if you stop the log then it's over, the accelLogger will no longer be valid.
-
Do you have the code for me to replicate the issue? This will probably be the easiest way to debug.
-
Only 1 sensor fusion output is available. This is per BOSCH sensor fusion algorithm specs. Linear acceleration OR Euler angles OR Quaternions. You can't have all 3.
-
Yes this is normal. While you may have recorded data at say 200Hz and gotten 10 million data points in 1 second, the Bluetooth link can only download data at 100Hz. So to download 10 million data points, it will take 2 seconds. The Bluetooth is sl…
-
@Christian, Thanks! I will fix in the next update.
-
Do you get this consistently by the way? Is this replicable 100% of the time?
-
@Christian, Thanks for noticing this. I will look into this asap, it might be related to one of the other bugs that has been filed regarding timestamps.
-
@benodisee, Sorry I was OOO, thank you for the fix and update!
-
Your code looks fine. Do you have data to show why you think this isn't working?
-
@trip Should we understand that, even using the "log" / "download" commands, there is still a limited number of 4 sensors that can be connected per on dongle? Yes there is. any progress/reply on the issue? We are also about to st…
-
I would need to see code to comment more. Are you using the defacto metahub? How are you scheduling the download and restart?
-
So two things. 1. We don't official support sensor fusion + raw sensor data so it is normal and acceptable that it does not work. 2. Sometimes you can get sensor fusion + really low frequency raw sensor data to work but it would have to be somethi…
-
This is already available but you have to upload the firmware yourself. We do plan on making it standard soon.
-
You can read the code, it's all open source: let mode = magnetometer ? MBL_MW_SENSOR_FUSION_MODE_NDOF : MBL_MW_SENSOR_FUSION_MODE_IMU_PLUS Which means its NDOF if the magnetometer is present.
-
mbl_mw_logger_subscribe() is just a closure, it probably loses context once the app closes. You need to restart the download by restarting it from accelLogger and whatever ios provides as a callback when the app returns to action.
-
Your code looks fine, it would set the ODR to 1.5625Hz (the closest value to 2.0). What makes you think it isn't working?
-
hey @jjm345, It sounds like you might just have had the wrong type for MBL_MW_LED_REPEAT_INDEFINITELY.
-
Are you able to send pictures of the device that isn't working as well as a diagnostic report from the metawear app?
-
Did you mean that your team is looking for ways to enable option #2 in the firmware? Or do you mean to enable in the SDK for developers? This has nothing to do with our firmware, it is settings on the smartphone and computers that need to be chang…
-
You can do this but it will be fairly erroneous.
-
You can define loggers in the high level class like the DeviceViewController: var loggers: [String: OpaquePointer] = [:] Check out: https://github.com/search?q=org:mbientlab+loggers&type=code
-
I can't comment much without seeing all of your code but there must be an issue with your bridge ptr, is the high level controller in your code even a "DeviceViewController"? Can you try to use some of the code from our examples in github?
-
Sorry it is taking so long, the BLE + USB spec can occasionally cause conflict and we do not want to release an unstable version of the firmware. We are working as fast as we can.
-
If you are still connected to the sensors and the board pointer is still valid, you do not need to re-use "connectAsync()". Please see how many examples on github.
-
The new firmware supports the new BLE5.2 which has two modes: 1. Long range but slower data throughput 2. Short range but faster data throughput Unfortunately in BLE5.2 #1 is the default. We are looking at the capabilities of Android, Linux, and …
-
Hey @jckulp , we think it's a really simple issue in the CPP library when the timestamp gets created and somehow there's a missing bit or some data getting dropped. I will look into it.
-
Yes the latest is on github, try it out and let me know: https://github.com/mbientlab/MetaBase-Hub Sounds like there's a simple missing } in the config.json. Try replacing it with the original and see what happens.
-
Do you get any print statements at all? Can you share the output?