Laura
About
- Username
- Laura
- Joined
- Visits
- 3,668
- Last Active
- Roles
- Administrator
Comments
-
Did you try to use the example I linked? self.acc = self.libmetawear.mbl_mw_acc_get_acceleration_data_signal(self.board) self.gyro = self.libmetawear.mbl_mw_gyro_bmi160_get_rotation_data_signal(self.board) signals = (c_void_p * 1)() …
-
Some example code in Python: def processor_created(context, pointer): self.processor = pointer e.set() fn_wrapper = cbindings.FnVoid_VoidP_VoidP(processor_created) acc = libmetawear.mbl_mw_acc_get_acceleration_data_signal(self.device.boa…
-
I think with the Metahub app it's all the same. If you want to set up sensors independently, you will have to modify the metahub app or write your own app (it would be easy to write a quick setup app in python).
-
Please read the tutorials on the data fuser, it trains you on how to pack data and we even have coding examples: https://github.com/mbientlab/MetaWear-SDK-Python/blob/master/examples/data_fuser.py
-
It's just JSON syntax: { "command": "stream", "devices": [ "D4:5E:82:E1:15:01", "D5:7B:B9:7D:CE:0E" ], "sensors": { "Accelerometer": {"odr" : 100.0, "range": 4.0, "threshold": 2.0}, …
-
Bluetooth is not that fast. With all the packet overhead and sensor data, you typically get about 120Hz out. If you "pack the data", which means less overhead and more data in a single packet, you can get around 200Hz.
-
Your code looks right. Try adding a delay between this command (setbtlecon) and the next (readdeviceinfo). Global.connInterval = Build.VERSION.SDK_INT >= Build.VERSION_CODES.M ? 11.25f : 7.5f; // More code here Settings.BleConnectionParameters…
-
Did you look at the README?
-
@renev, Read the tutorials, we offer a packed mode.
-
@renev, Obviously you know better than everyone else but you forget the data overhead in the bluetooth packets taking up bandwith. Also we do have a pack mode available which you are welcome to use to get more throughput. I will be deleting your…
-
@renev, I doubt it will work because there is no way to easily tie the Python SDK ble libraries to use the Android ble libraries.
-
Right after you connect, you can ASK to change connection parameters. Again, you can only ASK. Only the MASTER device can accept or reject and there is no way to know if your parameters will go through. This is part of the BLE spec and is not cha…
-
Can you explain your setup more?
-
If you sample at 50Hz for acc+gyro and about 10Hz for magnetometer you should be ok.
-
I am not sure that you will find this definition anywhere. There are obviously error rates on the bosch sensors and the fusion library (again you have to look at the docs for that). After that it is a matter of your application and software. What…
-
Thanks for lettings us know @dorlev22
-
It is not. There is a max of about 120Hz via bluetooth. That is simply a hard fact (it is the bluetooth hard spec + physics). You can log at higher speeds and download later. Is that what you are doing perhaps?
-
You can set the sampling rate.
-
You can't stream at 200Hz...that's beyond the capabilities of bluetooth. 100Hz MAX when streaming with BLE.
-
That sounds fair.
-
Which Api? Can you post in the correct category?
-
That means the battery was not replaced correctly and/or the new battery is bad.
-
Take a look at the bosch data sheet: https://www.bosch-sensortec.com/media/boschsensortec/downloads/product_flyer/bst-bno055-fl000.pdf
-
Just npm install
-
Hey @MarkBresler, I am not sure since we don't support our JS APIs on MAC OS. To be honest, this it seems like this doesn't have anything to do with our APIs though. It seems like a MAC permission/install issue. Have you Google-fued this issue…
-
Yes it is possible but limited by the bluetooth throughput. I don't think we have any examples of this but just sent your sensor to stream angular velocity at 100Hz (default) and acceleration at (25Hz or less).
-
Only one output for sensor fusion is supported at a time.
-
Yes, the issue is that the battery is dead from over-depletion. You can replace the battery yourself or we have an option on our store to fix it for you. If you have an engineer handy, they may be able to use their fancy power supply to recharge…
-
I didn't say line them up 1 to 1. I said line them up intelligently. It may involve duplicating or removing entries.
-
Use the epochs to "match" closest value between sensors, even if you have to delete or repeat entries. I would write a script to do this for me.