Matt
About
- Username
- Matt
- Joined
- Visits
- 350
- Last Active
- Roles
- Administrator
Comments
-
@giovanni_dq Some ways to improve download speed. Keep the device close while downloading to reduce potential interference/packet loss. Disable any sensor traffic, such as streaming that may be consuming bandwidth. Download over USB if using…
-
@giovanni_dq Make sure that you install the latest version of MetaWear Python on PyPi to be sure your devices are connecting over USB. The example scripts have also been updated to indicate what type of connection has been established and you may…
-
@giovanni_dq There is nothing special to be done to do both, just don't make any calls to stop logging or shutdown your sensor before doing a log download. If your remove line #37 libmetawear.mbl_mw_logging_stop(d.board) from https://github.co…
-
@FernandoMPN Unfortunately the chipset used in MMRL devices does not include the necessary hardware to support USB communications.
-
@jepse032 We identified a firmware issue related to log memory with the model and revision of your devices, and fixed it with firmware release r1.7.3 which is now available. Please let us know if you have any further issues. We will follow up …
-
@Srinivasa Support for forcing 1MHz PHY was added to the Cpp SDK along with bindings in this commit https://github.com/mbientlab/MetaWear-SDK-Cpp/commit/5ee04ff14c5fe9545cc87b30fddcd6665d8b323c @jepse032 We have released a firmware 1.7.3 which re…
-
@AlexCrux Yes, you will want to run the commands from the original script to configure the logger for the data sources that were logged (and in the original order). Then the firmware will be sufficiently configured for a recovery readout. Now …
-
@tsubakinohana have a look at the example script here: https://github.com/mbientlab/MetaWear-SDK-Python/blob/usb_perf/examples/stream_mag.py
-
@AlexCrux When you say anonymous signal downloader are you referring to the python example script or one of the apps? When power is lost, two critical pieces of information disappear -- the relative time base (system clock), and the configurat…
-
@tsubakinohana The process will be very similar to the accelerometer, but the calls will need to be updated to the appropriate ones for the magnetometer. The C++ SDK has details on all of the libmetawear. calls for the magnetometer here: https://…
-
@AndooBundoo The devices are capable of log download while actively logging. However, streaming high bandwidth (e.g. acc/gyo) while downloading will most likely result in data loss. When you start a download, the present length of the log is "sna…
-
@hjpark The API allows TX power settings for any value supported by the chipset. For the MMS that is 8, 7, 6, 5, 4, 3, 2, 0, -4, -8, -12, -16, -20 and -40 dBm. Setting -40 dBm is not advisable as it may make the device unconnectable.
-
@Srinivasa The MMRL update for this feature is in testing now. It is getting some internal changes integrated from the MMS development line, so it will be an extended test cycle. Estimate would be a release end of next week barring unforeseen issues.
-
@Doubie Just playing with the sensorfusion a little bit at my desk. When sensor fusion is first enabled pitch and roll both start at zero. Shortly afterwards they converge to true pitch and roll values, presumably mostly from the gravity vecto…
-
@hjpark libmetawear.mbl_mw_debug_reset(s.device.board) clears all settings and resets all sensors on the device. So this will be reverting your tx_power command. Unless you really want to wipe your sensor settings or similar, you should not need t…
-
@Claudia_rf On the first screen of MetaBase, where the sensors are normally listed under My Devices and new ones can be added, you can swipe left on a given sensor to remove it from MetaBase. Then you can Add a Device again and it will allow you …
-
@Raghav The sensors will continue to log while downloading unless logging is disabled first. This is a supported and tested configuration. A download operation typically runs for a requested number of data points, or until presently logged valu…
-
@hjpark libmetawear.mbl_mw_debug_reset(s.device.board) clears all settings and resets all sensors on the device. So this will be reverting your tx_power command. Unless you really want to wipe your sensor settings or similar, you should not need t…
-
@joerguwemeyer I would recommend restarting the app and/or trying the MetaWear app instead of MetaBase for the firmware update. It appears there may have been a glitch during this update, devices shipping with firmware 1.5.0 should not have a …
-
@Doubie It may be within the error margin immediately after turning on the sensor fusion. If you are not using a fixture there may be some angle error in the final resting position. Auto calibration of the magnetometer may be kicking in or introd…
-
@giovanni_dq I had no problem running the stream_gyro_packed.py script. Are you using the latest version of the SDK? We can see the epoch is the same for clusters of 3 samples indicating that packets are coming in packed. GYRO: XX:XX:XX:XX:XX:…
-
@atonino Does the accounter work in count mode when you run your example with quaternions as the source? Unfortunately, there is very little additional room in the quaternion data packet (1 byte). The accounter should work in count mode using a 1…
-
@Neurology Could you share a complete data capture or is the file too large? Does this happen with every new data capture initiated? Are all samples after the initial shift experiencing the same offset, or does the date return to normal aft…
-
Some comments and notes on MetaWearUSB class and device behavior from other discussions. * Only one connection is allowed at a time. * Initiating USB communication will force a BLE disconnect. * Device continues advertising for discovery whil…
-
@eletromago At the very least it looks like the system bluetooth libraries are missing -- one of the errors deep in the log is that it cannot find bluetooth/bluetooth.h. Please try running these commands on your system to install all of the OS…
-
@qpal1012 There is a misunderstanding here regarding Firmware 1.4.4 and 2MHz PHY. * Firmware 1.4.4 was running a BTLE 4.1 compliant software stack. 4.1 had absolutely no support for 2MHz PHY. Any results obtained with 1.4.4 were absolutely o…
-
@hjpark How is your python script disconnecting from the device? The device should not be resetting on disconnect unless commanded to. A parameter value of 8 for 8dB is supported on MMS model. In order for a setting to persist through a power …
-
@arzt2283 Yes, this is supported by the firmware. The second parameter to mbl_mw_logging_start named overwrite sets the mode. Pass a 1 for ring memory, or a 0 to halt logging once it is full. https://mbientlab.com/documents/metawear/cpp/0/logging…
-
To test log readout performance there is a simple python script in the SDK log_acc_perf.py . On the Win10 dev machine I receive ~735 entries/s over BLE, ~5725 entries/s over USB. Note that accelerometer samples require 2 entries each due to length. …
-
@Srinivasa I want to clarify a couple of things. MMRL uses a slightly older chipset than MMS, which does not support LE Coded PHY at all, so the slowdown cannot be related to it. Firmware 1.4.4 did not support 2M PHY at all, 1.5.1 primarily…