Laura
About
- Username
- Laura
- Joined
- Visits
- 3,668
- Last Active
- Roles
- Administrator
Comments
-
Hey @Srinivasa, for now we are just accepting that since we updated to the BLE5 stack, the default conn speeds are simply slower. Unfortunately that is not something our devices can control.
-
* It depends on the what's in the room but usually you get about 30ft of range if there are no obstacles. You can always log if need be. * What is your logging setup?
-
Hey @giovanni_dq , that's beyond the bluetooth spec, BLE5 only allows 100HZ TOTAL. So you could do acc 80Hz + gyroscope 20Hz for example.
-
If you download the MetaBase app for iOS or Android and connect to the sensor, you can product a diagnostic report. Also take pictures and itemize each sensor.
-
Can you put some debug statements in your app and also look into the bluetooth raw packets to help debug?
-
This is not possible as the button has no functionality tied to the bluetooth whatsoever.
-
You will need to look for damage and to see if they suffer from over discharge (basically the sensor battery is no longer charging). If you can connect them, you can also generate a diagnostics report. You should provide this information on a per s…
-
Hey Connor, Ryan is looking into this for you, he should have answer this weekend.
-
Unfortunately Bluetooth is slow. What you can do is only record when there is movement to make the datasets smaller.
-
Yes, that's the bootloader issue from the other thread.
-
What do you mean by "my app works great"?
-
Do the other functions in the menu like put to sleep work?
-
For the time being we are not supporting the MetaRom, you will have to update the code yourself.
-
We still don't have an Android person on staff. I can provide Python snippets if you want.
-
It's possible your MetaWear died. Have you been able to connect it after charging it for a while?
-
What's the sensor model/firmware/hardware version you are trying to downgrade?
-
Hi Torsten, For one or two of those MMCs, can you send me the diagnostic file?
-
It looks like this may just be the new download speeds with the Bluetooth 5.0 upgrade. We will keep looking for options but we may just have to accept this as the new standard.
-
Yes, there was an issue with the memory in 1.7.2 and that's why we immediately released 1.7.3. The issue only affected MMR/MMRL hardware version 0.4
-
Luckily 1.5.1 does use the same bootloader as 1.7.3. If you download the MetaBase iOS App you can use the Advanced menu to downgrade:
-
@DylanMach1, There's not enough information here from your code or crash log. Can you send us code snippers, crash logs, bluetooth outputs and so on?
-
@Srinivasa, We don't support firmware downgrading from 1.4.4 from 1.7.3 because they use different bootloaders.
-
HI @toffy_dee, There should only be disconnects if you: 1. Go too far away from the app 2. Stream beyond the capabilities of Bluetooth (100Hz) It is possible to go into logging mode after a disconnect. I will see if I have time to write an exa…
-
Hey @Srinivasa, I still didn't observe the reducing time to download the data from the sensor to mobile. it was like 1.5.1? Unfortunately this was only a test and was not guaranteed to succeed. Am I missing where I should call this mbl_mw_sett…
-
You can try to run the source code of the app which is on Github if you would like. Otherwise I do not have sufficient information to comment.
-
We don't support Windows, how are you trying to use the Lenovo?
-
This is outside of the scope of this forum as it does not pertain to our sensors/SDKs but It looks like you need to setup your developer profiles properly. You should look at how to setup profiles with your developer account: https://developer.apple…
-
@Srinivasa We are still updating our swift examples, SDK and Apps but I think we are going to make the executive decision to move to this new SDK permanently.
-
While this is not at all related to our SDK or sensors, it seems like you just need to put a VERSION # in your gradle file: versionCode 23 versionName "3.5.27"
-
Thank you @AndooBundoo, very helpful!