Matt

About

Username
Matt
Joined
Visits
348
Last Active
Roles
Member

Comments

  • @jec I would suggest trying a soft reset of all devices using the diagnostic page (or reset command in python) and then running your MetaBase configuration. The dev tools may be leaving subsystems in an unexpected state by consuming resources, espec…
  • @JCagle95 Those functions are accessing registers that the metawear interface exposes, and not always raw registers of the peripheral sensors. Sometimes there is a direct mapping. If you don't see a particular register defined in the header files th…
  • @Nbooth The limits in the docs are supported by all devices, the MMS chipset specifically supports the extended range of configurations mentioned above. Higher numbers increase the transmit power, which can help with communications in some cases.…
  • @organ006 Please download the MetaWear app on one of your mobile devices in addition to MetaBase. There is a toggle switch when scanning that will search for MetaBoot devices and it seems that your devices may be stuck there. The lack of charge LED …
  • @nickp This should work correctly in all versions of the MetaBase app, which one are you using?
  • @jec The error is thrown in upstream code, but has no effect in our testing. Are you having issues in your scripts?
  • @jec Based on the python tag I will assume you are working with custom scripts? In that case, for raw accel/gyro/mag there is the option of using packed mode, which puts multiple samples in a ble packet, and reduced data packets by 1/3. Other …
  • @RaquelProus Hi, I believe this was a duplicate question to one directed by one of your colleagues, here is what the response was. In the hardware/firmware design MMR and MMRL are the same. There are two basic ways to go about distinguishing M…
    in MMR and MMRL Comment by Matt June 23
  • @toffy_dee I haven't worked with kotlin but it looks very close compared to the MetaBase log download code. I would use the interactive debugger and poke around near the r.subscribe and the route = r lines to make sure the right objects are gettin…
  • @nickp On the diagnostic page for a sensor there is an option to issue a soft reset to the device. This will clear the present state and typically resolves issues with configuration. Give that a try and let us know if it resolves the issue.
  • @JCagle95 I can confirm the present Android SDK release has not exposed the log length endpoint. The scaffolding is in place, as it is called during the readout process, but some slight sdk changes would need to be made to expose it as a discrete…
  • @jbmere MMRL is more of a marketing name, in the hardware/firmware design MMR and MMRL are the same. There are two basic ways to go about distinguishing MMR from MMRL -- All hardware revision 0.5 MMR devices are MMRL, or via the presence of the b…
  • @Srinivasa Note that the second parameter is max interval, and should always be requested >= min interval. This may explain why you are getting no data with that setting. Here is Apples recommendation for the connection parameter settings. It …
    in Faster Download Comment by Matt May 25
  • @connorwinter Yes, this can be achieved with the present firmware. It seems like the best way to handle this would be to have a timer for starting logging be a repeated type, with delayed start. The second timer for stopping logging could be a…
  • @mhcohen56 There was no change made to sensor fusion in firmware 1.7.3. Based on your graphs previously provided, it appears that your formula for conversion to euler angles is reasonably accurate, that is to say the waveforms are similar in sha…
  • @awsllcjeff Is the data you are working with from coming from one of the app's logged CSV files with named headers? Our sensors adopted the bosch sensorfusion convention for pitch, roll and yaw, which correspond to x, y, and z axis rotations. …
  • @awsllcjeff The sensors are in the same orientation on the MetaMotionR sensors as the shuttle board you are showing. The magnetometer raw outputs for Y and Z are inverted in firmware to align them with the IMU axes and the orientation shown in…
  • @Srinivasa Could you confirm that there is a disconnect-reconnect cycle after forcing the 1M PHY? The setting only affects the link negotiation process, which typically occurs shortly after a connection is established.
  • @glebski Our Cpp SDK is considered the reference implementation for the MetaWear protocol, everything you can want to know about the protocol is there, written in code. If there is really no way to do Cpp bindings for your language, I would hi…
  • @ijimenez The Python SDK is asynchronous in design so you should not have any issue running QT on the main thread. Just be sure you are not making any blocking calls used in our examples like time.sleep() or Event.wait().
  • @bobaloo mbl_mw_sensor_fusion_write_calibration_data will write the calibration data into volatile memory, which will work until the device is reset or loses power. So it will persist a disconnect, but not a reset (restart) of the device. The …
  • @arzt2283 Be sure that you have updated to the latest version of the MetaBase App. Are all of your devices affecter, or just some? Are they affect all the time or just some of the time? If the IMU sensors on the device are damaged, they may…
  • @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…
    in Faster Download Comment by Matt April 15
  • @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