Last Active


  • After a bunch of debugging, I determined that I was dealing with a bad humidity sensor (it must have been damaged during board population). I can confirm that the Metawear API works fine when talking to an undamaged sensor :-) Cheers, Jeremy
  • I verified that the write completes with a logic analyzer, but it seems the extra '0' bytes are causing the transactions to fail. Are there any plans to expand I2C API flexibility in future firmware releases?
  • I finally got around to testing my humidity sensor and it seems there are some issues getting the MetaWear to communicate with it. As we had discussed before, the humidity sensor is a bit unconventional in that it has no register addresses. Commun…
  • Sorry for the lack of clarity...what I meant is "tell the ADC to use the internal 1.2V reference instead of a ratio of supply voltage." The line of code above appears to accomplish that.
  • Matt, Thanks for the response. I'm still waiting for the daughterboard I built to ship so that I can test the I2C interface. I'll let you know what I find -- it would be great to have more flexible I2C support in a subsequent firmware rev. Tha…
  • I think I found the answer to my own question. I believe the following line of code will use the internal 1.2V reference: gpioModule.routeData().fromAnalogIn((byte) 2, AnalogReadMode.ABS_REFERENCE);
  • Another question regarding I2C: Is it possible to issue a read with no register address? My humidity sensor has no register map and only outputs a 2 byte humidity value.
  • I resolved this. The problem was that I stuck the repository url in the 'buildscript' section of the gradle script instead of 'allprojects'.