CTGreybeard

Comments

• That all said, of course, it did connect after the fourth attempt.

  in MacOS: Is there a way to rate throttle SensorFusion? Comment by CTGreybeard March 2017
• Unfortunately the develop branch breaks the functionality of the sample app. I get several missing file warnings for the framework and one warning in the app itself. The app does build and run, detects the board, but will not connect. Up until that …

  in MacOS: Is there a way to rate throttle SensorFusion? Comment by CTGreybeard March 2017
• Thanks, I'll try that. You say that is "one way" to throttle the output, are there other ways?

  in MacOS: Is there a way to rate throttle SensorFusion? Comment by CTGreybeard March 2017
• Found it! Something in "~/Library/Application Support/com.mbientlab.metawear.devices/" was messed up. Removing that directory let the app continue.

  in Assertion failed: (self.activateCount >= 0) Comment by CTGreybeard March 2017
• I have connected via the iOS apps, MetaWear and MetaBase and they connect and work fine. I have tried a reset to factory but that has not affected my assertion failure.

  in Assertion failed: (self.activateCount >= 0) Comment by CTGreybeard March 2017
• The Metawear is just flopping around in the case. There is a small bit of what might be hot glue in the bottom but it's not attached any more. I do see the CAD files, I'll design something around that. Thanks.

  in 3-D designs for cases? Comment by CTGreybeard March 2017
• Thanks.

  in Buzzer broke off, need wiring details Comment by CTGreybeard March 2017
• I would say it took a couple of days and had stopped reporting completely. It has been several days though since I have checked again. I will test again and let you know.

  in onboardThermistor stopped reporting, onDieThermistor reporting OK Comment by CTGreybeard March 2017