gjin

About

Username
gjin
Joined
Visits
74
Last Active
Roles
Member

Comments

  • @Matt Thanks for the response. Yes, it is repeatable. I have the following tests, all comes out to 98.44-98.45Hz ~2min ~3min ~5min ~10min ~13min This doesn't occur with the other MMRs that I've tested so far from this …
  • @stephen That's great. Thank you!
  • @Laura We are trying to repro the problem with MetaBase App, but found this problem with the app.
  • @Laura The problem isn't related to export or file format. The "Name Session" prompt does not show up after completing the download. In the video that I posted above, fast forward to about 35 seconds, and you can see that the app just skip …
  • * Does this consistently happen on the 6th or 7th use? No. It could be 5th, or 10th or 15th. The only trend is that it could happen after some repeated usage. * The data does in fact not show up anywhere on your device? …
  • @Eric We had a fourth sensor showing the timestamp jump issue. We also noticed that with all 14 incidents across 4 sensors, the amount of seconds changed is the same: 6144 seconds. In my two examples above: 6151.55-7.540999989 = 6,144.…
  • @Eric Here is snippet of what we do to start and stop logging func start() { // Configure MetaWear mbl_mw_settings_set_connection_parameters(device.board, 7.5, 7.5, 0, 6000) mbl_mw_metawearboard_set_time_for_response…
  • @Laura @Eric We are logging sensor fused Acceleration and MF data simultaneously, then download from log to iOS. We just read the timestamp that's in the log, and have no code relating to timestamps. Each sample is about 30 seconds in duration…
  • @Eric, @Laura We found a third MMR with timestamp error. There were 5 incidents out 279 samples taken between Oct 29 - 30, 2018. We also found more incidents, 10 out of 1002 samples taken during that period by the second MMR reported yesterday…
  • @Eric, @Laura My team did more digging into the pervious results. * In addition to the 2 incident reported above, the same sensor produced 6 additional incidents in Feb, 2019. We have 8 total. * A different MMR had 3 incidents out of 404 …
  • We are using v3.1.9 of iOS SDK. We've been using 8 different MMRs the last few months without this issues. Issue did not reproduce in MetaBase app. That is not surprising since within that one hour period we had about 45 normal samples, and 2 …
  • Hi Laura, This is not an editor issue. Below is the actual epoch times received from the sensor. Jumped from 1550050851.54 to 1550056995.549 then back down to 1550050851.559 Thanks
  • Eric, I am experience the same issues with MetaMotion R, HW 0.3. Trying to reapply 1.4.4. firmware update.
  • I tried 1.3.6, and as expected, no change in behavior. I also noticed that the drift/offset is less dramatic when moving in North-South direction than East-West direction. Hopefully this is a helpful clue.
  • Thanks Eric. Does it make sense to downgrade to 1.3.6 and retry?