FooTheBar
About
- Username
- FooTheBar
- Joined
- Visits
- 74
- Last Active
- Roles
- Member
Comments
-
I did not find anything about the synchronization of the devices in the libraries. Could someone maybe tell me how the synchronization is implemented? Is there a way to get the current offset between the devices?
-
You are not advertising a developer tool. You advertise specific features (e.g. timestamp synchronization) that are missing in the product. Could you please return my money and I will send you back the devices (or destroy them)?
-
I just had a look at the data sheet and found the Oscillator specifications (6.2 OSC): https://mbientlab.com/documents/MetaMotionR-PS3.pdf By looking at the schematics (https://mbientlab.com/documents/MetaMotionR_0.3.pdf), I guess it's the X2-…
-
So you simply dropped Android support? And did not update the app but let every customer of you who uses android run into the same problem? And people without a current iPhone are just out of luck?
-
"Drifting happens. This is the real world." You advertise your product as "Synchronized timestamp: Supports multiple devices simultaneously" So you are simply lying to your customers? And after they find out, you mock them? 100ms error with…
-
Do you plan to enable the MetaBase app on Android to install the new firmware?
-
This is a known problem: https://mbientlab.com/community/discussion/3216/firmware-update-1-4-5-error#latest
-
Any updates on this issue?
-
which hardware do you use? I was testing with a T460 Thinkpad
-
I spent most of the day reading the tutorials. Isn't the fuser used to merge data from multiple sensors in a package? In this case, I want to merge multiple datapoints from the same sensor (!) into a package. So I think the packer would be the thing…
-
5 Minutes Test: Total Samples Received C3:25:9F:99:7D:B9 -> 5530, 18.4 F8:A3:30:FB:EA:57 -> 7398, 24.7
-
And the 200Hz in the app then only refers to the sampling rate on the sensor, but the data itself is packed into a smaller number of BTLE-packages?
-
I get the same message ("Firmware update failed (reason = No value for bootloader)") when trying to update a MMR vom 1.4.4 on an Android Pixel 3, Android 10.
-
I tried your code and got this result: Total Samples Received C3:25:9F:99:7D:B9 -> 567, 18.9 F8:A3:30:FB:EA:57 -> 732, 24.4 The second MMR came close to the configured 25 measurements/Second, the other one only got to 18.9/second.
-
Per device? Or for all connections together? (And why is the MetaBase-App offering a streaming rate of 200Hz if 100Hz is the max throughput?)
-
Having to run every program as a superuser is a huge problem (or what do you mean?) And I could not find the part of the tutorials you were referring to.
-
As I said, the first three octets can be used to identify the vendor of a device: A company can buy an identifier e.g. from IEEE: https://standards.ieee.org/products-services/regauth/oui/index.html Devices from HP for example, start with 00-50-8B…
-
I already did that. Which part are you referring to?