rlin

About

Username
rlin
Joined
Visits
112
Last Active
Roles
Member

Comments

  • Have a question regarding erasing macros, I know we need to disconnect to erase macros, but do I have to do: 1. Erase all macros 2. Disconnect 3. Re-connect 4. Set new macros Or can I do the following: 1. Erase all macros 2. Set new macros …
  • If we set the sensor name with a macro on boot, what will happen if a user tries to rename the device again? Will the name be set twice or the new macro will overwrite previous one? I don't find a function to erase a specific macro beside erasing al…
  • Calibration macro helps, but that doesn't solve all the problems. One side effect when unintentional reboot happens is sensor name would also get reset. It's hard to find the right sensor when there are multiple sensors and multiple iPads. We swap…
  • Hi Eric, Yes, the board is resetting. Do you know what's causing the board to be resetting? If I don't save the calibration data to the board, it never resets itself. When I do save the calibration, the board resets itself after a few re-connect…
  • Can this bug be confirmed?
  • Hi Laura, I attached a simple iOS app that replicate this in the previous post (CalibrationTest.zip). I missed the last segment when I copied. That part of the stream is similar except calibration state went back to 0,0,0. Here is the segment…
  • The problem is after "The connection has timed out unexpectedly.", the sensor calibration state reverts to unreliable after reconnect. It seems the calibration data is being cleared when this happens every time. In addition, the connection error …
  • I created mock up app that should reproduce the problem. It will connect and calibrate the device if it's unreliable. If you do disconnect/connect a few times after device is calibrated, you will see the exception message with disconnect.
  • Connecting Connected After Connect: mbl_mw_sensor_fusion_calibration_state_data_signal accelrometer,0,gyroscope,0,magnetometer,0 Calibration: mbl_mw_sensor_fusion_calibration_state_data_signal accelrometer,0,gyroscope,0,magnetometer,0 accelrometer,0…
  • @Laura said: @rlin, Can you confirm that after the disconnects you did not drop the sensors (this would affect calibration). Drop the sensor as having impact force on the sensor? No, the sensor is sitting stationary on flat surface. …
  • We use mbl_mw_debug_disconnect(device.board) when the sensor is connected. Yes, the first few reconnects, the board will return HIGH_ACCURACY instantly, but after a while (5 ~ 10 disconnect - reconnects) it will become UNRELIABLE again.
  • We used the logic from https://github.com/mbientlab/MetaWear-SDK-Python/blob/master/examples/calibrate.py as example for our iOS implementation.
  • @Eric said: Sorry, it slipped through the cracks. An update to the C++ sdk has been pushed with this change. I saw the fix in C++ SDK, but it's not part of the latest ios 3.2.0 pod. Can it be included in the next ios sdk update? Thanks!
  • Hi Eric, is there any updates with the fix? Thanks.
  • Changing if (force) to if (force && !pending_fns.empty()) in C++ SDK's AsyncCreator::create_next seems to fix the problem. Does this make sense? void AsyncCreator::create_next(bool force) { // if (force) { if (force && !pe…
  • I think I understand now, but I want to confirm is the execution order to received_progress_update is always after the relative mbl_mw_logger_subscribe callbacks? i.e Progress with entriesLeft == 0 would be called after the last subscribe data callb…
  • Hi Eric, We did use it as an template, but to be more specific to our problem using the example code. mbl_mw_logger_subscribe(temperatureSignal, bridge(obj: self)) { (context, data) in let _self: DeviceViewController = bridge(ptr: context…