Laura
About
- Username
- Laura
- Joined
- Visits
- 3,668
- Last Active
- Roles
- Administrator
Comments
-
Only the MMS will be supported because it is the only one that has the CPU with a USB driver embedded in it from Nordic.
-
The file doesn't include timestamps so I can't comment.
-
Unfortunately distance is not possible to do using Bluetooth. It would be very inaccurate using RSSI.
-
Take a look at https://mbientlab.com/community/discussion/2945/macos-a-c-function-pointer-cannot-be-formed-from-a-closure-that-captures-context#latest
-
Would you mind sharing data from the sensor (showing the bad timestamps), your setup steps (how you program it/code or metabase app setup) and also the device's diagnostic results?
-
4.2v 50ma constant current (be careful)
-
Take a look at this thread that shows how to create bridges: https://mbientlab.com/community/discussion/2945/macos-a-c-function-pointer-cannot-be-formed-from-a-closure-that-captures-context#latest This isn't really metawear api centric, just a gene…
-
If you set this to libmetawear.mbl_mw_acc_set_odr(s.device.board, 100.0) It should work just fine. Do you have data to show it does not work?
-
Looks like the battery over discharged. You have to jump it now like a car battery (the protection circuitry is preventing it from charging). You can do that if you have a Power supply handy. Let me know.
-
We are working on this. Our MMS model supports USB and Bluetooth. The USB is currently under development. We had planned to release last month but have hit a few issues and release will occur this month instead.
-
the MMR won't stop transmitting data unless: * The App crashes * There is a power failure (battery short/dead battery) * The Bluetooth link gets severed (this is most likely)
-
Can you share the code you are running? Can you share the data you are receiving that shows 25Hz?
-
Looks correct. you might need to post your entire code, I don't think the 100.0 is the issue.
-
Can you please send more info. Is this replicable? Sounds very odd like maybe in an orientation of some kind there is interference? I don't have any information to comment more but would appreciate pics/details.
-
You can try to run the calibration scheme.
-
Did you update your App with the latest APIs? You will need to update but it should be relatively minor/trivial.
-
The IMUs do not know anything about each other. Only the master device (like a computer or phone) knows anything about all the IMUs. IMUs don't show location like a GPS. They show change in motion.
-
To put the device to sleep call: mbl_mw_debug_enable_power_save(device.board) Then to wake it up you have to press the button OR plug it in to charge (or re-insert coin cell batt)
-
Here you go.
-
We don't allow retrieving subsets of data.
-
I've noticed sometimes I need to wait/pause a second before issuing the mbl_mw_led_play() command. Can you add that to your code and see if it makes a difference?
-
1) I don't think that is possible 2) limit? which api call?
-
As far as I know BOSCH doesn't have magnetic calibration. Supposedly initial calibration is done at the factory and then again based on the sensor fusion mode you are using (but it's just based on whether or not the magnetometer is used or not). Wh…
-
So it's the default settings of BLE 5.0 that sets the initial tx mode to a low setting. We unfortunately can't do anything about that but you can still use our API call to set the tx mode higher.
-
Working on it. Planned for the end of this month.
-
Can you connect to the device again and go ahead and update the firmware?
-
You should be able to log both if you write your own app (just not with our own app). Everything is open source so just look at the code and customize it yourself.
-
Unfortunately the BOSCH folks keep all of their algorithms completely closed-source. We don't get access to ANYTHING. You can always run your own kalman filter in software.
-
Did you follow the troubleshooting steps on the website? Can you report back with more information on what worked and what didn't? Also if you have a generic Bluetooth scanner app, does it show the MetaWear advertising?
-
No, this firmware was MMS specific.